grit VS todo.txt

This is cool, but the killer feature I'm looking for is a UI to accomplish the functionality of grit https://github.com/climech/grit. Grit itself isn't particularly functional, but its write-up in the readme hasn't been fully realized by any task tracking software (as far as I'm aware).

*

By specifying order through indentation, we've now created a DAG for what needs to be done, in what order, with the most actionable tasks having the largest indentation. This is how I organize my plaintext to-do files, but afaict no todo list software is able to handle this gracefully- with the exception of grit, which is more of an experiment (but the readme is incredibly well written and describes DAG problem to a tee).

https://github.com/climech/grit

Does anyone know if org-mode handles complex trees? All the examples I've found online were trivial (i.e. one task deep)

Seems like it uses sqlite. Presumably it's trivial to sync using whatever file sync tool you want (Dropbox, or whatever) as long as you're fine without concurrent editing. For that you'd need application support or a more amenable data structure.

https://github.com/climech/grit/blob/master/db/db.go

It would be awesome to have an option to sync to/from a text file in the todo.txt format. This is a plain text format for tasks which can be read by different apps on different platforms.

For this project: Make a todo.txt file in the root. Don't go overboard, just note the tasks as you realize them as "(B) Add Audio System". Break them down into components when you realize tasks will take more than one sit-down, "(A) Put AudioDefs into an array \n (B) Load each of the filedata into a stack". Personally, I use (A) for "This is on the schedule", (B) "Do this today", etc.

Another way is to use the todo.txt approach and add context tags like "@work" to the text of the task, and then filter the big Tasks list by searching for that context tag.

todo.txt on linux (format definition, tool -- available in most package repos also I think, though the name is not always the same!)

Privat mittlerweile nach Todo.txt-Aufbau https://github.com/todotxt/todo.txt/blob/master/description.svg

Actually, it's org-mode. But for the rest of us non-Emacs users, there's todo.txt:

https://github.com/todotxt/todo.txt

Otherwise, maybe go old school and use a todo.txt type workflow?