> > I am still very fond of XPathScript, as it allows easy mixing of > > program-flow decisions and HTML output and having real "programs" > > called by a xml-tag and bubble the output of the perl code through > > the stylesheets. > > > > So I never tried XSLT. Perl subs then have to to taglibs, > don't they? > > That's what Matt meant: XSLT works differently. There is no > Perl whatsoever involved with XSLT. But don't be fooled by the Syntax. > XSLT is turing-complete, and using EXSLT-Functions (see www.exslt.org) > you have most of the stuff you need and can do quite complex things. > Not that you need to, since often you just don't need to go > programming with XSLT. > > Taglibs belong to XSP and have nothing to do with XSLT. XSP doesn't compare > well to XPathScript or XSLT since it works more like HTML::Mason or PHP.
Hi, I'm a newbie still trying to wrap my head around when and why it would be desirable to use a taglib over a Provider. Let's say you had a database (your Model in the Model-View-Controller pattern) and you wanted to provide the data contained therein to a XSLT pipeline (the View) for dynamic transformation into any number of formats. You also have a client-side interface in...let's say Javascript (the Controller). Would it be fair to say that a "pure" XSLT solution would prefer the use of a Provider for database access as opposed to a taglib? Curious on your opinions, -- Sean Evans --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
