Too bad QML wasn't ready yet for this release. When they finish it we will have a killer tool for developing more interactive user interfaces. Hell, even designers can program in QML

So for PySide support we'd have to wait for a stable release of PySide, but why not get PyQt support in Creator?

In particular, I like how containers (that provide layouts) are widgets themselves, meaning that you can put a complex layout with multiple widgets in it anywhere that you could put a single widget. That's not true in Qt (at least, not without a little extra work): there, layouts are a separate entity from widgets.

I actually like GTK. In my limited experience, in GTK, more typing is involved, but things make more sense and it's easier to get things right. In particular, I like how containers (that provide layouts) are widgets themselves, meaning that you can put a complex layout with multiple widgets in it anywhere that you could put a single widget. That's not true in Qt (at least, not without a little extra work): there, layouts are a separate entity from widgets.

This bit me recently trying to create a push-button in Qt that could accommodate arbitrary child widgets and layouts: that's just there in GTK, but I had to sub-class QFrame in Qt and override the mouseReleaseEvent (which got the job done, save for the minor quibble that the result doesn't look like a normal QPushButton).

While that is true, something about that approach just doesn't sit with me: I find treating containers as widgets to be more... elegant and orthogonal, I suppose.

Heh, well, partly because we didn't want them to look like QPushButtons: we just wanted images you could click on, without the border or background-gradient.

No disagreement! I don't think that Qt is doing anything wrong by having Layouts and Widgets be separate things, I just like the gtk way better, and find it more intuitive. It's entirely a question of personal preference.

So for PySide support we'd have to wait for a stable release of PySide, but why not get PyQt support in Creator?

Darn. Couldn't have said it much better myself; I love how smooth the animations are in KDE and how much more advanced Qt feels compared to GTK+, but I just really hate how every KDE app includes a gazillion menu entries, buttons, layouts, heck, they seem to be stuffing the whole kitchen sink in there, too.

Nokia relicensed Qt under the more permissive Lesser General Public License (LGPL) and moved all active development to public source code repositories in an effort to encourage broader community participation in the development process.

The more inclusive development model has succeeded in boosting involvement. Nokia says that Qt 4.6 is the first major release of the toolkit to include a significant amount of code contributed by the third-party developers. In a post made today at the official Qt blog, Nokia expressed appreciation to the community for the role it played in building the new version of the toolkit.

"When we opened Qt up for easier contributions back in May we were unsure what to expect. Would anyone care? Would anyone contribute?" wrote Qt spokesperson Aron Kozak. "Well we are extremely pleased to say that indeed you did contribute. We have received roughly 500 contributions for Qt and Qt Creator since we launched this initiative, and of those, around half made it into the 4.6 release."

Performance optimization work on Qt is also an important ongoing effort. One of the most important changes in that area for Qt 4.6 is the adoption of WebKit's extremely fast JSCore engine for QtScript, the ECMAScript-based scripting language that Qt provides for application extension. QtScript used to have its own interpreter implementation, but now it can benefit from the performance advantage of having JSCore's JIT backends. This dramatically increases QtScript execution speed, as demonstrated in standard benchmarks. At the recent Maemo Summit, I learned that Nokia funded the development of a JSCore JIT backend for ARM, which means that these performance optimizations will even be available on mobile devices.

Another exciting improvement for WebKit integration in 4.6 is the availability of a new DOM access API that is modeled after the popular JQuery library. You can use CSS selectors to iterate over nodes in an HTML document. A small but very nice addition is the new clearMemoryCaches method for the QWebSettings class, which will make it possible to mitigate the massive memory overhead that typically comes with using an HTML renderer in a desktop or mobile application.

"i dont use this feature so nobody else should!" on a related note, i just really hate how everyone stuffs the world with their children(aka you), which i cant use for anything.. please.. have them go away... this is what you are saying, you do realize this? Nope, it's not. To copycat you, I could just as well state: "on a related note, i just really hate how no one ever has enough stuff with them all time time, i really need first aid kit, full toolbox, kitchen sink, vacuum cleaner, 12 different screwdrivers, canister of gasoline and a toolshed with me every time i do something as simple as drink coffee" Exaggerating things is fun, isn't it? Oh, and it _clearly_ makes my post look mature and well-presented, doesn't it?

"
Darn. Couldn't have said it much better myself; I love how smooth the animations are in KDE and how much more advanced Qt feels compared to GTK+, but I just really hate how every KDE app includes a gazillion menu entries, buttons, layouts, heck, they seem to be stuffing the whole kitchen sink in there, too.

Isn't VxWorks for embedded systems only? I am not aware of a VxWorks with a GUI. Excuse my ignorance but can someone please clarify this?.

Does this mean we are going to have to rebuild Qt4-QtRuby again from scratch?

How is this going to affect KDE 4.4?

QT's problem: excessive chatting chatting between the server and client because of all the QGraphicsView stuff.

From the looks of it, QML is to QT what XAML is to .NET and WPF. Disregarding the ".NET sUxX0Rz" mentality, as I believe most languages and platforms have their own merits, would this a fair comparison?