Details
-
New Feature
-
Resolution: Fixed
-
Major
-
None
-
None
Description
All code related to the configuration of settings should be moved to a ConfigurationManager (Configuration.FrameWork)
The ConfigurationManager then loads all settings from the PluginTree to a ConfigurationTree.
This has some advantages, like:
- no duplicated code (in stead of each config-util needing its own load/store functionality)
- the config utilities will only need an engine to load the settings from the ConfigurationTree to the screen
- all code will be grouped, which makes it easier to track bugs/add new features)
- a way to add search functionality
- a way to group settings from a single xml file, so this file will only have to be read and written once (major performance improvement)
The ConfigurationManager then loads all settings from the PluginTree to a ConfigurationTree.
This has some advantages, like:
- no duplicated code (in stead of each config-util needing its own load/store functionality)
- the config utilities will only need an engine to load the settings from the ConfigurationTree to the screen
- all code will be grouped, which makes it easier to track bugs/add new features)
- a way to add search functionality
- a way to group settings from a single xml file, so this file will only have to be read and written once (major performance improvement)