xsltforms-support Mailing List for XSLTForms (Page 56)
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: William D. V. <wi...@bi...> - 2011-10-27 21:50:19
|
>> Actually my server is reporting an error "Invalid URL encoded >> character >> (% D) at position 222" when my form do POST or a PUT and the >> instance >> contains the % character. > Could you please send me the submission element you're using? here is the submission element: <xforms:submission id="xsub" action="/siclho/pd/pdserver.dll/doc/store" method="post" replace="instance" instance="ins"> pdserver.dll is supposed to store the content of the request as an XML document in a XML field of a table in an oracle database. > > When changing from one form to another, with XSLTForms, it would be > better to use a method I named "xml-urlencoded-post" because it is > using an HTML form submit instead of an AJAX mechanism. The > corresponding instance is encoded within a field named "postdata". Using xml-urlencoded-post is not applicable (for now) because I requires changes in the ISAPI server built on Delphi, and it serves to other modules of the application, not based on XForms (they use Altova Authentic). I´ll take a look to the HTTP traffic and will post my observations. |
From: COUTHURES A. <ala...@fr...> - 2011-10-27 20:18:54
|
Hello William, > Actually my server is reporting an error "Invalid URL encoded character > (% D) at position 222" when my form do POST or a PUT and the instance > contains the % character. Could you please send me the submission element you're using? When changing from one form to another, with XSLTForms, it would be better to use a method I named "xml-urlencoded-post" because it is using an HTML form submit instead of an AJAX mechanism. The corresponding instance is encoded within a field named "postdata". > My server is build with Delphi Websnap technology, and I personally > don´t have many confidence on it. I don't know it myself and I understand your reservations. > > My question is: Should I start looking for the problem in the server? > or maybe there is some XSLTForms setting should I check? Depending on your browser, you might be able to log the HTTP request to check it manually. Thank you for your feedbacks! -Alain |
From: William D. V. <wi...@bi...> - 2011-10-27 19:08:11
|
Hello, I have a form where the user insert the % symbol in the text of a multiline input. (He writes somethign like "the customer offers 50% payment". Actually my server is reporting an error "Invalid URL encoded character (% D) at position 222" when my form do POST or a PUT and the instance contains the % character. My server is build with Delphi Websnap technology, and I personally don´t have many confidence on it. My question is: Should I start looking for the problem in the server? or maybe there is some XSLTForms setting should I check? Thanks for your advice, -- William David Velasquez Laboratorio de Software Bitlab http://bitlab.com.co Movil 310 412 0218 |
From: Alain C. <ala...@ag...> - 2011-10-27 06:40:06
|
Hello Steve, The tree Control is not effectively supported in XSLTForms because it is not defined in the XForms 1.1 Specifications but it was implemented in AJAXForms (http://ajaxforms.sourceforge.net/samples/addons.html). It shouldn't be too difficult to allow it in XSLTForms but I would first look at other XForms implementations to be sure to propose something suitable for future XForms specifications. Thanks! -Alain Le 27/10/2011 08:26, Stephen Cameron a écrit : > Hello XSLTForms Folk, > > Can someone point me to an example of the xf:tree control in XSLTForms? > > Thanks > > Steve Cameron > > > ------------------------------------------------------------------------------ > The demand for IT networking professionals continues to grow, and the > demand for specialized networking skills is growing even more rapidly. > Take a complimentary Learning@Cisco Self-Assessment and learn > about Cisco certifications, training, and career opportunities. > http://p.sf.net/sfu/cisco-dev2dev > > > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support |
From: Stephen C. <ste...@gm...> - 2011-10-27 06:26:50
|
Hello XSLTForms Folk, Can someone point me to an example of the xf:tree control in XSLTForms? Thanks Steve Cameron |
From: Alain C. <ala...@ag...> - 2011-10-27 06:22:25
|
Hello, Rev. 511 is fixing an issue relative to MIPs evaluations for bindings on more than one node. There are also new features: * IE9 support * @iterate on a nodeset for actions * a processing instruction to associate an XForms document to an XML document (no supported by Google Chrome because of document() function lack) * the XSLTForms Profiler being an XForms document opened in a new window The XSLTForms Profiler will be extended to become a reactive document visualizing the instances, for example. Do you have suggestions? Thank you for your feedbacks! -Alain |
From: Kurt C. <kur...@gm...> - 2011-10-24 21:18:38
|
I tried text/xsl first on the processing instruction, but could try that on the server as well. I'll let you know how that turns out. Kurt Cagle Invited Expert, XForms Working Group, W3C Managing Editor, XMLToday.org kur...@gm... 443-837-8725 On Mon, Oct 24, 2011 at 5:12 PM, ala...@ag... < ala...@ag...> wrote: > ** > > Kurt, > > > > Did you try "text/xsl"? It seems that IE is not supporting any other > type... > > > > -Alain > > > > > > Le 24 octobre 2011 à 22:56, Kurt Cagle <kur...@gm...> a écrit : > > > To anyone with MarkLogic experience who's played with IE8 and XSLTForms. > I > > have XSLTForms served up from an ML4.2 database, using the > <xml-stylesheet> > > directive 'type="text/xsl" href="/lib/xsltforms/xsltforms.xsl"/>. It > works > > with Chrome and Firefox, but it's just presenting as HTML markup in IE8 > > (XForms ignored). I've tried serving the xsl as both application/xslt+xml > > > and as application/xml, but it seems to make no difference. Any > suggestions? > > > > Kurt Cagle > |
From: <ala...@ag...> - 2011-10-24 21:17:53
|
Kurt, Did you try "text/xsl"? It seems that IE is not supporting any other type... -Alain Le 24 octobre 2011 à 22:56, Kurt Cagle <kur...@gm...> a écrit : > To anyone with MarkLogic experience who's played with IE8 and XSLTForms. I > have XSLTForms served up from an ML4.2 database, using the <xml-stylesheet> > directive 'type="text/xsl" href="/lib/xsltforms/xsltforms.xsl"/>. It works > with Chrome and Firefox, but it's just presenting as HTML markup in IE8 > (XForms ignored). I've tried serving the xsl as both application/xslt+xml > and as application/xml, but it seems to make no difference. Any suggestions? > > Kurt Cagle |
From: Kurt C. <kur...@gm...> - 2011-10-24 20:56:49
|
To anyone with MarkLogic experience who's played with IE8 and XSLTForms. I have XSLTForms served up from an ML4.2 database, using the <xml-stylesheet> directive 'type="text/xsl" href="/lib/xsltforms/xsltforms.xsl"/>. It works with Chrome and Firefox, but it's just presenting as HTML markup in IE8 (XForms ignored). I've tried serving the xsl as both application/xslt+xml and as application/xml, but it seems to make no difference. Any suggestions? Kurt Cagle |
From: Leigh L K. Jr <lei...@xe...> - 2011-10-12 23:49:31
|
I can't get a test I have with switch to work in XSLTForms-510 and IE8. It works ok in Firefox and Chrome current versions. It may take me some time to reduce the page to a test case, so if anybody else has XSLTForms-510 and IE8 test please be on the lookout for issues. |
From: Alain C. <ala...@ag...> - 2011-10-11 21:19:50
|
Hello Morgan, > 1. My general question is: can you point me to any examples that make > use of the XSLTForms transform function? > > The only one I have been able to find is the one provided by Alain at: > > http://www.agencexml.com/svgopen/graphs.xml Sorry, I have no other example yet. I'm writing a form which enables to load an XSLT stylesheet from a local file into an instance, then to apply it to another instance and, finally, to save the result locally. The W3C Forms Working Group has not yet agreed on how the transform function should be in XForms 2.0. > > 2. My specific question is: is it possible to use the output from the > transform function to insert an element node into an existing instance? > > My attempt to do this is below but it does not work as hoped. > Currently, the transform() function in XSLTForms is just generating a text string. But a parse() function could be added or the transform() function could evolve to generate a sub-tree which could then be inserted in an instance. It implies that XML documents have to be associated with XPath expressions: it's not difficult to prototype this but this is more complex when refresh is to be done and when such expressions are used in repeats, especially when adding or deleting items. Thanks! -Alain |
From: <mcu...@co...> - 2011-10-11 15:27:54
|
Hello All, 1. My general question is: can you point me to any examples that make use of the XSLTForms transform function? The only one I have been able to find is the one provided by Alain at: http://www.agencexml.com/svgopen/graphs.xml 2. My specific question is: is it possible to use the output from the transform function to insert an element node into an existing instance? My attempt to do this is below but it does not work as hoped. Note: the referenced stylesheet (ex2.xsl) just returns this: <p>para content</p> Thank you. Morgan ------------------------------- xquery version "1.0-ml"; declare namespace xdmp="http://marklogic.com/xdmp"; let $page := (xdmp:set-response-content-type("application/xml"), <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"> <head> <xf:model> <xf:instance xmlns="http://www.w3.org/1999/xhtml" id="i1"> <table> <row> <column></column> </row> </table> </xf:instance> <xf:insert ev:event="xforms-ready" context="instance('i1')/row/column" nodeset="p" origin="transform(instance('i2'), 'ex2.xsl')"/> </xf:model> <xf:model> <xf:instance xmlns="" id="i2"> <p>para content</p> </xf:instance> </xf:model> </head> <body> <h3>Datafield</h3> <xf:group nodeset="/table"> <xf:repeat id="repeat-row" nodeset="row"> <xf:input ref="column"/> </xf:repeat> <xf:trigger> <xf:label>Add Row</xf:label> <xf:action ev:event="DOMActivate" if="index('repeat-row') != (count(row))"> <xf:insert nodeset="row" at="index('repeat-row')" position="after" /> <xf:setvalue ref="row[index('repeat-row')]/column" value="/table/row/column/p" /> </xf:action> <xf:action ev:event="DOMActivate" if="index('repeat-row') = (count(row))"> <xf:insert nodeset="row[last()]" position="after" at="last()"/> <xf:setvalue ref="row[last()]/column" value="/table/row/column/p"/> </xf:action> </xf:trigger> </xf:group> </body> </html> ) let $xslt-pi := processing-instruction xml-stylesheet {'type="text/xsl" href="xsltforms/xsltforms.xsl"'} return ($xslt-pi, $page) ------------------------------- |
From: Alain C. <ala...@ag...> - 2011-10-10 20:15:31
|
Hello Thorsten, > I found an old thread in the list about this where you say you only use > native html controls. Any news on this? I understand if you prefer to > not support this, I wrote a few such controls myself, they are pretty > hard to get right. The calendar control is, indeed, not a native html control. Similarly, for open select, multiple HTML elements have to be used and, you're right, it's not very easy. As for range, it's not a priority yet but will be considered when necessary. > BTW, in search of this feature I evaluated betterforms which does > support open selection. XSLTforms seems to be far superior, cleaner, > faster, more user friendly (responsiveness), easier on server and > network, much easier to debug (cause it does not do all these server > requests on its own). I was quite surprised how much better I like > XSLTforms. Thank you very much for your enthusiasm! -Alain |
From: Thorsten R. <ju...@sc...> - 2011-10-08 19:38:39
|
Hi I found an old thread in the list about this where you say you only use native html controls. Any news on this? I understand if you prefer to not support this, I wrote a few such controls myself, they are pretty hard to get right. BTW, in search of this feature I evaluated betterforms which does support open selection. XSLTforms seems to be far superior, cleaner, faster, more user friendly (responsiveness), easier on server and network, much easier to debug (cause it does not do all these server requests on its own). I was quite surprised how much better I like XSLTforms. Regards Thorsten |
From: Alain C. <ala...@ag...> - 2011-10-07 20:45:46
|
Hello, It has been a long time since rev. 508 and the new revision (rev. 509) is full of improvements and there are also new features: * the id() function is now supported: its use is strongly recommended for big instances (measured at 10 times faster than with a predicate for an operational form) * the MIPs are re-evaluated according to dependencies only * the dependencies storage had been improved for big instances * the number of generated HTML elements have been minimized (no span/span/span/... anymore) and the Profiler is displaying the number of HTML elements in the resulting page * setvalue/@context is now supported * triggers can be displayed as read-only * union type support in schemas is improved * low-level XPath evaluation has been optimized * XHTML namespace is not anymore accepted instead of the empty namespace * an RDF description has been added into the XSLT stylesheet * some fixes concerning text(), inline XSLT transformation in IE and setindex action Thank you for your feedbacks! -Alain |
From: Santosh C. <san...@gm...> - 2011-10-07 07:07:36
|
I had to include SVG into XForms application recently and thought to share my findings. Without fiddling much with setting the application type in javascript, we can simply give xhtml extension to the result of transformation and use this xhtml result which supports SVG. XSLTForms fully work in xhtml mode (I use older version), you only need to make sure that your application works in xhtml. Typically things like not using innerHTML etc., more details here - http://www.w3.org/TR/xhtml-media-types/#application-xhtml-xml SVG has limited support in HTML as well if we avoid namespaces (for IE version 9 works), so one could try HTML first and see if it works for all the requirements. Regards, Santosh |
From: Jens Ø. P. <oe...@gm...> - 2011-10-06 07:19:00
|
Hi Alain, True, I just "rode" on Leigh's posting because the subject was (more or less) in the same general area …. The way I got around the problem with filtering in Firefox until now has been by masking the namespace: *:template. This works fine, but your suggestion (which I did not notice before) to use a dummy attribute in the form itself is better: just having something like 'e:dummy="dummy"' on any element indeed does the trick. If there is no hope for namespace support in Firefox, having this in a config file is best, I would think. In December last year, you made it possible to insert attributes. This meant a lot to our forms. In between then and now, I am sure it has been possible to insert namespaced attributes, but I don't know exactly when the change happened. I will try to track this down - unless there is a workaround for this as well! Thanks a lot! Jens On Oct 5, 2011, at 10:46 PM, Alain Couthures wrote: > Hello, > > The issue pointed by Leigh was just about the empty namespace and the XHTML namespace: by default, AJAXForms considered that authors would forget to declare the empty namespace in instances so the XHTML namespace was also accepted! > > FireFox still has the lack of namespace axis support: the current workaround is to add a dummy attribute anywhere in the form within the desired namespace so the XSLT stylesheet can find it. > > I'm now thinking of allowing namespace declarations in config files to avoid extra dummy attributes in each form. What do you think? > > Thanks! > > -Alain > > Le 04/10/2011 10:26, Jens Østergaard Petersen a écrit : >> Hi, >> >> I also have problems with namespaces in 508. >> >> Filtering with namespaces, as on line 266 of >> >> <http://exist.svn.sourceforge.net/viewvc/exist/apps/tamboti/modules/edit/body/00-compact-standalone.xml?view=markup&pathrev=15394> >> >> works in Chrome 14 and Safari 5.1, but not in FF 3.6 and 7. >> >> Inserting namespaced attributes, as on lines 227 and 236 of >> >> <http://exist.svn.sourceforge.net/viewvc/exist/apps/tamboti/modules/edit/body/01-title.xml?revision=15140&view=markup&pathrev=15394> >> >> does not work in any browser, though I am sure it has worked before. >> >> Am I doing something wrong? >> >> Best, >> >> Jens >> >> On Aug 10, 2011, at 1:11 AM, Leigh L Klotz Jr wrote: >> >>> Given this instance data: >>> >>> <?xml version="1.0" encoding="UTF-8"?> >>> <data> >>> <doc> >>> <div xmlns="http://www.w3.org/1999/xhtml"> >>> <p>Hi there</p> >>> </div> >>> </doc> >>> </data> >>> >>> xsltforms-508 in all browsers tested (FF5, Chrome13, IE8) will match >>> <group ref="doc/div" /> >>> even though the div is in another namespace. >>> >>> Also, FF5 fails to match this: >>> <group ref="doc/h:div" /> >>> >>> See attached files. >>> >>> Leigh. >>> <foo.xml><test.xml>------------------------------------------------------------------------------ >>> uberSVN's rich system and user administration capabilities and model >>> configuration take the hassle out of deploying and managing Subversion and >>> the tools developers use with it. Learn more about uberSVN and get a free >>> download at: http://p.sf.net/sfu/wandisco-dev2dev >>> _______________________________________________ >>> Xsltforms-support mailing list >>> Xsl...@li... >>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support >> >> ------------------------------------------------------------------------------ >> All the data continuously generated in your IT infrastructure contains a >> definitive record of customers, application performance, security >> threats, fraudulent activity and more. Splunk takes this data and makes >> sense of it. Business sense. IT sense. Common sense. >> http://p.sf.net/sfu/splunk-d2dcopy1 >> _______________________________________________ >> Xsltforms-support mailing list >> Xsl...@li... >> https://lists.sourceforge.net/lists/listinfo/xsltforms-support >> > |
From: Alain C. <ala...@ag...> - 2011-10-05 20:52:02
|
Hello, The issue pointed by Leigh was just about the empty namespace and the XHTML namespace: by default, AJAXForms considered that authors would forget to declare the empty namespace in instances so the XHTML namespace was also accepted! FireFox still has the lack of namespace axis support: the current workaround is to add a dummy attribute anywhere in the form within the desired namespace so the XSLT stylesheet can find it. I'm now thinking of allowing namespace declarations in config files to avoid extra dummy attributes in each form. What do you think? Thanks! -Alain Le 04/10/2011 10:26, Jens Østergaard Petersen a écrit : > Hi, > > I also have problems with namespaces in 508. > > Filtering with namespaces, as on line 266 of > > <http://exist.svn.sourceforge.net/viewvc/exist/apps/tamboti/modules/edit/body/00-compact-standalone.xml?view=markup&pathrev=15394> > > works in Chrome 14 and Safari 5.1, but not in FF 3.6 and 7. > > Inserting namespaced attributes, as on lines 227 and 236 of > > <http://exist.svn.sourceforge.net/viewvc/exist/apps/tamboti/modules/edit/body/01-title.xml?revision=15140&view=markup&pathrev=15394> > > does not work in any browser, though I am sure it has worked before. > > Am I doing something wrong? > > Best, > > Jens > > On Aug 10, 2011, at 1:11 AM, Leigh L Klotz Jr wrote: > >> Given this instance data: >> >> <?xml version="1.0" encoding="UTF-8"?> >> <data> >> <doc> >> <div xmlns="http://www.w3.org/1999/xhtml"> >> <p>Hi there</p> >> </div> >> </doc> >> </data> >> >> xsltforms-508 in all browsers tested (FF5, Chrome13, IE8) will match >> <group ref="doc/div" /> >> even though the div is in another namespace. >> >> Also, FF5 fails to match this: >> <group ref="doc/h:div" /> >> >> See attached files. >> >> Leigh. >> <foo.xml><test.xml>------------------------------------------------------------------------------ >> uberSVN's rich system and user administration capabilities and model >> configuration take the hassle out of deploying and managing Subversion and >> the tools developers use with it. Learn more about uberSVN and get a free >> download at: http://p.sf.net/sfu/wandisco-dev2dev >> _______________________________________________ >> Xsltforms-support mailing list >> Xsl...@li... >> https://lists.sourceforge.net/lists/listinfo/xsltforms-support > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > |
From: Jens Ø. P. <oe...@gm...> - 2011-10-04 08:26:56
|
Hi, I also have problems with namespaces in 508. Filtering with namespaces, as on line 266 of <http://exist.svn.sourceforge.net/viewvc/exist/apps/tamboti/modules/edit/body/00-compact-standalone.xml?view=markup&pathrev=15394> works in Chrome 14 and Safari 5.1, but not in FF 3.6 and 7. Inserting namespaced attributes, as on lines 227 and 236 of <http://exist.svn.sourceforge.net/viewvc/exist/apps/tamboti/modules/edit/body/01-title.xml?revision=15140&view=markup&pathrev=15394> does not work in any browser, though I am sure it has worked before. Am I doing something wrong? Best, Jens On Aug 10, 2011, at 1:11 AM, Leigh L Klotz Jr wrote: > Given this instance data: > > <?xml version="1.0" encoding="UTF-8"?> > <data> > <doc> > <div xmlns="http://www.w3.org/1999/xhtml"> > <p>Hi there</p> > </div> > </doc> > </data> > > xsltforms-508 in all browsers tested (FF5, Chrome13, IE8) will match > <group ref="doc/div" /> > even though the div is in another namespace. > > Also, FF5 fails to match this: > <group ref="doc/h:div" /> > > See attached files. > > Leigh. > <foo.xml><test.xml>------------------------------------------------------------------------------ > uberSVN's rich system and user administration capabilities and model > configuration take the hassle out of deploying and managing Subversion and > the tools developers use with it. Learn more about uberSVN and get a free > download at: http://p.sf.net/sfu/wandisco-dev2dev > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support |
From: Alain C. <ala...@ag...> - 2011-09-30 12:57:07
|
Hello Morgan, This action has to be defined within the model and not after the model declaration. You can also use a single element for this specific action: <xf:setvalue ev:event="xforms-ready" if="string(instance('i1')/row/column) != 'default'" ref="instance('i1')/row/column" value="'default'" /> Please note that I also replaced "@xf:if" by "@if". Thank you for your feedbacks! -Alain Le 30/09/2011 02:57, mcu...@co... a écrit : > Hello all: > > I am attempting to create an Xform (using XSLTForms and MarkLogic) where the instance initially contains no data, like this: > > <xf:model> > <xf:instance xmlns="" id="i1"> > <table> > <row> > <column></column> > </row> > </table> > </xf:instance> > </xf:model> > > I would like to set the value of the column element to "default" upon loading the form in a browser but have not been able to do so. > > My stab at it is the xquery below but it does not work as hoped. Can anyone tell me a correct way to do this? > > Thanks, > Morgan > > ---------------------------------- > xquery version "1.0-ml"; > declare namespace xdmp="http://marklogic.com/xdmp"; > > let $page := > (xdmp:set-response-content-type("application/xml"), > > > <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"> > <head> > <xf:model> > <xf:instance xmlns="" id="i1"> > <table> > <row> > <column></column> > </row> > </table> > </xf:instance> > </xf:model> > > <xf:action ev:event="xforms-ready"> > <xf:action xf:if="string(instance('i1')/row/column) != 'default'"> > <xf:setvalue ref="instance('i1')/row/column" value="'default'" /> > </xf:action> > </xf:action> > > > </head> > <body> > <h3>Datafield</h3> > <xf:group nodeset="/table"> > <xf:repeat id="repeat-row" nodeset="row"> > <xf:input ref="column"/> > </xf:repeat> > > <xf:trigger> > <xf:label>Add Row</xf:label> > <xf:action ev:event="DOMActivate" if="index('repeat-row') != (count(row))"> > <xf:insert nodeset="row" at="index('repeat-row')" position="after" /> > <xf:setvalue ref="row[index('repeat-row')]/column" > value="/table/row/column" /> > </xf:action> > > <xf:action ev:event="DOMActivate" if="index('repeat-row') = (count(row))"> > <xf:insert nodeset="row[last()]" position="after" at="last()"/> > <xf:setvalue ref="row[last()]/column" value="/table/row/column"/> > </xf:action> > > </xf:trigger> > > > </xf:group> > </body> > </html> > > ) > > let $xslt-pi := processing-instruction xml-stylesheet {'type="text/xsl" href="xsltforms/xsltforms.xsl"'} > return ($xslt-pi, $page) > > > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2dcopy2 > > > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support |
From: <mcu...@co...> - 2011-09-30 00:57:09
|
Hello all: I am attempting to create an Xform (using XSLTForms and MarkLogic) where the instance initially contains no data, like this: <xf:model> <xf:instance xmlns="" id="i1"> <table> <row> <column></column> </row> </table> </xf:instance> </xf:model> I would like to set the value of the column element to "default" upon loading the form in a browser but have not been able to do so. My stab at it is the xquery below but it does not work as hoped. Can anyone tell me a correct way to do this? Thanks, Morgan ---------------------------------- xquery version "1.0-ml"; declare namespace xdmp=" http://marklogic.com/xdmp "; let $page := (xdmp:set-response-content-type("application/xml"), <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 "> <head> <xf:model> <xf:instance xmlns="" id="i1"> <table> <row> <column></column> </row> </table> </xf:instance> </xf:model> <xf:action ev:event="xforms-ready"> <xf:action xf:if="string(instance('i1')/row/column) != 'default'"> <xf:setvalue ref="instance('i1')/row/column" value="'default'" /> </xf:action> </xf:action> </head> <body> <h3>Datafield</h3> <xf:group nodeset="/table"> <xf:repeat id="repeat-row" nodeset="row"> <xf:input ref="column"/> </xf:repeat> <xf:trigger> <xf:label>Add Row</xf:label> <xf:action ev:event="DOMActivate" if="index('repeat-row') != (count(row))"> <xf:insert nodeset="row" at="index('repeat-row')" position="after" /> <xf:setvalue ref="row[index('repeat-row')]/column" value="/table/row/column" /> </xf:action> <xf:action ev:event="DOMActivate" if="index('repeat-row') = (count(row))"> <xf:insert nodeset="row[last()]" position="after" at="last()"/> <xf:setvalue ref="row[last()]/column" value="/table/row/column"/> </xf:action> </xf:trigger> </xf:group> </body> </html> ) let $xslt-pi := processing-instruction xml-stylesheet {'type="text/xsl" href="xsltforms/xsltforms.xsl"'} return ($xslt-pi, $page) |
From: Leigh L K. Jr <lei...@xe...> - 2011-09-22 17:45:54
|
Looks like Chrome and FF >3.5 support it. http://code.google.com/p/chromium/issues/detail?id=12721 Perhaps this could be represented in markup using the existing <hint> as a new child of itemset, item, and choices: <itemset nodeset="foo"> <label ref="label" /> <value ref="value" /> <hint ref="hint" /> </itemset> Or <item> <label>Hello</label> <value>hello</value> <hint>It says "Hello"</hint> </item> Ditto for <choices> (label and hint). Leigh. On 09/05/2011 01:58 PM, Alain Couthures wrote: > > Hello, > > I'm not sure that the title attribute is well supported by every browser. > > Generating it with XSLTForms needs to change the XSLT stylesheet > (xsl:template match="xforms:item"). > > -Alain > > Le 05/09/2011 10:00, Ruslan Forostyanov a écrit : > > Hi guys! > > I have select1/itemset/label/value xform structure. > > What is the best way to get title attribute in generated select option. > > > > <select class="xforms-value"> > > <option id="xf-itemset-0" value="1" title="ORIGINAL TEXT HERE">CUTTED > > TEXT HERE...</option> > > <option id="clonedId0" cloned="true" oldid="xf-itemset-0" > > value="2">2</option> > > ... > > </select> > > > > Ruslan > > > > > ------------------------------------------------------------------------------ > > Special Offer -- Download ArcSight Logger for FREE! > Finally, a world-class log management solution at an even better > price-free! And you'll get a free "Love Thy Logs" t-shirt when you > download Logger. Secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsisghtdev2dev > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > |
From: Santosh C. <san...@gm...> - 2011-09-12 13:51:04
|
Hi Raja, There is no additional configuration needed. We transform the form to HTML beforehand so what we are running on android is simply HTML and javascript. So you don't need browser's XSLT processor, this will help in performance as well. I am running a previous version of XSLTForms (before introduction of native XML documents) since in my testing I found that the latest XSLTForms is slower than previous version. But the latest version might work too. Regards, Santosh On Mon, Sep 12, 2011 at 6:48 PM, Raja <m.r...@ni...> wrote: > Hi Santosh !!!! > > We are also testing the same but, i didnt find any relevant output or > how to run the XSLTForms in android mobile . If possible pls share me that > technical details about the XSLTForms configuration in android mobile . > > > By > Rajamani M > XRX Team > OTC > > On 09/11/11, *Santosh Chandak * <san...@gm...> wrote: > > Alain and Friends, > Just tried Our application on Android phone browser and the results are > amazing. I am really excited to share that it works great. Only things which > I did not found working are - > 1. Applets for loading and saving data and images which I am sure will find > something with the native Android stuff > 2. TinyMCE editor > > I will try it on i-phone also, has anyone tried it on iphone other devices > already? > > Regards, > Santosh > > > > > -- > Rajamani Marimuthu > Junior Research Fellow-JRF > NIC -Open Technology Centre > Rajaji Bhavan > Besant Nagar, > Chennai - 90 > Cell : 9677192096 > |
From: Raja <m.r...@ni...> - 2011-09-12 13:18:03
|
Hi Santosh !!!! We are also testing the same but, i didnt find any relevant output or how to run the XSLTForms in android mobile . If possible pls share me that technical details about the XSLTForms configuration in android mobile . By Rajamani M XRX Team OTC On 09/11/11, Santosh Chandak <san...@gm...> wrote: > Alain and Friends, > Just tried Our application on Android phone browser and the results are amazing. I am really excited to share that it works great. Only things which I did not found working are - > 1. Applets for loading and saving data and images which I am sure will find something with the native Android stuff > > 2. TinyMCE editor > > I will try it on i-phone also, has anyone tried it on iphone other devices already? > > Regards, > Santosh > > > > > > > -- Rajamani Marimuthu Junior Research Fellow-JRF NIC -Open Technology Centre Rajaji Bhavan Besant Nagar, Chennai - 90 Cell : 9677192096 |
From: Santosh C. <san...@gm...> - 2011-09-11 06:33:42
|
Yes, it works on iphone too. I did not try the xsltforms.xsl transform since we transform it beforehand. Regards, Santosh On Sun, Sep 11, 2011 at 11:42 AM, Santosh Chandak <san...@gm...>wrote: > Alain and Friends, > Just tried Our application on Android phone browser and the results are > amazing. I am really excited to share that it works great. Only things which > I did not found working are - > 1. Applets for loading and saving data and images which I am sure will find > something with the native Android stuff > 2. TinyMCE editor > > I will try it on i-phone also, has anyone tried it on iphone other devices > already? > > Regards, > Santosh > > > > > |