On Thu, Apr 3, 2014 at 10:52 AM, Dave Della Costa <[email protected]>wrote:
> Okay, I think I understand. I guess the key is to properly structure > data and components so that a collection of cursors is always getting > passed into build-all, or a single cursor into build...? I'll examine > where this seems to be a problem for us and see if we can structure our > code to better fit this paradigm. > components do not need to take cursors or collections of cursors. A component needs to take a cursor only if 1) it uses transact! 2) it uses set-state!. > I am curious about the rendering optimizations you're talking about > though--can you going into these any more, and why we would be missing out? > > Thanks for clarifying all of this--this helps tremendously David. > > DD It's not complicated. Because of the global app state we just have more information about what changed and we can more efficiently guide the reconciliation process when React provides the required hooks. David -- 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.
