It's been a while, but I finaly got Feeds to work on #gtk4 / #libadwaita, including a very fresh build of #webkit

I've spent some time ironing out some porting bugs, but so far it looks really good!

There's still a lot of work to do, plus probably refactoring some stuff, but it's finally coming together!

@gabmus sadly forces it's theming style. that just suxx :(

@scops could be wrong but I think that you can make themes that support libadwaita.

I'm not opposed to theming , but I can pretty much assure you that at some point themes just break UIs, because more often than not devs rely on the default stylesheet for readability as well as custom styles.

This is a difficult conversation to have, and while I'd love to have themes that would magically just work, I can see how it's not really possible for gtk at this point in time.

@gabmus yes, they could break the UI. but thats the freedom for the user. if a user "want" to break a UI... why shouldn't "you" (libadwaita) force him not to do so? yes, it's a difficult conversation and i'm on the "pro theme" side ;) maybe you could support libhandy too? i use this theme on my devices; github.com/daniruiz/skeuos-gtk (at the moment,... besides Pho-Earth and others depending on mood)

@scops

> you could support libhandy too?

nay, doesn't work with gtk4

> thats the freedom for the user

I understand, and I agree with you, but this is a technical limitation, not an imposition

@gabmus Thats (gtk4 / libhandy) are really bad news (for me) :( i hope there will be a working port of libhandy in the future. :(

@scops libadwaita IS the working port. The theming problem related to libadwaita is something to do with the direction gtk as a whole is taking. libadwaita is developed by the same people that develop gtk, as a natural extension to it, not as a third party add-on.

@gabmus @scops

libadwaita is developed by the same people that develop gtk

No no no. While we have contributions to GTK we are not the core GTK developers. libadwaita’s explicit purpose is to decouple the direction of GNOME from the direction of GTK.

@brainblasted @gabmus thats all fine to decouple it... but to force users to use only ONE ui theme makes the project more like for example apple.

@scops @gabmus GNOME never officially supported themes. That’s just something that people could do because GTK supported it and we used plain GTK instead of a platform library like libgranite.

@scops @brainblasted @gabmus GTK2 themes could literally side-load code into your applications. You may think that's a good feature, but I'm afraid that's on you.

Follow

@ebassi @brainblasted @gabmus no no, i don't want gtk2 back. i just say on the theming side it was "easy" with a good result to theme the ui :)
besides; if someone installs a theme from a untrusty source... it's the own fault. it's like that you shouldn't drive a car if you dont have a driving license... you can but you must bear the blame.

@scops @ebassi @gabmus how are they to know what’s an untrustworthy source when they’re just told “hey look, you can download themes!”

@scops @brainblasted @gabmus Things are so clear cut. Distributions add their own themes; applications add their own themes; and users expect everything to work, and will not accept the blame—especially if it seems that themes are actually supported. Then people will come screaming into the GTK issue tracker, and then *I* have to deal with them.

@ebassi @brainblasted @gabmus default answer templates... i know the problems (i'm also a developer ^^) thats a (bad) side of the work

@ebassi @brainblasted @gabmus hmm in the "theme selection" there could be just a disclaimer; "unsupported theme, if you use it it's your problem" ;) but yes, the noobs will come screaming either... the plasma guys should have the same problems, no?

Sign in to participate in the conversation
Mastodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!