Re: Re: new template engine
| From: | Björn Schotte | Date: | Tue, 24 Jul 2001 10:39:09 +0000 |
| Subject: | Re: Re: new template engine | ||
| References: | 1 2 | Groups: | php.pear.dev php.pear.general |
| Request: | Send a blank email to pear-dev+get-1016@lists.php.net to get a copy of this message | ||
* Tomas V.V.Cox wrote:
> documentation style, error reporting and quality". If Pear starts to
> accept everything, Pear will become something like hotscripts and
No. Hotscripts is another thing. Hotscripts contains
mostly "applications", not "components".
> believe me this will kill Pear.
Prove it. :)
> Pear ones it's because them meet their needs. Having many classes that
> provide _similar_ functionalities only will confuse people and make
No. Today we have similar Template classes (PHPLIB,
IT[X], FastTemplate, FastTemplate-patched, Smarty)
and I haven't seen one developer who gets confused
by them. I only have seen developers who thoroughly
test those classes and choose the one who _fits_ _their_
_needs_ _best_.
> helping that mess to grow ;). I'm friend of improving, enhancing or even
> replacing but not of duplicating.
Why should IT[X] (for example) have the right to be the
only one template class inside PEAR? Who is such a arrogant
boy to say that?
Björn.