KofTwentyTwo/carl
Archived
2
0 Fork 0
Code Issues 34 Actions Packages Projects Releases Wiki Activity

Provide light and dark palettes for the Carl theme once Next UI supports dual-palette application themes #32

New Issue
Open
opened 2026-10-02 12:08:24 +00:00 by KofTwentyTwo · 0 comments
KofTwentyTwo commented 2026-10-02 12:08:24 +00:00 (Migrated from github.com)
Copy link
Copy source

Summary

CarlTheme (src/main/java/com/kof22/carlai/CarlTheme.java) supplies a single palette through MaterialDashboardThemeMetaData, and that palette is the dark one (background #1b1b1b, surface #25282c, light text). The Next UI (RC8) disables dark mode whenever an application theme is applied and shows "This application theme requires light mode" in preferences, so the dark colours are currently painted onto a light-mode shell and the user's appearance preference is ignored.

Dependency

Upstream feature request in QRun-IO (qqq middleware allow-list plus qqq-frontend-next): optional dark palette on the theme model, dark tokens emitted under :root[data-theme="dark"], dark mode kept enabled when both palettes exist. James is filing that request.

Carl work once it ships

  1. Make the base palette a light version of the brand (same primary #0066cc / secondary #69b0ff, light background/surface/text, matching sidebar and table tokens).
  2. Move today's colours into the dark palette.
  3. Verify in the packaged browser suite that the appearance toggle switches palettes and that the preferences dialog no longer shows the light-mode notice.

Priority rationale

P2: visual quality and respects the user's appearance choice; blocked on upstream.

## Summary `CarlTheme` (`src/main/java/com/kof22/carlai/CarlTheme.java`) supplies a single palette through `MaterialDashboardThemeMetaData`, and that palette is the dark one (background `#1b1b1b`, surface `#25282c`, light text). The Next UI (RC8) disables dark mode whenever an application theme is applied and shows "This application theme requires light mode" in preferences, so the dark colours are currently painted onto a light-mode shell and the user's appearance preference is ignored. ## Dependency Upstream feature request in QRun-IO (qqq middleware allow-list plus qqq-frontend-next): optional dark palette on the theme model, dark tokens emitted under `:root[data-theme="dark"]`, dark mode kept enabled when both palettes exist. James is filing that request. ## Carl work once it ships 1. Make the base palette a light version of the brand (same primary `#0066cc` / secondary `#69b0ff`, light background/surface/text, matching sidebar and table tokens). 2. Move today's colours into the dark palette. 3. Verify in the packaged browser suite that the appearance toggle switches palettes and that the preferences dialog no longer shows the light-mode notice. ## Priority rationale P2: visual quality and respects the user's appearance choice; blocked on upstream.
This repo is archived. You cannot comment on issues.
No Branch/Tag Specified
Labels
Clear labels
accessibility
Barrier affecting people with disabilities
 audit-2026-10-01
Found by the October 1 2026 full codebase audit
 bug
Something isn't working
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 priority: P0
Critical: blocks release or is a correctness/security defect
 priority: P1
High: must fix before next release
 priority: P2
Medium: should fix soon
 priority: P3
Low: cleanup or nice to have
 question
Further information is requested
 tech-debt
Bloat, dead code, or housekeeping
 wontfix
This will not be worked on
No labels enhancement priority: P2
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
forge-recovery (Forge Recovery) james.maes (James Maes)
No Assignees
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: KofTwentyTwo/carl#32