"Reactive Sequences" (asynquence's "reactive" pattern) about asynquence HOT 3 CLOSED

Cool :). That's a good start!

I still think that the button event handling is still quite visible in the code.

What do you think about:

ASQ
.reactTo('.button')
.clicks()
.then(...)

You'd have the reactTo wrapper for the element searching and then that can get clicks() or any other event that is out there and then transform it. Clicks can optionally receive the button and send something from it if you need it.

I think DSL looks clearer that way!

from asynquence.

It looks cleaner, but significantly expands the scope of what asynquence does, and I think unacceptably so. I do not want to replicate any sort of event handling/binding/management in asynquence, there are already plenty of them out there, plenty of frameworks, etc.

The narrow goal of asynquence is to be able express async flow-control in a friendly way, without the overhead of promises. The expanded vision this includes is easy integration with any other auxiliary patterns that people are using to create or initiate asynchronicity.

So, providing an easy way for an event handler to fire off multiple sequence chains is within scope, but providing a way to do the event handling itself is outside of the scope.

Hope that makes sense. Thanks for the feedback! :)

from asynquence.

That makes sense!

from asynquence.