Re: Template Proposal

Sorry, didn't "To:" that last one to the list... =o) On Thursday, November 8, 2001, at 12:45 PM, Alex Black wrote:

Hmm, IMO we are at a point, where we have to decide something general for PEAR: Do we want to allow it to have different classes in PEAR which are all serving the same purpose (here: do we want to have different template classes in PEAR)?

I think that is a decision that should not be made globally: having multiple template engines doesn't hurt anyone (ok, it would in theory be better if everything used smarty) but having multiple db abstraction layers might be harmful.

When I first read up on PEAR, I read somewhere that it was supposed to be something of a CPAN for PHP. A search on CPAN for the word 'template' returned 142 modules (aka. classes) in 53 distributions (packages of related classes). I guess my issue is, I moved to PHP from Perl a year or two ago, and CPAN was nice because it didn't bother too much with details like coding style and whether to use tabs or spaces, and it also didn't say "we don't want duplicates." I've written probably 50+ classes now for PHP that I would love to share with everyone (http://freshmeat.net/projects/saf), and I'm sure a lot of people have. I've written my own DB abstraction layer which is largely DBI-inspired and I much prefer my syntax over PEAR DB, ADODB, Metabase, not because it's better, but because that's how I wanted it. There are also already half a dozen template classes (at least) for PHP. They all work, and they all have somewhat separate goals. I'd personally rather have a PEAR with more choice. However, I do think some guidelines are definitely necessary, don't get me wrong, but I think there are some road blocks here that might be inhibiting potential contributions. Lux

_a

-- PEAR Development Mailing List (http://pear.php.net/) To unsubscribe, e-mail: pear-dev-unsubscribe@lists.php.net For additional commands, e-mail: pear-dev-help@lists.php.net To contact the list administrators, e-mail: php-list-admin@lists.php.net