Linked by Hadrien Grasland on Sat 15th Jan 2011 18:02 UTC
Permalink for comment 458430
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 06/13/13 14:35 UTC
Linked by Thom Holwerda on 06/11/13 17:07 UTC
Linked by Thom Holwerda on 06/10/13 23:13 UTC
Linked by Thom Holwerda on 06/08/13 14:57 UTC
Linked by Thom Holwerda on 06/07/13 11:40 UTC
Linked by Thom Holwerda on 06/04/13 12:45 UTC
Linked by nfeske on 05/31/13 10:12 UTC
Linked by Thom Holwerda on 05/29/13 16:59 UTC
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
More Features »
Sponsored Links



Member since:
2008-12-26
hardware: x86 @ 1Ghz + sgx 530 + 1GB of ram
N900 uses hardware inferior to that, and QML is pretty smooth there.
Here's an example I saw just today:
http://www.youtube.com/watch?v=ak-Py3cf_Ac
Not true. You can create a global js context by doing ".pragma library" in the .js file.
QML actually can actually cache list elements:
http://doc.qt.nokia.com/4.7-snapshot/qml-listview.html#cacheBuffer-...
I don't know what you mean by this. You can call out to javascript and c++ components from your qml components.
One year, and they didn't contact Nokia at all for help? It seems to me that any problems they encountered should be pretty simple to solve.
Most of the videos seem to have N900, but I've been running my "QmlReddit" application ok on N97 mini. It's not 60fps, but it can do okay anyway. Perhaps I could make a video someday.
OTOH, N900 is old tech today as well ;-).
Incidentally, once we switch to QSceneGraph the performance will be much greater still:
http://www.youtube.com/watch?v=n3W5O2biSPU