xsltforms-support — XSLTForms support list

Re: [Xsltforms-support] New browser-based XForms processor

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

Hi Claudius,

For performance increasing, especially because of IE slowness,  I'm also 
considering XML data islands to be used by XSLTForms instead of 
Javascript objects. Those Javascript objects are now also used to store 
meta data whether the corresponding node (which might be an attribute) 
is valid, read-only, associated with an XML Schema type and so on. 
That's why instance data would have to be expanded with extra attributes 
and attributes would have to be stored as elements! XSLT might then help 
for expanding and serializing.

Using native XPath is also an interesting idea for reducing Javascript 
number of instructions about all those meta data. Unfortunately, native 
XPath is just XPath 1.0. XForms recommendation defines very useful extra 
XPath functions and, probably XPath 2.0 will be considered for next 
recommendation. Those functions are mandatory for effective web 
applications without Javascript instructions. That's why XSLTForms will 
keep its own XPath engine for evaluating "XForms" XPath expressions. 
There is another important reason for this: when performing an XPath 
evaluation, XSLTForms collects dependencies and I don't know how this 
could be done in a different manner.

I will look at your new project with great interest.

-Alain
> Hi,
>
> I have started to develop a new browser-based XForms processor, which 
> will make use of browsers' native XPath and XSLT capabilities.
> Thus, the approach is as follows:
> - transforming XForms page into XHTML + JS page by using XSLT in 
> browser (Alain Couthures' very good idea);
> - storing instance data as XML within the page;
> - bounding this data to UI controls by using browsers' 
> document.evaluate() function (except IE, which is a rara avis, and 
> will be dealt with later);
>  
> A very small example can be found here: 
> http://extxsltforms.sourceforge.net/sitKubera/examples/kuberaForms/example1.xml
>
> The project will be hosted here: 
> http://sourceforge.net/projects/kuberaforms/
>
>
> Claudius Teodorescu
> http://kuberam.ro
>
>

[Xsltforms-support] Discussion forum for eXSLTForms

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

Hi,

For all those interested, I have opened a discussion forum for eXSLTForms http://sourceforge.net/projects/extxsltforms/forums/forum/1152497

Claudius Teodorescu
http://kuberam.ro



      

Re: [Xsltforms-support] Display two inputs for one field; one readonly the other editable

[Mark v. d. B. <ko...@gm...>]

Done it the CSS way, but only one problem remains: when a value is
long it will stretch the field, a inputfield wil allow the user to
scroll through the contents of the box.

2010/5/26 Steven Pemberton <Ste...@cw...>:
> On Wed, 26 May 2010 12:50:30 +0200, Mark van den Boomen <ko...@gm...>
> wrote:
>
>> The problem is that the client wants to hold on to the look of an old
>> (oracle forms) application, and those applications show readonly data
>> with a disabled inputfield.
>
> That's just a CSS issue. Shouldn't be hard.
>
> Best wishes,
>
> Steven Pemberton
>
>>
>> 2010/5/26 Steven Pemberton <Ste...@cw...>:
>>>
>>> On Wed, 26 May 2010 12:11:19 +0200, Mark van den Boomen
>>> <ko...@gm...> wrote:
>>>
>>>> Given the following XML:
>>>>
>>>> <root>
>>>>  <item>
>>>>    <value>1</value>
>>>>  </item>
>>>>  <item>
>>>>    <value>2</value>
>>>>  </item>
>>>>  <item>
>>>>    <value>3</value>
>>>>  </item>
>>>> </root>
>>>>
>>>> The items are displayed in a table using xforms:repeat containing the
>>>> editable inputs. Under the table is a xforms:input which should be
>>>> disabled. If an user sets focus to one of the editable inputs then the
>>>> input under the table should show the value of the selected input in
>>>> the table.
>>>>
>>>> The problem is when using a xforms:bind to set the value to readonly
>>>> it will set both inputs readonly. Is there a way to set the readonly
>>>> independent for the inputs?
>>>
>>> I'm not sure if I understand the problem, but why not use an <output>
>>> under the table, and an input in the repeat?
>>>
>>> Best wishes,
>>>
>>> Steven Pemberton
>>>
>>>>
>>>> Thanks,
>>>>
>>>> Mark
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>>
>>>> _______________________________________________
>>>> 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] Display two inputs for one field; one readonly the other editable

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

On Wed, 26 May 2010 12:50:30 +0200, Mark van den Boomen  
<ko...@gm...> wrote:

> The problem is that the client wants to hold on to the look of an old
> (oracle forms) application, and those applications show readonly data
> with a disabled inputfield.

That's just a CSS issue. Shouldn't be hard.

Best wishes,

Steven Pemberton

>
> 2010/5/26 Steven Pemberton <Ste...@cw...>:
>> On Wed, 26 May 2010 12:11:19 +0200, Mark van den Boomen
>> <ko...@gm...> wrote:
>>
>>> Given the following XML:
>>>
>>> <root>
>>>   <item>
>>>     <value>1</value>
>>>   </item>
>>>   <item>
>>>     <value>2</value>
>>>   </item>
>>>   <item>
>>>     <value>3</value>
>>>   </item>
>>> </root>
>>>
>>> The items are displayed in a table using xforms:repeat containing the
>>> editable inputs. Under the table is a xforms:input which should be
>>> disabled. If an user sets focus to one of the editable inputs then the
>>> input under the table should show the value of the selected input in
>>> the table.
>>>
>>> The problem is when using a xforms:bind to set the value to readonly
>>> it will set both inputs readonly. Is there a way to set the readonly
>>> independent for the inputs?
>>
>> I'm not sure if I understand the problem, but why not use an <output>
>> under the table, and an input in the repeat?
>>
>> Best wishes,
>>
>> Steven Pemberton
>>
>>>
>>> Thanks,
>>>
>>> Mark
>>>
>>> ------------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> 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] Display two inputs for one field; one readonly the other editable

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

Clearly the second input should be an output. An output is just an input  
that is always read-only.

Best wishes,

Steven Pemberton

On Wed, 26 May 2010 15:02:30 +0200, Mark van den Boomen  
<ko...@gm...> wrote:

> Hi Javier,
>
> Here is the code illustrating the problem:
>
> <?xml-stylesheet href="xsltforms/xsltforms.xsl" type="text/xsl"?>
> <?xsltforms-options debug="yes"?>
> <html xmlns="http://www.w3.org/1999/xhtml"
>       xmlns:xf="http://www.w3.org/2002/xforms"
>       xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>       xmlns:ev="http://www.w3.org/2001/xml-events"
>       xml:lang="nl" lang="nl">
>   <head>
>
>   <title>Test</title>
>
>   <xf:model id="overzicht">
>     <xf:instance id="selectiescherm">
>       <root>
>        <item>
>          <value>1</value>
>        </item>
>        <item>
>          <value>2</value>
>        </item>
>        <item>
>          <value>3</value>
>        </item>
>       </root>
>     </xf:instance>
>     <xf:bind nodeset="/root/item/value" readonly="false()" />
>   </xf:model>
>
>   </head>
>   <body>
>     <table>
>       <xf:repeat nodeset="/root/item" id="items">
>         <tr>
>           <td>
>             <strong>This field should be editable:</strong>
>             <xf:input ref="value" />
>           </td>
>         </tr>
>       </xf:repeat>
>     </table>
>     <hr/>
>     <strong>This field should be readonly:</strong>
>     <xf:input ref="/root/item[position() = index('items')]/value" />
>   </body>
> </html>
>
>
> I think that your code is solving not the same problem as mine.
>
> Thanks
>
> Mark
>
> 2010/5/26 Javier Díaz <jd...@ge...>:
>>
>> Do you have the complete example? With inputs, binds, and so on. I  
>> think we
>> did something similar, I'm not sure if may help you.
>>
>>
>> <xf:bind
>> nodeset="/ACT_INTERCONEXION_IP/TRAZADO/POLITICA_INTERCONEXION/INTERCONEXION[*]/pPAI_IP[*]/ID_PPAI_IP"
>> relevant="true()" required="true()"
>> readonly="not(compare(instance('estado')/ACCION,'BAJA'))"
>> constraint="count(../../pPAI_IP[ID_PPAI_IP = current()]) &lt; 2"
>> type="xsd:string"/>
>>
>> We have a xforms with the following binding, and the constraint is  
>> activated
>> only in these elements of the repeat where the xpath assertion is true.  
>> In
>> our case, we get an error message when two elements of the repeat had  
>> the
>> same value.
>>
>> I don't know if this is similar with focus event, I hope it may help  
>> you.
>>
>> Best Regards,
>> Javier
>>
>> Thanks,
>>
>> Mark
>>
>> ------------------------------------------------------------------------------
>>
>> _______________________________________________
>> 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] Display two inputs for one field; one readonly the other editable

[Mark v. d. B. <ko...@gm...>]

Hi Javier,

Here is the code illustrating the problem:

<?xml-stylesheet href="xsltforms/xsltforms.xsl" type="text/xsl"?>
<?xsltforms-options debug="yes"?>
<html xmlns="http://www.w3.org/1999/xhtml"
      xmlns:xf="http://www.w3.org/2002/xforms"
      xmlns:xsd="http://www.w3.org/2001/XMLSchema"
      xmlns:ev="http://www.w3.org/2001/xml-events"
      xml:lang="nl" lang="nl">
  <head>

  <title>Test</title>

  <xf:model id="overzicht">
    <xf:instance id="selectiescherm">
      <root>
       <item>
         <value>1</value>
       </item>
       <item>
         <value>2</value>
       </item>
       <item>
         <value>3</value>
       </item>
      </root>
    </xf:instance>
    <xf:bind nodeset="/root/item/value" readonly="false()" />
  </xf:model>

  </head>
  <body>
    <table>
      <xf:repeat nodeset="/root/item" id="items">
        <tr>
          <td>
            <strong>This field should be editable:</strong>
            <xf:input ref="value" />
          </td>
        </tr>
      </xf:repeat>
    </table>
    <hr/>
    <strong>This field should be readonly:</strong>
    <xf:input ref="/root/item[position() = index('items')]/value" />
  </body>
</html>


I think that your code is solving not the same problem as mine.

Thanks

Mark

2010/5/26 Javier Díaz <jd...@ge...>:
>
> Do you have the complete example? With inputs, binds, and so on. I think we
> did something similar, I'm not sure if may help you.
>
>
> <xf:bind
> nodeset="/ACT_INTERCONEXION_IP/TRAZADO/POLITICA_INTERCONEXION/INTERCONEXION[*]/pPAI_IP[*]/ID_PPAI_IP"
> relevant="true()" required="true()"
> readonly="not(compare(instance('estado')/ACCION,'BAJA'))"
> constraint="count(../../pPAI_IP[ID_PPAI_IP = current()]) &lt; 2"
> type="xsd:string"/>
>
> We have a xforms with the following binding, and the constraint is activated
> only in these elements of the repeat where the xpath assertion is true. In
> our case, we get an error message when two elements of the repeat had the
> same value.
>
> I don't know if this is similar with focus event, I hope it may help you.
>
> Best Regards,
> Javier
>
> Thanks,
>
> Mark
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

Re: [Xsltforms-support] Display two inputs for one field; one readonly the other editable

[Javier D. <jd...@ge...>]

Mark van den Boomen escribió:
> Given the following XML:
>
> <root>
>   <item>
>     <value>1</value>
>   </item>
>   <item>
>     <value>2</value>
>   </item>
>   <item>
>     <value>3</value>
>   </item>
> </root>
>
> The items are displayed in a table using xforms:repeat containing the
> editable inputs. Under the table is a xforms:input which should be
> disabled. If an user sets focus to one of the editable inputs then the
> input under the table should show the value of the selected input in
> the table.
>
> The problem is when using a xforms:bind to set the value to readonly
> it will set both inputs readonly. Is there a way to set the readonly
> independent for the inputs?
>   
Do you have the complete example? With inputs, binds, and so on. I think
we did something similar, I'm not sure if may help you.


<xf:bind
nodeset="/ACT_INTERCONEXION_IP/TRAZADO/POLITICA_INTERCONEXION/INTERCONEXION[*]/pPAI_IP[*]/ID_PPAI_IP"
relevant="true()" required="true()"
readonly="not(compare(instance('estado')/ACCION,'BAJA'))"
constraint="*count(../../pPAI_IP[ID_PPAI_IP = current()]) &lt; 2*"
type="xsd:string"/>

We have a xforms with the following binding, and the constraint is
activated only in these elements of the repeat where the xpath assertion
is true. In our case, we get an error message when two elements of the
repeat had the same value.

I don't know if this is similar with focus event, I hope it may help you.

Best Regards,
Javier
> Thanks,
>
> Mark
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>   

Re: [Xsltforms-support] Display two inputs for one field; one readonly the other editable

[Mark v. d. B. <ko...@gm...>]

The problem is that the client wants to hold on to the look of an old
(oracle forms) application, and those applications show readonly data
with a disabled inputfield.

2010/5/26 Steven Pemberton <Ste...@cw...>:
> On Wed, 26 May 2010 12:11:19 +0200, Mark van den Boomen
> <ko...@gm...> wrote:
>
>> Given the following XML:
>>
>> <root>
>>   <item>
>>     <value>1</value>
>>   </item>
>>   <item>
>>     <value>2</value>
>>   </item>
>>   <item>
>>     <value>3</value>
>>   </item>
>> </root>
>>
>> The items are displayed in a table using xforms:repeat containing the
>> editable inputs. Under the table is a xforms:input which should be
>> disabled. If an user sets focus to one of the editable inputs then the
>> input under the table should show the value of the selected input in
>> the table.
>>
>> The problem is when using a xforms:bind to set the value to readonly
>> it will set both inputs readonly. Is there a way to set the readonly
>> independent for the inputs?
>
> I'm not sure if I understand the problem, but why not use an <output>
> under the table, and an input in the repeat?
>
> Best wishes,
>
> Steven Pemberton
>
>>
>> Thanks,
>>
>> Mark
>>
>> ------------------------------------------------------------------------------
>>
>> _______________________________________________
>> 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] Display two inputs for one field; one readonly the other editable

[Mark v. d. B. <ko...@gm...>]

Look promissing but pitty it's not ready jet.

2010/5/26 Kostis Anagnostopoulos <ank...@gm...>:
> Maybe this is a good "excuse" to start heading for MIPs on UI controls:
> See xforms future features:
> http://www.w3.org/MarkUp/Forms/wiki/Add_model_item_properties_to_UI_level
>
> Regards,
>  Kostis Anagnostopoulos
>

Re: [Xsltforms-support] Display two inputs for one field; one readonly the other editable

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

On Wed, 26 May 2010 12:11:19 +0200, Mark van den Boomen  
<ko...@gm...> wrote:

> Given the following XML:
>
> <root>
>   <item>
>     <value>1</value>
>   </item>
>   <item>
>     <value>2</value>
>   </item>
>   <item>
>     <value>3</value>
>   </item>
> </root>
>
> The items are displayed in a table using xforms:repeat containing the
> editable inputs. Under the table is a xforms:input which should be
> disabled. If an user sets focus to one of the editable inputs then the
> input under the table should show the value of the selected input in
> the table.
>
> The problem is when using a xforms:bind to set the value to readonly
> it will set both inputs readonly. Is there a way to set the readonly
> independent for the inputs?

I'm not sure if I understand the problem, but why not use an <output>  
under the table, and an input in the repeat?

Best wishes,

Steven Pemberton

>
> Thanks,
>
> Mark
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support

Re: [Xsltforms-support] Display two inputs for one field; one readonly the other editable

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

Maybe this is a good "excuse" to start heading for MIPs on UI controls:
See xforms future features:
http://www.w3.org/MarkUp/Forms/wiki/Add_model_item_properties_to_UI_level

Regards,
 Kostis Anagnostopoulos

On Wed, May 26, 2010 at 1:11 PM, Mark van den Boomen <ko...@gm...> wrote:
> Given the following XML:
>
> <root>
>  <item>
>    <value>1</value>
>  </item>
>  <item>
>    <value>2</value>
>  </item>
>  <item>
>    <value>3</value>
>  </item>
> </root>
>
> The items are displayed in a table using xforms:repeat containing the
> editable inputs. Under the table is a xforms:input which should be
> disabled. If an user sets focus to one of the editable inputs then the
> input under the table should show the value of the selected input in
> the table.
>
> The problem is when using a xforms:bind to set the value to readonly
> it will set both inputs readonly. Is there a way to set the readonly
> independent for the inputs?
>
> Thanks,
>
> Mark
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

[Xsltforms-support] Display two inputs for one field; one readonly the other editable

[Mark v. d. B. <ko...@gm...>]

Given the following XML:

<root>
  <item>
    <value>1</value>
  </item>
  <item>
    <value>2</value>
  </item>
  <item>
    <value>3</value>
  </item>
</root>

The items are displayed in a table using xforms:repeat containing the
editable inputs. Under the table is a xforms:input which should be
disabled. If an user sets focus to one of the editable inputs then the
input under the table should show the value of the selected input in
the table.

The problem is when using a xforms:bind to set the value to readonly
it will set both inputs readonly. Is there a way to set the readonly
independent for the inputs?

Thanks,

Mark

Re: [Xsltforms-support] Click on a read-only input field

[Dhiradj B. <dh...@gm...>]

Here is an example of the HTML for an input-field that has been set to
read-only. Actually it gets the HTML property 'disabled' instead of
'read-only'. I think this also depends on which browser you use. I use
Firefox. Right now, we have a workaround. We've made some modifications to
the javascript to accomplish that the property 'read-only' is set.

<span id="xf-input-1" class="activiteita  xforms-control xforms-input
xforms-appearance xforms-optional xforms-enabled xforms-readonly
xforms-valid  "><span><span><span class="focus">&nbsp;</span><
span><label id="xf-label-1"
class="xforms-label">Activiteit:</label></span><span class="value"><input
type="text" class="xforms-value" *disabled=""*/></span><span><span
class="xforms-required-icon">*</span><span class="xforms-alert"><span
class="xforms-alert-icon">&nbsp;</span></span></span></span></span></span>

Re: [Xsltforms-support] properties.doc.documentElement is null

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

Thank you for the suggestion. The XForms forms do double-duty as REST-like
XML remote procedure calls, so I can't expect the clients to be able to
support a complete XForms implementation. I have to keep it simple.

The good news is that after beating on it all day long, I've come up with a
little patch to the xsltforms.js file which appears to fix the issue with
double-escaping entities. Before I turn it loose, I need to make sure that
it doesn't break anything else. Stay tuned.

On Tue, May 25, 2010 at 7:57 PM, Stephen Cameron <
Ste...@ut...> wrote:

> Hi Chris,
>
> I'm not sure if this will help, but perhaps another approach to what you
> are trying to achieve is possible.
>
> If you use the xforms <switch> construct you can completely change the
> appearance of the form and also do a submission at the time you move from
> one <case> to another.
>
> I think one of the main ideas in Xforms is that the view adapts to the
> content of the model and the model can change due to user interaction, so
> the idea of dynamically generating a form server side does not make much
> sense in general.
>
> The <switch> was a revelation for me when I discovered it, it pays to read
> up before you start doing anything with Xforms.
>
>
>
> --
> Regards
>
> Stephen Cameron
>
> Data Programmer
> Integrated Marine Observing System  (IMOS)
> eMarine Information Infrastructure Project
> University of Tasmania, Private Bag 21, Hobart, TAS 7001, Australia
>
> Tel: +61 3 6226 8507
> Fax: +61 3 6226 2997
> Email: ste...@ut...
> URL: http://www.imos.org.au/eMII.html
>
>

Re: [Xsltforms-support] properties.doc.documentElement is null

[Stephen C. <Ste...@ut...>]

Hi Chris,

I'm not sure if this will help, but perhaps another approach to what you are trying to achieve is possible.

If you use the xforms <switch> construct you can completely change the appearance of the form and also do a submission at the time you move from one <case> to another.

I think one of the main ideas in Xforms is that the view adapts to the content of the model and the model can change due to user interaction, so the idea of dynamically generating a form server side does not make much sense in general.

The <switch> was a revelation for me when I discovered it, it pays to read up before you start doing anything with Xforms.



-- 
Regards

Stephen Cameron

Data Programmer
Integrated Marine Observing System  (IMOS)
eMarine Information Infrastructure Project
University of Tasmania, Private Bag 21, Hobart, TAS 7001, Australia

Tel: +61 3 6226 8507
Fax: +61 3 6226 2997
Email: ste...@ut...
URL: http://www.imos.org.au/eMII.html

Re: [Xsltforms-support] properties.doc.documentElement is null

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

I know it's in poor taste to post a reply to one's own post, but I'm
currently stuck and desperate. That's a bad combination. :)

Doing a comparison on the transformed XForms form, I notice that the escaped
<tags> are re-escaped on the second form in the generated Javascript. i.e.

<xforms:input> becomes '&lt;xforms:input&gt;' in the first form.
&lt;xforms:input&gt; becomes '&amp;lt;xforms:input&amp;gt;' in the second
form.
and I suspect (although it all crashes, so I can't get a good read to tell
for sure) that on the third form it would become
'&amp;amp;lt;xforms:input&amp;amp;gt;'

Now there is an escapeEntities.xsl.xml component that I /think/ was designed
to mitigate this problem. Is that perhaps malfunctioning on iterative calls
to the XForms form?





On Mon, May 24, 2010 at 4:24 PM, Chris Gamache <cga...@gm...> wrote:

> This happens on the third post.
>
> XSLTForms Exception
> --------------------------
>
> Error initializing :
>
> ("status")@http://path/to/xsltforms/xsltforms.js:640
> ()@http://path/to/xsltforms/xsltforms.js:1071
> initImpl()@http://path/to/breakfast.xml:30
> init()@http://path/to/breakfast.xml:36
> onload([object Event])@http://path/to/breakfast.xml:1
>
>
> TypeError
>
> properties.doc.documentElement is null
>
>
>
>
>
>
> The served XML will render when it is not generated as a result of another
> XForms form.
>
> I'm using revision 403. Any ideas?
>

Re: [Xsltforms-support] Click on a read-only input field

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

I've never heard of an /input/ field that didn't have the potential to take
/input/.

The behavior you cite for "read-only" is the correct behavior in XForms.

Perhaps you could post a proof-of-concept example. If we see what you're
talking about, maybe we'll understand what you're trying to accomplish.


On Tue, May 25, 2010 at 9:05 AM, Dhiradj Badloe <dh...@gm...> wrote:

> Hi Chris,
>
> Your solution only works for editable input fields, not for read-only input
> fields. I use Firefox as browser.
> Another issue that I found was that is when you set an input field to
> read-only it actually is a disabled input field in XSLTForms.
> Thanks anyway.
>
> Regards,
> Dhiradj
>
>
> On Tue, May 25, 2010 at 2:42 PM, Chris Gamache <cga...@gm...> wrote:
>
>> This works...
>>
>> ...
>> <xforms:bind nodeset="/foo/bar" readonly="true()" />
>> ...
>>         <xforms:input ref="/foo/bar">
>>             <xforms:label>Baz: </xforms:label>
>>             <xforms:action ev:event="DOMFocusIn">
>>                 <xforms:message level="modal">Ow!</xforms:message>
>>             </xforms:action>
>>         </xforms:input>
>>
>> HTH!
>>
>> On Tue, May 25, 2010 at 8:00 AM, Dhiradj Badloe <dh...@gm...>wrote:
>>
>>> Hi all,
>>>
>>> I want a read-only input field to be clickable, so I can tie it to an
>>> action. Is this possible with XSLTForms?
>>>
>>> Thanks.
>>>
>>> Warm regards,
>>>
>>> Dhiradj Badloe
>>>
>>>
>>> ------------------------------------------------------------------------------
>>>
>>>
>>> _______________________________________________
>>> Xsltforms-support mailing list
>>> Xsl...@li...
>>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>>
>>>
>>
>

Re: [Xsltforms-support] Click on a read-only input field

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

This works...

...
<xforms:bind nodeset="/foo/bar" readonly="true()" />
...
        <xforms:input ref="/foo/bar">
            <xforms:label>Baz: </xforms:label>
            <xforms:action ev:event="DOMFocusIn">
                <xforms:message level="modal">Ow!</xforms:
message>
            </xforms:action>
        </xforms:input>

HTH!


On Tue, May 25, 2010 at 8:00 AM, Dhiradj Badloe <dh...@gm...> wrote:

> Hi all,
>
> I want a read-only input field to be clickable, so I can tie it to an
> action. Is this possible with XSLTForms?
>
> Thanks.
>
> Warm regards,
>
> Dhiradj Badloe
>
>
> ------------------------------------------------------------------------------
>
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
>

Re: [Xsltforms-support] Filtering on a repeat table not workingcorrectly

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

Hi Dhiradj,

Can you please send me a test case about this bug?

Thanks!

-Alain

 
Hi all,

I apply filtering on a repeat table with a xforms:select1. This seems to work fine, but after a while(after selecting a few items from the list) it stops working. I don't know what really causes this problem. Maybe a Javascript bug or the event stops executing after a while? Anyone familiar with this or similar problems? Thanks.

Regards,

Dhiradj

[Xsltforms-support] Filtering on a repeat table not working correctly

[Dhiradj B. <dh...@gm...>]

Hi all,

I apply filtering on a repeat table with a xforms:select1. This seems to
work fine, but after a while(after selecting a few items from the list) it
stops working. I don't know what really causes this problem. Maybe a
Javascript bug or the event stops executing after a while? Anyone familiar
with this or similar problems? Thanks.

Regards,

Dhiradj

[Xsltforms-support] Click on a read-only input field

[Dhiradj B. <dh...@gm...>]

Hi all,

I want a read-only input field to be clickable, so I can tie it to an action.
Is this possible with XSLTForms?

Thanks.

Warm regards,

Dhiradj Badloe

Re: [Xsltforms-support] Improving XSLTForms performance in IE

[Stephen C. <Ste...@ut...>]

Thanks Alain,

See my comments

COUTHURES Alain wrote:
> Hi Steve
>> I recently had feed-back from some users and the main issue was slow 
>> form loading in IE.
>>   
> Real world feed-backs are always interesting. There are two situations 
> where it can be slow with IE: at form loading and at form refreshing.
>> I am wondering if there may be ways to get around this. I think that 
>> I am mainly having problems due to large XML files being included as 
>> external xform instances, that are then parsed into 'XDocument' 
>> javascript objects by XSLTForms.
>>   
> Maybe external instances should be loaded at the XSLT step. It could 
> also be possible to generate all the XNode calls at the XSLT step to 
> eliminate both the XSLT serialization and the Javascript parsing!
>> I previously asked Alain if these could be natively parsed as 
>> DOMDocument objects by the browser and then used as such by 
>> XSLTForms. I think that the reason why this could not work is the 
>> lack of XPath support in browsers. However, I now wonder if a 
>> half-way house solution might work. That is XNodes are wrapper 
>> objects for DOMNodes and the XSLTForms Xpath evaluations are actually 
>> using the DOMNode name, values (or childNodes) behind the scenes.
>>   
> DOMNodes are not exactly the same for each browser... and there are 
> already some Javascript instructions to handle this.
>> So the XDocument.parse() method would, in the case of external 
>> instances, build a tree of XNodes each holding a reference to a 
>> DOMNode and for each evaluation of such an XNode, the node itself 
>> would have to decide if it was purely javascript based or DOMNode 
>> based. If this mechanism might possibly work, I'd be happy to have a 
>> go at trying it out.
>>   
> A native Javascript parsing would probably require to add extra 
> attributes and methods to obtain an identical structure for each browser.
>> I think XSLTforms has a niche only because all browsers do not 
>> support the Xforms standard natively. If you are an organisation 
>> using Xforms then there is no problem to use a plugin (though I've 
>> not tried one), so XSLTforms is filling the opportunity for a 
>> cross-browser solution but it hasn't quite got there yet in my view 
>> due to the current slowness in IE. Realistically, trying to add more 
>> feature support is not a good use of time whilst this problem exists.
>>   
> XForms as a plug-in sounds to me more or less like an abandoned 
> solution today. Server-side solutions seem to be more and more active 
> but XSLTForms is apparently the only client-side solution being 
> improved now.
>
> About new features, upload is still on the list.
>> Browsers are very fast at parsing XML and also transforming using 
>> XSLT, it seems to me that XSLTForms is making good use of the later 
>> but ignoring the potential of the former.
>>   
> Yes, you're right and it would fix some serialization problems. ;-)
I don't understand fully the implications of what you are saying above 
but it sounds like there are some possibilities to try that might 
improve things, which is good news. I'll send you something that I did 
before as a test that might be relevant to this discussion. I hope i can 
do some tests on this area soon.

Also, IE 9.0 looks to hold some promise of improved javascript 
performance, so longer term the prospects for XSLTforms with IE seem 
brighter. This is not to say that improvements across all browsers 
aren't desirable and worth exploring.

>> Not using IE is an option perhaps, but you have to ask what is XForms 
>> competing against and is the competion working OK in IE?
> Are you talking about IE 6 too???
No IE 6 is too old to worry about, I'd be happy just to consider IE 7 & 
8, I am interested in scientists working in institutions that might have 
a restriction on installing software on PCs, if this means still using 
IE6 then something is badly wrong, larger institutions maybe not so 
easy. I am not interested in forms for use by the general public, these 
usually need coded business logic on the server anyway so you might as 
well use a server-side solution to be able to include that.

>
>> For me at least the competition is AJAX frameworks that can 
>> auto-generate a web-app from a relational database schema and do 
>> client-side validation. There are plenty of options in this space and 
>> all work well in IE I'd say (we use ZK framework).
>>   
> XForms is better with XML databases of course.
>
> XSLTForms doesn't have full-time contributors yet but it would deserve 
> them...
Agreed, my interest is similar to XML databases, to be able to easily 
set up a XML web-service and interact with it via XForms, that is, with 
very little programming skills and effort. I'd like at some stage soon 
to set up a site to promote this idea and provide example forms to study 
or copy. Also, looking at what the XRX model offers for scientific data 
management and handling as well.

>> My intention is not to put down XSLTforms at all, just to state my 
>> concerns about priorities.
>>   
> Strategy is important and performance might block real-world use if it 
> isn't considered enough.
>
> I have to study all this for each recent browser now. Do you have a 
> list of browsers to be supported by XSLTForms?
>
> Thanks!
>
> -Alain
>
>


-- 
Regards

Stephen Cameron

Data Programmer
Integrated Marine Observing System  (IMOS)
eMarine Information Infrastructure Project
University of Tasmania, Private Bag 21, Hobart, TAS 7001, Australia

Tel: +61 3 6226 8507
Fax: +61 3 6226 2997
Email: ste...@ut...
URL: http://www.imos.org.au/eMII.html

Re: [Xsltforms-support] Improving XSLTForms performance in IE

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

Hi Steve
> I recently had feed-back from some users and the main issue was slow 
> form loading in IE.
>   
Real world feed-backs are always interesting. There are two situations 
where it can be slow with IE: at form loading and at form refreshing.
> I am wondering if there may be ways to get around this. I think that I 
> am mainly having problems due to large XML files being included as 
> external xform instances, that are then parsed into 'XDocument' 
> javascript objects by XSLTForms.
>   
Maybe external instances should be loaded at the XSLT step. It could 
also be possible to generate all the XNode calls at the XSLT step to 
eliminate both the XSLT serialization and the Javascript parsing!
> I previously asked Alain if these could be natively parsed as 
> DOMDocument objects by the browser and then used as such by XSLTForms. I 
> think that the reason why this could not work is the lack of XPath 
> support in browsers. However, I now wonder if a half-way house solution 
> might work. That is XNodes are wrapper objects for DOMNodes and the 
> XSLTForms Xpath evaluations are actually using the DOMNode name, values 
> (or childNodes) behind the scenes.
>   
DOMNodes are not exactly the same for each browser... and there are 
already some Javascript instructions to handle this.
> So the XDocument.parse() method would, in the case of external 
> instances, build a tree of XNodes each holding a reference to a DOMNode 
> and for each evaluation of such an XNode, the node itself would have to 
> decide if it was purely javascript based or DOMNode based. If this 
> mechanism might possibly work, I'd be happy to have a go at trying it out.
>   
A native Javascript parsing would probably require to add extra 
attributes and methods to obtain an identical structure for each browser.
> I think XSLTforms has a niche only because all browsers do not support 
> the Xforms standard natively. If you are an organisation using Xforms 
> then there is no problem to use a plugin (though I've not tried one), so 
> XSLTforms is filling the opportunity for a cross-browser solution but it 
> hasn't quite got there yet in my view due to the current slowness in IE. 
> Realistically, trying to add more feature support is not a good use of 
> time whilst this problem exists.
>   
XForms as a plug-in sounds to me more or less like an abandoned solution 
today. Server-side solutions seem to be more and more active but 
XSLTForms is apparently the only client-side solution being improved now.

About new features, upload is still on the list.
> Browsers are very fast at parsing XML and also transforming using XSLT, 
> it seems to me that XSLTForms is making good use of the later but 
> ignoring the potential of the former.
>   
Yes, you're right and it would fix some serialization problems. ;-)
> Not using IE is an option perhaps, but you have to ask what is XForms 
> competing against and is the competion working OK in IE?
Are you talking about IE 6 too???
> For me at least 
> the competition is AJAX frameworks that can auto-generate a web-app from 
> a relational database schema and do client-side validation. There are 
> plenty of options in this space and all work well in IE I'd say (we use 
> ZK framework).
>   
XForms is better with XML databases of course.

XSLTForms doesn't have full-time contributors yet but it would deserve 
them...
> My intention is not to put down XSLTforms at all, just to state my 
> concerns about priorities.
>   
Strategy is important and performance might block real-world use if it 
isn't considered enough.

I have to study all this for each recent browser now. Do you have a list 
of browsers to be supported by XSLTForms?

Thanks!

-Alain

[Xsltforms-support] Improving XSLTForms performance in IE

[Stephen C. <Ste...@ut...>]

Hello,

I recently had feed-back from some users and the main issue was slow 
form loading in IE.

I am wondering if there may be ways to get around this. I think that I 
am mainly having problems due to large XML files being included as 
external xform instances, that are then parsed into 'XDocument' 
javascript objects by XSLTForms.

I previously asked Alain if these could be natively parsed as 
DOMDocument objects by the browser and then used as such by XSLTForms. I 
think that the reason why this could not work is the lack of XPath 
support in browsers. However, I now wonder if a half-way house solution 
might work. That is XNodes are wrapper objects for DOMNodes and the 
XSLTForms Xpath evaluations are actually using the DOMNode name, values 
(or childNodes) behind the scenes.

So the XDocument.parse() method would, in the case of external 
instances, build a tree of XNodes each holding a reference to a DOMNode 
and for each evaluation of such an XNode, the node itself would have to 
decide if it was purely javascript based or DOMNode based. If this 
mechanism might possibly work, I'd be happy to have a go at trying it out.

I think XSLTforms has a niche only because all browsers do not support 
the Xforms standard natively. If you are an organisation using Xforms 
then there is no problem to use a plugin (though I've not tried one), so 
XSLTforms is filling the opportunity for a cross-browser solution but it 
hasn't quite got there yet in my view due to the current slowness in IE. 
Realistically, trying to add more feature support is not a good use of 
time whilst this problem exists.

Browsers are very fast at parsing XML and also transforming using XSLT, 
it seems to me that XSLTForms is making good use of the later but 
ignoring the potential of the former.

Not using IE is an option perhaps, but you have to ask what is XForms 
competing against and is the competion working OK in IE? For me at least 
the competition is AJAX frameworks that can auto-generate a web-app from 
a relational database schema and do client-side validation. There are 
plenty of options in this space and all work well in IE I'd say (we use 
ZK framework).

My intention is not to put down XSLTforms at all, just to state my 
concerns about priorities.

Cheers

Steve Cameron

Re: [Xsltforms-support] chaining XForms forms

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

Chris,

This feature is supported by the SVN version, not the beta 2 release

Thank you for your feedbacks!

-Alain
> 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?
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
>
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>