Linked by Thom Holwerda on Mon 9th May 2011 21:14 UTC, submitted by Elv13
Thread beginning with comment 472495
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
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:
http://confusingdevelopers.wordpress.com/2011/04/01/intels-qt-quick...
http://labs.qt.nokia.com/2010/09/10/building-the-future-reintroduci...




Member since:
2008-03-17
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).