Re: [soft/philosophical] event handers in cljs

Hi François, That makes sense. I think I had read that discussion a while ago but hadn't really grokked it. Thanks! Juan On Tuesday, March 11, 2014 10:42:04 AM UTC-3, François Rey wrote: > > On 10/03/14 15:37, juan.facorro wrote: > > I have taken this approach as well, but I can can't seem

Re: [soft/philosophical] event handers in cljs

On 10/03/14 15:37, juan.facorro wrote: I have taken this approach as well, but I can can't seem to find a good answer to this question: When you create a bunch of elements with their corresponding channels to handle certain events, how do you handle the closing of those channels and the termina

Re: [soft/philosophical] event handers in cljs

Hi Sam, On Sunday, March 9, 2014 11:16:13 PM UTC-3, Sam Ritchie wrote: > > Well, I typically have multiple channels. No need to have a single global > event bus for everything. With multiple channels, you can have a bunch of > local event loops. > I have taken this approach as well, but I can

Re: [soft/philosophical] event handers in cljs

Well, I typically have multiple channels. No need to have a single global event bus for everything. With multiple channels, you can have a bunch of local event loops. t x March 9, 2014 1:43 PM Hi, Before core.async, the way I did event handling in cljs was: ## ap

[soft/philosophical] event handers in cljs

Hi, Before core.async, the way I did event handling in cljs was: ## approach 1 goog.events.listen(... , callback-func) After learning core.async, I read (and liked the idea of): ## approach 2 * (defn global-events (core.async/chan 1)) * shove all events on to global-events * ha