Re: [phplib] [RFC] Future of phplib From: Bertrand Mansion (bmansion <email protected>)
Date: 07/21/01

le 21/07/01 15:06, Björn Schotte ā bjoern <email protected> a écrit :

> * Bertrand Mansion wrote:
>> positioning. PEAR : heavyweight, powerful but slower - PHPLIB : easier,
>> faster but not as complete.
>
> I think you've missed the sense of PEAR: PEAR is not
> "heavyweight, powerful but slower" (only if you refer
> to PEAR::DB, but I think you mean the whole PEAR),
> 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.

I was actually referring to PEAR DB.
I don't think I have missed the sense of PEAR and I think we agree on many
points regarding the sense of PEAR. Actually, I have made an HTML_Table
class for PEAR.

> 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.

It does not have to be a part of PEAR to exist. It does not neither has to
use PEAR at all. For example, people could choose, thanks to a wrapper,
whether they want to use PEAR DB or PHPLIB DB. The rest (Auth and sessions
for example) would be pure PHPLIB.

> You want to invent a second PEAR. I don't think this
> will be a good idea.

This is not what I want. I did not make myself clear. I want PHPLIB to stay
the framework it is now, but just that. Not an extension repository.

Bertrand 

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