makiolaj
207475ef37
The usual way to set an alarm is pick, OK, back, and back disposed the editor's snackbar a moment after it appeared. Day taps left within the one-second settle were never announced at all, and a rotation threw a showing snackbar away for good. The announcer is now an app-wide singleton holding the notice as state until a snackbar has run to the end, so the list picks up what the editor could not finish showing. An editor closed mid-settle announces on the way out. Announcing is serialised, so a quick on-then-off cannot land the "on" read last, and a notice nobody showed within ten seconds is dropped rather than shown stale. The engine's one-alarm read now shares upcoming()'s preview helper. Refs #19
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.