RE: [binarycloud-dev] xslt

[Faine, M. <Mar...@ms...>]

I like xslt but I do believe it seems complex and overly strict.  I once
tried to do my resume as xml/xslt and gave up after pulling my hair out for
3 days trying to get the page layout right.  It wasn't that I couldn't make
it work, I just couldn't make it work like I wanted it to work.

I got an error on your example:

Fatal error: msgtype: error in /home/mfaine/www/xslt_example/form.php on
line 18

never seen a msgtype before.

-Mark





-----Original Message-----
From: alex black [mailto:en...@tu...]
Sent: Thursday, May 17, 2001 12:20 AM
To: bin...@li...
Subject: Re: [binarycloud-dev] xslt


> I'm interested in seeing some examples. How does this affect the use of
> template engines, such as Smarty?

Attached.

Note that this isn't r2 stuff really, I'm putzing with some ideas.

But assuming you have sablot compiled in to php you can run this stuff.
It's surprisingly fast.

I got _180k_ of html out of it from a 44k xml source + 5k xslt, and that
only took 1 second.
Most normal documents take in the thounsanths of seconds.

Sablot sort of sucks, but 4.1 will solve that.

Re: smarty:
I'm not going to build in support for smarty, but I should explicitly
mention that you can easily build a smarty subclass for TemplateManager.
TemplateManager was specifically designed to take any template type, it's a
generalized API.

But XSLT is so unbelieveably groovy, I'll be building all my code with it.
Once you get over some of the little idiosyncracies, you realize how
powerful xslt really is.

So the short answer is that all release binarycloud 2 modules will use XSLT
exclusively. If someone wants to write a smarty subclass for
TemplateManager, I'm happy to include it in the release.

_alex