mmm, yes the component should handle everything itself. I am seeing strange behaviour so I am currently trying to break out a small example, in the hope that either I find the bug, or have a standalone reproducable problem which I can show
On Wednesday, January 28, 2015 at 3:51:21 PM UTC+1, Colin Yates wrote: > I am not sure of the exact interaction between om and react (other than om > implements react's lifecycle for performance enhancements), but two things > occur: > - this sounds like a loaded question - are you seeing some surprising > behaviour? > - "deleted and then reinserted" isn't part of om's lifecycle; there is only > state. How it got to that state isn't interesting. > > AIUI, at runtime, when state changes om will look at each component and check > the (app and local) state used to last render that component. If the state > has changed then the component is "updated", if not it isn't. The "updated" > component is then passed to react to do the actual rendering (of which there > might be none). > > I am beating around the bush of saying, this isn't something I have had to > worry about - is there a specific problem you are seeing? > > On Wednesday, 28 January 2015 11:59:50 UTC, Zubair Quraishi wrote: > > I am building an application in Om and wanted to know what happens to an Om > > component when the global state containing the Om Component's part of the > > UI tree is deleted and then reinserted. Is the Om component garbage > > collected and then recreated automatically, or should the component be > > destroyed and recreated using some commands in Om? -- 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.