xsltforms-support Mailing List for XSLTForms (Page 95)
Brought to you by:
alain-couthures
You can subscribe to this list here.
2009 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(6) |
Jun
(9) |
Jul
(16) |
Aug
(5) |
Sep
(43) |
Oct
(36) |
Nov
(58) |
Dec
(43) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2010 |
Jan
(79) |
Feb
(81) |
Mar
(107) |
Apr
(93) |
May
(85) |
Jun
(54) |
Jul
(64) |
Aug
(54) |
Sep
(45) |
Oct
(53) |
Nov
(34) |
Dec
(77) |
2011 |
Jan
(56) |
Feb
(53) |
Mar
(52) |
Apr
(66) |
May
(44) |
Jun
(16) |
Jul
(28) |
Aug
(5) |
Sep
(15) |
Oct
(21) |
Nov
(51) |
Dec
(46) |
2012 |
Jan
(16) |
Feb
(38) |
Mar
(47) |
Apr
(45) |
May
(41) |
Jun
(41) |
Jul
(72) |
Aug
(17) |
Sep
(10) |
Oct
(16) |
Nov
(29) |
Dec
(30) |
2013 |
Jan
(25) |
Feb
(13) |
Mar
(20) |
Apr
(25) |
May
(34) |
Jun
(8) |
Jul
(12) |
Aug
(9) |
Sep
(21) |
Oct
(19) |
Nov
(6) |
Dec
(2) |
2014 |
Jan
(14) |
Feb
(8) |
Mar
(7) |
Apr
(13) |
May
(33) |
Jun
(13) |
Jul
(6) |
Aug
(5) |
Sep
(5) |
Oct
(34) |
Nov
(7) |
Dec
|
2015 |
Jan
(1) |
Feb
(6) |
Mar
(17) |
Apr
(12) |
May
(10) |
Jun
(18) |
Jul
(31) |
Aug
(9) |
Sep
(3) |
Oct
(6) |
Nov
(19) |
Dec
(1) |
2016 |
Jan
(18) |
Feb
(4) |
Mar
(13) |
Apr
(19) |
May
|
Jun
(17) |
Jul
(7) |
Aug
|
Sep
(3) |
Oct
(6) |
Nov
(3) |
Dec
|
2017 |
Jan
(5) |
Feb
(17) |
Mar
(4) |
Apr
(8) |
May
(3) |
Jun
|
Jul
(8) |
Aug
(2) |
Sep
|
Oct
(5) |
Nov
(6) |
Dec
(4) |
2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(6) |
Nov
|
Dec
(1) |
2019 |
Jan
|
Feb
|
Mar
(4) |
Apr
(2) |
May
(4) |
Jun
|
Jul
|
Aug
(2) |
Sep
(7) |
Oct
|
Nov
|
Dec
|
2020 |
Jan
(13) |
Feb
(17) |
Mar
(8) |
Apr
(11) |
May
(15) |
Jun
(11) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(6) |
2021 |
Jan
(9) |
Feb
(26) |
Mar
(17) |
Apr
|
May
(7) |
Jun
(18) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(10) |
2022 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
(2) |
Sep
(3) |
Oct
(2) |
Nov
(10) |
Dec
(1) |
2023 |
Jan
(10) |
Feb
|
Mar
(7) |
Apr
(8) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
(8) |
Oct
(11) |
Nov
(8) |
Dec
(5) |
2024 |
Jan
(7) |
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2025 |
Jan
(4) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Christian M. <chr...@mu...> - 2010-03-01 10:34:25
|
Hi all I do have a strange problem that might be a bug. I can now insert attributes and I can also insert elements into elements that contain already one sibling of the same name. If i try however to insert an element into an empty element I do get "Uncaught TypeError: Cannot read property 'nextSibling' of undefined xsltforms.js:2494<http://localhost:8080/exist/rest/www/xforms/xsltforms/xsltforms.js> " When I add an element to the instance and try again a second element is added just fine. my insert element looks as following: <xf:trigger> <xf:label>Add: spin</xf:label> <xf:action ev:event="DOMActivate"> <xf:insert context="/input/groundstate" origin="instance('elemprototype')/spin" nodeset="spin"/> </xf:action> </xf:trigger> I am using xsltforms svn 357 Yours grateful Christian |
From: Claudius T. <cla...@ya...> - 2010-02-26 14:19:17
|
Hi, A new version of eXSLTForms (beta 4) is now available http://sourceforge.net/projects/extxsltforms/files/ Changelog 1. This version provides a better rendering of data instances by the extension "Data Instances Viewer". 2. As XSLTForms has now a fix for insert with @position="after", our xslt action works now as intended, namely it replaces the target nodeset. 3. This version has a new action, called replace action. For details see readme.txt or http://kuberam.ro. Claudius Teodorescu http://kuberam.ro |
From: Christian M. <chr...@mu...> - 2010-02-26 10:40:32
|
I' am impressed! Thank you Alain! Merci beaucoup! Works like a charm!-- well attribute remove would have been the logical next step. :-) but I will be occupied a while with testing Attribute insert. On Fri, Feb 26, 2010 at 10:09 AM, COUTHURES Alain < ala...@ag...> wrote: > Christian, > > Attribute insert is now implemented (Test #b.4.a is now PASS) and you can > download the latest SVN version for that. > > Do you also require "attribute remove" and so on ? > > Best regards, > > -Alain > > Thanks, > meanwhile I know that in principle this ( > http://www.w3.org/TR/xforms11/#data-mutation-patterns-set-attribute) would > work but xsltforms kindly allerts me via message: > > "TODO clone Attribute" > > So It is known but not Implemented. > > Is there a possibility that there is a version of xsltforms that implements > this? I don't really know where to look for something like a version number > so I can't really say what version I'm using. > > ------------------------------ > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta.http://p.sf.net/sfu/intel-sw-dev > > ------------------------------ > > _______________________________________________ > Xsltforms-support mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/xsltforms-support > > > |
From: COUTHURES A. <ala...@ag...> - 2010-02-26 09:08:22
|
Christian, Attribute insert is now implemented (Test #b.4.a is now PASS) and you can download the latest SVN version for that. Do you also require "attribute remove" and so on ? Best regards, -Alain > Thanks, > meanwhile I know that in principle this > (http://www.w3.org/TR/xforms11/#data-mutation-patterns-set-attribute) > would work but xsltforms kindly allerts me via message: > > "TODO clone Attribute" > > So It is known but not Implemented. > > Is there a possibility that there is a version of xsltforms that > implements this? I don't really know where to look for something like > a version number so I can't really say what version I'm using. > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > ------------------------------------------------------------------------ > > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > |
From: Grégoire C. <gco...@gm...> - 2010-02-26 08:18:59
|
Hi Christian, I don't know what needs to be done to implement this, but maybe Alain Couthures could tell, so I'm forwarding this to the list. Grégoire Christian Meisenbichler a écrit : > Bhu, My project pretty much depends on this functionality. What must I > learn/read to fix that? > > 2010/2/25 Grégoire Colbert <gco...@gm... > <mailto:gco...@gm...>> > > Hi, > > For your information, I use latest SVN version (355) and I see the > string "TODO clone Attribute" when searching in "xsltforms.js". :-( > > Grégoire > |
From: Christian M. <chr...@mu...> - 2010-02-25 09:04:50
|
Thanks, meanwhile I know that in principle this ( http://www.w3.org/TR/xforms11/#data-mutation-patterns-set-attribute) would work but xsltforms kindly allerts me via message: "TODO clone Attribute" So It is known but not Implemented. Is there a possibility that there is a version of xsltforms that implements this? I don't really know where to look for something like a version number so I can't really say what version I'm using. |
From: Claudius T. <cla...@ya...> - 2010-02-24 21:31:48
|
Hi, I managed to remember: 1. add xmlns:mysc="http://www.agencexml.com/schema" mysc:dummy="dummy" to root of XForms page 2. example pf inline schema <xsd:simpleType name="tipStringNenul"> <xsd:restriction base="xsd:string"> <xsd:minLength value="1"/> </xsd:restriction> </xsd:simpleType> </xsd:schema> Note that, AFAIK, only simpleType is supported and the targetNamespace="http://www.agencexml.com/schema"(!!!). 3. Example of defining data type" <idPartener type="mysc:tipStringNenul"/> Good luck, Claudius Teodorescu http://kuberam.ro |
From: Klotz, L. <Lei...@xe...> - 2010-02-24 19:44:41
|
We documented how to do it in the XForms 1.1 as it's possible but not obvious. In the XForms 1.1 I don't know if XSLTForms implements the feature, but here's the magic: http://www.w3.org/TR/xforms11/#data-mutation-patterns-set-attribute Leigh. ________________________________ From: Christian Meisenbichler [mailto:ch...@gm...] Sent: Wednesday, February 24, 2010 8:06 AM To: xsl...@li... Subject: [Xsltforms-support] add attribute to instance element by selectingattribute name from list Dear XSLTforms Mailing List, Hi I am new to the xforms, but very fascinated. I have an exist db application that renders a form from a XML Schema. I have inputs and bindings for all possible inputs. meaning I can display the content of the instance completely in the form. I would like to have a way to insert new attributes from a list to the instance. I need a select widget that allows me to select a attribute to add, and allows for adding it to the instance. The input for that attribute should then appear in the list. Maybe you can throw some hints and starting points to me. Thank you very much |
From: Christian M. <ch...@gm...> - 2010-02-24 16:06:35
|
Dear XSLTforms Mailing List, Hi I am new to the xforms, but very fascinated. I have an exist db application that renders a form from a XML Schema. I have inputs and bindings for all possible inputs. meaning I can display the content of the instance completely in the form. I would like to have a way to insert new attributes from a list to the instance. I need a select widget that allows me to select a attribute to add, and allows for adding it to the instance. The input for that attribute should then appear in the list. Maybe you can throw some hints and starting points to me. Thank you very much |
From: Grégoire C. <gco...@gm...> - 2010-02-24 11:15:28
|
Hi Claudius, I had the same error with an external schema but I don't remember how I solved this. Could you post your XForm? Grégoire 2010/2/23 Claudius Teodorescu <cla...@ya...> > Hi, > > Could somebody point me to an working example for inline schema in > XSLTForms. > > I got the error: > Error initializing > > Needed schema name or exists one schema with that namespace > > Thank you, > > Claudius Teodorescu > http://kuberam.ro > > > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > > |
From: Grégoire C. <gco...@gm...> - 2010-02-23 11:25:10
|
In fact, it works with <xf:select> or <xf:select1> but not with inside values (like <itemset>). Le 23 février 2010 12:21, Grégoire Colbert <gco...@gm...> a écrit : > Hi, > > I noticed that with latest revision (355), when we click on the <xf:label> > text, the widget is not activated when the control is <xf:select> or > <xf:select1>. It still works with <xf:input>. > > Regards, > Grégoire > |
From: Grégoire C. <gco...@gm...> - 2010-02-23 11:21:15
|
Hi, I noticed that with latest revision (355), when we click on the <xf:label> text, the widget is not activated when the control is <xf:select> or <xf:select1>. It still works with <xf:input>. Regards, Grégoire |
From: Claudius T. <cla...@ya...> - 2010-02-23 08:41:28
|
Hi, Could somebody point me to an working example for inline schema in XSLTForms. I got the error: Error initializing Needed schema name or exists one schema with that namespace Thank you, Claudius Teodorescu http://kuberam.ro |
From: COUTHURES A. <ala...@ag...> - 2010-02-22 21:23:28
|
David, > I have determined that the inclusion of an xf:send element inside the > "Close" trigger causes the behavior to occur. When the xf:send > element is present in the "Close" trigger then the bug occurs, but if > I remove the xf:send element then the bug does not occur. > Sorry, I'm not able to reproduce this behavior by just adding an xf:send myself. Can you construct a minimal test case to allow debugging? Thanks! -Alain |
From: Grégoire C. <gco...@gm...> - 2010-02-22 15:40:15
|
Hi, I'm using a XML Schema for the validation of the instance, and I intended to define my allowed elements like in : <xsd:element name="codePostal"> <xsd:simpleType name="zipCodeDefinition"> <xsd:restriction></xsd:restriction> </xsd:simpleType> </xsd:element> However, XSLTForms ignores the xsd:element tags. It only sees (and uses correctly!) "xsd:simpleType" when they are siblings of the <xsd:schema> tag, not when they are inside <xsd:element>. Is it normal that we cannot use <xsd:element> with XForms, or is it a bug? Thanks, Grégoire |
From: Sandra B. <sb...@lo...> - 2010-02-22 15:21:20
|
Thank you. It'a sll working now. Sandy >>> COUTHURES Alain <ala...@ag...> 2/21/2010 4:39:37 PM >>> Sandy, There was a bug in XSLTForms SVN version when xf:case was used inside xf:toggle. This is now fixed and the test case you sent is working correctly for me. Thanks! -Alain > Sorry about not including that: > > <?xml version="1.0" encoding="UTF-8"?> > <mods> > <name type=""> > <namePart type="family"/> > <namePart type="given"/> > <namePart type="date"/> > <namePart type="termsOfAddress"/> > <namePart/> > <role> > <roleTerm authority="marcrelator"/> > </role> > </name> > </mods> > > Thanks, > Sandy > > |
From: COUTHURES A. <ala...@ag...> - 2010-02-21 21:38:57
|
Sandy, There was a bug in XSLTForms SVN version when xf:case was used inside xf:toggle. This is now fixed and the test case you sent is working correctly for me. Thanks! -Alain > Sorry about not including that: > > <?xml version="1.0" encoding="UTF-8"?> > <mods> > <name type=""> > <namePart type="family"/> > <namePart type="given"/> > <namePart type="date"/> > <namePart type="termsOfAddress"/> > <namePart/> > <role> > <roleTerm authority="marcrelator"/> > </role> > </name> > </mods> > > Thanks, > Sandy > > |
From: David A. <am...@gm...> - 2010-02-20 22:40:51
|
Alain, For this basic case, adding a tbody element does work. However, in a more advanced case, where I am using a server endpoint to provide the instance, I still see the bug. I have determined that the inclusion of an xf:send element inside the "Close" trigger causes the behavior to occur. When the xf:send element is present in the "Close" trigger then the bug occurs, but if I remove the xf:send element then the bug does not occur. The problem is that for my application I need an xf:send action to take place on the closing of the dialog. Can you suggest a work around for this? Thank you, David On Sat, Feb 20, 2010 at 2:01 PM, COUTHURES Alain <ala...@ag...> wrote: > David, > > It seems there is a simple workaround for this bug: insert a tbody element > to contain the xf:repeat element. > > It works for me with the latest SVN revision. > > Does it work for you with revision #314 ? > > Thanks! > > -Alain > > When using an xf:repeat within an HTML table, the dialog that opens > from an xsf:show is the correct dialog the first time that the button > for the associated trigger is clicked, but clicking any other button > subsequently opens the first dialog instead of correctly opening the > dialog for the button that was clicked. > > I have a table with the following structure: > > <table> > <xf:repeat nodeset="item"> > <tr> > <td> > <xf:trigger> > <xf:label>Modify</xf:label> > <xsf:show ev:event="DOMActivate" dialog="dialog"/> > </xf:trigger> > </td> > ... > </tr> > <div> > <xsf:dialog id="dialog"> > ... > </xsf:dialog> > </div> > </xf:repeat> > </table> > > If I replace all the table/tr/td elements with div/span elements, then > the behavior is correct. > > To reproduce the issue, open the attached file > "dialog-repeat-table.xhtml" in a browser. Click on the first "Modify" > button. The dialog associated with the first button will open. Now, > close this dialog, and click the second "Modify" button. The dialog > associated with the first button will open, but this is incorrect > because the dialog associated with the second button should open > instead. > > If you open the attached file "dialog-repeat-div.xhtml" and try the > same actions, then the behavior is correct and the correct dialog will > open each time. This file ("dialog-repeat-div.xhtml") uses div/span > elements instead of table/tr/td elements, which are used in > "dialog-repeat-table.xhtml". > > I am using revision #314 from the SVN repository. > > Thank you, > David > > > ________________________________ > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > > ________________________________ > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > > |
From: COUTHURES A. <ala...@ag...> - 2010-02-20 22:00:38
|
David, It seems there is a simple workaround for this bug: insert a tbody element to contain the xf:repeat element. It works for me with the latest SVN revision. Does it work for you with revision #314 ? Thanks! -Alain > When using an xf:repeat within an HTML table, the dialog that opens > from an xsf:show is the correct dialog the first time that the button > for the associated trigger is clicked, but clicking any other button > subsequently opens the first dialog instead of correctly opening the > dialog for the button that was clicked. > > I have a table with the following structure: > > <table> > <xf:repeat nodeset="item"> > <tr> > <td> > <xf:trigger> > <xf:label>Modify</xf:label> > <xsf:show ev:event="DOMActivate" dialog="dialog"/> > </xf:trigger> > </td> > ... > </tr> > <div> > <xsf:dialog id="dialog"> > ... > </xsf:dialog> > </div> > </xf:repeat> > </table> > > If I replace all the table/tr/td elements with div/span elements, then > the behavior is correct. > > To reproduce the issue, open the attached file > "dialog-repeat-table.xhtml" in a browser. Click on the first "Modify" > button. The dialog associated with the first button will open. Now, > close this dialog, and click the second "Modify" button. The dialog > associated with the first button will open, but this is incorrect > because the dialog associated with the second button should open > instead. > > If you open the attached file "dialog-repeat-div.xhtml" and try the > same actions, then the behavior is correct and the correct dialog will > open each time. This file ("dialog-repeat-div.xhtml") uses div/span > elements instead of table/tr/td elements, which are used in > "dialog-repeat-table.xhtml". > > I am using revision #314 from the SVN repository. > > Thank you, > David > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > ------------------------------------------------------------------------ > > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > |
From: David A. <am...@gm...> - 2010-02-20 20:21:52
|
When using an xf:repeat within an HTML table, the dialog that opens from an xsf:show is the correct dialog the first time that the button for the associated trigger is clicked, but clicking any other button subsequently opens the first dialog instead of correctly opening the dialog for the button that was clicked. I have a table with the following structure: <table> <xf:repeat nodeset="item"> <tr> <td> <xf:trigger> <xf:label>Modify</xf:label> <xsf:show ev:event="DOMActivate" dialog="dialog"/> </xf:trigger> </td> ... </tr> <div> <xsf:dialog id="dialog"> ... </xsf:dialog> </div> </xf:repeat> </table> If I replace all the table/tr/td elements with div/span elements, then the behavior is correct. To reproduce the issue, open the attached file "dialog-repeat-table.xhtml" in a browser. Click on the first "Modify" button. The dialog associated with the first button will open. Now, close this dialog, and click the second "Modify" button. The dialog associated with the first button will open, but this is incorrect because the dialog associated with the second button should open instead. If you open the attached file "dialog-repeat-div.xhtml" and try the same actions, then the behavior is correct and the correct dialog will open each time. This file ("dialog-repeat-div.xhtml") uses div/span elements instead of table/tr/td elements, which are used in "dialog-repeat-table.xhtml". I am using revision #314 from the SVN repository. Thank you, David |
From: Sandra B. <sb...@lo...> - 2010-02-19 15:08:04
|
Sorry about not including that: <?xml version="1.0" encoding="UTF-8"?> <mods> <name type=""> <namePart type="family"/> <namePart type="given"/> <namePart type="date"/> <namePart type="termsOfAddress"/> <namePart/> <role> <roleTerm authority="marcrelator"/> </role> </name> </mods> Thanks, Sandy >>> Grégoire Colbert <gco...@gm...> 2/19/2010 5:09 AM >>> Hi Sandra, I tried to test your code but couldn't recreate a working <xf:instance id="mods-data">. Could you post it too? Grégoire 2010/2/18 Sandra Bostian <sb...@lo...> > Hello all, > > I have a form that works fine until I add a switch in a select1. I want to > show a different entry section depending on what a user chooses in a > drop-down list. I thought it might be the blank initial value but when I > removed that I still got an error so I'm not sure what to do. Any advice > would be greatly appreciated. > > Thanks, > Sandy > > I'm using rev. 352 with Exist. I get the following error message: > > XSLTForms Exception > -------------------------- > Error initializing : > > (null, "xforms-select")@ > http://localhost:8080/exist/xforms/xsltforms/xsltforms.js:5989 > init()@http://localhost:8080/exist/xforms/mods_editor2.xhtml:425 > onload([object Event])@ > http://localhost:8080/exist/xforms/mods_editor2.html:1@:0 > > TypeError > target has no properties > > The offending section of code seems to be: > > <!--Creator Info--> > <h2>Creator Info</h2> > <xf:repeat nodeset="instance('mods-data')/name" id="mods-repeat"> > <group class="table"> > > <!--Type of name--> > <div class="table-row"> > <xf:label class="label-cell">Type of Name: </xf:label> > <div class="input-cell"> > <xf:select1 ref="@type" selection="closed"> > <xf:item> > <xf:label></xf:label> > <xf:value>1</xf:value> > </xf:item> > <xf:item> > <xf:label>personal</xf:label> > <xf:value>personal</xf:value> > </xf:item> > <xf:item> > <xf:label>corporate</xf:label> > <xf:value>corporate</xf:value> > </xf:item> > <xf:item> > <xf:label>conference</xf:label> > <xf:value>conference</xf:value> > </xf:item> > <xf:toggle ev:event="xforms-value-changed"> > <xf:case value="concat('case', )"/> > </xf:toggle> > </xf:select1> > </div> > </div> > <xf:switch> > <xf:case id="case1"> > </xf:case> > <xf:case id="casepersonal"> > <!--Role (creator, scribe, etc.)--> > <div class="table-row"> > <xf:label class="label-cell">Role: > </xf:label> > <div class="input-cell"> > <xf:select1 ref="role/roleTerm" > selection="closed"> > <xf:item> > <xf:label/> > <xf:value/> > </xf:item> > <xf:item> > > <xf:label>Architect</xf:label> > > <xf:value>Architect</xf:value> > </xf:item> > <xf:item> > <xf:label>Artist</xf:label> > <xf:value>Artist</xf:value> > </xf:item> > <xf:item> > <xf:label>Author</xf:label> > <xf:value>Author</xf:value> > </xf:item> > <xf:item> > > <xf:label>Calligrapher</xf:label> > > <xf:value>Calligrapher</xf:value> > </xf:item> > <xf:item> > > <xf:label>Cartographer</xf:label> > > <xf:value>Cartographer</xf:value> > </xf:item> > <xf:item> > > <xf:label>Contributor</xf:label> > > <xf:value>Contributor</xf:value> > </xf:item> > <xf:item> > <xf:label>Creator</xf:label> > <xf:value>Creator</xf:value> > </xf:item> > <xf:item> > <xf:label>Editor</xf:label> > <xf:value>Editor</xf:value> > </xf:item> > <xf:item> > > <xf:label>Illustrator</xf:label> > > <xf:value>Illustrator</xf:value> > </xf:item> > <xf:item> > > <xf:label>Musician</xf:label> > > <xf:value>Musician</xf:value> > </xf:item> > <xf:item> > > <xf:label>Narrator</xf:label> > > <xf:value>Narrator</xf:value> > </xf:item> > <xf:item> > > <xf:label>Photographer</xf:label> > > <xf:value>Photographer</xf:value> > </xf:item> > <xf:item> > <xf:label>Printer</xf:label> > > <xf:value>Publisher</xf:value> > </xf:item> > <xf:item> > <xf:label>Scribe</xf:label> > <xf:value>Scribe</xf:value> > </xf:item> > <xf:item> > > <xf:label>Transcriber</xf:label> > > <xf:value>Transcriber</xf:value> > </xf:item> > </xf:select1> > </div> > </div> > <!--Last name--> > <div class="table-row"> > <xf:label class="label-cell">Family > Name: </xf:label> > <div class="input-cell"> > <xf:input > ref="namePart[@type='family']" incremental="true"/> > </div> > </div> > <!--First name--> > <div class="table-row"> > <xf:label class="label-cell">Given Name: > </xf:label> > <div class="input-cell"> > <xf:inp ut > ref="namePart[@type='given']" incremental="true"/> > </div> > </div> > > <!--Title--> > <div class="table-row"> > <xf:label class="label-cell">Title (such > as Sir): </xf:label> > <div class="input-cell"> > <xf:input > ref="namePart[@type='termsOfAddress']" incremental="true"/> > </div> > </div> > > <!--Birth-Death Dates--> > <div class="table-row"> > <xf:label class="label-cell">Birth/Death > Dates: </xf:label> > <div class="input-cell"> > <xf:input > ref="namePart[@type='date']" incremental="true"/> > </div> > </div> > </xf:case> > <xf:case id="casecorporate"> > <!-- Corporate --> > <div class="table-row"> > <xf:label class="label-cell">Corporate > Name: </xf:label> > <div class="input-cell"> > <xf:input ref="namePart[@type='']" > incremental="true"/> > </div> > </div> > </xf:case> > <xf:case id="caseconference"> > <!-- Corporate --> > <div class="table-row"> > <xf:label class="label-cell">Conference > Name: </xf:label> > <div class="input-cell"> > <xf:input ref="namePart[@type='']" > incremental="true"/> > </div> > </div> > </xf:case> > </xf:switch> > </group> > <br/> > </xf:repeat> > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > |
From: Grégoire C. <gco...@gm...> - 2010-02-19 10:20:38
|
Ok, Got your form working with : <xf:model id="modele-sandy"> <xf:instance id="mods-data"> <data> <name type=""> <namePart type="family"/> <namePart type="given"/> <namePart type="termsofAddress"/> <namePart type="date"/> <namePart type=""/> <role> <roleTerm/> </role> </name> </data> </xf:instance> </xf:model> I don't know whether I'm using revision 352, but it works here : http://img692.imageshack.us/img692/1106/xformloc.png Grégoire Le 19 février 2010 11:09, Grégoire Colbert <gco...@gm...> a écrit : > Hi Sandra, > > I tried to test your code but couldn't recreate a working <xf:instance > id="mods-data">. Could you post it too? > > Grégoire > > 2010/2/18 Sandra Bostian <sb...@lo...> > > Hello all, >> >> I have a form that works fine until I add a switch in a select1. I want to >> show a different entry section depending on what a user chooses in a >> drop-down list. I thought it might be the blank initial value but when I >> removed that I still got an error so I'm not sure what to do. Any advice >> would be greatly appreciated. >> >> Thanks, >> Sandy >> >> I'm using rev. 352 with Exist. I get the following error message: >> >> XSLTForms Exception >> -------------------------- >> Error initializing : >> >> (null, "xforms-select")@ >> http://localhost:8080/exist/xforms/xsltforms/xsltforms.js:5989 >> init()@http://localhost:8080/exist/xforms/mods_editor2.xhtml:425 >> onload([object Event])@ >> http://localhost:8080/exist/xforms/mods_editor2.html:1@:0 >> >> TypeError >> target has no properties >> >> The offending section of code seems to be: >> >> <!--Creator Info--> >> <h2>Creator Info</h2> >> <xf:repeat nodeset="instance('mods-data')/name" id="mods-repeat"> >> <group class="table"> >> >> <!--Type of name--> >> <div class="table-row"> >> <xf:label class="label-cell">Type of Name: </xf:label> >> <div class="input-cell"> >> <xf:select1 ref="@type" selection="closed"> >> <xf:item> >> <xf:label></xf:label> >> <xf:value>1</xf:value> >> </xf:item> >> <xf:item> >> <xf:label>personal</xf:label> >> <xf:value>personal</xf:value> >> </xf:item> >> <xf:item> >> <xf:label>corporate</xf:label> >> <xf:value>corporate</xf:value> >> </xf:item> >> <xf:item> >> <xf:label>conference</xf:label> >> <xf:value>conference</xf:value> >> </xf:item> >> <xf:toggle ev:event="xforms-value-changed"> >> <xf:case value="concat('case', .)"/> >> </xf:toggle> >> </xf:select1> >> </div> >> </div> >> <xf:switch> >> <xf:case id="case1"> >> </xf:case> >> <xf:case id="casepersonal"> >> <!--Role (creator, scribe, etc.)--> >> <div class="table-row"> >> <xf:label class="label-cell">Role: >> </xf:label> >> <div class="input-cell"> >> <xf:select1 ref="role/roleTerm" >> selection="closed"> >> <xf:item> >> <xf:label/> >> <xf:value/> >> </xf:item> >> <xf:item> >> >> <xf:label>Architect</xf:label> >> >> <xf:value>Architect</xf:value> >> </xf:item> >> <xf:item> >> <xf:label>Artist</xf:label> >> <xf:value>Artist</xf:value> >> </xf:item> >> <xf:item> >> <xf:label>Author</xf:label> >> <xf:value>Author</xf:value> >> </xf:item> >> <xf:item> >> >> <xf:label>Calligrapher</xf:label> >> >> <xf:value>Calligrapher</xf:value> >> </xf:item> >> <xf:item> >> >> <xf:label>Cartographer</xf:label> >> >> <xf:value>Cartographer</xf:value> >> </xf:item> >> <xf:item> >> >> <xf:label>Contributor</xf:label> >> >> <xf:value>Contributor</xf:value> >> </xf:item> >> <xf:item> >> >> <xf:label>Creator</xf:label> >> >> <xf:value>Creator</xf:value> >> </xf:item> >> <xf:item> >> <xf:label>Editor</xf:label> >> <xf:value>Editor</xf:value> >> </xf:item> >> <xf:item> >> >> <xf:label>Illustrator</xf:label> >> >> <xf:value>Illustrator</xf:value> >> </xf:item> >> <xf:item> >> >> <xf:label>Musician</xf:label> >> >> <xf:value>Musician</xf:value> >> </xf:item> >> <xf:item> >> >> <xf:label>Narrator</xf:label> >> >> <xf:value>Narrator</xf:value> >> </xf:item> >> <xf:item> >> >> <xf:label>Photographer</xf:label> >> >> <xf:value>Photographer</xf:value> >> </xf:item> >> <xf:item> >> >> <xf:label>Printer</xf:label> >> >> <xf:value>Publisher</xf:value> >> </xf:item> >> <xf:item> >> <xf:label>Scribe</xf:label> >> <xf:value>Scribe</xf:value> >> </xf:item> >> <xf:item> >> >> <xf:label>Transcriber</xf:label> >> >> <xf:value>Transcriber</xf:value> >> </xf:item> >> </xf:select1> >> </div> >> </div> >> <!--Last name--> >> <div class="table-row"> >> <xf:label class="label-cell">Family >> Name: </xf:label> >> <div class="input-cell"> >> <xf:input >> ref="namePart[@type='family']" incremental="true"/> >> </div> >> </div> >> <!--First name--> >> <div class="table-row"> >> <xf:label class="label-cell">Given >> Name: </xf:label> >> <div class="input-cell"> >> <xf:input >> ref="namePart[@type='given']" incremental="true"/> >> </div> >> </div> >> >> <!--Title--> >> <div class="table-row"> >> <xf:label class="label-cell">Title >> (such as Sir): </xf:label> >> <div class="input-cell"> >> <xf:input >> ref="namePart[@type='termsOfAddress']" incremental="true"/> >> </div> >> </div> >> >> <!--Birth-Death Dates--> >> <div class="table-row"> >> <xf:label >> class="label-cell">Birth/Death Dates: </xf:label> >> <div class="input-cell"> >> <xf:input >> ref="namePart[@type='date']" incremental="true"/> >> </div> >> </div> >> </xf:case> >> <xf:case id="casecorporate"> >> <!-- Corporate --> >> <div class="table-row"> >> <xf:label class="label-cell">Corporate >> Name: </xf:label> >> <div class="input-cell"> >> <xf:input ref="namePart[@type='']" >> incremental="true"/> >> </div> >> </div> >> </xf:case> >> <xf:case id="caseconference"> >> <!-- Corporate --> >> <div class="table-row"> >> <xf:label class="label-cell">Conference >> Name: </xf:label> >> <div class="input-cell"> >> <xf:input ref="namePart[@type='']" >> incremental="true"/> >> </div> >> </div> >> </xf:case> >> </xf:switch> >> </group> >> <br/> >> </xf:repeat> >> >> >> ------------------------------------------------------------------------------ >> Download Intel® Parallel Studio Eval >> Try the new software tools for yourself. Speed compiling, find bugs >> proactively, and fine-tune applications for parallel performance. >> See why Intel Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev >> _______________________________________________ >> Xsltforms-support mailing list >> Xsl...@li... >> https://lists.sourceforge.net/lists/listinfo/xsltforms-support >> > > |
From: Grégoire C. <gco...@gm...> - 2010-02-19 10:09:36
|
Hi Sandra, I tried to test your code but couldn't recreate a working <xf:instance id="mods-data">. Could you post it too? Grégoire 2010/2/18 Sandra Bostian <sb...@lo...> > Hello all, > > I have a form that works fine until I add a switch in a select1. I want to > show a different entry section depending on what a user chooses in a > drop-down list. I thought it might be the blank initial value but when I > removed that I still got an error so I'm not sure what to do. Any advice > would be greatly appreciated. > > Thanks, > Sandy > > I'm using rev. 352 with Exist. I get the following error message: > > XSLTForms Exception > -------------------------- > Error initializing : > > (null, "xforms-select")@ > http://localhost:8080/exist/xforms/xsltforms/xsltforms.js:5989 > init()@http://localhost:8080/exist/xforms/mods_editor2.xhtml:425 > onload([object Event])@ > http://localhost:8080/exist/xforms/mods_editor2.html:1@:0 > > TypeError > target has no properties > > The offending section of code seems to be: > > <!--Creator Info--> > <h2>Creator Info</h2> > <xf:repeat nodeset="instance('mods-data')/name" id="mods-repeat"> > <group class="table"> > > <!--Type of name--> > <div class="table-row"> > <xf:label class="label-cell">Type of Name: </xf:label> > <div class="input-cell"> > <xf:select1 ref="@type" selection="closed"> > <xf:item> > <xf:label></xf:label> > <xf:value>1</xf:value> > </xf:item> > <xf:item> > <xf:label>personal</xf:label> > <xf:value>personal</xf:value> > </xf:item> > <xf:item> > <xf:label>corporate</xf:label> > <xf:value>corporate</xf:value> > </xf:item> > <xf:item> > <xf:label>conference</xf:label> > <xf:value>conference</xf:value> > </xf:item> > <xf:toggle ev:event="xforms-value-changed"> > <xf:case value="concat('case', .)"/> > </xf:toggle> > </xf:select1> > </div> > </div> > <xf:switch> > <xf:case id="case1"> > </xf:case> > <xf:case id="casepersonal"> > <!--Role (creator, scribe, etc.)--> > <div class="table-row"> > <xf:label class="label-cell">Role: > </xf:label> > <div class="input-cell"> > <xf:select1 ref="role/roleTerm" > selection="closed"> > <xf:item> > <xf:label/> > <xf:value/> > </xf:item> > <xf:item> > > <xf:label>Architect</xf:label> > > <xf:value>Architect</xf:value> > </xf:item> > <xf:item> > <xf:label>Artist</xf:label> > <xf:value>Artist</xf:value> > </xf:item> > <xf:item> > <xf:label>Author</xf:label> > <xf:value>Author</xf:value> > </xf:item> > <xf:item> > > <xf:label>Calligrapher</xf:label> > > <xf:value>Calligrapher</xf:value> > </xf:item> > <xf:item> > > <xf:label>Cartographer</xf:label> > > <xf:value>Cartographer</xf:value> > </xf:item> > <xf:item> > > <xf:label>Contributor</xf:label> > > <xf:value>Contributor</xf:value> > </xf:item> > <xf:item> > <xf:label>Creator</xf:label> > <xf:value>Creator</xf:value> > </xf:item> > <xf:item> > <xf:label>Editor</xf:label> > <xf:value>Editor</xf:value> > </xf:item> > <xf:item> > > <xf:label>Illustrator</xf:label> > > <xf:value>Illustrator</xf:value> > </xf:item> > <xf:item> > > <xf:label>Musician</xf:label> > > <xf:value>Musician</xf:value> > </xf:item> > <xf:item> > > <xf:label>Narrator</xf:label> > > <xf:value>Narrator</xf:value> > </xf:item> > <xf:item> > > <xf:label>Photographer</xf:label> > > <xf:value>Photographer</xf:value> > </xf:item> > <xf:item> > <xf:label>Printer</xf:label> > > <xf:value>Publisher</xf:value> > </xf:item> > <xf:item> > <xf:label>Scribe</xf:label> > <xf:value>Scribe</xf:value> > </xf:item> > <xf:item> > > <xf:label>Transcriber</xf:label> > > <xf:value>Transcriber</xf:value> > </xf:item> > </xf:select1> > </div> > </div> > <!--Last name--> > <div class="table-row"> > <xf:label class="label-cell">Family > Name: </xf:label> > <div class="input-cell"> > <xf:input > ref="namePart[@type='family']" incremental="true"/> > </div> > </div> > <!--First name--> > <div class="table-row"> > <xf:label class="label-cell">Given Name: > </xf:label> > <div class="input-cell"> > <xf:input > ref="namePart[@type='given']" incremental="true"/> > </div> > </div> > > <!--Title--> > <div class="table-row"> > <xf:label class="label-cell">Title (such > as Sir): </xf:label> > <div class="input-cell"> > <xf:input > ref="namePart[@type='termsOfAddress']" incremental="true"/> > </div> > </div> > > <!--Birth-Death Dates--> > <div class="table-row"> > <xf:label class="label-cell">Birth/Death > Dates: </xf:label> > <div class="input-cell"> > <xf:input > ref="namePart[@type='date']" incremental="true"/> > </div> > </div> > </xf:case> > <xf:case id="casecorporate"> > <!-- Corporate --> > <div class="table-row"> > <xf:label class="label-cell">Corporate > Name: </xf:label> > <div class="input-cell"> > <xf:input ref="namePart[@type='']" > incremental="true"/> > </div> > </div> > </xf:case> > <xf:case id="caseconference"> > <!-- Corporate --> > <div class="table-row"> > <xf:label class="label-cell">Conference > Name: </xf:label> > <div class="input-cell"> > <xf:input ref="namePart[@type='']" > incremental="true"/> > </div> > </div> > </xf:case> > </xf:switch> > </group> > <br/> > </xf:repeat> > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > |
From: Sandra B. <sb...@lo...> - 2010-02-18 20:01:05
|
Hello all, I have a form that works fine until I add a switch in a select1. I want to show a different entry section depending on what a user chooses in a drop-down list. I thought it might be the blank initial value but when I removed that I still got an error so I'm not sure what to do. Any advice would be greatly appreciated. Thanks, Sandy I'm using rev. 352 with Exist. I get the following error message: XSLTForms Exception -------------------------- Error initializing : (null, "xforms-select")@http://localhost:8080/exist/xforms/xsltforms/xsltforms.js:5989 init()@http://localhost:8080/exist/xforms/mods_editor2.xhtml:425 onload([object Event])@http://localhost:8080/exist/xforms/mods_editor2.html:1@:0 TypeError target has no properties The offending section of code seems to be: <!--Creator Info--> <h2>Creator Info</h2> <xf:repeat nodeset="instance('mods-data')/name" id="mods-repeat"> <group class="table"> <!--Type of name--> <div class="table-row"> <xf:label class="label-cell">Type of Name: </xf:label> <div class="input-cell"> <xf:select1 ref="@type" selection="closed"> <xf:item> <xf:label></xf:label> <xf:value>1</xf:value> </xf:item> <xf:item> <xf:label>personal</xf:label> <xf:value>personal</xf:value> </xf:item> <xf:item> <xf:label>corporate</xf:label> <xf:value>corporate</xf:value> </xf:item> <xf:item> <xf:label>conference</xf:label> <xf:value>conference</xf:value> </xf:item> <xf:toggle ev:event="xforms-value-changed"> <xf:case value="concat('case', .)"/> </xf:toggle> </xf:select1> </div> </div> <xf:switch> <xf:case id="case1"> </xf:case> <xf:case id="casepersonal"> <!--Role (creator, scribe, etc.)--> <div class="table-row"> <xf:label class="label-cell">Role: </xf:label> <div class="input-cell"> <xf:select1 ref="role/roleTerm" selection="closed"> <xf:item> <xf:label/> <xf:value/> </xf:item> <xf:item> <xf:label>Architect</xf:label> <xf:value>Architect</xf:value> </xf:item> <xf:item> <xf:label>Artist</xf:label> <xf:value>Artist</xf:value> </xf:item> <xf:item> <xf:label>Author</xf:label> <xf:value>Author</xf:value> </xf:item> <xf:item> <xf:label>Calligrapher</xf:label> <xf:value>Calligrapher</xf:value> </xf:item> <xf:item> <xf:label>Cartographer</xf:label> <xf:value>Cartographer</xf:value> </xf:item> <xf:item> <xf:label>Contributor</xf:label> <xf:value>Contributor</xf:value> </xf:item> <xf:item> <xf:label>Creator</xf:label> <xf:value>Creator</xf:value> </xf:item> <xf:item> <xf:label>Editor</xf:label> <xf:value>Editor</xf:value> </xf:item> <xf:item> <xf:label>Illustrator</xf:label> <xf:value>Illustrator</xf:value> </xf:item> <xf:item> <xf:label>Musician</xf:label> <xf:value>Musician</xf:value> </xf:item> <xf:item> <xf:label>Narrator</xf:label> <xf:value>Narrator</xf:value> </xf:item> <xf:item> <xf:label>Photographer</xf:label> <xf:value>Photographer</xf:value> </xf:item> <xf:item> <xf:label>Printer</xf:label> <xf:value>Publisher</xf:value> </xf:item> <xf:item> <xf:label>Scribe</xf:label> <xf:value>Scribe</xf:value> </xf:item> <xf:item> <xf:label>Transcriber</xf:label> <xf:value>Transcriber</xf:value> </xf:item> </xf:select1> </div> </div> <!--Last name--> <div class="table-row"> <xf:label class="label-cell">Family Name: </xf:label> <div class="input-cell"> <xf:input ref="namePart[@type='family']" incremental="true"/> </div> </div> <!--First name--> <div class="table-row"> <xf:label class="label-cell">Given Name: </xf:label> <div class="input-cell"> <xf:input ref="namePart[@type='given']" incremental="true"/> </div> </div> <!--Title--> <div class="table-row"> <xf:label class="label-cell">Title (such as Sir): </xf:label> <div class="input-cell"> <xf:input ref="namePart[@type='termsOfAddress']" incremental="true"/> </div> </div> <!--Birth-Death Dates--> <div class="table-row"> <xf:label class="label-cell">Birth/Death Dates: </xf:label> <div class="input-cell"> <xf:input ref="namePart[@type='date']" incremental="true"/> </div> </div> </xf:case> <xf:case id="casecorporate"> <!-- Corporate --> <div class="table-row"> <xf:label class="label-cell">Corporate Name: </xf:label> <div class="input-cell"> <xf:input ref="namePart[@type='']" incremental="true"/> </div> </div> </xf:case> <xf:case id="caseconference"> <!-- Corporate --> <div class="table-row"> <xf:label class="label-cell">Conference Name: </xf:label> <div class="input-cell"> <xf:input ref="namePart[@type='']" incremental="true"/> </div> </div> </xf:case> </xf:switch> </group> <br/> </xf:repeat> |
From: Grégoire C. <gco...@gm...> - 2010-02-18 14:07:06
|
Hi, For information, removing the "model" attribute from the <xf:itemset> element solved this problem. Grégoire Le 15 février 2010 18:25, Grégoire Colbert <gco...@gm...> a écrit : > 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 > > |