xsltforms-support — XSLTForms support list

Re: [Xsltforms-support] Problem with submission and post method

[Aleksandar S. <ale...@pr...>]

Alain,

it works now!

Thanks for all good work.


-----Original Message-----
From: COUTHURES Alain [mailto:ala...@ag...] 
Sent: Saturday, February 13, 2010 11:21 PM
To: Aleksandar Stojsavljevic
Cc: xsl...@li...
Subject: Re: [Xsltforms-support] Problem with submission and post method

Aleksandar,
> xsl transformation is not performed when response 
> comes
I have just committed improvements for this. There is still a bug, at 
least, with Chrome.
> And my xforms need to be compatible with both XSLTForms and Chiba.
>   
Thank you for telling me if it's compatible now.

-Alain

[Xsltforms-support] Odd behaviour with xf:itemset and XPath predicate

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

Hi,

I've put a "xml:lang" attribute on my main model, as :

    <xf:model id="modele-recherche-requete">
      <xf:instance>
        <search xmlns="" xml:lang="en">
          <type/>
          <what/>
          <where/>
        </search>
      </xf:instance>
      <xf:submission id="submit" action="recherche.xql" method="get" />
    </xf:model>

What I want to do is to use the attribute's value in the "<search>" element
to retrieve the corresponding strings in my other model, as :

    <xf:select1 ref="/search/type" appearance="full" incremental="true">
      <xf:label><xf:output
ref="instance('instance-types-d-annonce')/resource[@xml:lang=*
/search/@xml:lang*]/label"/></xf:label>
      <xf:hint><xf:output
ref="instance('instance-types-d-annonce')/resource[@xml:lang=*
/search/@xml:lang*]/hint"/></xf:hint>
      <xf:itemset model="modele-types-d-annonce"
nodeset="instance('instance-types-d-annonce')/resource[@xml:lang=*
/search/@xml:lang***]/item">
        <xf:label ref="label"/>
        <xf:value ref="value"/>
      </xf:itemset>
    </xf:select1>

This works for the <xf:label> and <xf:hint>, but not for the <xf:itemset>
element (the list remains at "Loading..."). Please note that hard-coding the
language works, as in :

      <xf:itemset model="modele-types-d-annonce"
nodeset="instance('instance-types-d-annonce')/resource[@xml:lang=*'fr'***
]/item">

Why is the <xf:itemset> element in any way different from <xf:hint> or
<xf:label> regarding XPath? Any help would be kind as I'm out of ideas on
this one.

Regards,
Grégoire

Re: [Xsltforms-support] Charset problem (+ bug found)

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

Alain,

No, I did not test with IE6 or IE7 as I don't have these browsers.

Grégoire

Le 13 février 2010 23:16, COUTHURES Alain <ala...@ag...> a
écrit :

>  Grégoire,
>
> Thank you very much for these fixes. They have been committed now.
>
> I read encodeURIComponent() might be a problem with IE6 and IE7. Did you
> test with them ?
>
> -Alain
>
> Ok,
>
> I found another bug in "xsltforms.js". In "XFSubmission.toUrl_", you have :
>
>     if (!hasChilds && val.length > 0) {
>         url += node.nodeName + '=' + escape(val) + separator;
>     }
>
> but the escape() function works only with ASCII characters. So if the
> XForms is in UTF-8, a GET request will pass the model as ISO.
>
> Solution is to use encodeURIComponent() instead of escape() :
>
>         url += node.nodeName + '=' + encodeURIComponent(val) + separator;
>
> Now the strings are encoded correctly.
>
> Regards,
> Grégoire
>
> Le 12 février 2010 19:14, Grégoire Colbert <gco...@gm...> a écrit :
>
>> Hi,
>>
>> I'm submitting my XForm from an UTF-8 encoded page. When the data reaches
>> my eXist query, and I display the parameter, it is displayed as ISO-8859-1
>> on an UTF-8 page.
>>
>> BTW, looking in "xsltforms.js", I noticed that there is a missing "=" near
>> :
>>
>>             var media = this.mediatype;
>>             var mt = (media || "application/xml")
>>                 + (this.charset? ";charset" + this.charset : "");
>>
>> this last line should be :
>>
>>                 + (this.charset? ";charset*=*" + this.charset : "");
>>
>> However this does not solve my problem since "this.charset" is null (well
>> "undefined"). And even if I force UTF-8 with :
>>     mt = "application/xml;charset=UTF-8";
>> the request parameters are still converted to ISO somewhere. Any idea?
>>
>> Thanks,
>> Grégoire
>>
>>
> ------------------------------
>
> ------------------------------------------------------------------------------
> SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
> Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOWhttp://p.sf.net/sfu/solaris-dev2dev
>
> ------------------------------
>
> _______________________________________________
> Xsltforms-support mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
>
>

Re: [Xsltforms-support] Problem with submission and post method

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

Aleksandar,
> xsl transformation is not performed when response 
> comes
I have just committed improvements for this. There is still a bug, at 
least, with Chrome.
> And my xforms need to be compatible with both XSLTForms and Chiba.
>   
Thank you for telling me if it's compatible now.

-Alain

Re: [Xsltforms-support] Charset problem (+ bug found)

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

Grégoire,

Thank you very much for these fixes. They have been committed now.

I read encodeURIComponent() might be a problem with IE6 and IE7. Did you 
test with them ?

-Alain
> Ok,
>
> I found another bug in "xsltforms.js". In "XFSubmission.toUrl_", you 
> have :
>
>     if (!hasChilds && val.length > 0) {
>         url += node.nodeName + '=' + escape(val) + separator;
>     }
>
> but the escape() function works only with ASCII characters. So if the 
> XForms is in UTF-8, a GET request will pass the model as ISO.
>
> Solution is to use encodeURIComponent() instead of escape() :
>
>         url += node.nodeName + '=' + encodeURIComponent(val) + separator;
>
> Now the strings are encoded correctly.
>
> Regards,
> Grégoire
>
> Le 12 février 2010 19:14, Grégoire Colbert <gco...@gm... 
> <mailto:gco...@gm...>> a écrit :
>
>     Hi,
>
>     I'm submitting my XForm from an UTF-8 encoded page. When the data
>     reaches my eXist query, and I display the parameter, it is
>     displayed as ISO-8859-1 on an UTF-8 page.
>
>     BTW, looking in "xsltforms.js", I noticed that there is a missing
>     "=" near :
>
>                 var media = this.mediatype;
>                 var mt = (media || "application/xml")
>                     + (this.charset? ";charset" + this.charset : "");
>
>     this last line should be :
>
>                     + (this.charset? ";charset*=*" + this.charset : "");
>
>     However this does not solve my problem since "this.charset" is
>     null (well "undefined"). And even if I force UTF-8 with :
>         mt = "application/xml;charset=UTF-8";
>     the request parameters are still converted to ISO somewhere. Any idea?
>
>     Thanks,
>     Grégoire
>
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
> Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
> http://p.sf.net/sfu/solaris-dev2dev
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>   

Re: [Xsltforms-support] Charset problem (+ bug found)

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

Ok,

I found another bug in "xsltforms.js". In "XFSubmission.toUrl_", you have :

    if (!hasChilds && val.length > 0) {
        url += node.nodeName + '=' + escape(val) + separator;
    }

but the escape() function works only with ASCII characters. So if the XForms
is in UTF-8, a GET request will pass the model as ISO.

Solution is to use encodeURIComponent() instead of escape() :

        url += node.nodeName + '=' + encodeURIComponent(val) + separator;

Now the strings are encoded correctly.

Regards,
Grégoire

Le 12 février 2010 19:14, Grégoire Colbert <gco...@gm...> a écrit :

> Hi,
>
> I'm submitting my XForm from an UTF-8 encoded page. When the data reaches
> my eXist query, and I display the parameter, it is displayed as ISO-8859-1
> on an UTF-8 page.
>
> BTW, looking in "xsltforms.js", I noticed that there is a missing "=" near
> :
>
>             var media = this.mediatype;
>             var mt = (media || "application/xml")
>                 + (this.charset? ";charset" + this.charset : "");
>
> this last line should be :
>
>                 + (this.charset? ";charset*=*" + this.charset : "");
>
> However this does not solve my problem since "this.charset" is null (well
> "undefined"). And even if I force UTF-8 with :
>     mt = "application/xml;charset=UTF-8";
> the request parameters are still converted to ISO somewhere. Any idea?
>
> Thanks,
> Grégoire
>
>

[Xsltforms-support] Charset problem (+ bug found)

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

Hi,

I'm submitting my XForm from an UTF-8 encoded page. When the data reaches my
eXist query, and I display the parameter, it is displayed as ISO-8859-1 on
an UTF-8 page.

BTW, looking in "xsltforms.js", I noticed that there is a missing "=" near :

            var media = this.mediatype;
            var mt = (media || "application/xml")
                + (this.charset? ";charset" + this.charset : "");

this last line should be :

                + (this.charset? ";charset*=*" + this.charset : "");

However this does not solve my problem since "this.charset" is null (well
"undefined"). And even if I force UTF-8 with :
    mt = "application/xml;charset=UTF-8";
the request parameters are still converted to ISO somewhere. Any idea?

Thanks,
Grégoire

Re: [Xsltforms-support] Support de "src" pour charger une instance externe?

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

Ok,

I solved my problem. For some reason, with :

<html xmlns="http://www.w3.org/1999/xhtml"
           xmlns:xf="http://www.w3.org/2002/xforms"
           xmlns:xml="http://www.w3.org/XML/1998/namespace"
>

the [@xml:lang='fr'] selector doesn't work. But with :

<html xmlns="http://www.w3.org/1999/xhtml"
           xmlns:xf="http://www.w3.org/2002/xforms"
           xmlns:xml="http://www.w3.org/XML/1998/namespace"
           xml:lang="fr"
>

it works. Just like the "xml:" prefix needs to be initialized locally to be
recognized in external documents.

Grégoire

Le 10 février 2010 14:31, Grégoire Colbert <gco...@gm...> a écrit :

> Hi,
>
> Thank you Franclin. The "debug" mode was useful. My problem was with my
> XPath selector which I use to return the french strings only, like this :
>
> <xf:select1 ref="/search/type">
>   <xf:itemset model="myModel"
> nodeset="/resources/resource[@xml:lang='fr']/item">
>     <xf:label ref="label"/>
>     <xf:label ref="value"/>
>   </xf:itemset>
> </xf:select1>
>
> If I use [@xml:lang='fr'], it doesn't work and XSLTForms stays at the
> "Loading..." message in the Select1 widget. An event "xforms-out-of-range"
> is dispatched for this widget.
>
> However, if I change my external model to have the attribute "lang='fr'"
> and not "xml:lang='fr'", and change the XPath selector accordingly, then it
> works perfectly.
>
> It seems there's a bug in XSLTForms with external models and the way
> namespaces are dealt with, but I'm not an XPath expert so I may be wrong.
>
> Regards,
> Grégoire
>
> 2010/2/10 Franclin Foping <f.f...@4c...>
>
>  On 10/02/10 10:26, Grégoire Colbert wrote:
>>
>> Bonjour,
>>
>> Je voudrais savoir si ceci est faisable avec XSLTForms :
>>
>> <xf:model>
>>   <xf:instance src="myExternalInstance.xml"/>
>> </xf:model>
>>
>> Car ça n'a pas l'air de fonctionner chez moi...
>>
>> Cordialement,
>> Grégoire
>>
>>
>> ------------------------------------------------------------------------------
>> SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
>> Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOWhttp://p.sf.net/sfu/solaris-dev2dev
>>
>>
>> _______________________________________________
>> Xsltforms-support mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>
>>  Gregoire,
>> Oui je peux confirmer cette assertion car j'ai eu a utilise un tel
>> mecanisme tout recemment. Si cela ne fonctionne pas chez toi, je te
>> conseillerai que le fichier externe (myExternalInstance.xml) se trouve au
>> bon endroit. C'est a dire dans le meme repertoire que le fichier XSL de
>> XSLTForms. Tu peux aussi utiliser l'option debug pour savoir si le fichier a
>> ete charge ou pas.
>> Par contre, je ne suis pas sur que tu puisses utiliser Google Maps avec
>> XSLTForms j'ai tente a plusieurs sans succes. J'ai meme poste des messages
>> sur le forum mais sans reponse!
>>  Par souci d'equite ou pour beneficier a toute la communaute, je vais
>> poster ma reponse en Anglais :)
>>  Cordialement,
>>  Franclin.
>> *********************************************
>> ENGLISH VERSION
>> *********************************************
>> Gregoire,
>>  I can confirm that it is perfectly possible to do what you are after with
>> XSLTForms. I did a similar stuff recently. If you are unable to make it
>> work, I would strongly suggest that you check the path of your file. You can
>> also make use of the Debug option provided by XSLTForms to find out if the
>> file was loaded at runtime.
>>  However, I still do not believe it is possible to embed XSLTForms with
>> Google Maps maybe because of the excessive JavaScript involved. I have tried
>> different techniques but to no avail. I even posted a lot of messages on
>> this forum but never got a reply. Maybe nobody has a clue.
>>  Regards,
>>  Franclin
>>
>>
>>
>> ------------------------------------------------------------------------------
>> SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
>> Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
>> http://p.sf.net/sfu/solaris-dev2dev
>> _______________________________________________
>> Xsltforms-support mailing list
>> Xsl...@li...
>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>
>>
>

Re: [Xsltforms-support] Support de "src" pour charger une instance externe?

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

Hi,

Thank you Franclin. The "debug" mode was useful. My problem was with my
XPath selector which I use to return the french strings only, like this :

<xf:select1 ref="/search/type">
  <xf:itemset model="myModel"
nodeset="/resources/resource[@xml:lang='fr']/item">
    <xf:label ref="label"/>
    <xf:label ref="value"/>
  </xf:itemset>
</xf:select1>

If I use [@xml:lang='fr'], it doesn't work and XSLTForms stays at the
"Loading..." message in the Select1 widget. An event "xforms-out-of-range"
is dispatched for this widget.

However, if I change my external model to have the attribute "lang='fr'" and
not "xml:lang='fr'", and change the XPath selector accordingly, then it
works perfectly.

It seems there's a bug in XSLTForms with external models and the way
namespaces are dealt with, but I'm not an XPath expert so I may be wrong.

Regards,
Grégoire

2010/2/10 Franclin Foping <f.f...@4c...>

>  On 10/02/10 10:26, Grégoire Colbert wrote:
>
> Bonjour,
>
> Je voudrais savoir si ceci est faisable avec XSLTForms :
>
> <xf:model>
>   <xf:instance src="myExternalInstance.xml"/>
> </xf:model>
>
> Car ça n'a pas l'air de fonctionner chez moi...
>
> Cordialement,
> Grégoire
>
>
> ------------------------------------------------------------------------------
> SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
> Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOWhttp://p.sf.net/sfu/solaris-dev2dev
>
>
> _______________________________________________
> Xsltforms-support mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
>  Gregoire,
> Oui je peux confirmer cette assertion car j'ai eu a utilise un tel
> mecanisme tout recemment. Si cela ne fonctionne pas chez toi, je te
> conseillerai que le fichier externe (myExternalInstance.xml) se trouve au
> bon endroit. C'est a dire dans le meme repertoire que le fichier XSL de
> XSLTForms. Tu peux aussi utiliser l'option debug pour savoir si le fichier a
> ete charge ou pas.
> Par contre, je ne suis pas sur que tu puisses utiliser Google Maps avec
> XSLTForms j'ai tente a plusieurs sans succes. J'ai meme poste des messages
> sur le forum mais sans reponse!
>  Par souci d'equite ou pour beneficier a toute la communaute, je vais
> poster ma reponse en Anglais :)
>  Cordialement,
>  Franclin.
> *********************************************
> ENGLISH VERSION
> *********************************************
> Gregoire,
>  I can confirm that it is perfectly possible to do what you are after with
> XSLTForms. I did a similar stuff recently. If you are unable to make it
> work, I would strongly suggest that you check the path of your file. You can
> also make use of the Debug option provided by XSLTForms to find out if the
> file was loaded at runtime.
>  However, I still do not believe it is possible to embed XSLTForms with
> Google Maps maybe because of the excessive JavaScript involved. I have tried
> different techniques but to no avail. I even posted a lot of messages on
> this forum but never got a reply. Maybe nobody has a clue.
>  Regards,
>  Franclin
>
>
>
> ------------------------------------------------------------------------------
> SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
> Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
> http://p.sf.net/sfu/solaris-dev2dev
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
>

[Xsltforms-support] Problem with validate attribute of submission element

[Aleksandar S. <ale...@pr...>]

Hi,

I have a problem to set validate="false" to submission element.
Form is validated on submission inspite of validate="false".

I looked at .js code and I discovered following:

When validate attribute is defined in submission element (no matter what 
value it has) in XFSubmission definition it is type of string.
And when validate attribute is not defined - it is boolean.
Later on submit there is a line:
if (this.validate && !validate_(node))
and when validate is defined - first part of this if clause will always 
return true no matter what value validate has.

So, from my point of view, some string to boolean conversion has to be 
done somewhere.

Regards.

[Xsltforms-support] Problem with constraint attribute

[Aleksandar S. <ale...@pr...>]

Hi,

I discovered problem with constraint attribute in bind element.

Here is my test xform:

<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="xsltforms/xsltforms.xsl"?>
<html xmlns:xforms="http://www.w3.org/2002/xforms" 
xmlns:ev="http://www.w3.org/2001/xml-events" 
xmlns:an="http://www.together.at/2006/ANOTHER" 
xmlns="http://www.w3.org/1999/xhtml" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xmlns:xpdl="http://www.wfmc.org/2002/XPDL1.0" 
xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
xmlns:xpil="http://www.together.at/2006/XPIL1.0">
<head>
<title>Contact</title>
<xforms:model>

<xforms:instance id="firstInstance">
<xpil:ExtendedWorkflowFacilityInstance>
<xpil:StringDataInstance Id="firstname" 
Value="">INSIDE</xpil:StringDataInstance>
</xpil:ExtendedWorkflowFacilityInstance>
</xforms:instance>

<xforms:bind id="firstname" 
nodeset="instance('firstInstance')/xpil:StringDataInstance/@Value" 
constraint="true()" type="xsd:string" />

</xforms:model>
</head>
<body>
<h2>Contact</h2>
<xforms:group appearance="minimal">

<xforms:input bind="firstname">
<xforms:label>Name</xforms:label>
</xforms:input>

</xforms:group>
</body>
</html>

Problem is that input filed is marked as non-valid inspite 
constraint="true()".
When I enter something in input filed it becomes valid. And when I 
remove value from that input filed it becomes non-valid again.

Is this a bug or I'm missing something?

Regards.

Re: [Xsltforms-support] Support de "src" pour charger une instance externe?

[Franclin F. <f.f...@4c...>]

On 10/02/10 10:26, Grégoire Colbert wrote:
> Bonjour,
>
> Je voudrais savoir si ceci est faisable avec XSLTForms :
>
> <xf:model>
>   <xf:instance src="myExternalInstance.xml"/>
> </xf:model>
>
> Car ça n'a pas l'air de fonctionner chez moi...
>
> Cordialement,
> Grégoire
>
>
> ------------------------------------------------------------------------------
> SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
> Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
> http://p.sf.net/sfu/solaris-dev2dev
>
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>   
Gregoire,
Oui je peux confirmer cette assertion car j'ai eu a utilise un tel
mecanisme tout recemment. Si cela ne fonctionne pas chez toi, je te
conseillerai que le fichier externe (myExternalInstance.xml) se trouve
au bon endroit. C'est a dire dans le meme repertoire que le fichier XSL
de XSLTForms. Tu peux aussi utiliser l'option debug pour savoir si le
fichier a ete charge ou pas.
Par contre, je ne suis pas sur que tu puisses utiliser Google Maps avec
XSLTForms j'ai tente a plusieurs sans succes. J'ai meme poste des
messages sur le forum mais sans reponse!
 Par souci d'equite ou pour beneficier a toute la communaute, je vais
poster ma reponse en Anglais :)
 Cordialement,
 Franclin.
*********************************************
ENGLISH VERSION
*********************************************
Gregoire,
 I can confirm that it is perfectly possible to do what you are after
with XSLTForms. I did a similar stuff recently. If you are unable to
make it work, I would strongly suggest that you check the path of your
file. You can also make use of the Debug option provided by XSLTForms to
find out if the file was loaded at runtime.
 However, I still do not believe it is possible to embed XSLTForms with
Google Maps maybe because of the excessive JavaScript involved. I have
tried different techniques but to no avail. I even posted a lot of
messages on this forum but never got a reply. Maybe nobody has a clue.
 Regards,
 Franclin

[Xsltforms-support] Support de "src" pour charger une instance externe?

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

Bonjour,

Je voudrais savoir si ceci est faisable avec XSLTForms :

<xf:model>
  <xf:instance src="myExternalInstance.xml"/>
</xf:model>

Car ça n'a pas l'air de fonctionner chez moi...

Cordialement,
Grégoire

[Xsltforms-support] Problem with submission and post method

[Aleksandar S. <ale...@pr...>]

**Hi,

I have scenario with several xforms in sequence used for collecting data 
from user.
I need to submit data using POST method so I tried to use:
<xforms:submission id="continue" method="post" replace="all"...
but this doesn't work (xsl transformation is not performed when response 
comes).
replace="instance" doesn't do the job also.
I saw in code that you support method="xml-urlencoded-post" and behavior 
in that case is exactly what I need but this method is not compatible 
with Chiba.
And my xforms need to be compatible with both XSLTForms and Chiba.

Does anyone have idea how I can overcome this issue?
Of course, I don't want to patch XSLTForms code...

Regards.

Re: [Xsltforms-support] Problem with preventing submission

[Aleksandar S. <ale...@pr...>]

Hi Alain,

I've just checked out SVN version and it works. Great!

I'm implementing XSLTForms in Shark project (yes, it is workflow 
management server) as alternative to Chiba.

I have another issue but I will write another mail for that...

Thanks!


On 9.2.2010 21:40, COUTHURES Alain wrote:
> Hi Aleksandar,
>> When I change value in input element validation is properly performed 
>> but I'm able to submit non-valid form.
>> I discovered that I CAN'T submit non-valid form when nodeset in bind 
>> element is "instance('firstInstance')/xpil:StringDataInstance" but I 
>> CAN submit non-valid form when nodset is 
>> "instance('firstInstance')/xpil:StringDataInstance/@Value".
>>
>> Is this bug or I'm missing something?
> Well... Because attributes validation status was not tested before 
> submission, submission was allowed for non valid attributes.
>
> The corresponding instructions have been added in the SVN version.
>
> BTW, I reconsidered the logical test to determine whether a value is 
> valid or not...
>
> Are you experimenting XForms for workflow management ? Do you think 
> this could result in an online demo about that ?
>
> Thanks!
>
> -Alain

Re: [Xsltforms-support] Problem with preventing submission

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

Hi Aleksandar,
> When I change value in input element validation is properly performed 
> but I'm able to submit non-valid form.
> I discovered that I CAN'T submit non-valid form when nodeset in bind 
> element is "instance('firstInstance')/xpil:StringDataInstance" but I 
> CAN submit non-valid form when nodset is 
> "instance('firstInstance')/xpil:StringDataInstance/@Value".
>
> Is this bug or I'm missing something?
Well... Because attributes validation status was not tested before 
submission, submission was allowed for non valid attributes.

The corresponding instructions have been added in the SVN version.

BTW, I reconsidered the logical test to determine whether a value is 
valid or not...

Are you experimenting XForms for workflow management ? Do you think this 
could result in an online demo about that ?

Thanks!

-Alain

[Xsltforms-support] Problem with preventing submission

[Aleksandar S. <ale...@pr...>]

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>

<meta http-equiv="content-type" content="text/html; charset=ISO-8859-2">
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Calibri">Hi,<br>
<br>
I have a problem to prevent submission when form is not valid. Here is
my test case:<br>
<br>
<small><font face="Courier New, Courier, monospace">&lt;?xml
version="1.0" encoding="utf-8"?&gt;<br>
&lt;?xml-stylesheet type="text/xsl" href="xsltforms/xsltforms.xsl"?&gt;<br>
&lt;html xmlns:xforms=<a class="moz-txt-link-rfc2396E" href="http://www.w3.org/2002/xforms">"http://www.w3.org/2002/xforms"</a>
xmlns:ev=<a class="moz-txt-link-rfc2396E" href="http://www.w3.org/2001/xml-events">"http://www.w3.org/2001/xml-events"</a>
xmlns:an=<a class="moz-txt-link-rfc2396E" href="http://www.together.at/2006/ANOTHER">"http://www.together.at/2006/ANOTHER"</a>
xmlns=<a class="moz-txt-link-rfc2396E" href="http://www.w3.org/1999/xhtml">"http://www.w3.org/1999/xhtml"</a>
xmlns:xsi=<a class="moz-txt-link-rfc2396E" href="http://www.w3.org/2001/XMLSchema-instance">"http://www.w3.org/2001/XMLSchema-instance"</a>
xmlns:xpdl=<a class="moz-txt-link-rfc2396E" href="http://www.wfmc.org/2002/XPDL1.0">"http://www.wfmc.org/2002/XPDL1.0"</a>
xmlns:xsd=<a class="moz-txt-link-rfc2396E" href="http://www.w3.org/2001/XMLSchema">"http://www.w3.org/2001/XMLSchema"</a>
xmlns:xpil=<a class="moz-txt-link-rfc2396E" href="http://www.together.at/2006/XPIL1.0">"http://www.together.at/2006/XPIL1.0"</a>&gt;<br>
    &lt;head&gt;<br>
        &lt;title&gt;Contact&lt;/title&gt;<br>
        &lt;xforms:model&gt;<br>
            <br>
            &lt;xforms:submission id="s01" method="post" show="new"
replace="all" action="whatever.xml"&gt;<br>
                &lt;xforms:message level="modeless"
ev:event="xforms-submit-error"&gt;Submit error.&lt;/xforms:message&gt;<br>
            &lt;/xforms:submission&gt;<br>
            <br>
            &lt;xforms:instance id="firstInstance"&gt;<br>
                &lt;xpil:ExtendedWorkflowFacilityInstance&gt;<br>
                    &lt;xpil:StringDataInstance Id="firstname"
Value="VALUE"&gt;INSIDE&lt;/xpil:StringDataInstance&gt;<br>
                &lt;/xpil:ExtendedWorkflowFacilityInstance&gt;<br>
            &lt;/xforms:instance&gt;<br>
            <br>
            &lt;!--THIS DOESN'T WORK GOOD--&gt;<br>
            &lt;xforms:bind id="firstname" required="true()"
nodeset="instance('firstInstance')/xpil:StringDataInstance/@Value"
constraint="string-length(.) &amp;gt; 0" type="xsd:string" /&gt;<br>
            <br>
            &lt;!--THIS WORKS--&gt;<br>
            &lt;!--&lt;xforms:bind id="firstname" required="true()"
nodeset="instance('firstInstance')/xpil:StringDataInstance"
constraint="string-length(.) &amp;gt; 0" type="xsd:string" /&gt;--&gt;<br>
            <br>
        &lt;/xforms:model&gt;<br>
    &lt;/head&gt;<br>
    &lt;body&gt;<br>
        &lt;h2&gt;Contact&lt;/h2&gt;<br>
            &lt;xforms:group appearance="minimal"&gt;<br>
            <br>
                &lt;xforms:input bind="firstname"&gt;<br>
                    &lt;xforms:label&gt;Name&lt;/xforms:label&gt;<br>
                &lt;/xforms:input&gt;<br>
<br>
            &lt;/xforms:group&gt;<br>
            <br>
            &lt;xforms:submit submission="s01"&gt;<br>
                &lt;xforms:label&gt;View&lt;/xforms:label&gt;<br>
            &lt;/xforms:submit&gt;<br>
     &lt;/body&gt;<br>
&lt;/html&gt;<br>
</font></small><br>
When I change value in input element validation is properly performed
but I'm able to submit non-valid form.<br>
I discovered that I CAN'T submit non-valid form when <small><font
 face="Courier New, Courier, monospace">nodeset </font></small>in <small><font
 face="Courier New, Courier, monospace">bind </font></small>element is
"</font><font face="Calibri"><small><font
 face="Courier New, Courier, monospace">instance('firstInstance')/xpil:StringDataInstance</font></small></font><font
 face="Calibri">"</font><font face="Calibri"> but I CAN submit
non-valid form when <small><font face="Courier New, Courier, monospace">nodset</font>
</small>is "</font><font face="Calibri"><small><font
 face="Courier New, Courier, monospace">instance('firstInstance')/xpil:StringDataInstance/@Value</font></small></font><font
 face="Calibri">".<br>
<br>
Is this bug or I'm missing something?<br>
<br>
Regards</font><br>
<b><span
 style="font-size: 9pt; font-family: &quot;Tahoma&quot;,&quot;sans-serif&quot;; letter-spacing: 0.3pt;"
 lang="SR"></span></b><span
 style="font-size: 8pt; font-family: &quot;Tahoma&quot;,&quot;sans-serif&quot;; letter-spacing: 0.3pt;"
 lang="SR"><o:p></o:p></span><o:p><br>
</o:p>
<div class="moz-signature">
<div class="Section1"></div>
</div>
</body>
</html>

Re: [Xsltforms-support] Dialog OK vs. cancel

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

	
	
	-----Original Message-----
	From: Micah Dubinko [mailto:Mic...@ma...]
	Sent: Sunday, February 07, 2010 9:04 PM
	To: COUTHURES Alain
	Cc: xsl...@li...
	Subject: Re: [Xsltforms-support] Dialog OK vs. cancel
	
	
	On Feb 2, 2010, at 1:52 PM, COUTHURES Alain wrote:
	>
	>
	>
	> Then I would suggest another action to abort changes and hide the
	> dialog such as xf:abort or xf:rollback
	>
	> Maybe xf:commit could also be defined for a more explicit back up and
	> xf:reset could have an extra attribute to specify state to be restored....
	>
	> It wouldn't be very difficult to implement this in XSLTForms because
	> for each instance there is already a single srcXML Javascript property.
	> Turning it to an array might be the solution.
	>
	> What do you think?
	
	Sounds fantastic. How much of this is in the 1.2 spec? What can we do to help?
	
	-m
	
	

For 1.2, my personal belief is that we should be putting out smaller modular specs (like the thin-spec that John Boyer did) but have those be essentially final.  Then we produce a core XForms 1.2 document near the end of the charter, filling in the holes.  I'd like to have the modules come from implementors who are either already doing the work (JSON submission from several, xxf:dialog from Orbeon, etc.) or who are concurrently doing the work.  So if you or Alain plan to implement dialog with cancel ability, I'd recommend doing it with a submission or event communication mechanism, see what you like best, and then write up a text description of what it does.  Then the WG can turn that into a REC-track module.

Leigh.

Re: [Xsltforms-support] img within xf:trigger

[christophe g. <chr...@e-...>]

Dear Alain
Thanks a lot for your answer - and for having taken time to look into this
matter.
Agreed, the form is a bit complex - and its core structure is already pretty
well rendered with xsltforms.

I like the idea of directly playing with instance data through a tree view
(and its an important part of some of my forms). I will therefore try to dig
further into the remaining details (e.g. icons rendering) when I have some
more time... but hopefully soon - except if you see a fundamental reason
preventing this to be achievable with xsltforms.

Wishing you an excellent day

Christophe



On Sun, Feb 7, 2010 at 10:34 PM, COUTHURES Alain <
ala...@ag...> wrote:

>  Christophe,
>
>  The first one works quite well
>
> The "geo" example you sent is a quite complex XForms document based on CSS
> and elaborated XPath expressions but I'm not sure that the Mozilla extension
> interprets them correctly:
>
> When selecting every element with an @id at the main repeat, "continent"
> elements are selected. Because they don't have a @structure attribute, their
> names shouldn't be displayed...
>
> About unwanted required and irrelevant icons, they are displayed because of
> inherited CSS classes forcing display.
>
> -Alain
>



-- 
Christophe Geiser, social entrepreneur
e-Smile, solutions in monitoring and information management
--

Re: [Xsltforms-support] Dialog OK vs. cancel

[Micah D. <Mic...@ma...>]

On Feb 2, 2010, at 1:52 PM, COUTHURES Alain wrote:
> 
> 
> 
> Then I would suggest another action to abort changes and hide the dialog 
> such as xf:abort or xf:rollback
> 
> Maybe xf:commit could also be defined for a more explicit back up and 
> xf:reset could have an extra attribute to specify state to be restored....
> 
> It wouldn't be very difficult to implement this in XSLTForms because for 
> each instance there is already a single srcXML Javascript property. 
> Turning it to an array might be the solution.
> 
> What do you think?

Sounds fantastic. How much of this is in the 1.2 spec? What can we do to help?

-m

Re: [Xsltforms-support] img within xf:trigger

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

Christophe,
> The first one works quite well
The "geo" example you sent is a quite complex XForms document based on 
CSS and elaborated XPath expressions but I'm not sure that the Mozilla 
extension interprets them correctly:

When selecting every element with an @id at the main repeat, "continent" 
elements are selected. Because they don't have a @structure attribute, 
their names shouldn't be displayed...

About unwanted required and irrelevant icons, they are displayed because 
of inherited CSS classes forcing display.

-Alain

Re: [Xsltforms-support] repeat with //*[@attribute]

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

Christophe,
> an expression like <xf:repeat nodeset="instance('data')//*[@id]"/> 
> seems to have some difficulties to be properly evaluated.
I have discovered that a predicate such as [@id] was evaluated as 
[number(@id)] or [position() = number(@id)] when its value was 
eventually a number : if the predicate value could be converted to a 
number it was interpreted as an index in collection.

I have now fixed this and it's committed in the SVN repository.

Thanks!

-Alain

Re: [Xsltforms-support] xsltforms Performance

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

Christopher,
> After investigating this a bit further, I noticed that the xforms-recalculate event was being called twice--once from XFControl.prototype.valueChanged and again from xforms.closeAction.
>   
I have checked AJAXForms sources and it appears it was already like 
that. It seems impossible to contact AJAXForms creator so I won't be 
able to say why there is this double call.
> It seems to me that XFControl.prototype.valueChanged does all the leg work so that xforms.closeAction will recalculate and revalidate the instance.
Yes, xforms.closeChanges is called to perform the necessary event 
dispatches when everything is done and I agree that this should be the 
only place for xforms-recalculate to be dispatched.
>   By removing the line:
>
> XMLEvents.dispatch(model, "xforms-recalculate");
>
> from XFControl.prototype.valueChanged,
The next line:

xforms.refresh();

should also be removed for the same reason or it would disturb 
xforms.closeChanges.
>  I was able to almost halve the time it takes a user to "tab" from one field to the next.
Very interesting indeed because IE is so slow...
>   Preliminary testing indicates that there are no negative side effects.
>
> Is there any reason why this cannot be a permanent (albeit partial) fix for this issue?
>   
The SVN version is now integrating your suggestion. My own tests are 
passed but more are required to be sure...

Thanks!

-Alain

Re: [Xsltforms-support] external css

[Thorsten R. <t...@sc...>]

Hi

I just discovered, that the XML root tag will make firefox ignore the
first css rule. Workaround is to add a dummy rule like this:
.dummy {}

    Regards
   Thorsten

[Xsltforms-support] external css

[Thorsten R. <ju...@sc...>]

Hi

I encountered the external css problem and found the solution in the
list archive. It would be very helpful if there were some alert (not a
JS alert window) about the failure, at least in the debug messages. Why
does XSLTforms have to parse the external css at all? I guess there are
good reasons, just curious.

    Regards
   Thorsten