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...://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
>
>