71
Libadwaita: Splitting GTK and Design Language
(tesk.page)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 03 Jun 2024
71 points (93.8% liked)
Linux
47362 readers
1240 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
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?
When an app targets a platform-specific library like Adwaita it explicitly forgoes supporting generic, cross-platform GTK.
Depends what you mean by "usable".
Will it run, yes, most likely. But the UI will be full of Gnome-y things that make little sense on other DE's, among which the theme is just one. Could be other stuff, like accessibility, features etc.
As long as none of the shortcomings are deal-breakers for you I guess you can call it "usable".
At the end of the day there's always going to be DE's that expand their UI features, and apps that take advantage of those. Cosmic, Plasma, Granite etc. are all examples of such platform-specific UI libs. Even in a cross-platform library like GTK or Qt there's no guarantee that they're compatible with each other. Bottom line is, when you mix and match apps made for different toolkits there's always going to be variations.
It was nice for a while having common themes that could target both GTK and Qt and having unified-looking desktops. I guess that era is over. Back to each app having its own incompatible theming and the only common point being that they're all "light-ish" or "dark-ish".
Windows supports libadwaita
It means that on systems with apps installed written with libadwaita, will also have libadwaita installed, rather than just GTK. But those apps will look like GNOME apps, which might look out of place on e.g. a Windows or Xfce desktop.
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