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