Re: [binarycloud-dev] xslt

[alex b. <en...@tu...>]

> 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