xsltforms-support Mailing List for XSLTForms (Page 60)
Brought to you by:
alain-couthures
Menu
▾
▴
xsltforms-support — XSLTForms support list
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: Philip F. <Phi...@ma...> - 2011-05-17 11:32:08
|
Claudius, Many thanks for the tip. Regards Philip Fennell Consultant MarkLogic Corporation One Kingdom Street Paddington Central London W2 6BD United Kingdom Mobile: +44 (0) 7824 830 866 Tel: +44 (0) 203 402 3619 email Phi...@ma...<mailto:Fir...@ma...> web www.marklogic.com<http://www.marklogic.com/> From: Claudius Teodorescu [mailto:cla...@ya...] Sent: Tuesday, May 17, 2011 12:31 PM To: Philip Fennell Cc: support xsltforms Subject: Re: Problem with exsltforms and Chrome... Hi, It is better to use: var xf_instance_extensions = new XFInstance("xf-instance-extensions", xf_model_extensions, true, 'application/xml', null, "<extensionRoot/>"); This is my fault, as I forgot to update the installation.txt file of version 1.0.7. BTW, exsltforms has now new and improved examples here<http://extxsltforms.sourceforge.net/sitKubera/index/index.xml>. Claudius Teodorescu http://extxsltforms.sourceforge.net/sitKubera/index/index.xml ________________________________ From: Philip Fennell <Phi...@ma...> To: Claudius Teodorescu <cla...@ya...> Cc: "xsl...@li..." <xsl...@li...> Sent: Tue, May 17, 2011 2:20:43 PM Subject: RE: Problem with exsltforms and Chrome... For anyone trying the same as me, I seem to have solved this problem by providing the two additional arguments as follows: var xf_instance_extensions = new XFInstance("xf-instance-extensions", xf_model_extensions, null, 'application/xml', '', "<extensionRoot/>"); The fourth and fifth arguments I have added as media-type = “application/xml” and src = “”. I have no idea if they are correct in this context (beyond the fact that the acceptable values for media-type seem to be ‘application/xml’ and ‘application/json’, but as for the ‘src’ I have no idea but it seems to work! Regards Philip Fennell Consultant MarkLogic Corporation One Kingdom Street Paddington Central London W2 6BD United Kingdom Mobile: +44 (0) 7824 830 866 Tel: +44 (0) 203 402 3619 email Phi...@ma...<mailto:Fir...@ma...> web www.marklogic.com<http://www.marklogic.com/> From: Philip Fennell [mailto:Phi...@ma...] Sent: Tuesday, May 17, 2011 11:48 AM To: Claudius Teodorescu Cc: xsl...@li... Subject: Re: [Xsltforms-support] Problem with exsltforms and Chrome... Further to yesterday’s question regarding XSLTForms and eXSLTForms I have now also tried eXSLTForms with both r494 and r502. In both FF and Chrome I get the following error message: Unsupported mediatype '<extensionRoot/>' for instance #xf-instance-extensions It would seem that the constructor ‘XFInstance’ is defined as having six arguments but it is being called with only for, hence the mismatch between an element name and the media-type. What would the correct values be for the six argument version of ‘XFInstance’ in this context? Regards Philip Fennell Consultant MarkLogic Corporation One Kingdom Street Paddington Central London W2 6BD United Kingdom Mobile: +44 (0) 7824 830 866 Tel: +44 (0) 203 402 3619 email Phi...@ma...<mailto:Fir...@ma...> web www.marklogic.com<http://www.marklogic.com/> From: Philip Fennell [mailto:Phi...@ma...] Sent: Tuesday, May 17, 2011 7:09 AM To: Claudius Teodorescu Cc: xsl...@li... Subject: [Xsltforms-support] Problem with exsltforms and Chrome... I’m currently using XSLTForms (Beta3), I’ve installed eXSLTForms (1.0.7) and I’m using the CKEdit (3.6) RTE extension. This all works fine in Firefox (3.6.10) but I get the following message with Chrome (11.0.696.68): XSLTForms Exception ---------------------------- Incorrect Javascript code generation: ReferenceError: initImpl is not defined at init ([webapp-uri]:271:1) at ([webapp-uri]:276:301) at onload ([webapp-uri]:277:4) ReferenceError: initImpl is not defined I have isolated the problem to the markup that is added to the ‘extensions’ element in xsltforms/config.xsl. Any ideas what the problem/fix might be? Regards Philip Fennell Consultant MarkLogic Corporation One Kingdom Street Paddington Central London W2 6BD United Kingdom Mobile: +44 (0) 7824 830 866 Tel: +44 (0) 203 402 3619 email Phi...@ma...<mailto:Fir...@ma...> web www.marklogic.com<http://www.marklogic.com/> |
|
From: Philip F. <Phi...@ma...> - 2011-05-17 11:30:56
|
When I try the same thing with Google Chrome () I get a little more info on the error: Type Error Cannot read property 'length' of null Something in or around the parsing of the event() function appears to be trying to get the length of a null value. Regards Philip Fennell Consultant MarkLogic Corporation One Kingdom Street Paddington Central London W2 6BD United Kingdom Mobile: +44 (0) 7824 830 866 Tel: +44 (0) 203 402 3619 email Phi...@ma...<mailto:Fir...@ma...> web www.marklogic.com<http://www.marklogic.com/> From: Philip Fennell [mailto:Phi...@ma...] Sent: Monday, May 16, 2011 1:10 PM To: xsl...@li... Subject: [Xsltforms-support] Error when using event function Hello, I have found an issue with the r502 build of XSLTForms. I download the tarball for the 502 revision and copied its contents into my application. When my forms are being processed I get the following message: XSLTForms Exception -------------------------- Error initializing : stringValue(null)@http://localhost:8031/resource/xsltforms/xsltforms.js:8334 ([object Element],[object Array],0,[object Array])@http://localhost:8031/resource/xsltforms/xsltforms.js:1944 ([object Object],[object Element])@http://localhost:8031/resource/xsltforms/xsltforms.js:4027 ([object Element])@http://localhost:8031/resource/xsltforms/xsltforms.js:4136 ([object Element])@http://localhost:8031/resource/xsltforms/xsltforms.js:4013 ([object HTMLSpanElement],[object Element],true)@http://localhost:8031/resource/xsltforms/xsltforms.js:1807 ([object HTMLSpanElement],[object Element],true)@http://localhost:8031/resource/xsltforms/xsltforms.js:1824 ([object HTMLBodyElement],[object Element],true)@http://localhost:8031/resource/xsltforms/xsltforms.js:1824 ()@http://localhost:8031/resource/xsltforms/xsltforms.js:1754 ()@http://localhost:8031/resource/xsltforms/xsltforms.js:1643 initImpl()@http://localhost:8031/admin/events:27 init()@http://localhost:8031/admin/events:2 onload([object Event])@http://localhost:8031/admin/events:1 TypeError value is null After a process of elimination I got to this repeatable test case (see below) which generates the error. This is also a problem with r490 too. It does work with Beta3. <?xml version="1.0" encoding="UTF-8"?> <?xml-stylesheet href="/resource/xsltforms/xsltforms.xsl" type="text/xsl"?> <html xml:lang="en" lang="en" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:ev="http://www.w3.org/2001/xml-events" xmlns:xf="http://www.w3.org/2002/xforms" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns="http://www.w3.org/1999/xhtml"> <head> <title>EOI: Events Management</title> <meta http-equiv="content-language" content="en"/> <meta http-equiv="cache-control" content="no-cache"/> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/> <xf:model> <!-- === Collection. =========================================== --> <xf:submission id="retrieve-collection" method="get" instance="collection" replace="instance" resource="/events.atom" serialization="none"> <xf:action ev:event="xforms-submit-error"> <xf:message level="modal"> <xf:output value="event('response-reason-phrase')"/> </xf:message> </xf:action> </xf:submission> <xf:instance id="collection"> <atom:feed/> </xf:instance> <xf:bind id="entries" nodeset="instance('collection')/atom:entry"/> </xf:model> </head> <body> <div id="content"> </div> </body> </html> |
|
From: Philip F. <Phi...@ma...> - 2011-05-17 11:20:52
|
For anyone trying the same as me, I seem to have solved this problem by providing the two additional arguments as follows:
var xf_instance_extensions = new XFInstance("xf-instance-extensions", xf_model_extensions, null, 'application/xml', '', "<extensionRoot/>");
The fourth and fifth arguments I have added as media-type = "application/xml" and src = "".
I have no idea if they are correct in this context (beyond the fact that the acceptable values for media-type seem to be 'application/xml' and 'application/json', but as for the 'src' I have no idea but it seems to work!
Regards
Philip Fennell
Consultant
MarkLogic Corporation
One Kingdom Street
Paddington Central
London W2 6BD
United Kingdom
Mobile: +44 (0) 7824 830 866
Tel: +44 (0) 203 402 3619
email Phi...@ma...<mailto:Fir...@ma...>
web www.marklogic.com<http://www.marklogic.com/>
From: Philip Fennell [mailto:Phi...@ma...]
Sent: Tuesday, May 17, 2011 11:48 AM
To: Claudius Teodorescu
Cc: xsl...@li...
Subject: Re: [Xsltforms-support] Problem with exsltforms and Chrome...
Further to yesterday's question regarding XSLTForms and eXSLTForms I have now also tried eXSLTForms with both r494 and r502.
In both FF and Chrome I get the following error message:
Unsupported mediatype '<extensionRoot/>' for instance #xf-instance-extensions
It would seem that the constructor 'XFInstance' is defined as having six arguments but it is being called with only for, hence the mismatch between an element name and the media-type.
What would the correct values be for the six argument version of 'XFInstance' in this context?
Regards
Philip Fennell
Consultant
MarkLogic Corporation
One Kingdom Street
Paddington Central
London W2 6BD
United Kingdom
Mobile: +44 (0) 7824 830 866
Tel: +44 (0) 203 402 3619
email Phi...@ma...<mailto:Fir...@ma...>
web www.marklogic.com<http://www.marklogic.com/>
From: Philip Fennell [mailto:Phi...@ma...]
Sent: Tuesday, May 17, 2011 7:09 AM
To: Claudius Teodorescu
Cc: xsl...@li...
Subject: [Xsltforms-support] Problem with exsltforms and Chrome...
I'm currently using XSLTForms (Beta3), I've installed eXSLTForms (1.0.7) and I'm using the CKEdit (3.6) RTE extension. This all works fine in Firefox (3.6.10) but I get the following message with Chrome (11.0.696.68):
XSLTForms Exception
----------------------------
Incorrect Javascript code generation:
ReferenceError: initImpl is not defined
at init
([webapp-uri]:271:1)
at
([webapp-uri]:276:301)
at onload
([webapp-uri]:277:4)
ReferenceError:
initImpl is not defined
I have isolated the problem to the markup that is added to the 'extensions' element in xsltforms/config.xsl.
Any ideas what the problem/fix might be?
Regards
Philip Fennell
Consultant
MarkLogic Corporation
One Kingdom Street
Paddington Central
London W2 6BD
United Kingdom
Mobile: +44 (0) 7824 830 866
Tel: +44 (0) 203 402 3619
email Phi...@ma...<mailto:Fir...@ma...>
web www.marklogic.com<http://www.marklogic.com/>
|
|
From: Philip F. <Phi...@ma...> - 2011-05-17 10:48:29
|
Further to yesterday's question regarding XSLTForms and eXSLTForms I have now also tried eXSLTForms with both r494 and r502. In both FF and Chrome I get the following error message: Unsupported mediatype '<extensionRoot/>' for instance #xf-instance-extensions It would seem that the constructor 'XFInstance' is defined as having six arguments but it is being called with only for, hence the mismatch between an element name and the media-type. What would the correct values be for the six argument version of 'XFInstance' in this context? Regards Philip Fennell Consultant MarkLogic Corporation One Kingdom Street Paddington Central London W2 6BD United Kingdom Mobile: +44 (0) 7824 830 866 Tel: +44 (0) 203 402 3619 email Phi...@ma...<mailto:Fir...@ma...> web www.marklogic.com<http://www.marklogic.com/> From: Philip Fennell [mailto:Phi...@ma...] Sent: Tuesday, May 17, 2011 7:09 AM To: Claudius Teodorescu Cc: xsl...@li... Subject: [Xsltforms-support] Problem with exsltforms and Chrome... I'm currently using XSLTForms (Beta3), I've installed eXSLTForms (1.0.7) and I'm using the CKEdit (3.6) RTE extension. This all works fine in Firefox (3.6.10) but I get the following message with Chrome (11.0.696.68): XSLTForms Exception ---------------------------- Incorrect Javascript code generation: ReferenceError: initImpl is not defined at init ([webapp-uri]:271:1) at ([webapp-uri]:276:301) at onload ([webapp-uri]:277:4) ReferenceError: initImpl is not defined I have isolated the problem to the markup that is added to the 'extensions' element in xsltforms/config.xsl. Any ideas what the problem/fix might be? Regards Philip Fennell Consultant MarkLogic Corporation One Kingdom Street Paddington Central London W2 6BD United Kingdom Mobile: +44 (0) 7824 830 866 Tel: +44 (0) 203 402 3619 email Phi...@ma...<mailto:Fir...@ma...> web www.marklogic.com<http://www.marklogic.com/> |
|
From: Philip F. <Phi...@ma...> - 2011-05-17 06:09:23
|
I'm currently using XSLTForms (Beta3), I've installed eXSLTForms (1.0.7) and I'm using the CKEdit (3.6) RTE extension. This all works fine in Firefox (3.6.10) but I get the following message with Chrome (11.0.696.68): XSLTForms Exception ---------------------------- Incorrect Javascript code generation: ReferenceError: initImpl is not defined at init ([webapp-uri]:271:1) at ([webapp-uri]:276:301) at onload ([webapp-uri]:277:4) ReferenceError: initImpl is not defined I have isolated the problem to the markup that is added to the 'extensions' element in xsltforms/config.xsl. Any ideas what the problem/fix might be? Regards Philip Fennell Consultant MarkLogic Corporation One Kingdom Street Paddington Central London W2 6BD United Kingdom Mobile: +44 (0) 7824 830 866 Tel: +44 (0) 203 402 3619 email Phi...@ma...<mailto:Fir...@ma...> web www.marklogic.com<http://www.marklogic.com/> |
|
From: Mark T <par...@gm...> - 2011-05-17 03:16:18
|
A clue ... http://perfectionkills.com/understanding-delete/ This gives me some indication as to the preparation required for 'removing' an xsltXform from a Document. Other areas of interest are in the behavior of scripts in different load modes. 'onload' being a useful trigger. This can be in the xml of the form (body or html tags), on an object or in the xslt-generated javascript. Triggering of these occurs differently in transformToDocument <=\/=> transformToFragment. A fragment seems more contextually appropriate, though will require more re-wiring of the script triggers. Browser context of fragments may differ. Strict ECMA-5 may have something relevant to the delete op: http://ejohn.org/blog/ecmascript-5-strict-mode-json-and-more/. MarkT |
|
From: Philip F. <Phi...@ma...> - 2011-05-16 12:10:18
|
Hello,
I have found an issue with the r502 build of XSLTForms.
I download the tarball for the 502 revision and copied its contents into my application. When my forms are being processed I get the following message:
XSLTForms Exception
--------------------------
Error initializing :
stringValue(null)@http://localhost:8031/resource/xsltforms/xsltforms.js:8334
([object Element],[object Array],0,[object Array])@http://localhost:8031/resource/xsltforms/xsltforms.js:1944
([object Object],[object Element])@http://localhost:8031/resource/xsltforms/xsltforms.js:4027
([object Element])@http://localhost:8031/resource/xsltforms/xsltforms.js:4136
([object Element])@http://localhost:8031/resource/xsltforms/xsltforms.js:4013
([object HTMLSpanElement],[object Element],true)@http://localhost:8031/resource/xsltforms/xsltforms.js:1807
([object HTMLSpanElement],[object Element],true)@http://localhost:8031/resource/xsltforms/xsltforms.js:1824
([object HTMLBodyElement],[object Element],true)@http://localhost:8031/resource/xsltforms/xsltforms.js:1824
()@http://localhost:8031/resource/xsltforms/xsltforms.js:1754
()@http://localhost:8031/resource/xsltforms/xsltforms.js:1643
initImpl()@http://localhost:8031/admin/events:27
init()@http://localhost:8031/admin/events:2
onload([object Event])@http://localhost:8031/admin/events:1
TypeError
value is null
After a process of elimination I got to this repeatable test case (see below) which generates the error. This is also a problem with r490 too. It does work with Beta3.
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/resource/xsltforms/xsltforms.xsl" type="text/xsl"?>
<html xml:lang="en" lang="en"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:ev="http://www.w3.org/2001/xml-events"
xmlns:xf="http://www.w3.org/2002/xforms"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xhtml="http://www.w3.org/1999/xhtml"
xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>EOI: Events Management</title>
<meta http-equiv="content-language" content="en"/>
<meta http-equiv="cache-control" content="no-cache"/>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
<xf:model>
<!-- === Collection. =========================================== -->
<xf:submission id="retrieve-collection" method="get" instance="collection" replace="instance" resource="/events.atom" serialization="none">
<xf:action ev:event="xforms-submit-error">
<xf:message level="modal">
<xf:output value="event('response-reason-phrase')"/>
</xf:message>
</xf:action>
</xf:submission>
<xf:instance id="collection">
<atom:feed/>
</xf:instance>
<xf:bind id="entries" nodeset="instance('collection')/atom:entry"/>
</xf:model>
</head>
<body>
<div id="content">
</div>
</body>
</html>
|
|
From: Mark T <par...@gm...> - 2011-05-16 04:55:39
|
I'm trying to use processor.transformToDocument(....) to rebuild an xsltForm 'inplace'. The xsltXform xsl is GET'd and 'hello.xml' is GET'd. So I have javascript in a page which uses: processor.setParameter(null, "xsltforms_debug", "true"); // parameter settings.... They are combined using transformToDocument. This is then imported: var newForm = document.importNode(xmlDoc.documentElement, true); The newForm is of type 'Document'. This is attached to a node in the document. This is testing fine for the initial loading. A second invocation retrieves 'checkbox.xml' and attempts to do the same thing. The heading loads. No checkboxes. If I then attempt a second loading of 'hello.xml', the form loads and is showing the previous text entry. The above is testing with Chrome. (I am getting slightly different behavior with Firefox with which I am attempting to use transformToFragment). One area I am working on is the removal of relevant nodes and associated variables built by xsltForms. So that a new one can replace it. (Alain... is there a deleteXForm in there somewhere?) Can anyone link me with pages of clues for these types of actions? All the best, MarkT |
|
From: C. M. Sperberg-M. <cm...@bl...> - 2011-05-11 13:13:06
|
Just a quick reminder that 16 May is the deadliine for 'early bird' registration (and a corresponding discount) for the two-day introductory course on XForms being offered 16-17 June in San Carlos, California (at Mark Logic headquarters). XForms can help any project manage XML data more effectively and efficiently. The focus of the project is on the use of XForms to make specialized task-specific editors for specific XML vocabularies; because they can focus on a single task, task-specific editors can omit much of the functionality needed by a general-purpose tool and thus achieve a simpler user interface. XForms makes it possible to write a large class of task-specific editors much more simply, quickly, and easily than would otherwise be possible. For full information, see http://www.xforms201106.blackmesatech.com/ Space in the course is limited. To reserve a space in the course, to register, or for more information, please send email to in...@bl... or call Black Mesa Techologies at +1 505 747-4224. -- **************************************************************** * C. M. Sperberg-McQueen, Black Mesa Technologies LLC * http://www.blackmesatech.com * http://cmsmcq.com/mib * http://balisage.net **************************************************************** |
|
From: Philip F. <Phi...@ma...> - 2011-05-10 15:23:58
|
Alain, > What if the result of the transformation is a text? Currently, if the transform returns just text then Firefox wraps the result of the transform in an element but, of course, this gets serialized too. May be there should be a standard 'wrapper' element for plain text results in the same way that XProc will wrap the result of a p:data instruction defined in an input source port (used to retrieve non-XML content) in a c:data element. Regards Philip From: Alain Couthures [mailto:ala...@ag...] Sent: Tuesday, May 10, 2011 4:13 PM To: Philip Fennell Cc: xsl...@li... Subject: Re: [Xsltforms-support] Hints on using the transform function Philip, Would an alternative implementation of the transform function return a node and then you could use the existing serialize function to generate the textual representation from the result of transform? Wouldn't the result always be a document root or a document element? Considering that I don't know if people are already using the current transform() function, wouldn't it be better to name this function transform-doc(), for example? What if the result of the transformation is a text? Regards, -Alain |
|
From: Alain C. <ala...@ag...> - 2011-05-10 15:10:46
|
Philip, > Would an alternative implementation of the transform function return a > node and then you could use the existing serialize function to > generate the textual representation from the result of transform? Wouldn't the result always be a document root or a document element? Considering that I don't know if people are already using the current transform() function, wouldn't it be better to name this function transform-doc(), for example? What if the result of the transformation is a text? Regards, -Alain |
|
From: Philip F. <Phi...@ma...> - 2011-05-10 09:01:54
|
Alain,
Thank you. Yes, I can see that the function works when I use xf:setvalue to send the result to a text node. Would an alternative implementation of the transform function return a node and then you could use the existing serialize function to generate the textual representation from the result of transform?
Regards
Philip
From: Alain Couthures [mailto:ala...@ag...]
Sent: Tuesday, May 10, 2011 8:00 AM
To: Philip Fennell
Cc: xsl...@li...
Subject: Re: [Xsltforms-support] Hints on using the transform function
Hello Philip,
I've been experimenting with XSLTForms' extension transform function but I can't seem to get it to work or, maybe, I'm not using it correctly. I had hoped I could use it to apply a transform to one instance and deposit the result into another by using an xf:insert:
<xf:insert origin="transform(instance('source'), '/resources/schemas/schematron/atom-feed.xsl')" position="after" nodeset="." context="instance('svrlReport')"/>
The current transform() function in XSLTForms returns a string. A parse() function could be added to get an XML Document instead.
Regards,
-Alain
|
|
From: Alain C. <ala...@ag...> - 2011-05-10 06:57:43
|
Hello Philip,
> I've been experimenting with XSLTForms' extension transform function
> but I can't seem to get it to work or, maybe, I'm not using it
> correctly. I had hoped I could use it to apply a transform to one
> instance and deposit the result into another by using an xf:insert:
> <xf:insert origin="transform(instance('source'),
> '/resources/schemas/schematron/atom-feed.xsl')" position="after"
> nodeset="." context="instance('svrlReport')"/>
The current transform() function in XSLTForms returns a string. A
parse() function could be added to get an XML Document instead.
Regards,
-Alain
|
|
From: Philip F. <Phi...@ma...> - 2011-05-10 06:49:24
|
I've been experimenting with XSLTForms' extension transform function but I can't seem to get it to work or, maybe, I'm not using it correctly. I had hoped I could use it to apply a transform to one instance and deposit the result into another by using an xf:insert:
<xf:insert origin="transform(instance('source'), '/resources/schemas/schematron/atom-feed.xsl')" position="after" nodeset="." context="instance('svrlReport')"/>
I've tested the transform in the browser and it does work, I also know that the plain insert works but when I invoke the 'insert' in my form with the transform function as described above - nothing happens.
How should I be invoking the transform function?
Regards
Philip
|
|
From: Grégoire C. <gco...@gm...> - 2011-05-09 20:41:46
|
Hi Alain!
Indeed this was a problem with my form, using xf:output @ref instead of
@value.
Thanks!
Grégoire
Le 09/05/2011 21:47, Alain Couthures a écrit :
> Hi Grégoire,
>
> Sorry, I don't understand what the problem is: the substring() function
> is clearly returning a string and not a nodeset!
>
> Could you give me a test case?
>
> Thanks!
>
> -Alain
>
> Le 09/05/2011 20:49, Grégoire COLBERT a écrit :
>> Hi Alain!
>>
>> I've got a problem with revision 502, on initialization I get:
>>
>> Binding evaluation didn't returned a nodeset but '' for XPath
>> expression: substring(instance('instance-annonces')/annonce[id =
>> instance('instance-annonce-selectionnee')/id]/date-de-creation,9,2)
>>
>> Is this something I need to change in my XForms, or a problem with rev 502?
>>
>> Thanks!
>> Grégoire
>>
>> ------------------------------------------------------------------------------
>> WhatsUp Gold - Download Free Network Management Software
>> The most intuitive, comprehensive, and cost-effective network
>> management toolset available today. Delivers lowest initial
>> acquisition cost and overall TCO of any competing solution.
>> http://p.sf.net/sfu/whatsupgold-sd
>> _______________________________________________
>> Xsltforms-support mailing list
>> Xsl...@li...
>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>
>
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network
> management toolset available today. Delivers lowest initial
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
|
|
From: Alain C. <ala...@ag...> - 2011-05-09 19:45:28
|
Hi Grégoire,
Sorry, I don't understand what the problem is: the substring() function
is clearly returning a string and not a nodeset!
Could you give me a test case?
Thanks!
-Alain
Le 09/05/2011 20:49, Grégoire COLBERT a écrit :
> Hi Alain!
>
> I've got a problem with revision 502, on initialization I get:
>
> Binding evaluation didn't returned a nodeset but '' for XPath
> expression: substring(instance('instance-annonces')/annonce[id =
> instance('instance-annonce-selectionnee')/id]/date-de-creation,9,2)
>
> Is this something I need to change in my XForms, or a problem with rev 502?
>
> Thanks!
> Grégoire
>
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network
> management toolset available today. Delivers lowest initial
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
|
|
From: Grégoire C. <gco...@ar...> - 2011-05-09 19:16:19
|
Hi Alain!
I've got a problem with revision 502, on initialization I get:
Binding evaluation didn't returned a nodeset but '' for XPath
expression: substring(instance('instance-annonces')/annonce[id =
instance('instance-annonce-selectionnee')/id]/date-de-creation,9,2)
Is this something I need to change in my XForms, or a problem with rev 502?
Thanks!
Grégoire
|
|
From: Leigh L K. Jr <lei...@xe...> - 2011-05-03 20:08:54
|
Asian language IME systems are used to convert keyboard events into text. On Windows (at least), pressing the Enter key to accept a proposed conversion also incorrectly dispatches DOMActivate to the input control. In this situation, the Windows IME sends keyup charcode 13 but it has not previously sent keydown or keypress charcode 13. XSLTForms listens on keyup only, and therefore wrongly dispatches DOMActivate on charcode 13 during the input editing process. A proposed fix for XSLTForms would be to listen to keydown, keypress, and keep a state flag for input. If keydown or keypress charcode is not 13, then the state flag should be set to false. In keyup, only if the state flag is true should keyup charcode 13 dispatch DOMActivate. Here is a test case, with one incremental and one regular xf:input. <?xml version="1.0"?> <?xml-stylesheet href="/xsltforms/xsltforms.xsl" type="text/xsl"?> <?css-conversion no?> <?xsltforms-options debug="no" lang="en_US" css="no"?> <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>Japanese DOMActivate</title> <xf:model> <xf:instance> <data xmlns=""> <term /> </data> </xf:instance> </xf:model> </head> <body> <xf:input ref="term" incremental="true"> <xf:label>Text</xf:label> <xf:message level="modal" ev:event="DOMActivate">hi</xf:message> </xf:input> <xf:input ref="term"> <xf:label>Text</xf:label> <xf:message level="modal" ev:event="DOMActivate">hi</xf:message> </xf:input> </body> </html> Here are some references which propose the state flag solution: http://getsatisfaction.com/springpartners/topics/when_create_a_stuff_via_japanese_ime_enter_is_misidentified http://springpadit.com/shin3/note/keyeventsviajapaneseime http://groups.google.com/group/codemirror/browse_thread/thread/5a2db8b81f0c8535/b700a1493f3d7feb?lnk=raot&fwc=2 Here is a proposed solution for XSLTForms that stores the state variable in this.wasEnter (this == HTML input object). You may prefer a different implementation. I have tested this in Windows FF4, IE8, Chrome 11. I was unable to test it in IETester so I have no tests for IE6, IE7, or IE9. I have not tested this with IME on any other platforms. diff -c2 xsltforms.js~ xsltforms.js *** xsltforms.js~ 2011-05-02 14:35:04.000000000 -0700 --- xsltforms.js 2011-05-03 12:59:25.387599997 -0700 *************** *** 4502,4505 **** --- 4502,4507 ---- XSLTFormsEvent.attach(input, "keyup", XFInput.keyUpActivate); } + XSLTFormsEvent.attach(input, "keydown", XFInput.keyDownActivate); + XSLTFormsEvent.attach(input, "keypress", XFInput.keyPressActivate); } else { if (this.incremental) { *************** *** 4559,4572 **** XFInput.keyUpActivate = function(a) { var xf = XFControl.getXFElement(this); ! if (a.keyCode == 13) { xforms.openAction(); xf.valueChanged(this.value || ""); XMLEvents.dispatch(xf, "DOMActivate"); xforms.closeAction(); ! } }; --- 4561,4583 ---- + XFInput.keyDownActivate = function(a) { + this.wasEnterKey = (a.keyCode == 13); + } + + XFInput.keyPressActivate = function(a) { + this.wasEnterKey = this.wasEnterKey && (a.keyCode == 13); + } XFInput.keyUpActivate = function(a) { var xf = XFControl.getXFElement(this); ! if (this.wasEnterKey && a.keyCode == 13) { xforms.openAction(); xf.valueChanged(this.value || ""); XMLEvents.dispatch(xf, "DOMActivate"); xforms.closeAction(); ! } else { ! this.wasEnterKey = false; ! } }; *************** *** 4576,4580 **** XFInput.keyUpIncrementalActivate = function(a) { var xf = XFControl.getXFElement(this); ! if (a.keyCode == 13) { xforms.openAction(); xf.valueChanged(this.value || ""); --- 4587,4591 ---- XFInput.keyUpIncrementalActivate = function(a) { var xf = XFControl.getXFElement(this); ! if (this.wasEnterKey && a.keyCode == 13) { xforms.openAction(); xf.valueChanged(this.value || ""); *************** *** 4582,4585 **** --- 4593,4597 ---- xforms.closeAction(); } else { + this.wasEnterKey = false; if (xf.delay && xf.delay > 0) { if (xf.timer) { *************** *** 10190,10192 **** Leigh. |
|
From: Leigh L K. Jr <lei...@xe...> - 2011-05-02 22:51:27
|
Alain, Thank you! This works. I also found another spot in xsltforms-295 that needed this same change, but it's already present there in xsltforms-501. Leigh. On 05/02/2011 12:40 PM, Alain Couthures wrote: > > Leigh, > > The event management in IE is different and it appears to be the cause > of this issue (I'm surprised about IE6...). > > The corresponding exception is now ignored in Rev. 502. > > Thanks! > > -Alain > > Le 30/04/2011 00:35, Leigh L Klotz Jr a écrit : > > This bug occurs in xsltforms-295 and xsltforms-dataisland 495 and > > xsltforms-501, so it appears quite a robust bug. > > > > With submission @method='get' and @replace='all', trigger/send fails > > with a JavaScript error "Permission Denied", but plain xf:submit works. > > > > It fails in IE7 and IE8. It is not affected by compatibility view > > setting in IE8. > > It works in IE6, Firefox 4, and Chrome 11. > > > > <?xml version="1.0"?> > > <?xml-stylesheet href="/~klotz/xsltforms/xsltforms.xsl" > type="text/xsl"?> > > <?css-conversion no?> > > <?xsltforms-options debug="no" lang="en_US" css="no"?> > > <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>Trigger replace bug</title> > > <xf:model> > > <xf:instance> > > <data xmlns=""> > > <term>sample</term> > > </data> > > </xf:instance> > > <xf:submission id="doSearch" action="hello.html" method="get" > > replace="all" /> > > </xf:model> > > </head> > > <body> > > <xf:input ref="term"> > > <xf:label>Text</xf:label> > > </xf:input> > > <xf:trigger> > > <xf:label>Fails</xf:label> > > <xf:send ev:event="DOMActivate" submission="doSearch" /> > > </xf:trigger> > > <xf:submit submission="doSearch"> > > <xf:label>Works</xf:label> > > </xf:submit> > > </body> > > </html> > > > > The replaced file doesn't matter. Here is hello.html: > > <html> > > <head> > > <title>hi</title> > > </head> > > <body> > > <h1>test</h1> > > </body> > > </html> > > > > Leigh. > > > > > > > ------------------------------------------------------------------------------ > > WhatsUp Gold - Download Free Network Management Software > > The most intuitive, comprehensive, and cost-effective network > > management toolset available today. Delivers lowest initial > > acquisition cost and overall TCO of any competing solution. > > http://p.sf.net/sfu/whatsupgold-sd > > _______________________________________________ > > Xsltforms-support mailing list > > Xsl...@li... > > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > > > |
|
From: Alain C. <ala...@ag...> - 2011-05-02 19:43:13
|
Leigh, I have checked the XPath functions and added the corresponding test when required. This should be OK in Rev. 502. Thanks! -Alain Le 30/04/2011 01:40, Leigh L Klotz Jr a écrit : > If you call serialize(x) and x does not exist, you get a fatal popup > error from the browser. > Form authors can't protect against it because XPath will still evaluate > the arguments even if you try to check for non-existent nodes. > > I had a patch for this which I included accidentally in another patch. > http://sourceforge.net/mailarchive/forum.php?thread_name=4D7A99D5.2000606%40xerox.com&forum_name=xsltforms-support > <http://sourceforge.net/mailarchive/forum.php?thread_name=4D7A99D5.2000606%40xerox.com&forum_name=xsltforms-support> > > Here is the patch by itself this time: > > --- xsltforms.js.orig 2011-04-29 16:37:59.492079329 -0700 > +++ xsltforms.js.new 2011-04-29 16:33:29.339003561 -0700 > @@ -9569,6 +9569,7 @@ > if (arguments.length == 0) { > throw XPathCoreFunctionsExceptions.serializeNoContext; > } > + if (!nodeSet[0]) return ""; > return Core.saveXML(nodeSet[0]); > } ), > > > It's quite possible transform() has the same problem but I have not > tested it. > > Leigh. > > ------------------------------------------------------------------------------ > WhatsUp Gold - Download Free Network Management Software > The most intuitive, comprehensive, and cost-effective network > management toolset available today. Delivers lowest initial > acquisition cost and overall TCO of any competing solution. > http://p.sf.net/sfu/whatsupgold-sd > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > |
|
From: Alain C. <ala...@ag...> - 2011-05-02 19:38:04
|
Leigh, The event management in IE is different and it appears to be the cause of this issue (I'm surprised about IE6...). The corresponding exception is now ignored in Rev. 502. Thanks! -Alain Le 30/04/2011 00:35, Leigh L Klotz Jr a écrit : > This bug occurs in xsltforms-295 and xsltforms-dataisland 495 and > xsltforms-501, so it appears quite a robust bug. > > With submission @method='get' and @replace='all', trigger/send fails > with a JavaScript error "Permission Denied", but plain xf:submit works. > > It fails in IE7 and IE8. It is not affected by compatibility view > setting in IE8. > It works in IE6, Firefox 4, and Chrome 11. > > <?xml version="1.0"?> > <?xml-stylesheet href="/~klotz/xsltforms/xsltforms.xsl" type="text/xsl"?> > <?css-conversion no?> > <?xsltforms-options debug="no" lang="en_US" css="no"?> > <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>Trigger replace bug</title> > <xf:model> > <xf:instance> > <data xmlns=""> > <term>sample</term> > </data> > </xf:instance> > <xf:submission id="doSearch" action="hello.html" method="get" > replace="all" /> > </xf:model> > </head> > <body> > <xf:input ref="term"> > <xf:label>Text</xf:label> > </xf:input> > <xf:trigger> > <xf:label>Fails</xf:label> > <xf:send ev:event="DOMActivate" submission="doSearch" /> > </xf:trigger> > <xf:submit submission="doSearch"> > <xf:label>Works</xf:label> > </xf:submit> > </body> > </html> > > The replaced file doesn't matter. Here is hello.html: > <html> > <head> > <title>hi</title> > </head> > <body> > <h1>test</h1> > </body> > </html> > > Leigh. > > > ------------------------------------------------------------------------------ > WhatsUp Gold - Download Free Network Management Software > The most intuitive, comprehensive, and cost-effective network > management toolset available today. Delivers lowest initial > acquisition cost and overall TCO of any competing solution. > http://p.sf.net/sfu/whatsupgold-sd > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > |
|
From: Leigh L K. Jr <lei...@xe...> - 2011-04-29 23:40:11
|
If you call serialize(x) and x does not exist, you get a fatal popup error from the browser. Form authors can't protect against it because XPath will still evaluate the arguments even if you try to check for non-existent nodes. I had a patch for this which I included accidentally in another patch. http://sourceforge.net/mailarchive/forum.php?thread_name=4D7A99D5.2000606%40xerox.com&forum_name=xsltforms-support <http://sourceforge.net/mailarchive/forum.php?thread_name=4D7A99D5.2000606%40xerox.com&forum_name=xsltforms-support> Here is the patch by itself this time: --- xsltforms.js.orig 2011-04-29 16:37:59.492079329 -0700 +++ xsltforms.js.new 2011-04-29 16:33:29.339003561 -0700 @@ -9569,6 +9569,7 @@ if (arguments.length == 0) { throw XPathCoreFunctionsExceptions.serializeNoContext; } + if (!nodeSet[0]) return ""; return Core.saveXML(nodeSet[0]); } ), It's quite possible transform() has the same problem but I have not tested it. Leigh. |
|
From: Leigh L K. Jr <lei...@xe...> - 2011-04-29 22:35:30
|
This bug occurs in xsltforms-295 and xsltforms-dataisland 495 and xsltforms-501, so it appears quite a robust bug. With submission @method='get' and @replace='all', trigger/send fails with a JavaScript error "Permission Denied", but plain xf:submit works. It fails in IE7 and IE8. It is not affected by compatibility view setting in IE8. It works in IE6, Firefox 4, and Chrome 11. <?xml version="1.0"?> <?xml-stylesheet href="/~klotz/xsltforms/xsltforms.xsl" type="text/xsl"?> <?css-conversion no?> <?xsltforms-options debug="no" lang="en_US" css="no"?> <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>Trigger replace bug</title> <xf:model> <xf:instance> <data xmlns=""> <term>sample</term> </data> </xf:instance> <xf:submission id="doSearch" action="hello.html" method="get" replace="all" /> </xf:model> </head> <body> <xf:input ref="term"> <xf:label>Text</xf:label> </xf:input> <xf:trigger> <xf:label>Fails</xf:label> <xf:send ev:event="DOMActivate" submission="doSearch" /> </xf:trigger> <xf:submit submission="doSearch"> <xf:label>Works</xf:label> </xf:submit> </body> </html> The replaced file doesn't matter. Here is hello.html: <html> <head> <title>hi</title> </head> <body> <h1>test</h1> </body> </html> Leigh. |
|
From: Ivan P. <ipo...@ma...> - 2011-04-26 11:27:51
|
Hello, Nick! Why typos? Isn't it just a comma operator (http://en.m.wikipedia.org/wiki?search=Comma+operator) that stands where it should to provide in-place initialization of document.applets["xsltforms"]?? Regards, Ivan On 25.04.2011, at 20:31, Nick Van den Bleeken <ni...@bl...> wrote: > Hi, > > Shouldn't the ',' chars on line 328 and 337 not be a '.' (after Core.loadapplet())? > > First one: > > Core.javaReadFile = function(fname, encoding, xsdtype, title) { > if (document.applets["xsltforms"] || (Core.loadapplet(),document.applets["xsltforms"])) { > return document.applets["xsltforms"].readFile(fname, encoding, xsdtype, title) || ""; > } > return ""; > }; > > Second one: > > Core.javaWriteFile = function(fname, encoding, xsdtype, title, content) { > if (document.applets["xsltforms"] || (Core.loadapplet(),document.applets["xsltforms"])) { > if (fname == "") { > fname = document.applets["xsltforms"].lastChosenFileName; > } > return document.applets["xsltforms"].writeFile(fname, encoding, xsdtype, title, content) == 1; > } > return false; > }; > > -- > Regards, > > Nick Van den Bleeken > ------------------------------------------------------------------------------ > WhatsUp Gold - Download Free Network Management Software > The most intuitive, comprehensive, and cost-effective network > management toolset available today. Delivers lowest initial > acquisition cost and overall TCO of any competing solution. > http://p.sf.net/sfu/whatsupgold-sd > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support |
|
From: Nick V. d. B. <ni...@bl...> - 2011-04-25 17:01:25
|
Hi,
Shouldn't the ',' chars on line 328 and 337 not be a '.' (after
Core.loadapplet())?
First one:
Core.javaReadFile = function(fname, encoding, xsdtype, title) {
if (document.applets["xsltforms"] ||
(Core.loadapplet(),document.applets["xsltforms"])) {
return document.applets["xsltforms"].readFile(fname, encoding,
xsdtype, title) || "";
}
return "";
};
Second one:
Core.javaWriteFile = function(fname, encoding, xsdtype, title, content) {
if (document.applets["xsltforms"] ||
(Core.loadapplet(),document.applets["xsltforms"])) {
if (fname == "") {
fname = document.applets["xsltforms"].lastChosenFileName;
}
return document.applets["xsltforms"].writeFile(fname, encoding,
xsdtype, title, content) == 1;
}
return false;
};
--
Regards,
Nick Van den Bleeken
|
97 messages has been excluded from this view by a project administrator.
