While I think Om's approach to application state management delivers considerable benefit, I think it would be unfortunate if all the labor put into reusable Om components was confined to Om users. With the latest release I've included examples demonstrating how two important things are now possible:
1) Because of the cursor abstraction you can reinterpret the meaning of transact! For example here is an Om component that can be used from a plain React component http://github.com/swannodette/om/blob/master/examples/stateful/src/core.cljs. No Om requestAnimationFrame render loop or batched updates to be found. 2) Because Om components are one step removed from React components, you can back an Om component with an alternate implementation. For example here is an Om component that has been forced to write its local state into the global application state. http://github.com/swannodette/om/blob/master/examples/harmful/src/core.cljs#L158 Together these features offer a better interoperability story for ClojureScript React users as well as powerful debugging facilities when coupled with :instrument. Feedback welcome! http://github.com/swannodette/om David -- 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.
