I really like trying out tools that allow me to organize and track tasks, as they help me keep focused and more motivated if I know where I am, what I have done and what I need to do.<p>Grit is really cool, the name feels a bit unfortunate as it might have muscle memory overlap with “git” - nothing that can’t be solved with an alias but perhaps something to ponder.<p>I also sadly see limited use for a task tracking system that I don’t have with me at all times - I would love a way to use grit on my phone and desktop computer with some kind of sync. Otherwise it would be limited to tracking work-related stuff as when I’m not working I really don’t use the computer; the grocery list example was really nice but I don’t carry my laptop to the grocery store :)<p>I really like Grit, will keep an eye on how it evolves.
I've been working in this space for my own task manager (multi-parent + infinite depth), and here's a couple things I've landed on:<p>- My objective is being able to show a "todo" list that is _actually actionable_. So I think early on its important to build in notions of "availability" (i.e. "this is not waiting on something else, you can work on this now")<p>- The dual is you kind of need nodes that represent "blockers". Here you have the parenting mechnaism that could get you there, but also stuff like setting dates on nodes (in Omnifocus this looks like the "defer until" date)<p>- I tried making a UI that handled N-node depth, but ended up figuring out that just displaying at most 2 levels of depth and then having fast loading when zooming in/out saved me a lot of API design headache and gets me 95% of the way there<p>- Even if your data is a tree structure, a lot of times just showing a flat list (perhaps with "parent node is X" annotation) is going to work out nicer. Notably with search
What's the difference between a dag and a multitree? The wikipedia article was confusing - it seems that it prevents diamond shapes? Like where 1 leads to both 2 and 3, and where 2 and 3 both lead to 4?
I use a flat text file with exactly this structure, just indenting when I need a new layer.<p>I tried fiddling with it with vim folds but in the end just ended up deleting things I finish.<p>I learned this from a friend at work.
I just started migrating to taskwarrior which great due to the many clients. Actually its integration with vimwiki via the taskwiki plugin [1] is quite powerfull allowing editable views. Wonder if this dag aproach could be integrated via metadata without loosing compatibility.<p>[1] <a href="https://github.com/tools-life/taskwiki" rel="nofollow">https://github.com/tools-life/taskwiki</a>
TiddlyWiki uses a similar data model for table of contents by default and I love it! I think the multitree constraint is a good idea over a general DAG.
Wow a very cool idea. The idea of many root nodes for different views seems interesting.
Unfortunatly it does not build on my pc, it seems to import an absolute path in the go build command of the Makefile, which it can not do. (cannot import absolute path)<p>Since I never really worked with go, I don't know where to start here.
I've seen similar task management that syncs to CalDav:<p><a href="https://f-droid.org/en/packages/org.dmfs.tasks/" rel="nofollow">https://f-droid.org/en/packages/org.dmfs.tasks/</a><p>Is this something you're thinking about adding?
I’m going to play with this as well since I’m learning about the whole tasks/notes space.<p>Do you have plans to support any form of sync? Like CalDAV or some API on top of which CalDAV or another sync method can be implemented?
Not a CUI but Seatable has been a tremendous help to keep my to-do in a easy to use web interface that supports mobile pretty well.<p>You can also self host it.
If you add confidence interval estimates to each task and a way of inputting the amount of time you can allocate to grit-managed tasks, you could calculate estimated task completion dates: <a href="https://www.liquidplanner.com/support/articles/statistically-correct-totals/" rel="nofollow">https://www.liquidplanner.com/support/articles/statistically...</a>