Thanks Khalid, The way I see it, Om has three concepts regarding state:
1. The global state defined with atom. Named `app-state` 2. The cursor passed to each component with the relevant parts of the global state. Named `app` 3. Local state of each component, initialized in `IInitState` and manipulated with `(set-state! owner korks v)` and `(get-state owner)`. It is a property of the owner object so it is not directly referenced. I agree that `app` is ambiguous for 2 but I wouldn't like to call it `app-state` nor `state` since those could also be confused with 1 and 3. Nothing better than `cursor` or `data` comes to mind. Some other parts of the Documentation (the Example in https://github.com/swannodette/om) use `data` and I think it works even if it is a meaningless term for a fn argument. If you agree and nobody raises objections I'll change `app` to `data`. Sebastian -- 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.
