[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: "Steven Livingstone" <ceo@xxxxxxxxx> Date: Wed, 15 Sep 1999 21:24:51 +0100 |
I use them for different purposes. ECMAScript for validation and DHTML techniques, with XSL for customising the interface. I love the idea of being able to simply apply an XSL doc to XML depending on who wants to look at it and what they want to see. I just makes the interfaces easier to manage. Cheers Steven Steven Livingstone Glasgow, Scotland. +44 7771 957 280 Author - Professional Site Server 3, Wrox Press http://www.wrox.com/Store/Details.asp?Code=2696 Professional Site Server 3.0 Commerce Edition, Wrox Press http://www.wrox.com/Store/Details.asp?Code=2505 President, AIP Scotland. ceo@xxxxxxxxx http://www.citix.com Join Association of Internet Professionals - http://www.citix.com/aip ----- Original Message ----- From: Simon St.Laurent <simonstl@xxxxxxxxxxxx> To: <xsl-list@xxxxxxxxxxxxxxxx> Sent: Wednesday, September 15, 1999 9:07 PM Subject: Re: What will be the future improvements of XSLT? > At 02:39 PM 9/15/99 +0100, David Carlisle wrote: > > > >> I think also that somebody who can manage HTML with a little JavaScript, > >> even given a small subset a XSL, will surely be puzzled by such a > >> declarative language. > > > >Why should this be? > > > >I find XSL far far less puzzling than javascript. Am I really weird? > > You might be weird, but not because you find XSL less puzzling than > JavaScript. > > I've found (mostly from reader comments) that people seem to like working > with either procedural (i.e. JavaScript) or declarative (i.e. XSL) but > there aren't a lot of people who are willing to put the effort into > shifting from one to the other. > > (There are some people who are comfortable with both, but in my experience > they are the minority, though most of them do seem to inhabit this list.) > > Most of the Web developers I work with who are building XML-oriented > applications already have JavaScript and/or Java skills, and find XSL > occasionally useful at best, hair-pulling frustrating at worst. > > Basically, I can't recommend learning XSL if you already have experience > working with the DOM and/or procedural approaches - unless you have a > particular project where it seems especially appropriate or a manager who > thinks XSL _is required_ for XML. The rest of the world I tell (these days) > to try XSLT and see what they think of it. If they like it, great; if not, > they'll probably find it easier to get help with the procedural approach. > > Simon St.Laurent > XML: A Primer (2nd Ed - September) > Building XML Applications > Inside XML DTDs: Scientific and Technical > Sharing Bandwidth / Cookies > http://www.simonstl.com > > > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: What will be the future improve, Simon St.Laurent | Thread | Re: What will be the future improve, Miloslav Nic |
Re: What will be the future improve, Simon St.Laurent | Date | RE: How to use xslt to transform xm, Michael Teigman |
Month |