@brainblasted I don't see how this isn't themes. If you have a problem with GTK themes but not with this, isn't it more of a problem with that specific theme implementation and not themes in general?
Top-level
@brainblasted I don't see how this isn't themes. If you have a problem with GTK themes but not with this, isn't it more of a problem with that specific theme implementation and not themes in general? 5 comments
@anselmschueler It's not arbitrary CSS restyling, at least. That's what people have defined "themes" as previously. @bragefuglseth I always interpreted things like https://stopthemingmy.app/ as saying that app developers should have complete control over their app’s look, and a complete rejection of any overarching theming system. @anselmschueler If any sort of restyling was out of the picture, we wouldn't have light/dark mode either. This system still provides app developers with full control, as they can choose to opt out. If they don't, though, there is only a limited set of possible colors to account for, as opposed to an infinite amount of arbitrary CSS. |
@anselmschueler The only thing changing here is colors. For the light and dark style, app developers are expected to support those. The colors are the stable and can be relied on by developers. The accent colors are only used in specific spots and care is put into ensuring changing accent colors does not break apps.
The padding, borders, text style, and more are not changing when you change between light or dark styles or change accent colors. Those things can change drastically when you introduce full CSS theming.
@anselmschueler The only thing changing here is colors. For the light and dark style, app developers are expected to support those. The colors are the stable and can be relied on by developers. The accent colors are only used in specific spots and care is put into ensuring changing accent colors does not break apps.