You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think copy-on-write CRDT approach not only has promising performance improvements, but also might offer some good solution for Rich Text modeling due to introduced split operation. I imagine text blocks could be extended with additional metadata where formatting information could be stored and with that it would be possible to represent Rich Text without resorting to marker tokens as described in #193
The text was updated successfully, but these errors were encountered:
The Automerge 1.x binary encoding format (#253) compresses sequential insertions in a way that has much the same effect as RGASplit, while keeping the CRDT logic simpler. Also, for formatting metadata we now have cursors (#313). I think that addresses everything in this issue, so I'm going to close it.
This is related to #193, where I encounter a need for splitting text segments without making delete, insert route. As I was trying to find a solution I came across to RGASplit paper that happens to be foundation for xi editor, atom's collaborative editing feature and their next generation code editor.
I think copy-on-write CRDT approach not only has promising performance improvements, but also might offer some good solution for Rich Text modeling due to introduced split operation. I imagine text blocks could be extended with additional metadata where formatting information could be stored and with that it would be possible to represent Rich Text without resorting to marker tokens as described in #193
The text was updated successfully, but these errors were encountered: