RE: hard core xlt ;-)

> From:	Adam Van Den Hoven [SMTP:Adam.Hoven@xxxxxxxxxxxx]
> Sent:	Thursday, July 26, 2001 5:04 PM
> 
>Just like having server-side script that writes client-side script,
this is
>most difficult because you have to keep track of what bits of script
are
>doing their work now or later. I get a headache just thinking about it.

>I must say that I've never found a convincing situation where this
would be
>a preferable solution over using document() to load in additional data,
a
>number of global params and some well designed and judiciously used
named
>templates. Not that I'm claiming a wide breadth of experience in
situations
>that could make use of such a system. 

>What would be a good example of a problem that would be best solved in
this
>fashion? 

Where you wish to produce XSL transformations as a batch job. Lets say
you have XML files that define different types of information. You wish
to create XSLT files that generate a HTML form for viewing and editing
the different types of info.
It also gives a performance advantage because at run time you do not
have to parse the XML which contains the type definition.

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