Re: PHPlib PEAR
| From: | Holger Bahr | Date: | Fri, 19 Jan 2001 16:22:24 +0000 |
| Subject: | Re: PHPlib PEAR | ||
| Groups: | php.pear | ||
| Request: | Send a blank email to php-pear+get-1060@lists.php.net to get a copy of this message | ||
>> I envision something like:
>>
>> DB/ PHPLIB/
>> Auth/ BinaryCloud/
>> File/ Midgard/
>> Image/
>> HTML/
>> HTTP/
>> Console/
>> Crypt/
>> Math/
>> Net/
>> XML/
>> Schedule/
>> Log/
>> Mail/
looks great. let´s see what we have here.
Auth/ ... is also part of PHPLIB
With that envision, i think PHPLIB should be analyzed and splitted,
so that the functionality is to be found in the right place of the
tree.
You can put PHPLIB´s Auth into Auth/ but why should this also reside
in /PHPLIB
Some would say it´s "double", or "confusing" or "redundant to
administer" or whatever.
If PEAR has an OO oriented approach, it should be easy to combine the
functionality of several modules to the "application framework" of your
needs.
"sorry", but i think adding PHPLIB in it´s "current state" would be
senseless.
analyzing and splitting the functionality and putting the modules
in the right containers would make more sense
Holger