Man, I must just be failing really hard at describing this. transact! does take a cursor; the issue I'm struggling with is: in the context of an event handler, where does the destined-for-transact cursor come from? You can hard-code a key-sequence in your component definition but that makes your component not really reuseable; you can pass it in to the build call for the component, but often that build call takes place in the definition of another component, so now you've just moved the unreuseability up a layer. Alternately you can mirror the structure of the component hierarchy in your application state, but now you're (at high risk of) complecting state and its representation.
I suspect that I just need to play around more with higher-order components. The fact that Om components are functions makes a lot of things possible. -- 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.
