Keep settings tuned for one theme from applying under every other theme
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start with Sources/StableBar/ThemeConfiguration.swift and Sources/StableBar/ConfigurationLoader.swift to understand profile conditions and when the selected theme is resolved; then read Sources/StableBar/WidgetPackage.swift and Sources/StableBar/Configuration.swift for theme and configuration validation. The proposal also spans profile editing, Theme and widget Style settings, and undoable configuration changes, so identify those entry points before estimating implementation. Done means theme conditions match the selected theme as described and theme scoped settings can be edited and migrated in Settings.
Written by the indexing model from the issue text.
Description
Problem
A theme can't hold everything its look needs. A theme may contain only tokens, defaults, popupDefaults, roles, workspaceDefaults, bar, groups and profiles (validateThemeDocument in Sources/StableBar/WidgetPackage.swift), so the rest of the look goes in the main file:
- widget paddings sized for the theme's pills
- a clock drawn as an accent chip
- a filled slider style
- an Apple menu symbol
- a package widget's layout in
widgetOverrides - empty
groupsentries, needed only because a widget in a group the theme doesn't define fails the whole configuration ("Unknown group" inSources/StableBar/Configuration.swift)
Those values apply under every theme. Switch from Fern to Nord and the clock is still an @token.accent chip, and the widgets keep paddings meant for pills. Theme lists the values below the gallery, and Reset them deletes them, so going back to Fern means doing the work again.
Profiles can't help: they match appearance, onBattery, displayCount, externalDisplay and app (ProfileConditions in Sources/StableBar/ThemeConfiguration.swift), not the theme.
Proposal
-
A
themeprofile condition that matches the selected theme's ID, at any version, with"built-in"for Built-in:"profiles": [ { "name": "Fern", "when": { "theme": "fern" }, "configuration": { "widgetOverrides": { "date": { "group": "clock", "background": "@token.accent" }, "battery": { "group": "status", "style": { "paddingHorizontal": 12 } } }, "groups": { "clock": { "style": { "paddingLeading": 3 } } } } } ]composeFilesinSources/StableBar/ConfigurationLoader.swiftsettles the theme before profiles apply, including a screen setup's own theme and the theme Try Themes shows, so the condition reads that theme and a profile can't change it in a loop. Group memberships can move into the profile too, so the main file no longer needs emptygroups. Versions that don't know the condition never match it (Files from a newer StableBar), so the profile just stays off there. -
Settings → Profiles → + Condition offers Theme, listing the built-in and installed themes.
-
At the top of Theme and in a widget's Style tab, a scope switch: Every theme or Only with Fern. With Only with Fern, changes save into a profile with that condition, created on first use, the way Edit the bar for this profile saves into a profile today.
-
When the main file overrides the theme, Theme's notice offers to keep those values with a theme as well as Reset them: it moves them into that theme's profile in one undoable change.
The exact wording and placement of the switch and the notice are a matter of taste; renders of a few options can follow in a comment.
Possible today
Partly. Put the settings in a profile without when and turn it off with "enabled": false when switching theme, or pin it with "profile" or StableBar --profile. Pinning turns off automatic matching for every other profile, and nothing ties either way to the theme.
Related
- #81 asked for profile conditions set by commands and was closed as not planned ("
--profilecovers most of it"). The theme is different: StableBar already knows it, and pinning a profile turns off automatic matching for the others. - #28 stopped colors that StableBar wrote from overriding a chosen theme, #30 lists what overrides the theme, and Save as Theme (#91, #143) moves the shared look into a theme but leaves widget styles in the main file.
- #648 (open) adds group editing in Settings, which writes
groupsand widgetgroup. - Themes that carry named looks (any role name, with roles and groups the theme lacks ignored) were considered instead. They would let a theme package ship reusable looks, but they change what a role is, and they can't hold a widget's own layout or symbol.
Triaged by Claude Code (Claude Opus 5.5).
- Dominant language
- Swift
- Stars
- 184
- Forks
- 12
- Avg merge
- 3h 50m
- Merged PRs (30d)
- 387
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Seb-GRAF/StableBar
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 52/100
Maintainers usually reply within 1 day
-
Menu bar items drawn as in the menu bar show the wrong part of the menu bar after a display changePossibly taken @Jonathanm10 claimed this today. Openneeds-triage
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 30/100
Maintainers usually reply within 1 day
-
Allow the App Menu to display the frontmost app iconPossibly taken @khatami10 claimed this today. Openenhancement needs-triage
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
All issues in Seb-GRAF/StableBar
Similar issues
-
good first issue help wanted testing
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
area:cli documentation good first issue priority:low
Difficulty 1/5 Under an hour Newbie friendliness 94/100
isaaclins/freesnitch#430 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
MasterJ93/ATProtoKit#354 ·
-
enhancement help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
heysidhant/appvanish#4 ·
-
bug priority:low status:queued
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day