The motivation is to be able to group, manage and load several configurations (LQI Grid, plugins, etc.) from one place. In this way when a user is working on a particular task type or customer assignment then s/he can keep all configurations relevant for that task in one folder and load them all at once.
Proposal is to create .ocelot/config/default as a baseline folder in which we'll ship default configurations. An end user can then create other folders (e.g. .ocelot/config/myprefs) and put their own modified configurations there.
Upon first launch Ocelot will display a dialog informing that the default configurations are being loaded and an option to load another. This dialog will be capable of being turned off.
The last configuration loaded will be loaded on subsequent launches and this will be serialzed in .ocelot/config/last-session.json.