xsltforms-support — XSLTForms support list

Re: [Xsltforms-support] question about conversion from ubiquity

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

Hi Chris,

Could it be that the targeted resource is not in the same domain as the 
form itself (cross-domain restriction)?

What is the release of XSLTForms you are using?

Thank you for your feedback!

--Alain

Le 22/01/2020 à 14:04, ch...@el... a écrit :
>
> I'm still working on this off and on without success.
> POST doesn't seem to be sending anything at all.
>
> I only need a couple of pieces of information, maybe I will switch to GET.
>
> Here is my submission block:
>
>         <xf:submission 
> resource="https://xxxx.yyyy.zzz/cgi-bin/XMLSave1" method="post" 
> id="sendStuff">
>                 <xf:action ev:event="xforms-submit">
>                 </xf:action>
>         </xf:submission>
>
>     -------- Original Message --------
>     Subject: Re: [Xsltforms-support] question about conversion from
>     ubiquity
>     From: Alain Couthures <ala...@ag...
>     <mailto:ala...@ag...>>
>     Date: Thu, January 16, 2020 10:54 am
>     To: Chris Howard <ch...@el... <mailto:ch...@el...>>,
>     xsl...@li...
>     <mailto:xsl...@li...>
>
>     Hello Chris,
>
>     Did you check the HTTP request body with the browser network
>     debugger?
>
>     --Alain
>
>>     Le 16 janvier 2020 à 13:09, Chris Howard < ch...@el...
>>     <mailto:ch...@el...>> a écrit :
>>
>>
>>     Hello,
>>
>>     I have run into another issue:
>>
>>     I am using a CGI perl script and a submission button which calls
>>     the script.
>>     The script gets some data from the POSTDATA and does some actions.
>>
>>     My forms using xsltforms library are not sending any POST data.
>>     The script is being called, but no data.
>>
>>     I tried also with one of the sample forms, substituting in my own
>>     perl
>>     CGI as the action,
>>     still no POST data showing up.
>>
>>     Can you give me some pointers as to where I should be looking?
>>     Is this an issue with the web server config?  I am not seeing any
>>     errors
>>     in the
>>     log files, just no POST data coming through.
>>
>>     Thanks
>>
>>     Chris Howard
>>
>>
>>
>>
>>     On 1/12/20 7:06 AM, Chris Howard wrote:
>>>     Hi,
>>>
>>>     I spent some time with the samples and sorted it out.
>>>     The big first item was adding xmlns="" in the top-level instance
>>>     data
>>>     tag.
>>>     Then I started seeing my instance data.
>>>
>>>     Then I worked out some issues with stylesheet (also covered in the
>>>     examples).
>>>
>>>     I very much appreciate your help!
>>>
>>>     Chris
>>>
>>>
>>>     On 1/11/20 8:41 AM, Alain Couthures wrote:
>>>>     Hello Chris,
>>>>
>>>>     As far as I remember, Ubiquity had a limitation about models
>>>>     not to
>>>>     be declared in head section but in body section.
>>>>
>>>>     I suggest you to first check that XSLTForms samples are OK for
>>>>     you.
>>>>     Then, to compare with Ubiquity.
>>>>
>>>>     If possible, please don't hesitate to send a full form source.
>>>>
>>>>     Thank you for your feedback!
>>>>
>>>>     --Alain
>>>>
>>>>
>>>>     Le 11/01/2020 à 15:04, Chris Howard a écrit :
>>>>     >
>>>>>     Update,
>>>>>
>>>>>     I have been simplifying my form this morning and even with all of
>>>>>     the triggers
>>>>>     and events stripped out, I still don't see any of my data.
>>>>>
>>>>>
>>>>>
>>>>>     On 1/11/20 7:17 AM, Chris Howard wrote:
>>>>>>     Hi,
>>>>>>
>>>>>>     Many years ago I worked on a xform which would allow editing of
>>>>>>     an XML file. I didn't know a lot about XSLT or XForms but I was
>>>>>>     able to cook up something that worked.
>>>>>>
>>>>>>     We used the ubiquity library.
>>>>>>
>>>>>>     Recently the form quit working.
>>>>>>     I am remote from the situation such that I cannot directly debug
>>>>>>     the problem.
>>>>>>     There are other people working on that.
>>>>>>
>>>>>>     I've been given the task of researching a replacement for the
>>>>>>     ancient ubiquity library.
>>>>>>
>>>>>>     I have the xsltforms package installed on our web server and
>>>>>>     I can
>>>>>>     run some sample forms.
>>>>>>     It looks like the xsltforms content is being sent to the
>>>>>>     browser,
>>>>>>     so I think my
>>>>>>     basic plumbing is working ok.
>>>>>>
>>>>>>     My problem is that our form never seems to activate.  I get the
>>>>>>     screen drawn
>>>>>>     but none of my DOMActivate events seem to perform.  Also my
>>>>>>     submit
>>>>>>     buttons
>>>>>>     do not work. None of my instance data is showing up in the form.
>>>>>>
>>>>>>     I am looking for any help or advise that might be available
>>>>>>
>>>>>>     My triggers look like this:
>>>>>>
>>>>>>             <xf:trigger bind="detailSpecial">
>>>>>>
>>>>>>                     <xf:label>Insert tax/total Item</xf:label>
>>>>>>
>>>>>>                     <xf:action ev:event="DOMActivate">
>>>>>>
>>>>>>                             <xf:insert
>>>>>>     nodeset="/bill/billDetail/detailSpecialSet/detailSpecial"
>>>>>>     at="index('repeat-detailSpecial')" position="before"/>
>>>>>>
>>>>>>                             <xf:setvalue
>>>>>>     ref="/bill/billDetail/detailSpecialSet/detailSpecial[index('repeat-detailSpecial')]/specialDescription"></xf:setvalue>
>>>>>>
>>>>>>
>>>>>>                             <xf:setvalue
>>>>>>     ref="/bill/billDetail/detailSpecialSet/detailSpecial[index('repeat-detailSpecial')]/charge"></xf:setvalue>
>>>>>>
>>>>>>
>>>>>>                     </xf:action>
>>>>>>
>>>>>>             </xf:trigger>
>>>>>>
>>>>>>             <xf:trigger bind="detailSpecial">
>>>>>>
>>>>>>                     <xf:label>Delete tax/total Item</xf:label>
>>>>>>
>>>>>>                     <xf:delete ev:event="DOMActivate"
>>>>>>     nodeset="/bill/billDetail/detailSpecialSet/detailSpecial"
>>>>>>     at="index('repeat-detailSpecial')"/>
>>>>>>
>>>>>>             </xf:trigger>
>>>>>>
>>>>>>
>>>>>>
>>>>>>     _______________________________________________
>>>>>>     Xsltforms-support mailing list
>>>>>>     Xsl...@li...
>>>>>>     <mailto:Xsl...@li...>
>>>>>>     https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>>>>
>>>>>
>>>>>
>>>>>     _______________________________________________
>>>>>     Xsltforms-support mailing list
>>>>>     Xsl...@li...
>>>>>     <mailto:Xsl...@li...>
>>>>>     https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>     _______________________________________________
>>>     Xsltforms-support mailing list
>>>     Xsl...@li...
>>>     <mailto:Xsl...@li...>
>>>     https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>
>>
>>
>>     _______________________________________________
>>     Xsltforms-support mailing list
>>     Xsl...@li...
>>     <mailto:Xsl...@li...>
>>     https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

Re: [Xsltforms-support] question about conversion from ubiquity

[<ch...@el...>]

<html><body><span style="font-family:Verdana; color:#000000; font-size:10pt;"><div><br></div><div>I'm still working on this off and on without success.</div><div>POST doesn't seem to be sending anything at all.</div><div><br></div><div>I only need a couple of pieces of information, maybe I will switch to GET.</div><div><br></div><div>Here is my submission block:<br></div><div><br></div><div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xf:submission resource="https://xxxx.yyyy.zzz/cgi-bin/XMLSave1" method="post" id="sendStuff"&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xf:action ev:event="xforms-submit"&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/xf:action&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/xf:submission&gt;<br><br></div><blockquote id="replyBlockquote" webmail="1" style="border-left: 2px solid blue; margin-left: 8px; padding-left: 8px; font-size:10pt; color:black; font-family:verdana;">
<div id="wmQuoteWrapper">
-------- Original Message --------<br>
Subject: Re: [Xsltforms-support] question about conversion from ubiquity<br>
From: Alain Couthures &lt;<a href="mailto:ala...@ag...">ala...@ag...</a>&gt;<br>
Date: Thu, January 16, 2020 10:54 am<br>
To: Chris Howard &lt;<a href="mailto:ch...@el...">ch...@el...</a>&gt;,<br>
<a href="mailto:xsl...@li...">xsl...@li...</a><br>
<br>
      <div> Hello Chris, </div> <div> <br> </div> <div> Did you check the HTTP request body with the browser network debugger? </div> <div> <br> </div> <div> --Alain </div> <div> <br> </div> <blockquote type="cite" style="border-left: blue 2px solid; margin-left: 8px; padding-left: 8px;"> <div> Le 16 janvier 2020 à 13:09, Chris Howard &lt; <a target="_blank" href="mailto:ch...@el...">ch...@el...</a>&gt; a écrit&nbsp;: </div> <div> <br> </div> <div> <br> </div> <div> Hello, </div> <div> <br> </div> <div> I have run into another issue: </div> <div> <br> </div> <div> I am using a CGI perl script and a submission button which calls the script. </div> <div> The script gets some data from the POSTDATA and does some actions. </div> <div> <br> </div> <div> My forms using xsltforms library are not sending any POST data. </div> <div> The script is being called, but no data. </div> <div> <br> </div> <div> I tried also with one of the sample forms, substituting in my own perl </div> <div> CGI as the action, </div> <div> still no POST data showing up. </div> <div> <br> </div> <div> Can you give me some pointers as to where I should be looking? </div> <div> Is this an issue with the web server config?&nbsp; I am not seeing any errors </div> <div> in the </div> <div> log files, just no POST data coming through. </div> <div> <br> </div> <div> Thanks </div> <div> <br> </div> <div> Chris Howard </div> <div> <br> </div> <div> <br> </div> <div> <br> </div> <div> <br> </div> <div> On 1/12/20 7:06 AM, Chris Howard wrote: </div> <blockquote type="cite" style="border-left: blue 2px solid; margin-left: 8px; padding-left: 8px;"> <div> Hi, </div> <div> <br> </div> <div> I spent some time with the samples and sorted it out. </div> <div> The big first item was adding xmlns="" in the top-level instance data </div> <div> tag. </div> <div> Then I started seeing my instance data. </div> <div> <br> </div> <div> Then I worked out some issues with stylesheet (also covered in the </div> <div> examples). </div> <div> <br> </div> <div> I very much appreciate your help! </div> <div> <br> </div> <div> Chris </div> <div> <br> </div> <div> <br> </div> <div> On 1/11/20 8:41 AM, Alain Couthures wrote: </div> <blockquote type="cite" style="border-left: blue 2px solid; margin-left: 8px; padding-left: 8px;"> <div> Hello Chris, </div> <div> <br> </div> <div> As far as I remember, Ubiquity had a limitation about models not to </div> <div> be declared in head section but in body section. </div> <div> <br> </div> <div> I suggest you to first check that XSLTForms samples are OK for you. </div> <div> Then, to compare with Ubiquity. </div> <div> <br> </div> <div> If possible, please don't hesitate to send a full form source. </div> <div> <br> </div> <div> Thank you for your feedback! </div> <div> <br> </div> <div> --Alain </div> <div> <br> </div> <div> <br> </div> <div> Le 11/01/2020 à 15:04, Chris Howard a écrit&nbsp;: </div> <div> &gt; </div> <blockquote type="cite" style="border-left: blue 2px solid; margin-left: 8px; padding-left: 8px;"> <div> Update, </div> <div> <br> </div> <div> I have been simplifying my form this morning and even with all of </div> <div> the triggers </div> <div> and events stripped out, I still don't see any of my data. </div> <div> <br> </div> <div> <br> </div> <div> <br> </div> <div> On 1/11/20 7:17 AM, Chris Howard wrote: </div> <blockquote type="cite" style="border-left: blue 2px solid; margin-left: 8px; padding-left: 8px;"> <div> Hi, </div> <div> <br> </div> <div> Many years ago I worked on a xform which would allow editing of </div> <div> an XML file. I didn't know a lot about XSLT or XForms but I was </div> <div> able to cook up something that worked. </div> <div> <br> </div> <div> We used the ubiquity library. </div> <div> <br> </div> <div> Recently the form quit working. </div> <div> I am remote from the situation such that I cannot directly debug </div> <div> the problem. </div> <div> There are other people working on that. </div> <div> <br> </div> <div> I've been given the task of researching a replacement for the </div> <div> ancient ubiquity library. </div> <div> <br> </div> <div> I have the xsltforms package installed on our web server and I can </div> <div> run some sample forms. </div> <div> It looks like the xsltforms content is being sent to the browser, </div> <div> so I think my </div> <div> basic plumbing is working ok. </div> <div> <br> </div> <div> My problem is that our form never seems to activate.&nbsp; I get the </div> <div> screen drawn </div> <div> but none of my DOMActivate events seem to perform.&nbsp; Also my submit </div> <div> buttons </div> <div> do not work. None of my instance data is showing up in the form. </div> <div> <br> </div> <div> I am looking for any help or advise that might be available </div> <div> <br> </div> <div> My triggers look like this: </div> <div> <br> </div> <div> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xf:trigger bind="detailSpecial"&gt; </div> <div> <br> </div> <div> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xf:label&gt;Insert tax/total Item&lt;/xf:label&gt; </div> <div> <br> </div> <div> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xf:action ev:event="DOMActivate"&gt; </div> <div> <br> </div> <div> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xf:insert </div> <div> nodeset="/bill/billDetail/detailSpecialSet/detailSpecial" </div> <div> at="index('repeat-detailSpecial')" position="before"/&gt; </div> <div> <br> </div> <div> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xf:setvalue </div> <div> ref="/bill/billDetail/detailSpecialSet/detailSpecial[index('repeat-detailSpecial')]/specialDescription"&gt;&lt;/xf:setvalue&gt; </div> <div> <br> </div> <div> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xf:setvalue </div> <div> ref="/bill/billDetail/detailSpecialSet/detailSpecial[index('repeat-detailSpecial')]/charge"&gt;&lt;/xf:setvalue&gt; </div> <div> <br> </div> <div> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/xf:action&gt; </div> <div> <br> </div> <div> &nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/xf:trigger&gt; </div> <div> <br> </div> <div> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xf:trigger bind="detailSpecial"&gt; </div> <div> <br> </div> <div> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xf:label&gt;Delete tax/total Item&lt;/xf:label&gt; </div> <div> <br> </div> <div> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xf:delete ev:event="DOMActivate" </div> <div> nodeset="/bill/billDetail/detailSpecialSet/detailSpecial" </div> <div> at="index('repeat-detailSpecial')"/&gt; </div> <div> <br> </div> <div> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/xf:trigger&gt; </div> <div> <br> </div> <div> <br> </div> <div> <br> </div> <div> _______________________________________________ </div> <div> Xsltforms-support mailing list </div> <div> <a target="_blank" href="mailto:Xsl...@li...">Xsl...@li...</a> </div> <div> <a href="https://lists.sourceforge.net/lists/listinfo/xsltforms-support" rel="noopener" target="_blank">https://lists.sourceforge.net/lists/listinfo/xsltforms-support</a> </div> </blockquote> <div> <br> </div> <div> <br> </div> <div> <br> </div> <div> _______________________________________________ </div> <div> Xsltforms-support mailing list </div> <div> <a target="_blank" href="mailto:Xsl...@li...">Xsl...@li...</a> </div> <div> <a href="https://lists.sourceforge.net/lists/listinfo/xsltforms-support" rel="noopener" target="_blank">https://lists.sourceforge.net/lists/listinfo/xsltforms-support</a> </div> </blockquote> <div> <br> </div> <div> <br> </div> <div> <br> </div> </blockquote> <div> <br> </div> <div> <br> </div> <div> <br> </div> <div> _______________________________________________ </div> <div> Xsltforms-support mailing list </div> <div> <a target="_blank" href="mailto:Xsl...@li...">Xsl...@li...</a> </div> <div> <a href="https://lists.sourceforge.net/lists/listinfo/xsltforms-support" rel="noopener" target="_blank">https://lists.sourceforge.net/lists/listinfo/xsltforms-support</a> </div> </blockquote> <div> <br> </div> <div> <br> </div> <div> <br> </div> <div> _______________________________________________ </div> <div> Xsltforms-support mailing list </div> <div> <a target="_blank" href="mailto:Xsl...@li...">Xsl...@li...</a> </div> <div> <a href="https://lists.sourceforge.net/lists/listinfo/xsltforms-support" rel="noopener" target="_blank">https://lists.sourceforge.net/lists/listinfo/xsltforms-support</a> </div> </blockquote>   
</div>
</blockquote></span></body></html>

Re: [Xsltforms-support] question about conversion from ubiquity

[Chris H. <ch...@el...>]

---
Yes, I see the "postdata" window in FireFox Web Console when I use the 
"Contact" form example on your site.
It has data in it.

I downloaded that sample to my own site and I modified the "action" to 
use my own simple script.
But I am not seeing any post data at all.

Chris Howard



On 1/16/20 8:05 PM, Chris Howard wrote:
>
> I attempted to do so.  I don't work on this very often.
> But I can see the POST action, and the Firefox console will show me 
> the request and the return..
> but I don't see any of the POST data.
>
> And the IE debugger doesn't show anything, but I can't get it to show 
> me much.
>
> What should I be looking for?
>
>
>
>
> On 1/16/20 11:54 AM, Alain Couthures wrote:
>> Hello Chris,
>>
>> Did you check the HTTP request body with the browser network debugger?
>>
>> --Alain
>>
>>> Le 16 janvier 2020 à 13:09, Chris Howard < ch...@el... 
>>> <mailto:ch...@el...>> a écrit :
>>>
>>>
>>> Hello,
>>>
>>> I have run into another issue:
>>>
>>> I am using a CGI perl script and a submission button which calls the 
>>> script.
>>> The script gets some data from the POSTDATA and does some actions.
>>>
>>> My forms using xsltforms library are not sending any POST data.
>>> The script is being called, but no data.
>>>
>>> I tried also with one of the sample forms, substituting in my own perl
>>> CGI as the action,
>>> still no POST data showing up.
>>>
>>> Can you give me some pointers as to where I should be looking?
>>> Is this an issue with the web server config?  I am not seeing any 
>>> errors
>>> in the
>>> log files, just no POST data coming through.
>>>
>>> Thanks
>>>
>>> Chris Howard
>>>
>>>
>>>
>>>
>>> On 1/12/20 7:06 AM, Chris Howard wrote:
>>>> Hi,
>>>>
>>>> I spent some time with the samples and sorted it out.
>>>> The big first item was adding xmlns="" in the top-level instance data
>>>> tag.
>>>> Then I started seeing my instance data.
>>>>
>>>> Then I worked out some issues with stylesheet (also covered in the
>>>> examples).
>>>>
>>>> I very much appreciate your help!
>>>>
>>>> Chris
>>>>
>>>>
>>>> On 1/11/20 8:41 AM, Alain Couthures wrote:
>>>>> Hello Chris,
>>>>>
>>>>> As far as I remember, Ubiquity had a limitation about models not to
>>>>> be declared in head section but in body section.
>>>>>
>>>>> I suggest you to first check that XSLTForms samples are OK for you.
>>>>> Then, to compare with Ubiquity.
>>>>>
>>>>> If possible, please don't hesitate to send a full form source.
>>>>>
>>>>> Thank you for your feedback!
>>>>>
>>>>> --Alain
>>>>>
>>>>>
>>>>> Le 11/01/2020 à 15:04, Chris Howard a écrit :
>>>>> >
>>>>>> Update,
>>>>>>
>>>>>> I have been simplifying my form this morning and even with all of
>>>>>> the triggers
>>>>>> and events stripped out, I still don't see any of my data.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 1/11/20 7:17 AM, Chris Howard wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> Many years ago I worked on a xform which would allow editing of
>>>>>>> an XML file. I didn't know a lot about XSLT or XForms but I was
>>>>>>> able to cook up something that worked.
>>>>>>>
>>>>>>> We used the ubiquity library.
>>>>>>>
>>>>>>> Recently the form quit working.
>>>>>>> I am remote from the situation such that I cannot directly debug
>>>>>>> the problem.
>>>>>>> There are other people working on that.
>>>>>>>
>>>>>>> I've been given the task of researching a replacement for the
>>>>>>> ancient ubiquity library.
>>>>>>>
>>>>>>> I have the xsltforms package installed on our web server and I can
>>>>>>> run some sample forms.
>>>>>>> It looks like the xsltforms content is being sent to the browser,
>>>>>>> so I think my
>>>>>>> basic plumbing is working ok.
>>>>>>>
>>>>>>> My problem is that our form never seems to activate. I get the
>>>>>>> screen drawn
>>>>>>> but none of my DOMActivate events seem to perform. Also my submit
>>>>>>> buttons
>>>>>>> do not work. None of my instance data is showing up in the form.
>>>>>>>
>>>>>>> I am looking for any help or advise that might be available
>>>>>>>
>>>>>>> My triggers look like this:
>>>>>>>
>>>>>>>         <xf:trigger bind="detailSpecial">
>>>>>>>
>>>>>>>                 <xf:label>Insert tax/total Item</xf:label>
>>>>>>>
>>>>>>>                 <xf:action ev:event="DOMActivate">
>>>>>>>
>>>>>>>                         <xf:insert
>>>>>>> nodeset="/bill/billDetail/detailSpecialSet/detailSpecial"
>>>>>>> at="index('repeat-detailSpecial')" position="before"/>
>>>>>>>
>>>>>>>                         <xf:setvalue
>>>>>>> ref="/bill/billDetail/detailSpecialSet/detailSpecial[index('repeat-detailSpecial')]/specialDescription"></xf:setvalue> 
>>>>>>>
>>>>>>>
>>>>>>>                         <xf:setvalue
>>>>>>> ref="/bill/billDetail/detailSpecialSet/detailSpecial[index('repeat-detailSpecial')]/charge"></xf:setvalue> 
>>>>>>>
>>>>>>>
>>>>>>>                 </xf:action>
>>>>>>>
>>>>>>>         </xf:trigger>
>>>>>>>
>>>>>>>         <xf:trigger bind="detailSpecial">
>>>>>>>
>>>>>>>                 <xf:label>Delete tax/total Item</xf:label>
>>>>>>>
>>>>>>>                 <xf:delete ev:event="DOMActivate"
>>>>>>> nodeset="/bill/billDetail/detailSpecialSet/detailSpecial"
>>>>>>> at="index('repeat-detailSpecial')"/>
>>>>>>>
>>>>>>>         </xf:trigger>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Xsltforms-support mailing list
>>>>>>> Xsl...@li... 
>>>>>>> <mailto:Xsl...@li...>
>>>>>>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Xsltforms-support mailing list
>>>>>> Xsl...@li... 
>>>>>> <mailto:Xsl...@li...>
>>>>>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Xsltforms-support mailing list
>>>> Xsl...@li... 
>>>> <mailto:Xsl...@li...>
>>>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>>
>>>
>>>
>>> _______________________________________________
>>> Xsltforms-support mailing list
>>> Xsl...@li... 
>>> <mailto:Xsl...@li...>
>>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

Re: [Xsltforms-support] question about conversion from ubiquity

[Chris H. <ch...@el...>]

I attempted to do so.  I don't work on this very often.
But I can see the POST action, and the Firefox console will show me the 
request and the return..
but I don't see any of the POST data.

And the IE debugger doesn't show anything, but I can't get it to show me 
much.

What should I be looking for?




On 1/16/20 11:54 AM, Alain Couthures wrote:
> Hello Chris,
>
> Did you check the HTTP request body with the browser network debugger?
>
> --Alain
>
>> Le 16 janvier 2020 à 13:09, Chris Howard < ch...@el... 
>> <mailto:ch...@el...>> a écrit :
>>
>>
>> Hello,
>>
>> I have run into another issue:
>>
>> I am using a CGI perl script and a submission button which calls the 
>> script.
>> The script gets some data from the POSTDATA and does some actions.
>>
>> My forms using xsltforms library are not sending any POST data.
>> The script is being called, but no data.
>>
>> I tried also with one of the sample forms, substituting in my own perl
>> CGI as the action,
>> still no POST data showing up.
>>
>> Can you give me some pointers as to where I should be looking?
>> Is this an issue with the web server config?  I am not seeing any errors
>> in the
>> log files, just no POST data coming through.
>>
>> Thanks
>>
>> Chris Howard
>>
>>
>>
>>
>> On 1/12/20 7:06 AM, Chris Howard wrote:
>>> Hi,
>>>
>>> I spent some time with the samples and sorted it out.
>>> The big first item was adding xmlns="" in the top-level instance data
>>> tag.
>>> Then I started seeing my instance data.
>>>
>>> Then I worked out some issues with stylesheet (also covered in the
>>> examples).
>>>
>>> I very much appreciate your help!
>>>
>>> Chris
>>>
>>>
>>> On 1/11/20 8:41 AM, Alain Couthures wrote:
>>>> Hello Chris,
>>>>
>>>> As far as I remember, Ubiquity had a limitation about models not to
>>>> be declared in head section but in body section.
>>>>
>>>> I suggest you to first check that XSLTForms samples are OK for you.
>>>> Then, to compare with Ubiquity.
>>>>
>>>> If possible, please don't hesitate to send a full form source.
>>>>
>>>> Thank you for your feedback!
>>>>
>>>> --Alain
>>>>
>>>>
>>>> Le 11/01/2020 à 15:04, Chris Howard a écrit :
>>>> >
>>>>> Update,
>>>>>
>>>>> I have been simplifying my form this morning and even with all of
>>>>> the triggers
>>>>> and events stripped out, I still don't see any of my data.
>>>>>
>>>>>
>>>>>
>>>>> On 1/11/20 7:17 AM, Chris Howard wrote:
>>>>>> Hi,
>>>>>>
>>>>>> Many years ago I worked on a xform which would allow editing of
>>>>>> an XML file. I didn't know a lot about XSLT or XForms but I was
>>>>>> able to cook up something that worked.
>>>>>>
>>>>>> We used the ubiquity library.
>>>>>>
>>>>>> Recently the form quit working.
>>>>>> I am remote from the situation such that I cannot directly debug
>>>>>> the problem.
>>>>>> There are other people working on that.
>>>>>>
>>>>>> I've been given the task of researching a replacement for the
>>>>>> ancient ubiquity library.
>>>>>>
>>>>>> I have the xsltforms package installed on our web server and I can
>>>>>> run some sample forms.
>>>>>> It looks like the xsltforms content is being sent to the browser,
>>>>>> so I think my
>>>>>> basic plumbing is working ok.
>>>>>>
>>>>>> My problem is that our form never seems to activate.  I get the
>>>>>> screen drawn
>>>>>> but none of my DOMActivate events seem to perform.  Also my submit
>>>>>> buttons
>>>>>> do not work. None of my instance data is showing up in the form.
>>>>>>
>>>>>> I am looking for any help or advise that might be available
>>>>>>
>>>>>> My triggers look like this:
>>>>>>
>>>>>>         <xf:trigger bind="detailSpecial">
>>>>>>
>>>>>>                 <xf:label>Insert tax/total Item</xf:label>
>>>>>>
>>>>>>                 <xf:action ev:event="DOMActivate">
>>>>>>
>>>>>>                         <xf:insert
>>>>>> nodeset="/bill/billDetail/detailSpecialSet/detailSpecial"
>>>>>> at="index('repeat-detailSpecial')" position="before"/>
>>>>>>
>>>>>>                         <xf:setvalue
>>>>>> ref="/bill/billDetail/detailSpecialSet/detailSpecial[index('repeat-detailSpecial')]/specialDescription"></xf:setvalue> 
>>>>>>
>>>>>>
>>>>>>                         <xf:setvalue
>>>>>> ref="/bill/billDetail/detailSpecialSet/detailSpecial[index('repeat-detailSpecial')]/charge"></xf:setvalue> 
>>>>>>
>>>>>>
>>>>>>                 </xf:action>
>>>>>>
>>>>>>         </xf:trigger>
>>>>>>
>>>>>>         <xf:trigger bind="detailSpecial">
>>>>>>
>>>>>>                 <xf:label>Delete tax/total Item</xf:label>
>>>>>>
>>>>>>                 <xf:delete ev:event="DOMActivate"
>>>>>> nodeset="/bill/billDetail/detailSpecialSet/detailSpecial"
>>>>>> at="index('repeat-detailSpecial')"/>
>>>>>>
>>>>>>         </xf:trigger>
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Xsltforms-support mailing list
>>>>>> Xsl...@li... 
>>>>>> <mailto:Xsl...@li...>
>>>>>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Xsltforms-support mailing list
>>>>> Xsl...@li... 
>>>>> <mailto:Xsl...@li...>
>>>>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Xsltforms-support mailing list
>>> Xsl...@li... 
>>> <mailto:Xsl...@li...>
>>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>
>>
>>
>> _______________________________________________
>> Xsltforms-support mailing list
>> Xsl...@li... 
>> <mailto:Xsl...@li...>
>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support

Re: [Xsltforms-support] question about conversion from ubiquity

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

<!doctype html>
<html>
 <head> 
  <meta charset="UTF-8"> 
 </head>
 <body>
  <div>
   Hello Chris,
  </div>
  <div>
   <br>
  </div>
  <div>
   Did you check the HTTP request body with the browser network debugger?
  </div>
  <div>
   <br>
  </div>
  <div>
   --Alain
  </div>
  <div>
   <br>
  </div>
  <blockquote type="cite">
   <div>
    Le 16 janvier 2020 à 13:09, Chris Howard &lt;
    <a href="mailto:ch...@el...">ch...@el...</a>&gt; a écrit&nbsp;:
   </div>
   <div>
    <br>
   </div>
   <div>
    <br>
   </div>
   <div>
    Hello,
   </div>
   <div>
    <br>
   </div>
   <div>
    I have run into another issue:
   </div>
   <div>
    <br>
   </div>
   <div>
    I am using a CGI perl script and a submission button which calls the script.
   </div>
   <div>
    The script gets some data from the POSTDATA and does some actions.
   </div>
   <div>
    <br>
   </div>
   <div>
    My forms using xsltforms library are not sending any POST data.
   </div>
   <div>
    The script is being called, but no data.
   </div>
   <div>
    <br>
   </div>
   <div>
    I tried also with one of the sample forms, substituting in my own perl
   </div>
   <div>
    CGI as the action,
   </div>
   <div>
    still no POST data showing up.
   </div>
   <div>
    <br>
   </div>
   <div>
    Can you give me some pointers as to where I should be looking?
   </div>
   <div>
    Is this an issue with the web server config?&nbsp; I am not seeing any errors
   </div>
   <div>
    in the
   </div>
   <div>
    log files, just no POST data coming through.
   </div>
   <div>
    <br>
   </div>
   <div>
    Thanks
   </div>
   <div>
    <br>
   </div>
   <div>
    Chris Howard
   </div>
   <div>
    <br>
   </div>
   <div>
    <br>
   </div>
   <div>
    <br>
   </div>
   <div>
    <br>
   </div>
   <div>
    On 1/12/20 7:06 AM, Chris Howard wrote:
   </div>
   <blockquote type="cite">
    <div>
     Hi,
    </div>
    <div>
     <br>
    </div>
    <div>
     I spent some time with the samples and sorted it out.
    </div>
    <div>
     The big first item was adding xmlns="" in the top-level instance data
    </div>
    <div>
     tag.
    </div>
    <div>
     Then I started seeing my instance data.
    </div>
    <div>
     <br>
    </div>
    <div>
     Then I worked out some issues with stylesheet (also covered in the
    </div>
    <div>
     examples).
    </div>
    <div>
     <br>
    </div>
    <div>
     I very much appreciate your help!
    </div>
    <div>
     <br>
    </div>
    <div>
     Chris
    </div>
    <div>
     <br>
    </div>
    <div>
     <br>
    </div>
    <div>
     On 1/11/20 8:41 AM, Alain Couthures wrote:
    </div>
    <blockquote type="cite">
     <div>
      Hello Chris,
     </div>
     <div>
      <br>
     </div>
     <div>
      As far as I remember, Ubiquity had a limitation about models not to
     </div>
     <div>
      be declared in head section but in body section.
     </div>
     <div>
      <br>
     </div>
     <div>
      I suggest you to first check that XSLTForms samples are OK for you.
     </div>
     <div>
      Then, to compare with Ubiquity.
     </div>
     <div>
      <br>
     </div>
     <div>
      If possible, please don't hesitate to send a full form source.
     </div>
     <div>
      <br>
     </div>
     <div>
      Thank you for your feedback!
     </div>
     <div>
      <br>
     </div>
     <div>
      --Alain
     </div>
     <div>
      <br>
     </div>
     <div>
      <br>
     </div>
     <div>
      Le 11/01/2020 à 15:04, Chris Howard a écrit&nbsp;:
     </div>
     <div>
      &gt;
     </div>
     <blockquote type="cite">
      <div>
       Update,
      </div>
      <div>
       <br>
      </div>
      <div>
       I have been simplifying my form this morning and even with all of
      </div>
      <div>
       the triggers
      </div>
      <div>
       and events stripped out, I still don't see any of my data.
      </div>
      <div>
       <br>
      </div>
      <div>
       <br>
      </div>
      <div>
       <br>
      </div>
      <div>
       On 1/11/20 7:17 AM, Chris Howard wrote:
      </div>
      <blockquote type="cite">
       <div>
        Hi,
       </div>
       <div>
        <br>
       </div>
       <div>
        Many years ago I worked on a xform which would allow editing of
       </div>
       <div>
        an XML file. I didn't know a lot about XSLT or XForms but I was
       </div>
       <div>
        able to cook up something that worked.
       </div>
       <div>
        <br>
       </div>
       <div>
        We used the ubiquity library.
       </div>
       <div>
        <br>
       </div>
       <div>
        Recently the form quit working.
       </div>
       <div>
        I am remote from the situation such that I cannot directly debug
       </div>
       <div>
        the problem.
       </div>
       <div>
        There are other people working on that.
       </div>
       <div>
        <br>
       </div>
       <div>
        I've been given the task of researching a replacement for the
       </div>
       <div>
        ancient ubiquity library.
       </div>
       <div>
        <br>
       </div>
       <div>
        I have the xsltforms package installed on our web server and I can
       </div>
       <div>
        run some sample forms.
       </div>
       <div>
        It looks like the xsltforms content is being sent to the browser,
       </div>
       <div>
        so I think my
       </div>
       <div>
        basic plumbing is working ok.
       </div>
       <div>
        <br>
       </div>
       <div>
        My problem is that our form never seems to activate.&nbsp; I get the
       </div>
       <div>
        screen drawn
       </div>
       <div>
        but none of my DOMActivate events seem to perform.&nbsp; Also my submit
       </div>
       <div>
        buttons
       </div>
       <div>
        do not work. None of my instance data is showing up in the form.
       </div>
       <div>
        <br>
       </div>
       <div>
        I am looking for any help or advise that might be available
       </div>
       <div>
        <br>
       </div>
       <div>
        My triggers look like this:
       </div>
       <div>
        <br>
       </div>
       <div>
        &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xf:trigger bind="detailSpecial"&gt;
       </div>
       <div>
        <br>
       </div>
       <div>
        &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xf:label&gt;Insert tax/total Item&lt;/xf:label&gt;
       </div>
       <div>
        <br>
       </div>
       <div>
        &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xf:action ev:event="DOMActivate"&gt;
       </div>
       <div>
        <br>
       </div>
       <div>
        &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xf:insert
       </div>
       <div>
        nodeset="/bill/billDetail/detailSpecialSet/detailSpecial"
       </div>
       <div>
        at="index('repeat-detailSpecial')" position="before"/&gt;
       </div>
       <div>
        <br>
       </div>
       <div>
        &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xf:setvalue
       </div>
       <div>
        ref="/bill/billDetail/detailSpecialSet/detailSpecial[index('repeat-detailSpecial')]/specialDescription"&gt;&lt;/xf:setvalue&gt;
       </div>
       <div>
        <br>
       </div>
       <div>
        &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xf:setvalue
       </div>
       <div>
        ref="/bill/billDetail/detailSpecialSet/detailSpecial[index('repeat-detailSpecial')]/charge"&gt;&lt;/xf:setvalue&gt;
       </div>
       <div>
        <br>
       </div>
       <div>
        &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/xf:action&gt;
       </div>
       <div>
        <br>
       </div>
       <div>
        &nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/xf:trigger&gt;
       </div>
       <div>
        <br>
       </div>
       <div>
        &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xf:trigger bind="detailSpecial"&gt;
       </div>
       <div>
        <br>
       </div>
       <div>
        &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xf:label&gt;Delete tax/total Item&lt;/xf:label&gt;
       </div>
       <div>
        <br>
       </div>
       <div>
        &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xf:delete ev:event="DOMActivate"
       </div>
       <div>
        nodeset="/bill/billDetail/detailSpecialSet/detailSpecial"
       </div>
       <div>
        at="index('repeat-detailSpecial')"/&gt;
       </div>
       <div>
        <br>
       </div>
       <div>
        &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/xf:trigger&gt;
       </div>
       <div>
        <br>
       </div>
       <div>
        <br>
       </div>
       <div>
        <br>
       </div>
       <div>
        _______________________________________________
       </div>
       <div>
        Xsltforms-support mailing list
       </div>
       <div>
        <a href="mailto:Xsl...@li...">Xsl...@li...</a>
       </div>
       <div>
        <a href="https://lists.sourceforge.net/lists/listinfo/xsltforms-support" rel="noopener" target="_blank">https://lists.sourceforge.net/lists/listinfo/xsltforms-support</a>
       </div>
      </blockquote>
      <div>
       <br>
      </div>
      <div>
       <br>
      </div>
      <div>
       <br>
      </div>
      <div>
       _______________________________________________
      </div>
      <div>
       Xsltforms-support mailing list
      </div>
      <div>
       <a href="mailto:Xsl...@li...">Xsl...@li...</a>
      </div>
      <div>
       <a href="https://lists.sourceforge.net/lists/listinfo/xsltforms-support" rel="noopener" target="_blank">https://lists.sourceforge.net/lists/listinfo/xsltforms-support</a>
      </div>
     </blockquote>
     <div>
      <br>
     </div>
     <div>
      <br>
     </div>
     <div>
      <br>
     </div>
    </blockquote>
    <div>
     <br>
    </div>
    <div>
     <br>
    </div>
    <div>
     <br>
    </div>
    <div>
     _______________________________________________
    </div>
    <div>
     Xsltforms-support mailing list
    </div>
    <div>
     <a href="mailto:Xsl...@li...">Xsl...@li...</a>
    </div>
    <div>
     <a href="https://lists.sourceforge.net/lists/listinfo/xsltforms-support" rel="noopener" target="_blank">https://lists.sourceforge.net/lists/listinfo/xsltforms-support</a>
    </div>
   </blockquote>
   <div>
    <br>
   </div>
   <div>
    <br>
   </div>
   <div>
    <br>
   </div>
   <div>
    _______________________________________________
   </div>
   <div>
    Xsltforms-support mailing list
   </div>
   <div>
    <a href="mailto:Xsl...@li...">Xsl...@li...</a>
   </div>
   <div>
    <a href="https://lists.sourceforge.net/lists/listinfo/xsltforms-support" rel="noopener" target="_blank">https://lists.sourceforge.net/lists/listinfo/xsltforms-support</a>
   </div>
  </blockquote> 
 </body>
</html>

Re: [Xsltforms-support] question about conversion from ubiquity

[Chris H. <ch...@el...>]

Hello,

I have run into another issue:

I am using a CGI perl script and a submission button which calls the script.
The script gets some data from the POSTDATA and does some actions.

My forms using xsltforms library are not sending any POST data.
The script is being called, but no data.

I tried also with one of the sample forms, substituting in my own perl 
CGI as the action,
still no POST data showing up.

Can you give me some pointers as to where I should be looking?
Is this an issue with the web server config?  I am not seeing any errors 
in the
log files, just no POST data coming through.

Thanks

Chris Howard




On 1/12/20 7:06 AM, Chris Howard wrote:
> Hi,
>
> I spent some time with the samples and sorted it out.
> The big first item was adding xmlns="" in the top-level instance data 
> tag.
> Then I started seeing my instance data.
>
> Then I worked out some issues with stylesheet (also covered in the 
> examples).
>
> I very much appreciate your help!
>
> Chris
>
>
> On 1/11/20 8:41 AM, Alain Couthures wrote:
>> Hello Chris,
>>
>> As far as I remember, Ubiquity had a limitation about models not to 
>> be declared in head section but in body section.
>>
>> I suggest you to first check that XSLTForms samples are OK for you. 
>> Then, to compare with Ubiquity.
>>
>> If possible, please don't hesitate to send a full form source.
>>
>> Thank you for your feedback!
>>
>> --Alain
>>
>>
>> Le 11/01/2020 à 15:04, Chris Howard a écrit :
>>>
>>> Update,
>>>
>>> I have been simplifying my form this morning and even with all of 
>>> the triggers
>>> and events stripped out, I still don't see any of my data.
>>>
>>>
>>>
>>> On 1/11/20 7:17 AM, Chris Howard wrote:
>>>> Hi,
>>>>
>>>> Many years ago I worked on a xform which would allow editing of
>>>> an XML file. I didn't know a lot about XSLT or XForms but I was
>>>> able to cook up something that worked.
>>>>
>>>> We used the ubiquity library.
>>>>
>>>> Recently the form quit working.
>>>> I am remote from the situation such that I cannot directly debug 
>>>> the problem.
>>>> There are other people working on that.
>>>>
>>>> I've been given the task of researching a replacement for the 
>>>> ancient ubiquity library.
>>>>
>>>> I have the xsltforms package installed on our web server and I can 
>>>> run some sample forms.
>>>> It looks like the xsltforms content is being sent to the browser, 
>>>> so I think my
>>>> basic plumbing is working ok.
>>>>
>>>> My problem is that our form never seems to activate.  I get the 
>>>> screen drawn
>>>> but none of my DOMActivate events seem to perform.  Also my submit 
>>>> buttons
>>>> do not work. None of my instance data is showing up in the form.
>>>>
>>>> I am looking for any help or advise that might be available
>>>>
>>>> My triggers look like this:
>>>>
>>>>         <xf:trigger bind="detailSpecial">
>>>>
>>>>                 <xf:label>Insert tax/total Item</xf:label>
>>>>
>>>>                 <xf:action ev:event="DOMActivate">
>>>>
>>>>                         <xf:insert 
>>>> nodeset="/bill/billDetail/detailSpecialSet/detailSpecial" 
>>>> at="index('repeat-detailSpecial')" position="before"/>
>>>>
>>>>                         <xf:setvalue 
>>>> ref="/bill/billDetail/detailSpecialSet/detailSpecial[index('repeat-detailSpecial')]/specialDescription"></xf:setvalue>
>>>>
>>>>                         <xf:setvalue 
>>>> ref="/bill/billDetail/detailSpecialSet/detailSpecial[index('repeat-detailSpecial')]/charge"></xf:setvalue>
>>>>
>>>>                 </xf:action>
>>>>
>>>>         </xf:trigger>
>>>>
>>>>         <xf:trigger bind="detailSpecial">
>>>>
>>>>                 <xf:label>Delete tax/total Item</xf:label>
>>>>
>>>>                 <xf:delete ev:event="DOMActivate" 
>>>> nodeset="/bill/billDetail/detailSpecialSet/detailSpecial" 
>>>> at="index('repeat-detailSpecial')"/>
>>>>
>>>>         </xf:trigger>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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] question about conversion from ubiquity

[Chris H. <ch...@el...>]

Hi,

I spent some time with the samples and sorted it out.
The big first item was adding xmlns="" in the top-level instance data tag.
Then I started seeing my instance data.

Then I worked out some issues with stylesheet (also covered in the 
examples).

I very much appreciate your help!

Chris


On 1/11/20 8:41 AM, Alain Couthures wrote:
> Hello Chris,
>
> As far as I remember, Ubiquity had a limitation about models not to be 
> declared in head section but in body section.
>
> I suggest you to first check that XSLTForms samples are OK for you. 
> Then, to compare with Ubiquity.
>
> If possible, please don't hesitate to send a full form source.
>
> Thank you for your feedback!
>
> --Alain
>
>
> Le 11/01/2020 à 15:04, Chris Howard a écrit :
>>
>> Update,
>>
>> I have been simplifying my form this morning and even with all of the 
>> triggers
>> and events stripped out, I still don't see any of my data.
>>
>>
>>
>> On 1/11/20 7:17 AM, Chris Howard wrote:
>>> Hi,
>>>
>>> Many years ago I worked on a xform which would allow editing of
>>> an XML file. I didn't know a lot about XSLT or XForms but I was
>>> able to cook up something that worked.
>>>
>>> We used the ubiquity library.
>>>
>>> Recently the form quit working.
>>> I am remote from the situation such that I cannot directly debug the 
>>> problem.
>>> There are other people working on that.
>>>
>>> I've been given the task of researching a replacement for the 
>>> ancient ubiquity library.
>>>
>>> I have the xsltforms package installed on our web server and I can 
>>> run some sample forms.
>>> It looks like the xsltforms content is being sent to the browser, so 
>>> I think my
>>> basic plumbing is working ok.
>>>
>>> My problem is that our form never seems to activate.  I get the 
>>> screen drawn
>>> but none of my DOMActivate events seem to perform.  Also my submit 
>>> buttons
>>> do not work. None of my instance data is showing up in the form.
>>>
>>> I am looking for any help or advise that might be available
>>>
>>> My triggers look like this:
>>>
>>>         <xf:trigger bind="detailSpecial">
>>>
>>>                 <xf:label>Insert tax/total Item</xf:label>
>>>
>>>                 <xf:action ev:event="DOMActivate">
>>>
>>>                         <xf:insert 
>>> nodeset="/bill/billDetail/detailSpecialSet/detailSpecial" 
>>> at="index('repeat-detailSpecial')" position="before"/>
>>>
>>>                         <xf:setvalue 
>>> ref="/bill/billDetail/detailSpecialSet/detailSpecial[index('repeat-detailSpecial')]/specialDescription"></xf:setvalue>
>>>
>>>                         <xf:setvalue 
>>> ref="/bill/billDetail/detailSpecialSet/detailSpecial[index('repeat-detailSpecial')]/charge"></xf:setvalue>
>>>
>>>                 </xf:action>
>>>
>>>         </xf:trigger>
>>>
>>>         <xf:trigger bind="detailSpecial">
>>>
>>>                 <xf:label>Delete tax/total Item</xf:label>
>>>
>>>                 <xf:delete ev:event="DOMActivate" 
>>> nodeset="/bill/billDetail/detailSpecialSet/detailSpecial" 
>>> at="index('repeat-detailSpecial')"/>
>>>
>>>         </xf:trigger>
>>>
>>>
>>>
>>> _______________________________________________
>>> 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] question about conversion from ubiquity

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

Hello Chris,

As far as I remember, Ubiquity had a limitation about models not to be 
declared in head section but in body section.

I suggest you to first check that XSLTForms samples are OK for you. 
Then, to compare with Ubiquity.

If possible, please don't hesitate to send a full form source.

Thank you for your feedback!

--Alain


Le 11/01/2020 à 15:04, Chris Howard a écrit :
>
> Update,
>
> I have been simplifying my form this morning and even with all of the 
> triggers
> and events stripped out, I still don't see any of my data.
>
>
>
> On 1/11/20 7:17 AM, Chris Howard wrote:
>> Hi,
>>
>> Many years ago I worked on a xform which would allow editing of
>> an XML file. I didn't know a lot about XSLT or XForms but I was
>> able to cook up something that worked.
>>
>> We used the ubiquity library.
>>
>> Recently the form quit working.
>> I am remote from the situation such that I cannot directly debug the 
>> problem.
>> There are other people working on that.
>>
>> I've been given the task of researching a replacement for the ancient 
>> ubiquity library.
>>
>> I have the xsltforms package installed on our web server and I can 
>> run some sample forms.
>> It looks like the xsltforms content is being sent to the browser, so 
>> I think my
>> basic plumbing is working ok.
>>
>> My problem is that our form never seems to activate.  I get the 
>> screen drawn
>> but none of my DOMActivate events seem to perform.  Also my submit 
>> buttons
>> do not work. None of my instance data is showing up in the form.
>>
>> I am looking for any help or advise that might be available
>>
>> My triggers look like this:
>>
>>         <xf:trigger bind="detailSpecial">
>>
>>                 <xf:label>Insert tax/total Item</xf:label>
>>
>>                 <xf:action ev:event="DOMActivate">
>>
>>                         <xf:insert 
>> nodeset="/bill/billDetail/detailSpecialSet/detailSpecial" 
>> at="index('repeat-detailSpecial')" position="before"/>
>>
>>                         <xf:setvalue 
>> ref="/bill/billDetail/detailSpecialSet/detailSpecial[index('repeat-detailSpecial')]/specialDescription"></xf:setvalue>
>>
>>                         <xf:setvalue 
>> ref="/bill/billDetail/detailSpecialSet/detailSpecial[index('repeat-detailSpecial')]/charge"></xf:setvalue>
>>
>>                 </xf:action>
>>
>>         </xf:trigger>
>>
>>         <xf:trigger bind="detailSpecial">
>>
>>                 <xf:label>Delete tax/total Item</xf:label>
>>
>>                 <xf:delete ev:event="DOMActivate" 
>> nodeset="/bill/billDetail/detailSpecialSet/detailSpecial" 
>> at="index('repeat-detailSpecial')"/>
>>
>>         </xf:trigger>
>>
>>
>>
>> _______________________________________________
>> 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] question about conversion from ubiquity

[Chris H. <ch...@el...>]

Update,

I have been simplifying my form this morning and even with all of the 
triggers
and events stripped out, I still don't see any of my data.



On 1/11/20 7:17 AM, Chris Howard wrote:
> Hi,
>
> Many years ago I worked on a xform which would allow editing of
> an XML file. I didn't know a lot about XSLT or XForms but I was
> able to cook up something that worked.
>
> We used the ubiquity library.
>
> Recently the form quit working.
> I am remote from the situation such that I cannot directly debug the 
> problem.
> There are other people working on that.
>
> I've been given the task of researching a replacement for the ancient 
> ubiquity library.
>
> I have the xsltforms package installed on our web server and I can run 
> some sample forms.
> It looks like the xsltforms content is being sent to the browser, so I 
> think my
> basic plumbing is working ok.
>
> My problem is that our form never seems to activate.  I get the screen 
> drawn
> but none of my DOMActivate events seem to perform.  Also my submit 
> buttons
> do not work. None of my instance data is showing up in the form.
>
> I am looking for any help or advise that might be available
>
> My triggers look like this:
>
>         <xf:trigger bind="detailSpecial">
>
>                 <xf:label>Insert tax/total Item</xf:label>
>
>                 <xf:action ev:event="DOMActivate">
>
>                         <xf:insert 
> nodeset="/bill/billDetail/detailSpecialSet/detailSpecial" 
> at="index('repeat-detailSpecial')" position="before"/>
>
>                         <xf:setvalue 
> ref="/bill/billDetail/detailSpecialSet/detailSpecial[index('repeat-detailSpecial')]/specialDescription"></xf:setvalue>
>
>                         <xf:setvalue 
> ref="/bill/billDetail/detailSpecialSet/detailSpecial[index('repeat-detailSpecial')]/charge"></xf:setvalue>
>
>                 </xf:action>
>
>         </xf:trigger>
>
>         <xf:trigger bind="detailSpecial">
>
>                 <xf:label>Delete tax/total Item</xf:label>
>
>                 <xf:delete ev:event="DOMActivate" 
> nodeset="/bill/billDetail/detailSpecialSet/detailSpecial" 
> at="index('repeat-detailSpecial')"/>
>
>         </xf:trigger>
>
>
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support

[Xsltforms-support] question about conversion from ubiquity

[Chris H. <ch...@el...>]

Hi,

Many years ago I worked on a xform which would allow editing of
an XML file. I didn't know a lot about XSLT or XForms but I was
able to cook up something that worked.

We used the ubiquity library.

Recently the form quit working.
I am remote from the situation such that I cannot directly debug the 
problem.
There are other people working on that.

I've been given the task of researching a replacement for the ancient 
ubiquity library.

I have the xsltforms package installed on our web server and I can run 
some sample forms.
It looks like the xsltforms content is being sent to the browser, so I 
think my
basic plumbing is working ok.

My problem is that our form never seems to activate.  I get the screen drawn
but none of my DOMActivate events seem to perform.  Also my submit buttons
do not work. None of my instance data is showing up in the form.

I am looking for any help or advise that might be available

My triggers look like this:

         <xf:trigger bind="detailSpecial">

                 <xf:label>Insert tax/total Item</xf:label>

                 <xf:action ev:event="DOMActivate">

                         <xf:insert 
nodeset="/bill/billDetail/detailSpecialSet/detailSpecial" 
at="index('repeat-detailSpecial')" position="before"/>

                         <xf:setvalue 
ref="/bill/billDetail/detailSpecialSet/detailSpecial[index('repeat-detailSpecial')]/specialDescription"></xf:setvalue>

                         <xf:setvalue 
ref="/bill/billDetail/detailSpecialSet/detailSpecial[index('repeat-detailSpecial')]/charge"></xf:setvalue>

                 </xf:action>

         </xf:trigger>

         <xf:trigger bind="detailSpecial">

                 <xf:label>Delete tax/total Item</xf:label>

                 <xf:delete ev:event="DOMActivate" 
nodeset="/bill/billDetail/detailSpecialSet/detailSpecial" 
at="index('repeat-detailSpecial')"/>

         </xf:trigger>

Re: [Xsltforms-support] Reenviar: XForms trigger on svg elements

[Jorge S. <jo...@vi...>]

Hi Tim, 



This is exactly what I was asking for. Found a workaround, but I wanted to do it in the right way. 


Kind Regards.
Enviar: martes 24 de septiembre de 2019 a las 3:41

De: "Tim Thompson" <mailto:tim...@gm...>

Para: "Jorge sr" <mailto:xu...@gm...>

CC: mailto:Xsl...@li...

Asunto: Re: [Xsltforms-support] Reenviar: XForms trigger on svg elements


Sorry--this is not a feature I use as often as I should! The SVG "g" element can be the observer, but the event phase needs to be declared as "capture."



<dispatch ev:observer="my-g" ev:event="DOMActivate" ev:phase="capture" targetid="m" name="svg-g-trigger"/>






--

Tim A. Thompson

Discovery Metadata Librarian

Yale University Library

mailto:tim...@ya...







On Mon, Sep 23, 2019 at 9:34 PM Tim Thompson <mailto:tim...@gm...> wrote:

Hi, Jorge,



I may be missing something, but I think this should be possible just by declaring an SVG element to be an observer of the DOMActivate event. For example:



<dispatch ev:observer="my-circle" ev:event="DOMActivate" targetid="m" name="svg-circle-trigger"/>



See this page for a working example: https://www.tat2.io/basex/svg-test



Here, I have an SVG "circle" and "text" element within a "g" element. I had to make each of the child elements observers. I tried making the containing "g" element the observer, but that didn't seem to work. Any ideas why not?



Is this close to what you were looking for?



Best regards,

Tim





--

Tim A. Thompson

Discovery Metadata Librarian

Yale University Library

mailto:tim...@ya...







On Mon, Sep 23, 2019 at 3:25 PM Jorge sr <mailto:xu...@gm...> wrote:





Hi, 



I want to add a trigger to an svg on a form based on Xsltforms. For now I managed to launch the submissions with the following call from an onclick. 



XsltForms_xmlevents.dispatch(document.getElementById("actual-trigger-id"),"DOMActivate")

This has two obvious disadvantages. First, it is not a proper XForms solution and is coupled to the framework. The second one is that at any time an update in the xsltforms may break the solution. 

Is there a "good way" to add a trigger to an svg element in XForms?

Kind Regards, 

Jorge Sánchez 

@Alain thanks in advance, amazing work ;) 










_______________________________________________

Xsltforms-support mailing list

mailto:Xsl...@li...

https://lists.sourceforge.net/lists/listinfo/xsltforms-support

Re: [Xsltforms-support] Reenviar: XForms trigger on svg elements

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

Sorry--this is not a feature I use as often as I should! The SVG "g"
element can be the observer, but the event phase needs to be declared as
"capture."

<dispatch ev:observer="my-g" ev:event="DOMActivate" ev:phase="capture"
targetid="m" name="svg-g-trigger"/>


--
Tim A. Thompson
Discovery Metadata Librarian
Yale University Library
tim...@ya...


On Mon, Sep 23, 2019 at 9:34 PM Tim Thompson <tim...@gm...> wrote:

> Hi, Jorge,
>
> I may be missing something, but I think this should be possible just by
> declaring an SVG element to be an observer of the DOMActivate event. For
> example:
>
> <dispatch ev:observer="my-circle" ev:event="DOMActivate" targetid="m" name
> ="svg-circle-trigger"/>
>
> See this page for a working example: https://www.tat2.io/basex/svg-test
>
> Here, I have an SVG "circle" and "text" element within a "g" element. I
> had to make each of the child elements observers. I tried making the
> containing "g" element the observer, but that didn't seem to work. Any
> ideas why not?
>
> Is this close to what you were looking for?
>
> Best regards,
> Tim
>
>
> --
> Tim A. Thompson
> Discovery Metadata Librarian
> Yale University Library
> tim...@ya...
>
>
> On Mon, Sep 23, 2019 at 3:25 PM Jorge sr <xu...@gm...> wrote:
>
>>
>>
>> Hi,
>>
>> I want to add a trigger to an svg on a form based on Xsltforms. For now I
>> managed to launch the submissions with the following call from an onclick.
>>
>>
>> XsltForms_xmlevents.dispatch(document.getElementById("actual-trigger-id"),"DOMActivate")
>>
>> This has two obvious disadvantages. First, it is not a proper XForms
>> solution and is coupled to the framework. The second one is that at any
>> time an update in the xsltforms may break the solution.
>>
>> Is there a "good way" to add a trigger to an svg element in XForms?
>>
>> Kind Regards,
>>
>> Jorge Sánchez
>>
>> @Alain thanks in advance, amazing work ;)
>> _______________________________________________
>> Xsltforms-support mailing list
>> Xsl...@li...
>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>
>

Re: [Xsltforms-support] Reenviar: XForms trigger on svg elements

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

Hi, Jorge,

I may be missing something, but I think this should be possible just by
declaring an SVG element to be an observer of the DOMActivate event. For
example:

<dispatch ev:observer="my-circle" ev:event="DOMActivate" targetid="m" name="
svg-circle-trigger"/>

See this page for a working example: https://www.tat2.io/basex/svg-test

Here, I have an SVG "circle" and "text" element within a "g" element. I had
to make each of the child elements observers. I tried making the containing
"g" element the observer, but that didn't seem to work. Any ideas why not?

Is this close to what you were looking for?

Best regards,
Tim


--
Tim A. Thompson
Discovery Metadata Librarian
Yale University Library
tim...@ya...


On Mon, Sep 23, 2019 at 3:25 PM Jorge sr <xu...@gm...> wrote:

>
>
> Hi,
>
> I want to add a trigger to an svg on a form based on Xsltforms. For now I
> managed to launch the submissions with the following call from an onclick.
>
>
> XsltForms_xmlevents.dispatch(document.getElementById("actual-trigger-id"),"DOMActivate")
>
> This has two obvious disadvantages. First, it is not a proper XForms
> solution and is coupled to the framework. The second one is that at any
> time an update in the xsltforms may break the solution.
>
> Is there a "good way" to add a trigger to an svg element in XForms?
>
> Kind Regards,
>
> Jorge Sánchez
>
> @Alain thanks in advance, amazing work ;)
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

[Xsltforms-support] Reenviar: XForms trigger on svg elements

[Jorge s. <xu...@gm...>]

<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>
<div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">&nbsp;
<div name="quoted-content">
<div style="font-family: Verdana;font-size: 12.0px;">
<div>&nbsp;</div>

<div>
<div>Hi,&nbsp;</div>

<div>&nbsp;</div>

<div>I want to add a trigger to an svg on a form based on Xsltforms. For now I managed to launch the submissions with the following call from an onclick.&nbsp;</div>

<div>&nbsp;</div>

<div>
<div>XsltForms_xmlevents.dispatch(document.getElementById(&quot;actual-trigger-id&quot;),&quot;DOMActivate&quot;)</div>

<div>
<p>This has two obvious disadvantages. First, it is not a proper XForms solution and is coupled to the framework. The second one is that at any time an update in the xsltforms may break the solution.&nbsp;</p>

<p>Is there a &quot;good way&quot; to add a trigger to an svg element in XForms?</p>

<p>Kind Regards,&nbsp;</p>

<p>Jorge S&aacute;nchez&nbsp;</p>

<p>@Alain thanks in advance, amazing work ;)&nbsp;</p>
</div>
</div>
</div>
</div>
</div>
</div>
</div></div></body></html>

Re: [Xsltforms-support] Open selection

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

Hello Tim,

Yes, open selection is not yet supported and using HTML5 autocompletion 
has already been tested as a workaround for XSLTForms.

Version 1.5 will reconsider how XForms controls are converted into HTML5 
elements and Javascript should do this instead of XSLT. It will be a 
good opportunity to continue implementing open selection.

Regards,

--Alain

Le 06/09/2019 à 03:47, Tim Thompson a écrit :
> Hello, Alain,
>
> I see that HTML5 datalist with "selection='open'" has been 
> (partially?) implemented in XSLTForms (I am using version 1.4). Is 
> this a working feature, or is it still being tested? Based on my 
> initial tests, I assume it hasn't been fully implemented yet, but I 
> thought I would ask :)
>
> Best regards,
> Tim
>
> --
> Tim A. Thompson
> Discovery Metadata Librarian
> Yale University Library
>
>
>
> On Sat, Mar 30, 2019 at 6:41 AM Alain Couthures 
> <ala...@ag... <mailto:ala...@ag...>> 
> wrote:
>
>     Hi Emmanuel,
>
>     Actually, HTML5 datalist does really sound like XForms open
>     select, because the associated input allows to enter a new value!
>
>     I will experiment this soon in XSLTForms.
>
>     Thank you for pointing at this!
>
>     --Alain
>
>     Le 22/03/2019 à 05:52, Chateau Dutier Emmanuel a écrit :
>>     Thanks a lot for your kind answer.
>>
>>     Do you ask if I’m in a hurry considering the fact I’would have to
>>     wait for HTML6 ? ;)
>>
>>     I’ve seen the WikipediaSearch for autocompletion, didn’t get all
>>     the details. By the way, what would be the recommend way to deal
>>     with autocompletion in XForms since HTML5 introduced it ?
>>
>>     Best regards,
>>     Emmanuel
>>
>>     *
>>     Emmanuel Château-Dutier*
>>     Professeur adjoint
>>
>>     *Faculté des arts et sciences,*
>>     Département d’histoire de l’art et d’études cinématographiques
>>
>>     *Université de Montréal*
>>     Pavillon Lionel-Groulx, Bureau C-2067
>>     3200, av. Jean-Brillant, Montréal QC
>>     C.P. 6128, succursale Centre-ville, Montréal QC H3C 3J7
>>
>>     Tél.  +1 514 343-6026
>>     emm...@um...
>>     <mailto:emm...@um...> | @emchateau
>>
>>>     Le 18 mars 2019 à 04:29, Alain Couthures
>>>     <ala...@ag...
>>>     <mailto:ala...@ag...>> a écrit :
>>>
>>>     Hello Emmanuel,
>>>
>>>     Unfortunately, HTML5 is not providing a native solution for some
>>>     open selection ready to be used by XSLTForms.
>>>
>>>     It is still possible to add this to XSLTForms with multiple HTML
>>>     elements and CSS classes. Did you already have a look at this
>>>     example: http://www.agencexml.com/xsltforms/wikipediasearch.xml?
>>>     As you can see, I am not a CSS expert...
>>>
>>>     Are you in a hurry for open selection?
>>>
>>>     Thanks!
>>>
>>>     --Alain
>>>
>>>     Le 15/03/2019 à 19:29, Chateau Dutier Emmanuel a écrit :
>>>>     Hi,
>>>>
>>>>     We are currently working avec XForms and we really enjoy it !
>>>>     Thanks a lot.
>>>>
>>>>     We couldn’t manage to use the open selection. Is it that we
>>>>     didn’t declare it properly or is it not supported ?
>>>>     In 2010, you answered that it wasn’t supported yet
>>>>     https://sourceforge.net/p/xsltforms/mailman/message/24465876/
>>>>
>>>>     Best regards,
>>>>
>>>>     *
>>>>     Emmanuel Château-Dutier*
>>>>     Professeur adjoint
>>>>
>>>>     *Faculté des arts et sciences,*
>>>>     Département d’histoire de l’art et d’études cinématographiques
>>>>
>>>>     *Université de Montréal*
>>>>     Pavillon Lionel-Groulx, Bureau C-2067
>>>>     3200, av. Jean-Brillant, Montréal QC
>>>>     C.P. 6128, succursale Centre-ville, Montréal QC H3C 3J7
>>>>
>>>>
>>>>
>>>>     _______________________________________________
>>>>     Xsltforms-support mailing list
>>>>     Xsl...@li...  <mailto:Xsl...@li...>
>>>>     https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>>
>>>
>>>     _______________________________________________
>>>     Xsltforms-support mailing list
>>>     Xsl...@li...
>>>     <mailto:Xsl...@li...>
>>>     https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>
>
>     _______________________________________________
>     Xsltforms-support mailing list
>     Xsl...@li...
>     <mailto:Xsl...@li...>
>     https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

Re: [Xsltforms-support] Open selection

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

I've been thinking about how best to do this in the absence of native HTML  
support, and you can see my tests for select1 here:

   https://homepages.cwi.nl/~steven/forms/tests/open-select.xhtml

I think example 4 best matches what is required, though perhaps "*other*"  
is not the ideal choice of label. However, it seems to need little extra  
support, and does what it is meant to.

I realise <select/> is more work, and I shall continue to think about that  
case.

Steven

On Fri, 15 Mar 2019 19:29:01 +0100, Chateau Dutier Emmanuel  
<emm...@um...> wrote:

> Hi,
>
> We are currently working avec XForms and we really enjoy it ! Thanks a  
> lot.
>
> We couldn’t manage to use the open selection. Is it that we didn’t  
> declare it properly or is it not supported ?
> In 2010, you answered that it wasn’t supported yet  
> https://sourceforge.net/p/xsltforms/mailman/message/24465876/
>
> Best regards,
>
>
>> Emmanuel Château-Dutier
> Professeur adjoint
>
> Faculté des arts et sciences,
> Département d’histoire de l’art et d’études cinématographiques
>
> Université de Montréal
> Pavillon Lionel-Groulx, Bureau C-2067
> 3200, av. Jean-Brillant, Montréal QC
> C.P. 6128, succursale Centre-ville, Montréal QC H3C 3J7

Re: [Xsltforms-support] Open selection

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

Hello, Alain,

I see that HTML5 datalist with "selection='open'" has been (partially?)
implemented in XSLTForms (I am using version 1.4). Is this a working
feature, or is it still being tested? Based on my initial tests, I assume
it hasn't been fully implemented yet, but I thought I would ask :)

Best regards,
Tim

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



On Sat, Mar 30, 2019 at 6:41 AM Alain Couthures <
ala...@ag...> wrote:

> Hi Emmanuel,
>
> Actually, HTML5 datalist does really sound like XForms open select,
> because the associated input allows to enter a new value!
>
> I will experiment this soon in XSLTForms.
>
> Thank you for pointing at this!
>
> --Alain
>
> Le 22/03/2019 à 05:52, Chateau Dutier Emmanuel a écrit :
>
> Thanks a lot for your kind answer.
>
> Do you ask if I’m in a hurry considering the fact I’would have to wait for
> HTML6 ? ;)
>
> I’ve seen the WikipediaSearch for autocompletion, didn’t get all the
> details. By the way, what would be the recommend way to deal with
> autocompletion in XForms since HTML5 introduced it ?
>
> Best regards,
> Emmanuel
>
>
> * Emmanuel Château-Dutier*
> Professeur adjoint
>
> *Faculté des arts et sciences,*
> Département d’histoire de l’art et d’études cinématographiques
>
> *Université de Montréal*
> Pavillon Lionel-Groulx, Bureau C-2067
> 3200, av. Jean-Brillant, Montréal QC
> C.P. 6128, succursale Centre-ville, Montréal QC H3C 3J7
>
> Tél.  +1 514 343-6026
> emm...@um... | @emchateau
>
> Le 18 mars 2019 à 04:29, Alain Couthures <ala...@ag...>
> a écrit :
>
> Hello Emmanuel,
>
> Unfortunately, HTML5 is not providing a native solution for some open
> selection ready to be used by XSLTForms.
>
> It is still possible to add this to XSLTForms with multiple HTML elements
> and CSS classes. Did you already have a look at this example:
> http://www.agencexml.com/xsltforms/wikipediasearch.xml? As you can see, I
> am not a CSS expert...
>
> Are you in a hurry for open selection?
>
> Thanks!
>
> --Alain
>
> Le 15/03/2019 à 19:29, Chateau Dutier Emmanuel a écrit :
>
> Hi,
>
> We are currently working avec XForms and we really enjoy it ! Thanks a lot.
>
> We couldn’t manage to use the open selection. Is it that we didn’t declare
> it properly or is it not supported ?
> In 2010, you answered that it wasn’t supported yet
> https://sourceforge.net/p/xsltforms/mailman/message/24465876/
>
> Best regards,
>
>
> * Emmanuel Château-Dutier*
> Professeur adjoint
>
> *Faculté des arts et sciences,*
> Département d’histoire de l’art et d’études cinématographiques
>
> *Université de Montréal*
> Pavillon Lionel-Groulx, Bureau C-2067
> 3200, av. Jean-Brillant, Montréal QC
> C.P. 6128, succursale Centre-ville, Montréal QC H3C 3J7
>
>
>
> _______________________________________________
> Xsltforms-support mailing lis...@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] Fwd: XForms and Web sockets

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

Thank you for considering this, Alain--it would be a powerful feature to
add to XSLTForms!

I remember that Mark Lawson did a nice demo, adding a small amount of
custom JavaScript, to enable push notifications in XSLTForms using MQTT:

Code: https://github.com/Tingenek/xml-amsterdam-2015
Blog: https://tingenek.wordpress.com/category/mqtt/


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

On Thu, Aug 1, 2019 at 12:21 PM Alain Couthures <
ala...@ag...> wrote:

> Hello,
>
> Web sockets support in XSLTForms could be interesting, don't you think?
>
> It could probably be implemented at instance level, maybe with a specific
> scheme, such as "ws://".
>
> Thank you for sharing links and ideas!
>
> --Alain
>
>
> -------- Message transféré --------
> Sujet : XForms and Web sockets
> Date de renvoi : Thu, 01 Aug 2019 15:42:24 +0000
> De (renvoi) : pub...@w3...
> Date : Thu, 1 Aug 2019 11:41:52 -0400
> De : C. M. Sperberg-McQueen <cm...@bl...>
> <cm...@bl...>
> Pour : XForms <pub...@w3...> <pub...@w3...>
> Copie à : C. M. Sperberg-McQueen <cm...@bl...>
> <cm...@bl...>
>
> At the Balisage conference yesterday, there was an interesting
> paper [1] by Zahra Al-Awadai, Anne Brüggemann-Klein, Christina Grubmüller,
> and Philipp Ulrich of the TU Munich about using the XML technology stack to
> create graphical user interfaces;
> among other things, they discussed contexts which require the
> server to push information to the client in a way that does not
> jibe easily with the statelessness of HTTP.
>
> [1]
> https://www.balisage.net/Proceedings/vol23/html/Bruggemann-Klein01/BalisageVol23-Bruggemann-Klein01.html
>
> Philipp Ulrich reported in particular on work towards encapsulating
> the web sockets functionality of current browsers into an XML
> element which provides a declarative packaging for the web sockets
> the team need for their server-push functionality.
>
> Afterwards (and again in discussion this morning), John Boyer
> and the authors and I got interested in whether and how it would
> be possible to integrate this kind of functionality into XForms.
> (The current work is independent of earlier work at TUM which
> used XForms, and the web-socket element is not currently
> integrated into any XForms environment.)
>
> Much of the existing machinery of XForms is relevant here and
> could be reused.
> The web socket could of course raise an XForms event when
> it receives a message from the server; since the message may be
> XML, I might want it to update or be appended to an instance
> in my model (which seems to make the web socket behave a bit
> like a submission which is triggered not by a user action but by an event
> of some other kind.
>
> I hope that the WG (and implementors!) will be interested and will take
> some time to consider whether web sockets could be integrated into the
> spec.
>
> ********************************************
> C. M. Sperberg-McQueen
> Black Mesa Technologies LLC
> cm...@bl...
> http://www.blackmesatech.com
> ********************************************
>
>
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

[Xsltforms-support] Fwd: XForms and Web sockets

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

Hello,

Web sockets support in XSLTForms could be interesting, don't you think?

It could probably be implemented at instance level, maybe with a 
specific scheme, such as "ws://".

Thank you for sharing links and ideas!

--Alain



-------- Message transféré --------
Sujet : 	XForms and Web sockets
Date de renvoi : 	Thu, 01 Aug 2019 15:42:24 +0000
De (renvoi) : 	pub...@w3...
Date : 	Thu, 1 Aug 2019 11:41:52 -0400
De : 	C. M. Sperberg-McQueen <cm...@bl...>
Pour : 	XForms <pub...@w3...>
Copie à : 	C. M. Sperberg-McQueen <cm...@bl...>



At the Balisage conference yesterday, there was an interesting
paper [1] by Zahra Al-Awadai, Anne Brüggemann-Klein, Christina 
Grubmüller, and Philipp Ulrich of the TU Munich about using the XML 
technology stack to create graphical user interfaces;
among other things, they discussed contexts which require the
server to push information to the client in a way that does not
jibe easily with the statelessness of HTTP.

[1] 
https://www.balisage.net/Proceedings/vol23/html/Bruggemann-Klein01/BalisageVol23-Bruggemann-Klein01.html

Philipp Ulrich reported in particular on work towards encapsulating
the web sockets functionality of current browsers into an XML
element which provides a declarative packaging for the web sockets
the team need for their server-push functionality.

Afterwards (and again in discussion this morning), John Boyer
and the authors and I got interested in whether and how it would
be possible to integrate this kind of functionality into XForms.
(The current work is independent of earlier work at TUM which
used XForms, and the web-socket element is not currently
integrated into any XForms environment.)

Much of the existing machinery of XForms is relevant here and
could be reused.
The web socket could of course raise an XForms event when
it receives a message from the server; since the message may be
XML, I might want it to update or be appended to an instance
in my model (which seems to make the web socket behave a bit
like a submission which is triggered not by a user action but by an 
event of some other kind.

I hope that the WG (and implementors!) will be interested and will take 
some time to consider whether web sockets could be integrated into the 
spec.

********************************************
C. M. Sperberg-McQueen
Black Mesa Technologies LLC
cm...@bl...
http://www.blackmesatech.com
********************************************

Re: [Xsltforms-support] Error handling and display

[Robert K. <ro...@er...>]

I restarted from a BaseX-supplied example, here-attached, which works as
expected.
It uses a <bind nodeset="..." /> definition.
Considering nodeset as deprecated in XF2.0 , I changed it to ref, then the
demo fails ! (in a bizarre way).

This asks 2 questions:

   - What is the XF version supported by XsltForms: 1.1 + some 2.0?
   - Can you reproduce this behaviour (in a non-BaseX system)?

TIA,
Best regards,
Robert.

On Thu, May 2, 2019 at 9:55 AM Steven Pemberton <ste...@cw...>
wrote:

> If I were you I would comment parts out, and try to locate what is causing
> the problem.
>
> Steven
>
>
> On Wed, 01 May 2019 17:40:49 +0200, Robert Kirkpatrick <ro...@er...>
> wrote:
>
> Additional point:
> My test relies on a BaseX http server, as you can see from the xsltforms
> url (port 8984).
> This should not make a difference, but well a variation with the tests you
> made.
> Regards,
> Robert.
>
> On Wed, May 1, 2019 at 2:58 PM Robert Kirkpatrick <ro...@er...>
> wrote:
>
>> Very strange.
>> I'm using Chrome Version 73.0.3683.103
>>
>> On Wed, May 1, 2019 at 12:58 PM Steven Pemberton <ste...@cw...>
>> wrote:
>>
>>> On Tue, 30 Apr 2019 19:29:39 +0200, Robert Kirkpatrick <
>>> ro...@er...> wrote:
>>>
>>> Thank you Steven.
>>>
>>> Indeed type errors show up clearly. But in my example, the displayed
>>> values were not typed in via the form, but defined in the <instance/> as
>>> default values: ? for item, 0 for amount.
>>> And very weirdly, they are output *concatenated* in *both* form fields
>>> !!
>>> An X error flag indicates a problem, not surprising, but totally blind..
>>> !?
>>>
>>>
>>> I ran your test in 4 different browsers, and didn't get this problem.
>>>
>>> Steven
>>>
>>>
>>>
>>> Robert.
>>>
>>> On Tue, Apr 30, 2019 at 2:14 PM Steven Pemberton <
>>> ste...@cw...> wrote:
>>>
>>>> On Tue, 30 Apr 2019 11:35:47 +0200, Robert Kirkpatrick <
>>>> ro...@er...> wrote:
>>>>
>>>> (Newcomer first post)
>>>>
>>>> Hello,
>>>>
>>>> Here is a basic Xform:
>>>> [image: image.png]
>>>>
>>>> When I hover over the error flags, I only get a little question mark.
>>>> What can I do to display the error associated with the event, which I
>>>> can't identify?
>>>>
>>>> As far as I recall, you only get the red X if the value doesn't match
>>>> the node's type or constraints.
>>>>
>>>> I don't understand why you are getting an X for Item, because that's a
>>>> string; amount is an integer, and ?0 is not a valid integer value, so
>>>> that's why you are getting it there.
>>>>
>>>> To get a message to show, you need to include an <alert/> element in
>>>> the input; for instance
>>>>
>>>>    <xf:label>Amount:</xf:label><xf:alert>Must be an integer</xf:alert>
>>>>
>>>>
>>>> There must be some binding mistake in the form, here attached, but the
>>>> messages associated with xforms-binding-error are not displayed.
>>>>
>>>> The bindings are fine. If there were a binding error, the control would
>>>> not show up.
>>>>
>>>> Hope this helps somewhat.
>>>>
>>>> Steven
>>>>
>>>>
>>>> Thanks for any help,
>>>> Robert.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>
>
>

Re: [Xsltforms-support] Error handling and display

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

If I were you I would comment parts out, and try to locate what is causing  
the problem.

Steven


On Wed, 01 May 2019 17:40:49 +0200, Robert Kirkpatrick <ro...@er...>  
wrote:

> Additional point:
> My test relies on a BaseX http server, as you can see from the xsltforms  
> url (port 8984).
> This should not make a difference, but well a variation with the tests  
> you made.
> Regards,
> Robert.
>
> On Wed, May 1, 2019 at 2:58 PM Robert Kirkpatrick <ro...@er...>  
> wrote:
>> Very strange.
>> I'm using Chrome Version 73.0.3683.103
>>
>> On Wed, May 1, 2019 at 12:58 PM Steven Pemberton  
>> <ste...@cw...> wrote:
>>> On Tue, 30 Apr 2019 19:29:39 +0200, Robert Kirkpatrick  
>>> <ro...@er...> wrote:
>>>
>>>> Thank you Steven.
>>>>
>>>> Indeed type errors show up clearly. But in my example, the displayed  
>>>> values were not typed in via the form, but defined in the <instance/>  
>>>> as default values: ? for item, >>>>0 for amount.
>>>> And very weirdly, they are output concatenated in both form fields !!
>>>> An X error flag indicates a problem, not surprising, but totally  
>>>> blind.. !?
>>>
>>> I ran your test in 4 different browsers, and didn't get this problem.
>>>
>>> Steven
>>>
>>>
>>>>
>>>> Robert.
>>>>
>>>> On Tue, Apr 30, 2019 at 2:14 PM Steven Pemberton  
>>>> <ste...@cw...> wrote:
>>>>> On Tue, 30 Apr 2019 11:35:47 +0200, Robert Kirkpatrick  
>>>>> <ro...@er...> wrote:
>>>>>
>>>>>> (Newcomer first post)
>>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> Here is a basic Xform:
>>>>>>
>>>>>> When I hover over the error flags, I only get a little question  
>>>>>> mark.
>>>>>> What can I do to display the error associated with the event, which  
>>>>>> I can't identify?
>>>>> As far as I recall, you only get the red X if the value doesn't  
>>>>> match the node's type or constraints.
>>>>>
>>>>> I don't understand why you are getting an X for Item, because that's  
>>>>> a string; amount is an integer, and ?0 is not a valid integer value,  
>>>>> so that's why you are getting >>>>>it there.
>>>>>
>>>>> To get a message to show, you need to include an <alert/> element in  
>>>>> the input; for instance
>>>>>
>>>>>   <xf:label>Amount:</xf:label><xf:alert>Must be an integer</xf:alert>
>>>>>
>>>>>
>>>>>> There must be some binding mistake in the form, here attached, but  
>>>>>> the messages associated with xforms-binding-error are not displayed.
>>>>> The bindings are fine. If there were a binding error, the control  
>>>>> would not show up.
>>>>>
>>>>> Hope this helps somewhat.
>>>>>
>>>>> Steven
>>>>>
>>>>>>
>>>>>> Thanks for any help,
>>>>>> Robert.

Re: [Xsltforms-support] Error handling and display

[Robert K. <ro...@er...>]

Additional point:
My test relies on a BaseX http server, as you can see from the xsltforms
url (port 8984).
This should not make a difference, but well a variation with the tests you
made.
Regards,
Robert.

On Wed, May 1, 2019 at 2:58 PM Robert Kirkpatrick <ro...@er...> wrote:

> Very strange.
> I'm using Chrome Version 73.0.3683.103
>
> On Wed, May 1, 2019 at 12:58 PM Steven Pemberton <ste...@cw...>
> wrote:
>
>> On Tue, 30 Apr 2019 19:29:39 +0200, Robert Kirkpatrick <ro...@er...>
>> wrote:
>>
>> Thank you Steven.
>>
>> Indeed type errors show up clearly. But in my example, the displayed
>> values were not typed in via the form, but defined in the <instance/> as
>> default values: ? for item, 0 for amount.
>> And very weirdly, they are output *concatenated* in *both* form fields !!
>> An X error flag indicates a problem, not surprising, but totally blind..
>> !?
>>
>>
>> I ran your test in 4 different browsers, and didn't get this problem.
>>
>> Steven
>>
>>
>>
>> Robert.
>>
>> On Tue, Apr 30, 2019 at 2:14 PM Steven Pemberton <ste...@cw...>
>> wrote:
>>
>>> On Tue, 30 Apr 2019 11:35:47 +0200, Robert Kirkpatrick <
>>> ro...@er...> wrote:
>>>
>>> (Newcomer first post)
>>>
>>> Hello,
>>>
>>> Here is a basic Xform:
>>> [image: image.png]
>>>
>>> When I hover over the error flags, I only get a little question mark.
>>> What can I do to display the error associated with the event, which I
>>> can't identify?
>>>
>>> As far as I recall, you only get the red X if the value doesn't match
>>> the node's type or constraints.
>>>
>>> I don't understand why you are getting an X for Item, because that's a
>>> string; amount is an integer, and ?0 is not a valid integer value, so
>>> that's why you are getting it there.
>>>
>>> To get a message to show, you need to include an <alert/> element in the
>>> input; for instance
>>>
>>>    <xf:label>Amount:</xf:label><xf:alert>Must be an integer</xf:alert>
>>>
>>>
>>> There must be some binding mistake in the form, here attached, but the
>>> messages associated with xforms-binding-error are not displayed.
>>>
>>> The bindings are fine. If there were a binding error, the control would
>>> not show up.
>>>
>>> Hope this helps somewhat.
>>>
>>> Steven
>>>
>>>
>>> Thanks for any help,
>>> Robert.
>>>
>>>
>>>
>>>
>>>
>>
>>
>>

Re: [Xsltforms-support] Error handling and display

[Robert K. <ro...@er...>]

Very strange.
I'm using Chrome Version 73.0.3683.103

On Wed, May 1, 2019 at 12:58 PM Steven Pemberton <ste...@cw...>
wrote:

> On Tue, 30 Apr 2019 19:29:39 +0200, Robert Kirkpatrick <ro...@er...>
> wrote:
>
> Thank you Steven.
>
> Indeed type errors show up clearly. But in my example, the displayed
> values were not typed in via the form, but defined in the <instance/> as
> default values: ? for item, 0 for amount.
> And very weirdly, they are output *concatenated* in *both* form fields !!
> An X error flag indicates a problem, not surprising, but totally blind.. !?
>
>
> I ran your test in 4 different browsers, and didn't get this problem.
>
> Steven
>
>
>
> Robert.
>
> On Tue, Apr 30, 2019 at 2:14 PM Steven Pemberton <ste...@cw...>
> wrote:
>
>> On Tue, 30 Apr 2019 11:35:47 +0200, Robert Kirkpatrick <ro...@er...>
>> wrote:
>>
>> (Newcomer first post)
>>
>> Hello,
>>
>> Here is a basic Xform:
>> [image: image.png]
>>
>> When I hover over the error flags, I only get a little question mark.
>> What can I do to display the error associated with the event, which I
>> can't identify?
>>
>> As far as I recall, you only get the red X if the value doesn't match the
>> node's type or constraints.
>>
>> I don't understand why you are getting an X for Item, because that's a
>> string; amount is an integer, and ?0 is not a valid integer value, so
>> that's why you are getting it there.
>>
>> To get a message to show, you need to include an <alert/> element in the
>> input; for instance
>>
>>    <xf:label>Amount:</xf:label><xf:alert>Must be an integer</xf:alert>
>>
>>
>> There must be some binding mistake in the form, here attached, but the
>> messages associated with xforms-binding-error are not displayed.
>>
>> The bindings are fine. If there were a binding error, the control would
>> not show up.
>>
>> Hope this helps somewhat.
>>
>> Steven
>>
>>
>> Thanks for any help,
>> Robert.
>>
>>
>>
>>
>>
>
>
>

Re: [Xsltforms-support] Error handling and display

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

On Tue, 30 Apr 2019 11:35:47 +0200, Robert Kirkpatrick <ro...@er...>  
wrote:

> (Newcomer first post)
>
> Hello,
>
> Here is a basic Xform:
>
> When I hover over the error flags, I only get a little question mark.
> What can I do to display the error associated with the event, which I  
> can't identify?
As far as I recall, you only get the red X if the value doesn't match the  
node's type or constraints.

I don't understand why you are getting an X for Item, because that's a  
string; amount is an integer, and ?0 is not a valid integer value, so  
that's why you are getting it there.

To get a message to show, you need to include an <alert/> element in the  
input; for instance

    <xf:label>Amount:</xf:label><xf:alert>Must be an integer</xf:alert>


> There must be some binding mistake in the form, here attached, but the  
> messages associated with xforms-binding-error are not displayed.
The bindings are fine. If there were a binding error, the control would  
not show up.

Hope this helps somewhat.

Steven

>
> Thanks for any help,
> Robert.

[Xsltforms-support] Error handling and display

[Robert K. <ro...@er...>]

(Newcomer first post)

Hello,

Here is a basic Xform:
[image: image.png]

When I hover over the error flags, I only get a little question mark.
What can I do to display the error associated with the event, which I can't
identify?

There must be some binding mistake in the form, here attached, but the
messages associated with xforms-binding-error are not displayed.

Thanks for any help,
Robert.