Irakli Gozalishvili

> Definitely worth considering how moving text will work too. You mean cut & paste ?

Side remark: this echos quite a bit constraints I had in https://github.com/gozala/dominion where node moves were preferred over remove / insert. I end up wish something like register where I...

I was hoping to get a basic demo working of what I was trying to build before sharing, but I'm also happy to do it much sooner as potentially it...

> Regarding cursor positions, the safest would be to use the internal element ID to refer to a position within the text, since it remains stable, even as people insert...

> My intention was that Automerge.Text should be usable for this purpose. That is, I want Automerge.Text to be able to contain marker objects as well as characters from the...

> Maybe I am overlooking something, but "If a document is just a flat sequence, hitting enter in the middle of a paragraph just means inserting a '\n' element into...

I've published my current draft of the discussed `RichText` exploration here https://github.com/Gozala/conspire/ At the moment I'm using array / list instead of `Text` because of the issues discussed in #194,...

> Here’s one way to do a link > > ```js > before link { link: { to: "https://github.com", target: "_blank", etc } }link here{ link: "end" } after link...

> My new design theory is that we should keep an ordered array of formatting spans. Each span will refer to a start and end character and will be applied...

@pvh I think primary problem with just computed formatting dictionaries (in front position only & no span length) is that could lead to multiple such dictionaries in the same position...