YATED = Yet Another Template Engine Discussion
| From: | Lukas Smith | Date: | Sun, 20 Jul 2003 10:11:07 +0000 |
| Subject: | YATED = Yet Another Template Engine Discussion | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-18447@lists.php.net to get a copy of this message | ||
> From: Paul M Jones [mailto:pjones@ciaweb.net]
> Sent: Sunday, July 20, 2003 2:49 AM
> Martin, can we hear you say with authority that "no new template
> engines" is the official PEAR policy? It'd be nice to see it posted
to
> the list exactly that way (if you have not already, sorry if you
have).
> This would help to dissuade persons like myself who think there may
be
> a chance, when in fact there is no chance. (Not being bitter, I just
> want to make sure nobody's time is wasted in the future -- certainly I
> didn't expect to generate this much traffic on the list, and everybody
> has heard the same arguments at least three times before.)
Well such an authority is currently in the final stages of being set
into place by Stig. Anyways I think its not so much that we don't allow
ANY new template classes it is just that we feel that there is probably
no need for new ones if developers would just try to implement their
ideas based on the existing template engines. And while I really like
your style you atleast haven't convinced me that Dummy wouldn't fit into
one of the existing classes (same goes for xTemplate).
So I hereby ask all template engine developers who feel they can leave a
"dent" (in the good sense) in PEAR to first consider the existing
packages and how their ideas could fit in there. Through modularizing or
adding a plugin system into existing template engines your ideas might
well fit into PEAR without adding yet another template engine, however
as the authority of each package stays with the lead developer(s) I
recommend that you try to talk to the given developer(s) early. However
since we have this "template engine" mess you often have multiple
developers on different packages you can approach :-)
> I'll put out HTML_Template_Dummy (or maybe just "Dummy" now ;-) as a
> separate PEAR-compliant but not PEAR-accepted class, if that's OK with
> the PEAR leads.
yes you can even create a package which is installable via the installer
and you can just publish the url and then people can still do "pear
install yoururl.tar.gz".
regards,
Lukas