RE: [PHP-PEAR] RFC on merge of PHPLib and Pear

Let me point out that phplib is NOT an application but an API.

--
Jeff Stuart
[email protected]

-----Original Message-----
From: Chuck Hagenbuch [mailto:[email protected]]
Sent: Wednesday, March 07, 2001 11:05 AM
To: [email protected]
Subject: Re: [PHP-PEAR] RFC on merge of PHPLib and Pear

Quoting "Jeffrey A. Stuart" <[email protected]>:

> Ok.. here's my ramblings and thoughts on the merge... If anyone has any
> ideas/suggestions, PLEASE holler. :)

Doing so.

> 1) Create a Pear::PHPLib Class.

Why?

> 2) Underneath that, import ALL of the PHPLib classes into it.
> 3) Initial Pearize of the phplib classes... (IE PHPDoc/style changes to
> functions/var names).
> 4) Start moving things around. :)  IE for example, probably move the Auth
> stuff from PHPLib into an Pear::Auth class.

Again: let's not put this framework into PEAR. We should have a seperate
place
for complete app frameworks.

> 7) Write wrappers around the newly moved classes to behave as the old
> phplib
> classes.

This, IMHO, should not be part of PEAR. Yet another reason for keeping
phplib
as its own framework somewhere.

-chuck

--
Charles Hagenbuch, <[email protected]>
"Live, from Washington, where the doctors were telling us what they did, and
 did not, do with Vice President Cheney." -Dan Rather

--
PHP Extension and Add-on Repository (PEAR) mailing list.
Documentation can be found at http://pear.php.net/doc/pear.html
To unsubscribe, e-mail: [email protected] from the
mail address you subscribed with.