diff options
| author | Danilo M. <danix@danix.xyz> | 2026-09-16 09:23:17 +0200 |
|---|---|---|
| committer | Danilo M. <danix@danix.xyz> | 2026-09-16 09:23:17 +0200 |
| commit | 82dfcae2225e4313f400e87e97b1e5f42a0e7b3f (patch) | |
| tree | e6b04d7f25390ee861a23c169d91cb99a4916f0e /AGENTS.md | |
| parent | 6bb645eef6078bf8b8cb8f3b807e97e4b227c68c (diff) | |
| download | unified-desktop-theme-82dfcae2225e4313f400e87e97b1e5f42a0e7b3f.tar.gz unified-desktop-theme-82dfcae2225e4313f400e87e97b1e5f42a0e7b3f.zip | |
docs(gtk): record GTK as a generated consumer
AGENTS.md listed GTK3/GTK4 among the covered consumers, but nothing generated
or installed a theme for it: the claim had been aspirational since the repo
started. It now describes what the code does, and says plainly that the old
state was a gap rather than a drift.
templates/qt-gtk/ documented both Qt and GTK as installed from upstream. Qt
still derives from catppuccin/Kvantum and GTK from catppuccin/gtk, but both
are generated here now, so the table and the gsettings line say 'udt'. Its
tracked gtk3-settings.ini carried the old theme name too, which made the
record disagree with the live config it mirrors.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Diffstat (limited to 'AGENTS.md')
| -rw-r--r-- | AGENTS.md | 17 |
1 files changed, 15 insertions, 2 deletions
@@ -43,7 +43,9 @@ The generated set is `rofi/udt/palette.rasi`, `templates/terminal/kitty-theme.conf`, `templates/homepage/custom.css`, `templates/kvantum/theme.{kvconfig,svg}`, `templates/sublime/udt.sublime-color-scheme`, -`templates/sublime/udt.sublime-theme` and `bin/udt_colors.py`. +`templates/sublime/udt.sublime-theme`, `templates/gtk/gtk{3,4}.css`, +`templates/gtk/index.theme`, `templates/gtk/assets/*.svg` and +`bin/udt_colors.py`. Sublime is two outputs, not one. The **colour scheme** is the editor pane and tracks the wallpaper accent. The **theme** is the UI chrome, and is an override @@ -60,7 +62,8 @@ Material Behave's own `material_theme_contrast_mode` block, which re-tints the sidebar and status bar, and carry no settings gate of its own, or contrast mode wins. Removing the Materialize package leaves the override inert. -Qt and GTK apps reach the palette through Kvantum. Its theme is a `.kvconfig` +Qt apps reach the palette through Kvantum; GTK has its own generated theme. +Kvantum's theme is a `.kvconfig` of colours plus a `.svg` of widget artwork with the colours baked into the paths, so both are templates: the twelve palette colours are placeholders and the fifteen neutral greys are left alone, because those are shading rather than @@ -69,6 +72,16 @@ every scheme, so switching needs no change to `kvantum.kvconfig` and leaves no stale theme behind. Derived from `catppuccin-macchiato-lavender`, which this desktop was already running by hand. +**GTK is generated, not installed from upstream.** It used to sit on a +hardcoded `catppuccin-macchiato-lavender-standard+default` from `catppuccin/gtk`, +which meant every GTK app stayed Macchiato while the rest of the desktop moved +to another scheme. That was a gap rather than a drift: nothing ever generated +or installed a GTK theme, though this file claimed GTK was covered. The two +stylesheets and their 67 widget assets are now templates rendered into +`~/.themes/udt`, under one fixed name for every scheme so gsettings and the +GTK4 symlink are set once. See `templates/gtk/README.md` for what is +substituted and what is deliberately left as upstream drew it. + **Qt apps only read a theme at startup**, so a running one keeps the old colours until restarted. `install.sh` cannot signal them and does not try. |