ok, its theme specific, and that particular folder is for theme related bbcode "themes".
however, yes, I dont see why not, as a "default part" of the theme-info it should be able to cope with something like $bbcode
remember that what us used in the site (from admin) should not be "exclusive" to a bbcode "theme".
so maybe in this particular casewe would have the following (without overly complicating it)
Code:
Plugins/_BBcode/MarkItUp/
Plugins/_BBcode/bbCodePress/ (not bbCodePress-lite)
themes/_BBcode/light/
then there is the question of:
Code:
themes/_BBcode/egi/ or
themes/egi/images/bbcode/
I thinks the second one, because that is the default for egi, and hence "part of the theme"
anyway, there is a 3rd part to bbcode & emoticons, and that is how they are stored in eoCMS itself, and how they are linked back to "image sets". ATM you can link to a image, the trick will be to be able to choose a different set of images, and what happens when there is no "image" for a specific item
I so if you can imaging that all "bbcode" folders are "related" to each other, but each one does a diffent part (so that it can be quickly and simple added/plugged/unplugged)
a lot of word to say, yeah, there needs to be a theme-info-new example of how it would work.
the admin/db stuff would be (in the code) separated into bbcode plugin (JS, etc), default images (theme), bbcode entries (buttons & "others"), and bbcode "replace" entries.. but presented as one in the admin..
BTW the example theme-info is able to extend to other "?-info" files too, and flexible enough to handle even the db stuff.. so its just a matter of organising it so that it has and does everything that you want (or needs it to do)