Alain and other list members
After examining the profiler I see that the main time is taken with the following:
instance('report-transformed')/body/table/tr[not(td[3] = preceding-sibling::tr/td[3]) and not(td[3]='')]
This is my way of populating a second select box with unique values from an xhtml file that is loaded into my form, and I suspect (but don't know) that changing the selected value in my first select box is triggering a refresh of the whole form. Is this the case? Can it be prevented so that it only happens when I make a submission on the changed select box value?
Cheers
Peter
-----Original Message-----
From: [email protected]
Sent: Wed, 13 Mar 2013 22:08:11 +0100
To: [email protected]
Subject: Re: [Xsltforms-support] Select1 box: What is the reason for the delay?Yes, currently, there is no optimization for // in XSLTForms.
It means that each and every nodes in the subtree are tested.
Using the id() function, when possible, can be very useful too.
-Alain
Le 13/03/2013 22:02, peter winstanley a écrit :Hello Alain
Thanks you for our kind suggestions.... so is // much more computationally intensive than using the full path in an XPath _expression_?
Regards
Peter
Free 3D Marine Aquarium Screensaver
------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________ Xsltforms-support mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xsltforms-support
