Hello fellow citizen, I almost agree but libadwaita is inherently gnome’s thing, and libadwaita apps are usually closely built into the gnome desktop, so using it outside of gnome seems weird. Kinda like using Dolphin outside of KDE (tho that’s just because of qt). They want to be able to integrate their forks visually.
I don’t see libadadwaita as progress. Last week, simple-scan got an update and is stuck to a dark theme since then. To change it, i would have to install gnome-settings and klick a button there. Can’t do that via my usual keyboard-combo.
edit: edited Gnome’s ‘don’t theme our apps’ away since it’s beside the point.
If you actually read through that they say theme away to your heart’s content, just please don’t report issues to the app developer, report it to the theme developer.
They say that lots of time they could spend developing is managing and investigating bugs that end up being due to the user installing some random poorly-made theme, wasting precious dev time that they are donating for free.
It’s a perfectly reasonable request, and has no bearing on whether an app is proprietary or not.
E: the guy above has drastically changed their comment so now mine probably doesn’t make sense.
If a theme is able to break core functionality then your theming system/guidelines needs to be fixed. And it to be more accessible to theme designers so these problems don’t occur in the first place.
That’s bs. No matter how good your theming system is, it can’t fix a bunch of things. Even something as basic as text being shown against a background with not enough contrast.
Theming has been known to cause issues on literally every DE. You can’t stop people from theming poorly, or ban bugs, they’re both just part of the landscape of downloading random themes and applying it to all your apps.
And random dev shouldn’t be on the hook for third party themes that cause issues. Nor should they be expected to drop everything and investigate bugs in somebody else’s theme project. That stuff should be reported to the theme developer.
Most Linux app devs are volunteers and their time shouldn’t be wasted investigating theming-related issues. Report it to the theme developer.
I admit i stopped reading after i got alienated by the bullet points. And Gnomes points after are nice and all, but only caring about their own vision is not the solution either, especially if you create one of the two main GUI frameworks. A tool is not an art piece but something that has to adapt to the user.
So you tried to shit on developers by posting a link to a completely reasonable request (“theming is fine but please be mindful of wasting our limited time by bombarding us with bug reports related to janky themes”) that you hadn’t even read. Got it.
People need to understand that none of this development is free. These people donate their time to make these projects for us to have, completely free of charge. Investigating a bug can take hours, or days, sometimes longer. Imagine doing that and it turns out there wasn’t a bug with your program at all, it was with a theme that the user installed. I’d also be pissed off about the time I’m donating for the good of the community being wasted.
You absolutely did lol. You complained about them and it reeked of entitlement. You don’t have a God-given right for the developer of every app to investigate issues with somebody else’s themes.
I see you’ve edited away much of it though. Sneaky.
The gsettings command can change things on the fly in the dconf, assuming that’s where the setting actually resides. It’s a pain to do, but that means it’s possible to write a script that makes the necessary change(s) and that can then be assigned to a keyboard combo.
For example, I have one that toggles a Cinnamon panel between the top and the bottom of its screen (I won’t get into why) and currently have it bound to Ctrl-Alt-Space.
It’s currently a hack that uses a couple of hardcoded values that I pulled from the dconf by observing what it was set to with the panel in each location. If it finds the first value it changes it to the second, and vice versa.
(In the unlikely event I come to change the layout to something it doesn’t recognise, it bails out, doing nothing.)
Anyway, you could probably do something similar to toggle the dark/light mode.
gsettings didn’t work in my case. Which is why i guess it’s libadwaita. Btw, i’m on XFCE.
edit: though, toggling light/dark via gsettings might work.
editedit: it didn’t. But GTK_THEME=<theme> did. Which is kinda troublesome still, since you can’t switch session variable content for the current session. Needs a wrapper script now.
They could just accept GTK 4. Anyway, they will need some GTK 4/libadwaita support as there are an increasing number of apps that use it.
Hello fellow citizen, I almost agree but libadwaita is inherently gnome’s thing, and libadwaita apps are usually closely built into the gnome desktop, so using it outside of gnome seems weird. Kinda like using Dolphin outside of KDE (tho that’s just because of qt). They want to be able to integrate their forks visually.
I don’t see libadadwaita as progress. Last week, simple-scan got an update and is stuck to a dark theme since then. To change it, i would have to install gnome-settings and klick a button there. Can’t do that via my usual keyboard-combo.
edit: edited Gnome’s ‘don’t theme our apps’ away since it’s beside the point.
If you actually read through that they say theme away to your heart’s content, just please don’t report issues to the app developer, report it to the theme developer.
They say that lots of time they could spend developing is managing and investigating bugs that end up being due to the user installing some random poorly-made theme, wasting precious dev time that they are donating for free.
It’s a perfectly reasonable request, and has no bearing on whether an app is proprietary or not.
E: the guy above has drastically changed their comment so now mine probably doesn’t make sense.
If a theme is able to break core functionality then your theming system/guidelines needs to be fixed. And it to be more accessible to theme designers so these problems don’t occur in the first place.
That’s bs. No matter how good your theming system is, it can’t fix a bunch of things. Even something as basic as text being shown against a background with not enough contrast.
Theming has been known to cause issues on literally every DE. You can’t stop people from theming poorly, or ban bugs, they’re both just part of the landscape of downloading random themes and applying it to all your apps.
And random dev shouldn’t be on the hook for third party themes that cause issues. Nor should they be expected to drop everything and investigate bugs in somebody else’s theme project. That stuff should be reported to the theme developer.
Most Linux app devs are volunteers and their time shouldn’t be wasted investigating theming-related issues. Report it to the theme developer.
I admit i stopped reading after i got alienated by the bullet points. And Gnomes points after are nice and all, but only caring about their own vision is not the solution either, especially if you create one of the two main GUI frameworks. A tool is not an art piece but something that has to adapt to the user.
So you tried to shit on developers by posting a link to a completely reasonable request (“theming is fine but please be mindful of wasting our limited time by bombarding us with bug reports related to janky themes”) that you hadn’t even read. Got it.
People need to understand that none of this development is free. These people donate their time to make these projects for us to have, completely free of charge. Investigating a bug can take hours, or days, sometimes longer. Imagine doing that and it turns out there wasn’t a bug with your program at all, it was with a theme that the user installed. I’d also be pissed off about the time I’m donating for the good of the community being wasted.
No, i didn’t. Calm down.
You absolutely did lol. You complained about them and it reeked of entitlement. You don’t have a God-given right for the developer of every app to investigate issues with somebody else’s themes.
I see you’ve edited away much of it though. Sneaky.
Yeah, and i stated why. Stop trolling.
No, you shat on them, I called you out, then you hid what you said and said “oh it’s not relevant never mind”. You were absolutely shitting on devs.
Trolling? Lol I was directly conversing with you and addressing the point you made.
If anybody is trolling, it’s the person who was shitting on devs (now denying it) and backing himself up with a blog post that he hadn’t even read.
The
gsettingscommand can change things on the fly in the dconf, assuming that’s where the setting actually resides. It’s a pain to do, but that means it’s possible to write a script that makes the necessary change(s) and that can then be assigned to a keyboard combo.For example, I have one that toggles a Cinnamon panel between the top and the bottom of its screen (I won’t get into why) and currently have it bound to Ctrl-Alt-Space.
It’s currently a hack that uses a couple of hardcoded values that I pulled from the dconf by observing what it was set to with the panel in each location. If it finds the first value it changes it to the second, and vice versa.
(In the unlikely event I come to change the layout to something it doesn’t recognise, it bails out, doing nothing.)
Anyway, you could probably do something similar to toggle the dark/light mode.
gsettings didn’t work in my case. Which is why i guess it’s libadwaita. Btw, i’m on XFCE.
edit: though, toggling light/dark via gsettings might work.
editedit: it didn’t. But GTK_THEME=<theme> did. Which is kinda troublesome still, since you can’t switch session variable content for the current session. Needs a wrapper script now.
You can use gradence to set a custom theme.