Linked by Thom Holwerda on Wed 12th Mar 2008 18:11 UTC, submitted by Pfeifer
"On the 2008 GTK+ Hackfest in Berlin, Imendio's GTK+ hackers presented their vision of GTK+'s future and the reasons why they think that GTK+ has to make a step forward, embrace change and break ABI compatibility. Other GTK+ developers have also voiced their opinions, listing parts of GTK+ that need serious love, but state that they don't require breakage. Whether or not these are the things that will mark the road to GTK+ 3.0, almost all of them need attention. And give hints to the shape of things to come."
Thread beginning with comment 304775
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2006-07-26
Member since:2007-08-22
"WxWidgets is public domain last I looked. So you can pretty much use it anywhere.
I thought that wxWidgets used GTK+.
But since GTK+ is LGPL that means that wxWidgets isn't forced to be GPL. "
My guess (based on the wxWidgets websites) is that they treat Gtk just like any other system (e.g. Win32, WinCE, etc.). So their programs inter-operate well.
In order to use Gtk with wxWidgets though, you will need to have wxGtk (wxWidgets for Gtk) installed though.
So where with KDE/Qt you can use a lot of Qt easily (not extra bindings required), you cannot use Gtk easily with wxWidgets without installing an additional binding.
wxWidgets is really its own system - it just relies on underlying OS features/tools/libraries to function with that system (see their flash presentation), which it wraps to provide the functionality. So, while I'm not an authoritative source on this - this is just what I've seen from their website, I'd say that wxWidgets is more based on Gtk than Java is.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
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.