Hi Nelson, Is the goal to have the actual data model be XHTML using wave's XML OT, or do you just want raw text?
The reason wave's data model is so dissimilar to HTML is because it's not easy to get good collaborative behavior with OT on HTML. For example, splitting a paragraph would involve deleting and re-inserting a lot of content, which would play really badly with someone else concurrently editing. (We actually used to have a "split" operation that handled this, but it was more trouble than it was worth, and resulted in a lot of nasty complexity) Dan Στις 28 Φεβρουαρίου 2011 4:06 μ.μ., ο χρήστης Nelson Silva < [email protected]> έγραψε: > Hi all, > > I'd like to know what is the best approach to create an editor to > manipulate a pure HTML DOM element. > > If I wanted to be able to support collaborative edition of pure HTML how > should I approach it? > > I could use an HTML doodad but I'd have to add support for the full HTML > schema and would have a one to one mapping between my document model and the > view... > > The idea is to use Wave and OT but not the client interface to create a > collaborative HTML editor. Should I just skip gadgets and doodads and create > a simple editor or would it be best to use doodas even with a direct mapping > between the document and the view ? > > Thanks >
