makiolaj
2191166035
The countdown used the stock Material snackbar, while Agendula and Calendula confirm with floret-kit's SnackChip. It now opens as that chip: bottom-start in the FAB's band on the list, ellipsising short of the FAB, and in the editor's snackbar slot so it follows the predictive-back preview. It fills the band's height, as an Undo chip does in the other apps, and sits on the secondary container to stand apart from the cards. The chip has no timer, so AlarmSetChipBand holds it for a short snackbar's four seconds, stretched as the accessibility settings ask. The hand-over is unchanged: a chip cut short stays pending for the next resumed screen. Beside the FAB there is room for about 308 dp, so the message is now "Alarm in 7 hours and 12 minutes" rather than "Alarm set for … from now", which would have lost its number to the ellipsis. 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.