Some feedback from the top of my head. I may be looking at a completely wrong place:
http://doc.qt.nokia.com/qtmobility-1.1.0/qml-plugins.html The "Location" link takes you to a wrong looking place: http://doc.qt.nokia.com/qtmobility-1.1.0/qml-location.html About Multimedia: http://doc.qt.nokia.com/qtmobility-1.1.0/qml-multimedia.html This should tell whether you can use something apart from an URL. E.g. how would you hook up gstreamer to this, now or in the future? Or is this entirely off topic for Qt Mobility Multimedia? Can 'source' be something more abstract than an url? Should there be a separate "MediaSource" qml component that would be referred to instead of url string? About Gallery: http://doc.qt.nokia.com/qtmobility-1.1.0/qml-gallery.html The filter structure seems way too declararative to me. Could it have an alternative api where filter was just a javascript function: filter: GalleryWildcardFilter { property: "fileName"; value: "*.jpg"; } => filter: function (elem) { return elem.fileName.match(/.*jpg/); } This would be more natural to most programmers, and it makes debugging easier (you can use console.log etc. in the function). I realize the declarative way can be optimized in the query level in the backend, but a slow-but-easy api would be nice for development phase. Same probably applies to Messaging. -- Ville M. Vainio @@ Forum Nokia _______________________________________________ Qt-mobility-feedback mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-mobility-feedback
