Ah, yes, I meant shared state. The reason I was saying shared and not app is that app state usually gets "narrowed" the lower in the component tree you get, so when your low down in the tree and then need to access something on a completely different branch, how do you do this without accessing the root app state (which I was storing in :shared so that components can access it without global knowledge)?
But perhaps I'm still thinking about it wrong. Would love to hear your thoughts. On 12 April 2014 14:54, Dmitry Suzdalev <dim...@gmail.com> wrote: > Ok :) If you are talking about :shared state, than it's true, but for the > generic case of the global app state, auto updates are supposed to work > regardless of which part of the state cursor points to AFAIK. > 12 апр. 2014 г. 17:37 пользователь "Daniel Kersten" <dkers...@gmail.com> > написал: > > I think perhaps I was misunderstanding how cursors work. Let me try it >> out and get back to you then :) >> >> >> On 12 April 2014 12:25, Dmitry Suzdalev <dim...@gmail.com> wrote: >> >>> Hi Daniel! >>> >>> Can you clarify this moment a bit for me: >>> >>> On Wednesday, April 9, 2014 2:33:31 PM UTC+4, Daniel Kersten wrote: >>> > I can pass the entire app state to each component (perhaps trough >>> shared state) and use transformation functions (similar to what Sean Grove >>> did in his recent slides) to transform the state into a local view for each >>> component. This means each component gets to select exactly what it needs >>> to access without worrying about what comes before or after it in the >>> hierarchy, but then you lose the benefit of cursors and automatic >>> re-rendering when something changes. >>> >>> Why do you say that in this case "automatic re-rendering when something >>> changes" is being lost? Not clear to me, it seems working ok for some of my >>> components which get passed a 'whole' app state... I'm interested to know >>> if I maybe miss something here :) >>> >>> Dmitry. >>> >>> -- >>> 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 clojurescript+unsubscr...@googlegroups.com. >>> To post to this group, send email to clojurescript@googlegroups.com. >>> 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 clojurescript+unsubscr...@googlegroups.com. >> To post to this group, send email to clojurescript@googlegroups.com. >> 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 clojurescript+unsubscr...@googlegroups.com. > To post to this group, send email to clojurescript@googlegroups.com. > 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 clojurescript+unsubscr...@googlegroups.com. To post to this group, send email to clojurescript@googlegroups.com. Visit this group at http://groups.google.com/group/clojurescript.
