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

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

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
>