Yes I've found that using channels to communicate back up the tree and propagating changes back down works reasonably well. Just takes some getting used to.
On Wednesday, January 15, 2014, Ruslan Prokopchuk wrote: > Component is dropped by user near some position, in render this component > sees it and snaps itself to this position. Then component and position ids > should be reported to app global state. I've done it in render, but now I > think about putting message with ids into core.async channel and process it > somewhere in logic. Maybe even putting component coords & owner to it and > decide about snap outside render — and snap will appear to user next render > phase, delay will be negligible. > > -- > Note that posts from new members are moderated - please be patient with > your first post. > --- > You received this message because you are subscribed to the Google Groups > "ClojureScript" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:;>. > To post to this group, send email to > [email protected]<javascript:;> > . > Visit this group at http://groups.google.com/group/clojurescript. > -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups "ClojureScript" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/clojurescript.
