Re: [PEPr] Comment on HTML::Template_Savant

Hello,

Greg Beaver said, in response to Lukas:

how hard would it be to provide API aliases to existing PEAR templates? This could even be in optional wrapper classes in separate files that extend Savant.

This is an excellent point. Savant is flexible enough, with its plugin and filter architecture, that it might serve as a base class to mimic other template engines. This is not something I'd like to do by myself, but it could be done.

Although it would be good to see a common API for the template engines of PEAR, I don't feel it has to be done now, with Savant. I'm using Savant since a week and it worked great from the beginning. As it's fully PEAR-compatible (hence the proposal), I'd be happy to see it in PEAR to use the common bug system, manual, whatever.. I think Savant should be allowed to be in PEAR as it's a great tool and it's just as good as the other 5 template engines. When someone someday comes up with the idea of contributing something regarding to API-unifying, he/she will be allowed to do it. I don't see why this should be solved in Savant when the other engines doesn't solve this. Regards, Norbert