diff options
| author | dam <dam@gudinoff> | 2022-10-17 23:32:10 +0000 |
|---|---|---|
| committer | dam <dam@gudinoff> | 2022-10-17 23:32:10 +0000 |
| commit | ab4ce6148563b21b6d41b09a2448bd63765ffa21 (patch) | |
| tree | d731c45f913cdb2f423017400d6f9ad3d1ba0332 /readme.md | |
| parent | a915b49f8d46e9d861bd9755a9a9a4d67aa45771 (diff) | |
| download | task-time-tracker-ab4ce6148563b21b6d41b09a2448bd63765ffa21.tar.zst task-time-tracker-ab4ce6148563b21b6d41b09a2448bd63765ffa21.zip | |
Improved compilation commands. Added bonus items to to-do list.
Diffstat (limited to 'readme.md')
| -rw-r--r-- | readme.md | 7 |
1 files changed, 5 insertions, 2 deletions
@@ -55,9 +55,12 @@ Task Time Tracker - [x] Add/remove time using keys: `F3`; - [x] Add/remove time for any day of week; - [x] Total times may saturate, but before that the user will see the infinite symbol. Solution: Provide user with possibility to refresh totals. -- [ ] After user input, we should save the changes on the database... or defer them and check every few seconds if we need to save. -- [ ] REVISE ALL CODE ptrdiff_t/size_t (signed/unsigned)! - [ ] Implement logs as described above. +- [ ] Improve the way we save the changes made to the database: + - When operating on the archive, will we keep the saves synchronous? + - Maybe add a cooldown timer and save changes after it times out? + - Maybe add a partial-save when (de)activating a task (just save the task and the database core? +- [ ] REVISE ALL CODE ptrdiff_t/size_t (signed/unsigned)! - [ ] Go over all `TODO` items; - [ ] Cleanup `draw_tui`: - Selected and active tasks should be drawn after everything else. |