I've noticed that you did not mention Items View in UI-SPEC and describe it as something orthogonal in freactive readme. Yes, it is really could be implemented independently, and yes, it must be decoupled from core. But it reveals drawback in abstract spec — how in terms of UI-SPEC model list of items should be rendered? Current model only supports full rerender, you need items view hackery to overcome this and apply changes only where data has been changed. But dynamic lists of things is so common case, so spec should contain conceptual key to solve it without additional entities such as items view with its own magic. I'm not sure I have solution right now, but I think it is thing worth to think about.
But, m.b., I am not right, and lists should stay opaque for reactive model. Don't know, let's discuss. -- 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.
