FR: less args upon run

[LeandroMarceddu]

Using binary ./frominput.js ./baseconfig.js will probably be confusing to less-pc-literate people.

Maybe implement frominput.js (in perhaps another name) automatically and make the user provide only one more arg?

We should divide up which config settings we want static and which ones we want dynamic

[GijsvanDulmen]

Ok. Proposal:
1)
./platerflow => uses settings.js (previous baseconfig) and prints.js (previous frominput.js).

./platerflow ./prints-for-customer.js => uses settings.js and prints-for-customer.js

./platerflow ./prints-for-customer.js ./other-settings => uses other-settings.js and prints-for-customer.js

[LeandroMarceddu]

Proposal:

4. ./platerflow --argument1=value1 --set=set2 -> uses settings.js, one giant settings file.
   This would require maybe an external/extra binary/app for generating a settingsfile to make it more convenient for them

[GijsvanDulmen]

Yeah, the fact that we use a config file based approach makes it simple to save a bunch of configuration files for a few different things you want to re-platter/slice/upload a lot.

[LeandroMarceddu]

Perhaps the introduction of sets can be used to generate a per-set settings-override? E.G load value on start up, then load values in set again, overwriting the general config one?

[GijsvanDulmen]

This makes a bit more easy. More work to be done on this part.
01f3e27