First of, awesome tool! Great work, very useful and impressive.
One of the problem I've faced is: when tasks inserted, file is created in the cwd, it's not very convenient.
ie: problem is finding the file eventually if application is run in the another directory next time.
There could be few solutions:
-
initially filename might be something like ~/task_manager_data.json (not sure if it plays well with Windows etc, probably platform dependent values could be used)
modified here:
|
const DATA_FILE: &str = "task_manager_data.json"; |
-
popup on first run asking for a file (that is probably the most complicated solution with variety of edge cases)
-
using something like sqlx & sqlite or other (that's probably the most robust solution)
First of, awesome tool! Great work, very useful and impressive.
One of the problem I've faced is: when tasks inserted, file is created in the cwd, it's not very convenient.
ie: problem is finding the file eventually if application is run in the another directory next time.
There could be few solutions:
initially filename might be something like ~/task_manager_data.json (not sure if it plays well with Windows etc, probably platform dependent values could be used)
modified here:
taskim/src/data.rs
Line 5 in b5c0775
popup on first run asking for a file (that is probably the most complicated solution with variety of edge cases)
using something like sqlx & sqlite or other (that's probably the most robust solution)