Plugins

I don't see what you mean by "plugins" - what are you talking about? :)

Ah I see - so you're talking about writing additional "sub modules" that can be slapped into the uieforum module directory, and that will be picked up by the module itself?

Well that certainly is an incredibly interesting idea - and one that I hadn't ever thought of before.
But as that's moving even further away from the Drupal ideals I don't think it will actually be coded. It really is an interesting thought though - I think I'll have to consider this one for a little while :)

Daniel

Right here we go ... :)

Basically, UIEForum doesn't use Drupal's node system. It stores its' own content in its' own tables - F_Forums, F_Threads, F_Posts, F_Groups ... and so on.
Drupal stores all content in a table called "nodes", and all data entry is done through the node module (as far as I'm aware). Due to this centralisation, when you enter content for one module (that uses nodes) and when you enter it for another module (that also uses nodes) they both use the same input system, be that TinyMCE, or plaintext. It will also be passed through the various content filtering functions that you have applied to the content in the settings ("Filtered HTML", "PHP", "Full HTML" ... etc).

UIEForum uses its own form system for data entry, as well as its own filtering functions. In order to prevent XSS I make a manual call to filter_xss() within the uieforum_filter() function.
If UIEForum were to pass its' content through the pre-defined filters that you have setup in your settings then I'd have to duplicate yet another system that already works perfectly well in Drupal itself :)

Ideally, I should be concentrating on making UIEForum store its' content as nodes, instead of in their own tables that remain outside of Drupal's system, instead of trying to duplicate any other functionality :)

Do you get what I mean now?
Daniel