- From: Nilsson, Claes1 <Claes1.Nilsson@sonymobile.com>
- Date: Thu, 17 Oct 2013 10:46:47 +0200
- To: "'Kostiainen, Anssi'" <anssi.kostiainen@intel.com>, "public-sysapps@w3.org" <public-sysapps@w3.org>
- CC: Arthur Barstow <art.barstow@nokia.com>, GALINDO Virginie <Virginie.GALINDO@gemalto.com>, "Isberg, Anders" <Anders.Isberg@sonymobile.com>, "Falk, Mattias" <Mattias.Falk@sonymobile.com>, "Edenbrandt, Anders" <Anders.Edenbrandt@sonymobile.com>
My proposal is to base this "Application management" API specification from the whole of section 4 in http://www.w3.org/2012/sysapps/runtime/, including for example the methods in http://www.w3.org/2012/sysapps/runtime/#applicationregistry-interface.
The main use case is a "web based home screen".
BR
Claes
> -----Original Message-----
> From: Kostiainen, Anssi [mailto:anssi.kostiainen@intel.com]
> Sent: den 16 oktober 2013 17:06
> To: public-sysapps@w3.org; Nilsson, Claes1
> Cc: Arthur Barstow; GALINDO Virginie; Isberg, Anders; Falk, Mattias;
> Edenbrandt, Anders
> Subject: Re: [W3S SysApps]: Application Management (was RE: Life cycle
> and security model - status)
>
> On Oct 16, 2013, at 5:06 PM, "Nilsson, Claes1"
> <Claes1.Nilsson@sonymobile.com> wrote:
>
> > Thanks for starting this thread Virginie. This is a good discussion.
> >
> > I also agree that some kind of vision/global architecture would be
> useful. Furthermore we must dig out which parts to be normatively
> standardized. Looking into the deprecated(?)
> http://www.w3.org/2012/sysapps/runtime/ specification I think that one
> part is Application Management,
> http://www.w3.org/2012/sysapps/runtime/#application-management. There
> may be some overlap with http://www.w3.org/2012/sysapps/app-lifecycle/
> but I suggest that a separate "Application management for installed web
> applications" API specification is created based on section 4 in the
> old runtime specification.
>
>
> Would this be a companion spec to the Manifest similar to what the
> Widget interface is to config.xml (i.e. an object representation of the
> parsed manifest), or something else?
>
> If we leave out the on* events and state, that leaves us with:
>
> interface Application {
> readonly attribute DOMString origin;
> readonly attribute Object manifest;
> readonly attribute DOMString installOrigin;
> readonly attribute unsigned long installTime;
> readonly attribute Object parameters;
> DOMRequest launch ();
> DOMRequest uninstall ();
> readonly attribute DOMString updateState;
> readonly attribute unsigned long downloadSize;
> DownloadRequest downloadUpdate ();
> void hide ();
> void exit ();
> };
>
> I assume you already have some use cases in mind you'd like to share
> with us?
>
> Thanks,
>
> -Anssi
Received on Thursday, 17 October 2013 08:47:16 UTC