Exchanger XML Editor: Difference between revisions
(42 intermediate revisions by 4 users not shown) | |||
Line 1: | Line 1: | ||
<!-- <pageby nominor="false" comments="false"/> --> | |||
{{incomplete}} | |||
== Introduction == | == Introduction == | ||
'''Exchanger XML editor''' is an [[XML editor]]. I use it in various course settings where I either teach XML or use XML - [[User:Daniel K. Schneider|Daniel K. Schneider]] | '''Exchanger XML editor''' is an [[XML editor]]. I use it in various course settings where I either teach XML or use XML - [[User:Daniel K. Schneider|Daniel K. Schneider]] 2010 - 2015. As of nov. 2010, the last release was v.3.3.01 (June 2010). It is available through a "Google code" repository: https://code.google.com/archive/p/exchangerxml/downloads. It seems that the company who developed the initial version is inactive and that they made their code open source. This "new" free version includes the XSLT debuger, something that the free V3.2 version did not... | ||
As of | |||
As of July 2015, '''Exchanger XML editor''' is still the '''best free general purpose''' XML code editor. It offers schema support and includes an XSLT debugger and a whole lot of editing tools that we will not describe here. Other free editors may better suit precise purposes such as DocBook editing. | |||
Main Features: | |||
* DTD/Schema aware editing | |||
* Wellformedness checking and validation | |||
* XSLT Support (including a good tracer/debugger) | |||
* DTD/XSD/RNG conversion tools | |||
* Xinclude resolver | |||
* Multi-platfrom (Java-based). | |||
This editor is quite well documented (press the '''Help''' item in the menu bar). Below we just will write down a few essential tricks. | |||
== XML editing == | == XML editing == | ||
To insert an element | === DTD-defined XML === | ||
* | |||
'''Very important''': Exchanger has a little bug that requires you to define a well-formed XML file with a correct header and an inserted root element before you start editing. This is a quite "normal requirement". But, then you must '''close''' this *.xml file and re-open it again in order to make the editor DTD aware. In other words, if you don't create this skeleton, then close and open it again, the editor will not help you with XML editing as described below. | |||
A typical skeleton looks like this, i.e. it would include XML declaration on top, follow by a schema declaration and and inserted root element. | |||
<source lang="xml"> | |||
<?xml version="1.0"?> | |||
<!DOCTYPE recipe SYSTEM "cooking.dtd"> | |||
<recipe> | |||
</recipe> | |||
</source> | |||
Below is a screenshot of the V3.3. editor: | |||
[[image:xml-echanger-editor-v33-essentials.jpg|thumb|800px|none| (To do: annotate this picture ... ]] | |||
To insert an element: | |||
* As in the screen shot above, select the '''Editing helper pane''' to the left by clicking on ('''*>''') . Then (in the editing window) click on the element tag you wish to edit or put your cursor in a location between child element. The helper pane will then display available elements on which you can click to insert. | |||
* Or, in the contents window press press Ctrl-T to insert an element. | * Or, in the contents window press press Ctrl-T to insert an element. | ||
* Or, pressing "<" in the editing window gives more options and you can do it in any place. | * Or, pressing "<" in the editing window gives more options and you can do it in any place. | ||
To insert an attribute | To insert an attribute: | ||
* Click on a tag name of an element. Then click on an attribute on top of the helper pane to the left | |||
* or position the cursor after the element name (but remain within the tag itself). Then press the space bar | |||
The order of elements (works only with DTD's but not with XSD's) is shown in the top pane to the left. You may have to fiddle with options in the ''XML''menu if your XSD Schema is not attached in the right way. | |||
Soft wrapping (important for text-centric XML) | Soft wrapping (important for text-centric XML) | ||
* Menu | * Menu: ''View -> Editor Properties'' Select | ||
=== XSD-defined XML === | |||
Editing a documented based on and XSD follows the same principle as using a DTD, however associating an XSD with a XML file is somewhat more tricky. | |||
== XSLT Transformation == | == XSLT Transformation == | ||
When you develop an XSLT style sheet, it is important to verify that correct HTML (or whatever other kind of output) is being produced. To do so, you can use the built-in XSLT processor that is available through the ''Transform'' menu | When you develop an [[XSLT]] style sheet, it is important to verify that correct HTML (or whatever other kind of output) is being produced. To do so, you can use the built-in XSLT processor that is available through the ''Transform'' menu. | ||
'''Suggested procedure''' | |||
* Open your XML file ('''not''' the xslt file as many beginners do ....) | |||
* Then use menu '''Transform->Execute Advanced XSLT...''' | |||
This procedure allows to use a style-sheet processing declaration of your XML file, e.g. something like this: | |||
<source lang="xml"> | |||
<?xml version="1.0"?> | |||
<!DOCTYPE recipe SYSTEM "cooking.dtd"> | |||
<?xml-stylesheet href="cooking.xsl" type="text/xsl"?> | |||
</source> | |||
For '''output''', either choose ''new document'' or ''file''. Choose file, if you plan to validate the output | For '''output''', either choose ''new document'' or ''file''. Choose file, if you plan to validate the output | ||
In '''addition''' (truly important !), it seems that only the Saxon 2.0 processor is working in the V3.3.1 edition. Therefore you must define the right processor. | In '''addition''' (truly important !), it seems that only the '''Saxon 2.0''' processor is working in the V3.3.1 edition. Therefore you '''must''' define the right processor. You can do this by clicking on the ''Processor'' button as shown in the figure below, but we rather suggest to change the global preferences in Menu ''file->Preferences; XML Tab''. Saxon 2.0 is probably the best XSLT processor anyhow. | ||
[[image:xml-echanger-editor-v33-xslt-execution-settings.jpg|thumb|500px|none|XSLT Processor settings ('''important''')]] | |||
Of course, in other situations you may choose other options, e.g. you don't need to open the files in the editor, they don't even need to be on your computer. | |||
For Mac users: in some cases, even if you opened the right document (xml), the XSLT transformation doesn't work (apparently after an incorrect installation) so try selecting ''Open document'' instead of ''Current document'' in ''Execute Advanced XSLT'' window, and choose the xml file you need to transform. | |||
== XSLT debugging == | == XSLT debugging == | ||
Line 40: | Line 91: | ||
* Menu ''Transform->XSLT Debugger'' | * Menu ''Transform->XSLT Debugger'' | ||
[[image:xml-echanger-editor-v33-xslt-debugger.jpg| | [[image:xml-echanger-editor-v33-xslt-debugger.jpg|thumb|800px|none|Screen shot of the Exchanger XSLT Debugger]] | ||
== Schema development == | |||
The Schema menu allows: | |||
* Validation of DTD, XSD and RNG. It is '''crucial''' to use this feature when you develop a schema. | |||
* Schema conversion from XML, DTD or RNG to XSD | |||
== Installation tips == | == Installation tips == | ||
=== Installation on Ubuntu 10 | === Download === | ||
# Get [http:// | |||
* [http://code.google.com/p/exchangerxml/ Download at Google] (code.google.com). | |||
* Links from the no longer maintained [http://www.exchangerxml.com/ Exchanger XML Editor website] also point to google.com | |||
* Last release: v.3.3.1 (July 2010). Re-tested and installed on Windows 7 64-bit, Windows 8 and Windows 10, Ubuntu 16x and Ubuntu 18x | |||
* '''Overall, still the best free XML editor IMHO''' - [[User:Daniel K. Schneider|Daniel K. Schneider]] September 2010 / Sept. 2018. | |||
=== Installation on Ubuntu 10 LTS to 18 LTS === | |||
Java must be installed. Under Ubuntu 18, openjdk 10 is fine. | |||
# Get the zip file version from [http://code.google.com/p/exchangerxml/ Google] | |||
# Unzip in an install directory, then run it with: | # Unzip in an install directory, then run it with: | ||
java -jar xngr-editor.jar & | java -jar xngr-editor.jar & | ||
You then could write a shell script like this (or better) | |||
#! /bin/bash | #! /bin/bash | ||
cd /usr/local/xngr | cd /usr/local/xngr | ||
java -jar xngr-editor.jar & | java -jar xngr-editor.jar & | ||
=== Installation on Windows === | |||
We have been using this editor under Windows XP, VISTA, Win7, Win8 and Win10 | |||
Make sure that [http://java.com java] is installed. | |||
The installer version worked on most configuration. In case it does not, you could install the "zip" version. I do it anyhow on most of my machines, since I don't like "windows" installation using the registry. | |||
Also, sometimes in the past we had to write a short [[shell script]] to make it work. Contents of file xngr.cmd: | |||
rem Change to the path where you extracted the zip | rem Change to the path where you extracted the zip | ||
cd c:\soft\xngr | cd c:\soft\xngr | ||
start javaw -jar lib\xngr-loader.jar | start javaw -jar lib\xngr-loader.jar | ||
=== Installation on Mac === | |||
Since Apple does everything to inhibit use of open source software, installation can be a nightmare. Try the following (tested in Sept. 2018 again): | |||
* Make sure that [http://java.com java] is installed. | |||
* Create a new directory called xngr-editor (use this name and '''not''' something else, otherwise a path will be broken) | |||
* Copy the zip file into the xngr-editor directory | |||
* Unzip the zip file using the command line, i.e. ''terminal'' (the normal Apple unzipper will not work for whatever reason) | |||
unzip ..... | |||
* Click on the *.jar file pressing down the <code>CTRL</code> key and override the warning you get. | |||
=== Adaptation to high DPI screens === | |||
On windows, one can adapt DPI settings for certain software. | |||
This is '''crucial''' if you do not plan to kill your eyesight. It also works with other programs such as Inkscape. Basically, you just lower the screen resolution for just this application. Windows (after updgrades) will complain about this (do not worry). | |||
* Locate the binary <code>Exchanger XML Editor 3.3.exe</code> (in principle in <code>C:\Program Files (x86)\Exchanger XML Editor 3.3</code>) | |||
* Right-click on <code>Exchanger XML Editor 3.3.exe</code> | |||
* Select the <code>Compatibility</code> tab | |||
* Click <code>Change high DPI settings</code> at the bottom | |||
* Tick <code>high DPI scaling behavior</code> and select System | |||
[[file:xml-exchanger-dpi-settings.png|800px|none|thumb|DPI setttings using Windows properties]] | |||
Note: If the system won't let you: | |||
* Create a shortcut to the desktop, i.e. hold the right mouse button and drag <code>Exchanger XML Editor 3.3.exe</code> | |||
* Right-click on the shortcut -> Properties | |||
== Opinions == | == Opinions == | ||
=== Opinion of [[User:DSchneider|DSchneider]]=== | |||
Editing is fairly ergonomic, DTD-based XML editing support is ok, XSD-based XML editing support could be improved (does not display information about element structure). There are many additional tools (some useless for beginners but of interest to advanced users). '''So this is my best choice for a free structure editor'''. | |||
Only major problem: It does not propose elements in the right order (DTD rules are displayed, but XSD no). This is a problem with almost all editors I have seen. An exception that does this better is Framemaker (an expensive word processor). | Only major problem: It does not propose elements in the right order (DTD rules are displayed, but XSD no). This is a problem with almost all editors I have seen. An exception that does this better is Framemaker (an expensive word processor). | ||
Addition (Feb 2007). I used this editor in a 8 weeks XML beginner's class and indeed it was a good choice. I also liked the XSLT support. There is a validator and editing support for major XSL and XSD elements. Also, I found out that one can format text (Menu Edit->XML->Format). This is crucial when confronted with ugly student productions :). | |||
Xchanger was again updated on June 2010 (version 3.3). It still remains the '''best overal choice for teaching introductory XML''' (DTD,XSLT,XSD etc.). Only caveat: Make sure to change the XSLT processor option to Saxon 2.0 (the others won't work). Also, adapt DPI settings if you got a high resolution (4K) Screen. | |||
As of Sept. 2018, there is still no good free XML editor that provides schema aware editing and XSLT support (i.e. basics for any sort of text-centric XML editing). | |||
- [[User:Daniel K. Schneider|Daniel K. Schneider]] September 2010 / August 2018. | |||
[[Category:XML]] | [[Category:XML]] | ||
[[fr:Exchanger XML Editor]] |
Latest revision as of 16:55, 10 February 2020
Introduction
Exchanger XML editor is an XML editor. I use it in various course settings where I either teach XML or use XML - Daniel K. Schneider 2010 - 2015. As of nov. 2010, the last release was v.3.3.01 (June 2010). It is available through a "Google code" repository: https://code.google.com/archive/p/exchangerxml/downloads. It seems that the company who developed the initial version is inactive and that they made their code open source. This "new" free version includes the XSLT debuger, something that the free V3.2 version did not...
As of July 2015, Exchanger XML editor is still the best free general purpose XML code editor. It offers schema support and includes an XSLT debugger and a whole lot of editing tools that we will not describe here. Other free editors may better suit precise purposes such as DocBook editing.
Main Features:
- DTD/Schema aware editing
- Wellformedness checking and validation
- XSLT Support (including a good tracer/debugger)
- DTD/XSD/RNG conversion tools
- Xinclude resolver
- Multi-platfrom (Java-based).
This editor is quite well documented (press the Help item in the menu bar). Below we just will write down a few essential tricks.
XML editing
DTD-defined XML
Very important: Exchanger has a little bug that requires you to define a well-formed XML file with a correct header and an inserted root element before you start editing. This is a quite "normal requirement". But, then you must close this *.xml file and re-open it again in order to make the editor DTD aware. In other words, if you don't create this skeleton, then close and open it again, the editor will not help you with XML editing as described below.
A typical skeleton looks like this, i.e. it would include XML declaration on top, follow by a schema declaration and and inserted root element.
<?xml version="1.0"?>
<!DOCTYPE recipe SYSTEM "cooking.dtd">
<recipe>
</recipe>
Below is a screenshot of the V3.3. editor:
To insert an element:
- As in the screen shot above, select the Editing helper pane to the left by clicking on (*>) . Then (in the editing window) click on the element tag you wish to edit or put your cursor in a location between child element. The helper pane will then display available elements on which you can click to insert.
- Or, in the contents window press press Ctrl-T to insert an element.
- Or, pressing "<" in the editing window gives more options and you can do it in any place.
To insert an attribute:
- Click on a tag name of an element. Then click on an attribute on top of the helper pane to the left
- or position the cursor after the element name (but remain within the tag itself). Then press the space bar
The order of elements (works only with DTD's but not with XSD's) is shown in the top pane to the left. You may have to fiddle with options in the XMLmenu if your XSD Schema is not attached in the right way.
Soft wrapping (important for text-centric XML)
- Menu: View -> Editor Properties Select
XSD-defined XML
Editing a documented based on and XSD follows the same principle as using a DTD, however associating an XSD with a XML file is somewhat more tricky.
XSLT Transformation
When you develop an XSLT style sheet, it is important to verify that correct HTML (or whatever other kind of output) is being produced. To do so, you can use the built-in XSLT processor that is available through the Transform menu.
Suggested procedure
- Open your XML file (not the xslt file as many beginners do ....)
- Then use menu Transform->Execute Advanced XSLT...
This procedure allows to use a style-sheet processing declaration of your XML file, e.g. something like this:
<?xml version="1.0"?>
<!DOCTYPE recipe SYSTEM "cooking.dtd">
<?xml-stylesheet href="cooking.xsl" type="text/xsl"?>
For output, either choose new document or file. Choose file, if you plan to validate the output
In addition (truly important !), it seems that only the Saxon 2.0 processor is working in the V3.3.1 edition. Therefore you must define the right processor. You can do this by clicking on the Processor button as shown in the figure below, but we rather suggest to change the global preferences in Menu file->Preferences; XML Tab. Saxon 2.0 is probably the best XSLT processor anyhow.
Of course, in other situations you may choose other options, e.g. you don't need to open the files in the editor, they don't even need to be on your computer.
For Mac users: in some cases, even if you opened the right document (xml), the XSLT transformation doesn't work (apparently after an incorrect installation) so try selecting Open document instead of Current document in Execute Advanced XSLT window, and choose the xml file you need to transform.
XSLT debugging
The included XML debugger can be used at two levels
- Beginners just can open it and have a look at the processing traces, i.e. understand what elements are dealt with by which templates and in what order. Also, the result (e.g. HTML) is displayed.
- Advanced users can insert breakpoints (right-click next to a number) and then inspect bindings.
To launch it:
- Menu Transform->XSLT Debugger
Schema development
The Schema menu allows:
- Validation of DTD, XSD and RNG. It is crucial to use this feature when you develop a schema.
- Schema conversion from XML, DTD or RNG to XSD
Installation tips
Download
- Download at Google (code.google.com).
- Links from the no longer maintained Exchanger XML Editor website also point to google.com
- Last release: v.3.3.1 (July 2010). Re-tested and installed on Windows 7 64-bit, Windows 8 and Windows 10, Ubuntu 16x and Ubuntu 18x
- Overall, still the best free XML editor IMHO - Daniel K. Schneider September 2010 / Sept. 2018.
Installation on Ubuntu 10 LTS to 18 LTS
Java must be installed. Under Ubuntu 18, openjdk 10 is fine.
- Get the zip file version from Google
- Unzip in an install directory, then run it with:
java -jar xngr-editor.jar &
You then could write a shell script like this (or better)
#! /bin/bash cd /usr/local/xngr java -jar xngr-editor.jar &
Installation on Windows
We have been using this editor under Windows XP, VISTA, Win7, Win8 and Win10
Make sure that java is installed.
The installer version worked on most configuration. In case it does not, you could install the "zip" version. I do it anyhow on most of my machines, since I don't like "windows" installation using the registry.
Also, sometimes in the past we had to write a short shell script to make it work. Contents of file xngr.cmd:
rem Change to the path where you extracted the zip cd c:\soft\xngr start javaw -jar lib\xngr-loader.jar
Installation on Mac
Since Apple does everything to inhibit use of open source software, installation can be a nightmare. Try the following (tested in Sept. 2018 again):
- Make sure that java is installed.
- Create a new directory called xngr-editor (use this name and not something else, otherwise a path will be broken)
- Copy the zip file into the xngr-editor directory
- Unzip the zip file using the command line, i.e. terminal (the normal Apple unzipper will not work for whatever reason)
unzip .....
- Click on the *.jar file pressing down the
CTRL
key and override the warning you get.
Adaptation to high DPI screens
On windows, one can adapt DPI settings for certain software.
This is crucial if you do not plan to kill your eyesight. It also works with other programs such as Inkscape. Basically, you just lower the screen resolution for just this application. Windows (after updgrades) will complain about this (do not worry).
- Locate the binary
Exchanger XML Editor 3.3.exe
(in principle inC:\Program Files (x86)\Exchanger XML Editor 3.3
) - Right-click on
Exchanger XML Editor 3.3.exe
- Select the
Compatibility
tab - Click
Change high DPI settings
at the bottom - Tick
high DPI scaling behavior
and select System
Note: If the system won't let you:
- Create a shortcut to the desktop, i.e. hold the right mouse button and drag
Exchanger XML Editor 3.3.exe
- Right-click on the shortcut -> Properties
Opinions
Opinion of DSchneider
Editing is fairly ergonomic, DTD-based XML editing support is ok, XSD-based XML editing support could be improved (does not display information about element structure). There are many additional tools (some useless for beginners but of interest to advanced users). So this is my best choice for a free structure editor.
Only major problem: It does not propose elements in the right order (DTD rules are displayed, but XSD no). This is a problem with almost all editors I have seen. An exception that does this better is Framemaker (an expensive word processor).
Addition (Feb 2007). I used this editor in a 8 weeks XML beginner's class and indeed it was a good choice. I also liked the XSLT support. There is a validator and editing support for major XSL and XSD elements. Also, I found out that one can format text (Menu Edit->XML->Format). This is crucial when confronted with ugly student productions :).
Xchanger was again updated on June 2010 (version 3.3). It still remains the best overal choice for teaching introductory XML (DTD,XSLT,XSD etc.). Only caveat: Make sure to change the XSLT processor option to Saxon 2.0 (the others won't work). Also, adapt DPI settings if you got a high resolution (4K) Screen.
As of Sept. 2018, there is still no good free XML editor that provides schema aware editing and XSLT support (i.e. basics for any sort of text-centric XML editing).
- Daniel K. Schneider September 2010 / August 2018.