Draggable: dropOnEmpty option or Sortable: repurpose same

[Altreus]

I found a (brief!) discussion on whether dropOnEmpty should exist on Sortable. The answer was no.

It is useful; but it's the wrong way around. Currently in order to prevent a connected Draggable from being dropped on an empty sortable you have to disable the sortable whenever it becomes empty and re-enable it if it gains content (on the theory that drag+drop is not the only way of creating DOM content).

I would propose that dropOnEmpty should apply to the sortable itself, as to whether it will accept a droppable if it is empty; rather than whether its own items can be dropped onto empty others.

Alternatively, the options to Draggable should have a dropOnEmpty that does the same thing as Sortable's; i.e. prevents this draggable being dropped on an empty sortable.

The former, while preferable in my mind, has the disadvantage of not being backward-compatible.

[Jörn Zaefferer]

Should take this usecase into account for 2.0.0, even though the APIs for interacting with draggable and sortable are likely to change a lot.

[Scott González]

We're not going to add any drop on empty logic in the rewrite. This will need to be implemented in your app-specific logic using the provided APIs for connecting, e.g., by toggling a class when the sortable is empty.