search

googlearchive / polymer-gestures

84 stars 27 forks source link

Flick #50

Open sbmaxx opened 10 years ago

sbmaxx commented 10 years ago

Ported flick event from PolymerGestures

dfreedm commented 10 years ago

Same concerns as https://github.com/Polymer/polymer-gestures/pull/49#issuecomment-56715150, then it just needs a rebase and I'll merge.

sbmaxx commented 10 years ago

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

kevinwestern commented 9 years ago

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

sbmaxx commented 9 years ago

I want this to be merged ;)

sbmaxx commented 9 years ago

ping :)

steida commented 9 years ago

This project seems to be dead.

sbmaxx commented 9 years ago

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

steida commented 9 years ago

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

sbmaxx commented 9 years ago

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

steida commented 9 years ago

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 commented 9 years ago

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

picitujeromanov commented 9 years ago

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 commented 9 years ago

@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.