Re: Re: Categories

> > > > A "Forms" top-level category would probably be what we needed if there > > > > is XML form stuff coming too. > > > > > > Top-level? Please explain me why top level and not sub-category of HTML. > > > > What if someone makes an "über-forms-package" that deals with HTML, > > XHTML, WML and PDF/FDF? :-) > > > > Ah, ok, ACK :). But as far as we can IMHO we should minimize the number > of categories to never overcome 10-15 per level. hmm. what about doing something like php? you have one MAIN/BASE-tree and a EXT-tree. (think this is the way they do it, sort of ;o) MAIN | +- HTML +- FORM +- TABLE etc EXT +- ÜBER-FORMS-PACKAGE +- SUPER-DUPER-PDF-STUFF and when a package is ready to include in the main-tree you just move it. yes, i know. how do you keep backward-compability? well, an easy way would be something like include $PEAR_ROOT . "/base.php"; $base = new base(); $base->include("package_name"); (forgive me if the code wouldn't work (i haven't touched classes yet (forgive me god)), but you understand what it SHOULD do) and then it doesn't matter where you have the package. AND if you move it and rename it in some way, you just make an alias in the base.php-file (or base.xml, what do i know?). and this would also help people distribute packages for use in PEAR. download a package, the package is then installed into EXT. maybe? / d