Re: Merging PHPLIB into PEAR

> I agree with Ulf that the primary audience for PEAR will and should be web > application developers. This would place a requirement on PEAR that it > support the activies of web application developers. This will be difficult > to do it the components are not integrated in some fashion. Once we start > getting into integrating multiple components there is really no escaping > the fact that you are implicitly endorsing an application framework. right. but in that case, it is a _huge_ amount of work to properly design and build such a framework. I have already done that work. I would like to improve on it, but improving is a hell of a lot easier than starting from scratch. > That said I do have my own issues with PHPLIB. I don't think dumping all > application code into a single PHP directory is scalable or promotes > independent development of the code base very well. I think this has been agreed. > corrected in the development releases but there is no downloadable snapshot > for me to verify that it is a workable partitioning. Also, the logic of > some of the authentication is extremely difficult to follow so when you > have problems with your authentication it is very difficult to figure out > where the source of the problem is. Finally, the effort behind PHPLIB > seemed to have died for awhile and I'm not sure why. I am thus wary of the > offer to incorporate PHPLIB into PEARs codebase unless I can see what > concrete steps the primary authors intend to take towards making this a > reality. This offer could in fact impede development of an alternative > application framework if we are all waiting with our hands in our pockets hrm. -alex