New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Refactor] Discuss the structure of the test.settings file #335

Open

ferpasri opened this issue Feb 23, 2023 · 1 comment

Labels

priority: medium status: not assigned type: refactor

Projects

Refactoring TESTAR code

Member

ferpasri commented Feb 23, 2023 •

edited

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.

ferpasri added priority: medium status: not assigned type: refactor labels

Collaborator

oliviarves commented Apr 3, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment