- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Thu, 10 Nov 2011 15:23:36 -0800
- To: Scott Graham <scottmg@google.com>
- Cc: Arthur Barstow <art.barstow@nokia.com>, ext Anssi Kostiainen <anssi.kostiainen@nokia.com>, "public-device-apis@w3.org WG" <public-device-apis@w3.org>, public-webevents@w3.org
On Thu, Nov 10, 2011 at 3:12 PM, Scott Graham <scottmg@google.com> wrote: > Hi device-apis and webevents, > > I'm not sure what the correct protocol for this is, but it seems like > the gamepad and vibration APIs ought to be coordinated. > > Specifically, the vibration API assumes only one connected vibrator > and thus it's on "navigator" (which seems suitable for phones, etc.) > > My initial thought would be that the same Vibration Interface would > also appear on Gamepad, so a connected gamepad would have > .vibrate(time) and .vibrate([pattern]). This seems reasonable. One could even have a device which can, itself, vibrate (controlled via the navigator interface) and which can have gamepads hooked up to it which can vibrate (controlled via the gamepad interface). > As the DAP is set up to handle things related to vibration, could the > vibration spec simply add a reference to the Gamepad spec, and make > the addition of having Gamepad implement Vibration? (as well as > Navigator of course) Yes, that sort of reference is acceptable. ~TJ
Received on Thursday, 10 November 2011 23:24:28 UTC