How to Organize settings?

Jun 17, 2008 at 5:21 PM
In order for the RTE to be useful in a large set of circumstances without having to modify the source and re-build, we'll need to have a large number of settings. I'm at a loss as to how to organize these settings. For instance, we'll probably want a collection of settings for each toolbar button such as visibility and the like. Are there examples to draw from? What are your thoughts on how to organize these settings? For that matter, what should be configurable?
Jun 19, 2008 at 4:04 PM
My thoughts on questions 1 & 2:
My opinion would be to use an xml configuration file(s) with a schema.  Look at the xml file i18N.xml and it's schema i18N.xsd (in the RTE proj) for an example of what I mean.  Maybe have some type of Settings Class(es) to represent these xml files.  Properties would need to be added to the rte to specify the locations of the XML config files.  If you need more examples let me know.

My Thoughts on question 3:
I've always been a fan of being able to adjust as much as possible through config files.  Using themes and allowing the config to specify CSS Classes is a good way of reducing the amount of "configuration" code, while still allowing lot's of customization.