xsltforms-support — XSLTForms support list

Re: [Xsltforms-support] CDATA in subforms

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

Just to update: the previous errors were produced in eXist 2.2. I have also
done some testing in BaseX 8.2.2, and I did not get these errors. In BaseX,
the CDATA sections seem to be properly generated (no processing
instructions appear in the output) and the application runs in Chrome and
Internet Explorer 11. It still does not run in Firefox, however, which
fails to load properly and throws a vague "not well-formed" error.

--Tim

--
Tim A. Thompson
Metadata Librarian (Spanish/Portuguese Specialty)
Princeton University Library


On Tue, Jul 7, 2015 at 8:46 PM, Tim Thompson <tim...@gm...> wrote:

> Alain,
>
> Thank you very much for these updates!
>
> However, I am running into a couple of errors.
>
> 1. In addition to the CDATA comments,
> <?javax.xml.transform.enable-output-escaping?> processing instructions are
> also being output inside the <script> tags, which is causing a syntax error
> (in Firefox, Chrome, and IE). Firefox throws the following error:
>
>     SyntaxError: expected expression, got '<'
>
> 2. When I clear my browser cache and reload the page, the transformation
> breaks with a server error:
>
>     Error while serializing XML: Ambiguous rule match for
> /html/head[1]/script[1] Matches both "xhtml:script[not(@type) or @type =
> 'text/javascript'] | script[not(@type) or @type = 'text/javascript']"
>
> Sorry for the trouble!
>
> Tim
>
> --
> Tim A. Thompson
> Metadata Librarian (Spanish/Portuguese Specialty)
> Princeton University Library
>
>
> On Tue, Jul 7, 2015 at 3:23 PM, Alain Couthures <
> ala...@ag...> wrote:
>
>>  Tim,
>>
>> I have now committed CDATA support:
>>
>>    - script content is "escaped" with CDATA for "text/javascript" and
>>    "text/turtle"
>>    - @cdata-section-elements in submission is supported for all major
>>    browsers
>>
>> Thank you for your feedback!
>>
>> --Alain
>>
>>
>> Le 06/07/2015 20:00, Tim Thompson a écrit :
>>
>>   Alain,
>>
>>  I think adding the proposed CDATA encapsulations to script elements
>> would be a great solution.
>>
>>  Regarding @cdata-section-elements, I do need this functionality, in some
>> form, for the application I'm working on. But my first preference would be
>> to output the CDATA sections on the server using XQuery. Unfortunately,
>> eXist does not currently support cdata-section-elements as a serialization
>> parameter either, so I was considering the @cdata-section-elements
>> submission attribute as a temporary workaround. I do think this would be a
>> good feature to have, but for now, just adding the CDATA encapsulations
>> would make a big difference.
>>
>>  Thanks again!
>>  Tim
>>
>>
>>  --
>> Tim A. Thompson
>> Metadata Librarian (Spanish/Portuguese Specialty)
>> Princeton University Library
>>
>>
>> On Mon, Jul 6, 2015 at 1:08 PM, Alain Couthures <
>> ala...@ag...> wrote:
>>
>>>  Tim,
>>>
>>> XSLT does not preserve CDATA nodes but treats them into text nodes. It
>>> is still possible to treat script elements according to their type
>>> attributes. I can modified the XSLT stylesheet accordingly: for
>>> "text/javascript", the script value can be encapsulated with "/* <![CDATA[
>>> */" and "/* ]]> */", and, for "text/turtle", with "# <![CDATA[" and "#
>>> ]]>". What do you think?
>>>
>>> For submission, adding support for @cdata-section-elements is not
>>> difficult for non-IE browsers because serialization is performed with
>>> Javascript instructions. For IE, because serialization is still based on an
>>> XSLT transformation, the stylesheet source would have to be adapted
>>> according to @cdata-section-elements value. Do you already need this?
>>>
>>> --Alain
>>>
>>>
>>> Le 05/07/2015 04:10, Tim Thompson a écrit :
>>>
>>>    Alain,
>>>
>>>  I am trying to load a subform that contains a <script
>>> type="text/turtle"> tag with RDF data serialized as Turtle.
>>>
>>>  This data is enclosed in a CDATA section (per
>>> http://www.w3.org/TR/turtle/#h3_xhtml). However, when I load the
>>> subform (as XHTML), the CDATA is ignored and all <> characters are escaped,
>>> which causes the Turtle parser I am using to break. Shouldn't CDATA
>>> contents be ignored when a subform is loaded?
>>>
>>>  As a related question, does XSLTForms support the
>>> @cdata-section-elements attribute on <xf:submission>? I see some reference
>>> to it in the code, but wasn't sure whether it had been fully implemented.
>>> This could be very useful for dealing with non-XML formats in hybrid
>>> applications.
>>>
>>>  Many thanks,
>>>  Tim
>>>
>>>   --
>>> Tim A. Thompson
>>> Metadata Librarian (Spanish/Portuguese Specialty)
>>> Princeton University Library
>>>
>>>
>>>  ------------------------------------------------------------------------------
>>> Don't Limit Your Business. Reach for the Cloud.
>>> GigeNET's Cloud Solutions provide you with the tools and support that
>>> you need to offload your IT needs and focus on growing your business.
>>> Configured For All Businesses. Start Your Cloud Today.https://www.gigenetcloud.com/
>>>
>>>
>>>
>>> _______________________________________________
>>> Xsltforms-support mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>>
>>>
>>>
>>
>>
>

Re: [Xsltforms-support] CDATA in subforms

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

Alain,

Thank you very much for these updates!

However, I am running into a couple of errors.

1. In addition to the CDATA comments,
<?javax.xml.transform.enable-output-escaping?> processing instructions are
also being output inside the <script> tags, which is causing a syntax error
(in Firefox, Chrome, and IE). Firefox throws the following error:

    SyntaxError: expected expression, got '<'

2. When I clear my browser cache and reload the page, the transformation
breaks with a server error:

    Error while serializing XML: Ambiguous rule match for
/html/head[1]/script[1] Matches both "xhtml:script[not(@type) or @type =
'text/javascript'] | script[not(@type) or @type = 'text/javascript']"

Sorry for the trouble!

Tim

--
Tim A. Thompson
Metadata Librarian (Spanish/Portuguese Specialty)
Princeton University Library


On Tue, Jul 7, 2015 at 3:23 PM, Alain Couthures <
ala...@ag...> wrote:

>  Tim,
>
> I have now committed CDATA support:
>
>    - script content is "escaped" with CDATA for "text/javascript" and
>    "text/turtle"
>    - @cdata-section-elements in submission is supported for all major
>    browsers
>
> Thank you for your feedback!
>
> --Alain
>
>
> Le 06/07/2015 20:00, Tim Thompson a écrit :
>
>   Alain,
>
>  I think adding the proposed CDATA encapsulations to script elements would
> be a great solution.
>
>  Regarding @cdata-section-elements, I do need this functionality, in some
> form, for the application I'm working on. But my first preference would be
> to output the CDATA sections on the server using XQuery. Unfortunately,
> eXist does not currently support cdata-section-elements as a serialization
> parameter either, so I was considering the @cdata-section-elements
> submission attribute as a temporary workaround. I do think this would be a
> good feature to have, but for now, just adding the CDATA encapsulations
> would make a big difference.
>
>  Thanks again!
>  Tim
>
>
>  --
> Tim A. Thompson
> Metadata Librarian (Spanish/Portuguese Specialty)
> Princeton University Library
>
>
> On Mon, Jul 6, 2015 at 1:08 PM, Alain Couthures <
> ala...@ag...> wrote:
>
>>  Tim,
>>
>> XSLT does not preserve CDATA nodes but treats them into text nodes. It is
>> still possible to treat script elements according to their type attributes.
>> I can modified the XSLT stylesheet accordingly: for "text/javascript", the
>> script value can be encapsulated with "/* <![CDATA[ */" and "/* ]]> */",
>> and, for "text/turtle", with "# <![CDATA[" and "# ]]>". What do you think?
>>
>> For submission, adding support for @cdata-section-elements is not
>> difficult for non-IE browsers because serialization is performed with
>> Javascript instructions. For IE, because serialization is still based on an
>> XSLT transformation, the stylesheet source would have to be adapted
>> according to @cdata-section-elements value. Do you already need this?
>>
>> --Alain
>>
>>
>> Le 05/07/2015 04:10, Tim Thompson a écrit :
>>
>>    Alain,
>>
>>  I am trying to load a subform that contains a <script
>> type="text/turtle"> tag with RDF data serialized as Turtle.
>>
>>  This data is enclosed in a CDATA section (per
>> http://www.w3.org/TR/turtle/#h3_xhtml). However, when I load the subform
>> (as XHTML), the CDATA is ignored and all <> characters are escaped, which
>> causes the Turtle parser I am using to break. Shouldn't CDATA contents be
>> ignored when a subform is loaded?
>>
>>  As a related question, does XSLTForms support the
>> @cdata-section-elements attribute on <xf:submission>? I see some reference
>> to it in the code, but wasn't sure whether it had been fully implemented.
>> This could be very useful for dealing with non-XML formats in hybrid
>> applications.
>>
>>  Many thanks,
>>  Tim
>>
>>   --
>> Tim A. Thompson
>> Metadata Librarian (Spanish/Portuguese Specialty)
>> Princeton University Library
>>
>>
>>  ------------------------------------------------------------------------------
>> Don't Limit Your Business. Reach for the Cloud.
>> GigeNET's Cloud Solutions provide you with the tools and support that
>> you need to offload your IT needs and focus on growing your business.
>> Configured For All Businesses. Start Your Cloud Today.https://www.gigenetcloud.com/
>>
>>
>>
>> _______________________________________________
>> Xsltforms-support mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>
>>
>>
>
>

Re: [Xsltforms-support] CDATA in subforms

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

Tim,

I have now committed CDATA support:

  * script content is "escaped" with CDATA for "text/javascript" and
    "text/turtle"
  * @cdata-section-elements in submission is supported for all major
    browsers

Thank you for your feedback!

--Alain

Le 06/07/2015 20:00, Tim Thompson a écrit :
> Alain,
>
> I think adding the proposed CDATA encapsulations to script elements 
> would be a great solution.
>
> Regarding @cdata-section-elements, I do need this functionality, in 
> some form, for the application I'm working on. But my first preference 
> would be to output the CDATA sections on the server using XQuery. 
> Unfortunately, eXist does not currently support cdata-section-elements 
> as a serialization parameter either, so I was considering the 
> @cdata-section-elements submission attribute as a temporary 
> workaround. I do think this would be a good feature to have, but for 
> now, just adding the CDATA encapsulations would make a big difference.
>
> Thanks again!
> Tim
>
>
> --
> Tim A. Thompson
> Metadata Librarian (Spanish/Portuguese Specialty)
> Princeton University Library
>
>
> On Mon, Jul 6, 2015 at 1:08 PM, Alain Couthures 
> <ala...@ag... <mailto:ala...@ag...>> 
> wrote:
>
>     Tim,
>
>     XSLT does not preserve CDATA nodes but treats them into text
>     nodes. It is still possible to treat script elements according to
>     their type attributes. I can modified the XSLT stylesheet
>     accordingly: for "text/javascript", the script value can be
>     encapsulated with "/* <![CDATA[ */" and "/* ]]> */", and, for
>     "text/turtle", with "# <![CDATA[" and "# ]]>". What do you think?
>
>     For submission, adding support for @cdata-section-elements is not
>     difficult for non-IE browsers because serialization is performed
>     with Javascript instructions. For IE, because serialization is
>     still based on an XSLT transformation, the stylesheet source would
>     have to be adapted according to @cdata-section-elements value. Do
>     you already need this?
>
>     --Alain
>
>
>     Le 05/07/2015 04:10, Tim Thompson a écrit :
>>     Alain,
>>
>>     I am trying to load a subform that contains a <script
>>     type="text/turtle"> tag with RDF data serialized as Turtle.
>>
>>     This data is enclosed in a CDATA section (per
>>     http://www.w3.org/TR/turtle/#h3_xhtml). However, when I load the
>>     subform (as XHTML), the CDATA is ignored and all <> characters
>>     are escaped, which causes the Turtle parser I am using to break.
>>     Shouldn't CDATA contents be ignored when a subform is loaded?
>>
>>     As a related question, does XSLTForms support the
>>     @cdata-section-elements attribute on <xf:submission>? I see some
>>     reference to it in the code, but wasn't sure whether it had been
>>     fully implemented. This could be very useful for dealing with
>>     non-XML formats in hybrid applications.
>>
>>     Many thanks,
>>     Tim
>>
>>     --
>>     Tim A. Thompson
>>     Metadata Librarian (Spanish/Portuguese Specialty)
>>     Princeton University Library
>>
>>
>>     ------------------------------------------------------------------------------
>>     Don't Limit Your Business. Reach for the Cloud.
>>     GigeNET's Cloud Solutions provide you with the tools and support that
>>     you need to offload your IT needs and focus on growing your business.
>>     Configured For All Businesses. Start Your Cloud Today.
>>     https://www.gigenetcloud.com/
>>
>>
>>     _______________________________________________
>>     Xsltforms-support mailing list
>>     Xsl...@li...
>>     <mailto:Xsl...@li...>
>>     https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
>

Re: [Xsltforms-support] [xsltforms] Events not getting raised on subform element? (#8)

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

Hi, Artyom,

This might be a good question for the XSLTForms e-mail support list (copied
here). From what I can tell, since your subform target is in a separate
<xf:case>, it is not possible to load the subforms a second time without
toggling the case again. If I add <xforms:toggle case="form-sub"/> to the
#form-main triggers, it seems to work as expected:

<xforms:trigger>
    <xforms:label>Open subform 1</xforms:label>
    <xforms:action ev:event="DOMActivate">
        <xforms:message>Opening subform 1</xforms:message>
        <xforms:toggle case="form-sub"/>
        <xforms:load show="embed" targetid="subform"
resource="showform3_subform1.xml"/>
    </xforms:action>
</xforms:trigger>

--
Tim A. Thompson
Metadata Librarian (Spanish/Portuguese Specialty)
Princeton University Library


On Tue, Jul 7, 2015 at 2:32 AM, Artyom Shalkhakov <not...@gi...>
wrote:

> Hello,
>
> I have a form sketch where subforms are embedded into the main form.
> However, there are complications:
>
>    1. if subform failed to be found, then the user should be notified
>    about the error
>    2. user has to be able to dismiss the subform either by accepting or
>    rejecting it
>
> Here's the main form (showform3_load.xml):
>
> <?xml-stylesheet href="/xsltforms/xsltforms.xsl" type="text/xsl"?>
> <html xmlns="http://www.w3.org/1999/xhtml"
>       xmlns:xforms="http://www.w3.org/2002/xforms"
>       xmlns:ev="http://www.w3.org/2001/xml-events">
>   <head>
>     <title>Main Form</title>
>     <xforms:model>
>       <xforms:instance>
>         <data xmlns=""/>
>       </xforms:instance>
>       <!-- FIXME: these actions are only run once (probably get removed on subform unload?) -->
>       <xforms:action ev:event="xforms-link-exception" ev:observer="subform">
>         <xforms:message>
>           Failed to obtain the subform at: <xforms:output value="event('resource-uri')"/>,
>           error code: <xforms:output value="event('response-status-code')"/>,
>           error reason: <xforms:output value="event('response-reason-phrase')"/>
>         </xforms:message>
>       </xforms:action>
>       <xforms:action ev:event="xforms-load-done" ev:observer="subform">
>         <xforms:message>Load Success!</xforms:message>
>         <xforms:toggle case="form-sub"/>
>       </xforms:action>
>     </xforms:model>
>   </head>
>   <body>
>     <xforms:switch id="form-switch">
>       <!-- this is the "main" form -->
>       <xforms:case id="form-main">
>         <h2>Main form</h2>
>         <xforms:trigger>
>           <xforms:label>Open subform 1</xforms:label>
>           <xforms:action ev:event="DOMActivate">
>             <xforms:message>Opening subform 1</xforms:message>
>             <xforms:load show="embed" targetid="subform" resource="showform3_subform1.xml"/>
>           </xforms:action>
>         </xforms:trigger>
>         <xforms:trigger>
>           <xforms:label>Open subform 2</xforms:label>
>           <xforms:action ev:event="DOMActivate">
>             <xforms:message>Opening subform 2</xforms:message>
>             <xforms:load show="embed" targetid="subform" resource="showform3_subform2.xml"/>
>           </xforms:action>
>         </xforms:trigger>
>       </xforms:case>
>       <!-- this is the portion of the form that we will be using for subforms (e.g. Edit subform) -->
>       <xforms:case id="form-sub">
>         <xforms:trigger>
>           <xforms:label>Accept Subform</xforms:label>
>           <xforms:action ev:event="DOMActivate">
>             <xforms:message>Accepting Subform</xforms:message>
>             <xforms:unload targetid="subform"/>
>             <xforms:toggle case="form-main"/>
>           </xforms:action>
>         </xforms:trigger>
>         <!-- this actually does what we want, but the subform *by itself*
>            is invalid (there is no such targetid in the subform!
>         -->
>         <xforms:trigger>
>           <xforms:label>Reject Subform</xforms:label>
>           <xforms:action ev:event="DOMActivate">
>             <xforms:message>Rejecting Subform</xforms:message>
>             <xforms:unload targetid="subform"/>
>             <xforms:toggle case="form-main"/>
>           </xforms:action>
>         </xforms:trigger>
>         <xforms:group id="subform"/>
>       </xforms:case>
>     </xforms:switch>
>   </body>
> </html>
>
> Here is subform 1 (showform3_subform1.xml):
>
> <?xml-stylesheet href="/xsltforms/xsltforms.xsl" type="text/xsl"?>
> <html xmlns="http://www.w3.org/1999/xhtml"
>       xmlns:xforms="http://www.w3.org/2002/xforms"
>       xmlns:ev="http://www.w3.org/2001/xml-events">
>   <head>
>     <title>Subform 1</title>
>     <xforms:model>
>       <xforms:instance>
>         <data xmlns=""/>
>       </xforms:instance>
>     </xforms:model>
>   </head>
>   <body>
>     <h2>Subform 1</h2>
>     <p>hello world!</p>
>   </body>
> </html>
>
> And finally, here is subform 3 (showform3_subform2.xml):
>
> <?xml-stylesheet href="/xsltforms/xsltforms.xsl" type="text/xsl"?>
> <html xmlns="http://www.w3.org/1999/xhtml"
>       xmlns:xforms="http://www.w3.org/2002/xforms"
>       xmlns:ev="http://www.w3.org/2001/xml-events">
>   <head>
>     <title>Subform 2</title>
>     <xforms:model>
>       <xforms:instance>
>         <data xmlns=""/>
>       </xforms:instance>
>     </xforms:model>
>   </head>
>   <body>
>     <h2>Subform 2</h2>
>     <p>goodbye world!</p>
>   </body>
> </html>
>
> To reproduce:
>
>    1. Open the main form
>    2. Click on "Open subform 1"
>    3. Subform 1 will be opened
>    4. Click on "Accept Subform"
>    5. You will be brought back to the main form
>    6. Click on either "Open subform 1" or "Open subform 2", and there is
>    no change
>
> Please help me figure this one out.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/AlainCouthures/xsltforms/issues/8>.
>

Re: [Xsltforms-support] CDATA in subforms

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

Alain,

I think adding the proposed CDATA encapsulations to script elements would
be a great solution.

Regarding @cdata-section-elements, I do need this functionality, in some
form, for the application I'm working on. But my first preference would be
to output the CDATA sections on the server using XQuery. Unfortunately,
eXist does not currently support cdata-section-elements as a serialization
parameter either, so I was considering the @cdata-section-elements
submission attribute as a temporary workaround. I do think this would be a
good feature to have, but for now, just adding the CDATA encapsulations
would make a big difference.

Thanks again!
Tim


--
Tim A. Thompson
Metadata Librarian (Spanish/Portuguese Specialty)
Princeton University Library


On Mon, Jul 6, 2015 at 1:08 PM, Alain Couthures <
ala...@ag...> wrote:

>  Tim,
>
> XSLT does not preserve CDATA nodes but treats them into text nodes. It is
> still possible to treat script elements according to their type attributes.
> I can modified the XSLT stylesheet accordingly: for "text/javascript", the
> script value can be encapsulated with "/* <![CDATA[ */" and "/* ]]> */",
> and, for "text/turtle", with "# <![CDATA[" and "# ]]>". What do you think?
>
> For submission, adding support for @cdata-section-elements is not
> difficult for non-IE browsers because serialization is performed with
> Javascript instructions. For IE, because serialization is still based on an
> XSLT transformation, the stylesheet source would have to be adapted
> according to @cdata-section-elements value. Do you already need this?
>
> --Alain
>
>
> Le 05/07/2015 04:10, Tim Thompson a écrit :
>
>   Alain,
>
>  I am trying to load a subform that contains a <script type="text/turtle">
> tag with RDF data serialized as Turtle.
>
>  This data is enclosed in a CDATA section (per
> <http://www.w3.org/TR/turtle/#h3_xhtml>
> http://www.w3.org/TR/turtle/#h3_xhtml). However, when I load the subform
> (as XHTML), the CDATA is ignored and all <> characters are escaped, which
> causes the Turtle parser I am using to break. Shouldn't CDATA contents be
> ignored when a subform is loaded?
>
>  As a related question, does XSLTForms support the @cdata-section-elements
> attribute on <xf:submission>? I see some reference to it in the code, but
> wasn't sure whether it had been fully implemented. This could be very
> useful for dealing with non-XML formats in hybrid applications.
>
>  Many thanks,
>  Tim
>
>   --
> Tim A. Thompson
> Metadata Librarian (Spanish/Portuguese Specialty)
> Princeton University Library
>
>
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.https://www.gigenetcloud.com/
>
>
>
> _______________________________________________
> Xsltforms-support mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
>
>

Re: [Xsltforms-support] CDATA in subforms

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

Tim,

XSLT does not preserve CDATA nodes but treats them into text nodes. It 
is still possible to treat script elements according to their type 
attributes. I can modified the XSLT stylesheet accordingly: for 
"text/javascript", the script value can be encapsulated with "/* 
<![CDATA[ */" and "/* ]]> */", and, for "text/turtle", with "# 
<![CDATA[" and "# ]]>". What do you think?

For submission, adding support for @cdata-section-elements is not 
difficult for non-IE browsers because serialization is performed with 
Javascript instructions. For IE, because serialization is still based on 
an XSLT transformation, the stylesheet source would have to be adapted 
according to @cdata-section-elements value. Do you already need this?

--Alain

Le 05/07/2015 04:10, Tim Thompson a écrit :
> Alain,
>
> I am trying to load a subform that contains a <script 
> type="text/turtle"> tag with RDF data serialized as Turtle.
>
> This data is enclosed in a CDATA section (per 
> http://www.w3.org/TR/turtle/#h3_xhtml). However, when I load the 
> subform (as XHTML), the CDATA is ignored and all <> characters are 
> escaped, which causes the Turtle parser I am using to break. Shouldn't 
> CDATA contents be ignored when a subform is loaded?
>
> As a related question, does XSLTForms support the 
> @cdata-section-elements attribute on <xf:submission>? I see some 
> reference to it in the code, but wasn't sure whether it had been fully 
> implemented. This could be very useful for dealing with non-XML 
> formats in hybrid applications.
>
> Many thanks,
> Tim
>
> --
> Tim A. Thompson
> Metadata Librarian (Spanish/Portuguese Specialty)
> Princeton University Library
>
>
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
>
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support

[Xsltforms-support] CDATA in subforms

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

Alain,

I am trying to load a subform that contains a <script type="text/turtle">
tag with RDF data serialized as Turtle.

This data is enclosed in a CDATA section (per
http://www.w3.org/TR/turtle/#h3_xhtml). However, when I load the subform
(as XHTML), the CDATA is ignored and all <> characters are escaped, which
causes the Turtle parser I am using to break. Shouldn't CDATA contents be
ignored when a subform is loaded?

As a related question, does XSLTForms support the @cdata-section-elements
attribute on <xf:submission>? I see some reference to it in the code, but
wasn't sure whether it had been fully implemented. This could be very
useful for dealing with non-XML formats in hybrid applications.

Many thanks,
Tim

--
Tim A. Thompson
Metadata Librarian (Spanish/Portuguese Specialty)
Princeton University Library

Re: [Xsltforms-support] Javascript problem

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

Hello Mark,

Could you please send me a minimal test case for this issue?

I suspect that this might be due to some broken initialization for 
OpenLayers. Frameworks integration might have this kind of problem...

Thanks!

--Alain

Le 29/06/2015 14:56, Mark Seaborne a écrit :
> Hi,
>
> I don’t know if anyone can help me, but I have a problem with Firefox and XSLTForms:
>
> I am using XSLTForms with the OpenLayers 3 mapping library. The Javascript function that initialises the map runs fine and the map loads.
>
> However, interaction-triggered Javascript intended to change the visual state of the map has no visible effect. The code runs, properties are set, but changes never become visible in the map. So, I change the opacity of a layer, I read the new value of the property, but the opacity doesn’t actually change.
>
> I have set up a very simple page that simply includes the XSLTForms stylesheet and sets one map property using an onclick event.
>
> If I remove the XSLTForms stylesheet reference the map property change is reflected in the visual appearance of the map. When the XSLTForms stylesheet runs, the appearance of the map doesn’t change, though the code seems to run.
>
> Any ideas or suggestions gratefully received.
>
> Thanks
>
> Mark
> ------------------------------------------------------------------------------
> Monitor 25 network devices or servers for free with OpManager!
> OpManager is web-based network management software that monitors
> network devices and physical & virtual servers, alerts via email & sms
> for fault. Monitor 25 devices for free with no restriction. Download now
> http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support

Re: [Xsltforms-support] Instance viewer XML formatting

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

Tim,

XSLTForms supports all major browsers and IE requires different 
instructions for XML processing. MS Edge is similar to Firefox and 
Chrome but there are still some issues, especially concerning XSLT 
processor. I had to decide not to use anymore an XSLT stylesheet to 
serialize XML documents in XSLTForms, except for IE. So, in rev 615 and 
rev 616, indented serialization is not supported for not-IE browsers.

Luckily, I have already developed this in my own DOM implementation. I 
have just integrated this part in XSLTForms and I will commit this as 
soon as possible.

--Alain

Le 27/06/2015 17:45, Tim Thompson a écrit :
> Alain,
>
> In the last two versions of XSLTForms (615 and 616), I noticed, in 
> Firefox and Chrome, that XML pretty printing had broken in the 
> XSLTForms Profiler Instance Viewer. The XML appears as a single 
> unformatted string.
>
> I tested this on both Mac and Windows, and the result is the same. 
> However, in IE, it still works as before. For issues like this, would 
> it be better to submit an issue on GitHub?
>
> Thank you for XSLTForms!
>
> Tim
>
> --
> Tim A. Thompson
> Metadata Librarian (Spanish/Portuguese Specialty)
> Princeton University Library
>
>
>
> ------------------------------------------------------------------------------
> Monitor 25 network devices or servers for free with OpManager!
> OpManager is web-based network management software that monitors
> network devices and physical & virtual servers, alerts via email & sms
> for fault. Monitor 25 devices for free with no restriction. Download now
> http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
>
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support

[Xsltforms-support] Javascript problem

[Mark S. <m_s...@ma...>]

Hi,

I don’t know if anyone can help me, but I have a problem with Firefox and XSLTForms:

I am using XSLTForms with the OpenLayers 3 mapping library. The Javascript function that initialises the map runs fine and the map loads. 

However, interaction-triggered Javascript intended to change the visual state of the map has no visible effect. The code runs, properties are set, but changes never become visible in the map. So, I change the opacity of a layer, I read the new value of the property, but the opacity doesn’t actually change.

I have set up a very simple page that simply includes the XSLTForms stylesheet and sets one map property using an onclick event.

If I remove the XSLTForms stylesheet reference the map property change is reflected in the visual appearance of the map. When the XSLTForms stylesheet runs, the appearance of the map doesn’t change, though the code seems to run.

Any ideas or suggestions gratefully received.

Thanks

Mark    

[Xsltforms-support] Instance viewer XML formatting

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

Alain,

In the last two versions of XSLTForms (615 and 616), I noticed, in Firefox
and Chrome, that XML pretty printing had broken in the XSLTForms Profiler
Instance Viewer. The XML appears as a single unformatted string.

I tested this on both Mac and Windows, and the result is the same. However,
in IE, it still works as before. For issues like this, would it be better
to submit an issue on GitHub?

Thank you for XSLTForms!

Tim

--
Tim A. Thompson
Metadata Librarian (Spanish/Portuguese Specialty)
Princeton University Library

Re: [Xsltforms-support] Calling Javascript-defined functions from XForms.

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

Hello Cyril,

First, xf:load/@resource can only contains an URL. The protocol (http:, 
ftp:, ...), even if it ends with a colon, is not a namespace prefix so 
it is not possible to declare its own prefix for Javascript which is 
always javascript:. The string after "javascript:" is interpreted as 
Javascript instructions: it is not possible to directly call any XPath 
function such as instance().

On the contrary, xf:load/xf:resource/@value is always containing an 
XPath expression returning a string which has to be a valid value for 
xf:load/@resource.

As an extension, XSLTForms allows to directly call Javascript functions 
within XPath expressions, without any prefix (because, according to 
XForms 1.1 Specifications, only an XPath 1.0 engine is required). This 
is why it is possible, with XSLTForms only, to call a Javascript 
function for a setvalue action.

Finally, XSLTForms latest builds support, as a convenience, double 
quotes and double apostrophes within strings, as specified in XPath2.0+, 
instead of having to use " and '.

Please find below the modified test case:

<html
     xmlns="http://www.w3.org/1999/xhtml"
     xmlns:xf="http://www.w3.org/2002/xforms"
     xmlns:xsd="http://www.w3.org/2001/XMLSchema"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xmlns:ev="http://www.w3.org/2001/xml-events">
     <head>
         <title>Test News</title>
         <script type="text/javascript">
             function intMyAlert(str) {
                 alert(str);
                 return 1;
             }
         </script>
         <xf:model id="mdlMyModel">
             <xf:instance id="itcMyInstance">
                 <data xmlns="">
                     <text>My Instance Text</text>
                     <dump/>
                 </data>
             </xf:instance>
         </xf:model>
     </head>
     <body>
         <h3>Load Javascript Test</h3>
         <div>
             <p>Test 1 :
                 <xf:trigger>
                     <xf:label>Alert()</xf:label>
                     <xf:action ev:event="DOMActivate">
                         <xf:load resource="javascript:alert('Hello 
World!')" />
                     </xf:action>
                 </xf:trigger>
             </p>
             <!--
             <p>Test 2 :
                 <xf:trigger>
                     <xf:label>Alert() + namespace 'js'</xf:label>
                     <xf:action ev:event="DOMActivate">
                         <xf:load resource="js:alert('Hello World!')" />
                     </xf:action>
                 </xf:trigger>
             </p>
             -->
             <p>Test 3 :
                 <xf:trigger>
                     <xf:label>Alert() + resource value</xf:label>
                     <xf:action ev:event="DOMActivate">
                         <xf:load>
                            <xf:resource 
value="'javascript:alert(''Hello World!'')'"/>
                         </xf:load>
                     </xf:action>
                 </xf:trigger>
             </p>

             <p>Test 4 :
                 <xf:trigger>
                     <xf:label>Alert() + instance text</xf:label>
                     <xf:action ev:event="DOMActivate">
                         <xf:load>
                            <xf:resource 
value="concat('javascript:alert(''',instance('itcMyInstance')/text,''')')"/>
                         </xf:load>
                     </xf:action>
                 </xf:trigger>
             </p>

             <p/>
             <h3>Setvalue Javascript Test</h3>
             <xf:trigger>
                 <xf:label>Function + instance text + setvalue</xf:label>
                 <xf:action ev:event="DOMActivate">
                     <xf:setvalue ref="instance('itcMyInstance')/dump" 
value="intMyAlert(instance('itcMyInstance')/text)"/>
                 </xf:action>
             </xf:trigger>
         </div>
     </body>
</html>

What do you think?

--Alain

> Hello,
>
> I'm trying to use the load element with a javascript function, to do
> things like changing the page title or the anchor dynamically, and
> there's some strange problems. I managed to do it with the setvalue
> element though, but I don't know if it's a correct way to do it with
> xforms or if it's just working with Xsltforms.
>
> Here is the code :
>> <?xml version="1.0" encoding="UTF-8"?>
>> <?xml-stylesheet href="xsltforms/xsltforms.xsl" type="text/xsl"?>
>> <html
>>      xmlns="http://www.w3.org/1999/xhtml"
>>      xmlns:xf="http://www.w3.org/2002/xforms"
>>      xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>>      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>      xmlns:ev="http://www.w3.org/2001/xml-events"
>>      xmlns:js="javascript:code">
>>      <head>
>>          <title>Test News</title>
>>          <script type="text/javascript">
>>              function intMyAlert(str) {
>>                  alert(str);
>>                  return 1;
>>              }
>>          </script>
>>          <xf:model id="mdlMyModel">
>>
>>              <xf:instance id="itcMyInstance">
>>                  <data xmlns="">
>>                      <text>My Instance Text</text>
>>                      <dump/>
>>                  </data>
>>              </xf:instance>
>>          </xf:model>
>>      </head>
>>      <body>
>>          <h3>Load Javascript Test</h3>
>>          <div>
>>              <p>Test 1 :
>>                  <xf:trigger>
>>                      <xf:label>Alert()</xf:label>
>>                      <xf:action ev:event="DOMActivate">
>>                          <xf:load resource="javascript:alert('Hello
>> World !')" />
>>                      </xf:action>
>>                  </xf:trigger>
>>              </p>
>>
>>              <p>Test 2 :
>>                  <xf:trigger>
>>                      <xf:label>Alert() + namespace 'js'</xf:label>
>>                      <xf:action ev:event="DOMActivate">
>>                          <xf:load resource="js:alert('Hello World !')" />
>>                      </xf:action>
>>                  </xf:trigger>
>>              </p>
>>
>>              <p>Test 3 :
>>                  <xf:trigger>
>>                      <xf:label>Alert() + resource value</xf:label>
>>                      <xf:action ev:event="DOMActivate">
>>                          <xf:load>
>>                             <xf:resource value="js:alert('Hello World
>> !')"/>
>>                          </xf:load>
>>                      </xf:action>
>>                  </xf:trigger>
>>              </p>
>>
>>              <p>Test 4 :
>>                  <xf:trigger>
>>                      <xf:label>Alert() + instance text</xf:label>
>>                      <xf:action ev:event="DOMActivate">
>>                          <xf:load
>> resource="javascript:alert(instance('itcMyInstance')/text)" />
>>                      </xf:action>
>>                  </xf:trigger>
>>              </p>
>>
>>              <p/>
>>              <h3>Setvalue Javascript Test</h3>
>>              <xf:trigger>
>>                  <xf:label>Function + instance text + setvalue</xf:label>
>>                  <xf:action ev:event="DOMActivate">
>>                      <xf:setvalue  ref="instance('itcMyInstance')/dump"
>>   value="js:intMyAlert(instance('itcMyInstance')/text)"/>
>>                  </xf:action>
>>              </xf:trigger>
>>          </div>
>>      </body>
>> </html>
> With Test 2 in think the new namespace for javascript is not recognized
> and Test 3 load the script but then tries to load the page « Hello World
> ! ». With Test 4 there's a XSLTForms Exception : « instance is not
> defined ».
>
> Regards,
> Cyril.
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support

Re: [Xsltforms-support] Calling Javascript-defined functions from XForms.

[Cyril <sfg...@fr...>]

Hello,

I'm trying to use the load element with a javascript function, to do 
things like changing the page title or the anchor dynamically, and 
there's some strange problems. I managed to do it with the setvalue 
element though, but I don't know if it's a correct way to do it with 
xforms or if it's just working with Xsltforms.

Here is the code :
> <?xml version="1.0" encoding="UTF-8"?>
> <?xml-stylesheet href="xsltforms/xsltforms.xsl" type="text/xsl"?>
> <html
>     xmlns="http://www.w3.org/1999/xhtml"
>     xmlns:xf="http://www.w3.org/2002/xforms"
>     xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>     xmlns:ev="http://www.w3.org/2001/xml-events"
>     xmlns:js="javascript:code">
>     <head>
>         <title>Test News</title>
>         <script type="text/javascript">
>             function intMyAlert(str) {
>                 alert(str);
>                 return 1;
>             }
>         </script>
>         <xf:model id="mdlMyModel">
>
>             <xf:instance id="itcMyInstance">
>                 <data xmlns="">
>                     <text>My Instance Text</text>
>                     <dump/>
>                 </data>
>             </xf:instance>
>         </xf:model>
>     </head>
>     <body>
>         <h3>Load Javascript Test</h3>
>         <div>
>             <p>Test 1 :
>                 <xf:trigger>
>                     <xf:label>Alert()</xf:label>
>                     <xf:action ev:event="DOMActivate">
>                         <xf:load resource="javascript:alert('Hello 
> World !')" />
>                     </xf:action>
>                 </xf:trigger>
>             </p>
>
>             <p>Test 2 :
>                 <xf:trigger>
>                     <xf:label>Alert() + namespace 'js'</xf:label>
>                     <xf:action ev:event="DOMActivate">
>                         <xf:load resource="js:alert('Hello World !')" />
>                     </xf:action>
>                 </xf:trigger>
>             </p>
>
>             <p>Test 3 :
>                 <xf:trigger>
>                     <xf:label>Alert() + resource value</xf:label>
>                     <xf:action ev:event="DOMActivate">
>                         <xf:load>
>                            <xf:resource value="js:alert('Hello World 
> !')"/>
>                         </xf:load>
>                     </xf:action>
>                 </xf:trigger>
>             </p>
>
>             <p>Test 4 :
>                 <xf:trigger>
>                     <xf:label>Alert() + instance text</xf:label>
>                     <xf:action ev:event="DOMActivate">
>                         <xf:load 
> resource="javascript:alert(instance('itcMyInstance')/text)" />
>                     </xf:action>
>                 </xf:trigger>
>             </p>
>
>             <p/>
>             <h3>Setvalue Javascript Test</h3>
>             <xf:trigger>
>                 <xf:label>Function + instance text + setvalue</xf:label>
>                 <xf:action ev:event="DOMActivate">
>                     <xf:setvalue  ref="instance('itcMyInstance')/dump"
>  value="js:intMyAlert(instance('itcMyInstance')/text)"/>
>                 </xf:action>
>             </xf:trigger>
>         </div>
>     </body>
> </html>

With Test 2 in think the new namespace for javascript is not recognized 
and Test 3 load the script but then tries to load the page « Hello World 
! ». With Test 4 there's a XSLTForms Exception : « instance is not 
defined ».

Regards,
Cyril.

Re: [Xsltforms-support] Cascading Dynamic Dropboxes (xf:select1). existdb templating framework

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

Hello!

For populating the first select1, I guess that this code snippet will 
create a div element within the select1 element. This will not work with 
regular XForms engines. I would suggest to generate all the XForms 
control with the template instead of just the minimal chunk. Actually, 
it would be more in XForms approach to generate an instance and use 
itemset within the select1 control.

For cascading dropboxes, for which XForms is naturally well designed, 
XForms bindings allow to specify conditions in between with XPath 
expressions. When an AJAX processing is required, again, XForms 
instances are well suited and XForms submissions are easy to manipulate.

What do you think?

--Alain

Le 18/06/2015 12:42, Дмитрий Сураев a écrit :
>
> Hello everyone!
>
> I'm working with existdb XForm and its HTML Templating Module (xquery logic)
> Trying to make two cascaded dropboxes:
>
>     I. 1-st one loads data from database at XForm loading:
>
>         <xf:select1 ref="Region" selection="open" appearance="minimal" incremental="true">
>              <xf:label>Region: </xf:label>
>              <div data-template="app:get_regions"/>
>            </xf:select1>
>
>
>                   xquery  function "get_regions" in app module forms xf:item then processing XForm:
>
>                                               declare
>
>                                               function app:get_regions($node as node(), $model as map(*)) {
>                                                   let $connection := sql:get-connection('oracle.jdbc.OracleDriver', 'my conn string')
>
>                                                   let $q1 := "select distinct RG from ds8test.VLANMAP_64 where mr = 'FE' and rg not like ' ' order by rg"
>
>                                                       let $qry := sql:execute( $connection, $q1, fn:true())
>
>                                                           let $result := for $row at $pos in $qry//sql:row
>                                                                       let $rg := $row/sql:RG/text()
>                                                                           return
>                                                                           <xf:item>
>                                                                               <xf:label>{$rg}</xf:label>
>                                                                               <xf:value>{$rg}</xf:value>
>                                                                           </xf:item>
>                                                   return $result
>                                               };
>
>
>     II. The second dropbox should be populated with values, when any option is selected in dropbox 1
>
>
> Is it possible to do this by means of xquery functions? Or how should I do?
>
> Thank you!
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

Re: [Xsltforms-support] xsd:list

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

Hello Michel,

I have now committed a new XSLTForms build which includes xsd:list fixes 
and support for xsd:include and fn:tokenize.

Please find below the testcase you sent with some modifications:

<html xmlns:xf  ="http://www.w3.org/2002/xforms"
       xmlns:fn  ="http://www.w3.org/2005/xpath-functions"
       xmlns="http://www.w3.org/1999/xhtml"
       xmlns:ev  ="http://www.w3.org/2001/xml-events"
       xmlns:xs  ="http://www.w3.org/2001/XMLSchema"
       xmlns:xsi ="http://www.w3.org/2001/XMLSchema-instance"
       xmlns:ns1 ="http://www.exemple.com/my_namespace" ns1:dummy="dummy">
<head>
<title>simpleType list</title>
<xf:model >
     <xf:instance>
         <data xmlns="">
             <counts>1 6 2 33 91 250</counts>
         </data>
     </xf:instance>
     <xs:schema targetNamespace="http://www.exemple.com/my_namespace">
         <xs:include schemaLocation="listOfInts.xsd"/>
     </xs:schema>
     <xf:bind ref="counts" type="ns1:listOfInts"/>
</xf:model>
</head>
<body>
     <p>Testing simpleType list</p>
     <xf:input ref="counts">
         <xf:label>Input counts:</xf:label>
         <xf:hint>list of integers separated by white space</xf:hint>
     </xf:input>
     <br/>
     <br/>
     <br/>
     <xf:output ref="counts">
         <xf:label>Output counts:</xf:label>
     </xf:output>
     <br/>
     <br/>
     <p>Trying more...</p>
     <ul>
         <xf:repeat ref="tokenize(counts,'\s+')">
             <li><xf:output ref="."/></li>
         </xf:repeat>
     </ul>
</body>
</html>

It has been successfully tested at client-side with both Firefox (I 
added the required workaround "ns:dummy" for namespaces only used in 
values) , IE11 and Chrome.

Thank you for your feedback!

--Alain

Le 18/06/2015 21:45, Alain Couthures a écrit :
> Hello Michel,
>
> Obviously, the source code for xsd:list, inherited from AJAXForms, had 
> never been tested before...
>
> I have fixed it now and, before committing a new build on repositories 
> (Github and SF.net), I am wondering what you will need to manipulate 
> lists: currently, XSLTForms is XForms 1.1 compliant which means that 
> only XPath 1.0 is available (no sequence, no type,...).
>
> XSLTForms already includes some XForms 2.0 features and some XPath 2.0 
> functions. I am now working at full XPath 3.1 support for XSLTForms 2.0!
>
> In the meantime, to add support for fn:tokenize(), for example, in 
> XSLTForms 1.0, I can use a trick which would return a nodeset instead 
> of a sequence.
>
> So, could you please tell me which functions you would need to process 
> lists?
>
> Thanks!
>
> --Alain
>
> Le 17/06/2015 23:49, Michel Kruglanski a écrit :
>> Dear Alain,
>>
>> Please find an illustration in attachment.
>>
>> Best regards
>>
>> Michel K.
>>
>> On 17/06/2015 21:37, COUTHURES Alain wrote:
>>> Hello again,
>>>
>>> This error sounds like an issue. Could you please send me a small
>>> testcase so I can quickly locate this issue?
>>>
>>> Thanks in advance!
>>>
>>> Alain Couthures
>>>
>>> Le 17/06/2015 12:49, Michel Kruglanski a écrit :
>>>> Hi,
>>>>
>>>> It seems that the handling of data types defined as list of values is
>>>> not working properly inside XSLTFORMS.
>>>>
>>>> Including data type such as
>>>>
>>>> <xsd:simpleType><xsd:list itemType="xsd:integer"/></xsd:simpleType>
>>>>
>>>> is generating an error in xsltforms/xsltforms.js on a missing property
>>>> "baseType" for the class XsltForms_listType.
>>>>
>>>> Could you confirm this shortcoming and suggest a workaround?
>>>>
>>>> Thank you in advance.
>>>>
>>>> Best regards
>>>>
>>>> Michel Kruglanski
>>>> -- 
>>>> Belgian Institute for Space Aeronomy
>>>>
>>>> ------------------------------------------------------------------------------ 
>>>>
>>>> _______________________________________________
>>>> Xsltforms-support mailing list
>>>> Xsl...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>>>
>>>
>>> ------------------------------------------------------------------------------ 
>>>
>>> _______________________________________________
>>> Xsltforms-support mailing list
>>> Xsl...@li...
>>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>
>>
>>
>> ------------------------------------------------------------------------------
>>
>>
>> _______________________________________________
>> Xsltforms-support mailing list
>> Xsl...@li...
>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
>
>
> ------------------------------------------------------------------------------
>
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support

Re: [Xsltforms-support] xsd:list

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

Hello Michel,

Obviously, the source code for xsd:list, inherited from AJAXForms, had 
never been tested before...

I have fixed it now and, before committing a new build on repositories 
(Github and SF.net), I am wondering what you will need to manipulate 
lists: currently, XSLTForms is XForms 1.1 compliant which means that 
only XPath 1.0 is available (no sequence, no type,...).

XSLTForms already includes some XForms 2.0 features and some XPath 2.0 
functions. I am now working at full XPath 3.1 support for XSLTForms 2.0!

In the meantime, to add support for fn:tokenize(), for example, in 
XSLTForms 1.0, I can use a trick which would return a nodeset instead of 
a sequence.

So, could you please tell me which functions you would need to process 
lists?

Thanks!

--Alain

Le 17/06/2015 23:49, Michel Kruglanski a écrit :
> Dear Alain,
>
> Please find an illustration in attachment.
>
> Best regards
>
> Michel K.
>
> On 17/06/2015 21:37, COUTHURES Alain wrote:
>> Hello again,
>>
>> This error sounds like an issue. Could you please send me a small
>> testcase so I can quickly locate this issue?
>>
>> Thanks in advance!
>>
>> Alain Couthures
>>
>> Le 17/06/2015 12:49, Michel Kruglanski a écrit :
>>> Hi,
>>>
>>> It seems that the handling of data types defined as list of values is
>>> not working properly inside XSLTFORMS.
>>>
>>> Including data type such as
>>>
>>> <xsd:simpleType><xsd:list itemType="xsd:integer"/></xsd:simpleType>
>>>
>>> is generating an error in xsltforms/xsltforms.js on a missing property
>>> "baseType" for the class XsltForms_listType.
>>>
>>> Could you confirm this shortcoming and suggest a workaround?
>>>
>>> Thank you in advance.
>>>
>>> Best regards
>>>
>>> Michel Kruglanski
>>> -- 
>>> Belgian Institute for Space Aeronomy
>>>
>>> ------------------------------------------------------------------------------ 
>>>
>>> _______________________________________________
>>> Xsltforms-support mailing list
>>> Xsl...@li...
>>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>>
>>
>> ------------------------------------------------------------------------------ 
>>
>> _______________________________________________
>> Xsltforms-support mailing list
>> Xsl...@li...
>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
>
>
> ------------------------------------------------------------------------------
>
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support

[Xsltforms-support] Cascading Dynamic Dropboxes (xf:select1). existdb templating framework

[Дмитрий С. <di...@ra...>]

Hello everyone!

I'm working with existdb XForm and its HTML Templating Module (xquery logic)
Trying to make two cascaded dropboxes:

   I. 1-st one loads data from database at XForm loading:

       <xf:select1 ref="Region" selection="open" appearance="minimal" incremental="true">
            <xf:label>Region: </xf:label>
            <div data-template="app:get_regions"/>
          </xf:select1>


                 xquery  function "get_regions" in app module forms xf:item then processing XForm:

                                             declare 

                                             function app:get_regions($node as node(), $model as map(*)) {
                                                 let $connection := sql:get-connection('oracle.jdbc.OracleDriver', 'my conn string') 

                                                 let $q1 := "select distinct RG from ds8test.VLANMAP_64 where mr = 'FE' and rg not like ' ' order by rg"

                                                     let $qry := sql:execute( $connection, $q1, fn:true())

                                                         let $result := for $row at $pos in $qry//sql:row
                                                                     let $rg := $row/sql:RG/text()
                                                                         return
                                                                         <xf:item>
                                                                             <xf:label>{$rg}</xf:label>
                                                                             <xf:value>{$rg}</xf:value>
                                                                         </xf:item>
                                                 return $result
                                             };


   II. The second dropbox should be populated with values, when any option is selected in dropbox 1


Is it possible to do this by means of xquery functions? Or how should I do?

Thank you!

Re: [Xsltforms-support] xsd:list

[Michel K. <mic...@ae...>]

Dear Alain,

Please find an illustration in attachment.

Best regards

Michel K.

On 17/06/2015 21:37, COUTHURES Alain wrote:
> Hello again,
>
> This error sounds like an issue. Could you please send me a small
> testcase so I can quickly locate this issue?
>
> Thanks in advance!
>
> Alain Couthures
>
> Le 17/06/2015 12:49, Michel Kruglanski a écrit :
>> Hi,
>>
>> It seems that the handling of data types defined as list of values is
>> not working properly inside XSLTFORMS.
>>
>> Including data type such as
>>
>> <xsd:simpleType><xsd:list itemType="xsd:integer"/></xsd:simpleType>
>>
>> is generating an error in xsltforms/xsltforms.js on a missing property
>> "baseType" for the class XsltForms_listType.
>>
>> Could you confirm this shortcoming and suggest a workaround?
>>
>> Thank you in advance.
>>
>> Best regards
>>
>> Michel Kruglanski
>> --
>> Belgian Institute for Space Aeronomy
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Xsltforms-support mailing list
>> Xsl...@li...
>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support

Re: [Xsltforms-support] xsd:list

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

Hello again,

This error sounds like an issue. Could you please send me a small 
testcase so I can quickly locate this issue?

Thanks in advance!

Alain Couthures

Le 17/06/2015 12:49, Michel Kruglanski a écrit :
> Hi,
>
> It seems that the handling of data types defined as list of values is
> not working properly inside XSLTFORMS.
>
> Including data type such as
>
> <xsd:simpleType><xsd:list itemType="xsd:integer"/></xsd:simpleType>
>
> is generating an error in xsltforms/xsltforms.js on a missing property
> "baseType" for the class XsltForms_listType.
>
> Could you confirm this shortcoming and suggest a workaround?
>
> Thank you in advance.
>
> Best regards
>
> Michel Kruglanski
> --
> Belgian Institute for Space Aeronomy
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

Re: [Xsltforms-support] xsd:include

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

Hello Michel,

Currently, XSLTForms is just looking at xsd:simpleType elements.

Adding xsd:include support in XSLTForms does not seem difficult within 
the XSLT stylesheet but some browsers don't allow document() function 
calls anymore... Are you applying the XSLT stylesheet at server-side??

BTW, are you just evaluating XSLTForms or are you integrating XSLTForms 
in an effective project? When would you require this new feature?

Thanks!

Alain Couthures

Le 17/06/2015 12:40, Michel Kruglanski a écrit :
> Hi,
>
> I have the impression that xsd:include elements are ignored by XSLTFORMS.
>
> Could you confirm this statement and suggest a possible workaround?
>
> Thank you in advance.
>
> Best regards
>
> Michel Kruglanski
> --
> Belgian Institute for Space Aeronomy
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

[Xsltforms-support] xsd:list

[Michel K. <mic...@ae...>]

Hi,

It seems that the handling of data types defined as list of values is 
not working properly inside XSLTFORMS.

Including data type such as

<xsd:simpleType><xsd:list itemType="xsd:integer"/></xsd:simpleType>

is generating an error in xsltforms/xsltforms.js on a missing property 
"baseType" for the class XsltForms_listType.

Could you confirm this shortcoming and suggest a workaround?

Thank you in advance.

Best regards

Michel Kruglanski
--
Belgian Institute for Space Aeronomy

[Xsltforms-support] xsd:include

[Michel K. <mic...@ae...>]

Hi,

I have the impression that xsd:include elements are ignored by XSLTFORMS.

Could you confirm this statement and suggest a possible workaround?

Thank you in advance.

Best regards

Michel Kruglanski
--
Belgian Institute for Space Aeronomy

Re: [Xsltforms-support] Support for javascript: pseudo-URLs in IE

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

Hello Tim,

Could you please post a minimal test case to illustrate this issue?

Thanks!

--Alain

Le 05/06/2015 03:10, Tim Thompson a écrit :
> Update: in IE 10 and 11 (Windows 7), if I wrap the pseudo-URL 
> expression in an array, a function constructor, or an anonymous 
> function, the browser seems to evaluate it successfully, but still 
> throws a (different) error: "Bad URI value, no scheme: undefined."
>
> Other than pseudo-URLs, how can I execute a JavaScript function from a 
> subform once it has loaded? I tried loading the subform with a trigger 
> and attaching an event listener to the trigger, and this also works in 
> Firefox and Chrome, but not IE.
>
> Thanks,
> Tim
>
> On Thu, Jun 4, 2015 at 4:18 PM, Tim Thompson <tim...@gm... 
> <mailto:tim...@gm...>> wrote:
>
>     Hello,
>
>     I am using subforms to build a single-page-style app in XSLTForms.
>     So far, this seems like a very flexible and powerful design
>     pattern. I have a main form with a nav bar that links to different
>     subforms to populate the page body. When a subform is ready (once
>     the "xforms-subform-ready" event fires in the subform), I need to
>     load a bit of JavaScript to pull in a couple of other libraries I
>     am using. I can do this with an XSLTForms javascript: pseudo-URL
>     on the xf:load element, and it works perfectly in Firefox and Chrome.
>
>     However, in IE 11 (have not tested other versions), the browser
>     cannot parse the pseudo-URL, and the app fails to load. I get an
>     XSLTForms Exception error stating, "Error evaluating the following
>     Javascript expression."
>
>     Is it possible to support pseudo-URLs in IE?
>
>     Thanks so much,
>     Tim
>
>
>
>
> ------------------------------------------------------------------------------
>
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support

Re: [Xsltforms-support] Support for javascript: pseudo-URLs in IE

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

Update: in IE 10 and 11 (Windows 7), if I wrap the pseudo-URL expression in
an array, a function constructor, or an anonymous function, the browser
seems to evaluate it successfully, but still throws a (different) error:
"Bad URI value, no scheme: undefined."

Other than pseudo-URLs, how can I execute a JavaScript function from a
subform once it has loaded? I tried loading the subform with a trigger and
attaching an event listener to the trigger, and this also works in Firefox
and Chrome, but not IE.

Thanks,
Tim

On Thu, Jun 4, 2015 at 4:18 PM, Tim Thompson <tim...@gm...> wrote:

> Hello,
>
> I am using subforms to build a single-page-style app in XSLTForms. So far,
> this seems like a very flexible and powerful design pattern. I have a main
> form with a nav bar that links to different subforms to populate the page
> body. When a subform is ready (once the "xforms-subform-ready" event fires
> in the subform), I need to load a bit of JavaScript to pull in a couple of
> other libraries I am using. I can do this with an XSLTForms javascript:
> pseudo-URL on the xf:load element, and it works perfectly in Firefox and
> Chrome.
>
> However, in IE 11 (have not tested other versions), the browser cannot
> parse the pseudo-URL, and the app fails to load. I get an XSLTForms
> Exception error stating, "Error evaluating the following Javascript
> expression."
>
> Is it possible to support pseudo-URLs in IE?
>
> Thanks so much,
> Tim
>

[Xsltforms-support] Support for javascript: pseudo-URLs in IE

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

Hello,

I am using subforms to build a single-page-style app in XSLTForms. So far,
this seems like a very flexible and powerful design pattern. I have a main
form with a nav bar that links to different subforms to populate the page
body. When a subform is ready (once the "xforms-subform-ready" event fires
in the subform), I need to load a bit of JavaScript to pull in a couple of
other libraries I am using. I can do this with an XSLTForms javascript:
pseudo-URL on the xf:load element, and it works perfectly in Firefox and
Chrome.

However, in IE 11 (have not tested other versions), the browser cannot
parse the pseudo-URL, and the app fails to load. I get an XSLTForms
Exception error stating, "Error evaluating the following Javascript
expression."

Is it possible to support pseudo-URLs in IE?

Thanks so much,
Tim