Re: Merging PHPLIB into PEAR

> The bad thing on Java or Perl is that you can't say you know the > language unless you know lots of library code. Let's concentrate to > build an integrated core system. Such a system determines the success of > PEAR not amount of classes. ulf: that system exists. I am using an integrated, core system, called binarycloud. it is production tested and it works. I don't see the point of going through all the trouble to reinvent another set of wheels, you'll just go around in circles forever doing that. hopefully this is not the opinion of the wider pear group. am I wrong? > The "application framework" would be loosely tight together. As with > PHPLib you can use every class on it's own (beside some few > dependencies). You don't have to use perm and auth, but you may use it > and be able to write full-fledged applications just by using the given > solution. You don't have to rebuild this code every time. If you don't > like the perm, auth or whatever implementation it's still a good > starting point for your own implementation and you'll be able to learn > from the prototyle. perm and auth exist. we also have written a number of libraries that I intend to sonate to PEAR: a serious, robust form builder (which uses xml declaration of elements, and has support for rulesets) a table builder, etc. from what I have heard stig talking about, PEAR is first and foremost a library repository, _not_ an integrated platform for php webapps. I've got that, I'm running it, and I'm improving upon it. >> applications. Things like permissions and authentication, no matter how >> generically written, dictate some model of permissions, some model of > > That's not really of importance. IT managers considering to use PHP > should always hear "Use PHP it comes with PEAR, that's a cool framework > for developing webapplications, it's more than a source collection like > CPAN is.". ulf: go download binarycloud. :) -alex > Ulf > > -- > 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: php-pear-unsubscribe@lists.php.net from the > mail address you subscribed with. >