The current behavior (in `master`) is to define the handling functions for events as strings. Default for `onSort` for example is `handleSort`. Commit 8cef762d11 changed this behavior forcing handling functions to be defined as functions in the options. This breaks all existing code, resulting in a no-op even with the default options (which still define the default handlers as strings).
This commit restores previous behavior AND allows you to define your handlers as functions directly, if you’re so inclined.
Only components having a state are currently working correctly with the sortable mixing. The proposed fix is to allow custom state handling method to be passed in as config.
with React v0.14 this.refs.*.getDOMNode() is deprecated,
we have to use this.refs.* instead, to reference the DOM Node.
this is a implementation, that is backward compatible
* misspelled ref in README fixed
* fixed Demo of forceFallback
modified the private _onMove prototype, so it calls events on it's
source Element like it's sibling function _dispatchEvent
added the handleMove, which listens to the onMove events to the react
mixin