Hi,
I wanted to let everyone know that I propose to add a new feature
flag, JOYSTICK. http://webkit.org/b/66859
This flag will enable an API and events for accessing joysticks and
related devices. There's a prototype effort happening in Mozilla also
(https://wiki.mozilla.org/JoystickAPI), and the
I think it's too early to implement this. We should wait until it's a W3C draft
at least.
window.addEventListener("MozJoyConnected"..), really?
Simon
On Aug 24, 2011, at 8:36 AM, Scott Graham wrote:
> Hi,
>
> I wanted to let everyone know that I propose to add a new feature
> flag, JOYSTICK.
On Wed, Aug 24, 2011 at 9:19 AM, Simon Fraser wrote:
> I think it's too early to implement this. We should wait until it's a W3C
> draft at least.
There's certainly work to be done in improving the design. I'm not proposing
to slavishly implement the API exactly as specified there.
However, I w
On Wed, Aug 24, 2011 at 9:39 AM, Scott Graham wrote:
> On Wed, Aug 24, 2011 at 9:19 AM, Simon Fraser
> wrote:
>>
>> I think it's too early to implement this. We should wait until it's a W3C
>> draft at least.
>
> There's certainly work to be done in improving the design. I'm not proposing
> to sl
My main objection to adding this is that it's just one of many different types
of input device, and if we add these piecemeal for each device that takes our
fancy, we'll end up with a horrible mishmash of different input events.
I'd prefer a more general strategy of thinking about all the variou
We should do this right, you won't hear any arguments from me. But I
am also sure that "W3C time investment" is a code word for years of
soul-sucking bureaucratic drudgery. As such, I don't think you meant
we should be using W3C process as the measuring stick for doing things
"right" in WebKit. The
If it's helpful, I can attempt to document these bits of methodology
somewhere on our wiki.
Another thing -- perhaps we could point newcomers like Scott to Whatwg
as the forum for design discussions, rather than referring to W3C
process?
:DG<
On Wed, Aug 24, 2011 at 11:25 AM, Dimitri Glazkov wr
On Aug 24, 2011, at 19:21 , Simon Fraser wrote:
> My main objection to adding this is that it's just one of many different
> types of input device, and if we add these piecemeal for each device that
> takes our fancy, we'll end up with a horrible mishmash of different input
> events.
>
> I'd pr
On Wed, Aug 24, 2011 at 8:36 AM, Scott Graham wrote:
> Hi,
>
> I wanted to let everyone know that I propose to add a new feature
> flag, JOYSTICK. http://webkit.org/b/66859
>
> This flag will enable an API and events for accessing joysticks and
> related devices. There's a prototype effort happeni
Thanks Simon and Dimitri, I wasn't familiar with the procedure for
attacking these sorts of things.
I've started a discussion on public-webapps, which will hopefully help
to clarify a sensible API. Please add your voice if you have the time
and inclination:
http://lists.w3.org/Archives/Public/publ
Hello,
Work has started on a Gamepad (Joystick) spec in the W3C WebEvents WG.
If you're interested in commenting or participating, the mailing list
can be found at http://lists.w3.org/Archives/Public/public-webevents/
For reference, the draft in-progress can be found at
http://dvcs.w3.org/hg/web
This proposal has matured somewhat, so an update is in order.
FYI:
http://dvcs.w3.org/hg/webevents/raw-file/default/gamepad.html
http://www.w3.org/2010/webevents/charter/2011/Overview.html
We are working behind the ENABLE(GAMEPAD) flag at the moment. Mozilla is
also building a prototype of this
I share Simon's concern that that providing low level access to every possible
controller creates fragmentation, with purportedly "HTML" content that only
works on a few devices. There is no clear cut border here - it's been mentioned
that even touch events can be seen as rare - and then I advo
On Thu, Oct 6, 2011 at 11:07 AM, Alexey Proskuryakov wrote:
>
> I share Simon's concern that that providing low level access to every
> possible controller creates fragmentation, with purportedly "HTML" content
> that only works on a few devices. There is no clear cut border here - it's
> been me
On Thu, Oct 6, 2011 at 11:07 AM, Alexey Proskuryakov wrote:
>
> I share Simon's concern that that providing low level access to every
> possible controller creates fragmentation, with purportedly "HTML" content
> that only works on a few devices. There is no clear cut border here - it's
> been me
06.10.2011, в 11:12, James Robinson написал(а):
> Would you mind raising this concern in the relevant standards body (in this
> case, webevents-pub...@w3.org seems to be relevant)? Debating issues with
> standards on webkit-dev is unproductive - it does not include all parties who
> have an i
On Thu, Oct 6, 2011 at 11:50 AM, Alexey Proskuryakov wrote:
> I don't want to take a particularly strong stance against Joystick/Gamepad
> specifically, but I see codifying input device fragmentation in Web specs
> and APIs as a move in a wrong direction.
>
Why are you convinced there is input d
06.10.2011, в 13:23, Peter Kasting написал(а):
> Why are you convinced there is input device fragmentation here? My
> understanding is that the spec as proposed already handles multi-axis digital
> and analog controls so things you mentioned earlier like wheels and 3d mice
> would all "just w
On Thu, Oct 6, 2011 at 1:42 PM, Alexey Proskuryakov wrote:
>
> 06.10.2011, в 13:23, Peter Kasting написал(а):
>
> Why are you convinced there is input device fragmentation here? My
> understanding is that the spec as proposed already handles multi-axis
> digital and analog controls so things you
Hi Alexey,
The first revision of the spec (from the Scope section) is intended to
handle:
... support for devices common to current gaming systems including gamepads,
directional pads, joysticks, wheels, pedals, accelerometers.
This is based on a somewhat generic treatment of axes and buttons t
06.10.2011, в 13:49, Scott Graham написал(а):
> The first revision of the spec (from the Scope section) is intended to handle:
>
> ... support for devices common to current gaming systems including gamepads,
> directional pads, joysticks, wheels, pedals, accelerometers.
Why does the spec title
2011/10/6 Alexey Proskuryakov
>
> 06.10.2011, в 13:49, Scott Graham написал(а):
>
> The first revision of the spec (from the Scope section) is intended to
> handle:
>
> ... support for devices common to current gaming systems including
> gamepads, directional pads, joysticks, wheels, pedals, acce
On Thu, Oct 6, 2011 at 2:07 PM, Alexey Proskuryakov wrote:
>
> 06.10.2011, в 13:49, Scott Graham написал(а):
>
> The first revision of the spec (from the Scope section) is intended to
> handle:
>
> ... support for devices common to current gaming systems including
> gamepads, directional pads, jo
2011/10/6 Ryosuke Niwa
> 2011/10/6 Alexey Proskuryakov
>
>>
>> 06.10.2011, в 13:49, Scott Graham написал(а):
>>
>> The first revision of the spec (from the Scope section) is intended to
>> handle:
>>
>> ... support for devices common to current gaming systems including
>> gamepads, directional p
24 matches
Mail list logo
