[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: Style vs. transformation
I second the requirement for multiple passes. I could foresee another use besides just breaking a problem down into smaller pieces. It could also be useful if someone already has an existing XSL script for a class of documents (A). The user has a second class of documents (B) that are almost the same as A. Wouldn't it be nice if the user could just augment the script for A by putting a transformation pass at the front that transforms B to A? Sure they could invoke the XSL processor twice, but this is a big performance hit on some systems. Wouldn't it be nice if one could do it with a single invokation of the XSL processor? Rob >-----Original Message----- >From: Sean Mc Grath [SMTP:digitome@xxxxxx] >Sent: Wednesday, March 04, 1998 6:39 AM >To: xsl-list@xxxxxxxxxxxxxxxx >Subject: Re: Style vs. transformation > > [snip] > >I would like to see something in XSL that supported >"chaining" the flow object tree resulting from one >stylesheet transformation into another stylesheet. > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|