W3C home > Mailing lists > Public > public-device-apis@w3.org > November 2011

Re: Vibrator API: extract from Navigator

From: Anssi Kostiainen <anssi.kostiainen@nokia.com>
Date: Tue, 8 Nov 2011 13:23:16 +0200
Message-Id: <8252066A-D1D3-4D09-B7B3-EA59364BF51D@nokia.com>
To: "public-device-apis@w3.org WG" <public-device-apis@w3.org>
Hi,

On 8.11.2011, at 10.37, ext Dave Raggett wrote:

> On 07/11/11 21:44, Justin Lebar wrote:
>>> Having a Vibrator interface, which then Gamepad and Navigator implement,
>>> hence being reusable.
>>> 
>>> So we then get navigator.vibrate() and gamepad.vibrate(). Same API, same
>>> behavior.
> 
> Isn't this just a matter of replacing "Navigator" below with a more appropriate name, e.g. "Vibrator" and then specifying that the navigator object implements the Vibrator interface, e.g. as navigator.vibrate(1000);
> 
> partial interfaceNavigator  {
>    void  vibrate  <http://dev.w3.org/2009/dap/vibration/#widl-Navigator-vibrate-void-long-time>  (optionallong  time);
>    void  vibrate  <http://dev.w3.org/2009/dap/vibration/#widl-Navigator-vibrate-void-longArray-pattern>  (optionallong[]  pattern);
> };

Yes. Here's the new IDL which should address Joćo's reusability concerns:

Navigator implements Vibration;

partial interface Vibration {
    void vibrate (optional long time);
    void vibrate (optional long[] pattern);
};

I updated the Editor's Draft accordingly. Let me know if there are any concerns with this change.

-Anssi
Received on Tuesday, 8 November 2011 11:23:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:24 GMT