determine feasibility of rewriting into a component based map voting system

[GoogleCodeExporter]

What would you like to see changed?
Instead of having a single plugin with all the features packed into it (using 
CVARs to enable/disable), make it more component based.  Either put the 
different features into separate include files that can be included based on 
defines or have the different features each have their own plugin file (ala 
Total Ban Management) that registers with the main Galileo plugin (which would 
only do basic map voting things).

Why do you want this change made?
It'd be fun to write. For people that are worried about the size of their 
plugins, they could only include the features they want, reducing the total 
size of the system. It'd make the code clearer.

What version of the plugin are you using?

Please provide any additional information below.

Original issue reported on code.google.com by jones.p....@gmail.com on 25 Dec 2010 at 9:47

[GoogleCodeExporter]

probably look at this again after TBM is released. at the very least, TBM will 
give a better idea how this type of thing would work and be received.

Original comment by jones.p....@gmail.com on 25 Dec 2010 at 9:49

[GoogleCodeExporter]

[separate plugins]
pros: easier for others to write components
cons: plugin clutter (lots of plugins listed)

[separate include files]
pros: single plugin. quality control.
cons: lacks 'cool' factor. most complex from user POV.

Original comment by jones.p....@gmail.com on 25 Dec 2010 at 9:59