Andreas Kemkes wrote: > > My thoughts were as following: > receive a callback when insertions and deletions > occur (maybe when the undo/redo list is updated) > wrap the content appropriately (e.g., xhtml:ins and > xhtml:del or use edit attribute ala xhtml2.0) > use the style sheet for the visual feedback > > Are ContextChangeListener, DocumentListener the right > place to start? > > Or maybe Chapter 12 / 3.2.2 Strategy c using the > editing context?
Sorry but I'm not allowed to answer this kind of questions in this mailing list. (That's a good thing! your questions are difficult and I've no clear idea on how to implement what you want. ;-) ) > > Nonetheless, I would like to hear if you know of any > backend tools that would serve such a purpose. Does > DeltaXML at > http://www.deltaxml.com/products/index.html fit your > architectural thinking? No. Our first studies have shown that - the problem of storing efficiently changes made to XML files is very different from - the problem of showing/explaining these changes to the user. (We may be wrong. May be DeltaXML is an incredibly good product.) > Would it be possible and > reasonable to use XMLMind for the presentation of what > the backend produces? No. The successor of XMLmind XML Editor, if it exists one day, will be *vastly* different from current editor. (That's why the project has been postponed for one year or more: we are not sure that people are ready to accept the idea of giving up *files*, at least for certain tasks.) > > What if the XML document type supports it (e.g., > xhtml)? > XHTML ins and del elements are not sufficient to do something serious in terms of redlining. May be they are useful when printing an XHTML page which has been modified? The fact that these elements/attributes are there does not imply that you are forced to use them.
