Thanks for replying, Santosh.
The issue is - The 'precompiled' version seems ok with 'static' forms,
however long. But we have forms with varying numbers of (nested) repeats in
the data set, and the compiled version did not seem to adjust for it, as
might be expected. Perhaps I am missing something.
*--*
Best Regards,*
*
* Bala Krishnamurthy*
On Sun, Nov 27, 2011 at 9:09 AM, Santosh Chandak
<[email protected]>wrote:
> Hello Bala,
>
> You don't really need to apply the xsltforms transform at runtime. You can
> transform the form beforehand to HTML result and directly use it, that way
> your application will not spend any time in transformation and will be much
> faster.
>
> Regards,
> Santosh
>
>
> On Sat, Nov 26, 2011 at 7:31 PM, Bala Krishnamurthy <[email protected]>wrote:
>
>> I got it to work. I played around with path settings for the js and css
>> includes in the xsltforms.xsl as well as my own xforms
>>
>> But the performance seems the same though, with PHP doing the xsl
>> transform on the server.
>>
>> *--*
>> Best Regards,*
>> *
>> * Bala Krishnamurthy*
>>
>>
>>
>
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Xsltforms-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xsltforms-support
