On 13 jan 2014, at 19:44, David Nolen <[email protected]> wrote: > Aah, I see. That is a very good question: most of the time you shouldn't see > any inconsistent output, since React normally batches updates – but only in > React's own event handlers. There are ways around that, but none of them are > very attractive... > > FWIW, this is something I wanted to solve in Om. Application state updates > are *always* batched, rendering always occurs on requestAnimationFrame (where > available), and there's some basic enforcement logic around trying to update > the app state from event handlers to work around inconsistency.
Yes, it is a tradeoff (as everything in life, it seems). Batching-by-delaying would be doable in Cloact as well I think - but then you can get into all kinds of trouble e.g if you need to do something with the DOM, since it will be out of sync with your data. Still thinking about that one, though. /dan -- 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.
