makiolaj
ef26d433e1
A snackbar the screen leaves unanswered (another tab, Settings, the app closing) now counts as expired, except across a rotation. Held back, it could restore a snapshot from hours ago, ring a long-gone timer, or land on top of a backup restored in the meantime. One shared UndoSnackbarEffect does this for alarms and timers. The engines' delete and restore run non-cancellable, so a caller cancelled half-way cannot leave a restored alarm unscheduled. The editor writes the label still in flight before it deletes, so Undo brings back what was typed. The swipe counts the touch-slop overshoot, keeps a card flung back towards the start, slides a card home if its row is still there a second after the delete, and no longer recomposes on every drag frame.
Clockula — documentation
Clockula is a Material 3 Expressive clock app for Android: alarms, timers,
stopwatch and world clock. Third floret of the bloom, after
Calendula (calendar) and
Agendula (tasks). See the top-level
../README.md for the pitch.
Unlike its siblings, Clockula owns its storage, because there is no open provider behind
a clock. What that costs and how the open-standards commitment is honoured anyway
is the first section of PLAN.md.
Index
| Doc | What it covers |
|---|---|
PLAN.md |
The spec. Thesis, locked decisions, the alarm engine, data model, system interop, identity, pipeline, and how ClockMaster is used. The "why". |
ROADMAP.md |
Status and the work queue: milestones M0–M11 and post-v1. What the build loop works through. |
ARCHITECTURE.md |
How Clockula is built today: layers, the data seam, the alarm engine, DI, build/tooling, manifest. Written from M2 onward. |
RELEASING.md |
How to cut a release. Written at M0 alongside the pipeline. |
PROVENANCE.md |
Third-party code and assets carried in-tree, and under what licence (PLAN.md §11). |
Also: ../CHANGELOG.md (Keep a Changelog format; tag sections
feed the release notes).
How the docs relate
- PLAN is the design decisions (stable; the "why").
- ARCHITECTURE is the current shape of the code (kept in sync as it grows).
- ROADMAP is the moving status layer (updated as milestones land).
- RELEASING is the operational runbook.