Date: 07/21/01
- Next message: Richard Archer: "Re: [phplib] [RFC] Future of phplib"
- Previous message: Björn Schotte: "Re: [phplib] [RFC] Future of phplib"
- In reply to: giancarlo pinerolo: "Re: [phplib] [RFC] Future of phplib"
- Next in thread: Richard Archer: "Re: [phplib] [RFC] Future of phplib"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
* giancarlo pinerolo wrote:
> BTW I missed to stay up-to-date with the evolution of PEAR too, of which
> I know little.
> I'd like to read what happened, and why and how, it sounds as an
> important point in the course of PHPLIB
>From a logical point of view, it is clear that PHPLIB or at
least most parts of it, should migrate to PEAR. PEAR is the
future in the sense of PHP components.
> I am optimist, and can see a future for PHPLib
In my opinion, the first and next step would be migrating
PHPLIB's components (DB, Session, Auth, Perm, Templates, ...)
to PEAR.
-- PHP Schulungen und | International PHP Conference Schulungsmaterial: | 05. - 07.11.2001 http://thinkphp.de/ | Astron Hotel, Frankfurt http://rent-a-phpwizard.de/schulungen.php | http://www.php-kongress.de/-- Abbestellen mit Mail an: phplib-unsubscribe <email protected> Kommandoliste mit Mail an: phplib-help <email protected>
- Next message: Richard Archer: "Re: [phplib] [RFC] Future of phplib"
- Previous message: Björn Schotte: "Re: [phplib] [RFC] Future of phplib"
- In reply to: giancarlo pinerolo: "Re: [phplib] [RFC] Future of phplib"
- Next in thread: Richard Archer: "Re: [phplib] [RFC] Future of phplib"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

