Let's list the todo items, completion of which will indicate we have reached 1.0. As we list and start each of these things we can create separate issues to track or ask questions, but wanted to take the questions from the software architecture document and juice them into a todo-list taped to the repo.
Comment and i'll add to this list.
I'll make a separate issue for stuff we'd like to have but don't need to have in order to reach v1.0. let me know if anything i've put here needs to be moved there.
[x] Controller, Alarm Manager, GUI - Ability for controller to send technical/hardware alarms to alarm manager to be displayed by GUI (reimplement get_alarms in controller, coordinator will poll and send to alarm manager?)
[x] Controller, Coordinator, GUI - heartbeating to track state of each component
[ ] Configuration - We need to pull out any hard-coded parameters that should be controllable by the user and add them to vent.common.prefs . prefs should keep a .json file updated in the ~/vent directory.
Let's list the todo items, completion of which will indicate we have reached 1.0. As we list and start each of these things we can create separate issues to track or ask questions, but wanted to take the questions from the software architecture document and juice them into a todo-list taped to the repo.
Comment and i'll add to this list.
I'll make a separate issue for stuff we'd like to have but don't need to have in order to reach v1.0. let me know if anything i've put here needs to be moved there.
DEBUG
level for anything cyclical,INFO
for discrete events like user interactions, initialization events, etc.prefs
should maintain persistent system preferences like hardware configuration, update times, etc.vent.common.prefs
.prefs
should keep a.json
file updated in the~/vent
directory.