InfoWorld: Qt is still a prime choice for toolkits even if you ignore its greatest strengths
Aug 06, 2000, 19:10 (2 Talkback[s])
(Other stories by Nicholas Petreley)
Re-Imagining Linux Platforms to Meet the Needs of Cloud Service Providers
"I've been itching to work with Qt in more depth since I
took a look at it some weeks ago, so I took the plunge and went for
Qt and C++."
"At first I thought my biggest obstacle would be getting more
proficient with Qt. But it was the process of relearning C++ that
gave me the most trouble. After all, I've only written a few useful
C++ programs, and that was many years ago. Sure, I have an
excellent memory, but it's short. So I forgot even some of the most
basic principles of C++ programming...."
"In view of the fact that I'm not using one of the best features
of Qt, was the effort to relearn C++ worth it? Absolutely.
Programmers of GUI-based Linux applications tend to lean toward
either C++ and Qt or C and the Gimp Toolkit (GTK)."
- Freshmeat: Response to Troll Tech on Qt, KDE, and the QPL(Jul 17, 2000)
- Freshmeat: Trolltech on Qt, KDE, and the QPL(Jul 01, 2000)
- Trolltech.com: Qt Designer: ...Cross-platform GUI Builder for the Qt Application Framework(Jun 29, 2000)
- Advogato: A possible solution to the Qt/KDE license dilemma(Jun 20, 2000)
- Freshmeat: Why Debian Doesn't Include KDE(Jun 18, 2000)
- LinuxWorld: On the Qt -- Discover the object library behind KDE(Apr 02, 2000)
- osOpinion: Who Redhat Should Really Buy(Dec 03, 1999)
- Qt 2.0 released(Jun 25, 1999)