RE: [phplib] [RFC] Future of phplib From: Chris Johnson (chris <email protected>)
Date: 07/23/01

PEAR is a repository of all kinds of stuff, as you say yourself.

No one here wants to invent a second PEAR, as far as I've seen.

PHPLIB is an integrated framework. Some of us want to extend it to
being an integrated application framework. That means all parts of
PHPLib are designed to work together, and optional parts can be used or
not used.

PEAR, as a repository, has a bunch of stuff that you can pick and
choose, but it is NOT designed to work all together as a system or
framework. In fact, many of its pieces will conflict or totally replace
other pieces.

> -----Original Message-----
> From: Björn Schotte [mailto:bjoern <email protected>]

> PEAR is and will be something like CPAN: a comprehensive
> repository of many classes like DB abstraction layers,
> auth classes, template classes and so forth.
>
> As PHPLIB is a framework with many classes (some depending
> on each other), it is predestinated that it (or some or
> most components of it) will be a part of PEAR.
>
> You want to invent a second PEAR. I don't think this
> will be a good idea.
> 

-- 
Abbestellen mit Mail an:   phplib-unsubscribe <email protected>
Kommandoliste mit Mail an: phplib-help <email protected>