Thanks for the responses, sounds really cool. It can satisfy 1 and 2 if the user can control the cursor generated by > `om.core/get-shared`. This is part of the design. >
Can you outline how this will work a little bit? If you're still figuring this out, then no worries - I won't ask you to explain a work in progress (unless you want feedback), but otherwise I'd be interested in hearing what you are planning here. Om needs to work without needing users to think very much about > transformation or paths. This is not something people need to consider in > traditional UI approaches and I'd be disappointed to force this kind of > incidental complexity on Om users. > Ok, yeah, I completely agree that eliminating the need for users to think about these is the way to go. I guess the idea of using transformations is that it abstracts the data that components need/receive from where that data comes from, but at the cost of complexity. Definitely better to avoid that if there are other ways to get the same (or similar) benefits. -- 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.
