zlacker

[parent] [thread] 3 comments
1. nikau+(OP)[view] [source] 2022-09-25 06:36:22
This isn't either/or - you can have a nice preferences GUI and a sensible yaml or toml config file backend.
replies(1): >>pjmlp+a2
2. pjmlp+a2[view] [source] 2022-09-25 07:12:44
>>nikau+(OP)
Except on Linux usually most environments stop at the config file part. And if a GUI tool happens to exist, it isn't kept in sync with the file format.
replies(1): >>nikau+P2
◧◩
3. nikau+P2[view] [source] [discussion] 2022-09-25 07:20:39
>>pjmlp+a2
Yes - ideally there should be a standard library for this. There is no reason the GUI cant update the config file and refresh from it when it updates.
replies(1): >>bee_ri+011
◧◩◪
4. bee_ri+011[view] [source] [discussion] 2022-09-25 16:57:58
>>nikau+P2
A convention for writing JSON, YAML, or whatever config files that standardized types of options, their default, and something about their types (is it a toggleable boolean, a bounded continuous value, an integer, etc etc) could be nice. It might be possible to provide enough info automatically generate the GUI (draw the first as a button, the second as a slider, and the third as a number box), and that sort of info would be helpful to have if you were writing the file by hand anyway.
[go to top]