PEAR issues #4 (tree structure, applications)

Hi, spamming again :)
we should spend some more thoughts on tree structure. This will become 
very important and should be done as fast as possible, we are in an 
early stage now and will not hurt many people if we change the tree 
structure, while it won't be that simple if we wait a year or so until 
it the tree is a crowd of unsorted stuff like CPAN.

a) applications in the tree
Applications and base classes have to be separated. Otherwise it will 
not be possible to keep a clean tree structure. Currently PHPDoc is the 
only application, but I'm going to submit some and other people will follow.

I) I'd suggest splitting the tree into
/classes
/applications 
(maybe /apps)
and other PEAR _internal_ dirs like
/tests
/scripts

Quiz 1) but what do we now with function libraries? do we allow them in 
PEAR? OToneH why not? OTOH class the core of PEAR is a class...
I am pretty unsure on this point and definitely need some input.
maybe some additional /functions or /functionlibs directory

Quiz 2) What kind of applications do we allow in PEAR (of course the 
decision should be made by caseon the list)? I would suggest to 
emphasize the use of some PEAR components as a *preferred* requirement 
(they would then serve as additional examples too ;) )
Exceptions like PHPDoc that do not use PEAR but should be available 
commonly aside.

b) overall tree structure
we should also work on a provident tree structure at all, sure PHPDoc 
would be moved to /apps but where? There has to be a skeleton where to 
put it, it might xactly be the same like the one used in /classes
does "Benchmark" really qualify as a top-level node? Does Cache? I do 
not think so, instead we'll have to work out some intelligent non-flat 
structure to keep the tree clear even if there are many classes and 
applications in it

like
/Math
/Science
/Template

these were easy, but what to do with the rest? where to put numbers? 
(maybe Math?) this really needs some effort to create an intelligent 
structure here, I will not post too much here, maybe some other more 
sophisticated solution is already in the head of one of you :)

andré






-- 
· André Langhorst        t: +49 331 5811560 ·
· [email protected]          m: +49 173 9558736 ·
* PHP Quality Assurance  http://qa.php.net  *