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.
Permalink for comment 472485
To read all comments associated with this story, please click here.
RE[4]: Meh
by vivainio on Tue 10th May 2011 09:14 UTC in reply to "RE[3]: Meh"
vivainio
Member since:
2008-12-26


I should point out on the ui level silverlight is a pretty similar concept to QtQuick but uses XAML instead of javascript.


The big difference between QML and XAML is that you just can't add nontrivial logic to XAML; all the logic ends up in C# file. XAML can only do the "declarative" part, i.e. you can do simple bindings there.

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 ;-).

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


What does this mean?

Reply Parent Score: 2