xsltforms-support — XSLTForms support list

Re: [Xsltforms-support] problem with date picker and i18n

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

Hi Thorsten,

Thank you very much for pointing at this problem and for providing this 
localization file.

The next version of XSLTForms will not be using messages.properties 
files anymore but config.xsl files so I have modified the previous 
config_de.xsl instead.
This can already be tested with the SVN version.

Best regards,

-Alain
> Hi
>
> Sorry, I've done too much date programming with is very bad for you
> mental health. In the German localization I used the ISO date separator
> instead of the customary German separator. This is corrected in the
> attached file.
>
>     Regards
>    Thorsten
>   

Re: [Xsltforms-support] problem with date picker and i18n

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

Hi

Sorry, I've done too much date programming with is very bad for you
mental health. In the German localization I used the ISO date separator
instead of the customary German separator. This is corrected in the
attached file.

    Regards
   Thorsten

[Xsltforms-support] problem with date picker and i18n

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

Hi

The date picker does not work if the correct language support file for
the browser language is not available. I attached the German i18n file.
If the list eats it or something miscodes the Umlaut in March (März) let
me know and I'll remail to wherever is appropriate.

    Regards
   Thorsten

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

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

Hi Christophe,
> is there a way to properly render a structure like this one?
>
> <xf:trigger class="tree-icon" appearance="minimal" ref="current()/@l">
>             <img  class="tree-icon elbow-line" 
> src="/db/e-Smile/system/resource/images/s.gif"/>
> </xf:trigger>
>
> With the current release, the img stuff is not rendered at all. This 
> structure (trigger+img) can be pretty usefull in complex scenario - 
> for instance I use it to render a classic dynamic tree structure (with 
> '+' and '-' triggers to expand/collapse the tree.
>
> A workaround seems to write it this way:
> <xf:trigger class="tree-icon" appearance="minimal" ref="current()/@l">
>        <xf:label>
>             <img  class="tree-icon elbow-line" 
> src="/db/e-Smile/system/resource/images/s.gif"/>
>        </xf:label>
> </xf:trigger>
I prefer the mediatype approach. Can you test this ?

<xf:trigger class="tree-icon" appearance="minimal" ref="current()/@l">
       <xf:label>
            <xf:output  class="tree-icon elbow-line" 
value="'/db/e-Smile/system/resource/images/s.gif'" mediatype="image/*"/>
       </xf:label>
</xf:trigger>
>
> But this option is only a partial one (= img is rendered) as the 
> xf:label adds '*' (required) and 'x'(alert) symbols on the form.
I can't see that with a simple test case. Don't you have a binding on 
this attribute ?

-Alain

[Xsltforms-support] img within xf:trigger

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

Hi all
is there a way to properly render a structure like this one?

<xf:trigger class="tree-icon" appearance="minimal" ref="current()/@l">
            <img  class="tree-icon elbow-line"
src="/db/e-Smile/system/resource/images/s.gif"/>
</xf:trigger>

With the current release, the img stuff is not rendered at all. This
structure (trigger+img) can be pretty usefull in complex scenario - for
instance I use it to render a classic dynamic tree structure (with '+' and
'-' triggers to expand/collapse the tree.

A workaround seems to write it this way:
<xf:trigger class="tree-icon" appearance="minimal" ref="current()/@l">
       <xf:label>
            <img  class="tree-icon elbow-line"
src="/db/e-Smile/system/resource/images/s.gif"/>
       </xf:label>
</xf:trigger>

But this option is only a partial one (= img is rendered) as the xf:label
adds '*' (required) and 'x'(alert) symbols on the form.

Thanks
Christophs

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

Re: [Xsltforms-support] the default replace instance seems to be thefirst one on submission

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

You're right, I think: http://www.w3.org/TR/xforms11/#submit-submission-element
"When the [instance] attribute is absent, then the default is the instance that contains the submission data."
Leigh.

________________________________

From: christophe geiser [mailto:chr...@e-...] 
Sent: Friday, February 05, 2010 2:23 AM
To: xsl...@li...
Subject: [Xsltforms-support] the default replace instance seems to be thefirst one on submission


Hi all
See the attached doc or below for the test case. It seems that a submission written without the 'instance' attribute like:
<xforms:submission id="submit" ref="instance('toInsert')" action="toInsert.xml" replace="instance" method="post"/> 
would replace the first instance in the model and not the instance declared by the 'ref' attribute as default - I am not sure this is the spec behavior.

Cheers and have a nice day
Christophe

 ... 

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

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

Hi all
just to report on this:

an expression like <xf:repeat nodeset="instance('data')//*[@id]"/> seems to
have some difficulties to be properly evaluated.

<?xml-stylesheet href="xsltForms/db/xsltforms/trunk/build/xsltforms.xsl"
type="text/xsl"?>
<?xsltforms-options debug="yes"?>
<html xmlns="http://www.w3.org/1999/xhtml"
      xmlns:xs="http://www.w3.org/2001/XMLSchema"
      xmlns:xf="http://www.w3.org/2002/xforms"
      xmlns:ev="http://www.w3.org/2001/xml-events">
   <head>
      <title>test repeat with //</title>
      <xf:model id="mod">
         <xf:instance id="data" xmlns="">
            <data>
               <task id="1">
                <name>1</name>
                <task id="2">
                    <name>2</name>
              </task>
              </task>
              <task id="3">
                <name>3</name>
              </task>
              <task id="4">
                <name>4</name>
                <task id="5">
                    <name>5</name>
              </task>
              </task>
            </data>
         </xf:instance>

      </xf:model>

   </head>
   <body>
      <h1>test repeat </h1>
        <div>
            <p>working: nodeset="instance('data')//@id"</p>
            <xf:repeat nodeset="instance('data')//@id" id="rep">
                <xf:output ref="../name"/>
            </xf:repeat>
        </div>
        <div>
            <p>not working: nodeset="instance('data')//*[@id]</p>
            <xf:repeat nodeset="instance('data')//*[@id]" id="rep2">
                <xf:output ref="name"/>
            </xf:repeat>
        </div>
       </body>
</html>

I will continue testing the features of xsltform against my application.
Till now, I must say that I am really happy with this solution - it is
pretty fast and intuitive.

Cheers
C.

Re: [Xsltforms-support] test on axes support

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

You are right - I naively tought the link 'download XSLTForms at
sourceforge.net' would point to the latest SVN version.
Axes works fine with the trunk - thanks a lot
C.

On Wed, Feb 3, 2010 at 9:06 PM, COUTHURES Alain <
ala...@ag...> wrote:

> Hi Christophe,
>
>  I must be missing something re axes support (I read somewhere that axes
>> support had been integrated - I might be wrong though). The following form
>> casts an xPath expression Error (Unknown operator at ':rep/tt' in
>> 'current()/ancestor::rep/tt). Or is there another way to declare axes?
>>
> I have just tested it successfully with the latest SVN version. Are you
> sure you tried with it ?
>
> Thanks!
>
> -Alain
>
>


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

Re: [Xsltforms-support] test on axes support

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

Hi Christophe,
> I must be missing something re axes support (I read somewhere that 
> axes support had been integrated - I might be wrong though). The 
> following form casts an xPath expression Error (Unknown operator at 
> ':rep/tt' in 'current()/ancestor::rep/tt). Or is there another way to 
> declare axes?
I have just tested it successfully with the latest SVN version. Are you 
sure you tried with it ?

Thanks!

-Alain

Re: [Xsltforms-support] xsltforms Performance

[Christopher D. <cd...@vi...>]

Alain,

I have a follow-up and possibly a partial solution to this issue.  However, I would like your feedback.

My largest issue is the number of seconds it takes a user to "tab" from one field to the next in my form.  As you probably saw, my form has several unique characteristics:
. very large instance data
. several hundred inputs
. nested repeats (3 levels deep)

After doing some profiling in IE, I noticed that the xmlValue and ExprContext functions are the biggest offenders in both number of calls and execution time.  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.

It seems to me that XFControl.prototype.valueChanged does all the leg work so that xforms.closeAction will recalculate and revalidate the instance.  By removing the line:

XMLEvents.dispatch(model, "xforms-recalculate");

from XFControl.prototype.valueChanged, I was able to almost halve the time it takes a user to "tab" from one field to the next.  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?

Regards,

Chris



From: COUTHURES Alain [mailto:ala...@ag...] 
Sent: Saturday, January 23, 2010 11:16 AM
To: Christopher Dedels
Cc: xsl...@li...
Subject: Re: [Xsltforms-support] xsltforms Performance

Christopher, 
I have been using xsltforms to create some complicated interfaces.  xsltforms performance appears to degrade significantly as the size of the instance data increases.  It does not seem to be impacted as significantly by the number of input controls on the page.  This means that paging the items in my repeat element has almost no performance impact.
Can you send me a link or the XForms document itself with its data ?

 
Profiling tools report at least 13 seconds in IE 8 (2.5 seconds in FF/Chrome)
Yes, IE is still very slower...

to "tab" from one field to the next, regardless of whether the data in the field was changed.
It's a good situation to check with a javascript debugger (focus is lost,...).

  As you can expect, this is not acceptable for my users.
There are different possibilities of optimization in XSLTForms: less generated HTML elements, less Javascript instructions executed,...

Because this has not been done yet, I hope that a minimal effort could improve it significantly.

 
What are the scalability limits of xsltforms?
This is not yet determined but there are many parameters involved: complexity, instance size, number of bindings, ...

  Do you have any suggestions on how to improve performance in my xforms document?
Use of // in XPath expressions is surely to avoid.

-Alain

Re: [Xsltforms-support] XForm control support

[Dimuthu N. <dim...@ya...>]

Hi Alain,
Thank you very much for the information.Would you please explain bit more about the server trick that can be used for file upload.
Thank you,
Dimuthu.

--- On Wed, 3/2/10, COUTHURES Alain <ala...@ag...> wrote:

From: COUTHURES Alain <ala...@ag...>
Subject: Re: [Xsltforms-support] XForm control support
To: "Dimuthu Nawarathna" <dim...@ya...>
Cc: xsl...@li...
Date: Wednesday, 3 February, 2010, 2:15 AM




  

 
Hi Dimuthu,

  
    
      
        
        1.  Tab control - Is there a way to organize content in
such a way that user would see as they are content Tabs?
        
      
    
  

xf:switch and xf:toggle can be use to loook like tabs.


  
    
      
        
        2. Selectable list control - It should be a list where one
can select an item. (Like HTML <select> tag)
        
      
    
  

xf:select and xf:select1 are supported


  
    
      
        
        3. xforms:upload
- Upload control to browse and add an image data into XML (I saw the
test fails for upload control. But is there any workaround? )
        
      
    
  

xf:upload is not yet supported (a server trick is required to fully
implement it in XSLTForms)


  
    
      
        
        4. xforms:group - Can't we use this group element for a
list. (But I don't see it render as a list )
        
      
    
  

xf:group is to change context and treat bubbling events. xf:repeat is
there to render a set.


  
    
      
        
        5. Can we integrate XSLTForm with a XML schema to validate
XML ? If so. can you please show me an example.
        
      
    
  

XML Schema support in XSLTForms is still incomplete...



-Alain

 




      Your Mail works best with the New Yahoo Optimized IE8. Get it NOW! http://downloads.yahoo.com/in/internetexplorer/

[Xsltforms-support] test on axes support

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

Hi all

I must be missing something re axes support (I read somewhere that axes
support had been integrated - I might be wrong though). The following form
casts an xPath expression Error (Unknown operator at ':rep/tt' in
'current()/ancestor::rep/tt). Or is there another way to declare axes?

<?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" >
   <head>
      <title>test axis</title>
      <xf:model id="my_model">
         <xf:instance id="my_instance">
            <data xmlns="">
               <rep>
        <tt>tt</tt>
        <level1>
            <level2>test1</level2>
        </level1>
        <level1>
            <level2>test2</level2>
        </level1>
        </rep>
            </data>
         </xf:instance>
      </xf:model>
   </head>
   <body>
       <p>axis</p>
    <xf:repeat nodeset="instance('my_instance')/rep/level1">
        level2: <xf:output ref="level2"/>
        test axis: <xf:output ref="current()/ancestor::rep/tt"/>
    </xf:repeat>
   </body>
</html>

Thanks in advance
Christophe

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

[Xsltforms-support] minor issue with firebug command line

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

Hi all
This is clearly not a priority (and it is very likely to be a firebug...
bug), but it can get quite annoying while debugging:
I cannot have the firebug command line to work on a xlstforms page.

No javascript is executed with the command line and at some point (after a
few refresh), I get a firebug error message stating: "Firebug cannot find
_firebugConsole element true".

Has somebody encoutered this and been able to fix it ?

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

Re: [Xsltforms-support] xforms context function

[Christopher D. <cd...@vi...>]

Alain,

Here is the test case for the xforms context function.  The sample allows a user to edit the title and author of a book.  The data is copied to a separate instance for editing and then, if the user decides to save the changes, the original values in the first instance should be replaced with the modified values from the second instance.

Let me know if I can help further.

Chris


<?xml version="1.0" ?>
<?xml-stylesheet href="xsltforms.xsl" type="text/xsl"?>
<html xmlns="http://www.w3.org/1999/xhtml"
			xmlns:xf="http://www.w3.org/2002/xforms"
			xmlns:ev="http://www.w3.org/2001/xml-events"
			xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <head>
    <xf:model>
      <!-- DATA FROM EXTERNAL SOURCES -->
      <xf:instance id="library">
        <library>
          <books>
            <book>
              <title>The Astonishing Life of Octavian Nothing, Traitor to the Nation, Volume II: The Kingdom on the Waves</title>
              <author>M. T. Anderson</author>
            </book>
            <book>
              <title>The Way We Work</title>
              <author>David Macaulay with Richard Walker, illustrated by David Macaulay</author>
            </book>
            <book>
              <title>Old Bear</title>
              <author>Kevin Henkes</author>
            </book>
          </books>
        </library>
      </xf:instance>
      <xf:instance id="editbook">
        <book>
          <title></title>
          <author></author>
        </book>
      </xf:instance>
    </xf:model>
    <title>context() Test</title>
    <style>
      td {
      border: 1px solid #000000;
      }
    </style>
  </head>
  <body>
    <xf:group ref="instance('editbook')">
      <xf:switch>
        <xf:case id="noedit" selected="true"/>
        <xf:case id="edit">
          <div style="width: 100%; height: 100%; position: absolute; background-color: #fff;">
            <table>
              <tr>
                <td>
                  Title
                </td>
                <td>
                  <xf:input ref="title"/>
                </td>
              </tr>
              <tr>
                <td>
                  Author
                </td>
                <td>
                  <xf:input ref="author"/>
                </td>
              </tr>
              <tr>
                <td colspan="2">
                  <xf:trigger>
                    <xf:label>
                      Cancel
                    </xf:label>
                    <xf:action ev:event="DOMActivate">
                      <xf:setvalue ref="title" value="''"/>
                      <xf:setvalue ref="author" value="''"/>
                      <xf:toggle case="noedit" />
                    </xf:action>
                  </xf:trigger>
                  <xf:trigger>
                    <xf:label>
                      Save
                    </xf:label>
                    <xf:action ev:event="DOMActivate">
                      <xf:setvalue ref="instance('library')/books/book[index('books')]/title" value="context()/title"/>
                      <xf:setvalue ref="instance('library')/books/book[index('books')]/author" value="context()/author"/>
                      <xf:toggle case="noedit" />
                    </xf:action>
                  </xf:trigger>
                </td>
              </tr>
            </table>
          </div>
        </xf:case>
      </xf:switch>
    </xf:group>
    <xf:group ref="instance('library')">
      <table>
        <thead>
          <tr>
            <td></td>
            <td>
              <b>Title</b>
            </td>
            <td>
              <b>Author</b>
            </td>
          </tr>
        </thead>
        <tbody>
          <xf:repeat id="books" nodeset="books/book">
            <td>
              <xf:trigger>
                <xf:label>
                  Edit
                </xf:label>
                <xf:action ev:event="DOMActivate">
                  <xf:setvalue ref="instance('editbook')/title" value="context()/title"/>
                  <xf:setvalue ref="instance('editbook')/author" value="context()/author"/>
                  <xf:toggle case="edit" />
                </xf:action>
              </xf:trigger>
            </td>
            <td>
              <xf:output ref="title"/>
            </td>
            <td>
              <xf:output ref="author"/>
            </td>
          </xf:repeat>
        </tbody>
      </table>
    </xf:group>
  </body>
</html>






-----Original Message-----
From: COUTHURES Alain [mailto:ala...@ag...] 
Sent: Tuesday, February 02, 2010 3:21 PM
To: Christopher Dedels
Cc: xsl...@li...
Subject: Re: [Xsltforms-support] xforms context function

Christopher,
> It appears that the context function does not work correctly.  Here is sample code to reproduce the issue:
>
> <xf:repeat id="books" nodeset="instance('library')/books/book">
> 	<xf:trigger appearance="minimal">
> 		<xf:label>
> 			<xf:output ref="title"/>
> 		</xf:label>
> 		<xf:setvalue ref="instance('customer')/book/title" value="context()/title" ev:event="DOMActivate"/>
> 	</xf:trigger>
> </xf:repeat>
>
> It appears that the context function is returning a reference to the instance('customer')/book/title node, not the instance('library')/books[index('books')]/book node as expected.
>   
Can you please provide a full test case ? It would surely accelerate 
debugging.

Thanks!

-Alain

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

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

Although not immediately implementable, one proposal the WG is considering is having the dialog use its own instance and "submit" back to another, local model (i.e., <submission resource="#foo">).

Some work by Charlie Wiecha and Rafah Hosn at IBM had been done on this in the past, under the name "XAC", with a "Russian Doll" composition of model-to-model communcation.

As far as I know, though, no concrete proposal for syntax to do this has yet been proposed on the receiving end of the submission (I.e., what element has id="foo" and what happens.)  A proposal for how to move forward on that would be great, and would probably be the same execution overhead as an "undo" instance, yet provide additional abstract power and recursive composition facilities, and enhance modularity.

Leigh.



-----Original Message-----
From: Micah Dubinko [mailto:Mic...@ma...] 
Sent: Tuesday, February 02, 2010 1:18 PM
To: xsl...@li...
Subject: [Xsltforms-support] Dialog OK vs. cancel

Now that we have dialogs (thanks Alain!) we are looking in to ways to make them work with two possible close cases, OK and Cancel (equivalently, the X button in the upper-right).

What do people think of this technique?

1) Create a separate instance called "undo". Upon opening the dialog, copy over the main instance data into "undo". If the user dismisses the dialog with OK, proceed as usual. If the user hits cancel or X, copy the stored instance back over the first one, thus rolling back whatever changes had been made in the dialog. If you have nested dialogs, you'd need to be more careful.

Is there a better/more straightforward way to accomplish this?

-m
------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
Xsltforms-support mailing list
Xsl...@li...
https://lists.sourceforge.net/lists/listinfo/xsltforms-support

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

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

Hey Micah,
> Now that we have dialogs (thanks Alain!) we are looking in to ways to make them work with two possible close cases, OK and Cancel (equivalently, the X button in the upper-right).
>
> What do people think of this technique?
>
> 1) Create a separate instance called "undo". Upon opening the dialog, copy over the main instance data into "undo". If the user dismisses the dialog with OK, proceed as usual. If the user hits cancel or X, copy the stored instance back over the first one, thus rolling back whatever changes had been made in the dialog. If you have nested dialogs, you'd need to be more careful.
>
> Is there a better/more straightforward way to accomplish this?
>   
The close attribute described at 
http://www.w3.org/MarkUp/Forms/wiki/Dialog?highlight=(CategoryXForms12) 
can be used to know that an internal back up is to be done of instances 
data.

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?

Thanks!

-Alain

[Xsltforms-support] Dialog OK vs. cancel

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

Now that we have dialogs (thanks Alain!) we are looking in to ways to make them work with two possible close cases, OK and Cancel (equivalently, the X button in the upper-right).

What do people think of this technique?

1) Create a separate instance called "undo". Upon opening the dialog, copy over the main instance data into "undo". If the user dismisses the dialog with OK, proceed as usual. If the user hits cancel or X, copy the stored instance back over the first one, thus rolling back whatever changes had been made in the dialog. If you have nested dialogs, you'd need to be more careful.

Is there a better/more straightforward way to accomplish this?

-m

Re: [Xsltforms-support] XForm control support

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

Hi Dimuthu,
> 1.  Tab control - Is there a way to organize content in such a way 
> that user would see as they are content Tabs?
>
xf:switch and xf:toggle can be use to loook like tabs.
> 2. Selectable list control - It should be a list where one can select 
> an item. (Like HTML <select> tag)
>
xf:select and xf:select1 are supported
> 3. xforms:upload - Upload control to browse and add an image data into 
> XML (I saw the test fails for upload control. But is there any 
> workaround? )
>
xf:upload is not yet supported (a server trick is required to fully 
implement it in XSLTForms)
> 4. xforms:group - Can't we use this group element for a list. (But I 
> don't see it render as a list )
>
xf:group is to change context and treat bubbling events. xf:repeat is 
there to render a set.
> 5. Can we integrate XSLTForm with a XML schema to validate XML ? If 
> so. can you please show me an example.
>
XML Schema support in XSLTForms is still incomplete...

-Alain

Re: [Xsltforms-support] <xf:trigger><xf:label ref="myLabelDoesNotSeemToWork"/></xf:trigger>

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

Because of this simple workaround, label/@ref support is now at very low 
priority in my plans...

-Alain
> label/@ref <mailto:label/@ref> is not implemented presently in XSLTForms.
>  
> I took a look at implementing it, but it's not trivial, because the 
> xsltforms.xsl doesn't have a match rule for xf:label; instead, it's 
> scattered about in the various controls and control states.
>  
> Alain would have to respond about his plans, but in the absence of an 
> implementation, use <xf:label><xf:output ref="..." /></xf:label> instead.
>
> ------------------------------------------------------------------------
> *From:* christophe geiser [mailto:chr...@e-...]
> *Sent:* Monday, February 01, 2010 8:16 AM
> *To:* Xsl...@li...
> *Subject:* [Xsltforms-support] <xf:trigger><xf:label 
> ref="myLabelDoesNotSeemToWork"/></xf:trigger>
>
> Hi all
>
> I am doing some tests before trying to migrate my XRX app to 
> XSLTForms, and triggers' label with ref attribute does not seem to 
> produce the expected result.
>
> I am missing something there, or is this feature not yet implemented :
>
> <html xmlns="http://www.w3.org/1999/xhtml"
>     xmlns:ev="http://www.w3.org/2001/xml-events"
>     xmlns:xf="http://www.w3.org/2002/xforms">
>     <head>
>         <title>XSLTForms test various</title>
>     <xf:model>
>             <xf:instance xmlns="" id="test">
>                 <cart>
>                     <items>
>                         <item>windshield wipers</item>
>                       </items>
>                 </cart>
>             </xf:instance>
>         </xf:model>
>     </head>
>     <body>
>         <xf:trigger ><xf:label 
> ref="instance('test')/items/item[1]"></xf:label></xf:trigger>
>     </body>
> </html>
>
> Cheers
> Christophe
> -- 
> Christophe Geiser, social entrepreneur
> e-Smile, solutions in monitoring and information management
> --

Re: [Xsltforms-support] xforms context function

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

Christopher,
> It appears that the context function does not work correctly.  Here is sample code to reproduce the issue:
>
> <xf:repeat id="books" nodeset="instance('library')/books/book">
> 	<xf:trigger appearance="minimal">
> 		<xf:label>
> 			<xf:output ref="title"/>
> 		</xf:label>
> 		<xf:setvalue ref="instance('customer')/book/title" value="context()/title" ev:event="DOMActivate"/>
> 	</xf:trigger>
> </xf:repeat>
>
> It appears that the context function is returning a reference to the instance('customer')/book/title node, not the instance('library')/books[index('books')]/book node as expected.
>   
Can you please provide a full test case ? It would surely accelerate 
debugging.

Thanks!

-Alain

[Xsltforms-support] XForm control support

[Dimuthu N. <dim...@ya...>]

Hi all,
I am bit new to XFrom development and I am assigned with a task to migrate a XForm document which is already processed via a activeX based approach to XSLT forms. I need to know whether the following types of controls are supported in XSLTForms
1.  Tab control - Is there a way to organize content in such a way that user would see as they are content Tabs?
2. Selectable list control - It should be a list where one can select an item. (Like HTML <select> tag)
3. xforms:upload - Upload control to browse and add an image data into XML (I saw the test fails for upload control. But is there any workaround? )
4. xforms:group - Can't we use this group element for a list. (But I don't see it render as a list )
5. Can we integrate XSLTForm with a XML schema to validate XML ? If so. can you please show me an example.

I went through the samples in http://www.agencexml.com/xsltforms.htm but could not find answers to above questions.
Please advice.
Thank you,
Dimuthu.


      Your Mail works best with the New Yahoo Optimized IE8. Get it NOW! http://downloads.yahoo.com/in/internetexplorer/

Re: [Xsltforms-support] <xf:trigger><xf:label ref="myLabelDoesNotSeemToWork"/></xf:trigger>

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

Thanks a lot Leigh

The first part of your message sounded a bit like a pretty bad news, but it
works quite well with the proposed workaround ; - )

Cheers
Christophe

On Mon, Feb 1, 2010 at 7:06 PM, Klotz, Leigh <Lei...@xe...> wrote:

>  label/@ref is not implemented presently in XSLTForms.
>
> I took a look at implementing it, but it's not trivial, because the
> xsltforms.xsl doesn't have a match rule for xf:label; instead, it's
> scattered about in the various controls and control states.
>
> Alain would have to respond about his plans, but in the absence of an
> implementation, use <xf:label><xf:output ref="..." /></xf:label> instead.
>
>  ------------------------------
> *From:* christophe geiser [mailto:chr...@e-...]
> *Sent:* Monday, February 01, 2010 8:16 AM
> *To:* Xsl...@li...
> *Subject:* [Xsltforms-support] <xf:trigger><xf:label
> ref="myLabelDoesNotSeemToWork"/></xf:trigger>
>
> Hi all
>
> I am doing some tests before trying to migrate my XRX app to XSLTForms, and
> triggers' label with ref attribute does not seem to produce the expected
> result.
>
> I am missing something there, or is this feature not yet implemented :
>
> <html xmlns="http://www.w3.org/1999/xhtml"
>     xmlns:ev="http://www.w3.org/2001/xml-events"
>     xmlns:xf="http://www.w3.org/2002/xforms">
>     <head>
>         <title>XSLTForms test various</title>
>     <xf:model>
>             <xf:instance xmlns="" id="test">
>                 <cart>
>                     <items>
>                         <item>windshield wipers</item>
>                       </items>
>                 </cart>
>             </xf:instance>
>         </xf:model>
>     </head>
>     <body>
>         <xf:trigger ><xf:label
> ref="instance('test')/items/item[1]"></xf:label></xf:trigger>
>     </body>
> </html>
>
> Cheers
> Christophe
> --
> Christophe Geiser, social entrepreneur
> e-Smile, solutions in monitoring and information management
> --
>
>


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

[Xsltforms-support] xforms context function

[Christopher D. <cd...@vi...>]

It appears that the context function does not work correctly.  Here is sample code to reproduce the issue:

<xf:repeat id="books" nodeset="instance('library')/books/book">
	<xf:trigger appearance="minimal">
		<xf:label>
			<xf:output ref="title"/>
		</xf:label>
		<xf:setvalue ref="instance('customer')/book/title" value="context()/title" ev:event="DOMActivate"/>
	</xf:trigger>
</xf:repeat>

It appears that the context function is returning a reference to the instance('customer')/book/title node, not the instance('library')/books[index('books')]/book node as expected.

Have I misunderstood the purpose of this function?
http://www.w3.org/TR/xforms11/#fn-context

Chris

Re: [Xsltforms-support] <xf:trigger><xf:label ref="myLabelDoesNotSeemToWork"/></xf:trigger>

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

label/@ref is not implemented presently in XSLTForms.
 
I took a look at implementing it, but it's not trivial, because the xsltforms.xsl doesn't have a match rule for xf:label; instead, it's scattered about in the various controls and control states.
 
Alain would have to respond about his plans, but in the absence of an implementation, use <xf:label><xf:output ref="..." /></xf:label> instead.

________________________________

From: christophe geiser [mailto:chr...@e-...] 
Sent: Monday, February 01, 2010 8:16 AM
To: Xsl...@li...
Subject: [Xsltforms-support] <xf:trigger><xf:label ref="myLabelDoesNotSeemToWork"/></xf:trigger>


Hi all

I am doing some tests before trying to migrate my XRX app to XSLTForms, and triggers' label with ref attribute does not seem to produce the expected result.

I am missing something there, or is this feature not yet implemented :

<html xmlns="http://www.w3.org/1999/xhtml" 
    xmlns:ev="http://www.w3.org/2001/xml-events"
    xmlns:xf="http://www.w3.org/2002/xforms">
    <head>
        <title>XSLTForms test various</title>
    <xf:model>
            <xf:instance xmlns="" id="test">
                <cart>
                    <items>
                        <item>windshield wipers</item>
                      </items>
                </cart>
            </xf:instance>
        </xf:model>
    </head>
    <body>
        <xf:trigger ><xf:label ref="instance('test')/items/item[1]"></xf:label></xf:trigger>
    </body>
</html>

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

[Xsltforms-support] <xf:trigger><xf:label ref ="myLabelDoesNotSeemToWork"/></xf:trigger>

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

Hi all

I am doing some tests before trying to migrate my XRX app to XSLTForms, and
triggers' label with ref attribute does not seem to produce the expected
result.

I am missing something there, or is this feature not yet implemented :

<html xmlns="http://www.w3.org/1999/xhtml"
    xmlns:ev="http://www.w3.org/2001/xml-events"
    xmlns:xf="http://www.w3.org/2002/xforms">
    <head>
        <title>XSLTForms test various</title>
    <xf:model>
            <xf:instance xmlns="" id="test">
                <cart>
                    <items>
                        <item>windshield wipers</item>
                      </items>
                </cart>
            </xf:instance>
        </xf:model>
    </head>
    <body>
        <xf:trigger ><xf:label
ref="instance('test')/items/item[1]"></xf:label></xf:trigger>
    </body>
</html>

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