191–200 of 206 posts
I honestly think we just need to have light and dark modes built in. If you want to modify the dark theme a bit, go ahead, but since the original dev knew the background should be dark and the foreground light, it should be OK. The problem is when people implicitly assume a light theme, but then use a dark one. If we could "tag" a theme as light or dark, a lot of this problem would go away.
I'll stop themeing apps and their icons once I don't see a single piece of software that has an UI and an icon look like as it were made in the 90s, also implement dark theme. Providing a more consistent UI for new users on a distro is also better idea than leaving it up for the developers.
The GNOME back button being wrongly themed is solved by switching GNOME to dark mode (`gnome-tweak-tool`) and a dark theme. The engine isn't the best but devs don't make it easy either.
Earlier quoted context omitted.
That paragraph continues. The letter is absolutely also aimed at end users: > If you like to tinker with your own system, that’s fine with us. However, if you change things like stylesheets and icons, you should be aware that you’re in unsupported territory. Any issues you encounter should be reported to the theme developer, not the app developer. Just not with the same vehemence as its message directed at distros.
But I mean it's also technically correct. How could an application developer make any kind of guarantee in the face of arbitrary theming and tinkering by the end user?
This all seems like a huge issue made about nothing on consequence
Earlier quoted context omitted.
Nobody is saying that you must not apply your favourite theme to whatever apps you like on your own computer. Not me, not the linked article. If themes are so important to you, pick your app based on that criteria. If you think an app is garbage because it doesn’t theme well, fork it and write a better version yourself.
The main point of confusion in this whole thread is whether or not the article states you shouldn't apply themes on your own computer. To some, myself included, it kind of does. Linux distributions are not individual operating systems - they're essentially skins on top of Linux kernel, created bottom-up to offer opinionated choices to users. Picking a distribution is like modifying software on one's own computer, exc…
That is an unfair inference because the author of the post explicitly says otherwise. To the extent he is speaking to you, he is only saying "thar be dragons" and that he will not explicitly support your use of a theme—therefore you should file any theme-induced bugs with the theme author and not with him.
Earlier quoted context omitted.
The redisign used for new.reddit.com doesn't give moderators as much control, much to the displeasure of many of us who have been on the platform for a long time. Although I dislike it when people significantly change UI controls.
I can't think of any CSS styles that are actually outright bad , though, unless it's intentional (like with /r/crappydesign or /r/ooer).
Earlier quoted context omitted.
I guess a radical solution would be to require (through trademark law) to force distros to brand the apps differently (name and icon) so that bug reports end up where they belong.
Debian used to have to do this with Firefox and Thunderbird.
This is more of an indictment of the way GTK3+ handles theming (or lack of it). GNOME/GTK devs, as usual, got confused and implemented something no one wants. Either you provide a proper and defined way to theme like KDE does or take the windows/mac route and tell developers to recreate any custom themed control from scratch. Instead, they go around saying that there is only one GTK theme and then leave a convenient…
> This is more of an indictment of the way GTK3+ handles theming (or lack of it). How do you think GTK+3 handles theming (or lacks handling for it)? It sounds like you're confusing GTK+3 theming for GTK+2 theming (which was based on "engines", which were quite a mess). Now it's very "proper and defined", it's accomplished with a strict subset of CSS which has fairly consistent behaviour. I personally don't see the po…
Earlier quoted context omitted.
I have a strong feeling that if custom themes are breaking apps, then those apps are almost certainly in violation of one or more of tables 2-4, 2-5, or 2-6.
Maybe, maybe not. Some apps have no obligation to meet these checklists because they are for tasks that can only be performed by people with no significant visual impairment. I am not claiming that this a common case. But how would e.g. someone with poor eyesight use gimp successfully? Dumb line of business apps that have a simple UI made mostly out of standard widgets have fewer excuses.
Earlier quoted context omitted.
I can't think of any CSS styles that are actually outright bad , though, unless it's intentional (like with /r/crappydesign or /r/ooer).
Just the inconsistency makes it very unusable.