Flick

[sbmaxx]

Ported flick event from PolymerGestures

[dfreedm]

Same concerns as #49 (comment), then it just needs a rebase and I'll merge.

[sbmaxx]

Did rebase from master, squash. Added defaultAction = none, _source = flick

[kevinwestern]

@sbmaxx Did you mean to close this? It would be nice to have this gesture.

[sbmaxx]

I want this to be merged ;)

[sbmaxx]

ping :)

[steida]

This project seems to be dead.

[sbmaxx]

@steida so, what we should use for touch-gestures? :)

[steida]

http://hammerjs.github.io/ looks promising.

[sbmaxx]

just for the history. PR was opened at 28th august, 2014. ;)

[steida]

They even have no balls to officially kill this project like Angular has killed itself. Unbelievable, I remember better Google. Now everything interesting comes from Facebook engineering. Good to know.

[sbmaxx]

Last commit to hammer.js was on Oct 25, 2014 :/ All projects about touch-events/gestures will be dead sooner or later :)

[picitujeromanov]

i've tried hammer.js for a rather complex layout but switched to polymer gestures instead ... there's no way how to prevent event from bubbling in hammer, and you can't listen for 'down' events only ... when you call stopPropagation on a tap, you're actually stopping 'up' event, but the 'down' event was already caught on your parent which just messes things up. Also features like hammers 'requireFailure' are hard to use in angular environment. Only thing that i've borrowed from hammer (and created directive for it) is how they apply css properties (touch-action etc...) to elements on which it is applied to

[DimitryDushkin]

@picitujeromanov in hammer.js the best way to handle events is to handle them on top layer and route these events to inner elements depending on e.currentTarget.
I had similar problems with hammer.js, but this trick did job well.