W3C home > Mailing lists > Public > public-pointer-events@w3.org > April to June 2013

Re: Last Call comments

From: Konstantinov Sergey <twirl@yandex-team.ru>
Date: Mon, 08 Apr 2013 19:45:37 +0400
To: Scott González <scott.gonzalez@gmail.com>
Cc: Rick Byers <rbyers@google.com>, "public-pointer-events@w3.org" <public-pointer-events@w3.org>
Message-Id: <16191365435937@webcorp2e.yandex-team.ru>
08.04.2013, 19:24, "Scott González" <scott.gonzalez@gmail.com>:
> On Mon, Apr 8, 2013 at 11:06 AM, Konstantinov Sergey <twirl@yandex-team.ru> wrote:
>> 08.04.2013, 18:14, "Rick Byers" <rbyers@google.com>:
>>> Can you elaborate on how this is 'unusable' without gestures?  I expect consumers to continue to implement gestures in javascript as they have been already for Chrome (eg. hammer.js and other popular libraries).  They seem separate to me, but since no browser has yet shipped with pointer events and without gesture events, this is certainly an area of risk we should watch out for.  Otherwise I take a lot of comfort in the experience that has been gained programming to pointer events in IE10 (eg. I've talked with the Google maps team about their experience - which was generally positive).
>>
>> Okay, look at the hammer.js pointer code: https://github.com/EightMedia/hammer.js/blob/master/src/pointerevent.js
>> 55 lines of code are just redundant and is used to handle the simpliest things: the number of touches and the positions of touches. And this code will be completely broken if some other script on the page uses the capturing.
>
> I think it's unfair to point to an abstraction over several event types when that's exactly what Pointer Events is. If Hammer.js was coding over the Pointer Events API and mapping Touch Events to Pointer Events, the code would be very different.

This code doesn't map anything. That's just the common counting pointers problem which will be implemented by everyone.

>
>> We are forcing EVERY web-developer to write such code; we (Yandex Maps API team) wrote such code too - just because such simple things are "out of scope" and "we will provide helpers in v2". Meanwhile every single js framework will be forced to write that code.
>
> Surely that's not true. Most web developers will never write such code. They will simply use someone else's code which already does this.

In first, there are lots of code which doesn't rely on frameworks. Cartographical APIs, the different "smooth scroll" plugins, etc.
In second, any errors in this code will be repeated hundreds of times.
In third, "not so many developers need to write the same code" doesn't answer the question why we are forcing to write such code at all.

>
> Also, what's wrong with iteration? Why is it imperative that v1 contain everything?

Then between first and second iteration hundreds of developers will write thousands lines of code which will be thrown away at the V2 spec release.
Maybe we should answer then why to release v1 spec if it obviously lacks the mechanisms which are needed by every developer?

-- 
Konstantinov Sergey
Yandex Maps API Development Team Lead
http://api.yandex.com/maps/
Received on Monday, 8 April 2013 15:46:05 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:20:25 UTC