Think about vehicle UI provider source
- Should we allow vehicle plugins to provide UI ?
- Should kirogi provide the UI for the
About 1., can result in a crappy UI with a windows 95 style where anyone can create the UI and resulting in a non uniform UI/UX problem, where each vehicle has it's own configuration and UI/UX.
About 2., we'll have an uniform UI/UX where kirogi code will try to deal with everything via information provided by each vehicle actions/capabilities.
This issue should be improved to seek 2. approach, showing how different and what kind of capabilities
AbstractVehicle should deal with, if we fail to provide such thing, 1. could be a valid solution.