Re: [binarycloud-dev] the xsl decision

[Alex B. <en...@tu...>]

> No, admittedly I only know what the acronym means.  I do know it has been
> said to be overly complex.  And quite frustrating to work with.  People say
> the same things of linux but I have no problems there.  So perhaps it
> requires a bit more investigation on my part.

XSL has problems, absolutely. It is also the most powerful template tool I
have come across, so it warrants attention.

The syntax isn't complex, it's verbose, which bothers some people (including
me). But when you work with it for a little while, you realize that in
combination with some necessary tools, it's extremely powerful and flexible.

You can render WML, HTML, and PDF from the _same_ document with XSL. That's
beefy.

> I think using XSL for other capabilities and still allowing people to have a
> simple template system is a good solution.  Though it probably means twice
> (or more) as much work for you.

The way that will need to go is I put the smarty templates in the spec, and
see who in the community is willing to construct the subclass for
TemplateManager.

Starting with r2, there's going to be more code spec'd than will be
generated inside turing.


_alex




--
alex black, ceo
en...@tu...

the turing studio, inc.
http://www.turingstudio.com

vox+510.666.0074
fax+510.666.0093