-
Notifications
You must be signed in to change notification settings - Fork 1
Closed
Description
Though I'm personally happy with taskparser being completely terminal-based, some have suggested adding some form of GUI to it. Here's a few things to think about:
Read-only vs. Read/Write
This also applies to the current TUI. Should interfaces provide some level of write access to parsed files? I am vehemently against this as I'd rather keep taskparser work as a parser / viewer / compiler with hot-reload, much like the venerable marked viewer. Furthermore, I expect the technical effort required to provide reasonable guarantees of consistency and correctness to be very significant.
Native? Cross-platform? Web-based?
- Serving an HTML file that embeds a hot-reload script based on long-polling or SSEs is likely to be the option that requires the least amount of dependencies (likely zero) and have minimal impact onto
taskparseras a whole. - Using something like Electron is out of the question as it would introduce a disproportionate amount of buildtime and runtime complexity and dependencies, most of which would be left completely unused. I don't need another Chromium instance to manage my tasks.
- I'm open to evaluating bindings to native and cross-platform GUI libraries but so far I have not seen one that light enough that I would feel comfortable adding it to this project. Even
node-guiwould bring in too much stuff.
Metadata
Metadata
Assignees
Labels
No labels