4 ms·
This post was written by Morten Welinder, the author of Gnumeric and a popular GNOME blogger. I feel really bad for GTK developers. The GNOME guys have clearly
by scrollaway 12y ago
This post was written by Morten Welinder, the author of Gnumeric and a popular GNOME blogger.
I feel really bad for GTK developers. The GNOME guys have clearly taken the toolkit from a "general purpose" direction to a much more gnome-centric one.
At the same time though, I can't help but be hopeful for the future. Qt is a wonderful project, with a bunch of wonderful licenses, developed in a wonderfully-open environment (It's not like before!) and with wonderful improvements already available in Qt 5. With more and more applications switching to it, I see Qt as a central part of the Linux desktop ecosystem in the future - finally, not only will we have a beautiful desktop with common themes for all apps, but also the power of a truly cross-platform toolkit in most Linux apps. It will be nice.
- maxlybbert 12y agoI've always preferred Gtkmm over Qt. That might be because Gtk+ (and Gtkmm) doesn't try to be an "everything, including the kitchen sink" library (and, in related news, I've never been a fan of the Gnome API -- even though I was a fan of the Gnome desktop until Gnome 3). However, it's always seemed a little perverse to me to have Gtk+ try to imitate '90s-style C++ in C, and then to use a C++ wrapper around that.
- scrollaway 12y ago> doesn't try to be an "everything, including the kitchen sink" Qt5 and its modularity is the answer to your concern. If you don't want everything including QtKitchenSink, you can limit yourself to QtCore.
- chris_wot 12y agoThe signals system of Gtkmm seems pretty neat.
- jesuslop 12y agoI agree, gtk2 was very nice and pleasant to learn, though gnomers have let the other camp to eat their lunch.
- jeorgun 12y agoI feel really conflicted about Qt. On one hand, as a graphical toolkit/environment, it's great. It's well-structured and easy to use, and QML is basically everything web applications should have been. On the other hand, as a C++ library it really couldn't be worse, with its flagrant reinvention of the standard library, pervasive UTF16, complex object hierarchies, raw pointers, extensive use of macros, etc., etc. Maybe I'm just too choosy, but it'd be really nice to have a graphical toolkit that didn't have such an air of sausage factory to it.
- derefr 12y agoHow would people feel about a cleanup-focused API-compatible fork of Qt, in the style of LibReSSL?
- scrollaway 12y agoIt would be stupid and pointless? The Qt Project is an incredibly open environment. You want cleanups, go and file some PRs. WTF is it with people's first instinct being "let's fork instead of contributing fixes"?
- KAMiKAZOW 12y agoNot everybody likes Qt's CLA.
- scrollaway 12y agoAnd by "Not everybody" you of course mean "People who don't know any better", right? The Qt legal situation has changed a lot lately, especially since Nokia went out of the picture. Look it up: https://qt-project.org/legal.html https://qt-project.org/legal.html
- KAMiKAZOW 12y agoThe situation is that a CLA is still required. Personally, I don't care (I'm just a consumer who is not affected by the CLA). Others care and insulting them as "People who don't know any better" is not right.