Proposal: Template_Flexy in pear.

I finally got round to writing the documentation for (Yet another template class), this one kind is based on Wolframs simpletemplate, however it really only focusses on the essentials of the template engine. and simple tags. I named it Template_Flexy, a) due to it's flexible nature, it is has been used for building uml diagrams, email templates, and rtf files (along with the usual html stuff) - which is why it's not called HTML_Template_Flexy b) flexy, as you can define your own tag system by just adding a filter.. While I did discuss with wolfram breifly about merging it with simple template, the aims of the two are slightly different. Flexy is heavily focused at allowing the templates to be edited in a WYSIWG editor, and hence does not have {$object->var}, but {object.var} and %7Dobject.var%7B. and it avoids managing (and caching) the resulting output, as that could be done by the controller classes using the PEAR::Cache. The overriding principle is a small package performing a single task, rather than making it too complex. The pear package is available at http://docs.akbkhome.com/Template_Flexy-0.2.tgz The documentation is alread in docbook http://docs.akbkhome.com/Template_Flexy/ and The code is 'pretty much there' (or on it's way) as far as the coding standards go.. I know this is not the only 'template solution', but I think this approach has enough to add value to the PEAR libraries. +1 from me :) regards alan