xsltforms-support — XSLTForms support list

Re: [Xsltforms-support] Download action/control

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

Hi Mats,

 From the XForms Recommendation point of view, it is already possible to 
write an instance to disk using the "file:" protocol. As you know, for 
security reasons, browser vendors have decided not to allow file 
writing. XSLTForms includes a small Java applet which can write a file 
but, again for security reasons, I chose to first display the "Save as" 
dialog to alert the user and allow him/her to cancel this. XForms 
submissions have many attributes which can modify the serialization, 
concerning validation, relevance, for example. I am still perplex about 
the pertinence of defining submissions within the model: it sounds 
declarative but it might as well be considered as an action (and the 
submit action, indeed, has no parameter except the submission id...). 
Actions are written with an XML notation and I am not, also, that much 
convinced that a script notation would be worse. Because I am now 
implementing XQuery 3.1 in Javascript for XSLTForms v2, I am thinking of 
actions being written in XQuery syntax and annotations to bind XQuery 
functions to Javascript ones. Different XML-DB implementations already 
have their own XQuery library modules for standard purposes such as file 
management.

Anyway, I am happy to see that you succeeded in implementing what you 
need and my current concern is now how new XSLTForms v1 releases might 
not disturb this...

First, you added an attribute to the action: it means you had to modify 
xsltforms.xsl for generating the corresponding Javascript object. To 
prevent this, I should better expose all action attributes in the 
Javascript part not as separate parameters but as named properties 
(without namespace prefix...) within a unique Javascript object. What do 
you think?

Of course, the load Javascript object in xsltforms.js has been 
extended... Do you have any idea about how to help you to manage this 
with next builds?

Second, you are using your own functions in expressions. Are they pure 
Javascript functions or are they added to standard XPath functions. 
Actually, in both cases, you don't have to modify xsltforms.js, is that 
correct?

Best regards,

Alain

Le 07/04/2016 23:08, Mats Eklund a écrit :
> Hi Alain,
>
> Thought I should share with you the solution I arrived at in the end 
> for the problem how best to implement downloading of instances to disk:
>
> <xf:load target=”xsltforms:download” xsltforms:filename="data.xml">
>  <xf:resource 
> value="create-object-url(serialize(instance('data')),'text/xml')"/>
> </xf:load>
>
> Regards,
> Mats
>
> ------------------------------------------------------------------------
> Date: Mon, 21 Sep 2015 09:09:13 +0000
>
> Hi Alain,
>
> Somewhat related to my previous question how best leverage HTML 5 Web 
> Workers for async processing in XForms/XsltForms, I now have a similar 
> question, this time related to how best to leverage browsers' 
> capability to allow downloading of resources client-side utilizing the 
> HTML 5 @download attribute on the <a/> element combined with the 
> URL.createObjectURL() method of the File API 
> (http://www.w3.org/TR/FileAPI/#dfn-createObjectURL), and am interested 
> to get your opinion on possible options of extending XsltForms.
>
> Obviously it is possible already now to leverage these features in 
> XsltForms via the <xf:load resource="javascript:..."/> or <xf:script/> 
> elements, but I'm thinking this functionality should rather be exposed 
> through and encapsulated in a proper XForms extension element.
>
> I was first figuring around the following options:
>
>   * <xf:download ref/value=""/> as a control element, "mirroring" the
>     <xf:upload/> control already part of the XForms specification
>   * <xf:download ref/value=""/> as an _action_ element, allowing it to
>     be used in event handlers for the <xf:trigger/> element for
>     example, similar to the <xf:load/> action element. (I'm wondering
>     why the <xf:upload/> wasn't made an action element in XForms as
>     well...?!)
>
>
> At the same time, other options also exist:
>
>   * A custom @appearance attribute on the <xf:output/> element (as in
>     Orbeon Forms:
>     http://wiki.orbeon.com/forms/doc/developer-guide/xforms-controls/output-control?pli=1#TOC-Appearance-xxforms:download)
>   * Extended behavior of the <xf:submission resource="file://"
>     method="get/put".../> element... ...
>
>
> What are your thoughts here? Which option would make most sense in 
> your view?
>
> Regards,
> Mats
>
>
>
>
> ------------------------------------------------------------------------------
>
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support

[Xsltforms-support] XSLTForms enhancements?

[Mats E. <mat...@li...>]

Hi Alain,
Just wanted to share with you, I succeeded with the following:
- Allowing XSLTForms to be run as Chrome Apps, with file save/open functionality etc.- Embedding SaxonCE library so that transform() function can run XSLT2 transforms- Adding @async attribute to xf:setvalue/xf:insert elements for non-blocking evaluation of long running XPath expressions in Web Workers- Adding validate-with-xml-schema() function, using xmllint library- Adding validate-with-schematron() function, using SaxonCE. Useful for doing more advanced form validations using SVRL.- Adding parse-xml() function, believe replacing need for xf:setnode
Would be glad to contribute these as well as some other extensions and performance optimizations.
/ Mats
 		 	   		   		 	   		   		 	   		  

Re: [Xsltforms-support] Download action/control

[Mats E. <mat...@li...>]

Hi Alain,
Thought I should share with you the solution I arrived at in the end for the problem how best to implement downloading of instances to disk:
<xf:load target=”xsltforms:download” xsltforms:filename="data.xml"> <xf:resource value="create-object-url(serialize(instance('data')),'text/xml')"/></xf:load>
Regards,Mats

Date: Mon, 21 Sep 2015 09:09:13 +0000




Hi Alain,

Somewhat related to my previous question how best leverage HTML 5 Web Workers for async processing in XForms/XsltForms, I now have a similar question, this time related to how best to leverage browsers' capability to allow downloading of resources client-side utilizing the HTML 5 @download attribute on the <a/> element combined with the URL.createObjectURL() method of the File API (http://www.w3.org/TR/FileAPI/#dfn-createObjectURL), and am interested to get your opinion on possible options of extending XsltForms. 
Obviously it is possible already now to leverage these features in XsltForms via the <xf:load resource="javascript:..."/> or <xf:script/> elements, but I'm thinking this functionality should rather be exposed through and encapsulated in a proper XForms extension element.
I was first figuring around the following options:
<xf:download ref/value=""/> as a control element, "mirroring" the <xf:upload/> control already part of the XForms specification<xf:download ref/value=""/> as an _action_ element, allowing it to be used in event handlers for the <xf:trigger/> element for example, similar to the <xf:load/> action element. (I'm wondering why the <xf:upload/> wasn't made an action element in XForms as well...?!)
At the same time, other options also exist:
A custom @appearance attribute on the <xf:output/> element (as in Orbeon Forms: http://wiki.orbeon.com/forms/doc/developer-guide/xforms-controls/output-control?pli=1#TOC-Appearance-xxforms:download)Extended behavior of the <xf:submission resource="file://" method="get/put".../> element... ... 
What are your thoughts here? Which option would make most sense in your view?
Regards,Mats

 		 	   		   		 	   		  

Re: [Xsltforms-support] A question relating to submissions: omit-xml-declaration

[<bc...@sh...>]

Hello there Alain

Thank you for replying.

"..Are you in a hurry about that??.."

No, not at all in a hurry..  I was just checking out the test suite as it
is my 'go to' when checking out usage and issues. As it was not working for
me and the test suite declares the 'omit' attribute as 'passed', I just
thought I would ask about it.

I like to have it in my documents, but it is not a major issue I suppose.

Thank you again.  I am sure many have said it and many times, but your (and
any other contributors') efforts on XSLTForms and for making it available
are [to me at least] most appreciated and invaluable.

Regards
Habs

On 29 March 2016 at 18:37, Alain Couthures <ala...@ag...>
wrote:

> Hello Habs,
>
> The omit-xml-declaration is supported in the XSLT stylesheet of XSLTForms,
> effectively memorized in the corresponding Javascript object... but ignored
> when performing the serialization...
>
> It should not be difficult to improve this situation.
>
> Are you in a hurry about that??
>
> Thanks!
>
> --Alain
>
>
> Le 29/03/2016 12:42, bc...@sh... a écrit :
>
> Dear Support, good morning
>
> Latest version of XSLTForms, Firefox
>
> re: omit-xml-declaration for submission element.
>
> This attribute does not appear to be being honoured on my setup in respect
> of including the declaration. Can someone confirm if it is or is not
> behaving correctly on their setup please ?
>
> I have an instance element with a src attribute, that loads the xml.
> The instance document being loaded has the xml declaration as the first
> line.
> If I browse to the xml instance directly, it is loaded in the browser
> showing the declaration.
>
> On submitting the instance to a Perl CGI script, which does nothing more
> than read the posted XML and store it to file and echo it back, the stored
> xml file and the returned xml has the declaration stripped.
>
> Indeed, when inspecting headers (Live HTTP Headers addon), the xml
> declaration is not present in the xml in the http body on submission. It is
> being removed by default; is this correct ?
>
> I have tried deliberately setting the omit-xml-declaration to false, to no
> avail.
>
> Thank you in advance, for your time and comments.
> Regards
> Habs
>
>
> ------------------------------------------------------------------------------
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140
>
>
>
> _______________________________________________
> Xsltforms-support mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
>
>

Re: [Xsltforms-support] A question relating to submissions: omit-xml-declaration

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

Hello Habs,

The omit-xml-declaration is supported in the XSLT stylesheet of 
XSLTForms, effectively memorized in the corresponding Javascript 
object... but ignored when performing the serialization...

It should not be difficult to improve this situation.

Are you in a hurry about that??

Thanks!

--Alain

Le 29/03/2016 12:42, bc...@sh... a écrit :
> Dear Support, good morning
>
> Latest version of XSLTForms, Firefox
>
> re: omit-xml-declaration for submission element.
>
> This attribute does not appear to be being honoured on my setup in 
> respect of including the declaration. Can someone confirm if it is or 
> is not behaving correctly on their setup please ?
>
> I have an instance element with a src attribute, that loads the xml.
> The instance document being loaded has the xml declaration as the 
> first line.
> If I browse to the xml instance directly, it is loaded in the browser 
> showing the declaration.
>
> On submitting the instance to a Perl CGI script, which does nothing 
> more than read the posted XML and store it to file and echo it back, 
> the stored xml file and the returned xml has the declaration stripped.
>
> Indeed, when inspecting headers (Live HTTP Headers addon), the xml 
> declaration is not present in the xml in the http body on submission. 
> It is being removed by default; is this correct ?
>
> I have tried deliberately setting the omit-xml-declaration to false, 
> to no avail.
>
> Thank you in advance, for your time and comments.
> Regards
> Habs
>
>
> ------------------------------------------------------------------------------
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
> http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140
>
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support

Re: [Xsltforms-support] XSLTForms and SVG-foreignObject

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

Hi MarkT,

Detailed feedback welcome!

I am very happy with SVG being supported by browsers, at last...

I would appreciate to integrate the adjustments you made into future 
versions of XSLTForms.

Generating complex SVG images from an instance with AVT is nice and, 
because of XPath 3.1 support in XSLTForms v2, this will be even more 
powerful.

Thanks!

--Alain

Le 24/03/2016 04:04, MarkT a écrit :
> Hi Alain, list,
> Tim mentioned SVG is a recent post.
> So I feel less like an alien writing about it.
> I've been exploring many options in the postgresql-ruby-forms-svg chain
> of use.
> I have been testing xsltforms within a foreignObject element within a
> svg document.
> I can get it working. Within limits.
> There are differences between the browsers as to how scripts are loaded
> and run within a foreignObject.
> There are adjustments I make to the core xsltforms.js to run in a svg
> document.
> The effort is attractive as the xforms model fits well with the
> ActiveRecord model.
> I don't use Rails, just AR.
> Then to produce an xform within an svg document can give very high
> quality presentation.
> You can imagine there are many points of hacking to make this hang
> together with xsltforms.
> Then it is for a limited version.
> Could there be some adjustments to the version 2 of xsltforms to assist
> in this path.
>
> Thanks many times for your persistence with this work Alain.
> There is chocolate waiting for you here in Sydney.
>
> All the best, MarkT
>
>
> ------------------------------------------------------------------------------
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
> http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

[Xsltforms-support] A question relating to submissions: omit-xml-declaration

[<bc...@sh...>]

Dear Support, good morning

Latest version of XSLTForms, Firefox

re: omit-xml-declaration for submission element.

This attribute does not appear to be being honoured on my setup in respect
of including the declaration. Can someone confirm if it is or is not
behaving correctly on their setup please ?

I have an instance element with a src attribute, that loads the xml.
The instance document being loaded has the xml declaration as the first
line.
If I browse to the xml instance directly, it is loaded in the browser
showing the declaration.

On submitting the instance to a Perl CGI script, which does nothing more
than read the posted XML and store it to file and echo it back, the stored
xml file and the returned xml has the declaration stripped.

Indeed, when inspecting headers (Live HTTP Headers addon), the xml
declaration is not present in the xml in the http body on submission. It is
being removed by default; is this correct ?

I have tried deliberately setting the omit-xml-declaration to false, to no
avail.

Thank you in advance, for your time and comments.
Regards
Habs

Re: [Xsltforms-support] Cumulative refresh time in IE

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

Le 24/03/2016 23:46, Tim Thompson a écrit :
> Thank you for your reply. Can Fleur be enabled simply by adding the 
> new processing instruction?For example:
>
> <?xsltforms-options 
> domengine="name=Fleur;url=../xphoneforms/stable/js/fleur.js;uri=http://www.agencexml.com/Fleur;version=1.0"?>
XSLTForms v1 can be run with Fleur as DOM engine with this option 
("stable" in xphoneforms context means "a quite old version, not 
optimized, but tested a long time ago!") or with an entry in the 
config.xsl. XSLTForms v2 will just use Fleur.

Performance counters are interesting: loading XML is currently slower 
with Fleur (upto 5 times as with Chrome native parser, not that bad for 
interpreted code, from my point of view) but faster for XForms refresh 
with every browser (divided by 1.5 approximately), even Internet Explorer!
>
> Or are there other dependencies involved?
As for xsltforms.js, I still hate dependencies! On the contrary, I could 
have to split fleur.js into multiple files according to requirements 
(obviously, the big serializer from compiled expressions back to XQuery 
source is not to be sent to browsers in standard situations...).
>
> I'm looking forward to the day when I can use XQuery and XForms 
> together in the browser!
XSLTForms v2 development is now requiring Fleur XPath engine: I have 
just written an XForms test runner (with XSLTForms v1) to read XQuery 
official test suite and execute tests with Fleur!

--Alain

Re: [Xsltforms-support] Cumulative refresh time in IE

[Tim T. <tim...@gm...>]

Thank you for your reply. Can Fleur be enabled simply by adding the new
processing instruction? For example:

<?xsltforms-options
domengine="name=Fleur;url=../xphoneforms/stable/js/fleur.js;uri=
http://www.agencexml.com/Fleur;version=1.0"?>

Or are there other dependencies involved?

I'm looking forward to the day when I can use XQuery and XForms together in
the browser!

Tim

--
Tim A. Thompson
Metadata Librarian (Spanish/Portuguese Specialty)
Princeton University Library


On Thu, Mar 24, 2016 at 4:26 PM, Alain Couthures <
ala...@ag...> wrote:

> Hi Tim,
>
> First, the Javascript engine of Internet Explorer is effectively the
> slowest one.
>
> But, XSLTForms v1 is also using the native XML engine of each browser and,
> for both Internet Explorer and Edge, it is still MSXML, which is a COM
> object. It appears that it is, again, the slowest one with DOM API,
> probably because it is not embedded in the browser itself.
>
> XSLTForms v2 is using Fleur, which is a Javascript XML engine. For loading
> big XML files, such as some XQuery test sets ;-) , in Internet Explorer,
> Fleur parser is already almost as fast as MSXML. When refreshing, because
> of MIPs and dependencies to be memorized, a lot of xsltforms-* attributes
> are added by XSLTForms v1. For XSLTForms v2, userdata property is directly
> used within Fleur Node object. I don't have yet performance reports for
> forms refresh with XSLTForms v2 and Fleur.
>
> Specifically for Internet Explorer, sorry, I have no idea for performance
> improvement which could already be applied to XSLTForms v1.
>
> --Alain
>
>
> Le 22/03/2016 20:49, Tim Thompson a écrit :
>
> Hi, Alain,
>
> A quick question. I have a very simple form whose purpose is to display an
> XML report (150KB). It can be accessed here:
>
> http://bibfram.es/basex/static/test/index.xml
>
> This is running in Tomcat7 in a BaseX web app.
>
> The XForms Cumulative Refresh Time is essentially the same in Firefox and
> Chrome: 695ms in FF and 669 in Chrome. However, in Internet Explorer, it
> skyrockets to 4471ms.
>
> Is IE really that bad, or is there something that I can do to optimize
> performance for this browser?
>
> Best regards,
> Tim
>
> --
> Tim A. Thompson
> Metadata Librarian (Spanish/Portuguese Specialty)
> Princeton University Library
>
>
>
> ------------------------------------------------------------------------------
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
>
>
>
> _______________________________________________
> Xsltforms-support mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
>
>

Re: [Xsltforms-support] Cumulative refresh time in IE

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

Hi Tim,

First, the Javascript engine of Internet Explorer is effectively the 
slowest one.

But, XSLTForms v1 is also using the native XML engine of each browser 
and, for both Internet Explorer and Edge, it is still MSXML, which is a 
COM object. It appears that it is, again, the slowest one with DOM API, 
probably because it is not embedded in the browser itself.

XSLTForms v2 is using Fleur, which is a Javascript XML engine. For 
loading big XML files, such as some XQuery test sets ;-) , in Internet 
Explorer, Fleur parser is already almost as fast as MSXML. When 
refreshing, because of MIPs and dependencies to be memorized, a lot of 
xsltforms-* attributes are added by XSLTForms v1. For XSLTForms v2, 
userdata property is directly used within Fleur Node object. I don't 
have yet performance reports for forms refresh with XSLTForms v2 and Fleur.

Specifically for Internet Explorer, sorry, I have no idea for 
performance improvement which could already be applied to XSLTForms v1.

--Alain

Le 22/03/2016 20:49, Tim Thompson a écrit :
> Hi, Alain,
>
> A quick question. I have a very simple form whose purpose is to 
> display an XML report (150KB). It can be accessed here:
>
> http://bibfram.es/basex/static/test/index.xml
>
> This is running in Tomcat7 in a BaseX web app.
>
> The XForms Cumulative Refresh Time is essentially the same in Firefox 
> and Chrome: 695ms in FF and 669 in Chrome. However, in Internet 
> Explorer, it skyrockets to 4471ms.
>
> Is IE really that bad, or is there something that I can do to optimize 
> performance for this browser?
>
> Best regards,
> Tim
>
> --
> Tim A. Thompson
> Metadata Librarian (Spanish/Portuguese Specialty)
> Princeton University Library
>
>
>
> ------------------------------------------------------------------------------
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
> http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
>
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support

Re: [Xsltforms-support] XSLTForms and SVG-foreignObject

[MarkT <par...@gm...>]

Hi Alain, list,
Tim mentioned SVG is a recent post.
So I feel less like an alien writing about it.
I've been exploring many options in the postgresql-ruby-forms-svg chain
of use.
I have been testing xsltforms within a foreignObject element within a
svg document.
I can get it working. Within limits.
There are differences between the browsers as to how scripts are loaded
and run within a foreignObject.
There are adjustments I make to the core xsltforms.js to run in a svg
document.
The effort is attractive as the xforms model fits well with the
ActiveRecord model.
I don't use Rails, just AR.
Then to produce an xform within an svg document can give very high
quality presentation.
You can imagine there are many points of hacking to make this hang
together with xsltforms.
Then it is for a limited version.
Could there be some adjustments to the version 2 of xsltforms to assist
in this path.

Thanks many times for your persistence with this work Alain.
There is chocolate waiting for you here in Sydney.

All the best, MarkT

[Xsltforms-support] Cumulative refresh time in IE

[Tim T. <tim...@gm...>]

Hi, Alain,

A quick question. I have a very simple form whose purpose is to display an
XML report (150KB). It can be accessed here:

http://bibfram.es/basex/static/test/index.xml

This is running in Tomcat7 in a BaseX web app.

The XForms Cumulative Refresh Time is essentially the same in Firefox and
Chrome: 695ms in FF and 669 in Chrome. However, in Internet Explorer, it
skyrockets to 4471ms.

Is IE really that bad, or is there something that I can do to optimize
performance for this browser?

Best regards,
Tim

--
Tim A. Thompson
Metadata Librarian (Spanish/Portuguese Specialty)
Princeton University Library

Re: [Xsltforms-support] Dialog vertical position problems on the last revisions

[Ioan F. <mi...@gm...>]

Hi Alain, back to this topic!

I discovered a disturbing situation when is opened a second modal dialog 
over one already open.

The problem arises only in the case of long lists in a page, with scroll 
vertically. The first dialog is positioned correctly over the center 
visible area of the page, but on show or hide the child modal dialog, 
the whole content "flees" on top, instead of staying on the position of 
the parent.

In code, the problem seems to be in xsltforms.js, 
XsltForms_browser.dialog function, approximately at line 2600 in the 
last revision (631).

What solution we could find?

Thanks for any hint to how we could do.

Ioan




On 06/07/2014 07:34 AM, Alain Couthures wrote:
> Hi Ioan,
>
> I have now changed to the old version in the latest build. It will 
> stay as this as long as I haven't yet found a good way to support 
> dialogs popup from an IFRAME...
>
> Thanks!
>
> --Alain
>
> Le 07/05/2014 14:50, Ioan Fericel a écrit :
>> Hi Alain,
>>
>> I find a solution for this problem, but not sure that is generally
>> valid. In xsltforms.js, at line 232 in latest revision (595):
>>> myHeight = document.body ? document.body.clientHeight :
>>> document.documentElement.clientHeight;
>> I changed to the old version:
>>> myHeight = document.documentElement.clientHeight;
>> Now modal dialog is centered correctly in visible area, both in Firefox
>> and Chrome. Is it possible to affect other parts or could be changed in
>> the next version to work correctly also in this case?
>>
>> Merci et bonne journée,
>> Ioan
>>
>

Re: [Xsltforms-support] java applet in XSLTForms

[Habs <ha...@us...>]

Hi Alain

I have used local HTTP servers too, on the odd occasion.
You have given me some other ideas too re: NodeJS.

The scenario I had in mind was a facility for kind of temporary
briefcase type store for XML document produced/downloaded, should
access to the remote server from where the XSLTForm was loaded be a
problem, or the network is down and so forth.

I think an extremely light-weight local server is possibly the way to
go, but I have always, rightly or wrongly, understood that a document
could only be written back to the server from where it was loaded. Of
course in the above scenario, it is more like a document would be read
from the remote server and written/stored locally until it was possible
to push it back to the server. I just wondered if a simple and
competent solution was in use my many people already. There are other
ways to get around this issue, so I think I will play around. It seems
like it perhaps is a different function to address with other tools, 
rather than trying to do it via XSLTForms.

Regarding the Java Applet, I was actually wondering out of interest,
when the Applet code would be removed from XSLTForms altogether as a
clean up matter more than anything.

I am a regular, but not an expert, user of XSLTForms, so I am not
familiar with everything it can do.

I have found it a very, very useful provision over the time and I am
grateful for all the work that has gone in to it and it being available.

Thank you.
Habs


On Thu, 10 Mar 2016 07:59:43 +0100
Alain Couthures <ala...@ag...> wrote:

> Hello Habs,
> 
> Recent browsers now support FileReader API so the XSLTForms Java
> applet is useless for reading files.
> 
> Writing files is unfortunately not yet implemented in browsers. As
> you said, Java applets won't work in Chrome anyway...
> 
> I personally use local HTTP servers for saving files and NodeJS is
> very nice for writing a small REST one, for example.
> 
> What do you need?
> 
> Thanks!
> 
> --Alain
> 
> Le 09/03/2016 12:33, Habs a écrit :
> > Good day to all :-)
> >
> > Having been through a head-scratching month regarding flash plugin
> > issues on various browsers (in GNU/Linux), it seems that NPAPI is
> > 'dead'....and therefore so will be flash, silverlight and....java
> > applets.
> >
> > With regard to Java applets and XSLTForms, I'm just checking when/if
> > the applet functionality will be removed (it would make sense?) and
> > what alternative ideas for local saving and loading people use
> > currently or will use (if at all) ?
> >
> > Regards
> > Habs
> >
> >
> > ------------------------------------------------------------------------------
> > Transform Data into Opportunity.
> > Accelerate data analysis in your applications with
> > Intel Data Analytics Acceleration Library.
> > Click to learn more.
> > http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
> > _______________________________________________
> > Xsltforms-support mailing list
> > Xsl...@li...
> > https://lists.sourceforge.net/lists/listinfo/xsltforms-support
> >  
> 

Re: [Xsltforms-support] java applet in XSLTForms

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

Hello Habs,

Recent browsers now support FileReader API so the XSLTForms Java applet 
is useless for reading files.

Writing files is unfortunately not yet implemented in browsers. As you 
said, Java applets won't work in Chrome anyway...

I personally use local HTTP servers for saving files and NodeJS is very 
nice for writing a small REST one, for example.

What do you need?

Thanks!

--Alain

Le 09/03/2016 12:33, Habs a écrit :
> Good day to all :-)
>
> Having been through a head-scratching month regarding flash plugin
> issues on various browsers (in GNU/Linux), it seems that NPAPI is
> 'dead'....and therefore so will be flash, silverlight and....java
> applets.
>
> With regard to Java applets and XSLTForms, I'm just checking when/if
> the applet functionality will be removed (it would make sense?) and
> what alternative ideas for local saving and loading people use
> currently or will use (if at all) ?
>
> Regards
> Habs
>
>
> ------------------------------------------------------------------------------
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
> http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

[Xsltforms-support] java applet in XSLTForms

[Habs <ha...@us...>]

Good day to all :-)

Having been through a head-scratching month regarding flash plugin
issues on various browsers (in GNU/Linux), it seems that NPAPI is
'dead'....and therefore so will be flash, silverlight and....java
applets.

With regard to Java applets and XSLTForms, I'm just checking when/if
the applet functionality will be removed (it would make sense?) and
what alternative ideas for local saving and loading people use
currently or will use (if at all) ?

Regards
Habs

Re: [Xsltforms-support] UI Events in XSLTForms

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

Tim,

Ignoring UIEvent was first added in XSLTForms because it happened that, 
with Google Chrome only, submissions were activated twice while just 
pressing once the corresponding trigger.

Since this workaround, Google Chrome has been updated and I have not 
reproduce this issue anymore. So, in the next commit, UIEvent will be 
treated as any Event allowing the Open Street Map demo to work as 
previously. We will see if users might complain again about submissions.

Best regards,

Alain

Le 20/02/2016 21:07, Tim Thompson a écrit :
> Hi, Alain,
>
> There still seems to be an issue with UI events in the latest 
> revision. I opened an issue on GitHub[1].
>
> Best regards,
> Tim
>
> [1] https://github.com/AlainCouthures/xsltforms/issues/15
>
> --
> Tim A. Thompson
> Metadata Librarian (Spanish/Portuguese Specialty)
> Princeton University Library
>
>
> On Sun, Dec 6, 2015 at 9:56 PM, Tim Thompson <tim...@gm... 
> <mailto:tim...@gm...>> wrote:
>
>     Alain,
>
>     I was working through Steven Pemberton's excellent OpenStreetMap
>     XForms example[1] from XML Amsterdam, and I noticed that it does
>     not work in the latest version of XSLTForms (his demo is using
>     XSLTForms RC1.0).
>
>     A small change introduced in rev. 620 appears to be the problem:
>     https://github.com/AlainCouthures/xsltforms/blob/972a712e47fb952255c25e15d437255aaa58b31a/src/js/xmlevtmngt/Listener.js.xml#L102
>
>     Removing "&& !(event instanceof UIEvent)" allows the mouse events
>     to be registered again. Is it safe to remove this condition?
>
>     Best regards,
>     Tim
>
>     [1] http://homepages.cwi.nl/~steven/Talks/2015/11-05-example/
>     <http://homepages.cwi.nl/%7Esteven/Talks/2015/11-05-example/>
>
>     --
>     Tim A. Thompson
>     Metadata Librarian (Spanish/Portuguese Specialty)
>     Princeton University Library
>
>

Re: [Xsltforms-support] Javascript URIs in XSLTForms

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

Hi Tim,

This exception is due to Javascript strict mode detecting an undeclared 
variable. In previous commits, an undeclared variable was automatically 
created when assigning a value to it.

The missing declaration will be added in the next commit. It is already 
possible for you to remove "use strict"; at the very beginning of 
xsltforms.js

Thank you for your feedback!

--Alain

Le 24/02/2016 19:27, Tim Thompson a écrit :
> Hi, Alain,
>
> I tried to use Javascript URIs recently (in <xf:load 
> resource="javascript: .."/>), but this feature seems to be broken in 
> the latest versions of XSLTForms. I had to revert to rev. 625 for it 
> to work.
>
> In rev. 631, I get an XSLTForms exception:
>
> XSLTForms Exception
> --------------------------
>
> Error evaluating the following Javascript expression :
>
> if (!(typeof d3.selectAll('g.node') == 'undefined')) { 
> d3.selectAll('g.node').remove(); d3.selectAll('line.link').remove(); } 
> { queueD3js('resources/data/nodes4.csv', 'resources/data/edges4.csv')}
>
> ReferenceError: assignment to undeclared variable XsltForms_context
>
> What do you think?
>
> Tim
>
> --
> Tim A. Thompson
> Metadata Librarian (Spanish/Portuguese Specialty)
> Princeton University Library
>

[Xsltforms-support] Javascript URIs in XSLTForms

[Tim T. <tim...@gm...>]

Hi, Alain,

I tried to use Javascript URIs recently (in <xf:load resource="javascript:
.."/>), but this feature seems to be broken in the latest versions of
XSLTForms. I had to revert to rev. 625 for it to work.

In rev. 631, I get an XSLTForms exception:

XSLTForms Exception
--------------------------

Error evaluating the following Javascript expression :

if (!(typeof d3.selectAll('g.node') == 'undefined')) {
d3.selectAll('g.node').remove(); d3.selectAll('line.link').remove(); } {
queueD3js('resources/data/nodes4.csv', 'resources/data/edges4.csv')}

ReferenceError: assignment to undeclared variable XsltForms_context

What do you think?

Tim

--
Tim A. Thompson
Metadata Librarian (Spanish/Portuguese Specialty)
Princeton University Library
<ta...@pr...>

Re: [Xsltforms-support] UI Events in XSLTForms

[Tim T. <tim...@gm...>]

Hi, Alain,

There still seems to be an issue with UI events in the latest revision. I
opened an issue on GitHub[1].

Best regards,
Tim

[1] https://github.com/AlainCouthures/xsltforms/issues/15

--
Tim A. Thompson
Metadata Librarian (Spanish/Portuguese Specialty)
Princeton University Library
<ta...@pr...>

On Sun, Dec 6, 2015 at 9:56 PM, Tim Thompson <tim...@gm...> wrote:

> Alain,
>
> I was working through Steven Pemberton's excellent OpenStreetMap XForms
> example[1] from XML Amsterdam, and I noticed that it does not work in the
> latest version of XSLTForms (his demo is using XSLTForms RC1.0).
>
> A small change introduced in rev. 620 appears to be the problem:
> https://github.com/AlainCouthures/xsltforms/blob/972a712e47fb952255c25e15d437255aaa58b31a/src/js/xmlevtmngt/Listener.js.xml#L102
>
> Removing "&& !(event instanceof UIEvent)" allows the mouse events to be
> registered again. Is it safe to remove this condition?
>
> Best regards,
> Tim
>
> [1] http://homepages.cwi.nl/~steven/Talks/2015/11-05-example/
>
> --
> Tim A. Thompson
> Metadata Librarian (Spanish/Portuguese Specialty)
> Princeton University Library
>

Re: [Xsltforms-support] XSLTForms and SVG

[Tim T. <tim...@gm...>]

Thanks, Alain. That seems to work for me too, cross-browser.

Regards,
Tim

--
Tim A. Thompson
Metadata Librarian (Spanish/Portuguese Specialty)
Princeton University Library
<ta...@pr...>

On Mon, Jan 25, 2016 at 1:54 PM, Alain Couthures <
ala...@ag...> wrote:

> Tim,
>
> This is a tricky issue because everything sounds OK from the debugger
> point of view.
>
> Happily, changing the identity template for attributes just into
> "<xsl:copy/>" instead of "<xsl:attribute..." appears to be working for this
> testcase.
>
> Thank you for your feedback!
>
> Alain
>
>
> Le 25/01/2016 04:53, Tim Thompson a écrit :
>
> Using your patch for xsltforms.xsl, I'm running into another SVG issue. I
> have a graphic that includes a rectangle with a gradient scale. The <rect>
> element has a @style attribute with a relative reference to the
> <linearGradient> element where the gradient is defined. It looks like this:
>
> <rect
> style="fill:url(#linearGradient5615);fill-opacity:1;stroke:#000000;stroke-width:1.00722218;stroke-opacity:1"
> id="rect5607" width="289.07648" height="39.794155" x="801.64746"
> y="649.0152" />
>
> When I try to load the image in a page with XSLTForms, the gradient does
> not render. However, if I revert to the old version of the xsltforms.xsl
> identity template, it does render. Any idea why the relative URL reference
> in the SVG is not working? This seems to be the case for both Chrome and
> Firefox.
>
> You can see the issue here: <http://timathom.github.io/florentine.xhtml>
> http://timathom.github.io/florentine.xhtml
>
> And the original image, with properly rendered gradient, here:
> http://timathom.github.io/img/florentine.svg
>
> Thanks again!
> Tim
>
> --
> Tim A. Thompson
> Metadata Librarian (Spanish/Portuguese Specialty)
> Princeton University Library
>
>
> On Tue, Jan 19, 2016 at 1:08 PM, Alain Couthures <
> <ala...@ag...>ala...@ag...> wrote:
>
>> Tim,
>>
>> Thank you for pointing at this issue!
>>
>> XSLTForms stylesheet has to deal with namespaces: the best approach for
>> browsers appears to deliver no namespace for HTML. Using <xsl:copy> is not
>> a good solution and using <xsl:element> and <xsl:attribute> allows to
>> remove the XHTML namespace.
>>
>> BTW, with the previous template, Saxon was complaining that attributes
>> cannot have attributes...
>>
>> So, I prefer improve the current templates with non-HTML namespaces
>> support, such as SVG, at least for elements:
>>
>> <xsl:template match="*" priority="-2" xmlns:xhtml=
>> "http://www.w3.org/1999/xhtml" <http://www.w3.org/1999/xhtml> xmlns:xsl=
>> "http://www.w3.org/1999/XSL/Transform"
>> <http://www.w3.org/1999/XSL/Transform>>
>>     <xsl:param name="appearance" select="@appearance"/>
>>     <xsl:param name="parentworkid"/>
>>     <xsl:param name="workid"
>> select="concat(position(),'_',$parentworkid)"/>
>>     <xsl:choose>
>>         <xsl:when test="namespace-uri() != '' and namespace-uri() != '
>> http://www.w3.org/1999/xhtml'">
>>             <xsl:element name="{local-name()}"
>> namespace="{namespace-uri()}">
>>                 <xsl:apply-templates select="@*"/>
>>                 <xsl:apply-templates select="node()">
>>                     <xsl:with-param name="parentworkid" select="$workid"/>
>>                     <xsl:with-param name="appearance"
>> select="$appearance"/>
>>                 </xsl:apply-templates>
>>             </xsl:element>
>>         </xsl:when>
>>         <xsl:otherwise>
>>             <xsl:element name="{local-name()}">
>>                 <xsl:apply-templates select="@*"/>
>>                 <xsl:apply-templates select="node()">
>>                     <xsl:with-param name="parentworkid" select="$workid"/>
>>                     <xsl:with-param name="appearance"
>> select="$appearance"/>
>>                 </xsl:apply-templates>
>>             </xsl:element>
>>         </xsl:otherwise>
>>     </xsl:choose>
>> </xsl:template>
>>
>> I have successfully tested this with Firefox (Firefox is not anymore my
>> default browser because of too many conformance, performance and freeze
>> issues...).
>>
>> Thank you for your feedback!
>>
>> --Alain
>>
>>
>> Le 19/01/2016 14:11, Tim Thompson a écrit :
>>
>> Alain,
>>
>> I am hoping to do some work with XForms and SVG and have been looking at
>> the current XSLTForms SVG examples. I noticed that, since rev. 595 of
>> XSLTForms, none of the SVG examples work in Firefox. The reason seems to be
>> the changes made to the fallback identity template in xsltforms.xsl.
>>
>> In the latest revision, if lines 1203-1228[1] are reverted back to the
>> template used prior to rev. 595, then the SVG examples will work in Firefox:
>>
>> <xsl:template xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>> match="node()|@*" priority="-2">
>>     <xsl:param name="appearance" select="@appearance"/>
>>     <xsl:param name="parentworkid"/>
>>     <xsl:param name="workid"
>> select="concat(position(),'_',$parentworkid)"/>
>>     <xsl:copy>
>>         <xsl:apply-templates select="@*"/>
>>         <xsl:apply-templates select="node()">
>>             <xsl:with-param name="parentworkid" select="$workid"/>
>>             <xsl:with-param name="appearance" select="$appearance"/>
>>         </xsl:apply-templates>
>>     </xsl:copy>
>> </xsl:template>
>>
>> Is there a reason not to use this more generic template? I tested on a
>> range of browsers and did not notice any immediate issues.
>>
>> Thanks again!
>> Tim
>>
>> [1]
>> <https://github.com/AlainCouthures/xsltforms/blob/master/build/xsltforms.xsl#L1203>
>> https://github.com/AlainCouthures/xsltforms/blob/master/build/xsltforms.xsl#L1203
>>
>>
>> --
>> Tim A. Thompson
>> Metadata Librarian (Spanish/Portuguese Specialty)
>> Princeton University Library
>>
>>
>>
>
>

Re: [Xsltforms-support] XSLTForms and SVG

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

Tim,

This is a tricky issue because everything sounds OK from the debugger 
point of view.

Happily, changing the identity template for attributes just into 
"<xsl:copy/>" instead of "<xsl:attribute..." appears to be working for 
this testcase.

Thank you for your feedback!

Alain

Le 25/01/2016 04:53, Tim Thompson a écrit :
> Using your patch for xsltforms.xsl, I'm running into another SVG 
> issue. I have a graphic that includes a rectangle with a gradient 
> scale. The <rect> element has a @style attribute with a relative 
> reference to the <linearGradient> element where the gradient is 
> defined. It looks like this:
>
> <rect 
> style="fill:url(#linearGradient5615);fill-opacity:1;stroke:#000000;stroke-width:1.00722218;stroke-opacity:1" 
> id="rect5607" width="289.07648" height="39.794155" x="801.64746" 
> y="649.0152" />
>
> When I try to load the image in a page with XSLTForms, the gradient 
> does not render. However, if I revert to the old version of the 
> xsltforms.xsl identity template, it does render. Any idea why the 
> relative URL reference in the SVG is not working? This seems to be the 
> case for both Chrome and Firefox.
>
> You can see the issue here: http://timathom.github.io/florentine.xhtml
>
> And the original image, with properly rendered gradient, here: 
> http://timathom.github.io/img/florentine.svg
>
> Thanks again!
> Tim
>
> --
> Tim A. Thompson
> Metadata Librarian (Spanish/Portuguese Specialty)
> Princeton University Library
>
>
> On Tue, Jan 19, 2016 at 1:08 PM, Alain Couthures 
> <ala...@ag... <mailto:ala...@ag...>> 
> wrote:
>
>     Tim,
>
>     Thank you for pointing at this issue!
>
>     XSLTForms stylesheet has to deal with namespaces: the best
>     approach for browsers appears to deliver no namespace for HTML.
>     Using <xsl:copy> is not a good solution and using <xsl:element>
>     and <xsl:attribute> allows to remove the XHTML namespace.
>
>     BTW, with the previous template, Saxon was complaining that
>     attributes cannot have attributes...
>
>     So, I prefer improve the current templates with non-HTML
>     namespaces support, such as SVG, at least for elements:
>
>     <xsl:template match="*" priority="-2"
>     xmlns:xhtml="http://www.w3.org/1999/xhtml"
>     <http://www.w3.org/1999/xhtml>
>     xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>     <http://www.w3.org/1999/XSL/Transform>>
>         <xsl:param name="appearance" select="@appearance"/>
>         <xsl:param name="parentworkid"/>
>         <xsl:param name="workid"
>     select="concat(position(),'_',$parentworkid)"/>
>         <xsl:choose>
>             <xsl:when test="namespace-uri() != '' and namespace-uri()
>     != 'http://www.w3.org/1999/xhtml'">
>                 <xsl:element name="{local-name()}"
>     namespace="{namespace-uri()}">
>                     <xsl:apply-templates select="@*"/>
>                     <xsl:apply-templates select="node()">
>                         <xsl:with-param name="parentworkid"
>     select="$workid"/>
>                         <xsl:with-param name="appearance"
>     select="$appearance"/>
>                     </xsl:apply-templates>
>                 </xsl:element>
>             </xsl:when>
>             <xsl:otherwise>
>                 <xsl:element name="{local-name()}">
>                     <xsl:apply-templates select="@*"/>
>                     <xsl:apply-templates select="node()">
>                         <xsl:with-param name="parentworkid"
>     select="$workid"/>
>                         <xsl:with-param name="appearance"
>     select="$appearance"/>
>                     </xsl:apply-templates>
>                 </xsl:element>
>             </xsl:otherwise>
>         </xsl:choose>
>     </xsl:template>
>
>     I have successfully tested this with Firefox (Firefox is not
>     anymore my default browser because of too many conformance,
>     performance and freeze issues...).
>
>     Thank you for your feedback!
>
>     --Alain
>
>
>     Le 19/01/2016 14:11, Tim Thompson a écrit :
>>     Alain,
>>
>>     I am hoping to do some work with XForms and SVG and have been
>>     looking at the current XSLTForms SVG examples. I noticed that,
>>     since rev. 595 of XSLTForms, none of the SVG examples work in
>>     Firefox. The reason seems to be the changes made to the fallback
>>     identity template in xsltforms.xsl.
>>
>>     In the latest revision, if lines 1203-1228[1] are reverted back
>>     to the template used prior to rev. 595, then the SVG examples
>>     will work in Firefox:
>>
>>     <xsl:template xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>>     match="node()|@*" priority="-2">
>>         <xsl:param name="appearance" select="@appearance"/>
>>         <xsl:param name="parentworkid"/>
>>         <xsl:param name="workid"
>>     select="concat(position(),'_',$parentworkid)"/>
>>         <xsl:copy>
>>             <xsl:apply-templates select="@*"/>
>>             <xsl:apply-templates select="node()">
>>                 <xsl:with-param name="parentworkid" select="$workid"/>
>>                 <xsl:with-param name="appearance" select="$appearance"/>
>>             </xsl:apply-templates>
>>         </xsl:copy>
>>     </xsl:template>
>>
>>     Is there a reason not to use this more generic template? I tested
>>     on a range of browsers and did not notice any immediate issues.
>>
>>     Thanks again!
>>     Tim
>>
>>     [1]
>>     https://github.com/AlainCouthures/xsltforms/blob/master/build/xsltforms.xsl#L1203
>>
>>
>>     --
>>     Tim A. Thompson
>>     Metadata Librarian (Spanish/Portuguese Specialty)
>>     Princeton University Library
>>
>
>

Re: [Xsltforms-support] XSLTForms and SVG

[Tim T. <tim...@gm...>]

Using your patch for xsltforms.xsl, I'm running into another SVG issue. I
have a graphic that includes a rectangle with a gradient scale. The <rect>
element has a @style attribute with a relative reference to the
<linearGradient> element where the gradient is defined. It looks like this:

<rect
style="fill:url(#linearGradient5615);fill-opacity:1;stroke:#000000;stroke-width:1.00722218;stroke-opacity:1"
id="rect5607" width="289.07648" height="39.794155" x="801.64746"
y="649.0152" />

When I try to load the image in a page with XSLTForms, the gradient does
not render. However, if I revert to the old version of the xsltforms.xsl
identity template, it does render. Any idea why the relative URL reference
in the SVG is not working? This seems to be the case for both Chrome and
Firefox.

You can see the issue here: http://timathom.github.io/florentine.xhtml

And the original image, with properly rendered gradient, here:
http://timathom.github.io/img/florentine.svg

Thanks again!
Tim

--
Tim A. Thompson
Metadata Librarian (Spanish/Portuguese Specialty)
Princeton University Library


On Tue, Jan 19, 2016 at 1:08 PM, Alain Couthures <
ala...@ag...> wrote:

> Tim,
>
> Thank you for pointing at this issue!
>
> XSLTForms stylesheet has to deal with namespaces: the best approach for
> browsers appears to deliver no namespace for HTML. Using <xsl:copy> is not
> a good solution and using <xsl:element> and <xsl:attribute> allows to
> remove the XHTML namespace.
>
> BTW, with the previous template, Saxon was complaining that attributes
> cannot have attributes...
>
> So, I prefer improve the current templates with non-HTML namespaces
> support, such as SVG, at least for elements:
>
> <xsl:template match="*" priority="-2" xmlns:xhtml=
> "http://www.w3.org/1999/xhtml" <http://www.w3.org/1999/xhtml> xmlns:xsl=
> "http://www.w3.org/1999/XSL/Transform"
> <http://www.w3.org/1999/XSL/Transform>>
>     <xsl:param name="appearance" select="@appearance"/>
>     <xsl:param name="parentworkid"/>
>     <xsl:param name="workid"
> select="concat(position(),'_',$parentworkid)"/>
>     <xsl:choose>
>         <xsl:when test="namespace-uri() != '' and namespace-uri() != '
> http://www.w3.org/1999/xhtml'">
>             <xsl:element name="{local-name()}"
> namespace="{namespace-uri()}">
>                 <xsl:apply-templates select="@*"/>
>                 <xsl:apply-templates select="node()">
>                     <xsl:with-param name="parentworkid" select="$workid"/>
>                     <xsl:with-param name="appearance"
> select="$appearance"/>
>                 </xsl:apply-templates>
>             </xsl:element>
>         </xsl:when>
>         <xsl:otherwise>
>             <xsl:element name="{local-name()}">
>                 <xsl:apply-templates select="@*"/>
>                 <xsl:apply-templates select="node()">
>                     <xsl:with-param name="parentworkid" select="$workid"/>
>                     <xsl:with-param name="appearance"
> select="$appearance"/>
>                 </xsl:apply-templates>
>             </xsl:element>
>         </xsl:otherwise>
>     </xsl:choose>
> </xsl:template>
>
> I have successfully tested this with Firefox (Firefox is not anymore my
> default browser because of too many conformance, performance and freeze
> issues...).
>
> Thank you for your feedback!
>
> --Alain
>
>
> Le 19/01/2016 14:11, Tim Thompson a écrit :
>
> Alain,
>
> I am hoping to do some work with XForms and SVG and have been looking at
> the current XSLTForms SVG examples. I noticed that, since rev. 595 of
> XSLTForms, none of the SVG examples work in Firefox. The reason seems to be
> the changes made to the fallback identity template in xsltforms.xsl.
>
> In the latest revision, if lines 1203-1228[1] are reverted back to the
> template used prior to rev. 595, then the SVG examples will work in Firefox:
>
> <xsl:template xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
> match="node()|@*" priority="-2">
>     <xsl:param name="appearance" select="@appearance"/>
>     <xsl:param name="parentworkid"/>
>     <xsl:param name="workid"
> select="concat(position(),'_',$parentworkid)"/>
>     <xsl:copy>
>         <xsl:apply-templates select="@*"/>
>         <xsl:apply-templates select="node()">
>             <xsl:with-param name="parentworkid" select="$workid"/>
>             <xsl:with-param name="appearance" select="$appearance"/>
>         </xsl:apply-templates>
>     </xsl:copy>
> </xsl:template>
>
> Is there a reason not to use this more generic template? I tested on a
> range of browsers and did not notice any immediate issues.
>
> Thanks again!
> Tim
>
> [1]
> https://github.com/AlainCouthures/xsltforms/blob/master/build/xsltforms.xsl#L1203
>
>
> --
> Tim A. Thompson
> Metadata Librarian (Spanish/Portuguese Specialty)
> Princeton University Library
>
>
>

Re: [Xsltforms-support] Using transform()

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

Hi Mark,

With XSLT 1.0, only a string can be passed as argument to a stylesheet. 
The document() function cannot be used to get an XForms instance either.

Building a specific instance for embedding all required data before 
applying the stylesheet to it might do the trick. I have created an 
action named "setnode" just to load serialized XML for one node with 
inner/outer option. What do you think?

Best regards
Alain

Le 19/01/2016 12:58, Mark Seaborne a écrit :
> Hi,
>
> I am experimenting with using the transform() function and would like 
> to pass an XML instance into a stylesheet as a parameter value. Using 
> something along the lines of
>
> transform(instance(‘myInstance'), 'xslt/test.xsl',false, 'theTestXML', 
> instance(’newCodes’))
>
>
>
> I can access the instance within my stylesheet as a string, but not as 
> a nodeset. Is it possible to do this?
>
> Best wishes
> Mark
>
>
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
>
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support

Re: [Xsltforms-support] Another XSLT question

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

Hi Mark,

It is possible using the serialize(node) function.

Thank you for your feedback!

Alain

Le 21/01/2016 13:14, Mark Seaborne a écrit :
> Hi Again,
>
> In the documentation 
> at https://en.wikibooks.org/wiki/XSLTForms/The_transform_function it 
> makes clear that the transform() function takes either the URI of an 
> external XSLT stylesheet, or XSLT as a string.
>
> I just wondered if the stylesheet can also be a node, like the XML to 
> be transformed?
>
> Best wishes
> Mark
>
>
>
>
>
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
>
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support