xsltforms-support — XSLTForms support list

[Xsltforms-support] chaining XForms forms

[Chris G. <cga...@gm...>]

I have an XForms form that posts to an XML-RPC gateway, and it returns
another XForms form with results from the operation. When the next XForms
form comes back, it's not transformed by the transformation engine. Do I
need to do anything special to get subsequent XForms forms to render?

Re: [Xsltforms-support] XSLTForms with mobile apps-reg

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

Rajamani,

For computers, many browsers now have the LocalStorage feature which could be used by XSLTForms to store instances locally.

I don't know if mobile phone browsers also have this feature... and I don't have any mobile phone supporting such a browser... Do you know and use mobile phone emulations?

Thanks!

-Alain

 
Dear Members !!!

    We are trying to develop an application in XForms with XSLTForms engine for offline users .We accessing that form in mobile (online) . It's working fine ... but in terms of offline access of that same form is possible or not we, don't know ... How to do that in mobile phone .. first is it possible ?...

Give me your suggestion  reg this ... 

Thanks and regards 

Rajamani Marimuthu
Junior Research Fellow-JRF
NIC -Open Technology Centre
Rajaji Bhavan
Besant Nagar,
Chennai - 90
Cell : 9791125383

[Xsltforms-support] XSLTForms with mobile apps-reg

[Raja <m.r...@ni...>]

Dear Members !!!

    We are trying to develop an application in XForms with XSLTForms engine for offline users .We accessing that form in mobile (online) . It's working fine ... but in terms of offline access of that same form is possible or not we, don't know ... How to do that in mobile phone .. first is it possible ?...

Give me your suggestion  reg this ... 

Thanks and regards 

Rajamani Marimuthu
Junior Research Fellow-JRF
NIC -Open Technology Centre
Rajaji Bhavan
Besant Nagar,
Chennai - 90
Cell : 9791125383

Re: [Xsltforms-support] Detecting and debug-logging of not-foundelements by id

[Kostis A. <ank...@gm...>]

Thank you
for your advice about overidding getElementById().

I would definetly need this to proceed to the latest svn revision.

Kostis

On Thu, May 20, 2010 at 1:21 PM,  <ala...@ag...> wrote:
> Hi Kostis,
>
> The $() function was in conflict with some Javascript frameworks where it is
> also defined that's why I had to, at least, rename it but I prefered
> removing it.
>
> A long time ago, such check was effectively present in XSLTForms and it's
> good for debugging but such a function is called very often and for speed it
> would be nice not to redefine it this way.
>
> Can you try to redefine document.getElementById itself? This should work
> because Javascript usually permits this! Debug mode could, then, add
> corresponding instructions...
>
> Thanks!
>
> -Alain
>

Re: [Xsltforms-support] Detecting and debug-logging of not-foundelements by id

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

Hi Kostis,

The $() function was in conflict with some Javascript frameworks where it is also defined that's why I had to, at least, rename it but I prefered removing it.

A long time ago, such check was effectively present in XSLTForms and it's good for debugging but such a function is called very often and for speed it would be nice not to redefine it this way.

Can you try to redefine document.getElementById itself? This should work because Javascript usually permits this! Debug mode could, then, add corresponding instructions...

Thanks!

-Alain

[Xsltforms-support] Detecting and debug-logging of not-found elements by id

[Kostis A. <ank...@gm...>]

Hi Alain,

in rev397-398 you replaced the invocation of the $() function with
directly invoking the getElementById() function.

Why was this change necessary?

I ask about it because i had discovered a new usage for the $() function,
by customizing it to report any not-found elements,
with the following code:

function $(id) {
	// return document.getElementById(id);
	var el = document.getElementById(id);
	if (!el && DebugMode){DebugConsole.write("Failed to find ID("+id+")!");}
	return el;
}


This change had prooved to be very usefull when debuging xforms,
since XSLTForms does not explicitely detect and report all such errors,
and the subsequent re null-pointer errors do not report the id in question.

Is there any plan to reinstitute such a check?

Regards for your efforts,
  Kostis Anagnostopoulos

Re: [Xsltforms-support] [PATCH] Reworked Dialogs to fix show-hidding problems

[Kostis A. <ank...@gm...>]

Hi Alain,

The Dialog.depth variable in xsltforms.js:357 (rev403) is not used anywhere.
It can be safely removed.

[Xsltforms-support] You could be the first donor!

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

Hello,

Different machines are required for XSLTForms development and compatibility tests: PC, Mac, phones,...

That's why I have enabled the "Donate" button at http://sourceforge.net/donate/index.php?group_id=242651 from $5 upto $250!

Thank you very much

-Alain

[Xsltforms-support] insert causes select1 appearance full to lose display

[Leigh L. K. Jr. <Lei...@Xe...>]

Please see the attached file.
Leigh.

Re: [Xsltforms-support] Is <xf:copy> within an <xf:itemset> supported yet?

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

Hi Dan,

<xf:copy> is not yet supported by XSLTForms and I have to study this 
more in details to know if it would be easy or not. When would you 
require this?

Thanks!

-Alain
> Hello XSLTForms fans!
>
> I am currently using the <xf:select> control and it currently puts the 
> selected items as space separated values in an element like this:
>
> <message-classification-codes>code-a code-b 
> code-c</message-classification-codes>
>
> But for a specific program that I am working on, I would like is the 
> following structure:
>
> <message-classification-codes>
>    <classifier>code-a</classifier>
>    <classifier>code-b</classifier>
>    <classifier>code-c</classifier>
> </message-classification-codes>
>
> There is an implication that this should be possible in XForms 1.1 
> using the <xf:copy> element inside of <xf:itemset> instead of <xf:value>.
>
> See http://www.w3.org/TR/xforms11/#ui-selection-commonelems-copy
>
> I know that I can get the same results by using a <xf:select1> inside 
> of a </xf:repeat>, but it seems like the <xf:copy> inside of 
> <xf:itemset> would be a lot nicer.
>
> Can anyone tell me if this would be easy to do?
>
> Thanks! - Dan
>
> -- 
> Dan McCreary
> Semantic Solutions Architect
> office: (952) 931-9198
> cell: (612) 986-1442
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
>
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>   

Re: [Xsltforms-support] How to implement http-header pasing on submission?

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

Hi Kostis,

Sorry for the delay, I needed time to analyze this!

I understand that a nodeset has to be returned by a 
event('response-headers') call. The corresponding XSLTForms Javascript 
function has, then, to return a Javascript array of nodes because it is 
the way a nodeset is stored in XSLTForms.

An XPath expression such as "event('response-headers')[2]" should be 
possible instead of "event('response-headers')/header[2]" because this 
one would require a parent-node to be returned instead. I'm not sure 
that XSLTForms XPath parser would yet accept this and is it valid XPath 
1.0 syntax anyway? The only example I found was about insert action: 
http://en.wikibooks.org/wiki/XForms/Web_Service_Tester.

Thank you for your efforts!

-Alain
> Please, any help on that?
>
> On Tue, May 11, 2010 at 7:49 PM, Kostis Anagnostopoulos
> <ank...@gm...> wrote:
>   
>> Hi Alain,
>>
>> i saw that you incorporated the event() code i had submitted a while ago,
>> so now i'm reworking it, to fix certain issues with it, such as:
>> * checking  for event-context items case-insesitivly,
>> * returning '' when not context items do not exist (insntead of 'undefined').
>>
>> Among others, i try to implement the parsing of xml-http-headers,
>> as defined by chapter 11.4 [1].
>>
>> Therefore, given the 3 response headers below:
>> ----------------
>> Date: Tue, 11 May 2010 16:26:46 GMT
>> Server: Apache
>> Content-Type: text/html; charset=iso-8859-1
>> ----------------
>>
>> we should return thw following nodeset:
>> ----------------
>> <header xmlns="">
>>  <name>Date</name><value>Tue, 11 May 2010 16:26:46 GMT</value
>> </header>
>> <header xmlns="">
>>  <name>Server</name>Apache<value></value
>> </header>
>> <header xmlns="">
>>  <name>Content-Type</name><value>text/html; charset=iso-8859-1</value
>> </header>
>> ----------------
>>
>>
>> Based on [2], I crafted the following code to parse the http-headers:
>> ----------------
>> /** @headers similar to the headers above */
>> XFSubmission.prototype.parseHttpHeaders_ = function(headers) {
>>        if (!headers)
>>                return '';
>>
>>        var hdoc = new XDocument();
>>        var nodes = [];
>>        try {
>>                var hlines = headers.split("\r\n");
>>                for(var i in hlines) {
>>                        var hline = hlines[i];
>>                        if (!hline.length)
>>                                continue;
>>                        var hpair = hline.split(":");
>>                        //alert("name="+hpair[0]+", value="+hpair[1]);
>>
>>                        var name = hpair[0];
>>                        var value = hpair[1].replace("/^\\s*/", "");
>>
>>                        var hel = hdoc.createElementNS("", "header");
>>                        var nel = hdoc.createElementNS("", "name");
>>                        var vel = hdoc.createElementNS("", "value");
>>                        var ntxt = hdoc.createTextNode(name);
>>                        var vtxt = hdoc.createTextNode(value);
>>
>>                        nel.appendChild(ntxt);
>>                        vel.appendChild(vtxt);
>>
>>                        hel.appendChild(nel);
>>                        hel.appendChild(vel);
>>
>>                        hdoc.appendChild(hel);// Is it necessary?
>>                        nodes.push(hel);
>>                }
>>        } catch(ex) {
>>                DebugConsole.write("Error while parsing http-headers: " + ex);
>>                hdoc = headers;
>>        }
>>
>>        return hdoc; // should i had returned 'nodes' var instead?
>> }
>> ----------------
>>
>> Now the questions:
>>
>> 1. Is there i simpler way?
>> (ie return an associative array?)
>>
>> 2) Why the above code does not work when using the XPath expressions below?
>>  event('response-headers')/header[2]/name
>>  event('response-headers')/header[1]/value
>>  ...etc
>>
>> What should i change with regard to the return value of the
>> parseHttpHeaders_() function?
>>
>> NOTE
>> 1. that in the above code i diregarded completely any header-encoding issues,
>> and
>> 2. that i'm planning to split this function in two,
>> one that parses headers to produce an associative array, to be used elsewhere
>> (i.e. to decide based on the 'Content-type' whether to parse the
>> response-body or not, see [2] again)
>> and anotherone, that produces the xml-nodeset.
>>
>>
>> Regards,
>>  Kostis Anagnostopoulos
>>
>>
>> [1] http://www.w3.org/TR/xforms11/#submit-evt-submit-error
>> [2] http://www.w3.org/TR/XMLHttpRequest/
>>
>>     
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
>   

[Xsltforms-support] Is <xf:copy> within an <xf:itemset> supported yet?

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

Hello XSLTForms fans!

I am currently using the <xf:select> control and it currently puts the
selected items as space separated values in an element like this:

<message-classification-codes>code-a code-b
code-c</message-classification-codes>

But for a specific program that I am working on, I would like is the
following structure:

<message-classification-codes>
   <classifier>code-a</classifier>
   <classifier>code-b</classifier>
   <classifier>code-c</classifier>
</message-classification-codes>

There is an implication that this should be possible in XForms 1.1 using the
<xf:copy> element inside of <xf:itemset> instead of <xf:value>.

See http://www.w3.org/TR/xforms11/#ui-selection-commonelems-copy

I know that I can get the same results by using a <xf:select1> inside of a
</xf:repeat>, but it seems like the <xf:copy> inside of <xf:itemset> would
be a lot nicer.

Can anyone tell me if this would be easy to do?

Thanks! - Dan

-- 
Dan McCreary
Semantic Solutions Architect
office: (952) 931-9198
cell: (612) 986-1442

Re: [Xsltforms-support] How to implement http-header pasing on submission?

[Kostis A. <ank...@gm...>]

Please, any help on that?

On Tue, May 11, 2010 at 7:49 PM, Kostis Anagnostopoulos
<ank...@gm...> wrote:
> Hi Alain,
>
> i saw that you incorporated the event() code i had submitted a while ago,
> so now i'm reworking it, to fix certain issues with it, such as:
> * checking  for event-context items case-insesitivly,
> * returning '' when not context items do not exist (insntead of 'undefined').
>
> Among others, i try to implement the parsing of xml-http-headers,
> as defined by chapter 11.4 [1].
>
> Therefore, given the 3 response headers below:
> ----------------
> Date: Tue, 11 May 2010 16:26:46 GMT
> Server: Apache
> Content-Type: text/html; charset=iso-8859-1
> ----------------
>
> we should return thw following nodeset:
> ----------------
> <header xmlns="">
>  <name>Date</name><value>Tue, 11 May 2010 16:26:46 GMT</value
> </header>
> <header xmlns="">
>  <name>Server</name>Apache<value></value
> </header>
> <header xmlns="">
>  <name>Content-Type</name><value>text/html; charset=iso-8859-1</value
> </header>
> ----------------
>
>
> Based on [2], I crafted the following code to parse the http-headers:
> ----------------
> /** @headers similar to the headers above */
> XFSubmission.prototype.parseHttpHeaders_ = function(headers) {
>        if (!headers)
>                return '';
>
>        var hdoc = new XDocument();
>        var nodes = [];
>        try {
>                var hlines = headers.split("\r\n");
>                for(var i in hlines) {
>                        var hline = hlines[i];
>                        if (!hline.length)
>                                continue;
>                        var hpair = hline.split(":");
>                        //alert("name="+hpair[0]+", value="+hpair[1]);
>
>                        var name = hpair[0];
>                        var value = hpair[1].replace("/^\\s*/", "");
>
>                        var hel = hdoc.createElementNS("", "header");
>                        var nel = hdoc.createElementNS("", "name");
>                        var vel = hdoc.createElementNS("", "value");
>                        var ntxt = hdoc.createTextNode(name);
>                        var vtxt = hdoc.createTextNode(value);
>
>                        nel.appendChild(ntxt);
>                        vel.appendChild(vtxt);
>
>                        hel.appendChild(nel);
>                        hel.appendChild(vel);
>
>                        hdoc.appendChild(hel);// Is it necessary?
>                        nodes.push(hel);
>                }
>        } catch(ex) {
>                DebugConsole.write("Error while parsing http-headers: " + ex);
>                hdoc = headers;
>        }
>
>        return hdoc; // should i had returned 'nodes' var instead?
> }
> ----------------
>
> Now the questions:
>
> 1. Is there i simpler way?
> (ie return an associative array?)
>
> 2) Why the above code does not work when using the XPath expressions below?
>  event('response-headers')/header[2]/name
>  event('response-headers')/header[1]/value
>  ...etc
>
> What should i change with regard to the return value of the
> parseHttpHeaders_() function?
>
> NOTE
> 1. that in the above code i diregarded completely any header-encoding issues,
> and
> 2. that i'm planning to split this function in two,
> one that parses headers to produce an associative array, to be used elsewhere
> (i.e. to decide based on the 'Content-type' whether to parse the
> response-body or not, see [2] again)
> and anotherone, that produces the xml-nodeset.
>
>
> Regards,
>  Kostis Anagnostopoulos
>
>
> [1] http://www.w3.org/TR/xforms11/#submit-evt-submit-error
> [2] http://www.w3.org/TR/XMLHttpRequest/
>

Re: [Xsltforms-support] Labels from instance not working

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

Oh, yes... label/@ref is not yet supported by XSLTForms so label/output/@ref has to be used instead!

Thanks!

-Alain

On Mon, 17 May 2010 15:57:37 +0200, <ala...@ag...> wrote:

> Steven,
>
> It is working for me with the latest SVN version. Are you using Beta 2  
> release?

I am, at least, that is what the directory name is... Did you remove the  
outputs from the source, because if my version were working, it would be  
outputting the labels twice.

> BTW, in French, please replace "Feminine" by "Féminin" ;-)

Ah! Thanks :-)

Steven

> Thanks!
>
> -Alain
>
>
> Enclosed is a form where the labels of controls come from an instance.  
> If you do a view source, you will see I have added <output>s to generate  
> the text of the labels, since the src= isn't working.
>
> Bug or feature? :-)
>
> Thanks!
>
> Best wishes,
>
> Steven Pemberton
> 
------------------------------------------------------------------------------
>
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support

Re: [Xsltforms-support] Labels from instance not working

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

On Mon, 17 May 2010 15:57:37 +0200, <ala...@ag...> wrote:

> Steven,
>
> It is working for me with the latest SVN version. Are you using Beta 2  
> release?

I am, at least, that is what the directory name is... Did you remove the  
outputs from the source, because if my version were working, it would be  
outputting the labels twice.

> BTW, in French, please replace "Feminine" by "Féminin" ;-)

Ah! Thanks :-)

Steven

> Thanks!
>
> -Alain
>
>
> Enclosed is a form where the labels of controls come from an instance.  
> If you do a view source, you will see I have added <output>s to generate  
> the text of the labels, since the src= isn't working.
>
> Bug or feature? :-)
>
> Thanks!
>
> Best wishes,
>
> Steven Pemberton
> ------------------------------------------------------------------------------
>
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support

[Xsltforms-support] Labels from instance not working

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

Enclosed is a form where the labels of controls come from an instance. If  
you do a view source, you will see I have added <output>s to generate the  
text of the labels, since the src= isn't working.

Bug or feature? :-)

Thanks!

Best wishes,

Steven Pemberton

[Xsltforms-support] New version of eXSLTForms

[Claudius T. <cla...@ya...>]

Hi, all,

A new version of eXSLTForms is available http://sourceforge.net/projects/extxsltforms/files/

Changelog:
Version 1.0.1. - 2010-05-17
1. This version of eXSLTForms works with the latest XSLTForms version, as of 2010-05-14.
2. For installing it, please see the installation.txt file.
3. This version provides a simpler way of embedding DataInstancesViewer on page - see the installation.txt file.
4. This version provides the integration of the web rich text editors CKEditor, TinyMCE, Dojo Editor, YUI Editor, and YUI SimpleEditor, 
as well as of the code editor EditArea. For installing them, please read installation.txt. For using them, please read the documentation.txt
 file (pay attention that the RTEs options should now be wrapped into curly brackets and have single quotes within, not double quotes).
5. On http://extxsltforms.sourceforge.net or http://kuberam.ro one can find examples of usage for each editor and even an page with ALL
the editors happily co-operating - just for fun.

Claudius Teodorescu
http://kuberam.ro



      

[Xsltforms-support] problem with responses on <send ev:event="xforms-value-changed"> in xsltforms-403

[Leigh L. K. Jr. <Lei...@Xe...>]

In xsltforms r403 and earlier versions, setvalue inside the 
xforms-submit-done handler of a submission caused by 
ev:event="xforms-value-changed" fails to get values of the 
submission/@instance target instance data.   Instead, it gets data prior 
to the replace="instance".

However, when this same submission is triggered by a <submit> control, 
it works fine.

<submission id="update-requestor" method="get" resource="lookup.xml" 
ref="instance('main')/requestor" replace="instance" instance="names" >
<message ev:event="xforms-submit-error" level="modal">OOPS</message>
<action ev:event="xforms-submit-done">
<setvalue ref="instance('main')/requestor/name" 
value="instance('names')/name" />
</action>
</submission>


This effect is most obvious if the result of the submission resource 
varies with the input, becuase you can see it's the previous set of values.

In the example posted at 
http://xformstest.org/klotz/2010/05/submit/test.xml the lookup.xml is a 
static file, so it returns static data, and so the effect is that the 
first time, you get nothing, and the second time, you see the setvalue 
results from the previous time.

Leigh.

Re: [Xsltforms-support] Delay before firing events?

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

Grégoire and Leigh,

I have just basically implemented the delay feature for the dispatch 
element so you could use a custom event for that but it wouldn't be that 
easy with focus management.

Adding a delay with @incremental="true" sounds much more simple for 
developers and I have also implemented this for tests: 
http://www.agencexml.com/jsoncallback/wikipediasearch.xml

It is nicer with this extension!

Thanks for your feedbacks!

-Alain
> XForms doesn't specify what @incremental=true means in detail.  Many 
> choose to implement a per-character event, but that's not necessarily 
> what everyone wants.
>  
> The delay attribute doesn't seem to me to be a good fit for this use, 
> given its definition.
>  
> How about if Alain or you consider an xsltforms specific attribute for 
> giving finer control over event timing with textarea or 
> input/@incremental=true? 
> <mailto:input/@incremental=true?%20Experience>Experience 
> <mailto:input/@incremental=true?%20Experience> with thsi 
> implementation would be good feedback to the Forms WG.
>  
> Leigyh.
>
> ------------------------------------------------------------------------
> *From:* Grégoire Colbert [mailto:gco...@gm...]
> *Sent:* Wednesday, May 12, 2010 9:51 AM
> *To:* support xsltforms
> *Subject:* Re: [Xsltforms-support] Delay before firing events?
>
> Hi,
>
> I'm still working on a XForm with a "autocomplete" field. Is there a 
> way, with XSLTForms, to only submit a form if no "key pressed" event 
> is received during a few milliseconds?
>
> I've seen in XForms 1.1 that there's a "dispatch" element with the 
> "delay" attribute, which could be the solution :
> http://www.w3.org/TR/xforms11/#action-dispatch
> Has anyone used it?
>
> Thanks a lot for your help!
>
> Grégoire
>
> Le 10 mars 2010 10:29, Grégoire Colbert <gco...@gm... 
> <mailto:gco...@gm...>> a écrit :
>
>     Hi,
>
>     I noticed the following message on "What's happening?" screen at SF :
>
>     /Hello, I'm trying an incremental search like the one you show in
>     http://en.wikibooks.org/wiki/XForms/Incremental_Find. When the
>     user write the first char in the xf:input , the event is fired and
>     the request sent and during that time we loose one or more typed
>     chars. Is there any mean to introduce a small delay before sending
>     the request ? Cordialement. Benoit VINCENT./
>
>     I have exactly the same issue. Is there a solution?
>
>     Grégoire
>
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
>
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>   

Re: [Xsltforms-support] Delay before firing events?

[Klotz, L. <Lei...@xe...>]

XForms doesn't specify what @incremental=true means in detail.  Many choose to implement a per-character event, but that's not necessarily what everyone wants.
 
The delay attribute doesn't seem to me to be a good fit for this use, given its definition.
 
How about if Alain or you consider an xsltforms specific attribute for giving finer control over event timing with textarea or input/@incremental=true? <mailto:input/@incremental=true? Experience> Experience with thsi implementation would be good feedback to the Forms WG.
 
Leigyh.

________________________________

From: Grégoire Colbert [mailto:gco...@gm...] 
Sent: Wednesday, May 12, 2010 9:51 AM
To: support xsltforms
Subject: Re: [Xsltforms-support] Delay before firing events?


Hi,

I'm still working on a XForm with a "autocomplete" field. Is there a way, with XSLTForms, to only submit a form if no "key pressed" event is received during a few milliseconds?

I've seen in XForms 1.1 that there's a "dispatch" element with the "delay" attribute, which could be the solution :
http://www.w3.org/TR/xforms11/#action-dispatch
Has anyone used it?

Thanks a lot for your help!

Grégoire


Le 10 mars 2010 10:29, Grégoire Colbert <gco...@gm...> a écrit :


	Hi,
	
	I noticed the following message on "What's happening?" screen at SF :
	
	Hello, I'm trying an incremental search like the one you show in http://en.wikibooks.org/wiki/XForms/Incremental_Find. When the user write the first char in the xf:input , the event is fired and the request sent and during that time we loose one or more typed chars. Is there any mean to introduce a small delay before sending the request ? Cordialement. Benoit VINCENT.
	
	I have exactly the same issue. Is there a solution?
	
	Grégoire
	
	

Re: [Xsltforms-support] Delay before firing events?

[Grégoire C. <gco...@gm...>]

Hi,

I'm still working on a XForm with a "autocomplete" field. Is there a way,
with XSLTForms, to only submit a form if no "key pressed" event is received
during a few milliseconds?

I've seen in XForms 1.1 that there's a "dispatch" element with the "delay"
attribute, which could be the solution :
http://www.w3.org/TR/xforms11/#action-dispatch
Has anyone used it?

Thanks a lot for your help!

Grégoire

Le 10 mars 2010 10:29, Grégoire Colbert <gco...@gm...> a écrit :

> Hi,
>
> I noticed the following message on "What's happening?" screen at SF :
>
> *Hello, I'm trying an incremental search like the one you show in
> http://en.wikibooks.org/wiki/XForms/Incremental_Find. When the user write
> the first char in the xf:input , the event is fired and the request sent and
> during that time we loose one or more typed chars. Is there any mean to
> introduce a small delay before sending the request ? Cordialement. Benoit
> VINCENT.*
>
> I have exactly the same issue. Is there a solution?
>
> Grégoire
>
>

Re: [Xsltforms-support] Config.xsl

[Claudius T. <cla...@ya...>]

Hi,

These elements are designated to contain the Javascript scripts/code to be embedded into the XHTML page generated by the XSLTForms engine. Could be an interesting idea, but how?

 Claudius Teodorescu
http://kuberam.ro




________________________________
From: "Klotz, Leigh" <Lei...@xe...>
To: Claudius Teodorescu <cla...@ya...>; support xsltforms <xsl...@li...>
Sent: Mon, May 10, 2010 6:20:13 PM
Subject: RE: [Xsltforms-support] Config.xsl


I wonder if it might be reasonable to use XML events 
instead of these names?


________________________________
 From: Claudius Teodorescu 
[mailto:cla...@ya...] 
Sent: Monday, May 10, 2010 2:55 
AM
To: support xsltforms
Subject: [Xsltforms-support] 
Config.xsl


Hi,

As 
you kindly support afterInit, etc. in xsltforms.xsl, the extensions element from 
config.xsl should consequently be as follows:

<extensions> <!-- 
HTML elements to be added just after xsltforms.js and xsltforms.css loading 
-->
        
<beforeInit/>
        
<onBeginInit/>
        
<onEndInit/>
        
<afterInit/>
</extensions>


Thank you, and good luck!
 
Claudius 
Teodorescu
http://kuberam.ro 


      

[Xsltforms-support] How to implement http-header pasing on submission?

[Kostis A. <ank...@gm...>]

Hi Alain,

i saw that you incorporated the event() code i had submitted a while ago,
so now i'm reworking it, to fix certain issues with it, such as:
* checking  for event-context items case-insesitivly,
* returning '' when not context items do not exist (insntead of 'undefined').

Among others, i try to implement the parsing of xml-http-headers,
as defined by chapter 11.4 [1].

Therefore, given the 3 response headers below:
----------------
Date: Tue, 11 May 2010 16:26:46 GMT
Server: Apache
Content-Type: text/html; charset=iso-8859-1
----------------

we should return thw following nodeset:
----------------
<header xmlns="">
  <name>Date</name><value>Tue, 11 May 2010 16:26:46 GMT</value
</header>
<header xmlns="">
  <name>Server</name>Apache<value></value
</header>
<header xmlns="">
  <name>Content-Type</name><value>text/html; charset=iso-8859-1</value
</header>
----------------


Based on [2], I crafted the following code to parse the http-headers:
----------------
/** @headers similar to the headers above */
XFSubmission.prototype.parseHttpHeaders_ = function(headers) {
	if (!headers)
		return '';

	var hdoc = new XDocument();
	var nodes = [];
	try {
		var hlines = headers.split("\r\n");
		for(var i in hlines) {
			var hline = hlines[i];
			if (!hline.length)
				continue;
			var hpair = hline.split(":");
			//alert("name="+hpair[0]+", value="+hpair[1]);
			
			var name = hpair[0];
			var value = hpair[1].replace("/^\\s*/", "");
			
			var hel = hdoc.createElementNS("", "header");
			var nel = hdoc.createElementNS("", "name");
			var vel = hdoc.createElementNS("", "value");
			var ntxt = hdoc.createTextNode(name);
			var vtxt = hdoc.createTextNode(value);
	
			nel.appendChild(ntxt);
			vel.appendChild(vtxt);
	
			hel.appendChild(nel);
			hel.appendChild(vel);
	
			hdoc.appendChild(hel);// Is it necessary?
			nodes.push(hel);
		}
	} catch(ex) {
		DebugConsole.write("Error while parsing http-headers: " + ex);
		hdoc = headers;
	}

	return hdoc; // should i had returned 'nodes' var instead?
}
----------------

Now the questions:

1. Is there i simpler way?
(ie return an associative array?)

2) Why the above code does not work when using the XPath expressions below?
  event('response-headers')/header[2]/name
  event('response-headers')/header[1]/value
  ...etc

What should i change with regard to the return value of the
parseHttpHeaders_() function?

NOTE
1. that in the above code i diregarded completely any header-encoding issues,
and
2. that i'm planning to split this function in two,
one that parses headers to produce an associative array, to be used elsewhere
(i.e. to decide based on the 'Content-type' whether to parse the
response-body or not, see [2] again)
and anotherone, that produces the xml-nodeset.


Regards,
  Kostis Anagnostopoulos


[1] http://www.w3.org/TR/xforms11/#submit-evt-submit-error
[2] http://www.w3.org/TR/XMLHttpRequest/

Re: [Xsltforms-support] Insert a new row in a repeat table

[Raja <m.r...@ni...>]

Hi Dhiradj Badloe !!!!

 Just u add the setvalue action after the insert action  in that u set empty value for the added row... that's it...

like 
  <xf:setvalue ref="element name [last()]" value=" '' "/> 

----- Original Message -----
From: Dan McCreary <dan...@gm...>
Date: Tuesday, May 11, 2010 6:06 pm
SuSendbject: Re: [Xsltforms-support] Insert a new row in a repeat table
To: Dhiradj Badloe <dh...@gm...>
Cc: xsl...@li...

> I would use the "origin" attribute in the insert.
> 
> http://en.wikibooks.org/wiki/XForms/Deep_Copy_with_Insert_Origin
> 
>  On Tue, May 11, 2010 at 2:46 AM, Dhiradj Badloe <dh...@gm...> wrote:
>  Hi all,
> 
> I'm trying to insert a new row in a repeated table with the following code:
> 
> <xf:trigger>
>       <xf:label>Add row</xf:label>
>       <xf:action ev:event="DOMActivate">
>               <xf:insert  at="index('repeat-opgaven')" position="after"
>                             nodeset="instance('inlinewerken')/data/tabbladOpgaven/sve/oge/detail[1]/ojt"/>
>         </xf:action>
> </xf:trigger>
> 
> This  results in a copy of an existing row, which is added to the end of the table.
> How can I add a new, empty row to the table? Thanks!
> 
> Regards,
> Dhiradj Badloe
 > 
> ------------------------------------------------------------------------------
 > 
 > 
> _______________________________________________
>  Xsltforms-support mailing list
 > Xsl...@li...
 > https://lists.sourceforge.net/lists/listinfo/xsltforms-support
 > 
> 
> > 
> -- 
> Dan McCreary
> Semantic Solutions Architect
> office: (952) 931-9198
> cell: (612) 986-1442
 > -----------------------------------------------------------------
> -------------
> > _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support

Rajamani Marimuthu
Junior Research Fellow-JRF
NIC -Open Technology Centre
Rajaji Bhavan
Besant Nagar,
Chennai - 90
Cell : 9791125383

Re: [Xsltforms-support] Insert a new row in a repeat table

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

I would use the "origin" attribute in the insert.

http://en.wikibooks.org/wiki/XForms/Deep_Copy_with_Insert_Origin

On Tue, May 11, 2010 at 2:46 AM, Dhiradj Badloe <dh...@gm...> wrote:

> Hi all,
>
> I'm trying to insert a new row in a repeated table with the following code:
>
> <xf:trigger>
>       <xf:label>Add row</xf:label>
>       <xf:action ev:event="DOMActivate">
>             <xf:insert  at="index('repeat-opgaven')" position="after"
>
> nodeset="instance('inlinewerken')/data/tabbladOpgaven/sve/oge/detail[1]/ojt"/>
>       </xf:action>
> </xf:trigger>
>
> This results in a copy of an existing row, which is added to the end of the
> table.
> How can I add a new, empty row to the table? Thanks!
>
> Regards,
> Dhiradj Badloe
>
>
> ------------------------------------------------------------------------------
>
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
>


-- 
Dan McCreary
Semantic Solutions Architect
office: (952) 931-9198
cell: (612) 986-1442