TESTAR_dev
TESTAR_dev copied to clipboard
[Refactor] Discuss the structure of the test.settings file
Right now, every time we change between protocols user needs to customize all settings again. Because settings are protocol specific.
- Maybe divide the test.settings into two different files:
- main.settings
- protocol.settings The protocol can be the priority and override the main file.
- Maybe add a list, text, or table panel to the GUI that loads all the settings.
Possible idea for settings formatting:
- Current settings file might contain too much explanatory text (we can reduce text)
- Plain text may not be suitable for more complicated nested settings structures (e.g., a more advanced abstraction based on types of widgets); a different format, such as YAML or another markup language, could provide more flexibility.