Re: pearifying Metabase (was: [PEAR-DEV] New Metabase Aniversary release)
| From: | Stig S. Bakken | Date: | Fri, 25 Jan 2002 11:33:56 +0000 |
| Subject: | Re: pearifying Metabase (was: [PEAR-DEV] New Metabase Aniversary release) | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-4160@lists.php.net to get a copy of this message | ||
On Tue, 2002-01-22 at 22:29, Björn Schotte wrote:
> * Lukas Smith wrote:
> > There are some radically different approaches in the various template
> > engines
>
> Not at all, compare IT/ITX and PEAR::HTML_Template (PHPLIB's
> template class).
>
> > Metabase is a good code base.
>
> No one doubts that.
>
> > So PEAR community ... please either shot this project down cleanly or
> > lets get the ball rolling. I can deal with Metabase. I do not _need_ a
> > pearified Metabase. I think it will help PHP greatly.
>
> I would appreciate PEAR::Metabase, but I doubt that replacing
> PEAR::DB would be a good move. There could be other voices in
> the future that say "You know, Metabase replaced PEAR::DB, now
> I want that my super duper PEAR::Socket_very_cool should replace
> PEAR::Socket".
What's the problem with that, if PEAR::Socket_very_cool is compatible
with PEAR::Socket? That's the case with the Metabase integration too:
current PEAR DB users should not have to change their code unless they
want to start using the added features.
- Stig