RE: [PEAR-DEV] Contribution for PECL

From: Date: Sat, 28 Dec 2002 15:35:53 +0000
Subject: RE: [PEAR-DEV] Contribution for PECL
References: 1  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-11883@lists.php.net to get a copy of this message
> -----Original Message----- > From: Markus Wolff [mailto:wolff@21st.de] > Sent: Saturday, December 28, 2002 4:33 PM > To: Maxx > Cc: pear-dev@lists.php.net > Subject: Re: [PEAR-DEV] Contribution for PECL > > On Sat, 28 Dec 2002 03:34:25 +0100 > "Maxx" <demiurg@ono.com> wrote: > > > Smarty is a one of the best engines I've ever seen, but it has a totally > > different ideology of templating, and can not be compared with > > php_templates. Despite of the fact that it has too much code to be > parsed > > for every request, and therefore needs something like ZendCache to be > > installed on the server for faster work, this is a one of "language > inside > > of a language" projects. You still have to be a programmer to create > > Smarty's templates. > > This topic is being discussed continuously among web developers and can > be > > considered as yet another never-ending ideological (religious?) war like > > "Linux vs. FreeBSD", "Intel vs. AMD", etc. I will gladly discuss this > issue > > with you personally, but I'm afraid [pear-dev] is not the appropriate > place > > for this kind of discussions. > > I am a big fan of simple template engines like IT[X] and don´t like the > language-in-a-language approach, too (which is one of the reasons why I > don´t use Smarty :-)). > > So I´d like to see such an extension in PECL - and what I´d like to see > even more once it´s been committed, is an enhancement for IT[X] that > uses a factory method to spawn either a "classic" IT[X] object, or one > that makes use of the much faster php_template extension - depending on > the extension´s availability on the system. > This way, one could always use the same familiar API and make of the > faster solution whenever possible. Sounds like a great idea. Maybe it is possible to give your extension a similar API as one of the existing PEAR template classes. Minor differences could probably be addressed someway. But that would have several benefits: 1) a nice user base to start off 2) a fallback solution for whenever the php extension is not available 3) a potential nice and snappy prefix for your extension ("it" or "itx") regards, Lukas

« previous php.pear.dev (#11883) next »