Although I haven't tested your specific scenario, what I've found with regards to QML performance on embedded devices for our project is, that it takes time to instantiate the QML instance hierarchy. So if you have a choice between creating a lot of QML Items (where maybe only a few are visible at once), it may give you better performance using JavaScript to handle the dynamics.
-Pelle On Wed, Jun 1, 2011 at 4:01 AM, 조성욱 <[email protected]> wrote: > > hello ! > > I have ever worked about ui using qml. it was consist of many number > image. > > so I first worked for it using many "switch case and if else " but it was > not easy to fit a position and size like ui guide. in fact i tried to make a > short code. (it took a long time) > > second, i tried to use a qtcreator's qml designer. it is very easy. It > generates many states. but code length is very long. > > so I wonder which faster is. qml's code length doesn't care its speed ? > > although long length code, I couldn't feel its speed down. but problem is > when running on low speed embedded platform. > > how about you ? is there anybody who have tested this ? > > Anyway Making a ui using a hand is very difficult. > > good luck . > > > > > > > > > > > > > > > > > > > _______________________________________________ > Qt-qml mailing list > [email protected] > http://lists.qt.nokia.com/mailman/listinfo/qt-qml > >
_______________________________________________ Qt-qml mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt-qml
