Re: Model-View-Controller: Template Toolkit vs. XSLT

XSLT makes the most sense if your data is in XML to start with. Transforming relational database to XML and then to XHTML with XSLT adds an extra step. But, for example, an aggregator might use XSLT to transform RSS and Atom.

XSL-FO is for printing. Programs like FOP render it into PDF.

Comment on Re: Model-View-Controller: Template Toolkit vs. XSLT

Replies are listed 'Best First'.
Re^2: Model-View-Controller: Template Toolkit vs. XSLT by tomhukins (Curate) on Oct 15, 2004 at 10:58 UTC
I've had some success using Template::Plugin::XML::LibXML for parsing simple XML files. This allows me to process XML using XPath, my favourite part of XSLT, without XSLT's syntax, which I find a little verbose and fiddly. Your tastes may vary, but my point is that XSLT isn't the only templating system that can process XML documents. It still helps if you learn XPath, which takes time, but provides a very convenient way of accessing data in tree structures.	[reply]

Replies are listed 'Best First'.

Re^2: Model-View-Controller: Template Toolkit vs. XSLT
by tomhukins (Curate) on Oct 15, 2004 at 10:58 UTC

I've had some success using Template::Plugin::XML::LibXML for parsing simple XML files. This allows me to process XML using XPath, my favourite part of XSLT, without XSLT's syntax, which I find a little verbose and fiddly. Your tastes may vary, but my point is that XSLT isn't the only templating system that can process XML documents.

It still helps if you learn XPath, which takes time, but provides a very convenient way of accessing data in tree structures.

[reply]