incubator-wave-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yuri Z <>
Subject Re: editor handling events vs tracking DOM changes
Date Thu, 10 May 2012 20:41:31 GMT
I am not sure, but I think that etherpad approach won't work in Federated

On Thu, May 10, 2012 at 11:21 PM, Dylan Dandelion <
> wrote:

> If I understand correctly, the Wave editor handles user events and
> processes them to generate operations, which are then applied to the
> document result in the visual rendering of the operation.
> This approach is different from Etherpad, which finds DOM nodes that have
> changed at regular intervals, and then generates operations, sanitizes the
> input and redraws the actual DOM.
> What are some of the advantages and disadvantages of the event-driven
> approach versus the diff-ing approach? Why did Wave choose to implement the
> editor using the event-driven approach?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message