> > It's not so much about "emulating threading" but about good software > design. Small, functionally well focussed stylesheets make code reuse and > recombination easy. Better performance through parallelisation is more of a > side-effect. > I've played with partial stylesheets enough to decide: one root XSLT for all site, all assembly made in XSL, correct XSL split and imports for cross-site parentness. That's exactly what you need on the long run. Putting presentation back to your code, even partially, messes the architecture wonderfully quick. Logic and data should leave on the one side, presentation - on another. And XML in between. If you do not like this clear setup I wonder why you ever use XSLT - building page in Perl/Pyton/etc and manipulating with blocks and templates there is even more trouble than just using native templating engine from the start. For making "focused stylesheet" there is <xsl:template and it's absoluelty enough.
_______________________________________________ xslt mailing list, project page http://xmlsoft.org/XSLT/ xslt@gnome.org https://mail.gnome.org/mailman/listinfo/xslt
