westures v1.0.0 Release Notes

    • ๐Ÿš€ Official first release! The engine is no longer considered to be in beta.
    • ๐Ÿ”จ Refactor Smoothable to be a data type, not a mixin.
    • โœ‚ Remove the Binding class and integrate with the Gesture class. It was more of a hindrance than a help on its own.
    • Provide automatic detection of enabled and disabled gestures, including using keys to enable and disable, in a simple way such that gestures don't need to check if their enabled inside their hooks.
    • 'cancel' phase is now properly called.
    • Region class now takes an optional 'options' object instead of lots of arguments.
    • โœ‚ Remove the 'getProgressOfGesture' method from the Input class. Gestures should track their progress internally, on their own instance!
    • โœ‚ Remove the 'radius' property from the outgoing data. It didn't seem useful and was just cluttering the output.
    • ๐Ÿ‘‰ Use Sets for tracking Gestures inside the Region instead of Arrays. (Faster access operations).
    • โšก๏ธ Update the Press gesture to allow multiple presses, one after the other, by adding successive inputs. Effectively makes it a multi-touch press! Single touch press is still possible using the min/maxInputs options!
    • ๐Ÿ‘‰ Use a Pivotable base gesture type for Swivel and Pull.
    • ๐Ÿ‘Œ Improved documentation by showing all of westures-core
    • ๐Ÿ”„ Change pivotCenter -> dynamicPivot, default to false
    • Clean up Rotate implementation to reduce reliance on side effects
    • 0๏ธโƒฃ Switch to using pointer events by default, combined with setting touch-action: none on the gesture elements (not the region itself).
    • Provide options on the Region for choosing whether to prefer pointer events over mouse/touch events (preferPointer) and what to set the touch-action property to on gesture elements (touchAction).
    • 0๏ธโƒฃ Default to using the window as the region if no element provided.
    • โž• Add mouseleave to the CANCEL_EVENTS
    • ๐Ÿ“ฆ Include the core engine as a git submodule instead of relying on the npm package.
      • Keeps the core code out of node_modules which simplifies a lot of things...