Linked by Eugenia Loli on Fri 10th Aug 2007 02:53 UTC, submitted by J. M.
Thread beginning with comment 262332
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
you can write Qt apps in python, ruby or java (to name three) so the "if you like C++" is really a non sequitur =)
that said, i completely agree that a better reason to pick between the toolkits is API design (for me this includes consistency, clarity, speed in use and documentation) which is a place where Qt has always shined brightly.
For programming C++, Qt is a toolkit that aims at making your programming easier. Gtkmm (the C++ layer of GTK) is a big mess to me compared to Qt, because of horrible docs , and very complex, barely documented APIs using templates. Still though, I think the signals system in Gtkmm (libsigc++) is much nicer than Qt Signals (argument binding is extremely useful) and doesn't need a preprocessor.





Member since:
2007-07-25
I was wondering what toolkit to use. To be honest I was really unsure, but finally I bought a GTK+ book. Now I am not so sure anymore. This flickering has been something I have been annoyed at for years, and pretty much makes QT superior with a great margin...if it works that is