Hello, I want to build a single page app with Om that has several screens and routing with Secretary. Each screen can have a bunch of components - some tables, forms, charts, whatever.
For a concrete but simplistic example, let's say I have 2 screens each with 2 components. My "master template" looks like: <html> <body> <div id="nav">Whatever</div> <div id="content"></div> </body> </html> Pages look like: <div id="page_1"> <div id="component_1_1"></div> <div id="component_1_2"></div> </div> <div id="page_2"> <div id="component_2_1"></div> <div id="component_2_2"></div> </div> So, what do you think is the best approach to implement it with Om? Should I put *all* of my application state into one gigantic atom and have one gigantic component tree bound to #content, with conditional rendering based on navigation state and everything else? That feels complicated. Is there any way to unbind components and create hierarchies? I feel a bit lost in the woods, would appreciate some advice! -- Konrad Garus -- 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.
