Re: Re: HTML_BBCodeParser orphan - New maintainer needed

On Aug 8, 2005, at 2:57 AM, bertrand Gugger wrote:

Paul M Jones wrote:

I would call it "Text_Markup" and say "yes." :-)

If we do that, then better do it whe we have the stufff restrucured (instead of Text_Wiki2 :) )

Agreed. We can work outside the main PEAR-DEV list to avoid cluttering it; perhaps the users@textwiki.tigris.org list would be better.

Text_Transform would perhaps be more suited

Hm, let me think about that one.

While we're on the subject, I'd like to come up with a better way to collect parsing rules, the array of rules in the main Text_Wiki object is OK but I think it could be much better.

I totally agree, design and packaging should be refunded as the stuff will only grow. As Helgi suggested , a plan can be to split as Validate or MDB2 did.

I agree that a refactoring of sorts is needed. The main issue is the parsing rule collections, not the rendering rules so much.

But that's perhaps a discussion for another thread.

That should be first a discussion among Text_Wiki devs, then when we can propose some plans, then OK, let colleagues give their (v|ch)oices. e.g. let answer my previous mail's questions

I'm sorry, which questions were those? Was it the "two headers" issue? Annoying though it may be, we do need to stick to the one-file-one-class rule, as it's the only way to reliably allow for mixing and matching of rules. -- Paul M. Jones <http://paul-m-jones.com> Solar: Simple Object Library and Application Repository for PHP5. <http://solarphp.com> Savant: The simple, elegant, and powerful alternative to Smarty for templates in PHP. <http://phpsavant.com>