Introduction to moveable mixin

[cmwd]

This is a part of #208.
Previously we were using jquery-ui draggable in order to move objects.

In future we should refactor this mixin to use css transform property instead of top/left.
This is why:
https://csstriggers.com/left vs https://csstriggers.com/transform

[codecov-io]

Current coverage is 20.95%

Merging #209 into master will increase coverage by 3.95%

@@             master       #209   diff @@
==========================================
  Files            19         20     +1   
  Lines           400        420    +20   
  Methods           0          0          
  Messages          0          0          
  Branches          0          0          
==========================================
+ Hits             68         88    +20   
  Misses          332        332          
  Partials          0          0          

Powered by Codecov. Last updated by bb06e1a...d718a78

[cmwd]

I updated the code to use transform instead of left/top.

before:

after:

🐎 🚗 💨 🚤 ✈️ 🐢

[magul]

These diagrams looks great, much like these created by Sam :) I'm starting review, so be aware!

[magul]

unnecessary export - we don't MOVE_START anywhere else

[magul]

Ok, I've review it. Looks like really good job! 🚀

I have some doubts if mixin here will not be an overkill (only these objects will be draggable). And You haven't removed jquery-ui from import and from package.json.

[cmwd]

And You haven't removed jquery-ui from import and from package.json.

We still need jquery-ui for drag/drop. This is only part of the issue. I wanted to split it into two pieces because of PR size.

I have some doubts if mixin here will not be an overkill (only these objects will be draggable).

Yeah, You're probably right. But I like that idea of creating separated mixins for features. Even though we use it for single element. It makes code easier to test. We might keep this code inside object module. What do you think?

[cmwd]

I found two major bugs in implementation:

1. I'm creating one scope for all instances,
2. Because I'm assign mousemove to every element it creates collision.

I should fix it till end of the week.

[cmwd]

@magul I made some major changes comparing to last version. I thought again about the way I implemented this and I didn't like it so much.
First of all I wanted to provide well encapsulated component. So I created simple function where I'm passing view instance. This way We don't need to deal so much with this, extending objects and creating pseudo private variables in Backbone classes.
Also I tested again whole thing and came out that dragging has some issues. For example when I dragged over another element. To solve it I changed the way We listening for mouseup and mousemove - now these events are global and assigned dynamically.
I changed the way we are binding mousedown. This way We don't need to reassign events.

[magul]

what false at the end here is doing?

[cmwd]

It means that these methods are read only

[cmwd]

I think we could improve this. Probably eslint has some environment settings for mocha/chai.

[magul]

Few questions, but look ok. 🚀