On Sat, Jan 25, 2014 at 12:34 PM, Jonas Enlund <[email protected]>wrote:
> Interesting! I can definitely see how UI components directly manipulating > global state can make reuse difficult. > > I guess this is not really an issue in React as their components have > local state (via getInitialState). It's possible to work with local state > in Reagent as well so reusable components are not completely out of the > picture. > It is an issue if you want modular time management. The undo example for Reagent is not modular. All time management in Om is designed to work across any configuration of components embedded in whatever way you please. > It's great if Om can work with global state without hindering reuse. That > means you can (for example) update :contacts without going via the UI > components at all (perhaps pushed to you from the server). Orthogonal concern and already possible as long as the server has the app state structure, which you must have in the production case anyway when you want to pre-render. David -- 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.
