It has the following pre-requisite: make XSLT available as part of the Zope framework.
Once you can rely on having XSLT as part of your framework (it really should be part
of "batteries included" IMHO), you can do interesting things like providing a transformer
for creating CSS files out of some sort of XML dialect. Here is a snippet of one we created
<FileName>ariel-letter</FileName> <Comment> Special style sheet to support printed Ariel Partners Letterhead </Comment>
If someone does not like the XSLT transformer that Zope would (in my proposal) provide
out of the box, they are free to substitute their own. Since it would be integrated with ZPT,
you could use ZPT expressions to create the XML dynamically out of pieces and parts.
If the XSLT capability were integrated into ZPT somehow, it could be made cache aware
for greatest efficiency.
Of course, not everyone likes this kind of "generative programming" approach. I find that
code generation tends to simplify alot of problems.
Just my 2c,
Richard Jones wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Friday 02 Apr 2004 18:44, Chris Withers wrote:
Ah, okay, I think building something purely for CSS would REALLY suck.
Something which could generically build SQL, CSS, Emails I would be less lielyl to vomit about...
So persuade the Python guys to make string interpolation as powerful as you
need it to be ;-)
Why don't we have a good, long look at:
under the "Templating Systems" heading and make sure that someone else hasn't already come up with a good system that templates SQL, CSS, email, etc nicely.
There's an awful lot of templating systems there...
Zope-Dev maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists - http://mail.zope.org/mailman/listinfo/zope-announce