#73 dynamic color scheme presets from .txt palettes + shell restart command #92
Reference in New Issue
Block a user
Delete Branch "73-colorscheme-options"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
Replace hardcoded MaterialYou seed-based color
PRESETSdict with a dynamicdirectory-scanning scheme system. The wallpaper auto mode (which uses MaterialYou
seed generation from images) is untouched.
schemepalettes.pySeedPalettedataclass +PRESETSdict (hardcoded Hct seeds)assets/schemes/for.txtpalette files; no JSON descriptors needed{accent}-{mode}.txtnaming patternCatppuccin color correction
.txtcolors from dankmaterialshell data.txtfiles (rosewater through lavender)scheme.pyCLI.txtpalettes directly for presets, bypassing MaterialYoulist-presetscommand (human +--jsonoutput)--preset <scheme>:<variant>selects a palette (removed:accentshorthand)--accent <name>picks accent for schemes that support it (catppuccin only)--accentagainst variant's available accents; reject invalid with clear errordefault_accentper variant so QML UI can pre-selectshell.pyrestartcommand (kill + start)callcommand crash when no method args givenCleanup
preset.py/record.pystubscatppuccin.py+catppuccin.json(replaced by.txtfiles)Tests
Suggestions to add later
scheme mode and scheme type. This can cause issues since that affects the
preset color scheme. These options could be hidden when automatic scheme mode
is disabled, optionally revealing the palette options instead.
approach. Maybe a different implementation like a toggle between automatic vs
palette is better?
Looks good overall, I have two things I wonder about:
--accentredundant when the second colon is also for setting accent, or am I misunderstanding? However I do think if there is a difference between the[:accent]and--accentthen we should probably rename either to avoid confusion.m3surfaceandm3surfaceContainercolors are so similar I can barely tell they're different sometimes. We should probably change that at some point, but not necessary before merge I don't think.Agreed, not a huge fan of the surfaces and the container colors.
--accentis reduntant. Probably AI moment and me not checking thoroughly. Will resolve in next commit.@zach Resolved.