Text_Markup , some necessary evolution of Text_Wiki ?

Bonjour,
My first reaction to Text_Wiki was "huh ?" , so much files for so simple 
things...
Later, I worked with Justin around some CMS's , then he showed me up his 
"home-cooked" extensions for Tiki, Doku and Cowiki.
I got immediately convinced, Paul's package was indeed what wikis need 
for user's text rendering.

Lol, then I put some pressure on Paul, so Justin and I became devs on 
Text_Wiki.
That was in fact some continuation of that whole move , Text_Wiki is 
from the beginning some community effort, just take a look on all the 
people in source contributors, devs, buggers & patchers.

Since those first released extensions, (Tiki, Doku and Cowiki), and 
moreover the various corrections occurred, it gave some more extensions:
* BBCode parser: the model is not restricted to "wikis" , I felt a 
necessity for it. Text_Wiki_BBCode offers some full replacement to 
HTML_BBCodeParser whose deprecation is in talk. Some experimental 
Text_Wiki_BBCode powered pearweb was successfully tested.
* under popular pressure, Text_Wiki_Mediawiki was born in late 2005.

Outer the improvements what will naturally give, some next extensions 
will occur in the optional renderings:
* pdf was planned and asked since long time
* I examine the possibility to docBook a little
* I have a quick made TiddlyWiki render, case somebody interested...

Naturally, I'm very happy about how all things turn out, I want to thank 
Paul to have put that stuff in here ... and sure also the numerous 
contributors.

Now, I believe that package has to evolve

* first of all the doc is outside pear, I request it to be inside (Paul 
?) (rendering docBook belongs to it)
* the name "..._Wiki" itself hides the real purpose, transforming text 
and markup inside, I like the Text_Markup name which came out couple of 
time (I would hate Text_Wiki2)
* we miss some global coherence tests as , say (html) <i><u> ... 
</i></u> and more ... I would point out Text_Markup mission cannot be to 
correct but refuse, eventually
* 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.
- we lack some practical examples

Sorry for such a long mail, be happy, I forgot a lot.

Please, feel free to report any comment/request as it's preparing 
Text_(Wiki|Markup)? future.

Pearly yours,
-- 
toggg

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