omawarisan@lemmy.world to Linux@lemmy.ml · 29 days agoOne GNOME session, multiple styleslemmy.worldimagemessage-square87fedilinkarrow-up10arrow-down10file-text
arrow-up10arrow-down1imageOne GNOME session, multiple styleslemmy.worldomawarisan@lemmy.world to Linux@lemmy.ml · 29 days agomessage-square87fedilinkfile-text
gtk3, gtk4 (probably?) qt, qt in flatpak, gtk3 in flatpak, gtk4 in flatpak (probably)… I’m just not fighting it anymore
minus-squarefitgse@sh.itjust.workslinkfedilinkarrow-up0·29 days agoWell, Wayland forces client side decorations which I’ve never agreed with.
minus-squaredeadcade@lemmy.deadca.delinkfedilinkarrow-up0·29 days agoGNOME devs simply can’t “tolerate” SSD, and force CSD in every scenario for GTK4. My machines running Wayland only have CSD for fully custom apps (like Steam) and every GTK4 app.
minus-squarestuner@lemmy.worldlinkfedilinkarrow-up0·29 days agoNo, that’s Gnome, not Wayland. KDE still prefers SSD on Wayland.
minus-squareMarkaos@discuss.tchncs.delinkfedilinkarrow-up0·28 days agoWayland does force clients to be able to cope with a compositor that doesn’t do SSD - CSD support is mandatory, SSD optional.
Well, Wayland forces client side decorations which I’ve never agreed with.
GNOME devs simply can’t “tolerate” SSD, and force CSD in every scenario for GTK4. My machines running Wayland only have CSD for fully custom apps (like Steam) and every GTK4 app.
No, that’s Gnome, not Wayland. KDE still prefers SSD on Wayland.
Wayland does force clients to be able to cope with a compositor that doesn’t do SSD - CSD support is mandatory, SSD optional.