Linked by Thom Holwerda on Wed 12th Mar 2008 18:11 UTC, submitted by Pfeifer
Permalink for comment 304775
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.





Member since:
2007-08-22
I have not yet used Qt very much. However, from my research:
1) Gtk does things a lot like Microsoft when it comes to messaging. If you know how to create a GUI in Visual C/C++, then Gtk will seem native - you declare your message maps the same way.
2) WxWidgets/WxWindows is need. It does it both the Gtk/Microsoft way, and the Qt Slot way.
3) Qt does not use the Message Map structure really at all - or if it does, it's all hidden. Rather, it uses something called "Slots", which are very dynamic and you call at run time to be added to.
Qt is also its own environment that you can easily extend - this is what KDE does for their ecosystem. You also need to get familiar with the QMake preprocessor that puts a lot of the Qt stuff together for you. The downside of Qt is that you have a big check per developer if you are doing something commercial, something that is not open source. (About $4k/developer for most all platforms Qt supports.) So it can be expensive. Of course, if you are only doing open source, then there is no difference. ;-)
WxWidgets is public domain last I looked. So you can pretty much use it anywhere.
Gtk is of course, GPL or LGPL.
Otherwise, most things are equal and its a matter of preference.