Fair enough; allow me to add my usecase for your future consideration. My CMS vendor's virtual drive plugin supports automatic checkout/checkin of the xinclude elements. If I encounter an Xinclude, and I select the "Edit Referenced Document" option, the referenced document is automatically checked out for editing and is checked back when the document is closed. Very convenient and it does indeed ease collaborative authoring.
However, some of my docbook documents are extremely long, and authors make heavy use of xref elements. Once we have broken the document into xincludes, it becomes extremely inconvienent to form xrefs between the various xinclude documents. If XMLmind picked up the fact that the document was read/write on the local drive, my users would be able to manually check out the parts of the document that they wanted to work with, and then open the master document and happily xref away. Cheers, Jeff. ? ----- Original Message ---- > From: Hussein Shafie <hussein at xmlmind.com> > To: Jeff Hooker <jeff at itwriting.ca> > Cc: "xmleditor-support at xmlmind.com" <xmleditor-support at xmlmind.com> > Sent: Wednesday, July 29, 2009 1:33:52 AM > Subject: Re: [XXE] Editing Xincludes > > Jeff Hooker wrote: > > > > I could have sworn that in previous versions of XMLmind, if an Xinclude > element was read/write in the file system, then it was integrated into the > containing document and editable there. Am I confusing xincludes with > entities, > or can this still be configured? > > > > This has never been the case, either with XIncludes, conrefs or > references to external entities. > > We are conscious that this feature, in-place editing of included > modules, is convenient to use. However, we have deliberately chosen not > to implement it because we are convinced that our approach eases the > *collaborative* editing of large, modular, documents. > > > > > > > > > > -- > XMLmind XML Editor Support List > xmleditor-support at xmlmind.com > http://www.xmlmind.com/mailman/listinfo/xmleditor-support
