W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2014

Re: [gamepad] Haptic Feedback/Controller Vibration

From: Florian Bösch <pyalot@gmail.com>
Date: Thu, 3 Apr 2014 18:05:05 +0200
Message-ID: <CAOK8ODj7S0UAipV8+reKJxWkw+zbSq_w2zQcQF4szkbXvOXjuA@mail.gmail.com>
To: "Patrick H. Lauke" <redux@splintered.co.uk>
Cc: Webapps WG <public-webapps@w3.org>
Every controller is an assemblage of input and output hardware. It's vastly
much easier to to oversee what kind of devices you'll get which are:

   - Buttons (down or up)
   - Axes (scalar value)
   - Rumbles (speed)
   - Motors (negative/positive force and/or scalar value for position)
   - Screens (bitmap)
   - Lights (intensity and/or color)
   - Touchpads (touch events)
   - Text displays (text)

That's not a "monolythic API", that's how every other game controller API
in existence on any platform works (like evdev, DirectInput, etc.). The
attempt to wrap specific usecases is what is a monolythic monster API that
tries to be everything and the kitchensink in the end.

On Thu, Apr 3, 2014 at 5:55 PM, Patrick H. Lauke <redux@splintered.co.uk>wrote:

> On 03/04/2014 16:43, Florian Bösch wrote:
>> But even so, what do you want to end up with?
> What do YOU want to end up with? A single monolithic API that covers each
> imaginable type of controller (which may also feature output components
> like additional lights, OLED displays, etc)?
> P
> --
> Patrick H. Lauke
> www.splintered.co.uk | https://github.com/patrickhlauke
> http://flickr.com/photos/redux/ | http://redux.deviantart.com
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
Received on Thursday, 3 April 2014 16:05:33 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:23 UTC