[Bug 21137] Define key names for game controller of Android

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21137

--- Comment #4 from Masayuki Nakano <masayuki@d-toybox.com> ---
(In reply to comment #3)
> (In reply to comment #2)
> > I believe that D3E spec should define key names which will be used in major
> > platforms as far as possible because if it wouldn't define them clearly,
> > it'd be possible each UA vendors to give different names for same key.
> > 
> > If this is wrong, the ".key" approach is failure since it allows different
> > key names, which means ".key" is not web developer friendly.
> 
> What does "GameButtonX" mean?  On a PSX controller, the button labelled "X"
> is in the bottom-left, and is usually a primary control.  On a 360
> controller, it's the top-left button and is usually a secondary input.  On
> whatever input device Android is exposing, it might mean something
> completely different.  Saying that "GameButtonX" maps to "KEYCODE_BUTTON_X
> on Android" doesn't give a useful definition on anything that isn't Android.
> 
> Being told "the user pressed GameButtonY" doesn't tell the web developer
> anything.  It doesn't even mean "pushed a button with a Y on it"--it might
> be a controller with PSX labels, which has symbols rather than letters.

Absolutely. However, I believe that it's impossible to tell the button position
on any platform. E.g., see the controllers for PS3 or XBOX 360 in game stores.
The button position can be changed by the controller vender. Actually,
controller pad and joy stick like arcade video game machine have different
layout. However, most game has button configuration and they handle each
buttons.

So, web application as game platform needs to implement button configuration on
each application since there are a lot of different environment. But then, the
platform information and the key name should help the developers to decide
default button configuration. So, I think that .key for games is useful if the
developer checks the platform name. Therefore, I think it does make sense to
tell "button Y pressed" with key event to web applications for their
developers.

> (For that matter, why are gamepad controllers being mapped like keys?  They
> should be exposed with a joystick API, not generate key events.)

Is there such draft? And you think that any web platforms must not generate key
events for all buttons on game pad or joy stick?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 5 March 2013 01:57:12 UTC