Re: [Xsltforms-support] quicker rendering

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

Hello Steve,

Which version of Saxon are you using? The node-set() function calls are 
always to be customized for each XSLT engine and Saxon changed its own 
approach last year, as far as I remember...

I would be happy to get effective time measures for the transformation step.

On Windows, I'm using Powershell which is based on .Net 2.0 by default. 
I could send you a script file for testing if you wish.

At browser side, it's difficult to measure something. Maybe native 
profilers might give an indication for XSLT step, especially if the 
generated page is not automatically inserting and calling Javascript 
instructions. With XSLTForms Profiler, you will get measures for the 
HTML and the Javascript part loadings. XSLTForms is adding a lot of HTML 
elements, "just in case" a group could become irrelevant for example.

Yes, the way ids are added is clearly not optimized, I think that using 
xsl:number could be interesting for that purpose, but I'm still not 
convinced that it is costing a lot. Adding yourself every possible ids 
might be a workaround.

Changing the place where the generated script elements are is also easy 
to modify in the XSLT stylesheet.

Could you please send me one of your huge forms?

Thanks!

-Alain

Le 09/02/2012 10:19, Stephen Cameron a écrit :
> Hello All,
>
> I have a large xform and its going to get bigger, the time to 
> transform the xform and render it is now quite significant and getting 
> to the point where it is an issue, given that people don't see 
> anything happening throughout the process.
>
> One option is to pre-transform the xml 'form' into an html 'page', 
> which I used to do successfully but now cannot using Saxon, it complains.
>
> But my questions actually relate to browser transformation:
>
> 1. If I give all of the xform controls an explicit ID, rather than the 
> xsltforms.xsl stylesheet having to calculate them, does this speed up 
> the transformation significantly?
>
> 2. Is it possible perhaps to change the way that the transform occurs 
> such that the html markup is generated first and then the Xform 
> related javascript second. In theory the browser should start 
> rendering the page before the parsing of the Javascript section is 
> completed. I'm imagining this as a two-pass process in the xsltforms 
> stylesheet.
>
> I have to say that once the rendering is completed the performance of 
> the form itself is excellent, despite its growing complexity. I assume 
> this is due to the presence of a true dependency graph in the newer 
> versions of XSLTForms. :)
>
> Thanks for your insights.
>
> Steve Cameron
>
>
>
>
>
> ------------------------------------------------------------------------------
> Virtualization&  Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
>
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support