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

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

From: Bryan Sullivan <blsaws@gmail.com>
Date: Wed, 9 Feb 2011 00:11:48 -0800
Message-ID: <08E80F6A993E4089A4CED021A0161074@ITServices.sbc.com>
To: "Robin Berjon" <robin@berjon.com>
Cc: "Dominique Hazael-Massieux" <dom@w3.org>, "public-device-apis" <public-device-apis@w3.org>
Examples are :
- vibration
- lights
- sound-based notifications
- change UI elements such as wallpaper
- chrome elements (e.g. menus, title bar, etc)
From: "Robin Berjon" <robin@berjon.com>
Sent: Monday, February 07, 2011 3:43 AM
To: "Bryan Sullivan" <blsaws@gmail.com>
Cc: "Dominique Hazael-Massieux" <dom@w3.org>; "public-device-apis" 
Subject: User Interaction API (was: Rechartering Device APIs & Policy 
Working Group)

> 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 Wednesday, 9 February 2011 09:14:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:32:25 UTC