W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2012

Re: [manifest] Is the Webapp Manifest spec ready for FPWD?

From: Tobie Langel <tobie@fb.com>
Date: Mon, 4 Jun 2012 10:03:54 +0000
To: Fabrice Desre <fabrice@mozilla.com>
CC: Marcos Caceres <w3c@marcosc.com>, Adam Barth <w3c@adambarth.com>, "Arthur Barstow" <art.barstow@nokia.com>, ext Anant Narayanan <anant@mozilla.com>, public-webapps <public-webapps@w3.org>, "public-native-web-apps@w3.org" <public-native-web-apps@w3.org>
Message-ID: <CBF25436.84CBE%tobie@fb.com>
On 6/2/12 6:54 AM, "Fabrice Desre" <fabrice@mozilla.com> wrote:

>On 06/01/2012 02:36 PM, Tobie Langel wrote:
>> On Jun 1, 2012, at 9:58 PM, "Marcos Caceres" <w3c@marcosc.com
>> <mailto:w3c@marcosc.com>> wrote:
>>
>>> Sounds good. AFAICT, Moz's proposal doesn't really cover packaging
>>> either ... Not in the sense of wrapping the app using zip or
>>> something. More metadata, feature control (potentially relevant to
>>> requiring certain SysApps API), and lifecycle management.
>>
>> Agreed. I'd be curious to see how it's planning to interact with
>> AppCache (if at all). Also whether integration with a JSON version of
>> AppCache has been considered.
>
>We're working on pre-loading the appcache at install time when the
>appcache path is specified in the manifest. See
>https://bugzilla.mozilla.org/show_bug.cgi?id=702369 for the b2g support,
>and https://bugzilla.mozilla.org/show_bug.cgi?id=753990 for desktop
>support.

That sounds nice. How do normal web pages link to their own config file? I
haven't seen that mentioned in the spec draft.

--tobie
Received on Monday, 4 June 2012 10:06:55 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:52 GMT