While Gal's approach of ditching IB is fine, I still use it, but bind UI components to atoms in ClojureScript. Once that is done, you have a lot of power at your disposal on the ClojureScript side of the JavaScriptCore bridge: With atom watchers you can react to UI state changes, feed them through core.async channels if you'd like to create FRP-like solutions, etc. You can create macros as needed to simplify any complexities that arise with the fact that iOS is on the other side of that bridge. You can nearly have your cake and eat it too :)
-- 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.
