New hook: actual text node diff about diffdom

[johanneswilm]

By extension, yes. The exit you get is an object which is labeled according to whether it contains a text node or whatever. You can manipulate that, and then also hook something in on the receiving end to handle it according to your setup.

What is the idea of doing it that way? Is it to save bandwidth by sending less data?

[marcelklehr]

Nope, Concurrent editing with intention preservation.

You want your a to be inserted right after the p, not to set the text content to some 100 chars.
I think working with diffs, this is easier to achieve.

[johanneswilm]

If it's not bandwidth, then do it at the end, not the beginning. You can easily create a diff there by comparing the old and the new text that are both present in the object.That's how we use it. No need to overcomplicate things.

[johanneswilm]

As for what you mention there - that is an entirely different operation (inserting new DOM elements) that has nothing to do with changing text nodes. Have you tried the library out?

[marcelklehr]

Good point, creating a diff on all sites instead of once is a trade off though, imo.

Yea, I have tried the library. Sorry if that came across wrong, I did mean modifying a text node. I'm currently trying to wrap my mind around which operations provide which properties and how they're supposed to work by reverse engineering the diffs and poking around in the code base. Do you have that documented somewhere by any chance?

[johanneswilm]

There is no more documentation then the code itself which is quite readable. I don't think creating the diff in several places is a significant tradeoff if this is about collaborative editing.But you can of course filter the output, and just take the diff of modified text nodes and change do the calculation already on th sending end and then also override the receiving end.

[marcelklehr]

Thanks for your help.