That was a good read. I’d not really been sure of the differences between libadawaita and GTK were. It sounds like this frees up GTK to focus on being a cross platform GUI library, perhaps competing more directly with Qt. Meanwhile, libadawaita allows GNOME developers to keep leveraging GTK and tune it to their design guidelines.
I’ve only seen positive things come out of recent GNOME apps, but I wonder if the downside of GTK no longer embedding GNOME’s design language would be apps choosing to use GTK directly instead of libadawaita for better cross platform support. Will we end up with a less cohesive GNOME environment in the future?
So I guess the implication here is apps written explicitly for libadwaita will not be usable on generic GTK. So a calculator, for instance, that uses AdwDialog won’t be executable on a platform that doesn’t support libadwaita, like windows.
Will an app dependent on libadwaita be usable on linux without gnome? Like xfce, or xmonad?
Will an app dependent on libadwaita that be usable on linux without gnome? Like xfce, or xmonad?
of course it will, that’s not the point, the point is to make apps that use libadwaita look consistent even in platforms outside of GNOME
Ok, I thought the article was saying libadwaita was to add special features and styles for use in gnome specific apps.
Don’t worry, this article is mainly to clear some misunderstanding about libadwaita anyway, having questions about it is natural