On Mon, Dec 27, 2010 at 7:40 PM, qt next <[email protected]> wrote: > I am trying to create a new application that use qml for interface (to > visualize and edit datas). I understand how to use qml with some simple > model (list, ...) : but in the real life, is it better to use one complex > QAbstractItemModel that acces all the data of my application (with complex > tree ...) or to have a lot of qabstractitemmodel simpler (list, ...), or to > not use at all qabstractItemModel ? is there any feedback from people that > use now QML in the true life (not a simple contact list ,...) ?
I am using this succesfully for moderate amounts of data: http://wiki.forum.nokia.com/index.php/Using_QStandardItemModel_in_QML If you have ginormous or naturally lazy models, a custom model could come in handy but "benchmark first" - it may be you don't need anything more complex. -- Ville M. Vainio @@ Forum Nokia _______________________________________________ Qt-qml mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt-qml
