Re: [widgets] Declarative support for a widget's metadata from Marcos Caceres on 2009-03-16 (public-webapps@w3.org from January to March 2009)

From: Marcos Caceres <marcosc@opera.com>
Date: Mon, 16 Mar 2009 12:57:18 +0100
To: Scott Wilson <scott.bradley.wilson@gmail.com>
Cc: Arthur Barstow <art.barstow@nokia.com>, public-webapps <public-webapps@w3.org>
Message-ID: <b21a10670903160457u45b56590tc8e99a94f8018aab@mail.gmail.com>

2009/2/23 Scott Wilson <scott.bradley.wilson@gmail.com>:
> So if a <preference> value is declared, there needs to be good guidance for widget developers on what to expect - e.g. if you specify <preference name="x" value="y"> in the manifest, don't always assume that this will be set by the engine, and have your JS able to handle getPreference("x") returning null and not "y".
>

No, we will make it a MUST that preferences shows up at runtime (at
least on first run) as part of the  Storage object.

Kind regards,
Marcos



-- 
Marcos Caceres
http://datadriven.com.au

Received on Monday, 16 March 2009 11:58:05 UTC