xsltforms-support — XSLTForms support list

[Xsltforms-support] Calendar display patch

[David C. <ot...@cr...>]

There's a display problem with the popup calendar selection when the
selected day is the first day of the month, causing the calendar cells
corresponding to the previous month's days in the same week to have the
"selected" class applied to them. The following patch (also attached in
case the inline code is mangled) fixes the problem.

- David


Index: src/js/controls/Calendar.js.xml
===================================================================
--- src/js/controls/Calendar.js.xml     (revision 374)
+++ src/js/controls/Calendar.js.xml     (working copy)
@@ -187,13 +187,13 @@
 
         for (var j = 0; j < 7; j++, cont++) {
             var cell = trLine.childNodes[j];
+            var day_in_month = (cont >= firstDay && cont < firstDay + daysOfMonth);
             Core.setClass(cell, "hover", false);
             Core.setClass(cell, "today", currentMonthYear && day == this.currentDay);
-            Core.setClass(cell, "selected", day == this.day);
+            Core.setClass(cell, "selected", day_in_month && day == this.day);
             Core.setClass(cell, "weekend", (j+ini)%7 > 4);
 
-            cell.firstChild.nodeValue
-                = (cont >= firstDay && cont < firstDay + daysOfMonth)? day++ : "";
+            cell.firstChild.nodeValue = day_in_month ? day++ : "";
         }
     }
 };

[Xsltforms-support] Extension XPath functions transform() and serialize() have bad namespace so they can't be used

[Kostis A. <ank...@gm...>]

The 2 XSTLTForms extension function are not declared specificaly as
xforms-funcs ,
yet their definition expects them to be in this NS
(http://www.w3.org/2002/xforms)
(definition at file src/js/xpathexpr/XPathCoreFunctions.js.xml:956)

- Reported against rev374, Not Chrome (probably but not sure others also)


Was that indeed your intention, Alan?
I mean, did you plan to add them on separate NS?
(I remind that you have already apply this for is-valid() extra function,
so it is also included in the xforms-NS.)

If yes,
then the patch below fixes the bug so as these extra XSLTForms XPath
functions to be available to the users of the library.
(also attached for if garbled)


Greetings for the Holidays,
  Kostis Anagnostopoulos



Index: src/xslt/elements/named-templates/fctfullname.xsl.xml
===================================================================
--- src/xslt/elements/named-templates/fctfullname.xsl.xml	(revision 374)
+++ src/xslt/elements/named-templates/fctfullname.xsl.xml	(working copy)
@@ -41,7 +41,7 @@
 				</xsl:when>
 				<xsl:otherwise>
 					<xsl:choose>
-						<xsl:when test="contains(' boolean-from-string is-card-number
count-non-empty index power random if choose property digest hmac
local-date local-dateTime now days-from-date days-to-date
seconds-from-dateTime seconds-to-dateTime adjust-dateTime-to-timezone
seconds months instance current context event nodeindex is-valid ',
concat(' ', $fctname, ' '))">http://www.w3.org/2002/xforms
<xsl:value-of select="$fctname"/></xsl:when>
+						<xsl:when test="contains(' boolean-from-string is-card-number
count-non-empty index power random if choose property digest hmac
local-date local-dateTime now days-from-date days-to-date
seconds-from-dateTime seconds-to-dateTime adjust-dateTime-to-timezone
seconds months instance current context event nodeindex is-valid
serialize transform ', concat(' ', $fctname, '
'))">http://www.w3.org/2002/xforms <xsl:value-of
select="$fctname"/></xsl:when>
 						<xsl:otherwise>http://www.w3.org/2005/xpath-functions
<xsl:value-of select="$fctname"/></xsl:otherwise>
 					</xsl:choose>
 				</xsl:otherwise>

Re: [Xsltforms-support] Strange error in submission with method=get & replace=all

[Javier D. <jd...@ge...>]

Hello,

we have corrected the error commenting line 233 of xsltforms.js:

if (Core.isMozilla) { req.overrideMimeType("text/xml"); }

But I don't know if this would affect to something else...

Best Regards,
Javier

Javier Díaz escribió:
> Hello,
>
> I have an strange javascript error in firefox, when in a xml of 
> xsltforms I am submitting using method=get and replace=all to a second 
> xsltforms page. It seems to work ok, but the javascript error worries me.
>
> I have seen in 
> http://www.agencexml.com/xforms-tests/testsuite/XForms1.1/Edition1/Chapt11/11.9/11.9.b.xhtml 
> a test case that works exactly as my xmls, when pressing "Get Data" 
> button, all seems to work ok, but in firefox error console I get:
>
> Error: mal formado
> Archivo de origen: 
> http://www.agencexml.com/xforms-tests/xsltforms/echo.php?carOwner=Henry&make=Acura&color=White
> Línea: 17, columna: 33
> Código fuente:
> QUERY_STRING=carOwner=Henry&make=Acura&color=White
>
> It seems all problems are related with characters as &, <, >, that makes 
> the resulting xml bad formed, because when I get the resulting xml from 
> this request and validate with an xml parser I get:
>
>
> $ xmllint --noout test.xml
> test.xml:17: parser error : EntityRef: expecting ';'
> QUERY_STRING=carOwner=Henry&make=Acura&color=White
>                                 ^
> test.xml:17: parser error : EntityRef: expecting ';'
> QUERY_STRING=carOwner=Henry&make=Acura&color=White
>                                             ^
> test.xml:19: parser error : EntityRef: expecting ';'
> REDIRECT_QUERY_STRING=carOwner=Henry&make=Acura&color=White
>                                          ^
> test.xml:19: parser error : EntityRef: expecting ';'
> REDIRECT_QUERY_STRING=carOwner=Henry&make=Acura&color=White
>                                                      ^
> test.xml:29: parser error : EntityRef: expecting ';'
> REQUEST_URI=/xforms-tests/xsltforms/echo.php?carOwner=Henry&make=Acura&color=Whi
>                                                                 ^
> test.xml:29: parser error : EntityRef: expecting ';'
> REQUEST_URI=/xforms-tests/xsltforms/echo.php?carOwner=Henry&make=Acura&color=Whi
>
> The error is thrown in line 1910 os xsltforms.js, "req.send(null)", when 
> getting the data to the browser with XMLHttpRequest.
>
> Best Regards,
> Javier
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>   

[Xsltforms-support] Accessing instance data from JS

[Grégoire C. <gco...@gm...>]

Hi,

I've registered a JS function on "xforms-submit-done" with this :

<xf:submission id="search" action="search.xql" method="get"
replace="instance" instance="instance-results">
  <xf:action ev:event="xforms-submit-done">
    <xf:load resource="javascript:dealWithResults()" />
  </xf:action>
</xf:submission>

So the query is passed to "search.xql" and the results are put in the
instance named "instance-results", then the JS function called
"dealWithResults" is launched. This part works perfectly.

My problem is that, in the JS function, I thought that I could use
getElementById('instance-results') to access the received data with XPath.
But the instance was transformed with XSL to an empty <span> element :

<span id="instance-results" class="xforms-instance"></span>

Is there a way to access the instance data from my JavaScript function?

Thanks,
Grégoire

[Xsltforms-support] Strange error in submission with method=get & replace=all

[Javier D. <jd...@ge...>]

Hello,

I have an strange javascript error in firefox, when in a xml of 
xsltforms I am submitting using method=get and replace=all to a second 
xsltforms page. It seems to work ok, but the javascript error worries me.

I have seen in 
http://www.agencexml.com/xforms-tests/testsuite/XForms1.1/Edition1/Chapt11/11.9/11.9.b.xhtml 
a test case that works exactly as my xmls, when pressing "Get Data" 
button, all seems to work ok, but in firefox error console I get:

Error: mal formado
Archivo de origen: 
http://www.agencexml.com/xforms-tests/xsltforms/echo.php?carOwner=Henry&make=Acura&color=White
Línea: 17, columna: 33
Código fuente:
QUERY_STRING=carOwner=Henry&make=Acura&color=White

It seems all problems are related with characters as &, <, >, that makes 
the resulting xml bad formed, because when I get the resulting xml from 
this request and validate with an xml parser I get:


$ xmllint --noout test.xml
test.xml:17: parser error : EntityRef: expecting ';'
QUERY_STRING=carOwner=Henry&make=Acura&color=White
                                ^
test.xml:17: parser error : EntityRef: expecting ';'
QUERY_STRING=carOwner=Henry&make=Acura&color=White
                                            ^
test.xml:19: parser error : EntityRef: expecting ';'
REDIRECT_QUERY_STRING=carOwner=Henry&make=Acura&color=White
                                         ^
test.xml:19: parser error : EntityRef: expecting ';'
REDIRECT_QUERY_STRING=carOwner=Henry&make=Acura&color=White
                                                     ^
test.xml:29: parser error : EntityRef: expecting ';'
REQUEST_URI=/xforms-tests/xsltforms/echo.php?carOwner=Henry&make=Acura&color=Whi
                                                                ^
test.xml:29: parser error : EntityRef: expecting ';'
REQUEST_URI=/xforms-tests/xsltforms/echo.php?carOwner=Henry&make=Acura&color=Whi

The error is thrown in line 1910 os xsltforms.js, "req.send(null)", when 
getting the data to the browser with XMLHttpRequest.

Best Regards,
Javier

[Xsltforms-support] focus span necessary?

[Stephen C. <Ste...@ut...>]

Hello Alain,

What should be a simple problem, but...

I have a list of xform input controls down the page with an xf:output  
in the  middle. The alignment of the output is slightly different to the 
inputs due to the presence of a small span (class="focus") on the left 
of the input label but not with the output label. However if  in my css 
i have

span.focus {display:none;}

the alignments do not change.

Normally, I'd use a workaround for something like this but in this case 
it may be of interest.

Is it intended that the focus span will have some use?

Thanks


-- 
Regards

Stephen Cameron

Data Programmer
Integrated Marine Observing System  (IMOS)
eMarine Information Infrastructure Project
University of Tasmania, Private Bag 21, Hobart, TAS 7001, Australia

Tel: +61 3 6226 8507
Fax: +61 3 6226 2997
Email: ste...@ut...
URL: http://www.imos.org.au/eMII.html

[Xsltforms-support] Adding XPath functions

[David C. <ot...@cr...>]

I'm trying to update an application that used an older version of
XSLTForms to use a more current release of XSLTForms but locally added
XPath functions are no longer working. Can someone point me to the
appropriate documentation or advise me what I'm doing wrong?

For a simple test case I've modified the Hello World example, as shown
below, to add a simple function in my own namespace. This works in
Safari, Chrome, and Opera, but not Firefox up through SVN rev 360. It
doesn't work in any of those browsers from SVN rev 361 onwards.

<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="xsltforms/xsltforms.xsl" type="text/xsl"?>
<html xmlns="http://www.w3.org/1999/xhtml"
      xmlns:xf="http://www.w3.org/2002/xforms"
      xmlns:local="http://example.com/local">
  <head>
    <title>Testing local XPath functions</title>
    <script>
      window.addEventListener('load', function() {
        XPathCoreFunctions['http://example.com/local sample'] =
          new XPathFunction(false, XPathFunction.DEFAULT_NONE, false,
            function() { return "a test"; } );
      }, false);
    </script>
    <xf:model>
      <xf:instance>
        <data xmlns="">
          <PersonGivenName/>
        </data>
      </xf:instance>
    </xf:model>
  </head>
  <body>
    <p>This is <xf:output value="local:sample()" />.</p>
    <p>Type your first name in the input box. <br/>
       If you are running XForms, the output should be displayed in the output area.</p>   
    <xf:input ref="PersonGivenName" incremental="true">
      <xf:label>Please enter your first name: </xf:label>
    </xf:input>
    <br />
    <xf:output value="concat('Hello ', PersonGivenName, '. We hope you like XForms!')">
      <xf:label>Output: </xf:label>
    </xf:output>
  </body>
</html>

When the above page fails to load, the following alert is generated:

    Error initializing :

    Function http://www.w3.org/2005/xpath-functions sample() not found

Looking at the generated HTML in Safari, the generated JavaScript has
the expected namespace when creating the FunctionCallExpr prior to r361:

    XPath.create("local:sample()",new FunctionCallExpr('http://example.com/local sample'));

But beginning with r361 (and with all versions when loaded in Firefox),
the namespace used when creating the FunctionCallExpr is wrong:

    XPath.create("local:sample()",new FunctionCallExpr('http://www.w3.org/2005/xpath-functions sample'));

Is this a XSLTForms bug or am I doing something wrong?

- David

Re: [Xsltforms-support] GET method query parameter, using in XForm

[COUTHURES A. <ala...@ag...>]

> * Is there some document describing all these extras and tricks of
> XSLTForms somewhere?
>   
A wikibook has been created for that: http://en.wikibooks.org/wiki/XSLTForms

These functions are very recent and are not yet described. I will update
the wikibook as soon as possible...

-Alain

Re: [Xsltforms-support] GET method query parameter, using in XForm

[Kostis A. <ank...@gm...>]

Hi,

On Wed, Mar 31, 2010 at 12:05 AM, COUTHURES Alain
<ala...@ag...> wrote:
> Hello,
>> This would be simple with XSL stylesheet but having done the design work
>> for XForm I don't really want to change much for the display version.
>>
> I have just added an extra transform() XPath function to be used in
> xf:output/@value with a mediatype for XHTML or SVG.
>
> Does it help?

Seems very usefull. Thanks.

* Is there some document describing all these extras and tricks of
XSLTForms somewhere?

Kostis

Re: [Xsltforms-support] GET method query parameter, using in XForm

[COUTHURES A. <ala...@ag...>]

Hello,
> Having developed an Xform to submit an model instance to a service and 
> have that instance persisted on the server, I now would like to display 
> the instance in a modified version of my submission form, with all 
> xf:input controls replaced by xf:output controls.
>   
Maybe a global readonly constraint would do the trick...
> I want to create hyperlinks with the id of the persisted instance as a 
> request parameter, clicking the link opens the (hopefully cached) XForm 
> which reads the id parameter and sends a customised submission to the 
> server to retrieve a specific instance which is then displayed.
>   
Triggers are rendered as hyperlinks with appearance="minimal". Did you 
try this?
> This would be simple with XSL stylesheet but having done the design work 
> for XForm I don't really want to change much for the display version.
>   
I have just added an extra transform() XPath function to be used in 
xf:output/@value with a mediatype for XHTML or SVG.

Does it help?

Thanks!

-Alain

Re: [Xsltforms-support] xf:select1 'minimal' cannot select single item after itemset updated

[COUTHURES A. <ala...@ag...>]

Kostis,
> (I hope that i'm not becoming too anoying...)
>   
On the contrary, it's very interesting to know what points have to be 
improved from your point of view.
> I think thar the xf:select are now much improved, but there is still 1
> minor problem that needs to be fixed:
>
> PROBLEM
> ----------------
> On a xf:select1 control with 'minimal' appearence that gets its
> pick-list from xf:itemset,
> When the itemset gets updated and results with only a single item,
> the user cannot select that single item.
>
>
> Note that when itemset gets updated with multiple-items, the problem
> is still there,
> but with the 1st pick-list item this time.
>
> In that case though, the user can interactively workaround it,
> by selecting first a different item (i.e. the 2nd), and then selecting
> back the 1st one,
> in order to properly set the underlying node-value.
>
> Reported against rev372, Chrome, Firefox, IE.
>
>
> SOLUTION
> ----------------
> To workaround it with xforms-code, an action like the one below maybe
> attached on some itemset-update event (i.e  'submit-done' event):
>    <xf:setvalue bind="/items/item[1]" if="note(/items/items[2])"
> /><!-- auto-select single-items -->
> But for some undetermined reason i can't make this trick to work on
> all xforms...
>
>
> Nevertheless, i think the correct behavior for when the itemset gets
> updated should either be:
>
>   a) to insert a 'null' item and set it preselected on the pick-list,
> which whould be auto-deleted after the first user-selection
> (this is the current behavior of the xf:select1 after the initial
> model construction)
>
>   b) or pre-select the single item, as similar to the workaround
> exemplified above, or .
>
>
> I would prefer the former solution (a), since it fixes the behavior
> even when pick-list has many items, and because it provides for
> implementing both choices to developers.
>
>   
XSLTForms is now only based on HTML select and, as you noticed, it isn't 
perfect. Other XForms implementations usually have the behavior you're 
describing.

This has not yet been a priority for XSLTForms because, at least, 1 or 2 
work days are required...

Thanks!

-Alain

Re: [Xsltforms-support] The css for xf:hint specifies an unnecessary 'width' declaration

[COUTHURES A. <ala...@ag...>]

Kostis,
> (sorry for the traffic)
>
> There is also another option for the hint-width:
> To keep the 'width' css-declaration and add:
>     width: 200px;
>     white-space: normal;
>
> Personally, i find this one a more pleasant effect.
>   
Thank you for this CSS improvement!

-Alain

Re: [Xsltforms-support] text/xml vs text/html

[COUTHURES A. <ala...@ag...>]

Hi Grégoire,
> I noticed that the examples at :
>     http://www.agencexml.com/xsltforms (bottom of the page)
> are served as text/html and work perfectly
No, they are .xml files...
>
> However, on my own computer, where I use the eXist database with the 
> Jetty server, all ".xml" files are served with a content-type of 
> text/xml. When I force the mime-type to "text/html", it seems that 
> XSLTForms doesn't apply the XSL at all.
text/xml is mandatory for XSLT transformation to be performed at 
client-side.

With eXistdb, the XSLT transformation can be done at server-side too.
>
> Is there a change since beta2, that makes the use of "text/xml" 
> compulsory?
Because of bad inline SVG support when the XSLT output is "html", 
current SVN release has an "xml" output so XHTML is used instead. 
Javascript part can now treat both HTML or XHTML.

I'm afraid this will be a manual option in XSLTForms beta 3 about output 
as "html" or as "xml" for XHTML....

Thanks!

-Alain

[Xsltforms-support] text/xml vs text/html

[Grégoire C. <gco...@gm...>]

Hi,

I noticed that the examples at :
    http://www.agencexml.com/xsltforms (bottom of the page)
are served as text/html and work perfectly

However, on my own computer, where I use the eXist database with the Jetty
server, all ".xml" files are served with a content-type of text/xml. When I
force the mime-type to "text/html", it seems that XSLTForms doesn't apply
the XSL at all.

Is there a change since beta2, that makes the use of "text/xml" compulsory?

Thanks,
Grégoire

[Xsltforms-support] xf:reset does not restore xf:itemset items modified by xf:submission

[Kostis A. <ank...@gm...>]

Hi,

Reseting a model does not restore a modified-by-submission xf:itemsets.
Reset indeed works when itemset was modified by an xf:delete
(xf:insert??) action.

Reported against rev372, Chrome, Firefox.


The following files demonstrate the problem.

XForms file
----------------
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="xsltforms/xsltforms.xsl" encoding="UTF-8"
type="text/xsl"?>
<html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml"
  xmlns:xf="http://www.w3.org/2002/xforms"
  xmlns:ev="http://www.w3.org/2001/xml-events"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="
     http://www.w3.org/2002/xforms
http://www.w3.org/MarkUp/Forms/2007/XForms-11-Schema.xsd
     http://www.w3.org/2001/xml-events
http://www.w3.org/MarkUp/SCHEMA/xml-events-attribs-1.xsd
">
  <head>
    <title>Restore xf:itemsets on xf:reset</title>
    <xf:model id="model-main" >
      <xf:instance id="inst-main">
        <main>
          <data >1</data>
        </main>
      </xf:instance>
      <xf:instance id="inst-items" >
        <items>
          <item>1</item>
          <item>2</item>
          <item>3</item>
        </items>
      </xf:instance>

      <xf:bind id="bind-data" nodeset="/main/data" />

      <xf:submission id="sub-fetch-items" resource="items.xml" method="GET"
          replace="instance" instance="inst-items"
      >
      </xf:submission>
    </xf:model>
  </head>

  <body>
    <p>Data: <xf:output  ref="/main/data"/> </p>
    <p>xf:itemset's bound-document contents:
      <xf:repeat nodeset="instance('inst-items')/item">
        <xf:output  ref="."/>
      </xf:repeat>
    </p>
    Select1(minimal): <xf:select1 ref="/main/data">
      <xf:itemset nodeset="instance('inst-items')/item">
        <xf:label ref="." />
        <xf:value ref="." />
      </xf:itemset>
    </xf:select1>
    Select1(full): <xf:select1 ref="/main/data" appearance="full">
      <xf:itemset nodeset="instance('inst-items')/item">
        <xf:label ref="." />
        <xf:value ref="." />
      </xf:itemset>
    </xf:select1>

    Select(minimal): <xf:select ref="/main/data">
      <xf:itemset nodeset="instance('inst-items')/item">
        <xf:label ref="." />
        <xf:value ref="." />
      </xf:itemset>
    </xf:select>

    <xf:trigger>
      <xf:label>Load items from file</xf:label>
      <xf:action ev:event="DOMActivate" >
        <xf:send submission="sub-fetch-items"/>
      </xf:action>
    </xf:trigger>
    <xf:trigger>
      <xf:label>Delete bound xf:itemset nodes</xf:label>
      <xf:action ev:event="DOMActivate" >
        <xf:delete nodeset="instance('inst-items')/*"/>
      </xf:action>
    </xf:trigger>

    <xf:trigger>
      <xf:label>Reset restores only xf:delete effects</xf:label>
      <xf:action ev:event="DOMActivate" >
        <xf:reset/>
      </xf:action>
    </xf:trigger>

  </body>
</html>

Items file
-------------
<items>
  <item>3</item>
</items>

Re: [Xsltforms-support] The css for xf:hint specifies an unnecessary 'width' declaration

[Kostis A. <ank...@gm...>]

(sorry for the traffic)

There is also another option for the hint-width:
To keep the 'width' css-declaration and add:
    width: 200px;
    white-space: normal;

Personally, i find this one a more pleasant effect.

Kostis

On Tue, Mar 30, 2010 at 1:54 PM, Kostis Anagnostopoulos
<ank...@gm...> wrote:
> I have noticed minor appearence glitch,
> that on long hints, the background box's width is limited, and as a re3sult,
> the text splis-out to the left.
>
> The cause of this is a 'width: 200px' css declaration on the
> hint-value's css rule.
>
> Reported against:
> - rev372
> - all browsers
>
> If this is indeed a bug,
> the following patch would fix the problem:
>
> Index: trunk/src/css/icones.css.xml
> ===================================================================
> --- src/css/icones.css.xml      (revision 371)
> +++ src/css/icones.css.xml      (working copy)
> @@ -43,7 +43,6 @@
>        background-color        : #ffffee;
>        position                        : absolute;
>        border                          : black 1px solid;
> -       width                           : 200px;
>        margin-top                      : 16px;
>        margin-left                     : -16px;
>        padding                         : 5px;
>
>
>
> Regards,
>  Kostis Anagnostopoulos
>

[Xsltforms-support] xf:select1 'minimal' cannot select single item after itemset updated

[Kostis A. <ank...@gm...>]

(I hope that i'm not becoming too anoying...)

Hi,

I think thar the xf:select are now much improved, but there is still 1
minor problem that needs to be fixed:

PROBLEM
----------------
On a xf:select1 control with 'minimal' appearence that gets its
pick-list from xf:itemset,
When the itemset gets updated and results with only a single item,
the user cannot select that single item.


Note that when itemset gets updated with multiple-items, the problem
is still there,
but with the 1st pick-list item this time.

In that case though, the user can interactively workaround it,
by selecting first a different item (i.e. the 2nd), and then selecting
back the 1st one,
in order to properly set the underlying node-value.

Reported against rev372, Chrome, Firefox, IE.


SOLUTION
----------------
To workaround it with xforms-code, an action like the one below maybe
attached on some itemset-update event (i.e  'submit-done' event):
   <xf:setvalue bind="/items/item[1]" if="note(/items/items[2])"
/><!-- auto-select single-items -->
But for some undetermined reason i can't make this trick to work on
all xforms...


Nevertheless, i think the correct behavior for when the itemset gets
updated should either be:

  a) to insert a 'null' item and set it preselected on the pick-list,
which whould be auto-deleted after the first user-selection
(this is the current behavior of the xf:select1 after the initial
model construction)

  b) or pre-select the single item, as similar to the workaround
exemplified above, or .


I would prefer the former solution (a), since it fixes the behavior
even when pick-list has many items, and because it provides for
implementing both choices to developers.


Regards,
  Kostis Anagnostopoulos

[Xsltforms-support] The css for xf:hint specifies an unnecessary 'width' declaration

[Kostis A. <ank...@gm...>]

I have noticed minor appearence glitch,
that on long hints, the background box's width is limited, and as a re3sult,
the text splis-out to the left.

The cause of this is a 'width: 200px' css declaration on the
hint-value's css rule.

Reported against:
- rev372
- all browsers

If this is indeed a bug,
the following patch would fix the problem:

Index: trunk/src/css/icones.css.xml
===================================================================
--- src/css/icones.css.xml	(revision 371)
+++ src/css/icones.css.xml	(working copy)
@@ -43,7 +43,6 @@
 	background-color	: #ffffee;
 	position			: absolute;
 	border				: black 1px solid;
-	width				: 200px;
 	margin-top			: 16px;
 	margin-left			: -16px;
 	padding				: 5px;



Regards,
  Kostis Anagnostopoulos

Re: [Xsltforms-support] When external schema defined, FF cannot see primitive xsd types

[Grégoire C. <gco...@gm...>]

Hi Kostis,

Kostis Anagnostopoulos a écrit :
> Grégoire, i did not understand where or why should i use your
> workaround - probably you did not understand the problem i presented
> in the fist place

I didn't looked closely enough. ;) So the only difference with my
problem is that your error comes from the "xsd" prefix not being used
anywhere else than in the "bind-otherItem" :
 <xf:bind id="bind-otherItem" nodeset="/data:root/data:otherItem"
type="xsd:integer" />

In this case, XSLTForms uses the "namespace::" axis to search through
the namespaces declared, but Firefox doesn't support this axis, hence
the error. But fortunately if you use this namespace somewhere else,
like in the "html" element, it will work. So you ought to try this :

<html
 xmlns="http://www.w3.org/1999/xhtml"
 xmlns:xf="http://www.w3.org/2002/xforms"
 xmlns:xsd="http://www.w3.org/2001/XMLSchema"
 xsd:workaroundForFirefoxBug="https://bugzilla.mozilla.org/show_bug.cgi?id=94270"
 xmlns:data="http://some-uri.org/data">

If I'm not wrong (am I?), adding a bogus attribute in the "html" element
won't do any damage/

Regards,
Grégoire

[Xsltforms-support] GET method query parameter, using in XForm

[Stephen C. <Ste...@ut...>]

Hello,

Is there a standard means to access the parameters of a GET request from 
within an Xform?

Having developed an Xform to submit an model instance to a service and 
have that instance persisted on the server, I now would like to display 
the instance in a modified version of my submission form, with all 
xf:input controls replaced by xf:output controls.

I want to create hyperlinks with the id of the persisted instance as a 
request parameter, clicking the link opens the (hopefully cached) XForm 
which reads the id parameter and sends a customised submission to the 
server to retrieve a specific instance which is then displayed.

This would be simple with XSL stylesheet but having done the design work 
for XForm I don't really want to change much for the display version.

Googling does not provide a ready answer to this question.



-- 

Regards

Stephen Cameron

Data Programmer
Integrated Marine Observing System  (IMOS)
eMarine Information Infrastructure Project
University of Tasmania, Private Bag 21, Hobart, TAS 7001, Australia

Tel: +61 3 6226 8507
Fax: +61 3 6226 2997
Email: ste...@ut...
URL: http://www.imos.org.au/eMII.html

Re: [Xsltforms-support] When external schema defined, FF cannot see primitive xsd types

[Kostis A. <ank...@gm...>]

2010/3/29 Grégoire COLBERT <gco...@gm...>:
> COUTHURES Alain a écrit :
>> FF doesn't support namespace:: axis and this is awful in many situations.
>>
> BTW, could everyone vote for this bug :
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=94270

Voted for it!


>> I have implemented workarounds for that but they are not perfect yet and
>> I'm not sure it's possible anyhow.
>>
> I'm not sure if this is exactly the same error I had weeks ago, but
> Kostis, maybe you should try to declare your own namespace in <html> and
> use it right away with a bogus attribute, as in the two last lines here
> with the "my" prefix :
>
> <html xmlns="http://www.w3.org/1999/xhtml"
>      xmlns:xf="http://www.w3.org/2002/xforms"
>      xmlns:ev="http://www.w3.org/2001/xml-events"
>      xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>      xmlns:my="http://www.myowndomain.com"
>
> my:workaroundForFirefoxBug="https://bugzilla.mozilla.org/show_bug.cgi?id=94270"
>>

Grégoire, i did not understand where or why should i use your
workaround - probably you did not understand the problem i presented
in the fist place.
And not to be faulted, since the xform file i sent had an error that
prevented you from trying it,
to see the error for yourself.

For reference, i'm re-sending it, corrected:
(the xsd.xml file remains unchanged)

-------------------
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="xsltforms/xsltforms.xsl" encoding="UTF-8"
type="text/xsl"?>
<html
 xmlns="http://www.w3.org/1999/xhtml"
 xmlns:xf="http://www.w3.org/2002/xforms"
 xmlns:xsd="http://www.w3.org/2001/XMLSchema"
 xmlns:data="http://some-uri.org/data"
>
 <head>
   <title>external-schema</title>

   <xf:model id="model-main" schema="xsd.xml">

     <xf:instance id="inst-main" >
       <data:root>
           <data:item />
           <data:otherItem />
       </data:root>
     </xf:instance>

     <xf:bind id="bind-item" nodeset="/data:root/data:item"
type="data:someInt" />
     <xf:bind id="bind-otherItem" nodeset="/data:root/data:otherItem"
type="xsd:integer" />

   </xf:model>

 </head>

 <body>
     Item: <xf:input bind="bind-item"  incremental="true" />
     OtherItem: <xf:input bind="bind-otherItem"  incremental="true" />
 </body>
</html>

Re: [Xsltforms-support] When external schema defined, FF cannot see primitive xsd types

[Grégoire C. <gco...@gm...>]

COUTHURES Alain a écrit :
> FF doesn't support namespace:: axis and this is awful in many situations.
>   
BTW, could everyone vote for this bug :

https://bugzilla.mozilla.org/show_bug.cgi?id=94270

> I have implemented workarounds for that but they are not perfect yet and 
> I'm not sure it's possible anyhow.
>   
I'm not sure if this is exactly the same error I had weeks ago, but
Kostis, maybe you should try to declare your own namespace in <html> and
use it right away with a bogus attribute, as in the two last lines here
with the "my" prefix :

<html xmlns="http://www.w3.org/1999/xhtml"
      xmlns:xf="http://www.w3.org/2002/xforms"
      xmlns:ev="http://www.w3.org/2001/xml-events"
      xmlns:xsd="http://www.w3.org/2001/XMLSchema"
      xmlns:my="http://www.myowndomain.com"
     
my:workaroundForFirefoxBug="https://bugzilla.mozilla.org/show_bug.cgi?id=94270"
>

Grégoire

Re: [Xsltforms-support] When external schema defined, FF cannot see primitive xsd types

[COUTHURES A. <ala...@ag...>]

Kostis,
> On FF, when an external schema is defined, xf:bind elements with
> 'type' attributes having xsd-types,
> i.e. "xsd:string, xsd:integer" fail to work,
> and the form on initialization complains about these types with a
> «Schema for namespace '' not defined for type string» msg.
> (or "Schema not defined" on older revisions)
>   
FF doesn't support namespace:: axis and this is awful in many situations.

I have implemented workarounds for that but they are not perfect yet and 
I'm not sure it's possible anyhow.

This has been improved and committed.
> The beta-2(rev260) release, on FF, although it did not work always
> quite-well with external schemas,
> it did *not* produce the err msg, and the attached-here test-case
> xform works indeed correctly.
> On rev262, the msg emerges on init, and the xsd-types ceases to work.
>   
beta-3 needs testing... Thank for your help!

-Alain

Re: [Xsltforms-support] xf:bind elements with no @nodeset attribute fails with a cryptic message, from rev361

[COUTHURES A. <ala...@ag...>]

Kostis,
> The generation of XPATH for <f:bind> elements with no @nodeset attribute
> (for instance, when <xf:bind> is used only for its @calculate or MIP
> attributes)
> fails with a cryptic message, saying: "4.*[1]".
>   
Because there is no sequence in XPath 1.0 and because node-set() was not 
supported in FF2 either, XSLTForms uses strings with a length.value 
structure. This is an XPath expression of 4 characters: "*[1]" (the 
first child element) and it is used as default value for xf:bind without 
@nodeset.
> The problem appeared on rev361 ("XPath parsing loop with node-set()")
> which i tihnk is caused by an erroneous xsl generated-template at
> trunk/buid/xsltforms.xsl:189:
>     <xsl:if test="//xforms:bind[not(@nodeset)]"><xexpr>4.*[1]</xexpr></xsl:if>
>   
Yes, xalan doesn't support heavy recursion so I have changed the main 
recursive mechanism to a loop. But I forgot to change "4.*[1]" into 
"*[1]" too !

This will be committed soon!

Thanks!

-Alain

Re: [Xsltforms-support] xf:bind elements with no @nodeset attribute fails with a cryptic message, from rev361

[Kostis A. <ank...@gm...>]

Attaching here forgotten test-case xform reproducing the error:


<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="xsltforms/xsltforms.xsl" encoding="UTF-8"
type="text/xsl"?>
<html
  xmlns="http://www.w3.org/1999/xhtml"
  xmlns:xf="http://www.w3.org/2002/xforms"
>
  <head>
    <title>Bind with no nodeset</title>

    <xf:model id="model-main" schema="xsd1.xml">

      <xf:instance id="inst-main" >
        <data:root/>
      </xf:instance>

      <xf:bind id="bind-someBind" />

    </xf:model>

  </head>

  <body>
      It fails on start up with a cryptic XPAth-invalid message.
  </body>
</html>


On Mon, Mar 29, 2010 at 2:19 PM, Kostis Anagnostopoulos
<ank...@gm...> wrote:
> The generation of XPATH for <f:bind> elements with no @nodeset attribute
> (for instance, when <xf:bind> is used only for its @calculate or MIP
> attributes)
> fails with a cryptic message, saying: "4.*[1]".
>
> The problem appeared on rev361 ("XPath parsing loop with node-set()")
> which i tihnk is caused by an erroneous xsl generated-template at
> trunk/buid/xsltforms.xsl:189:
>    <xsl:if test="//xforms:bind[not(@nodeset)]"><xexpr>4.*[1]</xexpr></xsl:if>
>
> - Reproduced on all browsers (ie, FF, chrome)
>
> Regards,
>  Kostis Anagnostopoulos
>