Replies: 2 comments 3 replies
-
Beta Was this translation helpful? Give feedback.
0 replies
-
IMO it would make sense to manage this in the module. We only avoid this for programs like Waybar, where it's very common for users to design their own layout from scratch (presumably this is not what spotify-player is for). |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Just realized there's something i didnt contemplate.
the same file where theme selected and theme palettes are stored, you can set which elements grab which colors
e.g
[themes.component_style]
selection = { bg = "BrightBlack", modifiers = ["Bold"] }
block_title = { fg = "Magenta" }
playback_track = { fg = "Cyan", modifiers = ["Bold"] }
playback_album = { fg = "Yellow" }
playback_metadata = { fg = "Blue" }
playback_progress_bar = { bg = "BrightBlack", fg = "Green" }
current_playing = { fg = "Green", modifiers = ["Bold"] }
page_desc = { fg = "Cyan", modifiers = ["Bold"] }
table_header = { fg = "Blue" }
border = {}
playback_status = { fg = "Cyan", modifiers = ["Bold"] }
playback_artists = { fg = "Cyan", modifiers = ["Bold"] }
playlist_desc = { fg = "White" }
without these things changed, default on some (most?) themes looks bad
e.g progress bar uses different colors on two elements

this did not happen with the theme i was using till now, so i did not realize it.
Should we let people define the component styles by themselves or should we manage this in the module?
https://mynixos.com/home-manager/option/programs.spotify-player.themes also see example
themes specifically made for spotify-player (see catpuccin) usually set 'em
Beta Was this translation helpful? Give feedback.
All reactions