xsltforms-support — XSLTForms support list

Re: [Xsltforms-support] Adding optional elements to an XML document

[Ihe O. <ihe...@go...>]

In your position I would explore using xsd:all instead of xsd:sequence
so that the elements can appear in any order in the instance or switch
to a relax schema or xsd 1.1 and use interleave.

Operative word in the above being explore. Someone who has tried it
may advise otherwise.


On Tue, Jun 5, 2012 at 10:21 AM, sores <so...@al...> wrote:
> Hi All,
>
> When inserting new elements into an empty repeat the context attribute
> has to be used to define the insert location. By default the inserted
> element will be positioned after the last child of the context nodeset.
> Is there a way to control this behaviour?
> (for example an axis xpath attribute somewhere that would define the
> insertion point in the context node)
>
> I am trying to build web interfaces for fairly complex XSD schema
> defined objects with lots of optional elements. In an XML instance these
> optional elements may not be present. When someone starts to add them
> they appeare in a wrong location and make XSD validation fail. Having
> empty optional elements in the XML instances would work, but | wanted to
> avoid this.
>
> An easy way to solve the problem is reordering the elements with an xsl
> transformation. Before doing so I would like to know if I am missing
> something obvious.
>
> Best regards,
>
> László Sőrés
>
>
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support

[Xsltforms-support] Adding optional elements to an XML document

[sores <so...@al...>]

Hi All,

When inserting new elements into an empty repeat the context attribute 
has to be used to define the insert location. By default the inserted 
element will be positioned after the last child of the context nodeset. 
Is there a way to control this behaviour?
(for example an axis xpath attribute somewhere that would define the 
insertion point in the context node)

I am trying to build web interfaces for fairly complex XSD schema 
defined objects with lots of optional elements. In an XML instance these 
optional elements may not be present. When someone starts to add them 
they appeare in a wrong location and make XSD validation fail. Having 
empty optional elements in the XML instances would work, but | wanted to 
avoid this.

An easy way to solve the problem is reordering the elements with an xsl 
transformation. Before doing so I would like to know if I am missing 
something obvious.

Best regards,

László Sőrés

[Xsltforms-support] Inserting into empty node set

[sores <so...@al...>]

Dear All,

Is there any way to control the insert location within a parent node 
set given by the context attribute? I am trying to insert elements into 
an empty repeat. Elements are inserted after the last child of the 
context node set, but I need them somewhere else for validation.
Please, see the XForms file attached. Example:

instance data:

<root>
<ch1/>
<ch2/>
<ch4/>
</root>

output after editing:

<root>
<ch1>aa</ch1>
<ch2>bb</ch2>
<ch4>dd</ch4>
<ch3>cc1</ch3>
<ch3>cc2</ch3>
</root>

I would prefer the output like this:

<root>
<ch1>aa</ch1>
<ch2>bb</ch2>
<ch3>cc1</ch3>
<ch3>cc2</ch3>
<ch4>dd</ch4>
</root>

If input contains <c3/> elements at the right location, it works fine.
Any help would be appreciated.

Regards,
Laszlo Sores

[Xsltforms-support] event cascading

[Stephen C. <ste...@gm...>]

Hi,

I have a table that contains rows created via an xf:repeat, in each row is
a xf:trigger that doesn't occupy the whole row.

If the user clicks on a row, but not the trigger in the row, then only the
repeat index changes. Conversely if the trigger is clicked in a row then
the repeat index changes as well, so it seems the DOMActivate event is
cascading up but not down the DOM (sounds logical).

Is there a standard way to get a xf node to observe an ancestor and respond
to events in the ancestor node?

Thanks

Steve Cameron

Re: [Xsltforms-support] Xsltforms-support Digest, Vol 36, Issue 6

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

Hi Sree,

You should have a look at this example: 
http://www.agencexml.com/xsltforms/address.xml

xf:itext support is not inherited from XForms Specification but from 
JavaRosa implementation.

Thank you for your feedbacks!

-Alain

Le 28/05/2012 12:06, srividhya a écrit :
> Hi All!!!!!
>
>     I want to know about the international support in xsltforms. for 
> example i have a field called "Name" in that  the user has to enter 
> either in english or hindi. How to do that one? any sample code is 
> there means greatly help.
>
> with thanks,
> sree
>

Re: [Xsltforms-support] Xsltforms-support Digest, Vol 36, Issue 6

[Ihe O. <ihe...@go...>]

It's not part of XSLTForms rather, it's something you build into your xform

http://xformsinstitute.com/essentials/browse/book.php#ch10-8-fm2xml

On Mon, May 28, 2012 at 11:06 AM, srividhya <n.s...@ni...> wrote:
> Hi All!!!!!
>
>     I want to know about the international support in xsltforms. for example
> i have a field called "Name" in that  the user has to enter either in
> english or hindi. How to do that one? any sample code is there means greatly
> help.
>
> with thanks,
> sree
>
>
> On 05/27/12, xsl...@li... wrote:
>
> Send Xsltforms-support mailing list submissions to
> xsl...@li...
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
> or, via email, send a message with subject or body 'help' to
> xsl...@li...
>
> You can reach the person managing the list at
> xsl...@li...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Xsltforms-support digest..."
>
>
> Today's Topics:
>
>    1. Submission - method = put not saving to xml file (Ihe Onwuka)
>    2. Binding to the absence of a node (Chimezie Ogbuji)
>    3. Re: Submission - method = put not saving to xml file
>       (Dan McCreary)
>    4. Re: Binding to the absence of a node (Chimezie Ogbuji)
>    5. behaviour of choices and the appearance attribute (Ihe Onwuka)
>    6. Regression after switching to XQuery generation (Ihe Onwuka)
>    7. Re: Regression after switching to XQuery generation (Ihe Onwuka)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 24 May 2012 08:23:28 +0100
> From: Ihe Onwuka <ihe...@go...>
> Subject: [Xsltforms-support] Submission - method = put not saving to
> xml file
> To: xsl...@li...
> Message-ID:
> <CAL...@ma...>
> Content-Type: text/plain; charset=ISO-8859-1
>
> In my model I have   <xf:submission id="submitSales" method="put"
> action="sales.xml" ref="b2b:Sales"/>.
>
> In my view I have
>
>         <xf:submit submission="submitSales">
>            <xf:label>Save</xf:label>
>         </xf:submit>
>
> but the model does not overwrite the sales.xml file when I click Save.
>
> Also earlier I mistakenly used the wrong IDRef (as in non-existent in
> the submission attribute of <xf:submit>.
>
> The form displayed the loading box and didn't do anything.
>
> Perhaps there should be some sort of exception, better than looking
> like it is going to do something but then not.
>
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 24 May 2012 08:07:02 -0400
> From: Chimezie Ogbuji <chi...@gm...>
> Subject: [Xsltforms-support] Binding to the absence of a node
> To: xsl...@li...
> Message-ID:
> <CAKSO3u=F24...@ma...>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hello, I'm trying to support a situation where a group of controls (or
> a single control) appear only if another node in the same instance
> document does not appear.  When I was using XForms extension for
> Firefox in the past, I was able to do it this way:
>
>
>                             <xforms:group
> ref="current()[not(AbsentElement)]">
>                                 <xforms:trigger>
>                                     <xforms:label>Add Skilled response
> section</xforms:label>
>                                     .. action to add AbsentElement to
> context..
>                                 </xforms:trigger>
>                             </xforms:group>
>
> The general idea is to only show a trigger if AbsentElement is not a
> child of the current context, which will add that element if clicked.
> However, I get the following exception
>
> XSLTForms Exception
> --------------------------
>
> Error parsing the following XPath expression :
>
> current()[not(AbsentElement)]
>
> Unknown operator at '[not(AbsentElement)]' in
> 'current()[not(AbsentElement)]'
>
> Can this be done in XSLTForms?
>
> Thanks.
>
> -- Chime
>
>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 24 May 2012 08:37:28 -0500
> From: Dan McCreary <dan...@gm...>
> Subject: Re: [Xsltforms-support] Submission - method = put not saving
> to xml file
> To: Ihe Onwuka <ihe...@go...>
> Cc: xsl...@li...
> Message-ID:
> <CAO...@ma...>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hello Ine,
>
> Although PUT will work under some circumstances (where you have write
> access) I think that using HTTP POST to a "save.xq" script will be much
> more reliable since there are many triggers you can add at the save point.
> You can also use "update.xq" in the same way.
>
> There are examples of this here:
>
> http://www.danmccreary.com/xrx/beginners-guide/beginners-guide-to-xrx.xhtml#d0e862
>
> - Dan
>
> On Thu, May 24, 2012 at 2:23 AM, Ihe Onwuka
> <ihe...@go...>wrote:
>
>> In my model I have   <xf:submission id="submitSales" method="put"
>> action="sales.xml" ref="b2b:Sales"/>.
>>
>> In my view I have
>>
>>        <xf:submit submission="submitSales">
>>           <xf:label>Save</xf:label>
>>        </xf:submit>
>>
>> but the model does not overwrite the sales.xml file when I click Save.
>>
>> Also earlier I mistakenly used the wrong IDRef (as in non-existent in
>> the submission attribute of <xf:submit>.
>>
>> The form displayed the loading box and didn't do anything.
>>
>> Perhaps there should be some sort of exception, better than looking
>> like it is going to do something but then not.
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Xsltforms-support mailing list
>> Xsl...@li...
>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>
>
>
>
> --
> Dan McCreary
> NoSQL Evangelist
> office: (952) 931-9198
> cell: (612) 986-1552
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 4
> Date: Thu, 24 May 2012 11:47:29 -0400
> From: Chimezie Ogbuji <chi...@gm...>
> Subject: Re: [Xsltforms-support] Binding to the absence of a node
> To: da...@da...
> Cc: xsl...@li...
> Message-ID:
> <CAKSO3unwLWi_5JKXW=8a109khj1xDeVhY+Nw-w6YM51=G6...@ma...>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hello, Dan (CC'ed support list).  Thanks for the suggestion.
>
> I was eventually able to get it to work via:
>
>                                 <xforms:group
> ref=".[not(AbsentElement)]">
>                                     <xforms:trigger>
>                                         <xforms:label>Add absent
> element</xforms:label>
>                                         ... action ..
>                                     </xforms:trigger>
>                                 </xforms:group>
>
>
> On Thu, May 24, 2012 at 10:03 AM, Dan McCreary <dan...@gm...>
> wrote:
>> Hello Chimezie,
>>
>> I have done this but I recall I just used the simpler following notation:
>>
>> <xforms:group ref="not(AbsentElement)">
>>
>> or perhaps
>>
>> <xforms:group ref="./not(AbsentElement)">
>>
>> Have you tried these?
>>
>> - Dan
>>
>> On Thu, May 24, 2012 at 7:07 AM, Chimezie Ogbuji <chi...@gm...>
>> wrote:
>>>
>>> Hello, I'm trying to support a situation where a group of controls (or
>>> a single control) appear only if another node in the same instance
>>> document does not appear. ?When I was using XForms extension for
>>> Firefox in the past, I was able to do it this way:
>>>
>>>
>>> ? ? ? ? ? ? ? ? ? ? ? ? ? ?<xforms:group
>>> ref="current()[not(AbsentElement)]">
>>> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?<xforms:trigger>
>>> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?<xforms:label>Add Skilled response
>>> section</xforms:label>
>>> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?.. action to add AbsentElement to
>>> context..
>>> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?</xforms:trigger>
>>> ? ? ? ? ? ? ? ? ? ? ? ? ? ?</xforms:group>
>>>
>>> The general idea is to only show a trigger if AbsentElement is not a
>>> child of the current context, which will add that element if clicked.
>>> However, I get the following exception
>>>
>>> XSLTForms Exception
>>> --------------------------
>>>
>>> Error parsing the following XPath expression :
>>>
>>> current()[not(AbsentElement)]
>>>
>>> Unknown operator at '[not(AbsentElement)]' in
>>> 'current()[not(AbsentElement)]'
>>>
>>> Can this be done in XSLTForms?
>>>
>>> Thanks.
>>>
>>> -- Chime
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Live Security Virtual Conference
>>> Exclusive live event will cover all the ways today's security and
>>> threat landscape has changed and how IT managers can respond. Discussions
>>> will include endpoint security, mobile security and the latest in malware
>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>> _______________________________________________
>>> Xsltforms-support mailing list
>>> Xsl...@li...
>>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>
>>
>>
>>
>> --
>> Dan McCreary
>> NoSQL Evangelist
>> office: (952) 931-9198
>> cell: (612) 986-1552
>
>
>
> ------------------------------
>
> Message: 5
> Date: Fri, 25 May 2012 17:24:45 +0100
> From: Ihe Onwuka <ihe...@go...>
> Subject: [Xsltforms-support] behaviour of choices and the appearance
> attribute
> To: xsl...@li...
> Message-ID:
> <CAL...@ma...>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I implemented a select1 with an xf:choice (for each language) and then an
> itemset showing the choices by language.
>
> On chrome the control only works if appearance is set to minimal or
> compact. full does not work.
>
> On firefox the control only works if appearance is set to minimal.
>
> FWIW when I say minimal I actually mean left at its defaulte setting.
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 6
> Date: Sun, 27 May 2012 10:37:05 +0100
> From: Ihe Onwuka <ihe...@go...>
> Subject: [Xsltforms-support] Regression after switching to XQuery
> generation
> To: xsl...@li...
> Message-ID:
> <CALfs7+wz6pNH0KWQLfLQc6nZ9MYFLcgWfR6=Ea2...@ma...>
> Content-Type: text/plain; charset="iso-8859-1"
>
> In order to complete developing my app I have switched to generating my
> form via XQuery (a la Beginners Guide to XRX thanks Dan).
>
> Unfortunately the form has regressed significantly (labels not rendered,
> select drop downs not populated) etc.
>
> I've checked that I have the correct paths to reference data but beyond
> that  I don't know what next to do.
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 7
> Date: Sun, 27 May 2012 13:18:29 +0100
> From: Ihe Onwuka <ihe...@go...>
> Subject: Re: [Xsltforms-support] Regression after switching to XQuery
> generation
> To: xsl...@li...
> Message-ID:
> <CALfs7+w5CapJHVpv4w65BYA1-uk=sq7...@ma...>
> Content-Type: text/plain; charset=ISO-8859-1
>
> I believe what is happening is that the form is being processed by
> betterform instead of XSLTForms even though i have followed the
> instructions and included
>
>   declare option exist:serialize "method=xhtml media-type=text/xml";
>   declare option exist:serialize "indent=no";
>   declare option exist:serialize "process-xsl-pi=no";
>
> in my xquery.
>
>
>
> On Sun, May 27, 2012 at 10:37 AM, Ihe Onwuka <ihe...@go...>
> wrote:
>>
>> In order to complete developing my app I have switched to generating my
>> form via XQuery (a la Beginners Guide to XRX thanks Dan).
>>
>> Unfortunately the form has regressed significantly (labels not rendered,
>> select drop downs not populated) etc.
>>
>> I've checked that I have the correct paths to reference data but beyond
>> that? I don't know what next to do.
>>
>>
>
>
>
> ------------------------------
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>
> ------------------------------
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
>
> End of Xsltforms-support Digest, Vol 36, Issue 6
> ************************************************
>
> --
> With thanks and Regards,
> N.Srividhya(RS-I)
> O.T.C, N.I.C,
> Chennai.
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

Re: [Xsltforms-support] Xsltforms-support Digest, Vol 36, Issue 6

[srividhya <n.s...@ni...>]

Hi All!!!!!

 I want to know about the international support in xsltforms. for example i have a field called "Name" in that the user has to enter either in english or hindi. How to do that one? any sample code is there means greatly help.

with thanks,
sree


On 05/27/12, xsl...@li... wrote:
> Send Xsltforms-support mailing list submissions to
> 	xsl...@li...
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://lists.sourceforge.net/lists/listinfo/xsltforms-support
> or, via email, send a message with subject or body 'help' to
> 	xsl...@li...
> 
> You can reach the person managing the list at
> 	xsl...@li...
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Xsltforms-support digest..."
> 
> 
> Today's Topics:
> 
>  1. Submission - method = put not saving to xml file (Ihe Onwuka)
>  2. Binding to the absence of a node (Chimezie Ogbuji)
>  3. Re: Submission - method = put not saving to xml	file
>  (Dan McCreary)
>  4. Re: Binding to the absence of a node (Chimezie Ogbuji)
>  5. behaviour of choices and the appearance	attribute (Ihe Onwuka)
>  6. Regression after switching to XQuery generation (Ihe Onwuka)
>  7. Re: Regression after switching to XQuery	generation (Ihe Onwuka)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Thu, 24 May 2012 08:23:28 +0100
> From: Ihe Onwuka <ihe...@go...>
> Subject: [Xsltforms-support] Submission - method = put not saving to
> 	xml file
> To: xsl...@li...
> Message-ID:
> 	<CAL...@ma...>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> In my model I have <xf:submission id="submitSales" method="put"
> action="sales.xml" ref="b2b:Sales"/>.
> 
> In my view I have
> 
>  <xf:submit submission="submitSales">
>  <xf:label>Save</xf:label>
>  </xf:submit>
> 
> but the model does not overwrite the sales.xml file when I click Save.
> 
> Also earlier I mistakenly used the wrong IDRef (as in non-existent in
> the submission attribute of <xf:submit>.
> 
> The form displayed the loading box and didn't do anything.
> 
> Perhaps there should be some sort of exception, better than looking
> like it is going to do something but then not.
> 
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Thu, 24 May 2012 08:07:02 -0400
> From: Chimezie Ogbuji <chi...@gm...>
> Subject: [Xsltforms-support] Binding to the absence of a node
> To: xsl...@li...
> Message-ID:
> 	<CAKSO3u=F24...@ma...>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> Hello, I'm trying to support a situation where a group of controls (or
> a single control) appear only if another node in the same instance
> document does not appear. When I was using XForms extension for
> Firefox in the past, I was able to do it this way:
> 
> 
>  <xforms:group ref="current()[not(AbsentElement)]">
>  <xforms:trigger>
>  <xforms:label>Add Skilled response
> section</xforms:label>
>  .. action to add AbsentElement to context..
>  </xforms:trigger>
>  </xforms:group>
> 
> The general idea is to only show a trigger if AbsentElement is not a
> child of the current context, which will add that element if clicked.
> However, I get the following exception
> 
> XSLTForms Exception
> --------------------------
> 
> Error parsing the following XPath expression :
> 
> current()[not(AbsentElement)]
> 
> Unknown operator at '[not(AbsentElement)]' in 'current()[not(AbsentElement)]'
> 
> Can this be done in XSLTForms?
> 
> Thanks.
> 
> -- Chime
> 
> 
> 
> ------------------------------
> 
> Message: 3
> Date: Thu, 24 May 2012 08:37:28 -0500
> From: Dan McCreary <dan...@gm...>
> Subject: Re: [Xsltforms-support] Submission - method = put not saving
> 	to xml	file
> To: Ihe Onwuka <ihe...@go...>
> Cc: xsl...@li...
> Message-ID:
> 	<CAO...@ma...>
> Content-Type: text/plain; charset="iso-8859-1"
> 
> Hello Ine,
> 
> Although PUT will work under some circumstances (where you have write
> access) I think that using HTTP POST to a "save.xq" script will be much
> more reliable since there are many triggers you can add at the save point.
> You can also use "update.xq" in the same way.
> 
> There are examples of this here:
> 
> http://www.danmccreary.com/xrx/beginners-guide/beginners-guide-to-xrx.xhtml#d0e862
> 
> - Dan
> 
> On Thu, May 24, 2012 at 2:23 AM, Ihe Onwuka <ihe...@go...>wrote:
> 
> > In my model I have <xf:submission id="submitSales" method="put"
> > action="sales.xml" ref="b2b:Sales"/>.
> >
> > In my view I have
> >
> > <xf:submit submission="submitSales">
> > <xf:label>Save</xf:label>
> > </xf:submit>
> >
> > but the model does not overwrite the sales.xml file when I click Save.
> >
> > Also earlier I mistakenly used the wrong IDRef (as in non-existent in
> > the submission attribute of <xf:submit>.
> >
> > The form displayed the loading box and didn't do anything.
> >
> > Perhaps there should be some sort of exception, better than looking
> > like it is going to do something but then not.
> >
> >
> > ------------------------------------------------------------------------------
> > Live Security Virtual Conference
> > Exclusive live event will cover all the ways today's security and
> > threat landscape has changed and how IT managers can respond. Discussions
> > will include endpoint security, mobile security and the latest in malware
> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> > _______________________________________________
> > Xsltforms-support mailing list
> > Xsl...@li...
> > https://lists.sourceforge.net/lists/listinfo/xsltforms-support
> >
> 
> 
> 
> -- 
> Dan McCreary
> NoSQL Evangelist
> office: (952) 931-9198
> cell: (612) 986-1552
> -------------- next part --------------
> An HTML attachment was scrubbed...
> 
> ------------------------------
> 
> Message: 4
> Date: Thu, 24 May 2012 11:47:29 -0400
> From: Chimezie Ogbuji <chi...@gm...>
> Subject: Re: [Xsltforms-support] Binding to the absence of a node
> To: da...@da...
> Cc: xsl...@li...
> Message-ID:
> 	<CAKSO3unwLWi_5JKXW=8a109khj1xDeVhY+Nw-w6YM51=G6...@ma...>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> Hello, Dan (CC'ed support list). Thanks for the suggestion.
> 
> I was eventually able to get it to work via:
> 
>  <xforms:group ref=".[not(AbsentElement)]">
>  <xforms:trigger>
>  <xforms:label>Add absent
> element</xforms:label>
>  ... action ..
>  </xforms:trigger>
>  </xforms:group>
> 
> 
> On Thu, May 24, 2012 at 10:03 AM, Dan McCreary <dan...@gm...> wrote:
> > Hello Chimezie,
> >
> > I have done this but I recall I just used the simpler following notation:
> >
> > <xforms:group ref="not(AbsentElement)">
> >
> > or perhaps
> >
> > <xforms:group ref="./not(AbsentElement)">
> >
> > Have you tried these?
> >
> > - Dan
> >
> > On Thu, May 24, 2012 at 7:07 AM, Chimezie Ogbuji <chi...@gm...> wrote:
> >>
> >> Hello, I'm trying to support a situation where a group of controls (or
> >> a single control) appear only if another node in the same instance
> >> document does not appear. ?When I was using XForms extension for
> >> Firefox in the past, I was able to do it this way:
> >>
> >>
> >> ? ? ? ? ? ? ? ? ? ? ? ? ? ?<xforms:group
> >> ref="current()[not(AbsentElement)]">
> >> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?<xforms:trigger>
> >> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?<xforms:label>Add Skilled response
> >> section</xforms:label>
> >> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?.. action to add AbsentElement to
> >> context..
> >> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?</xforms:trigger>
> >> ? ? ? ? ? ? ? ? ? ? ? ? ? ?</xforms:group>
> >>
> >> The general idea is to only show a trigger if AbsentElement is not a
> >> child of the current context, which will add that element if clicked.
> >> However, I get the following exception
> >>
> >> XSLTForms Exception
> >> --------------------------
> >>
> >> Error parsing the following XPath expression :
> >>
> >> current()[not(AbsentElement)]
> >>
> >> Unknown operator at '[not(AbsentElement)]' in
> >> 'current()[not(AbsentElement)]'
> >>
> >> Can this be done in XSLTForms?
> >>
> >> Thanks.
> >>
> >> -- Chime
> >>
> >>
> >> ------------------------------------------------------------------------------
> >> Live Security Virtual Conference
> >> Exclusive live event will cover all the ways today's security and
> >> threat landscape has changed and how IT managers can respond. Discussions
> >> will include endpoint security, mobile security and the latest in malware
> >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> >> _______________________________________________
> >> Xsltforms-support mailing list
> >> Xsl...@li...
> >> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
> >
> >
> >
> >
> > --
> > Dan McCreary
> > NoSQL Evangelist
> > office: (952) 931-9198
> > cell: (612) 986-1552
> 
> 
> 
> ------------------------------
> 
> Message: 5
> Date: Fri, 25 May 2012 17:24:45 +0100
> From: Ihe Onwuka <ihe...@go...>
> Subject: [Xsltforms-support] behaviour of choices and the appearance
> 	attribute
> To: xsl...@li...
> Message-ID:
> 	<CAL...@ma...>
> Content-Type: text/plain; charset="iso-8859-1"
> 
> I implemented a select1 with an xf:choice (for each language) and then an
> itemset showing the choices by language.
> 
> On chrome the control only works if appearance is set to minimal or
> compact. full does not work.
> 
> On firefox the control only works if appearance is set to minimal.
> 
> FWIW when I say minimal I actually mean left at its defaulte setting.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> 
> ------------------------------
> 
> Message: 6
> Date: Sun, 27 May 2012 10:37:05 +0100
> From: Ihe Onwuka <ihe...@go...>
> Subject: [Xsltforms-support] Regression after switching to XQuery
> 	generation
> To: xsl...@li...
> Message-ID:
> 	<CALfs7+wz6pNH0KWQLfLQc6nZ9MYFLcgWfR6=Ea2...@ma...>
> Content-Type: text/plain; charset="iso-8859-1"
> 
> In order to complete developing my app I have switched to generating my
> form via XQuery (a la Beginners Guide to XRX thanks Dan).
> 
> Unfortunately the form has regressed significantly (labels not rendered,
> select drop downs not populated) etc.
> 
> I've checked that I have the correct paths to reference data but beyond
> that I don't know what next to do.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> 
> ------------------------------
> 
> Message: 7
> Date: Sun, 27 May 2012 13:18:29 +0100
> From: Ihe Onwuka <ihe...@go...>
> Subject: Re: [Xsltforms-support] Regression after switching to XQuery
> 	generation
> To: xsl...@li...
> Message-ID:
> 	<CALfs7+w5CapJHVpv4w65BYA1-uk=sq7...@ma...>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> I believe what is happening is that the form is being processed by
> betterform instead of XSLTForms even though i have followed the
> instructions and included
> 
>  declare option exist:serialize "method=xhtml media-type=text/xml";
>  declare option exist:serialize "indent=no";
>  declare option exist:serialize "process-xsl-pi=no";
> 
> in my xquery.
> 
> 
> 
> On Sun, May 27, 2012 at 10:37 AM, Ihe Onwuka <ihe...@go...> wrote:
> >
> > In order to complete developing my app I have switched to generating my form via XQuery (a la Beginners Guide to XRX thanks Dan).
> >
> > Unfortunately the form has regressed significantly (labels not rendered, select drop downs not populated) etc.
> >
> > I've checked that I have the correct paths to reference data but beyond that? I don't know what next to do.
> >
> >
> 
> 
> 
> ------------------------------
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> 
> ------------------------------
> 
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
> 
> 
> End of Xsltforms-support Digest, Vol 36, Issue 6
> ************************************************
> 
> 
--
With thanks and Regards,
N.Srividhya(RS-I)
O.T.C, N.I.C,
Chennai.

Re: [Xsltforms-support] Regression after switching to XQuery generation

[Wolfgang M. <wol...@ex...>]

Call

request:set-attribute("betterform.filter.ignoreResponseBody", "true")

somewhere in the XQuery which generates the form or set the
corresponding property in

webapp/WEB-INF/betterform-config.xml

Wolfgang


2012/5/27 Ihe Onwuka <ihe...@go...>:
> I believe what is happening is that the form is being processed by
> betterform instead of XSLTForms even though i have followed the
> instructions and included
>
>  declare option exist:serialize "method=xhtml media-type=text/xml";
>  declare option exist:serialize "indent=no";
>  declare option exist:serialize "process-xsl-pi=no";
>
> in my xquery.
>
>
>
> On Sun, May 27, 2012 at 10:37 AM, Ihe Onwuka <ihe...@go...> wrote:
>>
>> In order to complete developing my app I have switched to generating my form via XQuery (a la Beginners Guide to XRX thanks Dan).
>>
>> Unfortunately the form has regressed significantly (labels not rendered, select drop downs not populated) etc.
>>
>> I've checked that I have the correct paths to reference data but beyond that  I don't know what next to do.
>>
>>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support

Re: [Xsltforms-support] Regression after switching to XQuery generation

[Ihe O. <ihe...@go...>]

I believe what is happening is that the form is being processed by
betterform instead of XSLTForms even though i have followed the
instructions and included

  declare option exist:serialize "method=xhtml media-type=text/xml";
  declare option exist:serialize "indent=no";
  declare option exist:serialize "process-xsl-pi=no";

in my xquery.



On Sun, May 27, 2012 at 10:37 AM, Ihe Onwuka <ihe...@go...> wrote:
>
> In order to complete developing my app I have switched to generating my form via XQuery (a la Beginners Guide to XRX thanks Dan).
>
> Unfortunately the form has regressed significantly (labels not rendered, select drop downs not populated) etc.
>
> I've checked that I have the correct paths to reference data but beyond that  I don't know what next to do.
>
>

[Xsltforms-support] Regression after switching to XQuery generation

[Ihe O. <ihe...@go...>]

In order to complete developing my app I have switched to generating my
form via XQuery (a la Beginners Guide to XRX thanks Dan).

Unfortunately the form has regressed significantly (labels not rendered,
select drop downs not populated) etc.

I've checked that I have the correct paths to reference data but beyond
that  I don't know what next to do.

[Xsltforms-support] behaviour of choices and the appearance attribute

[Ihe O. <ihe...@go...>]

I implemented a select1 with an xf:choice (for each language) and then an
itemset showing the choices by language.

On chrome the control only works if appearance is set to minimal or
compact. full does not work.

On firefox the control only works if appearance is set to minimal.

FWIW when I say minimal I actually mean left at its defaulte setting.

Re: [Xsltforms-support] Binding to the absence of a node

[Chimezie O. <chi...@gm...>]

Hello, Dan (CC'ed support list).  Thanks for the suggestion.

I was eventually able to get it to work via:

                                <xforms:group     ref=".[not(AbsentElement)]">
                                    <xforms:trigger>
                                        <xforms:label>Add absent
element</xforms:label>
                                        ... action ..
                                    </xforms:trigger>
                                </xforms:group>


On Thu, May 24, 2012 at 10:03 AM, Dan McCreary <dan...@gm...> wrote:
> Hello Chimezie,
>
> I have done this but I recall I just used the simpler following notation:
>
> <xforms:group ref="not(AbsentElement)">
>
> or perhaps
>
> <xforms:group ref="./not(AbsentElement)">
>
> Have you tried these?
>
> - Dan
>
> On Thu, May 24, 2012 at 7:07 AM, Chimezie Ogbuji <chi...@gm...> wrote:
>>
>> Hello, I'm trying to support a situation where a group of controls (or
>> a single control) appear only if another node in the same instance
>> document does not appear.  When I was using XForms extension for
>> Firefox in the past, I was able to do it this way:
>>
>>
>>                            <xforms:group
>> ref="current()[not(AbsentElement)]">
>>                                <xforms:trigger>
>>                                    <xforms:label>Add Skilled response
>> section</xforms:label>
>>                                    .. action to add AbsentElement to
>> context..
>>                                </xforms:trigger>
>>                            </xforms:group>
>>
>> The general idea is to only show a trigger if AbsentElement is not a
>> child of the current context, which will add that element if clicked.
>> However, I get the following exception
>>
>> XSLTForms Exception
>> --------------------------
>>
>> Error parsing the following XPath expression :
>>
>> current()[not(AbsentElement)]
>>
>> Unknown operator at '[not(AbsentElement)]' in
>> 'current()[not(AbsentElement)]'
>>
>> Can this be done in XSLTForms?
>>
>> Thanks.
>>
>> -- Chime
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Xsltforms-support mailing list
>> Xsl...@li...
>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
>
>
>
> --
> Dan McCreary
> NoSQL Evangelist
> office: (952) 931-9198
> cell: (612) 986-1552

Re: [Xsltforms-support] Submission - method = put not saving to xml file

[Dan M. <dan...@gm...>]

Hello Ine,

Although PUT will work under some circumstances (where you have write
access) I think that using HTTP POST to a "save.xq" script will be much
more reliable since there are many triggers you can add at the save point.
You can also use "update.xq" in the same way.

There are examples of this here:

http://www.danmccreary.com/xrx/beginners-guide/beginners-guide-to-xrx.xhtml#d0e862

- Dan

On Thu, May 24, 2012 at 2:23 AM, Ihe Onwuka <ihe...@go...>wrote:

> In my model I have   <xf:submission id="submitSales" method="put"
> action="sales.xml" ref="b2b:Sales"/>.
>
> In my view I have
>
>        <xf:submit submission="submitSales">
>           <xf:label>Save</xf:label>
>        </xf:submit>
>
> but the model does not overwrite the sales.xml file when I click Save.
>
> Also earlier I mistakenly used the wrong IDRef (as in non-existent in
> the submission attribute of <xf:submit>.
>
> The form displayed the loading box and didn't do anything.
>
> Perhaps there should be some sort of exception, better than looking
> like it is going to do something but then not.
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>



-- 
Dan McCreary
NoSQL Evangelist
office: (952) 931-9198
cell: (612) 986-1552

[Xsltforms-support] Binding to the absence of a node

[Chimezie O. <chi...@gm...>]

Hello, I'm trying to support a situation where a group of controls (or
a single control) appear only if another node in the same instance
document does not appear.  When I was using XForms extension for
Firefox in the past, I was able to do it this way:


                            <xforms:group ref="current()[not(AbsentElement)]">
                                <xforms:trigger>
                                    <xforms:label>Add Skilled response
section</xforms:label>
                                    .. action to add AbsentElement to context..
                                </xforms:trigger>
                            </xforms:group>

The general idea is to only show a trigger if AbsentElement is not a
child of the current context, which will add that element if clicked.
However, I get the following exception

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

Error parsing the following XPath expression :

current()[not(AbsentElement)]

Unknown operator at '[not(AbsentElement)]' in 'current()[not(AbsentElement)]'

Can this be done in XSLTForms?

Thanks.

-- Chime

[Xsltforms-support] Submission - method = put not saving to xml file

[Ihe O. <ihe...@go...>]

In my model I have   <xf:submission id="submitSales" method="put"
action="sales.xml" ref="b2b:Sales"/>.

In my view I have

        <xf:submit submission="submitSales">
           <xf:label>Save</xf:label>
        </xf:submit>

but the model does not overwrite the sales.xml file when I click Save.

Also earlier I mistakenly used the wrong IDRef (as in non-existent in
the submission attribute of <xf:submit>.

The form displayed the loading box and didn't do anything.

Perhaps there should be some sort of exception, better than looking
like it is going to do something but then not.

Re: [Xsltforms-support] Load from schema error

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

Ihe,

Whether the schema is inline or external, it's the same for XSLTForms 
which currently will only look at simpleType declarations in it.

These declarations can contain restrictions (pattern, enumeration 
(latest build required), length,...) such as in 
http://www.agencexml.com/xforms-tests/testsuite/XForms1.1/Edition1/Chapt02/2.3.a.xhtml

Thank you for your feedbacks!

-Alain

Le 23/05/2012 17:48, Ihe Onwuka a écrit :
> Alain,
>
> Could you please clarify. Do you mean I can attach a schema as long as
> it only contains simpleType declarations which I can then reference
> from the XForm.
>
> Or do you mean that I can define type declarations in a schema
> fragment in the xForm.
>
> Also by simpleTypes does that include derivation by restriction eg
> restricting a string to a few enumerated values or a pattern.
>
> Thanks
>
> ihe
>
> On Tue, May 22, 2012 at 9:40 PM, Alain Couthures
> <ala...@ag...>  wrote:
>> Only simpleType declarations in schemas are currently supported by
>> XSLTForms.
>>
>> -Alain
>>
>> Le 19/05/2012 17:52, ihe onwuka a écrit :
>>> Also I get the attached error when I run the load from schema example
>>> at http://en.wikibooks.org/wiki/XForms/Load_from_XML_Schema
>>>
>>> Do you support schema attachments?
>>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Xsltforms-support mailing list
>> Xsl...@li...
>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

Re: [Xsltforms-support] Load from schema error

[Ihe O. <ihe...@go...>]

Alain,

Could you please clarify. Do you mean I can attach a schema as long as
it only contains simpleType declarations which I can then reference
from the XForm.

Or do you mean that I can define type declarations in a schema
fragment in the xForm.

Also by simpleTypes does that include derivation by restriction eg
restricting a string to a few enumerated values or a pattern.

Thanks

ihe

On Tue, May 22, 2012 at 9:40 PM, Alain Couthures
<ala...@ag...> wrote:
> Only simpleType declarations in schemas are currently supported by
> XSLTForms.
>
> -Alain
>
> Le 19/05/2012 17:52, ihe onwuka a écrit :
>> Also I get the attached error when I run the load from schema example
>> at http://en.wikibooks.org/wiki/XForms/Load_from_XML_Schema
>>
>> Do you support schema attachments?
>>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support

Re: [Xsltforms-support] using switch statement causes error

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

Could you please send me test files for the 2 instances so I could 
reproduce this issue?

Thanks!

-Alain

Le 20/05/2012 16:16, ihe onwuka a écrit :
> The first file renders ok.
>
> The difference between the 2 files is that the  group in the second
> file is enclosed in a switch (and case) tag.
>
> The 2nd  file gives this error
>
> XSLTForms Exception
> --------------------------
>
> Error initializing :
>
> ([object Object],"sales",[object
> Object],false,"application/xml","sales.xml",null)@http://localhost:8080/exist/xforms/xsltforms/xsltforms.js:2693
> xsltforms_initImpl()@http://localhost:8080/exist/xforms/b2b/b2berror.xhtml:33
> xsltforms_init()@http://localhost:8080/exist/xforms/b2b/b2berror.xhtml:2
> onload([object Event])@http://localhost:8080/exist/xforms/b2b/b2berror.xhtml:1
>
>
> TypeError
>
> instelt.xfElement is undefined
>

Re: [Xsltforms-support] Load from schema error

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

Only simpleType declarations in schemas are currently supported by 
XSLTForms.

-Alain

Le 19/05/2012 17:52, ihe onwuka a écrit :
> Also I get the attached error when I run the load from schema example
> at http://en.wikibooks.org/wiki/XForms/Load_from_XML_Schema
>
> Do you support schema attachments?
>

Re: [Xsltforms-support] Chrome:Input bound to 2nd model not rendering

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

Hello Ihe,

The 2nd group is rendered when removing ref="/b2b:Client" or adding 
model="clientModel" because b2b:Client is not in the default model.

BTW, you don't have to always mention the document element in each XPath 
expression because it is the default evaluation context.

Thank you for your feedbacks!

-Alain

Le 22/05/2012 11:04, ihe onwuka a écrit :
> There are 2 groups in this. The first group is rendering ok on Chrome.
>
> The input control in the 2nd group is not rendering at all although
> the 2nd fieldset is.
>
>   I have added a dummy attribute in the namespace just in case.
>
> <?xml version="1.0"?>
> <?xml-stylesheet href="../xsltforms/xsltforms.xsl" type="text/xsl"?>
> <html xmlns:html="http://www.w3.org/1999/xhtml"
> xmlns="http://www.w3.org/1999/xhtml"
> xmlns:xf="http://www.w3.org/2002/xforms"
> xmlns:ev="http://www.w3.org/2001/xml-events"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:b2b="http://www.b2b.net/plants">
>    <head>
>      <title>B2B.Net Plants System</title>
>      <xf:model id="salesModel">
>        <xf:instance src="sales.xml"/>
>        <xf:bind nodeset="/b2b:Sales/b2b:Client" id="salesClient"
> type="xsd:string"/>
>        <xf:bind nodeset="/b2b:Sales/b2b:Date" id="salesDate" type="xsd:date"/>
>        <xf:bind nodeset="/b2b:Sales/b2b:Botanical" id="salesBotanical"
> type="xsd:string"/>
>        <xf:bind nodeset="/b2b:Sales/b2b:Quantity" id="salesQuantity"
> type="xsd:positiveInteger"/>
>        <xf:bind nodeset="/b2b:Sales/b2b:UnitPrice" id="salesUnitPrice"
> type="xsd:decimal"/>
>        <xf:bind nodeset="/b2b:Sales/b2b:DiscountRate"
> id="salesDiscountRate" type="xsd:decimal"/>
>        <xf:bind nodeset="/b2b:Sales/b2b:Comments" id="salesComments"
> type="xsd:string"/>
>      </xf:model>
>      <xf:model id="clientModel">
>        <xf:instance src="clients.xml"/>
>        <xf:bind nodeset="/b2b:Client/b2b:Name" id="clientName"
> type="xsd:string"/>
>        <xf:bind nodeset="/b2b:Client/b2b:Address" id="clientAddress"
> type="xsd:string"/>
>        <xf:bind nodeset="/b2b:Client/b2b:EmailAddress"
> id="clientEmailAddress" type="xsd:string"/>
>        <xf:bind nodeset="/b2b:Client/b2b:Phone" id="clientPhone"
> type="xsd:string"/>
>        <xf:bind nodeset="/b2b:Client/b2b:Comments" id="clientComments"
> type="xsd:string"/>
>      </xf:model>
>    </head>
>    <body>
>      <xf:trigger id="Plants" appearance="compact">
>        <xf:label>Plants</xf:label>
>      </xf:trigger>
>      <xf:trigger id="Stock" appearance="compact">
>        <xf:label>Stock</xf:label>
>      </xf:trigger>
>      <xf:trigger id="Clients" appearance="compact">
>        <xf:label>Clients</xf:label>
>      </xf:trigger>
>      <xf:trigger id="Sales" appearance="compact">
>        <xf:label>Sales</xf:label>
>      </xf:trigger>
>      <br/>
>      <fieldset>
>        <legend>Sales Details</legend>
>        <xf:group ref="/b2b:Sales">
>          <xf:input bind="salesClient">
>            <xf:label>Client:</xf:label>
>          </xf:input>
>          <br/>
>          <xf:input bind="salesDate">
>            <xf:label>Date:</xf:label>
>          </xf:input>
>          <br/>
>          <xf:input bind="salesBotanical">
>            <xf:label>Botanical:</xf:label>
>          </xf:input>
>          <br/>
>          <xf:input bind="salesQuantity">
>            <xf:label>Quantity:</xf:label>
>          </xf:input>
>          <br/>
>          <xf:input bind="salesDiscountRate">
>            <xf:label>Discount Rate:</xf:label>
>          </xf:input>
>          <br/>
>          <xf:input bind="salesUnitPrice">
>            <xf:label>Unit Price:</xf:label>
>          </xf:input>
>          <br/>
>          <xf:input bind="salesComments">
>            <xf:label>Comments:</xf:label>
>          </xf:input>
>          <br/>
>        </xf:group>
>      </fieldset>
>      <fieldset>
>        <legend>Client Details</legend>
>        <xf:group ref="/b2b:Client">
>          <xf:input bind="clientName">
>            <xf:label>Name:</xf:label>
>          </xf:input>
>          <br/>
>        </xf:group>
>      </fieldset>
>    </body>
> </html>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

[Xsltforms-support] Chrome:Input bound to 2nd model not rendering

[ihe o. <ihe...@go...>]

There are 2 groups in this. The first group is rendering ok on Chrome.

The input control in the 2nd group is not rendering at all although
the 2nd fieldset is.

 I have added a dummy attribute in the namespace just in case.

<?xml version="1.0"?>
<?xml-stylesheet href="../xsltforms/xsltforms.xsl" type="text/xsl"?>
<html xmlns:html="http://www.w3.org/1999/xhtml"
xmlns="http://www.w3.org/1999/xhtml"
xmlns:xf="http://www.w3.org/2002/xforms"
xmlns:ev="http://www.w3.org/2001/xml-events"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:b2b="http://www.b2b.net/plants">
  <head>
    <title>B2B.Net Plants System</title>
    <xf:model id="salesModel">
      <xf:instance src="sales.xml"/>
      <xf:bind nodeset="/b2b:Sales/b2b:Client" id="salesClient"
type="xsd:string"/>
      <xf:bind nodeset="/b2b:Sales/b2b:Date" id="salesDate" type="xsd:date"/>
      <xf:bind nodeset="/b2b:Sales/b2b:Botanical" id="salesBotanical"
type="xsd:string"/>
      <xf:bind nodeset="/b2b:Sales/b2b:Quantity" id="salesQuantity"
type="xsd:positiveInteger"/>
      <xf:bind nodeset="/b2b:Sales/b2b:UnitPrice" id="salesUnitPrice"
type="xsd:decimal"/>
      <xf:bind nodeset="/b2b:Sales/b2b:DiscountRate"
id="salesDiscountRate" type="xsd:decimal"/>
      <xf:bind nodeset="/b2b:Sales/b2b:Comments" id="salesComments"
type="xsd:string"/>
    </xf:model>
    <xf:model id="clientModel">
      <xf:instance src="clients.xml"/>
      <xf:bind nodeset="/b2b:Client/b2b:Name" id="clientName"
type="xsd:string"/>
      <xf:bind nodeset="/b2b:Client/b2b:Address" id="clientAddress"
type="xsd:string"/>
      <xf:bind nodeset="/b2b:Client/b2b:EmailAddress"
id="clientEmailAddress" type="xsd:string"/>
      <xf:bind nodeset="/b2b:Client/b2b:Phone" id="clientPhone"
type="xsd:string"/>
      <xf:bind nodeset="/b2b:Client/b2b:Comments" id="clientComments"
type="xsd:string"/>
    </xf:model>
  </head>
  <body>
    <xf:trigger id="Plants" appearance="compact">
      <xf:label>Plants</xf:label>
    </xf:trigger>
    <xf:trigger id="Stock" appearance="compact">
      <xf:label>Stock</xf:label>
    </xf:trigger>
    <xf:trigger id="Clients" appearance="compact">
      <xf:label>Clients</xf:label>
    </xf:trigger>
    <xf:trigger id="Sales" appearance="compact">
      <xf:label>Sales</xf:label>
    </xf:trigger>
    <br/>
    <fieldset>
      <legend>Sales Details</legend>
      <xf:group ref="/b2b:Sales">
        <xf:input bind="salesClient">
          <xf:label>Client: </xf:label>
        </xf:input>
        <br/>
        <xf:input bind="salesDate">
          <xf:label>Date: </xf:label>
        </xf:input>
        <br/>
        <xf:input bind="salesBotanical">
          <xf:label>Botanical: </xf:label>
        </xf:input>
        <br/>
        <xf:input bind="salesQuantity">
          <xf:label>Quantity: </xf:label>
        </xf:input>
        <br/>
        <xf:input bind="salesDiscountRate">
          <xf:label>Discount Rate: </xf:label>
        </xf:input>
        <br/>
        <xf:input bind="salesUnitPrice">
          <xf:label>Unit Price: </xf:label>
        </xf:input>
        <br/>
        <xf:input bind="salesComments">
          <xf:label>Comments: </xf:label>
        </xf:input>
        <br/>
      </xf:group>
    </fieldset>
    <fieldset>
      <legend>Client Details</legend>
      <xf:group ref="/b2b:Client">
        <xf:input bind="clientName">
          <xf:label>Name: </xf:label>
        </xf:input>
        <br/>
      </xf:group>
    </fieldset>
  </body>
</html>

Re: [Xsltforms-support] Input controls render on Chrome but not on Firefox 12.0 (running on Ubuntu)

[ihe o. <ihe...@go...>]

ok that worked. thanks.

On Tue, May 22, 2012 at 8:07 AM, Alain Couthures
<ala...@ag...> wrote:
> Hello Ihe,
>
> Because of namespace nodes not being accessible from Firefox XSLT engine,
> there is a workaround: add an attribute in this namespace at the document
> element level (b2b:dummy="dummy" for example).
>
> Thank you for your feedbacks!
>
> -Alain
>
> Le 22/05/2012 09:03, ihe onwuka a écrit :
>>
>> <?xml version="1.0"?>
>> <?xml-stylesheet href="../xsltforms/xsltforms.xsl" type="text/xsl"?>
>> <html xmlns:html="http://www.w3.org/1999/xhtml"
>> xmlns="http://www.w3.org/1999/xhtml"
>> xmlns:xf="http://www.w3.org/2002/xforms"
>> xmlns:ev="http://www.w3.org/2001/xml-events"
>> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>> xmlns:b2b="http://www.b2b.net/plants">
>>   <head>
>>     <title>B2B.Net Plants System</title>
>>     <xf:model id="salesModel">
>>       <xf:instance src="sales.xml"/>
>>       <xf:bind nodeset="/b2b:Sales/b2b:Client" id="salesClient"
>> type="xsd:string"/>
>>       <xf:bind nodeset="/b2b:Sales/b2b:Date" id="salesDate"
>> type="xsd:date"/>
>>     </xf:model>
>>   </head>
>>   <body>
>>     <xf:trigger id="Plants" appearance="compact">
>>       <xf:label>Plants</xf:label>
>>     </xf:trigger>
>>     <xf:trigger id="Stock" appearance="compact">
>>       <xf:label>Stock</xf:label>
>>     </xf:trigger>
>>     <xf:trigger id="Clients" appearance="compact">
>>       <xf:label>Clients</xf:label>
>>     </xf:trigger>
>>     <xf:trigger id="Sales" appearance="compact">
>>       <xf:label>Sales</xf:label>
>>     </xf:trigger>
>>     <br/>
>>     <xf:group ref="/b2b:Sales">
>>       <fieldset>
>>         <legend>Sales Details</legend>
>>         <xf:input bind="salesClient">
>>           <xf:label>Client:</xf:label>
>>         </xf:input>
>>         <br/>
>>         <xf:input bind="salesDate" appearance="compact">
>>           <xf:label>Date:</xf:label>
>>         </xf:input>
>>         <br/>
>>       </fieldset>
>>     </xf:group>
>>   </body>
>> </html>
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Xsltforms-support mailing list
>> Xsl...@li...
>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>
>

Re: [Xsltforms-support] Input controls render on Chrome but not on Firefox 12.0 (running on Ubuntu)

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

Hello Ihe,

Because of namespace nodes not being accessible from Firefox XSLT 
engine, there is a workaround: add an attribute in this namespace at the 
document element level (b2b:dummy="dummy" for example).

Thank you for your feedbacks!

-Alain

Le 22/05/2012 09:03, ihe onwuka a écrit :
> <?xml version="1.0"?>
> <?xml-stylesheet href="../xsltforms/xsltforms.xsl" type="text/xsl"?>
> <html xmlns:html="http://www.w3.org/1999/xhtml"
> xmlns="http://www.w3.org/1999/xhtml"
> xmlns:xf="http://www.w3.org/2002/xforms"
> xmlns:ev="http://www.w3.org/2001/xml-events"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:b2b="http://www.b2b.net/plants">
>    <head>
>      <title>B2B.Net Plants System</title>
>      <xf:model id="salesModel">
>        <xf:instance src="sales.xml"/>
>        <xf:bind nodeset="/b2b:Sales/b2b:Client" id="salesClient"
> type="xsd:string"/>
>        <xf:bind nodeset="/b2b:Sales/b2b:Date" id="salesDate" type="xsd:date"/>
>      </xf:model>
>    </head>
>    <body>
>      <xf:trigger id="Plants" appearance="compact">
>        <xf:label>Plants</xf:label>
>      </xf:trigger>
>      <xf:trigger id="Stock" appearance="compact">
>        <xf:label>Stock</xf:label>
>      </xf:trigger>
>      <xf:trigger id="Clients" appearance="compact">
>        <xf:label>Clients</xf:label>
>      </xf:trigger>
>      <xf:trigger id="Sales" appearance="compact">
>        <xf:label>Sales</xf:label>
>      </xf:trigger>
>      <br/>
>      <xf:group ref="/b2b:Sales">
>        <fieldset>
>          <legend>Sales Details</legend>
>          <xf:input bind="salesClient">
>            <xf:label>Client:</xf:label>
>          </xf:input>
>          <br/>
>          <xf:input bind="salesDate" appearance="compact">
>            <xf:label>Date:</xf:label>
>          </xf:input>
>          <br/>
>        </fieldset>
>      </xf:group>
>    </body>
> </html>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

[Xsltforms-support] Input controls render on Chrome but not on Firefox 12.0 (running on Ubuntu)

[ihe o. <ihe...@go...>]

<?xml version="1.0"?>
<?xml-stylesheet href="../xsltforms/xsltforms.xsl" type="text/xsl"?>
<html xmlns:html="http://www.w3.org/1999/xhtml"
xmlns="http://www.w3.org/1999/xhtml"
xmlns:xf="http://www.w3.org/2002/xforms"
xmlns:ev="http://www.w3.org/2001/xml-events"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:b2b="http://www.b2b.net/plants">
  <head>
    <title>B2B.Net Plants System</title>
    <xf:model id="salesModel">
      <xf:instance src="sales.xml"/>
      <xf:bind nodeset="/b2b:Sales/b2b:Client" id="salesClient"
type="xsd:string"/>
      <xf:bind nodeset="/b2b:Sales/b2b:Date" id="salesDate" type="xsd:date"/>
    </xf:model>
  </head>
  <body>
    <xf:trigger id="Plants" appearance="compact">
      <xf:label>Plants</xf:label>
    </xf:trigger>
    <xf:trigger id="Stock" appearance="compact">
      <xf:label>Stock</xf:label>
    </xf:trigger>
    <xf:trigger id="Clients" appearance="compact">
      <xf:label>Clients</xf:label>
    </xf:trigger>
    <xf:trigger id="Sales" appearance="compact">
      <xf:label>Sales</xf:label>
    </xf:trigger>
    <br/>
    <xf:group ref="/b2b:Sales">
      <fieldset>
        <legend>Sales Details</legend>
        <xf:input bind="salesClient">
          <xf:label>Client: </xf:label>
        </xf:input>
        <br/>
        <xf:input bind="salesDate" appearance="compact">
          <xf:label>Date: </xf:label>
        </xf:input>
        <br/>
      </fieldset>
    </xf:group>
  </body>
</html>

Re: [Xsltforms-support] Disabled buttons are click-able on IE, Chrome, Safari

[Benoit V. <bvi...@la...>]

Hi Alain,

Thx, it works fine now. But ... I found another weird feature with 
triggers (appearance="minimal") and IE9 :
1) In the same test code, replace the line "<xf:trigger ref="b1">" with 
"<xf:trigger ref="b1" appearance="minimal" >"
2) Display the form
3) each time you click on Button 1, you get a message box "Button 1" ... 
you are happy.
4) you click anywhere on the windows (Button1 loose the focus), you get 
an unwanted message box "Button 1" ... you are unhappy.
5) you click again on Button 1, you don't get the message box ... you 
are unhappy, again !

I think that there is problem with the focus events on minimal triggers. 
For now I prefer to use standard triggers with CSS to give them a 
"minimal" style, the produced "<button>" seems more reliable than a "<a 
href='javascript:void(0);'>" anchor.

Thank you for your help

	Benoit

Le 17/05/2012 18:27, Alain Couthures a écrit :
> Hi Benoit,
>
> I have added an extra Javascript test for not considering the click
> event on a disabled input.
>
> Please check again with r545.
>
> Thank you for your feedbacks!
>
> -Alain
>
> Le 15/05/2012 18:20, Benoit VINCENT a écrit :
>>
>> Hi Alain,
>>
>> Right now I try to make my forms compatible with IE9and my problem is
>> that the read-only triggers remain click-able.
>>
>> Here's an example:
>>
>> <?xml-stylesheet href="xsltforms/xsltforms.xsl" type="text/xsl"?>
>> <?xsltforms-options debug="yes"?>
>> <html xmlns="http://www.w3.org/1999/xhtml"
>> xmlns:xf="http://www.w3.org/2002/xforms"
>> xmlns:ev="http://www.w3.org/2001/xml-events">
>> <head>
>> <title>Test IE9 disabled button</title>
>> <xf:model>
>> <xf:instance id="main">
>> <data xmlns="">
>> <b1/>
>> <b2/>
>> </data>
>> </xf:instance>
>> <xf:bind nodeset="b2" readonly="true()"/>
>> </xf:model>
>> </head>
>> <body>
>> <xf:trigger ref="b1">
>> <xf:label>Button 1</xf:label>
>> <xf:message ev:event="DOMActivate">Button 1</xf:message>
>> </xf:trigger>
>> <xf:trigger ref="b2">
>> <xf:label>Disabled Button 2</xf:label>
>> <xf:message ev:event="DOMActivate">Disabled Button 2</xf:message>
>> </xf:trigger>
>> </body>
>> </html>
>>
>> Nothing appends when I try to click the disabled trigger on Firefox or
>> Opera, but the message is displayed when use this sample on IE8, IE9,
>> Chrome or Safari. What could I do to protect the disabled buttons on all
>> browsers ?
>>
>> Regards
>> Benoit
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>>
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Xsltforms-support mailing list
>> Xsl...@li...
>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>
>