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

Bonjour,
Alan Knowles wrote:

> Dont know the code that well, but cant you merge some of those classes 
> together into groups of methods, and support that method of loading? - 
> hence reduce the need to create 100's of classes?
>
> Regards
> Alan
>
> Stefano F. Rausch wrote:
>
>> Hi Paul,
>>
>> Paul M Jones wrote:
>
sorry, it's me having wrote that:

>>
>> > <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.
>>
Yes, that is the point !
I simply adore this flexibility "we" have
Any can customize it as needed

Just, so, more comments than code.

I don't suspect any performance side effect, no problem there

Anyway, the pear package command leads to warnings, not sure we could 
autoload...

Any "rule" grouping should consider the classification documented on 
http://wiki.ciaweb.net/index.php?area=Text_Wiki ,
there the order of appliance is fundamental.

Finally, we just need to apply successive preg_replace_callbacks, a way 
I see, would separate the regular expressions from the callback (which 
would load only if needed)

For the performance side of Text_(Markup|Wiki) we would need some 
factory() / singleton() too, that's runable, OO good enough.

>>
>>
>> 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
>>
>
I've no idea about this ScriptReorganizer, stefano, thanks for the link
blah ... again such a long mail, sorry
-- 
toggg

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