fmSetupAssistant: Config lists

[mrwatson-de]

Config lists are, unsurprisingly, a list of configurations, which can be applied one after the other. That means where configurations contain the same setting, the last configuration in the list wins since it overrides the previous Setting.

Examples:

• GBS Advanter user workplace
  1. GBS Basic user workplace
  2. GBS advanter User start file
• MrWatson's workplace
  1. GBS Developer workplace
  2. Start file fmLaunchPad
  3. …

Indeed , a Natural extension of this would be for config lists to be a list of configurations OR config lists.

Where one configuration list contains another configuration list and the contained configuration list will be applied in its normal way sequentially as one would expect.

This of course will require, checking to avoid infinite loops.

[mrwatson-de]

Of course, a possibly simpler implementation would be for configurations to be able to contain other configurations.

This would possibly be easier to implement, and would Maybe make the UX better?

Selecting a config list configuration would require the settings of each sub-configuration to be added to the current found set of settings and updated with the corresponding values, so that at the end you have a combined set of settings with the values set correctly.

Note that, while this would be the best way of selecting, applying and reporting on a config list, it would not be possible to save changes to the settings back to the config list.

[mrwatson-de]

Config lists

• will help avoid having to repeat the same settings in multiple configurations
• will make it possible to build up configurations from smaller pieces.
• will make maintenance of configurations much easier, since configurations will be DRYer