Design management of the JSON config

[MatthewColvin]

Potential requirements

• Have one top level file that can reference other files
• Allow for schema validation
  • when booting do validation on files and mark some invalid and notify the user of issues
  • maybe build some sort of cache to remember bad files
• Creation of UI lazily by reading files
• Need to have something very similar for Actions/Commands as we do for UI elements

Design Ideas

• Factories for different types of UI elements that compose upon one another to help keep thinks broken up when parsing
• Allow Custom C++ pages/widgets to be created with their own custom schema
  • Maybe we need an enum class to help the factory validate and produce widgets

Random Thoughts:
How can we leverage reflection to have JSON reference C++ code?
It would be sweet if the leverage construction argument names ask keys for the json.
Could have some sort of cheap check function built into the base type of the factory.