On Thursday, November 24, 2011 5:16 AM, Arthur Barstow wrote:
Below, Darin proposes the Pointer Lock [PL] (formerly known as Mouse
Lock) spec and the Gamepad [GP] spec be added to the Web Applications
WG's charter and not the Web Events WG's charter. This is a Call for
Consensus to accept
should be sent to public-webapps at w3.org.
-AB
[PL] http://dvcs.w3.org/hg/webevents/raw-file/default/mouse-lock.html
[GP] http://dvcs.w3.org/hg/webevents/raw-file/tip/gamepad.html
Original Message
Subject:PointerLock and Gamepad APIs
Date: Thu, 24 Nov 2011 00:04
Back in September, it was proposed to expand the charter of the WebEvents
WG to include PointerLock (formerly known as MouseLock) and Gamepad APIs
[1]. This seemed like a logical home for them given that both of these
APIs pertain to input event systems.
However, one thing that became apparent
On Thu, 24 Nov 2011 09:04:19 +0100, Darin Fisher da...@google.com wrote:
I'd like to therefore propose that instead of expanding the charter of
WebEvents to include PointerLock and Gamepad, that we instead add those
APIs to another WG such as WebApps. I believe they make sense in WebApps
given
On Thu, Nov 24, 2011 at 12:04 AM, Darin Fisher da...@google.com wrote:
Back in September, it was proposed to expand the charter of the WebEvents WG
to include PointerLock (formerly known as MouseLock) and Gamepad APIs [1].
This seemed like a logical home for them given that both of these APIs
/gamepad.html
Original Message
Subject:PointerLock and Gamepad APIs
Date: Thu, 24 Nov 2011 00:04:19 -0800
From: ext Darin Fisher da...@google.com
To: public-webeve...@w3.org, Web Applications Working Group WG
public-webapps@w3.org, Arthur Barstow art.bars
