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."
Permalink for comment 304752
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Member since:
2006-07-26
As someone who has never created a GUI in anything other than Java and VB, I am torn between learning GTK+ / wxWidgets, and QT.
QT looks attractive because it has more stuff like XML, collections, networking, threading etc. That is also what makes it unattractive for using QT with languages like Java or Python which already have all that stuff.
Using GTK+ looks attractive because it seems like it is just a GUI toolkit and you can use what libraries you want for the other stuff. But then you can get yourself into trouble if a library you choose isn't supported on all the platforms you're interested in or it may get a little hacky using cygwin / mingw on Windows etc.
Right now I'm learning Python by reading a book just on Python. I'm already writing command line scripts, doing DB stuff etc. Next I plan to survey both GTK+ and QT and make a decision where to devote my brain.
Hopefully how nice QT or GTK+ are to work with in Python reflect how nice they are to work with in C, C++ too.