Split project into 2 components - GUI and daemon
After much deliberation a solution which feels very nice sauntered into my mind a few evenings ago...
The HyperWalker Display/GUI could be separate from the rest of the logic. This opens up some new possibilities, such as writing the GUI in a different language than the program doing the snapshot and data work. This would also separate the software into more manageable modules.
The current plan:
HyperWalker backend process
- CLI utility which takes a URI as an argument, makes a snapshot, and then returns the filename
- Eventually this could be a daemon with a proper API
HyperWalker GUI
- Widget events execute the CLI utility