Re: Re: Forum hacks

Hello > I personally would not like a class that would try to do everything for > me, as it would take me a long time to customize it enough to serve my > needs. And customizing it would kill the purpose of a generalized API, > wouldn't it ? I m new in PEAR (just working on jpcache and test pear as an abstrack layer). I did not go in the deep of pear, but I really appreciate the way of PHP:DB. IMHO, it have to be a "model" for the others futur lib in PEAR. As far you use an object model to develop your user management class, you have to respect the principles. A data classes don't have to work with output/interfaces. I see others libs in pear to work with output (but not look inside or what exactly have as functionnality), you are not limited to one class, isn't ? A correct definition could be "module" that could have many objects, properties or methods. The most important problem of many API/lib/modules available for php is the one Joao told us. As far we want others users/dev will use it, we have to give us a way to customize it or simply use a part of it, in an easy way. By the way, where can I find informations about the PEAR goals and history ? my 2cents too ;) pa ps: Since 1 week, I see many messages but I didn t catch a global view.