Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
What about
mood=grumpyfor me ;-P
Dunno; I thought "mood" was a better word for it, as in "vibe" or "atmosphere". (It isn't really a "mode" in that it doesn't affect how the rest of the app operates; just an "artistic style", and I thought that word was fitting.) Could be called style or type, or simply dark=true|false.
name and name-dark eg
mint-yandmint-y-dark
Yeah; I guess one workaround could be to search for "dark" in the name, or for each name, see if it has a matching "dark" or "light" counterpart, but I don't think it'd be too reliable.
The problem with filters is that then some colour schemes are hidden
My idea here was to make the unspecified ones show up when neither "light themes" nor "dark themes" were selected (i.e., when not filtering); the default would be to show all themes together. And if you filter by style THEN only show those explicitly marching the style.
So I'm leaning more towards sorting not filtering, and that leads back to using the filename as the simple approach.
I... am not too convinced by the idea of having all themes named dark-* and bright-*1; feels a bit repetitive and unreliable. But it's true that it'd be a trivial way to group related themes together, without explicitly implying that they're grouped together BECAUSE they're light/dark themes; just an "intentional side effect". And an inexpensive change.
I don't know; I think I'd prefer some way to sort by "actual brightness", either explicitly stated in the file or computed from the values, rather than implied from the name. Or that's what I had in mind at least.
Using "bright" and not "light" so that it collates before "dark". ↩
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.