On Tue, Jan 17, 2012 at 10:08 PM, kovas boguta <kovas.bog...@gmail.com>wrote:
> Pretty basic question here. > > Suppose I want to have 2 copies of the form in the same application. > > How will the event handlers know which form the events are coming > from, and which form needs to be modified in response to those events? > > More generally, what if I have N copies of some widget that all have > the same structure, but different instance data. For example, a list > of tweets, where each tweet has "favorite" button. > > My current impression is that I'd have to architect the event routing > myself, making sure some distinguishing ID is carried around > throughout. > > Is this accurate? > > What is the recommended way to handle this situation? > > Thanks, > Kovas I think it's an open question on how to best solve this problem. There have been many, many approaches to binding the UI to the data layer. ClojureScript One's dispatch approach is very interesting, but it might need something like efficient predicate dispatch to scale. It's worth looking at complex binding solutions like Cocoa Bindings and simple binding UI / data binding projects like Backbone.js or Ember.js to see how much progress there is to be made in this space. If people have other suggestion of things to look at, speak up. David -- 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
