Post ANtSASAbAXn7k39OXw by huntra@mastodon.technology
 (DIR) More posts by huntra@mastodon.technology
 (DIR) Post #ANtRxLdCAWazhJHFkO by TheEvilSkeleton@fosstodon.org
       2022-09-24T15:23:27Z
       
       0 likes, 2 repeats
       
       Users often suggest to use the GTK_THEME environment variable for theming. Don't. It's a debug variable. When a GTK3 app ports to GTK4+libadwaita, the app appears broken. GTK_THEME removes all libadwaita widgets and should NEVER be recommended unless the user knows what they're doing.#gnome #foss #opensource #gtk #gtk4 #linux #gnu
       
 (DIR) Post #ANtSASAbAXn7k39OXw by huntra@mastodon.technology
       2022-09-24T15:25:47Z
       
       0 likes, 0 repeats
       
       @TheEvilSkeleton what is it used for in debugging context?
       
 (DIR) Post #ANtSEm4V7K9eckMJFY by TheEvilSkeleton@fosstodon.org
       2022-09-24T15:26:36Z
       
       0 likes, 0 repeats
       
       @huntra it's meant to debug theme issues. https://docs.gtk.org/gtk4/running.html#gtk_theme
       
 (DIR) Post #ANtefdBPTIRgKEAAqm by hund@fosstodon.org
       2022-09-24T17:45:43Z
       
       0 likes, 0 repeats
       
       @TheEvilSkeleton @huntra Why don't they use a good name for it instead? Then people wouldn't have so much issues with it.
       
 (DIR) Post #ANtktNgAVjWC1IURAO by TheEvilSkeleton@fosstodon.org
       2022-09-24T18:55:33Z
       
       0 likes, 0 repeats
       
       @hund the name makes sense for GNOME's purpose. GNOME only makes options graphically available when they are properly implemented. Otherwise, those options are hidden away inside gsettings, GNOME Tweaks. Since GTK_THEME is a debug variable, it's in an env variable.That said, why are people recommending to change a GTK variable when GTK devs themselves have been VERY vocal about theming being inherently hacky?
       
 (DIR) Post #ANtlBrWuGX2hoQyDpo by TheEvilSkeleton@fosstodon.org
       2022-09-24T18:58:49Z
       
       0 likes, 0 repeats
       
       @hund the name makes sense for GNOME's purpose. GNOME only makes options graphically available and accessible when they can be safely changed by the user via Settings. Otherwise, those options are hidden away inside gsettings or env variable.That said, why are people recommending to change a GTK variable when GTK and GNOME devs themselves have been VERY vocal about theming being inherently hacky?
       
 (DIR) Post #ANtnxlXS2mH92VC9Nw by hund@fosstodon.org
       2022-09-24T19:29:59Z
       
       0 likes, 0 repeats
       
       @TheEvilSkeleton Oh. Right.. Sorry. I forgot. It's GNOME we're talking about. The most hostile anti-feature big corporate meme desktop environment out there. :D
       
 (DIR) Post #ANupRnQnrhgqi2veQy by appelgriebsch@fosstodon.org
       2022-09-25T07:21:23Z
       
       0 likes, 0 repeats
       
       @hund @TheEvilSkeleton but wait… it’s declared hacky since gtk4 and libadwaita hit the scene. In gtk2 and gtk3 there was official support for theming (via css styles), wasn’t it?
       
 (DIR) Post #ANupWFOtomA4c4A1mi by dusansimic@mastodon.technology
       2022-09-25T07:22:11Z
       
       0 likes, 0 repeats
       
       @TheEvilSkeleton @hund well, people are that way essentially recommending hacks for themeing 😅, not perfect solutions
       
 (DIR) Post #ANv8Hw3ErNVZg1uzJY by hund@fosstodon.org
       2022-09-25T08:52:43Z
       
       0 likes, 0 repeats
       
       @appelgriebsch @TheEvilSkeleton Yes. GNOME said theming was hacky and said they would remove it, rather then fixing their bad code. I think it's more about they don't want any features what so ever (other than the absolute barebones) that some corporate Redhat employee doesn't use anyway. They're also removing support for wallpapers, which makes sense. It's not like corporate people care about some silly wallpaper anyway.
       
 (DIR) Post #ANv8HwaCsnsbKHLJhY by TheEvilSkeleton@fosstodon.org
       2022-09-25T10:52:30Z
       
       0 likes, 0 repeats
       
       @hund you can't fix "bad code", when it's not bad code to begin with. Theming is inherently hacky and it's not unique to GTK. Qt theming is equally as bad. This feature was never removed. You can use custom CSS to override the stylesheet, but it's just hidden away.Red Hat has nothing to do with it. libadwaita was started by Purism, and supported by many GNOME non-corporate contributors.Anyway, I will refrain from posting. It's clear that you have a grudge against GNOME and Red Hat.
       
 (DIR) Post #ANv8e5BtYlFGOTWmvY by TheEvilSkeleton@fosstodon.org
       2022-09-25T10:56:30Z
       
       0 likes, 0 repeats
       
       @appelgriebsch you can still override GTK4 and libadwaita using CSS. I don't know about GTK2 since I wasn't on Linux at that time, but GNOME certainly considered GTK3 theming hacky. It's why theming stuff were always in GNOME Tweaks. GNOME Tweaks usually contains hacky implementations.
       
 (DIR) Post #ANvJcjdfIrxal14q2a by shiba@fosstodon.org
       2022-09-25T12:59:29Z
       
       0 likes, 0 repeats
       
       @TheEvilSkeleton I know this is not what you meant, but you hit the nail: GTK4+libadwaita apps appear broken.
       
 (DIR) Post #ANwuOaS8YCM9fwlHEG by dusansimic@mastodon.technology
       2022-09-26T07:26:13Z
       
       0 likes, 0 repeats
       
       @TheEvilSkeleton @hund tbh, I personally ubderstand what you mean by that and I just think that state of themeing on gnome was always just communicated in a bad way. Seems like custom css is there not for themers but for developers to tweak the already existing stylesheets to look better on their specific app.