Orkan |
|
---|---|
Well, I have completely different idea about the parser in SED.
Lets say you have installed a new gallery plugin which adds new bbcode [photoid=123] Then, you have yet another plugin ie. for flash movies, with new bbcode [movie]...[/movie] How this will work with modules? You cant replace one parser with another b/c that way you lose the other one. I would like to see one, internal Parser() function which will operate on two arrays. PS. These 2 arrays are now "closed" in sed_bbcode() - one for str_replace() and one for eregi_replace() Both arrays should be stored in DB and therefore be accessible to any plugin. Each time you install new plugin, it can add new bbcodes to DB. What I mean is that we need only one powerful Parser() function with its basic functionality. With modules we can only destroy Seditio's clarity and code integrity. I would suggest - instead of modules - creating flexible functions that plugins can use with their own data. There is no point in copying Sed's functions to modules, IMO :) Perl - the only language that looks the same before and after RSA encryption.
|