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

Re: [widgets] What does it mean to have an unavailable API

From: Marcos Caceres <marcosc@opera.com>
Date: Tue, 2 Jun 2009 16:02:46 +0200
Message-ID: <b21a10670906020702g3aaeaa4asda9087adc92ad0e1@mail.gmail.com>
To: Scott Wilson <scott.bradley.wilson@gmail.com>
Cc: Henri Sivonen <hsivonen@iki.fi>, public-webapps <public-webapps@w3.org>
On Tue, Jun 2, 2009 at 3:17 PM, Scott Wilson
<scott.bradley.wilson@gmail.com> wrote:
> I think in such a case the UA should not be expected to make frob()
> available, and the Widget should not expect frob() to be present.
>
> For example, in the Shindig opensocial runtime, client JS is injected based
> on the <require> elements of the gadget. If it isn't declared, it isn't
> injected, and if you try calling those functions they just aren't there.
>
> What this does make less clear for me is in W:A&E why you'd ever want to
> call "hasFeature()"?
>

I agree. hasFeature should probably be dropped.

-- 
Marcos Caceres
http://datadriven.com.au
Received on Tuesday, 2 June 2009 14:03:46 GMT

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