mrwatson-de
commented
1 year ago I was thinking about this today, and thinking how different users could well want identical standard setups - except for the GUI language.
Presenting users with a checkbox list of the available configs could be really easily to implement, something like:
- [ ] StdUser001
- [ ] PwrUser001
- [ ] FM-DE-German
- [ ] FM-EN-English
- [ ] FM-ES-Spanish
- [ ] etc.
The list that results from checking the boxes could simply be passed to the setup script, and applied sequentially.
This simple solution would solve most of the problems of combining users multidimensional requirements.
Note: Currently, setting the language automatically is only implemented on Windows, where it is a simple FileMaker setting.
An alternative, and slightly easier, solution to the need for Modularity in the configurations could be for the apply config Scripts to accept a list of configuration identifiers.
fmSetupAssistant would loop over the list and apply the configurations one after the other.
Simplest would be a single text list of calls where each value can be a ConfigID or a UUID (or ? a search phrase?)