3 ms·
[from TFA, quoted above] "When you mark a task as done in your TODO app, it just hides it." Those are some big assumptions and sweeping generalizations appar
by chrisweekly 5y ago
[from TFA, quoted above]
"When you mark a task as done in your TODO app, it just hides it."
Those are some big assumptions and sweeping generalizations apparently made by the author; for example, my system leverages Roam Research. In Roam, a key bit of UX is to type cmd+enter to prefix any block element (Roam's atomic unit, renderered as an HTML `<li>` list item) with a TODO checkbox, or to toggle its presence and state (TODO|DONE|nil). "DONE"
items persist in the UI wherever you created them. I take it further than leaving signs of my progress around -- I tag the more significant ones with `#FTW` ("for the win") to ensure I give myself credit and opportunity to celebrate. When I do my weekly review / planning sessions, the "DONE" items, and the wins, play a role.
- nl 5y agoFrom point (1) in the post: > The amount of things one can customize is really large, but making all this decisions has a cost.
- chrisweekly 5y agoI don't see how that's relevant; my comment was about the OP's assertion that completed TODOs disappear from view. In Roam, when toggling an item from TODO->DONE, the "DONE" items persist in the UI wherever you created them. (No extra decisions involved.)
- chrisweekly 5y agoSame holds true for Obsidian, too -- marking checklist items done styles them with strikethrough, but they remain visible.