Linked by Thom Holwerda on Mon 9th May 2011 21:14 UTC, submitted by Elv13
Qt 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, since it has just announced the 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.
Thread beginning with comment 472495
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: Meh
by _txf_ on Tue 10th May 2011 09:51 UTC in reply to "RE[4]: Meh"
Member since:

You can start going on about enforcing the separation of concerns as being a good thing, but you would only be covering up inherent flaws of selecting XML as the ui annotation technology ;-).

you'll get no argument from me there

"From what I've seen of qtquick binding to the ui is not as intuitive as in silverlight."

What does this mean?

It could be from my lack of familiarity. Or it might stem from silverlights more complete widget library but there are more explicit/predefined ways of binding events to the underlying logic or exposing events to the ui layer (the whole Model View ViewModel thing).

Then again the ViewModel approach is not required in Qt quick due to the ability to do as you said non-trivial logic can be done in the ui layer.

(just for clarity the view-model is essentially the controller architected as a model for the ui, the view is almost pure graphics and the model is the same as always).

Reply Parent Score: 2

RE[6]: Meh
by vivainio on Tue 10th May 2011 09:57 in reply to "RE[5]: Meh"
vivainio Member since:

Or it might stem from silverlights more complete widget library

Ah, you were contrasting against raw qml. Luckily we have Qt Quick Components hitting production status in the following few weeks:

Reply Parent Score: 2