Add a light mode that keeps the same identity

Light is Tokyo Night Day, the palette's own light variant, rather than one invented to merely not be dark. Both share the same hues at different lightness, which is what lets the Prism signature survive the switch: blue still leads into orchid, it is simply a darker blue on a lighter ground. Every colour token became a binding on one boolean, so flipping it repaints the whole shell without any component needing to know it happened. That only worked because nothing outside Theme.qml defines a colour; the two places that did are fixed here. Surface alphas differ by scheme. The 0.34 that reads as glass over a dark desktop reads as haze over a light one, and text stops being legible on it. Two things that draw on this desktop do not read Panama's store: GTK applications, which read gsettings, and the compositor, which draws window borders. A toolbar or a border still wearing the other scheme is more jarring than either scheme on its own, so ColorScheme pushes the choice to both. It also pushes at startup, since a scheme chosen in a previous session would otherwise be in effect only for the shell. The unfocused window border follows too. It is a flat neutral, and a dark neutral is invisible against a light desktop. The focused border is the prism gradient and needs no variant. The live preview follows the scheme as well. A preview that stayed dark while the shell around it went light did not read as "your desktop", it read as a screenshot of someone else's. Claude-Session: https://claude.ai/code/session_01BRvzt4H8XXLPVH5MyYdk9L
2026-08-18 07:20:35 -04:00
parent d1b2cd2083
commit 9c574f9eb7
6 changed files with 177 additions and 30 deletions
@@ -0,0 +1,97 @@
+pragma Singleton
+
+// Keeps everything that draws a window agreeing about light or dark.
+//
+// The shell repaints itself from Theme.qml the moment the preference changes,
+// because every token there is a binding. Two other things draw on this desktop
+// and do not read Panama's store:
+//
+//   GTK applications          read gsettings colour-scheme and gtk-theme
+//   the compositor            draws window borders and shadows
+//
+// A toolbar or a window border still wearing the other scheme is more jarring
+// than either scheme on its own, which is why this exists rather than the
+// setting simply being a Theme property.
+
+import Quickshell
+import Quickshell.Io
+import QtQuick
+import qs.config
+
+Singleton {
+    id: root
+
+    readonly property bool dark: DesktopPreferences.get("colorScheme") !== "light"
+    property string lastError: ""
+
+    // Applied one command at a time: Process runs a single command, and several
+    // of these are separate programs.
+    property var pending: []
+
+    Process {
+        id: runner
+        onExited: (exitCode, exitStatus) => {
+            if (exitCode !== 0)
+                root.lastError = "The colour scheme could not be applied everywhere.";
+            root.drain();
+        }
+    }
+
+    function drain(): void {
+        if (runner.running || root.pending.length === 0)
+            return;
+        const next = root.pending[0];
+        root.pending = root.pending.slice(1);
+        runner.exec(next);
+    }
+
+    function enqueue(commands: var): void {
+        root.pending = root.pending.concat(commands);
+        root.drain();
+    }
+
+    // Pushed once at startup as well as on change: gsettings and the compositor
+    // do not read Panama's store, so a scheme chosen in a previous session is
+    // only in effect for the shell until this runs.
+    Component.onCompleted: settle.restart()
+
+    Timer {
+        id: settle
+        interval: 1200
+        onTriggered: root.apply()
+    }
+
+    Connections {
+        target: DesktopPreferences
+        function onRevisionChanged(): void { coalesce.restart(); }
+    }
+
+    Timer {
+        id: coalesce
+        interval: 250
+        onTriggered: root.apply()
+    }
+
+    function apply(): void {
+        root.lastError = "";
+
+        const scheme = root.dark ? "prefer-dark" : "prefer-light";
+        // Adwaita's light and dark are the same theme; only the preference and
+        // the -dark suffix differ, so applications that honour either agree.
+        const gtkTheme = root.dark ? "Adwaita-dark" : "Adwaita";
+
+        const commands = [
+            ["gsettings", "set", "org.gnome.desktop.interface", "color-scheme", scheme],
+            ["gsettings", "set", "org.gnome.desktop.interface", "gtk-theme", gtkTheme]
+        ];
+
+        // Unfocused window borders. The focused border is the prism gradient and
+        // is already scheme-independent; the inactive one is a flat neutral that
+        // would be invisible against the opposite background.
+        const inactive = root.dark ? "rgba(3b426199)" : "rgba(a8aecb99)";
+        commands.push(["hyprctl", "eval",
+            `hl.config({ general = { col = { inactive_border = "${inactive}" } } })`]);
+
+        root.enqueue(commands);
+    }
+}