Import and export Preferences #84
Description
There could be a JSON representation of the Preferences that can be setup in Live with Import/Export functionality for the following use cases:
- saving preferences for later use or backup
- migrating user preferences to another computer
- sharing preferences with other users
- enabling manufacturers to distribute drone-HW specific preferences with their clients (e.g. battery settings, tolerable takeoff distance, max polygon vertex count in geofences etc.)
The following requirements are needed when implementing Preferences import/export:
- each item in the Preferences shall have an "exportable" flag to avoid exporing superfluous stuff (e.g. map origin etc.)
- the JSON representation hierarchy should follow the structure of tabs on the Preferences dialog
- the JSON representation of preferences to import can be any subset of preferences
- migrations on variable renaming or preferences restructuring should be handled properly
- each loaded/imported setting should have validation on import. And at least part of this validation should be performed globally when all settings are loaded, as some settings might be dependent on others (e.g. battery full charge must be higher than low threshold, which should be higher than critical threshold etc.)
Regarding UX, I suggest to have a dropdown on pressing the Preferences widget with three items corresponding to import, export and edit preferences (edit corresponding to the current version of opening the Preferences dialog).