Re: Taking over HTML_Template_PHPLib

Hi, David Coallier wrote:

I was also think about something, instead of having a zillion different Templating in PEAR, what would you guys think about creating the ultimate templating (pear) engine ? We could have different type of drivers depending on the type of templating, etc.. I believe we could achieve something centralized that would be very flexible and yet very performant.. I mean.. all of us (mostly) have used some sort of PEAR templating ITX, PHPLib, Sigma, etc.. Could be a cool idea to make HTML_Template_Supremacy (That's a joke name of course). I'm just throwing an idea here.. let me know why you are against it.

That's not doable, the approaches used by different template engines are way too different. Consider looking at the examples for current QuickForm (it has Renderers for Smarty, Flexy and ITX / Sigma) to understand just *how* different they are. Someone even started writing a base class / interface a couple years ago, but it predictably led to nothing. Speaking of predictability, now that Services_Digg has no problems getting into PEAR, no one is actually interested in HTTP_Request2 anymore?