Hacker News Reader

Comment by kbd | Hacker News Reader

How do you handle ordering?

I noticed:

    $ grit add -p 5 Bread
    (5) -> (6)
    $ grit add -p 5 Milk
    (5) -> (7)
    $ grit add -p 5 Eggs
    (5) -> (8)

led to:

    ├──[ ] Get groceries (5)
    │   ├──[ ] Bread (6)
    │   ├──[ ] Eggs (8)
    │   └──[ ] Milk (7)

And I didn't see anything about reordering tasks in the readme. Is everything sorted by title?

View on HN

Yes, it's sorted by name in natural order. I haven't decided yet which would work best as default (this vs insertion order) -- feedback is welcome. This works well for numbered book chapters, something I personally find useful. In any case, the defaults will be configurable -- when I implement config :)

(Another thing on the TODO list is adding an optional priority score for each task, and sorting those on top of the list in all tree views.)

I hope you consider global prioritization of leaf nodes, either entered individually or calculated from weights of ancestor nodes.

One big deficiency of most todo apps is lack of support for making routes through the leaf nodes. I see that you can already do this with Grit via pointers and numeric task prefixes for sorting. But that brings us back to the bad old BASIC style line numbering problems.

With weights, you can have the user enter individual weight edges between root and task node, which would simplify the design, no?

Reply on news.ycombinator.com