mirror of
https://github.com/Felitendo/spotifast.git
synced 2026-11-01 17:33:26 +01:00
Carmine Paolino
8646630a39
Palette files, the background catalogue, the settings cache format and the Omarchy integration now come from fastframe-theme. Spotifast keeps its palette (as an implementation of the crate's Palette trait), its wording of the catalogue's status, the picker, and two pieces of its own: upgrading a Fastpotify-era Omarchy hook, and leaving the desktop alone during an updater trial of the legacy profile. The eight shared palettes stay out of the picker. Cached themes in settings.json read as before, and the shipped hook and template are tested against the crate's so they cannot drift. The Omarchy fixtures move to the crate. Behaviour changes, from ZapFast's newer copy of the same code: - Omarchy is followed on any Omarchy desktop, including portable and Cargo builds, not only when a package installed its assets. The palette comes from Omarchy's rendering for Spotifast, or is rendered from the current theme's colours, instead of only from themes/omarchy.json. - On Linux the themes folder and Omarchy's current theme are watched with filesystem notifications, so edited palettes and desktop theme changes apply without the hook or `spotifast reload-themes`. - When Omarchy is followed but its palette cannot be read, Settings says so and keeps the last usable colours. The sentence is new, and translated in every catalog. - The updater trial of the legacy profile no longer follows Omarchy at all for that one launch, where it used to read the old palette file.