On Wed, Jan 22, 2014 at 1:42 PM, David Nolen <[email protected]> wrote: > om.core/get-shared leaves the door open for components requesting some > global service without resorting to cljs.core/exists?.
Not clear to me what that means. Is there more to it than "get-shared is for things that don't change, :opts is for things that can change?" > Not true. React has exactly the same problem. There's no public way to get > at component state deep in the render tree. Fair enough. I'm still in the "local state is poison" camp though. Hard to get at, and against the grain of the value that Om provides. Being able to hold the complete state in your hand, rather than scattered across implementation details, is awesome. > application state and component local state are very different with respect > to consistency. I think I recall seeing a discussion about this, could you provide a pointer or re-summarize? The way I think about it is, look at atoms, refs and agents. Yes they are all a bit different, yet somehow it still feels like the same API. Similar deal with channels that having different buffers. > It should not be co-located if it is not something you intend to snapshot. This is an interesting point. How useful are snapshots if you don't capture local state? I would expect that undo would bring back exactly back to the state I had before. > a) application state > b) component local state > c) side information I agree there are about 3 kinds of data The most interesting question to me is, how should b) be conceptualized. > I do think that that being to able force a child component to write it's > state into a) instead of b) is an interesting direction to pursue and > perhaps can shed some light on how a) and b) can conceptually unified. I totally agree. Seems join would be useful here. -- 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.
