You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In general I'm not opposed to gtk4, but for now it still seems not really viable due to limitations in wayland support (gtk4 layershell seems to still be very hacky, but at least it's possible now, I gues...
I'll need to look into it again once it actually becomes a necessity..
I think it'll be good to keep either this or #109 open for tracking, also css variables landed in gtk4 in addition to other css improvements which is a massive improvement to usability. There's also the option of using a different toolkit altogether but it doesn't seem great at the moment, in addition to breaking pretty much all existing configs, qt is a pain with rust, and for rust toolkits winit layer shellis stack in limbo so the only options that seem viable are the iced popos fork that has a dedicated sctk layer shell backend, or adding support in another toolkit (perhaps GPUI 😉).
Update: Casilda has been released which is a wayland compositor implemented as a gtk4 widget, which would be awesome with the new cosmic applet ecosystem. On the iced front 0.13 has been released and the pop-os fork rebased to it (which has layershell support) and there's also iced_layershell which is an alternative implementation. GPUI hasn't really made progress towards being more usable as a library outside of Zed (which is understandable).
Hello!
As of March 4 the gtk crate eww uses is no longer maintained. I also noticed that the code for the dbusmenu crate has been removed.
Are there any plans to migrate to GTK4? It seems it has not gone well last time.
The text was updated successfully, but these errors were encountered: