Oliver, Have you looked at https://github.com/swannodette/om/wiki/Advanced-Tutorial ?
Geraldo On Friday, December 19, 2014 7:37:28 PM UTC-2, Oliver George wrote: > Hello > > I'm trying to work out a good method for applying business logic to an OM > based UI. In particular, I'd like to avoid embedding business logic in the > render components themselves. > > Things like: > * if this model attribute changes clear these other ones > * reject this new attribute value because it fails some validation test > * when this attribute changes use ajax to fetch some new data > > I think OM still requires a single atom holds all app state even when using > ref-cursors to decouple things better. That means my "models" would all be > in that main atom but parked at different locations within it. > > I wondered if there was a way to hook into transact! such that I could inject > this logic before the update was applied but it's not apparent. > > Seems like something others may have explored. I'd love any thoughts/links. > > cheers, Oliver -- 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.
