TouchAction and Gesture support for Ember Applications
npm install ember-gesturesEmber Gestures 
==============
Ember Gestures provides an easy way to use gestures by making it simple to define and use HammerJS managers
and recognizers throughout your app.
When installed via ember install ember-gestures, it will additionally install ember-hammertime
to use for "fastclick" support.
Join the Ember community on Discord
ember install ember-gestures
This will run the default blueprint which additionally installs HammerJS.
#### Recognizers and Managers
A Recognizer detects a gesture on a target element by listening to received touch, mouse, and pointer events
and passing through a series of rules to determine whether it's gesture is occurring.
Recognizers are registered with a Manager, which emits the recognized gestures for consumption by your app.
This addon does the grunt work of creating Managers and wiring up Recognizers for you. All you need to do
to use gestures is tell your app where you want a Manager to be created and what Recognizers it should have.
Example
``js
import RecognizerMixin from 'ember-gestures/mixins/recognizers';
import Ember from 'ember';
const {
Component
} = Ember;
export default Component.extend(RecognizerMixin, {
recognizers: 'pan tap press'
});
`
The component would create a new Manager and add the recognizers for pan,
tap, and press.
The component would recognize gestures based on events originating on it or it's child elements.
The corresponding gesture would be capable of being handled anywhere in the DOM branch in which the component
exists.
Example Dom Tree
`
body
|_ div 1
|_ component A
|_ div 2
|_ component B (with recognizers)
|_ div 3
In the above example, input events originating on component B or div 3 would be passed to the recognizers.component B
The emitted gestures are triggered on the element which began the gesture (also or div 3 andbody
bubble up to . This means that component A would also be capable of handling gestures emitted by thediv 3
manager on component B. If had an action handler that utilized a gesture, it too would be able to usediv 3
gestures emitted by component B if they had begun on or within .
This means you should be strategic about where you put your components with Managers. You don't need a lot of
Managers, you just need them placed strategically. You could even put one at the base of your app, but be
warned pinch rotate pan and swipe can break scrolling behavior if not placed correctly.
##### Note
pan and swipe are horizontal only (configured this way to avoid breaking vertical scroll).vertical-pan and vertical-swipe are vertical only (configured this way to avoid breaking horizontal scroll).
##### Modifier
As an alternative to using the RecognizerMixin, you may use the {{recognize-gesture}} modifier. This is particularly useful when you are applying the recognizer to an element within the handlebars of your component, rather than to the root element of a component, and vital when your component _has_ no root element, as when you use Glimmer components or components with tagName="".
Example When using Also, if you are using objects derived from The modifier can only be used with Ember 2.18 or later. #### Using Gestures Using gestures emitted by Hammer recognizers with Ember is almost like using any other event with Ember. Example const { export default Component.extend({ Gesture events bubble through the DOM, so you can use them with actions as well. #### Create A Recognizer This will generate the file ##### Note Although we have provided an example for An #### Increase the size of touchable areas to improve user experience on small controls Sometimes smaller buttons or critical buttons need a larger capture area than their visible area. Components available by default include jQuery events come with baggage, and using the Don't add recognizers to components created within an Contributions are very welcome. When making a PR try to use the following conventions: Commit Messages: Examples: - chore(deps): bump deps in package.json and bower.json Branch Naming: Examples: - chore/bump-deps
`hbs
`
Gestures to recognize are supplied using positional parameters on the modifier. Hammer manager options can be supplied using named parameters on the modifier. with these events, you must use the real DOM event names, which are lowercase without hyphens. So your event for "double-tap" would be "doubletap". EmberObject, like Ember components, avoid using action names that are the camel-case form of the gesture names, like doubleTap, as these are also the names for the component's generated event listeners, and may get unexpectedly triggered when an event bubbles up to the component as well as when your {{on}} action fires on the element. (This is one more reason to migrate to Glimmer components, which don't automatically add event handlers to your namespace.) Events
Your recognizers will be configured to emit , so to consume a gesture, you just need to add an`
event handler to your component. The handler's name just needs to match the camelCase version of a gesture
event.js`
import Ember from 'ember';
Component
} = Ember;
panStart(e) {
// do something with the event
}
});hbs
`.double-tap
Once you've filled out the recognizer (see ./addon/recognizers/ for examples),
it will be available to use in your app just like the default recognizers. and single-tap in the addon/recognizers folder, theydouble-tap
are for demo purposes only and do not ship with the actual addon because they are non-standard.
If you'd like to enable these recognizers for your own app; for instance ; execute:ember g recognizer double-tap file will be created. Inspect its contents and replacedouble-tap.js
it with the example from this addon's codebase.context-element
You can increase the area that recognizes touch events for a specific button with a little bit of CSS.$3
, fast-action, and fast-async.swiperight$3
The jQuery events you need to trigger are the Hammer variant, meaning it is entirely lowercase , panup.trigger helper executes handlers in a different order than theytrigger
would otherwise execute, and in some situations will cause a handler to execute twice. If you are experiencing
issues with testing gesture events, try creating your own helper that uses native APIs instead of jQuery{{#each}}
to trigger the event.Tips and Tricks
loop. Use a recognizer at the base of theeach instead.type(shortname): action based descriptionContributing
- docs(component): document the componenttype/short-description`
- docs/fast-action-component