Re: [binarycloud-dev] the xsl decision

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

I think it's worth clarifying that the TemplateManager will use subclasses
for each template type - so like almost everything else in binarycloud,
there's nothing that _prevents_ anyone from doing anything they want.

What I'm talking about with regard to XSLT and the like is, will _I_ be
using this in production, i.e. do I need to build this code for myself?

The answer is increasingly no where parsed templates are concerned,
especially in light of a few other projects that are part of r2.

When I'm done with the r2 specs (which should be quite soon, despite their
condition on the site) - I'm going to see what kind of support there is on
this list and in the community for building some of these advanced tools,
including an XSLT->PHP makefile, Smarty extensions to the TemplateManager,
etc.

Once the specs are done, the full power of the system will be evident (hm,
did I steal that from darth vader, or was it the scary old general guy
running the death star).

anyway: the idea with the managers, and indeed all of the subsystems in
binarycloud is that they should make the most basic assumptions they can to
get a cohesive system functioning - so people can work within the system
(benefiting from all the tools, etc.) without it getting in their way.

/rant

_alex


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

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

vox+510.666.0074
fax+510.666.0093