Re: Templates in PEAR

On Jun 2, 2004, at 11:21 AM, Joshua Eichorn wrote:

Lukas Smith wrote:

This is not a double standard. We are just now beginning to enforce a common vision (or even defining this common vision).

I still consider it a double standard, its the good old i got into PEAR in the past so the rules don't apply to but, but they apply to anything new.

Hate to say it, but it sure does look that way. It's the "land grab" analogy again: get in early so you can do what you like, any following competitors have to jump ever-higher bars, and the early entrants don't have to re-jump the new bars to stay in.

But really my only goal is to have singular modular template infrastructure in PEAR. And i think its base should be a something Pure php, if you want a different syntax you just have a filter on the templates and that converting could either be runtime, or compile time. And then the current template module would just become api wrappers.

I have to say I agree on all these points (a single modular structure based on PHP but extensible to other means). I think the Savant mode of operation, even if the end result is not called "Savant", is the mode to work from -- but that's just me. -- Paul M. Jones Savant: the simple alternative to Smarty for PHP. http://phpsavant.com/ DB_Table: build RDBMS tables and XHTML forms in one PHP class. http://wiki.ciaweb.net/yawiki/index.php?area=DB_Table Yawiki: a collaborative online documentation system. http://wiki.ciaweb.net/yawiki/index.php?area=Yawiki Yawp: a single-file foundation for PHP applications. http://phpyawp.com/