Mark D. Anderson wrote:
> I'm curious why you took the approach of generating separate js scripts,
> rather than using xslt extension so that the xslt processor invoked
> any script code you had to have.

extract from http://www.w3.org/1999/08/WD-xslt-19990813#extension
>>>    This version of XSLT does not provide a mechanism for defining
>>>    implementations of extensions.
This is THE feature I want in XSLT ASAP.
Given the rules I would be able to create my own extensions easily.
Until then I rather stay with XJS: XSLT/ JavaScript combination 
then going for application-specific extensions.


> Was it because the code got messy, or because there is no xslt
> processor that works in your environment that supports extensions
> in your chosen script language?

If anybody know of such XSLT processor, please let me know.



 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list