On 6 March 2015 at 09:13, Colin Yates <colin.ya...@gmail.com> wrote: > I know this is a different direction than a lot of people but I store > everything in the app-state and so far it has worked well. There are a > hundred reasons why this (storing everything in app-state) is a > terrible idea, but I haven't run into any of them. >
I was considering that. It seems wrong, but I hadn't been able to think of any specific problems that would come of it. > If you did want to store component-local state then channels or a > simple cb would suffice. I would go with a callback in this case as it > seems to be a pure implementation detail of the 'layout' component. If > the children of the layout are external to the layout (i.e. the layout > component is a generic reusable thing) then can you now simply put the > logic in the IDidMount of the container and then query the dom itself > for all children of that container? > Oh, now that's an interesting idea. I was trying to do everything through components in a very declarative way, but perhaps this is a case where it would be useful to reach into the DOM instead, and manually rearrange the positions after a IDidMount or IDidUpdate event. - James -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
