makiolaj
f5388042c6
Issue #24 asks for Google Clock's "automatic home clock": a temporary Home row while the device is somewhere the time differs from home. In Google Clock that works because the hero clock is local time. Clockula is the other way round: the hero face is home (the stored home zone, or the device's zone when none is stored), every row is read against home, and with a stored home the face already shows home time on a trip. A Home row would only repeat the face; what goes missing while travelling is the local time. So the feature is turned round. With a home zone stored and the device's zone on a different UTC offset right now, the tab shows the device's zone as a temporary "Local time" row between the face and the saved cities. It is never stored, sits outside the reorderable column, has no move or remove actions and does not count towards the 24-city cap. The comparison is the current UTC offset, as Google's is, so Paris with home in Berlin shows nothing. The row is hidden when a saved city is already on the device's offset. It is rebuilt on every tick from the same device-zone read the face uses, so it appears and disappears within a tick of a time-zone change while the tab is open. Home that follows the device can never differ from it. Settings > Clock gets an "Automatic local clock" switch (on by default) under the home zone row; while home follows the device the row is dimmed and its hint says it needs a home time zone. The switch is stored as automatic_local_clock and included in backups. Files written before this change restore it as on. Fixes #24
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.