To Do
Tasks from Microsoft To Do or Google Tasks, or local lists that need no account at all.
What it does
Shows one task list, with a circle to tick things off and an “Add task” row at the bottom that becomes an inline input when clicked. Due dates render as overdue, today, tomorrow, a short weekday, or a date, with past-due items on incomplete tasks highlighted. High-importance tasks carry a ! badge.
Long task titles wrap rather than being cut off mid-word, up to a number of lines you choose; only past that do they ellipsize, with the full text in the tooltip.
Two sources
Account mode pulls from Microsoft To Do or Google Tasks, syncing both ways.
Local mode needs no account at all. “This device” owns its own named lists, created and renamed from the config panel. These lists are device-wide rather than owned by a widget, which has three consequences worth knowing:
- Renaming a list retitles every widget showing it, immediately.
- Deleting a widget does not destroy its tasks.
- Two widgets can show the same list.
Local lists are included in Themia’s import/export, so they survive a move to a new machine.
Where the data comes from
In account mode, directly from Microsoft or Google over their own APIs, authorized through their OAuth flow. In local mode, nothing leaves the machine: tasks are stored on disk with the rest of your Themia configuration.
Due dates get careful handling: the two backends encode a due day as a timestamp in two different ways, and a naive conversion shifts tasks by a day for anyone west of UTC. Themia resolves both encodings so “due today” means today wherever you are.
Limits
- One list per widget.
- Local tasks are title and done-state only: no due dates, importance or recurrence, since a local task has no source for them.
- Deleting a local list that still has tasks is unrecoverable and asks for confirmation first.