Nokia Announces Qt 5 Plans

aloniv writes "Since Nokia announced its switch to Windows Phone 7, people have been worried about the future of Qt. Well, it turns out Nokia is still going full steam ahead with Qt, having just announced their plans for Qt 5. Some major changes are afoot code- and functionality-wise, but the biggest change is that Qt 5 will be developed out in the open from day one (unlike Qt 4). There will be no distinction between a Nokia developer or third-party developer."

Comments

Re:KDE5

[Randle_Revar]

KDE5 will not break the world like KDE4 did. Just as Qt5 will not break the world.

http://aseigo.blogspot.com/2011/05/relax.html
http://aseigo.blogspot.com/2011/05/qt5-kde5.html

Re:Best GUI library for C++

[Timmmm]

> The only way to do it right is to use the native controls, which QT DOES NOT.

I think you have not used Qt for a long time...

http://en.wikipedia.org/wiki/Qt_(framework)#Use_of_native_UI-rendering_APIs

Re:QT5 should drop MOC and adhere to standards

[tibit]

C++ simply does not provide the introspection needed for a major application development framework. If it did, you could drop MOC. The way it stands, moc basically generates introspection tables because the out-of-touch [expletive deleted] folks who design C++ couldn't be bothered. That's my take on it.

Every time you interface C++ code with any sort of an interpreted or JIT-ed language, you have to generate "bindings" using an external tool precisely because C++ lacks facilities for code to know about other code. Qt folks were nice enough to maintain such a tool themselves and to make it a core part of their process. I don't consider it a bad thing. QMetaObject system makes it fairly easy to expose QObjects to any other language that's either interpreted or JIT-ed.