[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
Re: What will be the future improvements of XSLT?
Subject: Re: What will be the future improvements of XSLT? From: David Carlisle <davidc@xxxxxxxxx> Date: Thu, 16 Sep 1999 09:20:09 +0100 (BST) |
> So far, the most difficult problems for me to solve are: > 1, Drawing a calendar as a table given only the year and the month. A solution to that one was posted on this list a week or so ago. > 2, Sorting of elements according This is one area where I think XSL is weak, not because of the declarative nature, but because you can't reuse the result tree, it is hard to do sorting and processing at the same time. (see the recent question about sorting data and grouping into table rows) sort template with syntax like: <xsl:sort select="@tour" comparison="golf-compare"/> probably the XSL way would be more sort template with syntax like: <xsl:sort select="golf-order(@tour)"/> with golf-order being an extension function that mapped from your enumerated type to the integers. > XSLT is very verbose If the world doesn't move to XML as being predicted, XSLT is anyway lost. If it does, then verbosity will be a general fact of life. If you use an XML editor which can hide some of the XML details then this isn't so much of an issue. > and I must rely on the comments to figure out the > function of the templates. Your XSLT file is an XML document, you can put in structured comments marked up from another namespace, html, docbook, whatever, and then tell the xslt processor to ignore that namespace. David XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: What will be the future improve, Khun Yee Fung | Thread | RE: What will be the future improve, Hunter, David |
[Fwd: Creating entities with XSL 19, Miloslav Nic | Date | xsl: javascript function., smoghe |
Month |
Keywords