Re: Re: [Text_Wiki] Text_Markup , some necessary evolution of Text_Wiki ?

Hi Paul,

Paul M Jones wrote:

 > <snip/>
 >
>> * the file structure of the package leads to too many files (as we 
>> accord to the 1 class/ 1 file rule) but as such we slightly don't 
>> respect the CS for naming classes and anyway:
>> [bertrand@ancilla Text_Wiki]$ find . -name '*.php' -print | wc -l
>> 481
>> the next extensions will explode that to more than 500 classes.
> 
> Agreed that the filespace gets gigantic, but I'm not sure how to 
> overcome that while keeping both flexibility and adherence to 
> one-class-one-file.

Why overcome the "filespace"? Have you looked at PEAR package 
ScriptReorganizer? [http://pear.php.net/package/ScriptReorganizer]

This package could possibly be the answer to your question from a 
deployment point of view, if that is what you're looking at. I haven't 
glanced at the source code of Text_Wiki, however, I (hopefully can) 
assume that parts of it could be reorganized into separate libraries 
according to the functionality these should expose.

Just my .02 in this respect.

-- Stefano

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php