cyclejs-community / cycle-mouse-driver Goto Github PK

Hey folks. Here's the good news: Cycle DOM now supports selecting document and body. Awesome! Users can now do things like:

DOM.select('document').events('mouseup');

Since this is now supported, we don't need to use a driver to do this.

What shall we do with Cycle Mouse Driver? Keep it, or deprecate it?

My preference would be to deprecate it, and encourage users to go ahead and use the new DOM feature.

Does anyone see a reason not to deprecate this driver?

cycle-mouse sounds better than cycle-mouse-driver to me, and is also in line with other drivers like cycle dom and cycle http :)

Your thoughts, please?

It would be great to have streams for mouseup, mousedown and click for the whole document. It can be useful in some components who want to know about mouse events in the outside world.

i.e. const submitUp$ = Mouse.up('.submit-button'); returns a stream of mouse up events on .submit-button

Users, contributors, collaborators, please let us know your thoughts this driver! We would love feedback about the api, ideas for features we haven't implemented yet, or any compliments you'd like to send our way 😉

Thanks for using Cycle Mouse Driver, and for taking the time to give feedback, it's appreciated!

We could start with this as a reference:
http://javascript.info/tutorial/mouse-events

SImple Events:

• mousedown
• mouseup
• mouseover
• mouseout
• mousemove

Complex Events:

• click

• contextmenu

• dblclick

  We could also expose some more functionality, like the driver making a few events cross-platform.

For example, relativePositions (element$): position$.

Would help people writing cycle.js apps with TypeScript (like me).
I could take this up.