Linked by Thom Holwerda on Thu 11th Feb 2010 18:15 UTC, submitted by martini
OS/2 and eComStation "Silvan Scherrer and Dmitry A. Kuminov have released the GA of the port of the Qt 4 application framework to OS/2 and eComStation, i.e., version 4.5.1 GA. The new release comes with complete support for drag and drop, session management, SQLite3, and includes the Qt Designer application."
E-mail Print r 0   7 Comment(s)
Thread beginning with comment 409274
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Maybe the other way around?
by Brandybuck on Sun 14th Feb 2010 08:45 UTC in reply to "Maybe the other way around?"
Member since:

You have completely misunderstood Qt. It is not its own windowing system, it uses the native windowing system on the desktop. It does draw its own controls, just like nearly every other toolkit, but it will use the underlying system to do it if it can (Aqua, Aero, etc). Yes it double buffers, because that eliminates flicker. "Alien" widgets are a huge improvement in speed, especially on X11. It doesn't replace file system and threading, it provides an C++ API on the native systems.

You imply that .NET does not do any of this, but that is wrong. Way down deep .NET is still using win32, gdi, low level files and threads, etc.

Reply Parent Score: 2

MacMan Member since:

You have completely misunderstood Qt. It is not its own windowing system,

Oh Really?,... Have you looked into the QT source code? I have, and I have the deep pain of using it a few years ago to develop a so called "cross platform application".

About all that QT uses of the native operating system is a window frame. Thats it, period. It calls the native operating system to create a window frame, then it has a pixbuff that it draws everything to, then the pixbuff is displayed in the window frame. QT uses its own "theming engine" to render controls. This is perfectly fine on Linux where QT IS THE NATIVE TOOLKIT, but bad on Windows, and an absolute disaster on the Mac.

We ended up scrapping the entire QT effort because the applications felt alien on the Windows and Mac, and ended up re-writting the UI with C# on Windows, and Cocoa on the Mac. This is the only way to write decent cross platform apps, and not short change your users: a cross platform core logic, in c++, and NATIVE UIs in C# and Cocoa.

Reply Parent Score: 1