RE: 3D Pointers

On Tue, Mar 26, 2013 at 6:33 PM, Joshua Hull <jhull@leapmotion.com> wrote:
>
> Hey Jacob. You're answer makes perfect sense to me. If this is where we're headed with this, I for one am happy getting our output into shape to match the spec, and, extending the api in a non-breaking way to support the additional data available in our specific case. Does this sound reasonable?

That sounds like a good approach to me. I look forward to seeing this.

-Jacob 

On Tue, Mar 26, 2013 at 5:33 PM, Jacob Rossi <Jacob.Rossi@microsoft.com> wrote:
>
> Hi Bill,
>
> Thanks again for the providing this feedback. In today's Working Group meeting, we discussed this issue.  Consensus was that considering this for the V1 spec would pose a risk to its current trajectory. No substantial spec changes were made during Last Call, so we're on track for Candidate Recommendation very soon. So our group's decision was that 3D pointers are out of scope for Pointer Events V1, but we will consider this for V2. [1]
>
> Of note, our group did specific work in the Pointer Events V1 spec to allow for additional device type extensions [2, 3] beyond those defined in the spec. Following the guidance you'll find in spec (specifically, in the definition for pointerType [4]), it is possible to extend the APIs to support this scenario.  This could be done by evolving script libraries, like Leap.JS, or even in native implementations.  Doing so will help validate the proposed design and also build a set of use cases and example code, similar to what we had when defining touch, mouse, and pen input.
>
> -Jacob
>
> [1] http://www.w3.org/2013/03/26-pointerevents-minutes.html#item03
> [2] https://www.w3.org/Bugs/Public/show_bug.cgi?id=20219
> [3] https://dvcs.w3.org/hg/pointerevents/rev/4f83615495ef
> [4] https://dvcs.w3.org/hg/pointerevents/rev/0ea145bbafad

Received on Wednesday, 27 March 2013 14:47:05 UTC