xsltforms-support

[Xsltforms-support] New release: Please give it a try!

[Alain C. <ala...@ag...>]

Hello,

Please find a new release for XSLTForms at 
www.agencexml.com/1.5beta/xsltforms.zip

It has not yet been fully tested because a lot of changes have been made 
and you are welcome to locate remaining issues with your own forms.

The XSLT part has been reduced to minimal for better performance. 
Instead of parsing the XPath expressions and transforming all the XForms 
elements into HTML elements, it basically just transposes the non-HTML 
elements into sort-of custom elements: xforms:* elements become xforms-* 
elements with xf-* and ev-* attributes.

Have a look with your favorite browser debugger! Actually, authors could 
even prefer to directly write/generate forms with this new notation and 
forget about the XSLT step. You can compare two sources for the same 
form: hello.xml and hello.htm

XSLTForms Javascript classes constructors are obtaining their properties 
directly from xf-* attributes and XPath parsing is then performed.

No ids are automatically added as previously.

Extra xf-* attributes and extra xforms-* elements are used to embed 
effective HTML rendering elements, for example, xforms-body or 
xforms-repeat-item while, before, span or div elements where used.

XSLTForms classes for xforms:select and xforms:itemset had to be 
partially rewritten.

SVG support has been basically tested too.

CSS styling is not anymore based on xforms-* classes but on custom 
element names and attribute selectors. For example, the extra xf-bound 
attribute, when present, says that the XForms control is bound to a 
node, eventually a not relevant one, and the extra xf-notrelevant 
attribute can, then, be checked...

Thank you for your contribution!

--Alain

Re: [Xsltforms-support] New release: Please give it a try!

[Tim T. <tim...@gm...>]

Hello, Alain,

Congratulations on this milestone! I am very eager to try and test the new
release. Is XSLTForms now using Fleur for XPath parsing? Does this mean
that XPath 3.0 functions are now supported? I guess I can test this myself
:)

It's quite amazing to see the xsltforms.xsl file down to just over 500
lines.

Thanks again for all your work.

Best regards,
Tim


--
Tim A. Thompson
Discovery Metadata Librarian
Yale University Library

On Wed, Feb 5, 2020 at 3:16 PM Alain Couthures <
ala...@ag...> wrote:

> Hello,
>
> Please find a new release for XSLTForms at
> www.agencexml.com/1.5beta/xsltforms.zip
>
> It has not yet been fully tested because a lot of changes have been made
> and you are welcome to locate remaining issues with your own forms.
>
> The XSLT part has been reduced to minimal for better performance. Instead
> of parsing the XPath expressions and transforming all the XForms elements
> into HTML elements, it basically just transposes the non-HTML elements into
> sort-of custom elements: xforms:* elements become xforms-* elements with
> xf-* and ev-* attributes.
>
> Have a look with your favorite browser debugger! Actually, authors could
> even prefer to directly write/generate forms with this new notation and
> forget about the XSLT step. You can compare two sources for the same form:
> hello.xml and hello.htm
>
> XSLTForms Javascript classes constructors are obtaining their properties
> directly from xf-* attributes and XPath parsing is then performed.
>
> No ids are automatically added as previously.
>
> Extra xf-* attributes and extra xforms-* elements are used to embed
> effective HTML rendering elements, for example, xforms-body or
> xforms-repeat-item while, before, span or div elements where used.
>
> XSLTForms classes for xforms:select and xforms:itemset had to be partially
> rewritten.
>
> SVG support has been basically tested too.
>
> CSS styling is not anymore based on xforms-* classes but on custom element
> names and attribute selectors. For example, the extra xf-bound attribute,
> when present, says that the XForms control is bound to a node, eventually a
> not relevant one, and the extra xf-notrelevant attribute can, then, be
> checked...
>
> Thank you for your contribution!
>
> --Alain
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

Re: [Xsltforms-support] New release: Please give it a try!

[Tim T. <tim...@gm...>]

Hello, Alain,

I've been testing an existing form with the new release and have some
feedback. First, the performance improvement seems impressive, and CSS
styling with Bootstrap now seems much easier. Thank you!

I did notice some issues after testing, however.

(1)
There seems to be a bug with XPath predicate filtering in xf:group
elements. For example, a group binding such as <xf:group
ref="instance('response')/response[*]">...</xf:group>, where the response
element should initially be empty (before a submission is executed) does
not seem to work.

See the test form copied below. Example form at:
https://www.tat2.io/basex2/static/xsltforms_test_2020-02-09.xml

(2)
I see that the xforms:var element is not currently supported. When loading
a form with an XForms variable defined, I get an error message:

Error initializing:

xforms:var is not supported

(3)
I also see that the XSLTForms Profiler does not seem to be available. When
I try to open it, I get an error:

File not found (404):
https://www.tat2.io/basex2/static/xsltforms_profiler.xhtml


*--Test form for XPath predicate bug--*

<?xml-stylesheet type="text/xsl" href="..."?>
<html xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="
http://www.w3.org/2001/XMLSchema" xmlns:xf="http://www.w3.org/2002/xforms"
xmlns:h="http://www.w3.org/1999/xhtml" xmlns:ev="
http://www.w3.org/2001/xml-events" xmlns="http://www.w3.org/1999/xhtml">
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
    <title>XForms/XPath Predicate Test</title>
    <style type="text/css"/>
    <model xmlns="http://www.w3.org/2002/xforms" id="m">
      <instance id="default">
        <data xmlns="">
          <default/>
        </data>
      </instance>
      <instance id="response">
        <data xmlns="">
          <response/>
        </data>
      </instance>
      <instance id="response-test">
        <data xmlns="">
          <response>
            <testing>Testing</testing>
          </response>
        </data>
      </instance>
    </model>
  </head>
  <body>
    <div class="container-fluid">
      <hr class="blue" />
      <h1>XForms/XPath predicate test</h1>
      <xf:group ref="instance('response')/response[*]">
        <h2 style="color: red;">This should not display!</h2>
        <xf:output value="concat('Value of &quot;serialize(.)&quot;: ',
serialize(.))"/>
      </xf:group>
      <xf:group ref="instance('response-test')/response[*]">
        <h2 style="color: blue;">This should display.</h2>
        <xf:output value="concat('Value of &quot;serialize(.)&quot;: ',
serialize(.))"/>
      </xf:group>
    </div>
  </body>
</html>



--
Tim A. Thompson
Discovery Metadata Librarian
Yale University Library

On Sun, Feb 9, 2020 at 11:06 AM Tim Thompson <tim...@gm...> wrote:

> Hello, Alain,
>
> Congratulations on this milestone! I am very eager to try and test the new
> release. Is XSLTForms now using Fleur for XPath parsing? Does this mean
> that XPath 3.0 functions are now supported? I guess I can test this myself
> :)
>
> It's quite amazing to see the xsltforms.xsl file down to just over 500
> lines.
>
> Thanks again for all your work.
>
> Best regards,
> Tim
>
>
> --
> Tim A. Thompson
> Discovery Metadata Librarian
> Yale University Library
>
> On Wed, Feb 5, 2020 at 3:16 PM Alain Couthures <
> ala...@ag...> wrote:
>
>> Hello,
>>
>> Please find a new release for XSLTForms at
>> www.agencexml.com/1.5beta/xsltforms.zip
>>
>> It has not yet been fully tested because a lot of changes have been made
>> and you are welcome to locate remaining issues with your own forms.
>>
>> The XSLT part has been reduced to minimal for better performance. Instead
>> of parsing the XPath expressions and transforming all the XForms elements
>> into HTML elements, it basically just transposes the non-HTML elements into
>> sort-of custom elements: xforms:* elements become xforms-* elements with
>> xf-* and ev-* attributes.
>>
>> Have a look with your favorite browser debugger! Actually, authors could
>> even prefer to directly write/generate forms with this new notation and
>> forget about the XSLT step. You can compare two sources for the same form:
>> hello.xml and hello.htm
>>
>> XSLTForms Javascript classes constructors are obtaining their properties
>> directly from xf-* attributes and XPath parsing is then performed.
>>
>> No ids are automatically added as previously.
>>
>> Extra xf-* attributes and extra xforms-* elements are used to embed
>> effective HTML rendering elements, for example, xforms-body or
>> xforms-repeat-item while, before, span or div elements where used.
>>
>> XSLTForms classes for xforms:select and xforms:itemset had to be
>> partially rewritten.
>>
>> SVG support has been basically tested too.
>>
>> CSS styling is not anymore based on xforms-* classes but on custom
>> element names and attribute selectors. For example, the extra xf-bound
>> attribute, when present, says that the XForms control is bound to a node,
>> eventually a not relevant one, and the extra xf-notrelevant attribute can,
>> then, be checked...
>>
>> Thank you for your contribution!
>>
>> --Alain
>> _______________________________________________
>> Xsltforms-support mailing list
>> Xsl...@li...
>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>
>

Re: [Xsltforms-support] New release: Please give it a try!

[Alain C. <ala...@ag...>]

Hello Tim,

(1) The xf:group processing was not correct: in the new approach, an 
xf-bound attribute has to be automatically added to each xforms-* 
element when xf-ref (or xf-bind) is evaluated as a non empty nodeset. 
CSS attribute selectors are, then, used to display/hide xforms-* 
elements accordingly.

(2) The xf:var processing was not functional: it should now work, at 
least, outside of actions.

(3) The profiler is actually just another external form: I have added 
the corresponding file into the updated .zip file at 
www.agencexml.com/1.5beta/xsltforms.zip

Thank you very much for your contributions!

--Alain

Le 09/02/2020 à 20:51, Tim Thompson a écrit :
> Hello, Alain,
>
> I've been testing an existing form with the new release and have some 
> feedback. First, the performance improvement seems impressive, and CSS 
> styling with Bootstrap now seems much easier. Thank you!
>
> I did notice some issues after testing, however.
>
> (1)
> There seems to be a bug with XPath predicate filtering in xf:group 
> elements. For example, a group binding such as <xf:group 
> ref="instance('response')/response[*]">...</xf:group>, where the 
> response element should initially be empty (before a submission is 
> executed) does not seem to work.
>
> See the test form copied below. Example form at: 
> https://www.tat2.io/basex2/static/xsltforms_test_2020-02-09.xml
>
> (2)
> I see that the xforms:var element is not currently supported. When 
> loading a form with an XForms variable defined, I get an error message:
>
> Error initializing:
>
> xforms:var is not supported
>
> (3)
> I also see that the XSLTForms Profiler does not seem to be available. 
> When I try to open it, I get an error:
>
> File not found (404): 
> https://www.tat2.io/basex2/static/xsltforms_profiler.xhtml
>
> *
> *
> *--Test form for XPath predicate bug--*
> *
> *
> <?xml-stylesheet type="text/xsl" href="..."?>
> <html xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
> xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
> xmlns:xf="http://www.w3.org/2002/xforms" 
> xmlns:h="http://www.w3.org/1999/xhtml" 
> xmlns:ev="http://www.w3.org/2001/xml-events" 
> xmlns="http://www.w3.org/1999/xhtml">
>   <head>
>     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
>     <title>XForms/XPath Predicate Test</title>
>     <style type="text/css"/>
>     <model xmlns="http://www.w3.org/2002/xforms" id="m">
>       <instance id="default">
>         <data xmlns="">
>           <default/>
>         </data>
>       </instance>
>       <instance id="response">
>         <data xmlns="">
>           <response/>
>         </data>
>       </instance>
>       <instance id="response-test">
>         <data xmlns="">
>           <response>
>             <testing>Testing</testing>
>           </response>
>         </data>
>       </instance>
>     </model>
>   </head>
>   <body>
>     <div class="container-fluid">
>       <hr class="blue" />
>       <h1>XForms/XPath predicate test</h1>
>       <xf:group ref="instance('response')/response[*]">
>         <h2 style="color: red;">This should not display!</h2>
>         <xf:output value="concat('Value of &quot;serialize(.)&quot;: 
> ', serialize(.))"/>
>       </xf:group>
>       <xf:group ref="instance('response-test')/response[*]">
>         <h2 style="color: blue;">This should display.</h2>
>         <xf:output value="concat('Value of &quot;serialize(.)&quot;: 
> ', serialize(.))"/>
>       </xf:group>
>     </div>
>   </body>
> </html>
>
>
>
> --
> Tim A. Thompson
> Discovery Metadata Librarian
> Yale University Library
>
> On Sun, Feb 9, 2020 at 11:06 AM Tim Thompson <tim...@gm... 
> <mailto:tim...@gm...>> wrote:
>
>     Hello, Alain,
>
>     Congratulations on this milestone! I am very eager to try and test
>     the new release. Is XSLTForms now using Fleur for XPath parsing?
>     Does this mean that XPath 3.0 functions are now supported? I guess
>     I can test this myself :)
>
>     It's quite amazing to see the xsltforms.xsl file down to just over
>     500 lines.
>
>     Thanks again for all your work.
>
>     Best regards,
>     Tim
>
>
>     --
>     Tim A. Thompson
>     Discovery Metadata Librarian
>     Yale University Library
>
>     On Wed, Feb 5, 2020 at 3:16 PM Alain Couthures
>     <ala...@ag...
>     <mailto:ala...@ag...>> wrote:
>
>         Hello,
>
>         Please find a new release for XSLTForms at
>         www.agencexml.com/1.5beta/xsltforms.zip
>         <http://www.agencexml.com/1.5beta/xsltforms.zip>
>
>         It has not yet been fully tested because a lot of changes have
>         been made and you are welcome to locate remaining issues with
>         your own forms.
>
>         The XSLT part has been reduced to minimal for better
>         performance. Instead of parsing the XPath expressions and
>         transforming all the XForms elements into HTML elements, it
>         basically just transposes the non-HTML elements into sort-of
>         custom elements: xforms:* elements become xforms-* elements
>         with xf-* and ev-* attributes.
>
>         Have a look with your favorite browser debugger! Actually,
>         authors could even prefer to directly write/generate forms
>         with this new notation and forget about the XSLT step. You can
>         compare two sources for the same form: hello.xml and hello.htm
>
>         XSLTForms Javascript classes constructors are obtaining their
>         properties directly from xf-* attributes and XPath parsing is
>         then performed.
>
>         No ids are automatically added as previously.
>
>         Extra xf-* attributes and extra xforms-* elements are used to
>         embed effective HTML rendering elements, for example,
>         xforms-body or xforms-repeat-item while, before, span or div
>         elements where used.
>
>         XSLTForms classes for xforms:select and xforms:itemset had to
>         be partially rewritten.
>
>         SVG support has been basically tested too.
>
>         CSS styling is not anymore based on xforms-* classes but on
>         custom element names and attribute selectors. For example, the
>         extra xf-bound attribute, when present, says that the XForms
>         control is bound to a node, eventually a not relevant one, and
>         the extra xf-notrelevant attribute can, then, be checked...
>
>         Thank you for your contribution!
>
>         --Alain
>         _______________________________________________
>         Xsltforms-support mailing list
>         Xsl...@li...
>         <mailto:Xsl...@li...>
>         https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

Re: [Xsltforms-support] New release: Please give it a try!

[Tim T. <tim...@gm...>]

Great! Works perfectly now. Looking forward to the XML Prague proceedings
and video for your presentation with Steven Pemberton.

Thanks again,
Tim


--
Tim A. Thompson
Discovery Metadata Librarian
Yale University Library



On Wed, Feb 12, 2020 at 4:00 PM Alain Couthures <
ala...@ag...> wrote:

> Hello Tim,
>
> (1) The xf:group processing was not correct: in the new approach, an
> xf-bound attribute has to be automatically added to each xforms-* element
> when xf-ref (or xf-bind) is evaluated as a non empty nodeset. CSS attribute
> selectors are, then, used to display/hide xforms-* elements accordingly.
>
> (2) The xf:var processing was not functional: it should now work, at
> least, outside of actions.
>
> (3) The profiler is actually just another external form: I have added the
> corresponding file into the updated .zip file at
> www.agencexml.com/1.5beta/xsltforms.zip
>
> Thank you very much for your contributions!
>
> --Alain
>
> Le 09/02/2020 à 20:51, Tim Thompson a écrit :
>
> Hello, Alain,
>
> I've been testing an existing form with the new release and have some
> feedback. First, the performance improvement seems impressive, and CSS
> styling with Bootstrap now seems much easier. Thank you!
>
> I did notice some issues after testing, however.
>
> (1)
> There seems to be a bug with XPath predicate filtering in xf:group
> elements. For example, a group binding such as <xf:group
> ref="instance('response')/response[*]">...</xf:group>, where the response
> element should initially be empty (before a submission is executed) does
> not seem to work.
>
> See the test form copied below. Example form at:
> https://www.tat2.io/basex2/static/xsltforms_test_2020-02-09.xml
>
> (2)
> I see that the xforms:var element is not currently supported. When loading
> a form with an XForms variable defined, I get an error message:
>
> Error initializing:
>
> xforms:var is not supported
>
> (3)
> I also see that the XSLTForms Profiler does not seem to be available. When
> I try to open it, I get an error:
>
> File not found (404):
> https://www.tat2.io/basex2/static/xsltforms_profiler.xhtml
>
>
> *--Test form for XPath predicate bug--*
>
> <?xml-stylesheet type="text/xsl" href="..."?>
> <html xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="
> http://www.w3.org/2001/XMLSchema" xmlns:xf="http://www.w3.org/2002/xforms"
> xmlns:h="http://www.w3.org/1999/xhtml" xmlns:ev="
> http://www.w3.org/2001/xml-events" xmlns="http://www.w3.org/1999/xhtml">
>   <head>
>     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
>     <title>XForms/XPath Predicate Test</title>
>     <style type="text/css"/>
>     <model xmlns="http://www.w3.org/2002/xforms" id="m">
>       <instance id="default">
>         <data xmlns="">
>           <default/>
>         </data>
>       </instance>
>       <instance id="response">
>         <data xmlns="">
>           <response/>
>         </data>
>       </instance>
>       <instance id="response-test">
>         <data xmlns="">
>           <response>
>             <testing>Testing</testing>
>           </response>
>         </data>
>       </instance>
>     </model>
>   </head>
>   <body>
>     <div class="container-fluid">
>       <hr class="blue" />
>       <h1>XForms/XPath predicate test</h1>
>       <xf:group ref="instance('response')/response[*]">
>         <h2 style="color: red;">This should not display!</h2>
>         <xf:output value="concat('Value of &quot;serialize(.)&quot;: ',
> serialize(.))"/>
>       </xf:group>
>       <xf:group ref="instance('response-test')/response[*]">
>         <h2 style="color: blue;">This should display.</h2>
>         <xf:output value="concat('Value of &quot;serialize(.)&quot;: ',
> serialize(.))"/>
>       </xf:group>
>     </div>
>   </body>
> </html>
>
>
>
> --
> Tim A. Thompson
> Discovery Metadata Librarian
> Yale University Library
>
> On Sun, Feb 9, 2020 at 11:06 AM Tim Thompson <tim...@gm...> wrote:
>
>> Hello, Alain,
>>
>> Congratulations on this milestone! I am very eager to try and test the
>> new release. Is XSLTForms now using Fleur for XPath parsing? Does this mean
>> that XPath 3.0 functions are now supported? I guess I can test this myself
>> :)
>>
>> It's quite amazing to see the xsltforms.xsl file down to just over 500
>> lines.
>>
>> Thanks again for all your work.
>>
>> Best regards,
>> Tim
>>
>>
>> --
>> Tim A. Thompson
>> Discovery Metadata Librarian
>> Yale University Library
>>
>> On Wed, Feb 5, 2020 at 3:16 PM Alain Couthures <
>> ala...@ag...> wrote:
>>
>>> Hello,
>>>
>>> Please find a new release for XSLTForms at
>>> www.agencexml.com/1.5beta/xsltforms.zip
>>>
>>> It has not yet been fully tested because a lot of changes have been made
>>> and you are welcome to locate remaining issues with your own forms.
>>>
>>> The XSLT part has been reduced to minimal for better performance.
>>> Instead of parsing the XPath expressions and transforming all the XForms
>>> elements into HTML elements, it basically just transposes the non-HTML
>>> elements into sort-of custom elements: xforms:* elements become xforms-*
>>> elements with xf-* and ev-* attributes.
>>>
>>> Have a look with your favorite browser debugger! Actually, authors could
>>> even prefer to directly write/generate forms with this new notation and
>>> forget about the XSLT step. You can compare two sources for the same form:
>>> hello.xml and hello.htm
>>>
>>> XSLTForms Javascript classes constructors are obtaining their properties
>>> directly from xf-* attributes and XPath parsing is then performed.
>>>
>>> No ids are automatically added as previously.
>>>
>>> Extra xf-* attributes and extra xforms-* elements are used to embed
>>> effective HTML rendering elements, for example, xforms-body or
>>> xforms-repeat-item while, before, span or div elements where used.
>>>
>>> XSLTForms classes for xforms:select and xforms:itemset had to be
>>> partially rewritten.
>>>
>>> SVG support has been basically tested too.
>>>
>>> CSS styling is not anymore based on xforms-* classes but on custom
>>> element names and attribute selectors. For example, the extra xf-bound
>>> attribute, when present, says that the XForms control is bound to a node,
>>> eventually a not relevant one, and the extra xf-notrelevant attribute can,
>>> then, be checked...
>>>
>>> Thank you for your contribution!
>>>
>>> --Alain
>>> _______________________________________________
>>> Xsltforms-support mailing list
>>> Xsl...@li...
>>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>>
>>
>

[Xsltforms-support] 1.5beta testing

[Tim T. <tim...@gm...>]

Hello, Alain,

Another test for you:

In XSLTForms 1.5beta, the DOMActivate event is not being evoked for input
controls. See this test form:

https://www.tat2.io/basex2/static/xsltforms_DOMActivate_test_2020-02-14_1-5beta.xml

Pressing "enter" in the input field does nothing, whereas clicking the
button triggers the event.

Compare this to a form running XSLTForms 1.4:

https://www.tat2.io/basex2/static/xsltforms_DOMActivate_test_2020-02-14_1-4.xml

Here, the DOMActivate enter works in both the input field with the "enter"
key and with the button.

All best,
Tim

--
Tim A. Thompson
Discovery Metadata Librarian
Yale University Library

On Wed, Feb 12, 2020 at 5:51 PM Tim Thompson <tim...@gm...> wrote:

> Great! Works perfectly now. Looking forward to the XML Prague proceedings
> and video for your presentation with Steven Pemberton.
>
> Thanks again,
> Tim
>
>
> --
> Tim A. Thompson
> Discovery Metadata Librarian
> Yale University Library
>
>
>
> On Wed, Feb 12, 2020 at 4:00 PM Alain Couthures <
> ala...@ag...> wrote:
>
>> Hello Tim,
>>
>> (1) The xf:group processing was not correct: in the new approach, an
>> xf-bound attribute has to be automatically added to each xforms-* element
>> when xf-ref (or xf-bind) is evaluated as a non empty nodeset. CSS attribute
>> selectors are, then, used to display/hide xforms-* elements accordingly.
>>
>> (2) The xf:var processing was not functional: it should now work, at
>> least, outside of actions.
>>
>> (3) The profiler is actually just another external form: I have added the
>> corresponding file into the updated .zip file at
>> www.agencexml.com/1.5beta/xsltforms.zip
>>
>> Thank you very much for your contributions!
>>
>> --Alain
>>
>> Le 09/02/2020 à 20:51, Tim Thompson a écrit :
>>
>> Hello, Alain,
>>
>> I've been testing an existing form with the new release and have some
>> feedback. First, the performance improvement seems impressive, and CSS
>> styling with Bootstrap now seems much easier. Thank you!
>>
>> I did notice some issues after testing, however.
>>
>> (1)
>> There seems to be a bug with XPath predicate filtering in xf:group
>> elements. For example, a group binding such as <xf:group
>> ref="instance('response')/response[*]">...</xf:group>, where the response
>> element should initially be empty (before a submission is executed) does
>> not seem to work.
>>
>> See the test form copied below. Example form at:
>> https://www.tat2.io/basex2/static/xsltforms_test_2020-02-09.xml
>>
>> (2)
>> I see that the xforms:var element is not currently supported. When
>> loading a form with an XForms variable defined, I get an error message:
>>
>> Error initializing:
>>
>> xforms:var is not supported
>>
>> (3)
>> I also see that the XSLTForms Profiler does not seem to be available.
>> When I try to open it, I get an error:
>>
>> File not found (404):
>> https://www.tat2.io/basex2/static/xsltforms_profiler.xhtml
>>
>>
>> *--Test form for XPath predicate bug--*
>>
>> <?xml-stylesheet type="text/xsl" href="..."?>
>> <html xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="
>> http://www.w3.org/2001/XMLSchema" xmlns:xf="http://www.w3.org/2002/xforms"
>> xmlns:h="http://www.w3.org/1999/xhtml" xmlns:ev="
>> http://www.w3.org/2001/xml-events" xmlns="http://www.w3.org/1999/xhtml">
>>   <head>
>>     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
>>     <title>XForms/XPath Predicate Test</title>
>>     <style type="text/css"/>
>>     <model xmlns="http://www.w3.org/2002/xforms" id="m">
>>       <instance id="default">
>>         <data xmlns="">
>>           <default/>
>>         </data>
>>       </instance>
>>       <instance id="response">
>>         <data xmlns="">
>>           <response/>
>>         </data>
>>       </instance>
>>       <instance id="response-test">
>>         <data xmlns="">
>>           <response>
>>             <testing>Testing</testing>
>>           </response>
>>         </data>
>>       </instance>
>>     </model>
>>   </head>
>>   <body>
>>     <div class="container-fluid">
>>       <hr class="blue" />
>>       <h1>XForms/XPath predicate test</h1>
>>       <xf:group ref="instance('response')/response[*]">
>>         <h2 style="color: red;">This should not display!</h2>
>>         <xf:output value="concat('Value of &quot;serialize(.)&quot;: ',
>> serialize(.))"/>
>>       </xf:group>
>>       <xf:group ref="instance('response-test')/response[*]">
>>         <h2 style="color: blue;">This should display.</h2>
>>         <xf:output value="concat('Value of &quot;serialize(.)&quot;: ',
>> serialize(.))"/>
>>       </xf:group>
>>     </div>
>>   </body>
>> </html>
>>
>>
>>
>> --
>> Tim A. Thompson
>> Discovery Metadata Librarian
>> Yale University Library
>>
>> On Sun, Feb 9, 2020 at 11:06 AM Tim Thompson <tim...@gm...> wrote:
>>
>>> Hello, Alain,
>>>
>>> Congratulations on this milestone! I am very eager to try and test the
>>> new release. Is XSLTForms now using Fleur for XPath parsing? Does this mean
>>> that XPath 3.0 functions are now supported? I guess I can test this myself
>>> :)
>>>
>>> It's quite amazing to see the xsltforms.xsl file down to just over 500
>>> lines.
>>>
>>> Thanks again for all your work.
>>>
>>> Best regards,
>>> Tim
>>>
>>>
>>> --
>>> Tim A. Thompson
>>> Discovery Metadata Librarian
>>> Yale University Library
>>>
>>> On Wed, Feb 5, 2020 at 3:16 PM Alain Couthures <
>>> ala...@ag...> wrote:
>>>
>>>> Hello,
>>>>
>>>> Please find a new release for XSLTForms at
>>>> www.agencexml.com/1.5beta/xsltforms.zip
>>>>
>>>> It has not yet been fully tested because a lot of changes have been
>>>> made and you are welcome to locate remaining issues with your own forms.
>>>>
>>>> The XSLT part has been reduced to minimal for better performance.
>>>> Instead of parsing the XPath expressions and transforming all the XForms
>>>> elements into HTML elements, it basically just transposes the non-HTML
>>>> elements into sort-of custom elements: xforms:* elements become xforms-*
>>>> elements with xf-* and ev-* attributes.
>>>>
>>>> Have a look with your favorite browser debugger! Actually, authors
>>>> could even prefer to directly write/generate forms with this new notation
>>>> and forget about the XSLT step. You can compare two sources for the same
>>>> form: hello.xml and hello.htm
>>>>
>>>> XSLTForms Javascript classes constructors are obtaining their
>>>> properties directly from xf-* attributes and XPath parsing is then
>>>> performed.
>>>>
>>>> No ids are automatically added as previously.
>>>>
>>>> Extra xf-* attributes and extra xforms-* elements are used to embed
>>>> effective HTML rendering elements, for example, xforms-body or
>>>> xforms-repeat-item while, before, span or div elements where used.
>>>>
>>>> XSLTForms classes for xforms:select and xforms:itemset had to be
>>>> partially rewritten.
>>>>
>>>> SVG support has been basically tested too.
>>>>
>>>> CSS styling is not anymore based on xforms-* classes but on custom
>>>> element names and attribute selectors. For example, the extra xf-bound
>>>> attribute, when present, says that the XForms control is bound to a node,
>>>> eventually a not relevant one, and the extra xf-notrelevant attribute can,
>>>> then, be checked...
>>>>
>>>> Thank you for your contribution!
>>>>
>>>> --Alain
>>>> _______________________________________________
>>>> Xsltforms-support mailing list
>>>> Xsl...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>>>
>>>
>>

Re: [Xsltforms-support] 1.5beta testing

[Alain C. <ala...@ag...>]

Hello Tim,

This issue is now fixed (and some more actually...).

The new build can be downloaded at the same URL: 
www.agencexml.com/1.5beta/xsltforms.zip 
<http://www.agencexml.com/1.5beta/xsltforms.zip>

Thank you again for your contributions!

--Alain

Le 15/02/2020 à 01:15, Tim Thompson a écrit :
> Hello, Alain,
>
> Another test for you:
>
> In XSLTForms 1.5beta, the DOMActivate event is not being evoked for 
> input controls. See this test form:
>
> https://www.tat2.io/basex2/static/xsltforms_DOMActivate_test_2020-02-14_1-5beta.xml
>
> Pressing "enter" in the input field does nothing, whereas clicking the 
> button triggers the event.
>
> Compare this to a form running XSLTForms 1.4:
>
> https://www.tat2.io/basex2/static/xsltforms_DOMActivate_test_2020-02-14_1-4.xml
>
> Here, the DOMActivate enter works in both the input field with the 
> "enter" key and with the button.
>
> All best,
> Tim
>
> --
> Tim A. Thompson
> Discovery Metadata Librarian
> Yale University Library
>
> On Wed, Feb 12, 2020 at 5:51 PM Tim Thompson <tim...@gm... 
> <mailto:tim...@gm...>> wrote:
>
>     Great! Works perfectly now. Looking forward to the XML Prague
>     proceedings and video for your presentation with Steven Pemberton.
>
>     Thanks again,
>     Tim
>
>
>     --
>     Tim A. Thompson
>     Discovery Metadata Librarian
>     Yale University Library
>
>
>
>     On Wed, Feb 12, 2020 at 4:00 PM Alain Couthures
>     <ala...@ag...
>     <mailto:ala...@ag...>> wrote:
>
>         Hello Tim,
>
>         (1) The xf:group processing was not correct: in the new
>         approach, an xf-bound attribute has to be automatically added
>         to each xforms-* element when xf-ref (or xf-bind) is evaluated
>         as a non empty nodeset. CSS attribute selectors are, then,
>         used to display/hide xforms-* elements accordingly.
>
>         (2) The xf:var processing was not functional: it should now
>         work, at least, outside of actions.
>
>         (3) The profiler is actually just another external form: I
>         have added the corresponding file into the updated .zip file
>         at www.agencexml.com/1.5beta/xsltforms.zip
>         <http://www.agencexml.com/1.5beta/xsltforms.zip>
>
>         Thank you very much for your contributions!
>
>         --Alain
>
>         Le 09/02/2020 à 20:51, Tim Thompson a écrit :
>>         Hello, Alain,
>>
>>         I've been testing an existing form with the new release and
>>         have some feedback. First, the performance improvement seems
>>         impressive, and CSS styling with Bootstrap now seems much
>>         easier. Thank you!
>>
>>         I did notice some issues after testing, however.
>>
>>         (1)
>>         There seems to be a bug with XPath predicate filtering in
>>         xf:group elements. For example, a group binding such as
>>         <xf:group
>>         ref="instance('response')/response[*]">...</xf:group>, where
>>         the response element should initially be empty (before a
>>         submission is executed) does not seem to work.
>>
>>         See the test form copied below. Example form at:
>>         https://www.tat2.io/basex2/static/xsltforms_test_2020-02-09.xml
>>
>>         (2)
>>         I see that the xforms:var element is not currently supported.
>>         When loading a form with an XForms variable defined, I get an
>>         error message:
>>
>>         Error initializing:
>>
>>         xforms:var is not supported
>>
>>         (3)
>>         I also see that the XSLTForms Profiler does not seem to be
>>         available. When I try to open it, I get an error:
>>
>>         File not found (404):
>>         https://www.tat2.io/basex2/static/xsltforms_profiler.xhtml
>>
>>         *
>>         *
>>         *--Test form for XPath predicate bug--*
>>         *
>>         *
>>         <?xml-stylesheet type="text/xsl" href="..."?>
>>         <html xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>         xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>>         xmlns:xf="http://www.w3.org/2002/xforms"
>>         xmlns:h="http://www.w3.org/1999/xhtml"
>>         xmlns:ev="http://www.w3.org/2001/xml-events"
>>         xmlns="http://www.w3.org/1999/xhtml">
>>           <head>
>>             <meta http-equiv="Content-Type" content="text/html;
>>         charset=UTF-8" />
>>             <title>XForms/XPath Predicate Test</title>
>>             <style type="text/css"/>
>>             <model xmlns="http://www.w3.org/2002/xforms" id="m">
>>               <instance id="default">
>>                 <data xmlns="">
>>                   <default/>
>>                 </data>
>>               </instance>
>>               <instance id="response">
>>                 <data xmlns="">
>>                   <response/>
>>                 </data>
>>               </instance>
>>               <instance id="response-test">
>>                 <data xmlns="">
>>                   <response>
>>         <testing>Testing</testing>
>>                   </response>
>>                 </data>
>>               </instance>
>>             </model>
>>           </head>
>>           <body>
>>             <div class="container-fluid">
>>               <hr class="blue" />
>>               <h1>XForms/XPath predicate test</h1>
>>               <xf:group ref="instance('response')/response[*]">
>>                 <h2 style="color: red;">This should not display!</h2>
>>                 <xf:output value="concat('Value of
>>         &quot;serialize(.)&quot;: ', serialize(.))"/>
>>               </xf:group>
>>               <xf:group ref="instance('response-test')/response[*]">
>>                 <h2 style="color: blue;">This should display.</h2>
>>                 <xf:output value="concat('Value of
>>         &quot;serialize(.)&quot;: ', serialize(.))"/>
>>               </xf:group>
>>             </div>
>>           </body>
>>         </html>
>>
>>
>>
>>         --
>>         Tim A. Thompson
>>         Discovery Metadata Librarian
>>         Yale University Library
>>
>>         On Sun, Feb 9, 2020 at 11:06 AM Tim Thompson
>>         <tim...@gm... <mailto:tim...@gm...>> wrote:
>>
>>             Hello, Alain,
>>
>>             Congratulations on this milestone! I am very eager to try
>>             and test the new release. Is XSLTForms now using Fleur
>>             for XPath parsing? Does this mean that XPath 3.0
>>             functions are now supported? I guess I can test this
>>             myself :)
>>
>>             It's quite amazing to see the xsltforms.xsl file down to
>>             just over 500 lines.
>>
>>             Thanks again for all your work.
>>
>>             Best regards,
>>             Tim
>>
>>
>>             --
>>             Tim A. Thompson
>>             Discovery Metadata Librarian
>>             Yale University Library
>>
>>             On Wed, Feb 5, 2020 at 3:16 PM Alain Couthures
>>             <ala...@ag...
>>             <mailto:ala...@ag...>> wrote:
>>
>>                 Hello,
>>
>>                 Please find a new release for XSLTForms at
>>                 www.agencexml.com/1.5beta/xsltforms.zip
>>                 <http://www.agencexml.com/1.5beta/xsltforms.zip>
>>
>>                 It has not yet been fully tested because a lot of
>>                 changes have been made and you are welcome to locate
>>                 remaining issues with your own forms.
>>
>>                 The XSLT part has been reduced to minimal for better
>>                 performance. Instead of parsing the XPath expressions
>>                 and transforming all the XForms elements into HTML
>>                 elements, it basically just transposes the non-HTML
>>                 elements into sort-of custom elements: xforms:*
>>                 elements become xforms-* elements with xf-* and ev-*
>>                 attributes.
>>
>>                 Have a look with your favorite browser debugger!
>>                 Actually, authors could even prefer to directly
>>                 write/generate forms with this new notation and
>>                 forget about the XSLT step. You can compare two
>>                 sources for the same form: hello.xml and hello.htm
>>
>>                 XSLTForms Javascript classes constructors are
>>                 obtaining their properties directly from xf-*
>>                 attributes and XPath parsing is then performed.
>>
>>                 No ids are automatically added as previously.
>>
>>                 Extra xf-* attributes and extra xforms-* elements are
>>                 used to embed effective HTML rendering elements, for
>>                 example, xforms-body or xforms-repeat-item while,
>>                 before, span or div elements where used.
>>
>>                 XSLTForms classes for xforms:select and
>>                 xforms:itemset had to be partially rewritten.
>>
>>                 SVG support has been basically tested too.
>>
>>                 CSS styling is not anymore based on xforms-* classes
>>                 but on custom element names and attribute selectors.
>>                 For example, the extra xf-bound attribute, when
>>                 present, says that the XForms control is bound to a
>>                 node, eventually a not relevant one, and the extra
>>                 xf-notrelevant attribute can, then, be checked...
>>
>>                 Thank you for your contribution!
>>
>>                 --Alain
>>                 _______________________________________________
>>                 Xsltforms-support mailing list
>>                 Xsl...@li...
>>                 <mailto:Xsl...@li...>
>>                 https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>
>

Re: [Xsltforms-support] 1.5beta testing

[Tim T. <tim...@gm...>]

Thank you, Alain!

If you don't mind, I have another test form that works in XSLTForms 1.4 but
not 1.5beta.

This one is testing xf:var again.

In 1.5beta, an error is thrown:
Assertion failed: Binding evaluation didn't returned a nodeset but '1' for
XPath expression: count(ancestor::item)
https://www.tat2.io/basex2/static/xsltforms_var_test_2020-02-17_with_var_1.5beta.xml

In 1.4, the form works as expected:
https://www.tat2.io/basex2/static/xsltforms_var_test_2020-02-17_with_var_1.4.xml

Best regards,
Tim


--
Tim A. Thompson
Discovery Metadata Librarian
Yale University Library


On Mon, Feb 17, 2020 at 3:54 PM Alain Couthures <
ala...@ag...> wrote:

> Hello Tim,
>
> This issue is now fixed (and some more actually...).
>
> The new build can be downloaded at the same URL:
> www.agencexml.com/1.5beta/xsltforms.zip
>
> Thank you again for your contributions!
>
> --Alain
>
> Le 15/02/2020 à 01:15, Tim Thompson a écrit :
>
> Hello, Alain,
>
> Another test for you:
>
> In XSLTForms 1.5beta, the DOMActivate event is not being evoked for input
> controls. See this test form:
>
>
> https://www.tat2.io/basex2/static/xsltforms_DOMActivate_test_2020-02-14_1-5beta.xml
>
> Pressing "enter" in the input field does nothing, whereas clicking the
> button triggers the event.
>
> Compare this to a form running XSLTForms 1.4:
>
>
> https://www.tat2.io/basex2/static/xsltforms_DOMActivate_test_2020-02-14_1-4.xml
>
> Here, the DOMActivate enter works in both the input field with the "enter"
> key and with the button.
>
> All best,
> Tim
>
> --
> Tim A. Thompson
> Discovery Metadata Librarian
> Yale University Library
>
> On Wed, Feb 12, 2020 at 5:51 PM Tim Thompson <tim...@gm...> wrote:
>
>> Great! Works perfectly now. Looking forward to the XML Prague proceedings
>> and video for your presentation with Steven Pemberton.
>>
>> Thanks again,
>> Tim
>>
>>
>> --
>> Tim A. Thompson
>> Discovery Metadata Librarian
>> Yale University Library
>>
>>
>>
>> On Wed, Feb 12, 2020 at 4:00 PM Alain Couthures <
>> ala...@ag...> wrote:
>>
>>> Hello Tim,
>>>
>>> (1) The xf:group processing was not correct: in the new approach, an
>>> xf-bound attribute has to be automatically added to each xforms-* element
>>> when xf-ref (or xf-bind) is evaluated as a non empty nodeset. CSS attribute
>>> selectors are, then, used to display/hide xforms-* elements accordingly.
>>>
>>> (2) The xf:var processing was not functional: it should now work, at
>>> least, outside of actions.
>>>
>>> (3) The profiler is actually just another external form: I have added
>>> the corresponding file into the updated .zip file at
>>> www.agencexml.com/1.5beta/xsltforms.zip
>>>
>>> Thank you very much for your contributions!
>>>
>>> --Alain
>>>
>>> Le 09/02/2020 à 20:51, Tim Thompson a écrit :
>>>
>>> Hello, Alain,
>>>
>>> I've been testing an existing form with the new release and have some
>>> feedback. First, the performance improvement seems impressive, and CSS
>>> styling with Bootstrap now seems much easier. Thank you!
>>>
>>> I did notice some issues after testing, however.
>>>
>>> (1)
>>> There seems to be a bug with XPath predicate filtering in xf:group
>>> elements. For example, a group binding such as <xf:group
>>> ref="instance('response')/response[*]">...</xf:group>, where the response
>>> element should initially be empty (before a submission is executed) does
>>> not seem to work.
>>>
>>> See the test form copied below. Example form at:
>>> https://www.tat2.io/basex2/static/xsltforms_test_2020-02-09.xml
>>>
>>> (2)
>>> I see that the xforms:var element is not currently supported. When
>>> loading a form with an XForms variable defined, I get an error message:
>>>
>>> Error initializing:
>>>
>>> xforms:var is not supported
>>>
>>> (3)
>>> I also see that the XSLTForms Profiler does not seem to be available.
>>> When I try to open it, I get an error:
>>>
>>> File not found (404):
>>> https://www.tat2.io/basex2/static/xsltforms_profiler.xhtml
>>>
>>>
>>> *--Test form for XPath predicate bug--*
>>>
>>> <?xml-stylesheet type="text/xsl" href="..."?>
>>> <html xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="
>>> http://www.w3.org/2001/XMLSchema" xmlns:xf="
>>> http://www.w3.org/2002/xforms" xmlns:h="http://www.w3.org/1999/xhtml"
>>> xmlns:ev="http://www.w3.org/2001/xml-events" xmlns="
>>> http://www.w3.org/1999/xhtml">
>>>   <head>
>>>     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
>>>     <title>XForms/XPath Predicate Test</title>
>>>     <style type="text/css"/>
>>>     <model xmlns="http://www.w3.org/2002/xforms" id="m">
>>>       <instance id="default">
>>>         <data xmlns="">
>>>           <default/>
>>>         </data>
>>>       </instance>
>>>       <instance id="response">
>>>         <data xmlns="">
>>>           <response/>
>>>         </data>
>>>       </instance>
>>>       <instance id="response-test">
>>>         <data xmlns="">
>>>           <response>
>>>             <testing>Testing</testing>
>>>           </response>
>>>         </data>
>>>       </instance>
>>>     </model>
>>>   </head>
>>>   <body>
>>>     <div class="container-fluid">
>>>       <hr class="blue" />
>>>       <h1>XForms/XPath predicate test</h1>
>>>       <xf:group ref="instance('response')/response[*]">
>>>         <h2 style="color: red;">This should not display!</h2>
>>>         <xf:output value="concat('Value of &quot;serialize(.)&quot;: ',
>>> serialize(.))"/>
>>>       </xf:group>
>>>       <xf:group ref="instance('response-test')/response[*]">
>>>         <h2 style="color: blue;">This should display.</h2>
>>>         <xf:output value="concat('Value of &quot;serialize(.)&quot;: ',
>>> serialize(.))"/>
>>>       </xf:group>
>>>     </div>
>>>   </body>
>>> </html>
>>>
>>>
>>>
>>> --
>>> Tim A. Thompson
>>> Discovery Metadata Librarian
>>> Yale University Library
>>>
>>> On Sun, Feb 9, 2020 at 11:06 AM Tim Thompson <tim...@gm...> wrote:
>>>
>>>> Hello, Alain,
>>>>
>>>> Congratulations on this milestone! I am very eager to try and test the
>>>> new release. Is XSLTForms now using Fleur for XPath parsing? Does this mean
>>>> that XPath 3.0 functions are now supported? I guess I can test this myself
>>>> :)
>>>>
>>>> It's quite amazing to see the xsltforms.xsl file down to just over 500
>>>> lines.
>>>>
>>>> Thanks again for all your work.
>>>>
>>>> Best regards,
>>>> Tim
>>>>
>>>>
>>>> --
>>>> Tim A. Thompson
>>>> Discovery Metadata Librarian
>>>> Yale University Library
>>>>
>>>> On Wed, Feb 5, 2020 at 3:16 PM Alain Couthures <
>>>> ala...@ag...> wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> Please find a new release for XSLTForms at
>>>>> www.agencexml.com/1.5beta/xsltforms.zip
>>>>>
>>>>> It has not yet been fully tested because a lot of changes have been
>>>>> made and you are welcome to locate remaining issues with your own forms.
>>>>>
>>>>> The XSLT part has been reduced to minimal for better performance.
>>>>> Instead of parsing the XPath expressions and transforming all the XForms
>>>>> elements into HTML elements, it basically just transposes the non-HTML
>>>>> elements into sort-of custom elements: xforms:* elements become xforms-*
>>>>> elements with xf-* and ev-* attributes.
>>>>>
>>>>> Have a look with your favorite browser debugger! Actually, authors
>>>>> could even prefer to directly write/generate forms with this new notation
>>>>> and forget about the XSLT step. You can compare two sources for the same
>>>>> form: hello.xml and hello.htm
>>>>>
>>>>> XSLTForms Javascript classes constructors are obtaining their
>>>>> properties directly from xf-* attributes and XPath parsing is then
>>>>> performed.
>>>>>
>>>>> No ids are automatically added as previously.
>>>>>
>>>>> Extra xf-* attributes and extra xforms-* elements are used to embed
>>>>> effective HTML rendering elements, for example, xforms-body or
>>>>> xforms-repeat-item while, before, span or div elements where used.
>>>>>
>>>>> XSLTForms classes for xforms:select and xforms:itemset had to be
>>>>> partially rewritten.
>>>>>
>>>>> SVG support has been basically tested too.
>>>>>
>>>>> CSS styling is not anymore based on xforms-* classes but on custom
>>>>> element names and attribute selectors. For example, the extra xf-bound
>>>>> attribute, when present, says that the XForms control is bound to a node,
>>>>> eventually a not relevant one, and the extra xf-notrelevant attribute can,
>>>>> then, be checked...
>>>>>
>>>>> Thank you for your contribution!
>>>>>
>>>>> --Alain
>>>>> _______________________________________________
>>>>> Xsltforms-support mailing list
>>>>> Xsl...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>>>>
>>>>
>>>
>

Re: [Xsltforms-support] New release: Please give it a try!

[Steven P. <ste...@cw...>]

Exciting to be testing the new implementation.

I'll start simple.

[Enter] in an <input/> doesn't seem to dispatch a DOMActivate.
For instance,  
https://homepages.cwi.nl/~steven/forms/examples/lists/list3.xhtml

Steven



On Wed, 05 Feb 2020 21:15:57 +0100, Alain Couthures  
<ala...@ag...> wrote:

> Hello,
>
> Please find a new release for XSLTForms at  
> www.agencexml.com/1.5beta/xsltforms.zip
>
> It has not yet been fully tested because a lot of changes have been made  
> and you are welcome to locate remaining issues with your own forms.
>
> The XSLT part has been reduced to minimal for better performance.  
> Instead of parsing the XPath expressions and transforming all the XForms  
> >elements into HTML elements, it basically just transposes the non-HTML  
> elements into sort-of custom elements: xforms:* elements become xforms-*  
> >elements with xf-* and ev-* attributes.
>
> Have a look with your favorite browser debugger! Actually, authors could  
> even prefer to directly write/generate forms with this new notation and  
> forget >about the XSLT step. You can compare two sources for the same  
> form: hello.xml and hello.htm
>
> XSLTForms Javascript classes constructors are obtaining their properties  
> directly from xf-* attributes and XPath parsing is then performed.
>
> No ids are automatically added as previously.
>
> Extra xf-* attributes and extra xforms-* elements are used to embed  
> effective HTML rendering elements, for example, xforms-body or  
> xforms-repeat->item while, before, span or div elements where used.
>
> XSLTForms classes for xforms:select and xforms:itemset had to be  
> partially rewritten.
>
> SVG support has been basically tested too.
>
> CSS styling is not anymore based on xforms-* classes but on custom  
> element names and attribute selectors. For example, the extra xf-bound  
> >attribute, when present, says that the XForms control is bound to a  
> node, eventually a not relevant one, and the extra xf-notrelevant  
> attribute can, then, >be checked...
>
> Thank you for your contribution!
>
> --Alain

Re: [Xsltforms-support] New release: Please give it a try!

[Alain C. <ala...@ag...>]

<!doctype html>
<html>
 <head> 
  <meta charset="UTF-8"> 
 </head>
 <body>
  <div>
   This has been fixed recently and I cannot reproduce this bug with your own test page: please clear browser cache.
  </div>
  <div>
   <br>
  </div>
  <div>
   --Alain
  </div>
  <blockquote type="cite">
   Le 24 février 2020 à 14:19, Steven Pemberton &lt;ste...@cw...&gt; a écrit&nbsp;: 
   <br>
   <br>
   <div>
    Exciting to be testing the new implementation.
   </div>
   <div>
    <br>
   </div>
   <div>
    I'll start simple.
   </div>
   <div>
    <br>
   </div>
   <div>
    [Enter] in an &lt;input/&gt; doesn't seem to dispatch a DOMActivate.
   </div>
   <div>
    For instance, https://homepages.cwi.nl/~steven/forms/examples/lists/list3.xhtml
   </div>
   <div>
    <br>
   </div>
   <div>
    Steven
   </div>
   <div>
    <br>
   </div>
   <div>
    <br>
   </div>
   <div>
    <br>
   </div>
   <div>
    On Wed, 05 Feb 2020 21:15:57 +0100, Alain Couthures &lt;ala...@ag...&gt; wrote: 
    <br>
   </div>
   <br>
   <blockquote>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     Hello,
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     <br>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     Please find a new release for XSLTForms at 
     <a href="http://www.agencexml.com/1.5beta/xsltforms.zip" class="ox-c64a9ada08-moz-txt-link-abbreviated">www.agencexml.com/1.5beta/xsltforms.zip</a>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     <br>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     It has not yet been fully tested because a lot of changes have been made and you are welcome to locate remaining issues with your own forms.
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     <br>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     The XSLT part has been reduced to minimal for better performance. Instead of parsing the XPath expressions and transforming all the XForms elements into HTML elements, it basically just transposes the non-HTML elements into sort-of custom elements: xforms:* elements become xforms-* elements with xf-* and ev-* attributes.
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     <br>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     Have a look with your favorite browser debugger! Actually, authors could even prefer to directly write/generate forms with this new notation and forget about the XSLT step. You can compare two sources for the same form: hello.xml and hello.htm
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     <br>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     XSLTForms Javascript classes constructors are obtaining their properties directly from xf-* attributes and XPath parsing is then performed.
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     <br>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     No ids are automatically added as previously.
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     <br>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     Extra xf-* attributes and extra xforms-* elements are used to embed effective HTML rendering elements, for example, xforms-body or xforms-repeat-item while, before, span or div elements where used.
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     <br>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     XSLTForms classes for xforms:select and xforms:itemset had to be partially rewritten.
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     <br>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     SVG support has been basically tested too.
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     <br>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     CSS styling is not anymore based on xforms-* classes but on custom element names and attribute selectors. For example, the extra xf-bound attribute, when present, says that the XForms control is bound to a node, eventually a not relevant one, and the extra xf-notrelevant attribute can, then, be checked...
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     <br>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     Thank you for your contribution!
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     <br>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     --Alain
    </div>
   </blockquote>
   <br>
   <br>
   <br>
  </blockquote>
  <div class="default-style">
   <br>&nbsp;
  </div> 
 </body>
</html>

Re: [Xsltforms-support] New release: Please give it a try!

[Steven P. <ste...@cw...>]

OK thanks.

New one: operator mod not recognised?

Steven

On Mon, 24 Feb 2020 14:30:56 +0100, Alain Couthures  
<ala...@ag...> wrote:

> This has been fixed recently and I cannot reproduce this bug with your  
> own test page: please clear browser cache.
> --Alain
>> Le 24 février 2020 à 14:19, Steven Pemberton <ste...@cw...>  
>> a écrit :
>> Exciting to be testing the new implementation.
>> I'll start simple.
>> [Enter] in an <input/> doesn't seem to dispatch a DOMActivate.For  
>> instance,  
>> https://homepages.cwi.nl/~steven/forms/examples/lists/list3.xhtml
>> Steven
>>
>>
>> On Wed, 05 Feb 2020 21:15:57 +0100, Alain Couthures  
>> <ala...@ag...> wrote:
>>> Hello,
>>> Please find a new release for XSLTForms at  
>>> www.agencexml.com/1.5beta/xsltforms.zip
>>> It has not yet been fully tested because a lot of changes have been  
>>> made and you are >>>welcome to locate remaining issues with your own  
>>> forms.
>>> The XSLT part has been reduced to minimal for better performance.  
>>> Instead of parsing the >>>XPath expressions and transforming all the  
>>> XForms elements into HTML elements, it >>>basically just transposes  
>>> the non-HTML elements into sort-of custom elements: xforms:*  
>>> >>>elements become xforms-* elements with xf-* and ev-* attributes.
>>> Have a look with your favorite browser debugger! Actually, authors  
>>> could even prefer to >>>directly write/generate forms with this new  
>>> notation and forget about the XSLT step. You >>>can compare two  
>>> sources for the same form: hello.xml and hello.htm
>>> XSLTForms Javascript classes constructors are obtaining their  
>>> properties directly from >>>xf-* attributes and XPath parsing is then  
>>> performed.
>>> No ids are automatically added as previously.
>>> Extra xf-* attributes and extra xforms-* elements are used to embed  
>>> effective HTML >>>rendering elements, for example, xforms-body or  
>>> xforms-repeat-item while, before, span >>>or div elements where used.
>>> XSLTForms classes for xforms:select and xforms:itemset had to be  
>>> partially rewritten.
>>> SVG support has been basically tested too.
>>> CSS styling is not anymore based on xforms-* classes but on custom  
>>> element names and >>>attribute selectors. For example, the extra  
>>> xf-bound attribute, when present, says that >>>the XForms control is  
>>> bound to a node, eventually a not relevant one, and the extra  
>>> xf->>>notrelevant attribute can, then, be checked...
>>> Thank you for your contribution!
>>> --Alain
>>
>>
>>
>

Re: [Xsltforms-support] New release: Please give it a try!

[Tim T. <tim...@gm...>]

Steven,

You'll want to download the .zip file again. This bug seems to have been
resolved (see https://sourceforge.net/p/xsltforms/mailman/message/36926131/
).

Cheers,
Tim

--
Tim A. Thompson
Discovery Metadata Librarian
Yale University Library



On Mon, Feb 24, 2020 at 8:31 AM Steven Pemberton <ste...@cw...>
wrote:

> Exciting to be testing the new implementation.
>
> I'll start simple.
>
> [Enter] in an <input/> doesn't seem to dispatch a DOMActivate.
> For instance,
> https://homepages.cwi.nl/~steven/forms/examples/lists/list3.xhtml
>
> Steven
>
>
>
> On Wed, 05 Feb 2020 21:15:57 +0100, Alain Couthures <
> ala...@ag...> wrote:
>
> Hello,
>
> Please find a new release for XSLTForms at
> www.agencexml.com/1.5beta/xsltforms.zip
>
> It has not yet been fully tested because a lot of changes have been made
> and you are welcome to locate remaining issues with your own forms.
>
> The XSLT part has been reduced to minimal for better performance. Instead
> of parsing the XPath expressions and transforming all the XForms elements
> into HTML elements, it basically just transposes the non-HTML elements into
> sort-of custom elements: xforms:* elements become xforms-* elements with
> xf-* and ev-* attributes.
>
> Have a look with your favorite browser debugger! Actually, authors could
> even prefer to directly write/generate forms with this new notation and
> forget about the XSLT step. You can compare two sources for the same form:
> hello.xml and hello.htm
>
> XSLTForms Javascript classes constructors are obtaining their properties
> directly from xf-* attributes and XPath parsing is then performed.
>
> No ids are automatically added as previously.
>
> Extra xf-* attributes and extra xforms-* elements are used to embed
> effective HTML rendering elements, for example, xforms-body or
> xforms-repeat-item while, before, span or div elements where used.
>
> XSLTForms classes for xforms:select and xforms:itemset had to be partially
> rewritten.
>
> SVG support has been basically tested too.
>
> CSS styling is not anymore based on xforms-* classes but on custom element
> names and attribute selectors. For example, the extra xf-bound attribute,
> when present, says that the XForms control is bound to a node, eventually a
> not relevant one, and the extra xf-notrelevant attribute can, then, be
> checked...
>
> Thank you for your contribution!
>
> --Alain
>
>
>
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

Re: [Xsltforms-support] New release: Please give it a try!

[Alain C. <ala...@ag...>]

Steven and Tim,

A new build with more fixes can now be downloaded at 
www.agencexml.com/1.5beta/xsltforms.zip 
<http://www.agencexml.com/1.5beta/xsltforms.zip>

Thank you for your contributions!

--Alain

Le 24/02/2020 à 14:39, Tim Thompson a écrit :
> Steven,
>
> You'll want to download the .zip file again. This bug seems to have 
> been resolved (see 
> https://sourceforge.net/p/xsltforms/mailman/message/36926131/).
>
> Cheers,
> Tim
>
> --
> Tim A. Thompson
> Discovery Metadata Librarian
> Yale University Library
>
>
>
> On Mon, Feb 24, 2020 at 8:31 AM Steven Pemberton 
> <ste...@cw... <mailto:ste...@cw...>> wrote:
>
>     Exciting to be testing the new implementation.
>
>     I'll start simple.
>
>     [Enter] in an <input/> doesn't seem to dispatch a DOMActivate.
>     For instance,
>     https://homepages.cwi.nl/~steven/forms/examples/lists/list3.xhtml
>
>     Steven
>
>
>
>     On Wed, 05 Feb 2020 21:15:57 +0100, Alain Couthures
>     <ala...@ag...
>     <mailto:ala...@ag...>> wrote:
>
>         Hello,
>
>         Please find a new release for XSLTForms at
>         www.agencexml.com/1.5beta/xsltforms.zip
>         <http://www.agencexml.com/1.5beta/xsltforms.zip>
>
>         It has not yet been fully tested because a lot of changes have
>         been made and you are welcome to locate remaining issues with
>         your own forms.
>
>         The XSLT part has been reduced to minimal for better
>         performance. Instead of parsing the XPath expressions and
>         transforming all the XForms elements into HTML elements, it
>         basically just transposes the non-HTML elements into sort-of
>         custom elements: xforms:* elements become xforms-* elements
>         with xf-* and ev-* attributes.
>
>         Have a look with your favorite browser debugger! Actually,
>         authors could even prefer to directly write/generate forms
>         with this new notation and forget about the XSLT step. You can
>         compare two sources for the same form: hello.xml and hello.htm
>
>         XSLTForms Javascript classes constructors are obtaining their
>         properties directly from xf-* attributes and XPath parsing is
>         then performed.
>
>         No ids are automatically added as previously.
>
>         Extra xf-* attributes and extra xforms-* elements are used to
>         embed effective HTML rendering elements, for example,
>         xforms-body or xforms-repeat-item while, before, span or div
>         elements where used.
>
>         XSLTForms classes for xforms:select and xforms:itemset had to
>         be partially rewritten.
>
>         SVG support has been basically tested too.
>
>         CSS styling is not anymore based on xforms-* classes but on
>         custom element names and attribute selectors. For example, the
>         extra xf-bound attribute, when present, says that the XForms
>         control is bound to a node, eventually a not relevant one, and
>         the extra xf-notrelevant attribute can, then, be checked...
>
>         Thank you for your contribution!
>
>         --Alain
>
>
>
>
>     _______________________________________________
>     Xsltforms-support mailing list
>     Xsl...@li...
>     <mailto:Xsl...@li...>
>     https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

Re: [Xsltforms-support] New release: Please give it a try!

[Steven P. <ste...@cw...>]

Thanks.

When you select1 an item from an itemset, the value you select gets  
displayed as a label.

Example form:
https://homepages.cwi.nl/~steven/forms/examples/suggest/suggest1.xhtml

Steven


On Tue, 25 Feb 2020 19:23:25 +0100, Alain Couthures  
<ala...@ag...> wrote:

> Steven and Tim,
>
> A new build with more fixes can now be downloaded at  
> www.agencexml.com/1.5beta/xsltforms.zip
>
> Thank you for your contributions!
>
> --Alain
>
> Le 24/02/2020 à 14:39, Tim Thompson a écrit :
>> Steven,
>>
>> You'll want to download the .zip file again. This bug seems to have  
>> been resolved (see  
>> https://sourceforge.net/>>p/xsltforms/mailman/message/36926131/).
>>
>> Cheers,
>> Tim
>>
>> --
>> Tim A. Thompson
>> Discovery Metadata Librarian
>> Yale University Library
>>
>>
>>
>> On Mon, Feb 24, 2020 at 8:31 AM Steven Pemberton  
>> <ste...@cw...> wrote:
>>> Exciting to be testing the new implementation.
>>>
>>> I'll start simple.
>>>
>>> [Enter] in an <input/> doesn't seem to dispatch a DOMActivate.
>>> For instance,  
>>> https://homepages.cwi.nl/~steven/forms/examples/lists/list3.xhtml
>>>
>>> Steven
>>>
>>>
>>>
>>> On Wed, 05 Feb 2020 21:15:57 +0100, Alain Couthures  
>>> <ala...@ag...> wrote:
>>>
>>>> Hello,
>>>>
>>>> Please find a new release for XSLTForms at  
>>>> www.agencexml.com/1.5beta/xsltforms.zip
>>>>
>>>> It has not yet been fully tested because a lot of changes have been  
>>>> made and you are welcome to locate remaining issues with >>>>your own  
>>>> forms.
>>>>
>>>> The XSLT part has been reduced to minimal for better performance.  
>>>> Instead of parsing the XPath expressions and transforming all >>>>the  
>>>> XForms elements into HTML elements, it basically just transposes the  
>>>> non-HTML elements into sort-of custom elements: >>>>xforms:* elements  
>>>> become xforms-* elements with xf-* and ev-* attributes.
>>>>
>>>> Have a look with your favorite browser debugger! Actually, authors  
>>>> could even prefer to directly write/generate forms with this new  
>>>> >>>>notation and forget about the XSLT step. You can compare two  
>>>> sources for the same form: hello.xml and hello.htm
>>>>
>>>> XSLTForms Javascript classes constructors are obtaining their  
>>>> properties directly from xf-* attributes and XPath parsing is then  
>>>> >>>>performed.
>>>>
>>>> No ids are automatically added as previously.
>>>>
>>>> Extra xf-* attributes and extra xforms-* elements are used to embed  
>>>> effective HTML rendering elements, for example, xforms-body >>>>or  
>>>> xforms-repeat-item while, before, span or div elements where used.
>>>>
>>>> XSLTForms classes for xforms:select and xforms:itemset had to be  
>>>> partially rewritten.
>>>>
>>>> SVG support has been basically tested too.
>>>>
>>>> CSS styling is not anymore based on xforms-* classes but on custom  
>>>> element names and attribute selectors. For example, the >>>>extra  
>>>> xf-bound attribute, when present, says that the XForms control is  
>>>> bound to a node, eventually a not relevant one, and the >>>>extra  
>>>> xf-notrelevant attribute can, then, be checked...
>>>>
>>>> Thank you for your contribution!
>>>>
>>>> --Alain
>>>
>>>
>>>
>>> _______________________________________________
>>> Xsltforms-support mailing list
>>> Xsl...@li...
>>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support

Re: [Xsltforms-support] 1.5beta testing

[Tim T. <tim...@gm...>]

Hello, Alain,

Thanks again for the latest updates! I have another test for you.

Here is my use case: I want to display an ephemeral "Loading" message when
I trigger a submission. To achieve this, I have an instance:

<instance id="state">
  <data xmlns="">
    <status loading="false" ready="false">...Loading...</status>
  </data>
</instance>

When the submission is triggered, I call xf:setvalue to change the @loading
attribute to "true." This causes the loading message to display. When the
submission completes, the @loading attribute is set to "false" again.

For the value change to take effect, I find that I have to call xf:refresh,
or else the binding won't be registered.

In the latest version of beta1.5, if I call xf:refresh from within an
xf:submit element, the following error is thrown. This does not occur in
XSLTForms 1.4.

XSLTForms Exception
--------------------------

Incorrect Javascript code generation:

XsltForms_abstractAction.prototype.init@
https://www.tat2.io/basex2/static/xsltforms.js:11252:35
XsltForms_dispatch@https://www.tat2.io/basex2/static/xsltforms.js:11462:7
anonymous@https://www.tat2.io/basex2/static/xsltforms.js line 5740 >
Function:3:181
schback/<@https://www.tat2.io/basex2/static/xsltforms.js:5759:125
schback@https://www.tat2.io/basex2/static/xsltforms.js:5759:66
schloader@https://www.tat2.io/basex2/static/xsltforms.js:5780:11
XsltForms_class.activateAll@
https://www.tat2.io/basex2/static/xsltforms.js:5815:11
xsltforms_init@https://www.tat2.io/basex2/static/xsltforms.js:16516:22


TypeError

mainaction.hasAttribute is not a function

However, if I call xf:refresh from within an xforms-submit action, no error
is thrown.

See examples:

*1. xf:setvalue with xf:refresh inside xf:submit (1.5beta)*:
https://www.tat2.io/basex2/static/xsltforms_setvalue_refresh_test_2020-02-27_1.5beta.xml

*2. xf:setvalue inside xf:submit, xf:refresh inside xforms-submit action
(1.5beta):*
https://www.tat2.io/basex2/static/xsltforms_setvalue_refresh_test_2020-02-27_1.5beta_v2.xml

*3. xf:setvalue with xf:refresh inside xf:submit (1.4):*
https://www.tat2.io/basex2/static/xsltforms_setvalue_refresh_test_2020-02-27_1.4.xml


Best regards,
Tim


--
Tim A. Thompson
Discovery Metadata Librarian
Yale University Library

On Mon, Feb 17, 2020 at 4:56 PM Tim Thompson <tim...@gm...> wrote:

> Thank you, Alain!
>
> If you don't mind, I have another test form that works in XSLTForms 1.4
> but not 1.5beta.
>
> This one is testing xf:var again.
>
> In 1.5beta, an error is thrown:
> Assertion failed: Binding evaluation didn't returned a nodeset but '1' for
> XPath expression: count(ancestor::item)
>
> https://www.tat2.io/basex2/static/xsltforms_var_test_2020-02-17_with_var_1.5beta.xml
>
> In 1.4, the form works as expected:
>
> https://www.tat2.io/basex2/static/xsltforms_var_test_2020-02-17_with_var_1.4.xml
>
> Best regards,
> Tim
>
>
> --
> Tim A. Thompson
> Discovery Metadata Librarian
> Yale University Library
>
>
> On Mon, Feb 17, 2020 at 3:54 PM Alain Couthures <
> ala...@ag...> wrote:
>
>> Hello Tim,
>>
>> This issue is now fixed (and some more actually...).
>>
>> The new build can be downloaded at the same URL:
>> www.agencexml.com/1.5beta/xsltforms.zip
>>
>> Thank you again for your contributions!
>>
>> --Alain
>>
>> Le 15/02/2020 à 01:15, Tim Thompson a écrit :
>>
>> Hello, Alain,
>>
>> Another test for you:
>>
>> In XSLTForms 1.5beta, the DOMActivate event is not being evoked for input
>> controls. See this test form:
>>
>>
>> https://www.tat2.io/basex2/static/xsltforms_DOMActivate_test_2020-02-14_1-5beta.xml
>>
>> Pressing "enter" in the input field does nothing, whereas clicking the
>> button triggers the event.
>>
>> Compare this to a form running XSLTForms 1.4:
>>
>>
>> https://www.tat2.io/basex2/static/xsltforms_DOMActivate_test_2020-02-14_1-4.xml
>>
>> Here, the DOMActivate enter works in both the input field with the
>> "enter" key and with the button.
>>
>> All best,
>> Tim
>>
>> --
>> Tim A. Thompson
>> Discovery Metadata Librarian
>> Yale University Library
>>
>> On Wed, Feb 12, 2020 at 5:51 PM Tim Thompson <tim...@gm...> wrote:
>>
>>> Great! Works perfectly now. Looking forward to the XML Prague
>>> proceedings and video for your presentation with Steven Pemberton.
>>>
>>> Thanks again,
>>> Tim
>>>
>>>
>>> --
>>> Tim A. Thompson
>>> Discovery Metadata Librarian
>>> Yale University Library
>>>
>>>
>>>
>>> On Wed, Feb 12, 2020 at 4:00 PM Alain Couthures <
>>> ala...@ag...> wrote:
>>>
>>>> Hello Tim,
>>>>
>>>> (1) The xf:group processing was not correct: in the new approach, an
>>>> xf-bound attribute has to be automatically added to each xforms-* element
>>>> when xf-ref (or xf-bind) is evaluated as a non empty nodeset. CSS attribute
>>>> selectors are, then, used to display/hide xforms-* elements accordingly.
>>>>
>>>> (2) The xf:var processing was not functional: it should now work, at
>>>> least, outside of actions.
>>>>
>>>> (3) The profiler is actually just another external form: I have added
>>>> the corresponding file into the updated .zip file at
>>>> www.agencexml.com/1.5beta/xsltforms.zip
>>>>
>>>> Thank you very much for your contributions!
>>>>
>>>> --Alain
>>>>
>>>> Le 09/02/2020 à 20:51, Tim Thompson a écrit :
>>>>
>>>> Hello, Alain,
>>>>
>>>> I've been testing an existing form with the new release and have some
>>>> feedback. First, the performance improvement seems impressive, and CSS
>>>> styling with Bootstrap now seems much easier. Thank you!
>>>>
>>>> I did notice some issues after testing, however.
>>>>
>>>> (1)
>>>> There seems to be a bug with XPath predicate filtering in xf:group
>>>> elements. For example, a group binding such as <xf:group
>>>> ref="instance('response')/response[*]">...</xf:group>, where the response
>>>> element should initially be empty (before a submission is executed) does
>>>> not seem to work.
>>>>
>>>> See the test form copied below. Example form at:
>>>> https://www.tat2.io/basex2/static/xsltforms_test_2020-02-09.xml
>>>>
>>>> (2)
>>>> I see that the xforms:var element is not currently supported. When
>>>> loading a form with an XForms variable defined, I get an error message:
>>>>
>>>> Error initializing:
>>>>
>>>> xforms:var is not supported
>>>>
>>>> (3)
>>>> I also see that the XSLTForms Profiler does not seem to be available.
>>>> When I try to open it, I get an error:
>>>>
>>>> File not found (404):
>>>> https://www.tat2.io/basex2/static/xsltforms_profiler.xhtml
>>>>
>>>>
>>>> *--Test form for XPath predicate bug--*
>>>>
>>>> <?xml-stylesheet type="text/xsl" href="..."?>
>>>> <html xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="
>>>> http://www.w3.org/2001/XMLSchema" xmlns:xf="
>>>> http://www.w3.org/2002/xforms" xmlns:h="http://www.w3.org/1999/xhtml"
>>>> xmlns:ev="http://www.w3.org/2001/xml-events" xmlns="
>>>> http://www.w3.org/1999/xhtml">
>>>>   <head>
>>>>     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"
>>>> />
>>>>     <title>XForms/XPath Predicate Test</title>
>>>>     <style type="text/css"/>
>>>>     <model xmlns="http://www.w3.org/2002/xforms" id="m">
>>>>       <instance id="default">
>>>>         <data xmlns="">
>>>>           <default/>
>>>>         </data>
>>>>       </instance>
>>>>       <instance id="response">
>>>>         <data xmlns="">
>>>>           <response/>
>>>>         </data>
>>>>       </instance>
>>>>       <instance id="response-test">
>>>>         <data xmlns="">
>>>>           <response>
>>>>             <testing>Testing</testing>
>>>>           </response>
>>>>         </data>
>>>>       </instance>
>>>>     </model>
>>>>   </head>
>>>>   <body>
>>>>     <div class="container-fluid">
>>>>       <hr class="blue" />
>>>>       <h1>XForms/XPath predicate test</h1>
>>>>       <xf:group ref="instance('response')/response[*]">
>>>>         <h2 style="color: red;">This should not display!</h2>
>>>>         <xf:output value="concat('Value of &quot;serialize(.)&quot;: ',
>>>> serialize(.))"/>
>>>>       </xf:group>
>>>>       <xf:group ref="instance('response-test')/response[*]">
>>>>         <h2 style="color: blue;">This should display.</h2>
>>>>         <xf:output value="concat('Value of &quot;serialize(.)&quot;: ',
>>>> serialize(.))"/>
>>>>       </xf:group>
>>>>     </div>
>>>>   </body>
>>>> </html>
>>>>
>>>>
>>>>
>>>> --
>>>> Tim A. Thompson
>>>> Discovery Metadata Librarian
>>>> Yale University Library
>>>>
>>>> On Sun, Feb 9, 2020 at 11:06 AM Tim Thompson <tim...@gm...>
>>>> wrote:
>>>>
>>>>> Hello, Alain,
>>>>>
>>>>> Congratulations on this milestone! I am very eager to try and test the
>>>>> new release. Is XSLTForms now using Fleur for XPath parsing? Does this mean
>>>>> that XPath 3.0 functions are now supported? I guess I can test this myself
>>>>> :)
>>>>>
>>>>> It's quite amazing to see the xsltforms.xsl file down to just over 500
>>>>> lines.
>>>>>
>>>>> Thanks again for all your work.
>>>>>
>>>>> Best regards,
>>>>> Tim
>>>>>
>>>>>
>>>>> --
>>>>> Tim A. Thompson
>>>>> Discovery Metadata Librarian
>>>>> Yale University Library
>>>>>
>>>>> On Wed, Feb 5, 2020 at 3:16 PM Alain Couthures <
>>>>> ala...@ag...> wrote:
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> Please find a new release for XSLTForms at
>>>>>> www.agencexml.com/1.5beta/xsltforms.zip
>>>>>>
>>>>>> It has not yet been fully tested because a lot of changes have been
>>>>>> made and you are welcome to locate remaining issues with your own forms.
>>>>>>
>>>>>> The XSLT part has been reduced to minimal for better performance.
>>>>>> Instead of parsing the XPath expressions and transforming all the XForms
>>>>>> elements into HTML elements, it basically just transposes the non-HTML
>>>>>> elements into sort-of custom elements: xforms:* elements become xforms-*
>>>>>> elements with xf-* and ev-* attributes.
>>>>>>
>>>>>> Have a look with your favorite browser debugger! Actually, authors
>>>>>> could even prefer to directly write/generate forms with this new notation
>>>>>> and forget about the XSLT step. You can compare two sources for the same
>>>>>> form: hello.xml and hello.htm
>>>>>>
>>>>>> XSLTForms Javascript classes constructors are obtaining their
>>>>>> properties directly from xf-* attributes and XPath parsing is then
>>>>>> performed.
>>>>>>
>>>>>> No ids are automatically added as previously.
>>>>>>
>>>>>> Extra xf-* attributes and extra xforms-* elements are used to embed
>>>>>> effective HTML rendering elements, for example, xforms-body or
>>>>>> xforms-repeat-item while, before, span or div elements where used.
>>>>>>
>>>>>> XSLTForms classes for xforms:select and xforms:itemset had to be
>>>>>> partially rewritten.
>>>>>>
>>>>>> SVG support has been basically tested too.
>>>>>>
>>>>>> CSS styling is not anymore based on xforms-* classes but on custom
>>>>>> element names and attribute selectors. For example, the extra xf-bound
>>>>>> attribute, when present, says that the XForms control is bound to a node,
>>>>>> eventually a not relevant one, and the extra xf-notrelevant attribute can,
>>>>>> then, be checked...
>>>>>>
>>>>>> Thank you for your contribution!
>>>>>>
>>>>>> --Alain
>>>>>> _______________________________________________
>>>>>> Xsltforms-support mailing list
>>>>>> Xsl...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>>>>>
>>>>>
>>>>
>>

Re: [Xsltforms-support] 1.5beta testing

[Alain C. <ala...@ag...>]

Hello Tim,

It appears that there is actually no event attached to this refresh 
action. The latest 1.5beta build does not support this situation so a 
Javascript error occurs (I don't know whether a warning should be 
displayed or if it better just to ignore "unreachable" actions).

Please try again with an embedding xf:action for xf:setvalue followed by 
xf:refresh (which might be useless BTW).

The next build should just ignore this.

Thanks!

--Alain


Le 28/02/2020 à 04:16, Tim Thompson a écrit :
> Hello, Alain,
>
> Thanks again for the latest updates! I have another test for you.
>
> Here is my use case: I want to display an ephemeral "Loading" message 
> when I trigger a submission. To achieve this, I have an instance:
>
> <instance id="state">
>   <data xmlns="">
>     <status loading="false" ready="false">...Loading...</status>
>   </data>
> </instance>
>
> When the submission is triggered, I call xf:setvalue to change the 
> @loading attribute to "true." This causes the loading message to 
> display. When the submission completes, the @loading attribute is set 
> to "false" again.
>
> For the value change to take effect, I find that I have to call 
> xf:refresh, or else the binding won't be registered.
>
> In the latest version of beta1.5, if I call xf:refresh from within an 
> xf:submit element, the following error is thrown. This does not occur 
> in XSLTForms 1.4.
>
> XSLTForms Exception
> --------------------------
>
> Incorrect Javascript code generation:
>
> XsltForms_abstractAction.prototype.init@https://www.tat2.io/basex2/static/xsltforms.js:11252:35
> XsltForms_dispatch@https://www.tat2.io/basex2/static/xsltforms.js:11462:7
> anonymous@https://www.tat2.io/basex2/static/xsltforms.js line 5740 > 
> Function:3:181
> schback/<@https://www.tat2.io/basex2/static/xsltforms.js:5759:125
> schback@https://www.tat2.io/basex2/static/xsltforms.js:5759:66
> schloader@https://www.tat2.io/basex2/static/xsltforms.js:5780:11
> XsltForms_class.activateAll@https://www.tat2.io/basex2/static/xsltforms.js:5815:11
> xsltforms_init@https://www.tat2.io/basex2/static/xsltforms.js:16516:22
>
>
> TypeError
>
> mainaction.hasAttribute is not a function
>
> However, if I call xf:refresh from within an xforms-submit action, no 
> error is thrown.
>
> See examples:
>
> *1. xf:setvalue with xf:refresh inside xf:submit (1.5beta)*:
> https://www.tat2.io/basex2/static/xsltforms_setvalue_refresh_test_2020-02-27_1.5beta.xml
>
> *2. xf:setvalue inside xf:submit, xf:refresh inside xforms-submit 
> action (1.5beta):*
> https://www.tat2.io/basex2/static/xsltforms_setvalue_refresh_test_2020-02-27_1.5beta_v2.xml
>
> *3. xf:setvalue with xf:refresh inside xf:submit (1.4):*
> https://www.tat2.io/basex2/static/xsltforms_setvalue_refresh_test_2020-02-27_1.4.xml
>
>
> Best regards,
> Tim
>
>
> --
> Tim A. Thompson
> Discovery Metadata Librarian
> Yale University Library
>
> On Mon, Feb 17, 2020 at 4:56 PM Tim Thompson <tim...@gm... 
> <mailto:tim...@gm...>> wrote:
>
>     Thank you, Alain!
>
>     If you don't mind, I have another test form that works in
>     XSLTForms 1.4 but not 1.5beta.
>
>     This one is testing xf:var again.
>
>     In 1.5beta, an error is thrown:
>     Assertion failed: Binding evaluation didn't returned a nodeset but
>     '1' for XPath expression: count(ancestor::item)
>     https://www.tat2.io/basex2/static/xsltforms_var_test_2020-02-17_with_var_1.5beta.xml
>
>     In 1.4, the form works as expected:
>     https://www.tat2.io/basex2/static/xsltforms_var_test_2020-02-17_with_var_1.4.xml
>
>     Best regards,
>     Tim
>
>
>     --
>     Tim A. Thompson
>     Discovery Metadata Librarian
>     Yale University Library
>
>
>     On Mon, Feb 17, 2020 at 3:54 PM Alain Couthures
>     <ala...@ag...
>     <mailto:ala...@ag...>> wrote:
>
>         Hello Tim,
>
>         This issue is now fixed (and some more actually...).
>
>         The new build can be downloaded at the same URL:
>         www.agencexml.com/1.5beta/xsltforms.zip
>         <http://www.agencexml.com/1.5beta/xsltforms.zip>
>
>         Thank you again for your contributions!
>
>         --Alain
>
>         Le 15/02/2020 à 01:15, Tim Thompson a écrit :
>>         Hello, Alain,
>>
>>         Another test for you:
>>
>>         In XSLTForms 1.5beta, the DOMActivate event is not being
>>         evoked for input controls. See this test form:
>>
>>         https://www.tat2.io/basex2/static/xsltforms_DOMActivate_test_2020-02-14_1-5beta.xml
>>
>>         Pressing "enter" in the input field does nothing, whereas
>>         clicking the button triggers the event.
>>
>>         Compare this to a form running XSLTForms 1.4:
>>
>>         https://www.tat2.io/basex2/static/xsltforms_DOMActivate_test_2020-02-14_1-4.xml
>>
>>         Here, the DOMActivate enter works in both the input field
>>         with the "enter" key and with the button.
>>
>>         All best,
>>         Tim
>>
>>         --
>>         Tim A. Thompson
>>         Discovery Metadata Librarian
>>         Yale University Library
>>
>>         On Wed, Feb 12, 2020 at 5:51 PM Tim Thompson
>>         <tim...@gm... <mailto:tim...@gm...>> wrote:
>>
>>             Great! Works perfectly now. Looking forward to the XML
>>             Prague proceedings and video for your presentation with
>>             Steven Pemberton.
>>
>>             Thanks again,
>>             Tim
>>
>>
>>             --
>>             Tim A. Thompson
>>             Discovery Metadata Librarian
>>             Yale University Library
>>
>>
>>
>>             On Wed, Feb 12, 2020 at 4:00 PM Alain Couthures
>>             <ala...@ag...
>>             <mailto:ala...@ag...>> wrote:
>>
>>                 Hello Tim,
>>
>>                 (1) The xf:group processing was not correct: in the
>>                 new approach, an xf-bound attribute has to be
>>                 automatically added to each xforms-* element when
>>                 xf-ref (or xf-bind) is evaluated as a non empty
>>                 nodeset. CSS attribute selectors are, then, used to
>>                 display/hide xforms-* elements accordingly.
>>
>>                 (2) The xf:var processing was not functional: it
>>                 should now work, at least, outside of actions.
>>
>>                 (3) The profiler is actually just another external
>>                 form: I have added the corresponding file into the
>>                 updated .zip file at
>>                 www.agencexml.com/1.5beta/xsltforms.zip
>>                 <http://www.agencexml.com/1.5beta/xsltforms.zip>
>>
>>                 Thank you very much for your contributions!
>>
>>                 --Alain
>>
>>                 Le 09/02/2020 à 20:51, Tim Thompson a écrit :
>>>                 Hello, Alain,
>>>
>>>                 I've been testing an existing form with the new
>>>                 release and have some feedback. First, the
>>>                 performance improvement seems impressive, and CSS
>>>                 styling with Bootstrap now seems much easier. Thank you!
>>>
>>>                 I did notice some issues after testing, however.
>>>
>>>                 (1)
>>>                 There seems to be a bug with XPath predicate
>>>                 filtering in xf:group elements. For example, a group
>>>                 binding such as <xf:group
>>>                 ref="instance('response')/response[*]">...</xf:group>,
>>>                 where the response element should initially be empty
>>>                 (before a submission is executed) does not seem to
>>>                 work.
>>>
>>>                 See the test form copied below. Example form at:
>>>                 https://www.tat2.io/basex2/static/xsltforms_test_2020-02-09.xml
>>>
>>>                 (2)
>>>                 I see that the xforms:var element is not currently
>>>                 supported. When loading a form with an XForms
>>>                 variable defined, I get an error message:
>>>
>>>                 Error initializing:
>>>
>>>                 xforms:var is not supported
>>>
>>>                 (3)
>>>                 I also see that the XSLTForms Profiler does not seem
>>>                 to be available. When I try to open it, I get an error:
>>>
>>>                 File not found (404):
>>>                 https://www.tat2.io/basex2/static/xsltforms_profiler.xhtml
>>>
>>>                 *
>>>                 *
>>>                 *--Test form for XPath predicate bug--*
>>>                 *
>>>                 *
>>>                 <?xml-stylesheet type="text/xsl" href="..."?>
>>>                 <html
>>>                 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>>                 xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>>>                 xmlns:xf="http://www.w3.org/2002/xforms"
>>>                 xmlns:h="http://www.w3.org/1999/xhtml"
>>>                 xmlns:ev="http://www.w3.org/2001/xml-events"
>>>                 xmlns="http://www.w3.org/1999/xhtml">
>>>                   <head>
>>>                     <meta http-equiv="Content-Type"
>>>                 content="text/html; charset=UTF-8" />
>>>                     <title>XForms/XPath Predicate Test</title>
>>>                     <style type="text/css"/>
>>>                     <model xmlns="http://www.w3.org/2002/xforms" id="m">
>>>                       <instance id="default">
>>>                         <data xmlns="">
>>>                           <default/>
>>>                         </data>
>>>                       </instance>
>>>                       <instance id="response">
>>>                         <data xmlns="">
>>>                           <response/>
>>>                         </data>
>>>                       </instance>
>>>                       <instance id="response-test">
>>>                         <data xmlns="">
>>>                           <response>
>>>                 <testing>Testing</testing>
>>>                           </response>
>>>                         </data>
>>>                       </instance>
>>>                     </model>
>>>                   </head>
>>>                   <body>
>>>                     <div class="container-fluid">
>>>                       <hr class="blue" />
>>>                       <h1>XForms/XPath predicate test</h1>
>>>                       <xf:group ref="instance('response')/response[*]">
>>>                         <h2 style="color: red;">This should not
>>>                 display!</h2>
>>>                         <xf:output value="concat('Value of
>>>                 &quot;serialize(.)&quot;: ', serialize(.))"/>
>>>                       </xf:group>
>>>                       <xf:group
>>>                 ref="instance('response-test')/response[*]">
>>>                         <h2 style="color: blue;">This should
>>>                 display.</h2>
>>>                         <xf:output value="concat('Value of
>>>                 &quot;serialize(.)&quot;: ', serialize(.))"/>
>>>                       </xf:group>
>>>                     </div>
>>>                   </body>
>>>                 </html>
>>>
>>>
>>>
>>>                 --
>>>                 Tim A. Thompson
>>>                 Discovery Metadata Librarian
>>>                 Yale University Library
>>>
>>>                 On Sun, Feb 9, 2020 at 11:06 AM Tim Thompson
>>>                 <tim...@gm... <mailto:tim...@gm...>> wrote:
>>>
>>>                     Hello, Alain,
>>>
>>>                     Congratulations on this milestone! I am very
>>>                     eager to try and test the new release. Is
>>>                     XSLTForms now using Fleur for XPath parsing?
>>>                     Does this mean that XPath 3.0 functions are now
>>>                     supported? I guess I can test this myself :)
>>>
>>>                     It's quite amazing to see the xsltforms.xsl file
>>>                     down to just over 500 lines.
>>>
>>>                     Thanks again for all your work.
>>>
>>>                     Best regards,
>>>                     Tim
>>>
>>>
>>>                     --
>>>                     Tim A. Thompson
>>>                     Discovery Metadata Librarian
>>>                     Yale University Library
>>>
>>>                     On Wed, Feb 5, 2020 at 3:16 PM Alain Couthures
>>>                     <ala...@ag...
>>>                     <mailto:ala...@ag...>> wrote:
>>>
>>>                         Hello,
>>>
>>>                         Please find a new release for XSLTForms at
>>>                         www.agencexml.com/1.5beta/xsltforms.zip
>>>                         <http://www.agencexml.com/1.5beta/xsltforms.zip>
>>>
>>>                         It has not yet been fully tested because a
>>>                         lot of changes have been made and you are
>>>                         welcome to locate remaining issues with your
>>>                         own forms.
>>>
>>>                         The XSLT part has been reduced to minimal
>>>                         for better performance. Instead of parsing
>>>                         the XPath expressions and transforming all
>>>                         the XForms elements into HTML elements, it
>>>                         basically just transposes the non-HTML
>>>                         elements into sort-of custom elements:
>>>                         xforms:* elements become xforms-* elements
>>>                         with xf-* and ev-* attributes.
>>>
>>>                         Have a look with your favorite browser
>>>                         debugger! Actually, authors could even
>>>                         prefer to directly write/generate forms with
>>>                         this new notation and forget about the XSLT
>>>                         step. You can compare two sources for the
>>>                         same form: hello.xml and hello.htm
>>>
>>>                         XSLTForms Javascript classes constructors
>>>                         are obtaining their properties directly from
>>>                         xf-* attributes and XPath parsing is then
>>>                         performed.
>>>
>>>                         No ids are automatically added as previously.
>>>
>>>                         Extra xf-* attributes and extra xforms-*
>>>                         elements are used to embed effective HTML
>>>                         rendering elements, for example, xforms-body
>>>                         or xforms-repeat-item while, before, span or
>>>                         div elements where used.
>>>
>>>                         XSLTForms classes for xforms:select and
>>>                         xforms:itemset had to be partially rewritten.
>>>
>>>                         SVG support has been basically tested too.
>>>
>>>                         CSS styling is not anymore based on xforms-*
>>>                         classes but on custom element names and
>>>                         attribute selectors. For example, the extra
>>>                         xf-bound attribute, when present, says that
>>>                         the XForms control is bound to a node,
>>>                         eventually a not relevant one, and the extra
>>>                         xf-notrelevant attribute can, then, be
>>>                         checked...
>>>
>>>                         Thank you for your contribution!
>>>
>>>                         --Alain
>>>                         _______________________________________________
>>>                         Xsltforms-support mailing list
>>>                         Xsl...@li...
>>>                         <mailto:Xsl...@li...>
>>>                         https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>>
>>
>

Re: [Xsltforms-support] 1.5beta testing

[Tim T. <tim...@gm...>]

Ah, I see--my mistake. I think I was confused by assuming that the
xf:refresh would inherit a DOMActivate event from the xf:submit button.

Thanks,
Tim

--
Tim A. Thompson
Discovery Metadata Librarian
Yale University Library

On Fri, Feb 28, 2020 at 11:54 AM Alain Couthures <
ala...@ag...> wrote:

> Hello Tim,
>
> It appears that there is actually no event attached to this refresh
> action. The latest 1.5beta build does not support this situation so a
> Javascript error occurs (I don't know whether a warning should be displayed
> or if it better just to ignore "unreachable" actions).
>
> Please try again with an embedding xf:action for xf:setvalue followed by
> xf:refresh (which might be useless BTW).
>
> The next build should just ignore this.
>
> Thanks!
>
> --Alain
>
>
> Le 28/02/2020 à 04:16, Tim Thompson a écrit :
>
> Hello, Alain,
>
> Thanks again for the latest updates! I have another test for you.
>
> Here is my use case: I want to display an ephemeral "Loading" message when
> I trigger a submission. To achieve this, I have an instance:
>
> <instance id="state">
>   <data xmlns="">
>     <status loading="false" ready="false">...Loading...</status>
>   </data>
> </instance>
>
> When the submission is triggered, I call xf:setvalue to change the
> @loading attribute to "true." This causes the loading message to display.
> When the submission completes, the @loading attribute is set to "false"
> again.
>
> For the value change to take effect, I find that I have to call
> xf:refresh, or else the binding won't be registered.
>
> In the latest version of beta1.5, if I call xf:refresh from within an
> xf:submit element, the following error is thrown. This does not occur in
> XSLTForms 1.4.
>
> XSLTForms Exception
> --------------------------
>
> Incorrect Javascript code generation:
>
> XsltForms_abstractAction.prototype.init@
> https://www.tat2.io/basex2/static/xsltforms.js:11252:35
> XsltForms_dispatch@https://www.tat2.io/basex2/static/xsltforms.js:11462:7
> anonymous@https://www.tat2.io/basex2/static/xsltforms.js line 5740 >
> Function:3:181
> schback/<@https://www.tat2.io/basex2/static/xsltforms.js:5759:125
> schback@https://www.tat2.io/basex2/static/xsltforms.js:5759:66
> schloader@https://www.tat2.io/basex2/static/xsltforms.js:5780:11
> XsltForms_class.activateAll@
> https://www.tat2.io/basex2/static/xsltforms.js:5815:11
> xsltforms_init@https://www.tat2.io/basex2/static/xsltforms.js:16516:22
>
>
> TypeError
>
> mainaction.hasAttribute is not a function
>
> However, if I call xf:refresh from within an xforms-submit action, no
> error is thrown.
>
> See examples:
>
> *1. xf:setvalue with xf:refresh inside xf:submit (1.5beta)*:
>
> https://www.tat2.io/basex2/static/xsltforms_setvalue_refresh_test_2020-02-27_1.5beta.xml
>
> *2. xf:setvalue inside xf:submit, xf:refresh inside xforms-submit action
> (1.5beta):*
>
> https://www.tat2.io/basex2/static/xsltforms_setvalue_refresh_test_2020-02-27_1.5beta_v2.xml
>
> *3. xf:setvalue with xf:refresh inside xf:submit (1.4):*
>
> https://www.tat2.io/basex2/static/xsltforms_setvalue_refresh_test_2020-02-27_1.4.xml
>
>
> Best regards,
> Tim
>
>
> --
> Tim A. Thompson
> Discovery Metadata Librarian
> Yale University Library
>
> On Mon, Feb 17, 2020 at 4:56 PM Tim Thompson <tim...@gm...> wrote:
>
>> Thank you, Alain!
>>
>> If you don't mind, I have another test form that works in XSLTForms 1.4
>> but not 1.5beta.
>>
>> This one is testing xf:var again.
>>
>> In 1.5beta, an error is thrown:
>> Assertion failed: Binding evaluation didn't returned a nodeset but '1'
>> for XPath expression: count(ancestor::item)
>>
>> https://www.tat2.io/basex2/static/xsltforms_var_test_2020-02-17_with_var_1.5beta.xml
>>
>> In 1.4, the form works as expected:
>>
>> https://www.tat2.io/basex2/static/xsltforms_var_test_2020-02-17_with_var_1.4.xml
>>
>> Best regards,
>> Tim
>>
>>
>> --
>> Tim A. Thompson
>> Discovery Metadata Librarian
>> Yale University Library
>>
>>
>> On Mon, Feb 17, 2020 at 3:54 PM Alain Couthures <
>> ala...@ag...> wrote:
>>
>>> Hello Tim,
>>>
>>> This issue is now fixed (and some more actually...).
>>>
>>> The new build can be downloaded at the same URL:
>>> www.agencexml.com/1.5beta/xsltforms.zip
>>>
>>> Thank you again for your contributions!
>>>
>>> --Alain
>>>
>>> Le 15/02/2020 à 01:15, Tim Thompson a écrit :
>>>
>>> Hello, Alain,
>>>
>>> Another test for you:
>>>
>>> In XSLTForms 1.5beta, the DOMActivate event is not being evoked for
>>> input controls. See this test form:
>>>
>>>
>>> https://www.tat2.io/basex2/static/xsltforms_DOMActivate_test_2020-02-14_1-5beta.xml
>>>
>>> Pressing "enter" in the input field does nothing, whereas clicking the
>>> button triggers the event.
>>>
>>> Compare this to a form running XSLTForms 1.4:
>>>
>>>
>>> https://www.tat2.io/basex2/static/xsltforms_DOMActivate_test_2020-02-14_1-4.xml
>>>
>>> Here, the DOMActivate enter works in both the input field with the
>>> "enter" key and with the button.
>>>
>>> All best,
>>> Tim
>>>
>>> --
>>> Tim A. Thompson
>>> Discovery Metadata Librarian
>>> Yale University Library
>>>
>>> On Wed, Feb 12, 2020 at 5:51 PM Tim Thompson <tim...@gm...> wrote:
>>>
>>>> Great! Works perfectly now. Looking forward to the XML Prague
>>>> proceedings and video for your presentation with Steven Pemberton.
>>>>
>>>> Thanks again,
>>>> Tim
>>>>
>>>>
>>>> --
>>>> Tim A. Thompson
>>>> Discovery Metadata Librarian
>>>> Yale University Library
>>>>
>>>>
>>>>
>>>> On Wed, Feb 12, 2020 at 4:00 PM Alain Couthures <
>>>> ala...@ag...> wrote:
>>>>
>>>>> Hello Tim,
>>>>>
>>>>> (1) The xf:group processing was not correct: in the new approach, an
>>>>> xf-bound attribute has to be automatically added to each xforms-* element
>>>>> when xf-ref (or xf-bind) is evaluated as a non empty nodeset. CSS attribute
>>>>> selectors are, then, used to display/hide xforms-* elements accordingly.
>>>>>
>>>>> (2) The xf:var processing was not functional: it should now work, at
>>>>> least, outside of actions.
>>>>>
>>>>> (3) The profiler is actually just another external form: I have added
>>>>> the corresponding file into the updated .zip file at
>>>>> www.agencexml.com/1.5beta/xsltforms.zip
>>>>>
>>>>> Thank you very much for your contributions!
>>>>>
>>>>> --Alain
>>>>>
>>>>> Le 09/02/2020 à 20:51, Tim Thompson a écrit :
>>>>>
>>>>> Hello, Alain,
>>>>>
>>>>> I've been testing an existing form with the new release and have some
>>>>> feedback. First, the performance improvement seems impressive, and CSS
>>>>> styling with Bootstrap now seems much easier. Thank you!
>>>>>
>>>>> I did notice some issues after testing, however.
>>>>>
>>>>> (1)
>>>>> There seems to be a bug with XPath predicate filtering in xf:group
>>>>> elements. For example, a group binding such as <xf:group
>>>>> ref="instance('response')/response[*]">...</xf:group>, where the response
>>>>> element should initially be empty (before a submission is executed) does
>>>>> not seem to work.
>>>>>
>>>>> See the test form copied below. Example form at:
>>>>> https://www.tat2.io/basex2/static/xsltforms_test_2020-02-09.xml
>>>>>
>>>>> (2)
>>>>> I see that the xforms:var element is not currently supported. When
>>>>> loading a form with an XForms variable defined, I get an error message:
>>>>>
>>>>> Error initializing:
>>>>>
>>>>> xforms:var is not supported
>>>>>
>>>>> (3)
>>>>> I also see that the XSLTForms Profiler does not seem to be available.
>>>>> When I try to open it, I get an error:
>>>>>
>>>>> File not found (404):
>>>>> https://www.tat2.io/basex2/static/xsltforms_profiler.xhtml
>>>>>
>>>>>
>>>>> *--Test form for XPath predicate bug--*
>>>>>
>>>>> <?xml-stylesheet type="text/xsl" href="..."?>
>>>>> <html xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>>>> xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xf="
>>>>> http://www.w3.org/2002/xforms" xmlns:h="http://www.w3.org/1999/xhtml"
>>>>> xmlns:ev="http://www.w3.org/2001/xml-events" xmlns="
>>>>> http://www.w3.org/1999/xhtml">
>>>>>   <head>
>>>>>     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"
>>>>> />
>>>>>     <title>XForms/XPath Predicate Test</title>
>>>>>     <style type="text/css"/>
>>>>>     <model xmlns="http://www.w3.org/2002/xforms" id="m">
>>>>>       <instance id="default">
>>>>>         <data xmlns="">
>>>>>           <default/>
>>>>>         </data>
>>>>>       </instance>
>>>>>       <instance id="response">
>>>>>         <data xmlns="">
>>>>>           <response/>
>>>>>         </data>
>>>>>       </instance>
>>>>>       <instance id="response-test">
>>>>>         <data xmlns="">
>>>>>           <response>
>>>>>             <testing>Testing</testing>
>>>>>           </response>
>>>>>         </data>
>>>>>       </instance>
>>>>>     </model>
>>>>>   </head>
>>>>>   <body>
>>>>>     <div class="container-fluid">
>>>>>       <hr class="blue" />
>>>>>       <h1>XForms/XPath predicate test</h1>
>>>>>       <xf:group ref="instance('response')/response[*]">
>>>>>         <h2 style="color: red;">This should not display!</h2>
>>>>>         <xf:output value="concat('Value of &quot;serialize(.)&quot;:
>>>>> ', serialize(.))"/>
>>>>>       </xf:group>
>>>>>       <xf:group ref="instance('response-test')/response[*]">
>>>>>         <h2 style="color: blue;">This should display.</h2>
>>>>>         <xf:output value="concat('Value of &quot;serialize(.)&quot;:
>>>>> ', serialize(.))"/>
>>>>>       </xf:group>
>>>>>     </div>
>>>>>   </body>
>>>>> </html>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Tim A. Thompson
>>>>> Discovery Metadata Librarian
>>>>> Yale University Library
>>>>>
>>>>> On Sun, Feb 9, 2020 at 11:06 AM Tim Thompson <tim...@gm...>
>>>>> wrote:
>>>>>
>>>>>> Hello, Alain,
>>>>>>
>>>>>> Congratulations on this milestone! I am very eager to try and test
>>>>>> the new release. Is XSLTForms now using Fleur for XPath parsing? Does this
>>>>>> mean that XPath 3.0 functions are now supported? I guess I can test this
>>>>>> myself :)
>>>>>>
>>>>>> It's quite amazing to see the xsltforms.xsl file down to just over
>>>>>> 500 lines.
>>>>>>
>>>>>> Thanks again for all your work.
>>>>>>
>>>>>> Best regards,
>>>>>> Tim
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Tim A. Thompson
>>>>>> Discovery Metadata Librarian
>>>>>> Yale University Library
>>>>>>
>>>>>> On Wed, Feb 5, 2020 at 3:16 PM Alain Couthures <
>>>>>> ala...@ag...> wrote:
>>>>>>
>>>>>>> Hello,
>>>>>>>
>>>>>>> Please find a new release for XSLTForms at
>>>>>>> www.agencexml.com/1.5beta/xsltforms.zip
>>>>>>>
>>>>>>> It has not yet been fully tested because a lot of changes have been
>>>>>>> made and you are welcome to locate remaining issues with your own forms.
>>>>>>>
>>>>>>> The XSLT part has been reduced to minimal for better performance.
>>>>>>> Instead of parsing the XPath expressions and transforming all the XForms
>>>>>>> elements into HTML elements, it basically just transposes the non-HTML
>>>>>>> elements into sort-of custom elements: xforms:* elements become xforms-*
>>>>>>> elements with xf-* and ev-* attributes.
>>>>>>>
>>>>>>> Have a look with your favorite browser debugger! Actually, authors
>>>>>>> could even prefer to directly write/generate forms with this new notation
>>>>>>> and forget about the XSLT step. You can compare two sources for the same
>>>>>>> form: hello.xml and hello.htm
>>>>>>>
>>>>>>> XSLTForms Javascript classes constructors are obtaining their
>>>>>>> properties directly from xf-* attributes and XPath parsing is then
>>>>>>> performed.
>>>>>>>
>>>>>>> No ids are automatically added as previously.
>>>>>>>
>>>>>>> Extra xf-* attributes and extra xforms-* elements are used to embed
>>>>>>> effective HTML rendering elements, for example, xforms-body or
>>>>>>> xforms-repeat-item while, before, span or div elements where used.
>>>>>>>
>>>>>>> XSLTForms classes for xforms:select and xforms:itemset had to be
>>>>>>> partially rewritten.
>>>>>>>
>>>>>>> SVG support has been basically tested too.
>>>>>>>
>>>>>>> CSS styling is not anymore based on xforms-* classes but on custom
>>>>>>> element names and attribute selectors. For example, the extra xf-bound
>>>>>>> attribute, when present, says that the XForms control is bound to a node,
>>>>>>> eventually a not relevant one, and the extra xf-notrelevant attribute can,
>>>>>>> then, be checked...
>>>>>>>
>>>>>>> Thank you for your contribution!
>>>>>>>
>>>>>>> --Alain
>>>>>>> _______________________________________________
>>>>>>> Xsltforms-support mailing list
>>>>>>> Xsl...@li...
>>>>>>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>>>>>>
>>>>>>
>>>>>
>>>
>

Re: [Xsltforms-support] 1.5beta testing

[Alain C. <ala...@ag...>]

Hello Tim,

Yet another 1.5beta build at www.agencexml.com/1.5beta/xsltforms.zip 
<http://www.agencexml.com/1.5beta/xsltforms.zip>

The main fix in it is about replace=all. There was also an issue about 
duplicated labels for xf:choices.

Thank you again for your contributions!

--Alain

Le 28/02/2020 à 18:50, Tim Thompson a écrit :
> Ah, I see--my mistake. I think I was confused by assuming that the 
> xf:refresh would inherit a DOMActivate event from the xf:submit button.
>
> Thanks,
> Tim
>
> --
> Tim A. Thompson
> Discovery Metadata Librarian
> Yale University Library
>
> On Fri, Feb 28, 2020 at 11:54 AM Alain Couthures 
> <ala...@ag... <mailto:ala...@ag...>> 
> wrote:
>
>     Hello Tim,
>
>     It appears that there is actually no event attached to this
>     refresh action. The latest 1.5beta build does not support this
>     situation so a Javascript error occurs (I don't know whether a
>     warning should be displayed or if it better just to ignore
>     "unreachable" actions).
>
>     Please try again with an embedding xf:action for xf:setvalue
>     followed by xf:refresh (which might be useless BTW).
>
>     The next build should just ignore this.
>
>     Thanks!
>
>     --Alain
>
>
>     Le 28/02/2020 à 04:16, Tim Thompson a écrit :
>>     Hello, Alain,
>>
>>     Thanks again for the latest updates! I have another test for you.
>>
>>     Here is my use case: I want to display an ephemeral "Loading"
>>     message when I trigger a submission. To achieve this, I have an
>>     instance:
>>
>>     <instance id="state">
>>       <data xmlns="">
>>         <status loading="false" ready="false">...Loading...</status>
>>       </data>
>>     </instance>
>>
>>     When the submission is triggered, I call xf:setvalue to change
>>     the @loading attribute to "true." This causes the loading message
>>     to display. When the submission completes, the @loading attribute
>>     is set to "false" again.
>>
>>     For the value change to take effect, I find that I have to call
>>     xf:refresh, or else the binding won't be registered.
>>
>>     In the latest version of beta1.5, if I call xf:refresh from
>>     within an xf:submit element, the following error is thrown. This
>>     does not occur in XSLTForms 1.4.
>>
>>     XSLTForms Exception
>>     --------------------------
>>
>>     Incorrect Javascript code generation:
>>
>>     XsltForms_abstractAction.prototype.init@https://www.tat2.io/basex2/static/xsltforms.js:11252:35
>>     XsltForms_dispatch@https://www.tat2.io/basex2/static/xsltforms.js:11462:7
>>     anonymous@https://www.tat2.io/basex2/static/xsltforms.js line
>>     5740 > Function:3:181
>>     schback/<@https://www.tat2.io/basex2/static/xsltforms.js:5759:125
>>     schback@https://www.tat2.io/basex2/static/xsltforms.js:5759:66
>>     schloader@https://www.tat2.io/basex2/static/xsltforms.js:5780:11
>>     XsltForms_class.activateAll@https://www.tat2.io/basex2/static/xsltforms.js:5815:11
>>     xsltforms_init@https://www.tat2.io/basex2/static/xsltforms.js:16516:22
>>
>>
>>     TypeError
>>
>>     mainaction.hasAttribute is not a function
>>
>>     However, if I call xf:refresh from within an xforms-submit
>>     action, no error is thrown.
>>
>>     See examples:
>>
>>     *1. xf:setvalue with xf:refresh inside xf:submit (1.5beta)*:
>>     https://www.tat2.io/basex2/static/xsltforms_setvalue_refresh_test_2020-02-27_1.5beta.xml
>>
>>     *2. xf:setvalue inside xf:submit, xf:refresh inside xforms-submit
>>     action (1.5beta):*
>>     https://www.tat2.io/basex2/static/xsltforms_setvalue_refresh_test_2020-02-27_1.5beta_v2.xml
>>
>>     *3. xf:setvalue with xf:refresh inside xf:submit (1.4):*
>>     https://www.tat2.io/basex2/static/xsltforms_setvalue_refresh_test_2020-02-27_1.4.xml
>>
>>
>>     Best regards,
>>     Tim
>>
>>
>>     --
>>     Tim A. Thompson
>>     Discovery Metadata Librarian
>>     Yale University Library
>>
>>     On Mon, Feb 17, 2020 at 4:56 PM Tim Thompson <tim...@gm...
>>     <mailto:tim...@gm...>> wrote:
>>
>>         Thank you, Alain!
>>
>>         If you don't mind, I have another test form that works in
>>         XSLTForms 1.4 but not 1.5beta.
>>
>>         This one is testing xf:var again.
>>
>>         In 1.5beta, an error is thrown:
>>         Assertion failed: Binding evaluation didn't returned a
>>         nodeset but '1' for XPath expression: count(ancestor::item)
>>         https://www.tat2.io/basex2/static/xsltforms_var_test_2020-02-17_with_var_1.5beta.xml
>>
>>         In 1.4, the form works as expected:
>>         https://www.tat2.io/basex2/static/xsltforms_var_test_2020-02-17_with_var_1.4.xml
>>
>>         Best regards,
>>         Tim
>>
>>
>>         --
>>         Tim A. Thompson
>>         Discovery Metadata Librarian
>>         Yale University Library
>>
>>
>>         On Mon, Feb 17, 2020 at 3:54 PM Alain Couthures
>>         <ala...@ag...
>>         <mailto:ala...@ag...>> wrote:
>>
>>             Hello Tim,
>>
>>             This issue is now fixed (and some more actually...).
>>
>>             The new build can be downloaded at the same URL:
>>             www.agencexml.com/1.5beta/xsltforms.zip
>>             <http://www.agencexml.com/1.5beta/xsltforms.zip>
>>
>>             Thank you again for your contributions!
>>
>>             --Alain
>>
>>             Le 15/02/2020 à 01:15, Tim Thompson a écrit :
>>>             Hello, Alain,
>>>
>>>             Another test for you:
>>>
>>>             In XSLTForms 1.5beta, the DOMActivate event is not being
>>>             evoked for input controls. See this test form:
>>>
>>>             https://www.tat2.io/basex2/static/xsltforms_DOMActivate_test_2020-02-14_1-5beta.xml
>>>
>>>             Pressing "enter" in the input field does nothing,
>>>             whereas clicking the button triggers the event.
>>>
>>>             Compare this to a form running XSLTForms 1.4:
>>>
>>>             https://www.tat2.io/basex2/static/xsltforms_DOMActivate_test_2020-02-14_1-4.xml
>>>
>>>             Here, the DOMActivate enter works in both the input
>>>             field with the "enter" key and with the button.
>>>
>>>             All best,
>>>             Tim
>>>
>>>             --
>>>             Tim A. Thompson
>>>             Discovery Metadata Librarian
>>>             Yale University Library
>>>
>>>             On Wed, Feb 12, 2020 at 5:51 PM Tim Thompson
>>>             <tim...@gm... <mailto:tim...@gm...>> wrote:
>>>
>>>                 Great! Works perfectly now. Looking forward to the
>>>                 XML Prague proceedings and video for your
>>>                 presentation with Steven Pemberton.
>>>
>>>                 Thanks again,
>>>                 Tim
>>>
>>>
>>>                 --
>>>                 Tim A. Thompson
>>>                 Discovery Metadata Librarian
>>>                 Yale University Library
>>>
>>>
>>>
>>>                 On Wed, Feb 12, 2020 at 4:00 PM Alain Couthures
>>>                 <ala...@ag...
>>>                 <mailto:ala...@ag...>> wrote:
>>>
>>>                     Hello Tim,
>>>
>>>                     (1) The xf:group processing was not correct: in
>>>                     the new approach, an xf-bound attribute has to
>>>                     be automatically added to each xforms-* element
>>>                     when xf-ref (or xf-bind) is evaluated as a non
>>>                     empty nodeset. CSS attribute selectors are,
>>>                     then, used to display/hide xforms-* elements
>>>                     accordingly.
>>>
>>>                     (2) The xf:var processing was not functional: it
>>>                     should now work, at least, outside of actions.
>>>
>>>                     (3) The profiler is actually just another
>>>                     external form: I have added the corresponding
>>>                     file into the updated .zip file at
>>>                     www.agencexml.com/1.5beta/xsltforms.zip
>>>                     <http://www.agencexml.com/1.5beta/xsltforms.zip>
>>>
>>>                     Thank you very much for your contributions!
>>>
>>>                     --Alain
>>>
>>>                     Le 09/02/2020 à 20:51, Tim Thompson a écrit :
>>>>                     Hello, Alain,
>>>>
>>>>                     I've been testing an existing form with the new
>>>>                     release and have some feedback. First, the
>>>>                     performance improvement seems impressive, and
>>>>                     CSS styling with Bootstrap now seems much
>>>>                     easier. Thank you!
>>>>
>>>>                     I did notice some issues after testing, however.
>>>>
>>>>                     (1)
>>>>                     There seems to be a bug with XPath predicate
>>>>                     filtering in xf:group elements. For example, a
>>>>                     group binding such as <xf:group
>>>>                     ref="instance('response')/response[*]">...</xf:group>,
>>>>                     where the response element should initially be
>>>>                     empty (before a submission is executed) does
>>>>                     not seem to work.
>>>>
>>>>                     See the test form copied below. Example form
>>>>                     at:
>>>>                     https://www.tat2.io/basex2/static/xsltforms_test_2020-02-09.xml
>>>>
>>>>                     (2)
>>>>                     I see that the xforms:var element is not
>>>>                     currently supported. When loading a form with
>>>>                     an XForms variable defined, I get an error message:
>>>>
>>>>                     Error initializing:
>>>>
>>>>                     xforms:var is not supported
>>>>
>>>>                     (3)
>>>>                     I also see that the XSLTForms Profiler does not
>>>>                     seem to be available. When I try to open it, I
>>>>                     get an error:
>>>>
>>>>                     File not found (404):
>>>>                     https://www.tat2.io/basex2/static/xsltforms_profiler.xhtml
>>>>
>>>>                     *
>>>>                     *
>>>>                     *--Test form for XPath predicate bug--*
>>>>                     *
>>>>                     *
>>>>                     <?xml-stylesheet type="text/xsl" href="..."?>
>>>>                     <html
>>>>                     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>>>                     xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>>>>                     xmlns:xf="http://www.w3.org/2002/xforms"
>>>>                     xmlns:h="http://www.w3.org/1999/xhtml"
>>>>                     xmlns:ev="http://www.w3.org/2001/xml-events"
>>>>                     xmlns="http://www.w3.org/1999/xhtml">
>>>>                       <head>
>>>>                         <meta http-equiv="Content-Type"
>>>>                     content="text/html; charset=UTF-8" />
>>>>                     <title>XForms/XPath Predicate Test</title>
>>>>                         <style type="text/css"/>
>>>>                         <model
>>>>                     xmlns="http://www.w3.org/2002/xforms" id="m">
>>>>                           <instance id="default">
>>>>                             <data xmlns="">
>>>>                               <default/>
>>>>                             </data>
>>>>                           </instance>
>>>>                           <instance id="response">
>>>>                             <data xmlns="">
>>>>                     <response/>
>>>>                             </data>
>>>>                           </instance>
>>>>                           <instance id="response-test">
>>>>                             <data xmlns="">
>>>>                               <response>
>>>>                     <testing>Testing</testing>
>>>>                     </response>
>>>>                             </data>
>>>>                           </instance>
>>>>                         </model>
>>>>                       </head>
>>>>                       <body>
>>>>                         <div class="container-fluid">
>>>>                           <hr class="blue" />
>>>>                     <h1>XForms/XPath predicate test</h1>
>>>>                           <xf:group
>>>>                     ref="instance('response')/response[*]">
>>>>                             <h2 style="color: red;">This should not
>>>>                     display!</h2>
>>>>                             <xf:output value="concat('Value of
>>>>                     &quot;serialize(.)&quot;: ', serialize(.))"/>
>>>>                           </xf:group>
>>>>                           <xf:group
>>>>                     ref="instance('response-test')/response[*]">
>>>>                             <h2 style="color: blue;">This should
>>>>                     display.</h2>
>>>>                             <xf:output value="concat('Value of
>>>>                     &quot;serialize(.)&quot;: ', serialize(.))"/>
>>>>                           </xf:group>
>>>>                         </div>
>>>>                       </body>
>>>>                     </html>
>>>>
>>>>
>>>>
>>>>                     --
>>>>                     Tim A. Thompson
>>>>                     Discovery Metadata Librarian
>>>>                     Yale University Library
>>>>
>>>>                     On Sun, Feb 9, 2020 at 11:06 AM Tim Thompson
>>>>                     <tim...@gm...
>>>>                     <mailto:tim...@gm...>> wrote:
>>>>
>>>>                         Hello, Alain,
>>>>
>>>>                         Congratulations on this milestone! I am
>>>>                         very eager to try and test the new release.
>>>>                         Is XSLTForms now using Fleur for XPath
>>>>                         parsing? Does this mean that XPath 3.0
>>>>                         functions are now supported? I guess I can
>>>>                         test this myself :)
>>>>
>>>>                         It's quite amazing to see the xsltforms.xsl
>>>>                         file down to just over 500 lines.
>>>>
>>>>                         Thanks again for all your work.
>>>>
>>>>                         Best regards,
>>>>                         Tim
>>>>
>>>>
>>>>                         --
>>>>                         Tim A. Thompson
>>>>                         Discovery Metadata Librarian
>>>>                         Yale University Library
>>>>
>>>>                         On Wed, Feb 5, 2020 at 3:16 PM Alain
>>>>                         Couthures <ala...@ag...
>>>>                         <mailto:ala...@ag...>> wrote:
>>>>
>>>>                             Hello,
>>>>
>>>>                             Please find a new release for XSLTForms
>>>>                             at
>>>>                             www.agencexml.com/1.5beta/xsltforms.zip
>>>>                             <http://www.agencexml.com/1.5beta/xsltforms.zip>
>>>>
>>>>                             It has not yet been fully tested
>>>>                             because a lot of changes have been made
>>>>                             and you are welcome to locate remaining
>>>>                             issues with your own forms.
>>>>
>>>>                             The XSLT part has been reduced to
>>>>                             minimal for better performance. Instead
>>>>                             of parsing the XPath expressions and
>>>>                             transforming all the XForms elements
>>>>                             into HTML elements, it basically just
>>>>                             transposes the non-HTML elements into
>>>>                             sort-of custom elements: xforms:*
>>>>                             elements become xforms-* elements with
>>>>                             xf-* and ev-* attributes.
>>>>
>>>>                             Have a look with your favorite browser
>>>>                             debugger! Actually, authors could even
>>>>                             prefer to directly write/generate forms
>>>>                             with this new notation and forget about
>>>>                             the XSLT step. You can compare two
>>>>                             sources for the same form: hello.xml
>>>>                             and hello.htm
>>>>
>>>>                             XSLTForms Javascript classes
>>>>                             constructors are obtaining their
>>>>                             properties directly from xf-*
>>>>                             attributes and XPath parsing is then
>>>>                             performed.
>>>>
>>>>                             No ids are automatically added as
>>>>                             previously.
>>>>
>>>>                             Extra xf-* attributes and extra
>>>>                             xforms-* elements are used to embed
>>>>                             effective HTML rendering elements, for
>>>>                             example, xforms-body or
>>>>                             xforms-repeat-item while, before, span
>>>>                             or div elements where used.
>>>>
>>>>                             XSLTForms classes for xforms:select and
>>>>                             xforms:itemset had to be partially
>>>>                             rewritten.
>>>>
>>>>                             SVG support has been basically tested too.
>>>>
>>>>                             CSS styling is not anymore based on
>>>>                             xforms-* classes but on custom element
>>>>                             names and attribute selectors. For
>>>>                             example, the extra xf-bound attribute,
>>>>                             when present, says that the XForms
>>>>                             control is bound to a node, eventually
>>>>                             a not relevant one, and the extra
>>>>                             xf-notrelevant attribute can, then, be
>>>>                             checked...
>>>>
>>>>                             Thank you for your contribution!
>>>>
>>>>                             --Alain
>>>>                             _______________________________________________
>>>>                             Xsltforms-support mailing list
>>>>                             Xsl...@li...
>>>>                             <mailto:Xsl...@li...>
>>>>                             https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>>>
>>>
>>
>

Re: [Xsltforms-support] New release: Please give it a try!

[Steven P. <ste...@cw...>]

Am I right in thinking that

    <output class="{@foo} value="bar"/>

doesn't work yet?

(Working to get the testsuite running under the new release).

Best wishes,

Steven

On Wed, 05 Feb 2020 21:15:57 +0100, Alain Couthures  
<ala...@ag...> wrote:

> Hello,
>
> Please find a new release for XSLTForms at  
> www.agencexml.com/1.5beta/xsltforms.zip
>
> It has not yet been fully tested because a lot of changes have been made  
> and you are welcome to locate remaining issues with your own forms.
>
> The XSLT part has been reduced to minimal for better performance.  
> Instead of parsing the XPath expressions and transforming all the XForms  
> >elements into HTML elements, it basically just transposes the non-HTML  
> elements into sort-of custom elements: xforms:* elements become xforms-*  
> >elements with xf-* and ev-* attributes.
>
> Have a look with your favorite browser debugger! Actually, authors could  
> even prefer to directly write/generate forms with this new notation and  
> forget >about the XSLT step. You can compare two sources for the same  
> form: hello.xml and hello.htm
>
> XSLTForms Javascript classes constructors are obtaining their properties  
> directly from xf-* attributes and XPath parsing is then performed.
>
> No ids are automatically added as previously.
>
> Extra xf-* attributes and extra xforms-* elements are used to embed  
> effective HTML rendering elements, for example, xforms-body or  
> xforms-repeat->item while, before, span or div elements where used.
>
> XSLTForms classes for xforms:select and xforms:itemset had to be  
> partially rewritten.
>
> SVG support has been basically tested too.
>
> CSS styling is not anymore based on xforms-* classes but on custom  
> element names and attribute selectors. For example, the extra xf-bound  
> >attribute, when present, says that the XForms control is bound to a  
> node, eventually a not relevant one, and the extra xf-notrelevant  
> attribute can, then, >be checked...
>
> Thank you for your contribution!
>
> --Alain

Re: [Xsltforms-support] New release: Please give it a try!

[Steven P. <ste...@cw...>]

I'm getting a strange effect:

If I run an XForm in an iframe, it's not getting the xforms-ready event.
If I run it in a tab of its own, it does.

This is happening over several forms, so I think it is a general effect,  
and not dependent on the form.

Here is an example.

In an iframe:

0 -> Dispatching event xforms-model-construct on <xforms-model id="M"/>
4 -> Calculate res
0 -> Calculate res
1 -> Calculate res
0 -> Calculate res
2 -> Calculate pass no
0 -> Calculate pass no
0 -> Calculate pass no
1 -> Calculate pass no
0 -> Calculate pass FAIL
2 -> Dispatching event xforms-model-construct-done on <xforms-model  
id="M"/>
1 -> Dispatching event xforms-model-construct on <xforms-model  
id="xsltforms_model_config"/>
1 -> Dispatching event xforms-model-construct-done on <xforms-model  
id="xsltforms_model_config"/>
5 -> Dispatching event xforms-enabled on <xforms-output/>
1 -> Dispatching event xforms-enabled on <xforms-output/>
0 -> Dispatching event xforms-enabled on <xforms-output/>
1 -> Dispatching event xforms-enabled on <xforms-output/>

That's all that happens.


In a tab:

1 -> Dispatching event go on <xforms-model id="M"/>
0 -> effectiveTarget:true
0 -> Captured event go on <XFORMS-MODEL id="M"/>
1 -> Setvalue test = 2020-04-03T23:15:15+02:00
1 -> Setvalue @req = 2020-04-03T23:15:15+02:00
0 -> Setvalue @index = 2
0 -> Dispatching event xforms-recalculate on <xforms-model id="M"/>
0 -> Calculate res 2020-04-03T23:15:15+02:00
0 -> Calculate res
0 -> Calculate res
0 -> Calculate res
1 -> Calculate pass yes
0 -> Calculate pass no
0 -> Calculate pass no
0 -> Calculate pass no
0 -> Calculate pass FAIL
0 -> Dispatching event xforms-revalidate on <xforms-model id="M"/>
1 -> Dispatching event xforms-refresh on <xforms-model id="M"/>
1 -> Dispatching event xforms-enabled on <xforms-output/>
0 -> Dispatching event xforms-optional on <xforms-output/>
0 -> Dispatching event xforms-enabled on <xforms-output/>
0 -> Dispatching event xforms-readonly on <xforms-output/>
0 -> Dispatching event xforms-valid on <xforms-output/>
0 -> Dispatching event xforms-value-changed on <xforms-output/>
1 -> Dispatching event xforms-disabled on <xforms-output class="wrong"/>
0 -> Dispatching event xforms-enabled on <xforms-output/>
1 -> Dispatching event xforms-enabled on <xforms-output/>
0 -> Dispatching event xforms-enabled on <xforms-output/>
0 -> Dispatching event xforms-ready on <xforms-model  
id="xsltforms_model_config"/>

Steven


On Wed, 05 Feb 2020 21:15:57 +0100, Alain Couthures  
<ala...@ag...> wrote:

> Hello,
>
> Please find a new release for XSLTForms at  
> www.agencexml.com/1.5beta/xsltforms.zip
>
> It has not yet been fully tested because a lot of changes have been made  
> and you are welcome to locate remaining issues with your own forms.
>
> The XSLT part has been reduced to minimal for better performance.  
> Instead of parsing the XPath expressions and transforming all the XForms  
> >elements into HTML elements, it basically just transposes the non-HTML  
> elements into sort-of custom elements: xforms:* elements become  
> xforms->* elements with xf-* and ev-* attributes.
>
> Have a look with your favorite browser debugger! Actually, authors could  
> even prefer to directly write/generate forms with this new notation and  
> forget >about the XSLT step. You can compare two sources for the same  
> form: hello.xml and hello.htm
>
> XSLTForms Javascript classes constructors are obtaining their properties  
> directly from xf-* attributes and XPath parsing is then performed.
>
> No ids are automatically added as previously.
>
> Extra xf-* attributes and extra xforms-* elements are used to embed  
> effective HTML rendering elements, for example, xforms-body or  
> xforms-repeat->item while, before, span or div elements where used.
>
> XSLTForms classes for xforms:select and xforms:itemset had to be  
> partially rewritten.
>
> SVG support has been basically tested too.
>
> CSS styling is not anymore based on xforms-* classes but on custom  
> element names and attribute selectors. For example, the extra xf-bound  
> >attribute, when present, says that the XForms control is bound to a  
> node, eventually a not relevant one, and the extra xf-notrelevant  
> attribute can, >then, be checked...
>
> Thank you for your contribution!
>
> --Alain

Re: [Xsltforms-support] New release: Please give it a try!

[Alain C. <ala...@ag...>]

<!doctype html>
<html>
 <head> 
  <meta charset="UTF-8"> 
 </head>
 <body>
  <div>
   Could you please send me a minimal test case for this issue?
  </div>
  <div>
   <br>
  </div>
  <div>
   Thanks!
  </div>
  <div>
   <br>
  </div>
  <div>
   --Alain
  </div>
  <blockquote type="cite">
   Le 3 avril 2020 à 23:18, Steven Pemberton &lt;ste...@cw...&gt; a écrit&nbsp;: 
   <br>
   <br>
   <div>
    I'm getting a strange effect:
   </div>
   <div>
    <br>
   </div>
   <div>
    If I run an XForm in an iframe, it's not getting the xforms-ready event.
   </div>
   <div>
    If I run it in a tab of its own, it does.
   </div>
   <div>
    <br>
   </div>
   <div>
    This is happening over several forms, so I think it is a general effect, and not dependent on the form.
   </div>
   <div>
    <br>
   </div>
   <div>
    Here is an example.
   </div>
   <div>
    <br>
   </div>
   <div>
    In an iframe:
   </div>
   <div>
    <br>
   </div>
   <div>
    0 -&gt; Dispatching event xforms-model-construct on &lt;xforms-model id="M"/&gt; 
    <br>4 -&gt; Calculate res 
    <br>0 -&gt; Calculate res 
    <br>1 -&gt; Calculate res 
    <br>0 -&gt; Calculate res 
    <br>2 -&gt; Calculate pass no 
    <br>0 -&gt; Calculate pass no 
    <br>0 -&gt; Calculate pass no 
    <br>1 -&gt; Calculate pass no 
    <br>0 -&gt; Calculate pass FAIL 
    <br>2 -&gt; Dispatching event xforms-model-construct-done on &lt;xforms-model id="M"/&gt; 
    <br>1 -&gt; Dispatching event xforms-model-construct on &lt;xforms-model id="xsltforms_model_config"/&gt; 
    <br>1 -&gt; Dispatching event xforms-model-construct-done on &lt;xforms-model id="xsltforms_model_config"/&gt; 
    <br>5 -&gt; Dispatching event xforms-enabled on &lt;xforms-output/&gt; 
    <br>1 -&gt; Dispatching event xforms-enabled on &lt;xforms-output/&gt; 
    <br>0 -&gt; Dispatching event xforms-enabled on &lt;xforms-output/&gt; 
    <br>1 -&gt; Dispatching event xforms-enabled on &lt;xforms-output/&gt;
   </div>
   <div>
    <br>
   </div>
   <div>
    That's all that happens.
   </div>
   <div>
    <br>
   </div>
   <div>
    <br>
   </div>
   <div>
    In a tab:
   </div>
   <div>
    <br>
   </div>
   <div>
    1 -&gt; Dispatching event go on &lt;xforms-model id="M"/&gt; 
    <br>0 -&gt; effectiveTarget:true 
    <br>0 -&gt; Captured event go on &lt;XFORMS-MODEL id="M"/&gt; 
    <br>1 -&gt; Setvalue test = 2020-04-03T23:15:15+02:00 
    <br>1 -&gt; Setvalue @req = 2020-04-03T23:15:15+02:00 
    <br>0 -&gt; Setvalue @index = 2 
    <br>0 -&gt; Dispatching event xforms-recalculate on &lt;xforms-model id="M"/&gt; 
    <br>0 -&gt; Calculate res 2020-04-03T23:15:15+02:00 
    <br>0 -&gt; Calculate res 
    <br>0 -&gt; Calculate res 
    <br>0 -&gt; Calculate res 
    <br>1 -&gt; Calculate pass yes 
    <br>0 -&gt; Calculate pass no 
    <br>0 -&gt; Calculate pass no 
    <br>0 -&gt; Calculate pass no 
    <br>0 -&gt; Calculate pass FAIL 
    <br>0 -&gt; Dispatching event xforms-revalidate on &lt;xforms-model id="M"/&gt; 
    <br>1 -&gt; Dispatching event xforms-refresh on &lt;xforms-model id="M"/&gt; 
    <br>1 -&gt; Dispatching event xforms-enabled on &lt;xforms-output/&gt; 
    <br>0 -&gt; Dispatching event xforms-optional on &lt;xforms-output/&gt; 
    <br>0 -&gt; Dispatching event xforms-enabled on &lt;xforms-output/&gt; 
    <br>0 -&gt; Dispatching event xforms-readonly on &lt;xforms-output/&gt; 
    <br>0 -&gt; Dispatching event xforms-valid on &lt;xforms-output/&gt; 
    <br>0 -&gt; Dispatching event xforms-value-changed on &lt;xforms-output/&gt; 
    <br>1 -&gt; Dispatching event xforms-disabled on &lt;xforms-output class="wrong"/&gt; 
    <br>0 -&gt; Dispatching event xforms-enabled on &lt;xforms-output/&gt; 
    <br>1 -&gt; Dispatching event xforms-enabled on &lt;xforms-output/&gt; 
    <br>0 -&gt; Dispatching event xforms-enabled on &lt;xforms-output/&gt; 
    <br>0 -&gt; Dispatching event xforms-ready on &lt;xforms-model id="xsltforms_model_config"/&gt;
   </div>
   <div>
    <br>
   </div>
   <div>
    Steven 
    <br>
    <br>
    <br>
   </div>
   <div>
    On Wed, 05 Feb 2020 21:15:57 +0100, Alain Couthures &lt;ala...@ag...&gt; wrote: 
    <br>
   </div>
   <br>
   <blockquote>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     Hello,
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     <br>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     Please find a new release for XSLTForms at 
     <a href="http://www.agencexml.com/1.5beta/xsltforms.zip" class="ox-9aac6c58ba-moz-txt-link-abbreviated">www.agencexml.com/1.5beta/xsltforms.zip</a>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     <br>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     It has not yet been fully tested because a lot of changes have been made and you are welcome to locate remaining issues with your own forms.
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     <br>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     The XSLT part has been reduced to minimal for better performance. Instead of parsing the XPath expressions and transforming all the XForms elements into HTML elements, it basically just transposes the non-HTML elements into sort-of custom elements: xforms:* elements become xforms-* elements with xf-* and ev-* attributes.
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     <br>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     Have a look with your favorite browser debugger! Actually, authors could even prefer to directly write/generate forms with this new notation and forget about the XSLT step. You can compare two sources for the same form: hello.xml and hello.htm
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     <br>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     XSLTForms Javascript classes constructors are obtaining their properties directly from xf-* attributes and XPath parsing is then performed.
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     <br>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     No ids are automatically added as previously.
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     <br>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     Extra xf-* attributes and extra xforms-* elements are used to embed effective HTML rendering elements, for example, xforms-body or xforms-repeat-item while, before, span or div elements where used.
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     <br>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     XSLTForms classes for xforms:select and xforms:itemset had to be partially rewritten.
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     <br>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     SVG support has been basically tested too.
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     <br>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     CSS styling is not anymore based on xforms-* classes but on custom element names and attribute selectors. For example, the extra xf-bound attribute, when present, says that the XForms control is bound to a node, eventually a not relevant one, and the extra xf-notrelevant attribute can, then, be checked...
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     <br>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     Thank you for your contribution!
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     <br>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     --Alain
    </div>
   </blockquote>
   <br>
   <br>
   <br>
  </blockquote>
  <div class="default-style">
   <br>&nbsp;
  </div> 
 </body>
</html>

Re: [Xsltforms-support] New release: Please give it a try!

[Steven P. <ste...@cw...>]

So I created a minimal test case, and it worked!

So I went back to the original problem example to see what was different,  
and it worked too!

So there was some glitch in the space-time continuum yesterday, because it  
is now working.

Sorry for the noise!

Steven


On Sun, 05 Apr 2020 14:02:04 +0200, Alain Couthures  
<ala...@ag...> wrote:

> Could you please send me a minimal test case for this issue?
> Thanks!
> --Alain
>> Le 3 avril 2020 à 23:18, Steven Pemberton <ste...@cw...> a  
>> écrit :
>> I'm getting a strange effect:
>> If I run an XForm in an iframe, it's not getting the xforms-ready event. 
>> If I run it in a tab of its own, it does.
>> This is happening over several forms, so I think it is a general  
>> effect, and not dependent on the form.
>> Here is an example.
>> In an iframe:
>> 0 -> Dispatching event xforms-model-construct on <xforms-model id="M"/> 
>> 4 -> Calculate res0 -> Calculate res1 -> Calculate res0 -> Calculate res 
>> 2 -> Calculate pass no0 -> Calculate pass no0 -> Calculate pass no1 ->  
>> Calculate pass no0 -> Calculate pass FAIL2 -> Dispatching event  
>> xforms-model-construct-done on <xforms-model id="M"/>1 -> Dispatching  
>> event xforms-model-construct on <xforms-model  
>> id="xsltforms_model_config"/>1 -> Dispatching event  
>> xforms-model-construct-done on <xforms-model  
>> id="xsltforms_model_config"/>5 -> Dispatching event xforms-enabled on  
>> <xforms-output/>1 -> Dispatching event xforms-enabled on  
>> <xforms-output/>0 -> Dispatching event xforms-enabled on  
>> <xforms-output/>1 -> Dispatching event xforms-enabled on  
>> <xforms-output/>
>> That's all that happens.
>>
>> In a tab:
>> 1 -> Dispatching event go on <xforms-model id="M"/>0 ->  
>> effectiveTarget:true0 -> Captured event go on <XFORMS-MODEL id="M"/>1  
>> -> Setvalue test = 2020-04-03T23:15:15+02:001 -> Setvalue @req =  
>> 2020-04-03T23:15:15+02:000 -> Setvalue @index = 20 -> Dispatching event  
>> xforms-recalculate on <xforms-model id="M"/>0 -> Calculate res  
>> 2020-04-03T23:15:15+02:000 -> Calculate res0 -> Calculate res0 ->  
>> Calculate res1 -> Calculate pass yes0 -> Calculate pass no0 ->  
>> Calculate pass no0 -> Calculate pass no0 -> Calculate pass FAIL0 ->  
>> Dispatching event xforms-revalidate on <xforms-model id="M"/>1 ->  
>> Dispatching event xforms-refresh on <xforms-model id="M"/>1 ->  
>> Dispatching event xforms-enabled on <xforms-output/>0 -> Dispatching  
>> event xforms-optional on <xforms-output/>0 -> Dispatching event  
>> xforms-enabled on <xforms-output/>0 -> Dispatching event  
>> xforms-readonly on <xforms-output/>0 -> Dispatching event xforms-valid  
>> on <xforms-output/>0 -> Dispatching event xforms-value-changed on  
>> <xforms-output/>1 -> Dispatching event xforms-disabled on  
>> <xforms-output class="wrong"/>0 -> Dispatching event xforms-enabled on  
>> <xforms-output/>1 -> Dispatching event xforms-enabled on  
>> <xforms-output/>0 -> Dispatching event xforms-enabled on  
>> <xforms-output/>0 -> Dispatching event xforms-ready on <xforms-model  
>> id="xsltforms_model_config"/>
>> Steven
>>
>> On Wed, 05 Feb 2020 21:15:57 +0100, Alain Couthures  
>> <ala...@ag...> wrote:
>>> Hello,
>>> Please find a new release for XSLTForms at  
>>> www.agencexml.com/1.5beta/xsltforms.zip
>>> It has not yet been fully tested because a lot of changes have been  
>>> made and you are >>>welcome to locate remaining issues with your own  
>>> forms.
>>> The XSLT part has been reduced to minimal for better performance.  
>>> Instead of parsing the >>>XPath expressions and transforming all the  
>>> XForms elements into HTML elements, it >>>basically just transposes  
>>> the non-HTML elements into sort-of custom elements: xforms:*  
>>> >>>elements become xforms-* elements with xf-* and ev-* attributes.
>>> Have a look with your favorite browser debugger! Actually, authors  
>>> could even prefer to >>>directly write/generate forms with this new  
>>> notation and forget about the XSLT step. You >>>can compare two  
>>> sources for the same form: hello.xml and hello.htm
>>> XSLTForms Javascript classes constructors are obtaining their  
>>> properties directly from >>>xf-* attributes and XPath parsing is then  
>>> performed.
>>> No ids are automatically added as previously.
>>> Extra xf-* attributes and extra xforms-* elements are used to embed  
>>> effective HTML >>>rendering elements, for example, xforms-body or  
>>> xforms-repeat-item while, before, span >>>or div elements where used.
>>> XSLTForms classes for xforms:select and xforms:itemset had to be  
>>> partially rewritten.
>>> SVG support has been basically tested too.
>>> CSS styling is not anymore based on xforms-* classes but on custom  
>>> element names and >>>attribute selectors. For example, the extra  
>>> xf-bound attribute, when present, says that >>>the XForms control is  
>>> bound to a node, eventually a not relevant one, and the extra  
>>> xf->>>notrelevant attribute can, then, be checked...
>>> Thank you for your contribution!
>>> --Alain
>>
>>
>>
>

Re: [Xsltforms-support] New release: Please give it a try!

[Alain C. <ala...@ag...>]

<!doctype html>
<html>
 <head> 
  <meta charset="UTF-8"> 
 </head>
 <body>
  <div>
   Hello Steven,
  </div>
  <div>
   <br>
  </div>
  <div>
   Everything was almost already there to support AVT on HTML attributes (typically @class and @style) of XForms controls so I just had to adjust the sources accordingly.
  </div>
  <div>
   <br>
  </div>
  <div>
   Please find the latest beta build at the same location:&nbsp;
   <span style="font-size: 13px;"></span>
   <a class="ox-1e2fe28a99-moz-txt-link-abbreviated" href="http://www.agencexml.com/1.5beta/xsltforms.zip" style="font-size: 13px;">www.agencexml.com/1.5beta/xsltforms.zip</a>
   <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
    <br>
   </div>
   <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
    Thank you for your feedback!
   </div>
   <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
    <br>
   </div>
   <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
    --Alain
   </div>
   <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
    <br>
   </div>
  </div>
  <blockquote type="cite">
   Le 3 avril 2020 à 22:52, Steven Pemberton &lt;ste...@cw...&gt; a écrit&nbsp;: 
   <br>
   <br>
   <div>
    Am I right in thinking that
   </div>
   <div>
    <br>
   </div>
   <div>
    &nbsp; &nbsp;&lt;output class="{@foo} value="bar"/&gt;
   </div>
   <div>
    <br>
   </div>
   <div>
    doesn't work yet?
   </div>
   <div>
    <br>
   </div>
   <div>
    (Working to get the testsuite running under the new release).
   </div>
   <div>
    <br>
   </div>
   <div>
    Best wishes,
   </div>
   <div>
    <br>
   </div>
   <div>
    Steven&nbsp;
   </div>
   <div>
    <br>
   </div>
   <div>
    On Wed, 05 Feb 2020 21:15:57 +0100, Alain Couthures &lt;ala...@ag...&gt; wrote: 
    <br>
   </div>
   <br>
   <blockquote>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     Hello,
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     <br>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     Please find a new release for XSLTForms at 
     <a href="http://www.agencexml.com/1.5beta/xsltforms.zip" class="ox-1e2fe28a99-moz-txt-link-abbreviated">www.agencexml.com/1.5beta/xsltforms.zip</a>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     <br>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     It has not yet been fully tested because a lot of changes have been made and you are welcome to locate remaining issues with your own forms.
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     <br>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     The XSLT part has been reduced to minimal for better performance. Instead of parsing the XPath expressions and transforming all the XForms elements into HTML elements, it basically just transposes the non-HTML elements into sort-of custom elements: xforms:* elements become xforms-* elements with xf-* and ev-* attributes.
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     <br>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     Have a look with your favorite browser debugger! Actually, authors could even prefer to directly write/generate forms with this new notation and forget about the XSLT step. You can compare two sources for the same form: hello.xml and hello.htm
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     <br>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     XSLTForms Javascript classes constructors are obtaining their properties directly from xf-* attributes and XPath parsing is then performed.
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     <br>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     No ids are automatically added as previously.
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     <br>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     Extra xf-* attributes and extra xforms-* elements are used to embed effective HTML rendering elements, for example, xforms-body or xforms-repeat-item while, before, span or div elements where used.
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     <br>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     XSLTForms classes for xforms:select and xforms:itemset had to be partially rewritten.
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     <br>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     SVG support has been basically tested too.
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     <br>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     CSS styling is not anymore based on xforms-* classes but on custom element names and attribute selectors. For example, the extra xf-bound attribute, when present, says that the XForms control is bound to a node, eventually a not relevant one, and the extra xf-notrelevant attribute can, then, be checked...
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     <br>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     Thank you for your contribution!
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     <br>
    </div>
    <div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
     --Alain
    </div>
   </blockquote>
   <br>
   <br>
   <br>
  </blockquote>
  <div class="default-style">
   <br>&nbsp;
  </div> 
 </body>
</html>

Re: [Xsltforms-support] New release: Please give it a try!

[Steven P. <ste...@cw...>]

Wonderful! It works.

Thanks!

Steven

On Sun, 05 Apr 2020 14:00:15 +0200, Alain Couthures  
<ala...@ag...> wrote:

> Hello Steven,
> Everything was almost already there to support AVT on HTML attributes  
> (typically @class and @style) of XForms controls so I >just had to  
> adjust the sources accordingly.
> Please find the latest beta build at the same location:   
> www.agencexml.com/1.5beta/xsltforms.zip
> Thank you for your feedback!
> --Alain
>> Le 3 avril 2020 à 22:52, Steven Pemberton <ste...@cw...> a  
>> écrit :
>> Am I right in thinking that
>>   <output class="{@foo} value="bar"/>
>> doesn't work yet?
>> (Working to get the testsuite running under the new release).
>> Best wishes,
>> Steven  
>> On Wed, 05 Feb 2020 21:15:57 +0100, Alain Couthures  
>> <ala...@ag...> wrote:
>>> Hello,
>>> Please find a new release for XSLTForms at  
>>> www.agencexml.com/1.5beta/xsltforms.zip
>>> It has not yet been fully tested because a lot of changes have been  
>>> made and you are >>>welcome to locate remaining issues with your own  
>>> forms.
>>> The XSLT part has been reduced to minimal for better performance.  
>>> Instead of parsing the >>>XPath expressions and transforming all the  
>>> XForms elements into HTML elements, it >>>basically just transposes  
>>> the non-HTML elements into sort-of custom elements: xforms:*  
>>> >>>elements become xforms-* elements with xf-* and ev-* attributes.
>>> Have a look with your favorite browser debugger! Actually, authors  
>>> could even prefer to >>>directly write/generate forms with this new  
>>> notation and forget about the XSLT step. You >>>can compare two  
>>> sources for the same form: hello.xml and hello.htm
>>> XSLTForms Javascript classes constructors are obtaining their  
>>> properties directly from >>>xf-* attributes and XPath parsing is then  
>>> performed.
>>> No ids are automatically added as previously.
>>> Extra xf-* attributes and extra xforms-* elements are used to embed  
>>> effective HTML >>>rendering elements, for example, xforms-body or  
>>> xforms-repeat-item while, before, span >>>or div elements where used.
>>> XSLTForms classes for xforms:select and xforms:itemset had to be  
>>> partially rewritten.
>>> SVG support has been basically tested too.
>>> CSS styling is not anymore based on xforms-* classes but on custom  
>>> element names and >>>attribute selectors. For example, the extra  
>>> xf-bound attribute, when present, says that >>>the XForms control is  
>>> bound to a node, eventually a not relevant one, and the extra  
>>> xf->>>notrelevant attribute can, then, be checked...
>>> Thank you for your contribution!
>>> --Alain
>>
>>
>>
>

Re: [Xsltforms-support] New release: Please give it a try!

[Steven P. <ste...@cw...>]

So it looks like the testsuite is now working with the new version.

I did create a new driver XForm that is more readable than the old one.

I'll package it all up, and send it to you tomorrow.

Steven


On Wed, 05 Feb 2020 21:15:57 +0100, Alain Couthures  
<ala...@ag...> wrote:

> Hello,
>
> Please find a new release for XSLTForms at  
> www.agencexml.com/1.5beta/xsltforms.zip
>
> It has not yet been fully tested because a lot of changes have been made  
> and you are welcome to locate remaining issues with your own forms.
>
> The XSLT part has been reduced to minimal for better performance.  
> Instead of parsing the XPath expressions and transforming all the XForms  
> >elements into HTML elements, it basically just transposes the non-HTML  
> elements into sort-of custom elements: xforms:* elements become xforms-*  
> >elements with xf-* and ev-* attributes.
>
> Have a look with your favorite browser debugger! Actually, authors could  
> even prefer to directly write/generate forms with this new notation and  
> forget >about the XSLT step. You can compare two sources for the same  
> form: hello.xml and hello.htm
>
> XSLTForms Javascript classes constructors are obtaining their properties  
> directly from xf-* attributes and XPath parsing is then performed.
>
> No ids are automatically added as previously.
>
> Extra xf-* attributes and extra xforms-* elements are used to embed  
> effective HTML rendering elements, for example, xforms-body or  
> xforms-repeat->item while, before, span or div elements where used.
>
> XSLTForms classes for xforms:select and xforms:itemset had to be  
> partially rewritten.
>
> SVG support has been basically tested too.
>
> CSS styling is not anymore based on xforms-* classes but on custom  
> element names and attribute selectors. For example, the extra xf-bound  
> >attribute, when present, says that the XForms control is bound to a  
> node, eventually a not relevant one, and the extra xf-notrelevant  
> attribute can, then, >be checked...
>
> Thank you for your contribution!
>
> --Alain