Linked by Thom Holwerda on Tue 8th May 2012 11:56 UTC, submitted by nej_simon
Thread beginning with comment 517367
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.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
2010-06-08
To be precise, QML is derived from JavaScript. But we are talking in general. Qt easily allows combining interpretive QML UI with native code backend. So the advised way is it to implement (potentially performance hungry) logic in C++, while the UI in declarative QML.
It's not stillborn though, since Qt has several serious participants (including KDE), and Nokia intends to use it heavily for their lower end devices, which are not polluted by MS yet.
Edited 2012-05-08 21:14 UTC