Re: [widgets] Device Specific APIs and Services

On Fri, Jun 20, 2008 at 11:37 AM, Marcos Caceres
<> wrote:
> APIs are identified as resources via URIs. For
> example:
> <widget>
>        <access network="true">
>                <requires id="gps"
>                                     src=""

This worries me. see clsid: and the problems of activex for porting platforms.

(I work on microb, and we're trying to have support for the series 60
browser widgets which have a number of things which I really don't
like and which we can't easily implement.)

>                                     type="application/jar"
>                                kind="api" />
>        </access>
> </widget>

> The interfaces that bind this binary component to JavaScript would

bad. Is api.jar really the binary component?

If what you mean is that api.jar contains an IDL file or something
equivalent to this, then it may be OK, although the language
definitely needs work.

> need to be standardized and I have no idea what they would look like
> at this point.

> interface APILoader{
>  attribute APILoader APILoader(DOMString id); // the id declared

sorry, i don't recognize this syntax. typically attributes don't take arguments.

>  void load();         //load the API
>  void cancel();     //cancel loading

what happens if the load has already finished?

can i unload() ?

>        gps = loadedAPI.bind();

you declared load() earlier, not bind().

Received on Friday, 20 June 2008 10:32:49 UTC