Hi Johan,
Just one small remark:
Unfortunately the recenet addition of master file in Oxygen (which I thought
would handle this)
does not seem to work this way for plain XML files (at least I didn't get it to
work). It works fine for XSLT stylesheets though.
You are right, we will try to make this new master files support also
work for XML-type files.
Regards,
Radu
Radu Coravu
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com
On 8/13/2012 8:42 PM, Johan Persson wrote:
Kind of.
If you like me use a master file with XInclude:s it takes a "trick" to
get Oxygens to resolve all references and then it works
really well. This "trick" has been available for quite some
time/versions - but it is not obvious.
You have to add all includes as files in the validation schema. Then
assign the validation schema to all included modules.
Having done that it will be possible to handle XML includes as expected,
all ref:s in all moduels can be
resolved by auto-completion. Unfortunately the recenet addition
of master file in Oxygen (which I thought would handle this)
does not seem to work this way for plain XML files (at least I didn't
get it to work). It works fine for XSLT stylesheets though.
In regards to the comments about price for Oxygen I would say that it is
very reasonable priced given
its capabilities and the speed up it will make in the writing of XML
(and XSLT stylesheets). It would be very easy to motivate
its cost in a business setting. Of course, for a hobbyist it would be
harder but I believe Oxygen also has a very cheap
"hobbyist not-for-profit" license that is less than US $100
Just my 2c
/J
On 2012-08-13 19:11, Warren Young wrote:
On 8/12/2012 4:41 PM, Richard Hamilton wrote:
There are a bunch of very good visual editors out there that will
handle DocBook. The one I know best is Oxygen
(http://www.oxygenxml.com/), which works very well with DocBook.
The last time I tried opening one of my DocBook manuals with it (version
9, maybe?) it didn't handle XML Includes gracefully.
I like to have a top-level document that simply includes all the chapter
files, which lets me edit the chapters individually. This keeps file
sizes reasonable and (much more important) localizes VCS comments to the
relevant section of the document.
As I recall, oXygen sort of kind of attempted to open the top-level
document, but didn't give me the seamless WYSIWYG view I expected: an
editable version of the final PDF output. If instead I opened an
individual chapter file, it got confused by the cross-references, since
it didn't understand that it was looking at a tree in a forest.
Have they fixed this limitation, or does it still push you toward
putting the entire document in a single file?
---------------------------------------------------------------------
To unsubscribe, e-mail:[email protected]
<mailto:[email protected]>
For additional commands, e-mail:[email protected]
<mailto:[email protected]>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
