Hi,
It's already possible to provide a QML launcher that loads remote QML applications but we have several security problems that must be addressed first. The most important one is to add a sandbox support for QtQuick in order to avoid remote applications from
loading untrusted QML modules or accessing elements outside its own scope. Without these barriers, these applications could read/write/remove personal data using features provided by local QML modules or even gain root access exploiting a vulnerability in
these modules.
But I also think it's a great idea. I've implemented a small POC one year ago (using Qt 4.7) that loads remote QML plugins inside a QWebView. It uses less than 200 lines of code. Follows a video:
http://www.youtube.com/watch?feature=player_embedded&v=VpRr5pAqBsM
Regarding distributed QML applets, it would be nice to have a package format in order to ease the distribution process and support some level of compression reducing the load time for new package versions. I've also implemented an unofficial package format
a long time ago, for QtQuick 1.0, that encapsulates everything inside a tarball and supports loading remote packages:
http://lists.qt.nokia.com/pipermail/qt-qml/2010-November/001814.html
Maybe we could have an official support in QtQuick2 in the future to address these cases. I can visualize, for example, remote applets being used in home screen, for mobile and desktop, that could be automatically updated in the server side and cached in the
local storage; applets like Weather, Feed Readers, Pastebin, Translators, etc...
Br,
Adriano