Re: [w3c/gamepad] Add gamepad input events (#152)

". . . different games use different models for handling input."
[bangs head against wall]

. . . what do I have to do to get people to think of a joystick/gamepad as a generic HID, (in the same way a mouse is a kind of HID), instead of just going "game. . . game. . . game"?

The biggest problem I have with all of these specifications, both this one and the security implementation, is that everyone is stuck on these items being "game" controllers.  People see a joystick and the first thing they think of is some flight-sim game and that's the problem.  At the risk of quoting an old Taco Bell commercial, people don't "think outside the bun".

A joystick or game controller can be used for so many other things, like:
1.  An accessibility aid
2. A robotics controller. (My current application)
3. Part of a piece of test equipment.
4. Medical devices.
5. Home automation.

The uses are out there, it just remains to create an interface where people can use them without being confined to either a game loop or a thoughtless security model.

Please!  Let's try to think of these devices as something other than game controllers.  OK?


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/gamepad/pull/152#issuecomment-1136710532
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/gamepad/pull/152/c1136710532@github.com>