W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2009

Re: [widgets] Declarative support for a widget's metadata

From: Marcos Caceres <marcosc@opera.com>
Date: Thu, 19 Feb 2009 18:59:09 +0100
Message-ID: <b21a10670902190959t3025d05fm38203351ec12cd3d@mail.gmail.com>
To: Arthur Barstow <art.barstow@nokia.com>
Cc: public-webapps <public-webapps@w3.org>
On Thu, Feb 19, 2009 at 6:47 PM, Arthur Barstow <art.barstow@nokia.com> wrote:
> Marcos,
>
> A few weeks ago we talked about how a widget author could add
> widget-specific metadata (e.g. initial settings) to the config file [1].
>
> I think providing a declarative means to provide this metadata is consistent
> with existing Req #14 - Widget Metadata [2]. Additionally, at least some of
> the Widget User Agents in the Widgets Landscape document also support this
> functionality [3].
>
> The type of syntax to support this would be something like:
>
> <preference name="..." value="..."/>
>
> And the A&E's getPreference method [4] would return the value attribute's
> value.
>
> I realize an author can define all of its widget-specific metadata in script
> but having the data defined in the config file is consistent with some
> existing WUAs.
>
> WDYT?

I think this is a good idea, though it does replicate some of the
functionality provided by the setPreference API. However, if other
people want this, I'm happy to specify it. It should not be very
difficult to do. Things set by the <preference> element will
automatically appear in the preferences object at runtime (or in
session storage, if we go down that route). These values will only be
set when the widget is first run. setPreference() can override the
values once the widget is running.

Kind regards,
Marcos

-- 
Marcos Caceres
http://datadriven.com.au
Received on Thursday, 19 February 2009 17:59:53 GMT

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