Re: [Phplib-users] extensions to oohforms, table

[Aric C. <gre...@pe...>]

Layne Weathers wrote:

> Nathaniel,
>
>I don't know if re-writing PHPLib is "worthwhile" to anyone else - one of
>the beauties of OSS is that everyone is allowed to define what is worthwhile
>for them. I have been using PHPLib for a few years now and have kept using
>it precisely for the interaction of the classes.
>
>(BTW, what is the correct capitalization - PHPLIB, PHPlib, PHPLib, etc?)
>
>I would love to start working on a fresh release of PHPLib. It would be a
>bit of an undertaking and will probably take a good while to complete, but
>I'd love to get rid of the cruft.
>
>It seems to me that some possible goals could/should be:
>- define some basic coding and formatting guidelines
>    (preferably, this would be set by the project admin or other designated
>    decision-maker so we don't waste time arguing about it)
>- completely audit/rewrite the existing code
>- only commit classes that have been tested by more than one person
>    (e.g., how many current users/developers have used db_msql.inc?)
>- require a minimum of (at least) PHP 4.1 - heck, this is going to take a
>    while, why not build on PHP 5? (semi-serious)
>
>Anyone else willing to consider taking on the challenge?
>
>Layne Weathers
>
>  
>
I've been using PHPLib since I started with PHP some years ago.  I like 
it.  I haven't found anything else that seems to be as simple and 
lightweight yet powerfull enough to be generaly usefull.

I'd like to see PHPLib updated, in addition to what's listed above:
  * MySQLi support (this is the 'improved' mysql extension in php5.  
Anybody know how to get it to play nice with the old mysql extension on 
windows? ).
  * SQLite support
  * PHP5 only.  Yes, that's right.  Why not?  Take full advantage of 
PHP5 new object oriented features.  I'm exploring some ideas now with 
the db and template objects.
  * Permx built in.
  * Better documentation.  I remember having a tough time with phplib at 
first...