About Qt5

parancibia

More here: " Just Announced: Qt 5 To Be Released Next Year":http://www.phoronix.com/scan.php?page=news_item&px=OTQyMA

kidproquo

Just had a quick read over of the Labs post...

Nothing too surprising really, Qt Components taking over from QWidgets slowly looks like it's the main thing. This was pretty much essential for really utilising the GPU in future as far as I can tell.

At a first glance it looks like it should be a pretty good foundation for the future. Exciting stuff. :-D

parancibia

A video from today on UDS (Ubuntu Developer Summit) "Jens Bache-Wiig - Snr Dev at Qt. Nokia, talks about Qt 5, Qt Quick and the future of Qt. Followed by a short Q&A session ":http://blip.tv/file/5122502

mario

Yeah, Qt 5 sounds promising

kidproquo

It's interesting to see how the comments on the labs post change. They start out really positive, then about halfway down you start getting a lot more people who think this is the beginning of the end for Qt.

ZapB

Yeah, many people seem to interpret it as Qt5 = QML + js only. It will of course still be perfectly possible to use C++ too just as we do now.

mario

Right, you need to use C++ if you need to extend QML with new types etc. Personally I think QML is really good and can't wait until the desktop components are officially supported.

I also think modularization is good.

kidproquo

The QML/ Qt Components based roadmap is pretty much identical to what Zack Rusin "suggested":http://zrusin.blogspot.com/2010/11/2d-musings.html in a blog post a few months ago.

I think if someone's Qt4 based project has done a good job of keeping the UI layer separate from the logic it wouldn't be too painful to slowly move to Qt Components . Not free, but not as hard as a lot of the commenters seem to think. Then again, if Your codebase is a crazy soup of widgets, logic and the kitchen sink, it probably is quite daunting.

Franzk

[quote author="kidproquo" date="1305016418"]It's interesting to see how the comments on the labs post change. They start out really positive, then about halfway down you start getting a lot more people who think this is the beginning of the end for Qt.[/quote]

People will always foretell the demise of something based on some proposed changes, without knowing the details, for the simple fact that humans can't stand changes that are about to happen. Turns out we are quite good at adapting to changes that have happened, but that's something most people don't think of in their first reaction.

DevMachines

Does anyone know is a any plans to add C++ exception handling into Qt5?

Like this:

@
QThread* thread = new QThread();
try
{
thread->start();
....
} except (QException& e)
{
ShowMessage("Error while thread starting");
}@

andre

There is a discussion on that on the qt5-feedback mailinglist. Archives are available online.

Franzk

Don't count on it being introduced in Qt 5.

jaak

I think QML + js is intended for web style apps. Something similar to what people are doing with WRT on Symbian. For others that need more processing, it will be the traditional c++ way. So as far as I understand, Qt 5 integrates these features into a single toolkit instead of, one for webapps and one for native c++ apps.

andre

On exception handling:
There has just been a thread on this on the Qt-5 feedback mailinglist again. Lars Knoll and Thiago Macieira pitched in. There are good arguments not to use exceptions in the Qt libraries themselves. Read back the "archives":http://lists.qt.nokia.com/pipermail/qt5-feedback/2011-June/thread.html online.

Note that the fact that Qt itself doesn't use them, does not stop you from using them in your own code.

Chuck Gao

[quote author="Jayakrishnan.M" date="1309335070"]I think QML + js is intended for web style apps. Something similar to what people are doing with WRT on Symbian. For others that need more processing, it will be the traditional c++ way. So as far as I understand, Qt 5 integrates these features into a single toolkit instead of, one for webapps and one for native c++ apps.[/quote]

I don't think so. The differences between QML and Qt C++ is not for style, but just concept of coding. It's more convenient to design and implemented UIs for app using QML. And also, you can extend your code with Qt C++ as engine or backend. So, i recommended you use this 2 together.