I spoke to some of the encapsulator guys at the SF conference. One concept I brought up is that by launching apps with some other declarativeview binary other than meego-qml-launcher may cause some problems.
For better or worse, meego-qml-launcher cooperates in some features needed by meego apps. It loads translation info on language changes, it currently reads the theme config file and exports values to qml (tho thus will change). At one point the launcher was going to participate in the save-and-restore functionality, though that was changed. In short, there is not stated requirement we have to enable meego apps to run well when launched with something other than meego-qml-launcher. [Sent from my phone] ----- Original Message ----- From: Andy Ross [mailto:[email protected]] Sent: Wednesday, June 01, 2011 08:53 AM To: [email protected] <[email protected]> Subject: Re: [MeeGo-dev] MeeGo app model in 2012: Rethinking the MeeGo app model to be more platform agnostic On 05/31/2011 08:40 PM, Akkana Peck wrote: > Is there a way to package an html+javascript app on meego so > that it has a desktop icon and shows up in the apps menu without > needing an architecture-specific C++ Qt wrapper? The Intel AppUp people are working on exactly such a product: http://appdeveloper.intel.com/en-us/tags/intel-appup-encapsulator It's still in alpha, I haven't actually used it, and it doesn't support anything but existing web standards APIs. But it appears to do what you want. I don't know what the status is of getting the runtime into MeeGo core. Andy _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
