On Friday, May 2, 2014 1:46:53 AM UTC-7, Jack Schaedler wrote: > your app-state atom should contain everything that would be saved > into a document if your user did a File->Save in a conventional > desktop application. Given that, it wouldn't seem appropriate to put > things like channels or flags for tracking mouse/hover state and > that sort of thing into the app-state atom.
This makes a lot of sense! > The parent component is then responsible for transacting! on the > app-state - It's acting sort of like a controller for all child > components, waiting for children to send events or requests over the > channels it created in its component local state. Yeah this seems to be the clean way to do it, not only receiving the controller events but making the rendering decision as to what child(ren) to render. > I don't see any benefit to letting another component transact! on > your behalf if you can do it via your own cursor You could theoretically enforce a separation of concerns where only the controller-style components operated on state, and the view-style components only communicated via channels, though in practice so far this separation has appeared to be overkill, as you said. Super helpful, thanks for your thoughts. - Elliot -- 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.
