Re: Re: cvs: php4 /pear/Experimental README/pear/Experimental/HTML Menu.php

From: Date: Fri, 09 Mar 2001 23:15:07 +0000
Subject: Re: Re: cvs: php4 /pear/Experimental README/pear/Experimental/HTML Menu.php
References: 1 2 3  Groups: php.pear php.pear.dev 
Request: Send a blank email to php-pear+get-1759@lists.php.net to get a copy of this message
DB Benchmark [...]
Shedule XML_RPC XML_Parser XML_Render
this is not very forethoughtful (if you thought to put them into the top-level directory), these kind of structures are simply to flat to contain a large amount of classes in a previous mail I already have asked on feedback for a top level differentiation between classes and applications, like this... /classes /applications (maybe /apps) and other PEAR _internal_ dirs like /tests /scripts and then I am in favor creating at least one layer of directories below to be able to group the packages to avoid ending up like CPAN in the previous mail I have thought up just these /Math /Science /Template but what we need is a bit more like this: http://www.hotscripts.com/PHP/Scripts_and_Programs/ there are many entries and some of them can be abridged to more generic directories for sure andré -- · André Langhorst t: +49 331 5811560 · · andre@php.net m: +49 173 9558736 · * PHP Quality Assurance http://qa.php.net *

« previous php.pear (#1759) next »