4 ms·
The funny thing about all this is it's just history repeating itself. Back in the days of GTK2, there were a handful or two of "libgnome"-prefixed libraries th
by kelnos 2y ago
The funny thing about all this is it's just history repeating itself. Back in the days of GTK2, there were a handful or two of "libgnome"-prefixed libraries that GNOME apps tended to use, but non-GNOME apps (that used GTK) tried to stay away from, in order to avoid depending on large bits of the GNOME desktop. The problem with that, of course, was that people in that position either got by with reduced functionality, or had to write their own code to do things that many people considered should be a part of the toolkit.
The GTK developers did recognize that a lot of this stuff was integral to a UI toolkit, and so most of the functionality in the various libgnome libraries was moved into GTK for GTK3.
And now apparently we're going backward again. No, I get, it's not the same situation. They are focusing more on "design language" than functionality: for example, the printing functionality that was moved from libgnomeprint (or whatever it was called) into GTK3 is staying (which makes sense), but menu bars (which have been in GTK since the beginning) are going away because GNOME doesn't use them anymore.
But that's a part of the problem; it seems like their rubric is "if GNOME doesn't need it, then it should be deleted"[0], coupled with the idea that many new design language elements should be GNOME-only and live in libadwaita, even if a more general audience would benefit from those elements.
As a developer of GTK-based applications for a good 20 years now, I honestly can't recommend GTK for new projects outside the GNOME umbrella. The problem is I'm not really sure what to use instead. Qt is really the only other major cross-platform toolkit, and does seem like a more stable base, but I don't want to do C++, and bindings for other languages aren't very ergonomic. (And toolkits like wxWidgets are just abstractions on top of other platform libraries.)
What I really want is a Rust-native UI toolkit library that does its own drawing, but can consume GTK3 themes. To me, the big issue is that of "native look", and I don't want Yet Another UI Toolkit that allows people to build apps that don't fit into my desktop at all.
[0] Note that quite a few things, like GtkDialog as a notable example, didn't get removed for GTK4, but have been deprecated and will be removed in GTK5.
- HumanOstrich 2y agoI was with you until you suggested rewriting everything in Rust.
- deleted 2y ago[deleted]
- grumpyprole 2y agoAre they really deleting menu bars? Wow. Maybe in ten years time they'll figure out that two hamburgers is better than one; and that they'll need names like "File" and "Edit".
- sameerds 2y agoNo they are not. The GtkMenuBar widget got dropped because a replacement already exists. Another comment below provided the reference: https://docs.gtk.org/gtk4/migrating-3to4.html#gtkmenu-gtkmenubar-and-gtkmenuitem-are-gone https://docs.gtk.org/gtk4/migrating-3to4.html#gtkmenu-gtkmen... I wish the GP would clarify this particular confusion in their comment! The way it stands, the comment makes these projects sound outright whimsical, which is clearly not true.
- tristan957 2y agoGtkDialog is just a GtkWindow with a few things done for you. It wasn't exactly a pleasant API to use either.
- AlienRobot 2y agoWhy does everyone have to make it so hard? All I want is literally the widgets Windows had 20 years ago in all platforms. That's all. I don't even need the ribbon. And now GTK has sliding tabs with animation effects I have to install tweaks to turn off. To begin with, why is tweaks even a thing? This should all be in the normal control panel! I can't believe I used to hear criticisms about the windows registry when in linux I need to install 2 different regedits to make the GUI look bearable. This is why people use electron.
- crashdancer 2y agoIt is in the normal control panel, see "Reduce Animation" in the accessibility page. >All I want is literally the widgets Windows had 20 years ago in all platforms. This seems to me a very bizarre request. I mean, you can literally do that already: write Windows apps using the old user32 APIs and run them in Wine. But then they will look and behave really out-of-place on non-Windows platforms when all your other apps are using the native toolkit.
- M95D 2y agoI'm doing exactly this. To me, most native apps look out-of-place and I avoid if possible. I just wish running apps in wine wasn't so slow compared to windows.
- crashdancer 2y ago>To me, most native apps look out-of-place and I avoid if possible That doesn't make sense, "out-of-place" here means with respect to the rest of the system and the shell. Doing things that way is guaranteed to result in an inconsistent desktop, so maybe you can understand why that won't really be a supported thing. For a while I actually used to do something similar to what you're doing. In the early 2000s when OS X was the new thing, I had gotten used to the Mac. So for a while I would only use Qt apps with a Mac-style theme and I would get really upset if something didn't work with it. But I stopped eventually because I realized I was being unreasonable and frustrating my own computer usage for no benefit. IMO it's helpful to recognize when you're in a harmful thought process and break out of it.
- crashdancer 2y ago>menu bars are going away because GNOME doesn't use them anymore. Where did you hear this? This is misinformation, menu bars aren't going away. The API is just changed in GTK4: https://docs.gtk.org/gtk4/migrating-3to4.html#gtkmenu-gtkmenubar-and-gtkmenuitem-are-gone https://docs.gtk.org/gtk4/migrating-3to4.html#gtkmenu-gtkmen... >GtkDialog as a notable example GtkDialog was deprecated because other changes made it now trivial for any app to re-implement dialogs with just a few CSS classes, and it's more flexible that way too. >a Rust-native UI toolkit library that does its own drawing, but can consume GTK3 themes This is never going to happen unless you re-implement nearly all of GTK3 in Rust with the exact same widget hierarchies and all the quirks of its (outdated) rendering model. Why would you want this anyway? GTK themes aren't particularly special, it's just CSS.
- nextaccountic 2y ago> Why would you want this anyway? GTK themes aren't particularly special, it's just CSS. So that non-gnome apps can blend reasonably well in Gnome (at least the colors) But, if it's just CSS, then at least an electron or tauri app can make use of it I guess?
- crashdancer 2y agoYou don't need a full CSS stylesheet just to change some colors. And no, you can't take CSS from a GTK app and use it with a web app or vice versa, the layout system and the elements/classes aren't compatible.
- nextaccountic 2y agoThe trouble is that I don't want to hardcode the colors in the app, but to learn which theme the user is using and adapt the application to use the colors of that theme (and other features if possible) If the toolkit supported this automatically, it would be easier to achieve this
- crashdancer 2y ago
- sameerds 2y ago> for example, the printing functionality that was moved from libgnomeprint (or whatever it was called) into GTK3 is staying (which makes sense), but menu bars (which have been in GTK since the beginning) are going away because GNOME doesn't use them anymore. You make it sound like menu bars are removed from GTK4. But I read the article multiple times to find where it says so. From what I understood, menu bars will stay in GTK4 but will not be represented in libadwaita because GNOME doesn't need them.