"Nowadays, it is difficult to imagine many applications being able to function without relational databases to back them up. For this reason Qt provides a range of classes in the QtSql module [.pdf] that work with various relational database management systems. Relational tables and queries can also be used as the basis of Interview models."
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2005-12-21
I have to agree with you, QT is an excellent framework. However, I wouldn't recommend using it for Java. By doing so, you sort of get the disadvantages of both systems. Your code will be platform dependent, and it will still load slower than a well written C++ app.
Qt is a cross-platform framework, so the code will not be platform dependant.
Besides, java allready have a GUI API that is equally good as QT. There is nothing you can do in QT that you can't do in swing. The only reason for using QT for java would be if you know QT, but not java swing.
Last time I looked, the Swing native look-and-feel was quite bad compared to Qt. Also, you couldn't easily do things like dynamically add/remove items from menus in Swing. The Java listener event model is also much more cumbersome than signals and slots.
Has Swing changed so much since I last looked?
Edited 2007-07-18 23:06 UTC
Member since:2005-09-21
I have to agree with you, QT is an excellent framework. However, I wouldn't recommend using it for Java. By doing so, you sort of get the disadvantages of both systems. Your code will be platform dependent, and it will still load slower than a well written C++ app.
Well not quite. Your code will still be cross platform, since both Qt and Java are cross platform. Of course you will be relying on some native libraries, so you will have to distribute different Qt libs for each platform you intend to support. The code however will be the same.
Also, while you do have the overhead of Java, if you heavily use Qt functions, it should be faster than using the Java class library, because all the heavy lifting is done in native code. You also get better integration into the platform than you can get with Swing.
Besides, java allready have a GUI API that is equally good as QT. There is nothing you can do in QT that you can't do in swing.
Of course, there is also nothing that you can do in Qt that you can't do in pure C, but it will be a lot more work without Qt. Swing is ok, but the API design still isn't as straightforward to use as Qt (at least in my experience). Then there is the system integration issue, as well as performance. Keep in mind that Qt is not just a GUI toolkit (as this article demonstrates), and if you're using it for database access or any of the hundreds of things it does, you might as well use it for the GUI as well. It will certainly look more native than a Swing UI.
Edited 2007-07-18 23:03
Member since:
2005-07-06
I have to agree with you, QT is an excellent framework. However, I wouldn't recommend using it for Java. By doing so, you sort of get the disadvantages of both systems. Your code will be platform dependent, and it will still load slower than a well written C++ app.
Besides, java allready have a GUI API that is equally good as QT. There is nothing you can do in QT that you can't do in swing. The only reason for using QT for java would be if you know QT, but not java swing.