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

User Interaction API (was: Rechartering Device APIs & Policy Working Group)

From: Robin Berjon <robin@berjon.com>
Date: Mon, 7 Feb 2011 12:43:34 +0100
Cc: Dominique Hazael-Massieux <dom@w3.org>, public-device-apis <public-device-apis@w3.org>
Message-Id: <68FE0FB8-3715-4D23-85B5-5064A0B2C591@berjon.com>
To: Bryan Sullivan <blsaws@gmail.com>
Hi,

On Feb 2, 2011, at 17:04 , Bryan Sullivan wrote:
> - User Interaction API (API to to manage vibration, beeps, and menus)

From what I've been hearing about this the primary complaint about this API is that it is too fuzzy in scope. So if it stays, it has to be really neatly delineated. To me this points to splitting out the various component, and scoping them individually. I can see how a Vibration API could be useful (for gaming, and not just on mobiles but also with game controllers or anything that might provide feedback), and that should be decided on its own singled out merit rather than bundled into a vague "UI" category.

We've also had suggestions for menuing. One participant in this group had ideas (that haven't been discussed), and I suggested something that could rely on the HTML <menu> element (but for which I haven't specified a security model, which is in itself an issue).

So what would be the individual components here?

-- 
Robin Berjon - http://berjon.com/
Received on Monday, 7 February 2011 11:44:02 GMT

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