Linked by vivainio on Thu 14th Oct 2010 11:31 UTC
Thread beginning with comment 445102
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:
2007-08-22
Do you have citation for that?
Perhaps you are confusing using QML with doing heavy calculations with JavaScript inside QML. QML is being pushed specifically for high-FPS 2D user interfaces - this use case is pretty different from 3d games. You should do heavy calculations in C++, and let QML take care of the UI parts of the program.
If you are into 3d, you may find this QML video interesting:
http://www.youtube.com/watch?v=OXcxFZbKUNI
It's pretty cool stuff, even if with very little practical applications for now. "
Check the archives for the Qt-Interests and Qt QML mailing lists (see qt.nokia.com). There's a number of e-mail discussing what to do and not to do under QML. I might have just picked a bad example.