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 ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/xsltforms-support
