my new favourite @postmarketOS T-shirt 😁

#GNOME #GUADEC

@cas @postmarketOS you forgot pipewire!

@krafting @postmarketOS well we're still using pulseaudio (migration not finished yet) so it wouldn't exactly be suitable 😆

@cas @postmarketOS Replace libadwaita for Kirigami and I'd be hooked!

@bart @cas @postmarketOS

Can we have an abstraction over these UI toolkits/libs so apps can target multiple UIs without thinking too hard about it? 😅

@craftyguy @bart @postmarketOS i asked a bunch of devs and they all yelled "nononononononononono"

sorry

@cas @bart @postmarketOS

So I guess we're doomed to deal with some apps looking shitty on some UIs, and the only fix being to "recreate the app using the other UI thing" 🙃

@craftyguy @bart @postmarketOS im sorry, i wish tjis was possible but this is a somewhat naive take on app dev.....

make a webapp if you want this?

@cas @bart @postmarketOS yeah, I mean, I've been around long enough to know this isn't a new problem 😅

For some reason we're still OK with this goofy situation where KDE and GNOME folks think users should just use apps written for their UI thing, users just want apps that do what they need them to do, and there's often cases where the most functional app was written for the "wrong" UI and users just have to "deal with it."

Web apps are usually not the answer 😉

@craftyguy @cas @bart @postmarketOS You could always make a backend with most of the logic and then write the apps around that?

@craftyguy @cas @bart @postmarketOS electron is not an option *honk*

@craftyguy @cas @bart @postmarketOS I think it was a similar feeling that led Canonical to use Flutter, a third interface... https://xkcd.com/927/

@dperson @cas @bart @postmarketOS

Yeah I don't think that's great either... 🤣

Anyways, just kinda annoyed that this is still a problem, because it's a silly problem for users. Like why do I need to run KDE if I want the super useful KStars app to not look bad?

@craftyguy @cas the problem is not about the technical side, but about ux, although it uses the same color and widgets that all your app uses, they won't follow the same guidelines, they will feel off even if they don't look off, sadly its's not something fixable

@psykose @dperson @postmarketOS @bart @cas ya would be cool if this just worked OOTB 😁

@craftyguy @cas @postmarketOS Yeah it's a sad state of affairs. I'm not sure how to solve it either. Every time I open some libadwaita app (mostly Lutris, I don't really use libadwaita apps otherwise) it sticks out as a sore thumb and I'm sure it's the same for any Kirigami app on GNOME.

So now every useful app is being duplicated and has it's own set of bugs and problems just because they want the UI different.

@bart @craftyguy @cas @postmarketOS Before libadwaita with gtk you could use a breeze theme that would look similar to breeze. Maybe libadwaita vould load a coloscheme or a set of widgets that look similar to breeze if on KDE...?

@Tau @bart @craftyguy @postmarketOS if you install plasma on arch linux it breaks your GNOME shell entirely because of theming hacks

@cas @Tau @craftyguy @postmarketOS Pretty sure it's the same other way around. I learned years ago that you shouldn't bother using multiple DE's on the same account, that's asking for problems.

@bart @Tau @craftyguy @postmarketOS not the same the other way around. on arch linux at least

@bart afaik lutris is not a libadwaita app, it uses gtk3, so it should fit better (? (if not, then i don't know why is linux mint sticking to that)

@pan Well then they actively tried to make it look like an libadwaita app. Anyway it's giant headerbar and GTK controls really do not look nice in a KDE environment and I wish it used a more classical GTK look.

@bart yeah, i don't think so, thats just how gtk3 apps look, there is this libadwaita predecesor called libhandy, but lutris doesn't use it (btw, maybe you are happy to know that the mantainer is thinking about porting the app to qt, as they dont want to port it to gtk4)

@hucksternoise @postmarketOS idk i know some gnomies who would disagree :3