While this can be very convenient, such real-time (or synchronous) collaboration is not always what users want. In a real-time collaborative editor such as Google Docs, every keystroke typed into a document is immediately visible to the other collaborators. We then explain how Peritext handles these issues, and demonstrate our prototype implementation of the algorithm. We provide a detailed analysis of various edge cases that need to be handled in collaborative rich-text editors, and explain why existing algorithms for plain text collaboration are not able to handle them correctly. Once the versions are merged, the algorithm guarantees that all users converge towards the same merged result. In this article we present Peritext, an algorithm for rich-text collaboration that provides greater flexibility: it allows users to edit independent copies of a document, and it provides a mechanism for automatically merging those versions back together in a way that preserves the users’ intent as much as possible. The algorithms underpinning services like Google Docs are not designed to support this use case. However, sometimes people prefer a more asynchronous collaboration style, where they can work on a private copy of a document for a while and share their updates later.
Peritext: A CRDT for Rich-Text Collaboration Peritext A CRDT for Rich-Text CollaborationĬollaborative editors like Google Docs allow people to work on a rich-text document in real-time, which is convenient when users want to immediately see each others’ changes.
0 kommentar(er)
