I'm real curious about the potential interplay between core.async and om/react. Bruce Hauman has a great tutorial on using core.async channels (as opposed to event callbacks) to process user input and gestures.[1] David Nolen (creator of Om) also covered core.async.[2] But these tutorials pre-date Om; core.async came to clojurescript in summer 2013, Om wasn't released until 2014.
I guess the way React handles input is by attaching event handlers to child components, so that changes to the child properties bubble up to the root component state. Is this the optimal pattern for handling events in a React app? Or is there an advantage to be gained by using core.async channels to process event input for Om/react?
I haven't seen any examples which use both core.async and Om/react, but I'm very curious about the possibility.
Ah yup, there it is in the basic tutorial, "Intercomponent communication". It is strange that I don't remember noticing that when I skimmed it. I must've been too distracted counting parentheses and trying to wrap my head around clojure syntax.
I'm relieved to know it was there the whole time and I simply missed it, thank you.
I rewrote the AngularJS tutorial in Om [1] and utilize core.async there.
The basic [2] tutorial on the Om wiki uses core.async heavily as well. Also, there are a ton of Om examples [3] within the repo itself that are a good reference.
I guess the way React handles input is by attaching event handlers to child components, so that changes to the child properties bubble up to the root component state. Is this the optimal pattern for handling events in a React app? Or is there an advantage to be gained by using core.async channels to process event input for Om/react?
I haven't seen any examples which use both core.async and Om/react, but I'm very curious about the possibility.
1. http://rigsomelight.com/2013/07/18/clojurescript-core-async-...
2. http://swannodette.github.io/2013/07/12/communicating-sequen...