makiolaj
19ee678a1b
Every widget instance can now follow the system or be pinned to Light or Dark, and on Android 12+ turn the wallpaper's colours off in favour of the app's own palette. Both are set in the widget's config screen and stored in its own Glance state; an instance without them keeps today's look. Glance content takes them through WidgetTheme. The plain-RemoteViews parts (the analog and digital faces, readouts and chronometers) go through a new WidgetPalette, which resolves the widget_* palette under a forced day/night and sets concrete colours, or day/night pairs, on the views. The app's own tones are now widget_app_*, so they stay reachable on API 31+. The analog and digital clocks are re-coloured on API 31+ only: below that AnalogClock's hands and a shape's background tint can't be set through RemoteViews, so their config screens don't offer it. The next-alarm and timer widgets gain a config screen for this (configuration_optional, so placing one doesn't stop there). The analog, stopwatch and quick-timer config screens become settings screens with an OK, like the digital clock's, since they now hold more than one choice. Background opacity is left out: most faces are a shape with text in its container colour rather than a card, so there is no background to fade without losing contrast against the wallpaper. Closes #6
Clockula
A modern Material 3 Expressive clock app for Android.
Alarms, timers, stopwatch and world clock. Open standards, no account required.
Clockula is the clock sibling to Calendula
(calendar) and Agendula (tasks). The
name follows theirs: clock, given Calendula's -ula ending. A Calendula flower
head is botanically a cluster of many small florets, so the three apps are
florets of one bloom — and they share one, floret-kit.
🚧 Early development. The spec is locked; the app is being built. See
docs/ROADMAP.mdfor where it actually is.
The honest difference from its siblings
Calendula is a pure front-end over Android's CalendarContract. Agendula speaks
the dmfs TaskContract. Both put a good interface on a standard someone else
already maintains.
There is no open provider behind a clock. Alarms, timers and laps are
Clockula's own data, so Clockula is the first app in the family to own its
storage — by design, not as a fallback. What that commitment is replaced with is
the first section of docs/PLAN.md, and it comes down to three
things:
- Clockula speaks Android's standard alarm contract. It implements
android.provider.AlarmClockin full, so your assistant and your automation apps can set alarms and timers in it exactly as they would in any stock clock, and the system status bar and lock screen show its next alarm. - World clocks are IANA time zones, not a bespoke city list that goes stale.
- Your data exports to a documented, versioned JSON file whenever you want it, because data you can't take with you isn't really yours.
Alarms that actually ring
An alarm app is only worth having if you can trust it, so Clockula treats that as the feature rather than the plumbing. Alarms are scheduled as real alarm clocks — doze-exempt, visible to the system — and re-resolved against your current time zone whenever anything moves underneath them, so DST and travel don't silently shift them.
When something on your device would stop an alarm ringing, Clockula tells you which setting it is and takes you there, instead of failing quietly at 7am.
Documentation
Start with docs/: PLAN.md is the spec and the
reasoning, ROADMAP.md is the status,
ARCHITECTURE.md is how the code is put together, and
RELEASING.md is the release runbook.
Building
git clone --recurse-submodules https://codeberg.org/jlmakiola/clockula.git
cd clockula
./gradlew assembleDebug
floret-kit is a submodule built from source as a Gradle composite build, so
--recurse-submodules is not optional. The included build needs to find the
Android SDK on its own: either export ANDROID_HOME, or drop a sdk.dir=… line
in a (gitignored) floret-kit/local.properties.
Licence
MIT — see LICENSE.