API: Waves.ripple(element)

[hoxxep]

Run Effect.show(e, element) on an element via an API call, and Waves.ripple(element) could mimic a click event occurring at the centre of the element, where element is a string passed to a querySelector.

Simulate mousedown and an immediate mouseup in the centre of element. I'll add this tonight, and this will simplify the mouseover/mouseleave/hover effect (requested in issue #105) as you can simply call Waves.ripple() on mouseover.

Question: Would Waves.ripple(element) check element for .waves-effect classes, or should it assume (for performance) that the necessary classes have already been set; since the user can [and should] set these through the HTML template and/or Waves.attach()?

In future, options to the function (If we used Waves.ripple(element, options)) could include setting the position of the ripple, timing etc.

[hoxxep]

Solved in pull request #113. It does not check for .waves-effect. It includes a warning in the documentation that .waves-effect should already be present on the element and could be added via Waves.attach().

Waves.calm(elements) was also added in that pull request to remove all ripples from an element. Useful when a ripple has no timeout.

[fians]

Merged.