Re: PHPLib and Pear merge

Quoting Sebastian Bergmann <sb@sebastian-bergmann.de>: > Some people really miss the point of Open Source, they just demand, but > don't want to help out. Yes, but it will always be this way, to some extent. You have to be in it because you want or need to be doing it. If you expect the community to pay you back in help or appreciation or whatever, you'll be disappointed. If you do it because you want to do it, what you _do_ get back will be a bonus. It's sometimes hard to keep thinking this way, though. > Yesterday, the following thought formed in my head: Why not take the > classes from PHPLIB that stand for themselves (like Forms, Tree, Menu) and > "merge" them into the appropriate PEAR/ directories and put the PHPLIB > Framework (Auth/User/Perm/Page/...) into PEAR/PHPLIB/ as a bundle of > classes? I still think that the framework stuff belongs outside of PEAR. But I see no reason at all why the form/tree/menu stuff couldn't be merged in - probably under HTML/? - and made to use PEAR-style APIs. We've had the framework discussion before; I think it's going to be really hard to agree on standards for it. For instance, I've written my own Auth class that will work with pretty much any backend that you want, and doesn't rely on other bits of the framework; I'm going to keep using it, since it makes it incredibly easy to add authentication to my apps. It doesn't do anything _other_ than authentication; permissions are in a seperate system. If people like it that way, I could contribute it, but I'm not holding my breath. :) So I've planned on just keeping that part of Horde, and I think the phplib auth/user/perm stuff should be the same - available as a complete framework, and maybe ported over to PEAR, but not part of it. If we need a PHP Framework Collection or something, I say we do it, and put phplib there. -chuck -- Charles Hagenbuch, <chuck@horde.org> "Live, from Washington, where the doctors were telling us what they did, and did not, do with Vice President Cheney." -Dan Rather