|Subject||:||XMLmind XML editor|
|Date||:||25 Feb, 2007 on 09:06|
|Sometime ago while reading my regular Linux Magazine online (< http://www.linux-mag.com/id/2887/ >), I became aware of an XML editor and wondered if it could be used under OS/2. Below is the result of my inquiry.
There are two versions of this Java XML editor: Standard and Professional.
The Standard Edition is free to download but some (professional use) functionaliy is crippled on purpose by the vendor.
Notwithstanding, from my perspective, even if crippled the Standard Edition offers more functionality than other equivalent XML editor offerings out there. And yes it works with Golden Code Development (GCD) native Java OS/2 implementation.
I have been testing the XML editor since the previous version, i.e., 3.5.1 ...er, well, I also was concurrently downloading Solaris with Sun Microsystems Download Manager.
Notwithstanding, for the current and more relevant version where I am faced with the need for SVG plugin to display an image, I need the Apache Batik image toolkit.
Subsequently, the plugin is automatically installed as can be seen with the progress bar dialog.
After I restart XMLmind XML editor for the plugin install to take effect, I can see the SVG graphic, finally --but I need another plugin-- the Jimi image toolkit.
Hence I proceed to install it; from the "Options" menu, I select "Install Add-ons" and scroll down to the appropriate plugin.
As before, I need to reboot so that the new plugin for TIFF and BMP images take effect. Upon restarting the XML editor I reopen the previous page to verify that the plugin was successful.
This is an example of the power of the free standard editor. Of course, if you requre more professional features, you may want to buy the Pro edition.
XMLmind XML editor homepage: < http://www.xmlmind.com/xmleditor/ >
XMLmind XML Standard vs. Professional differences: < http://www.xmlmind.com/xmleditor/proedition.html >
XMLmind XML free Standard editor download site: < http://www.xmlmind.com/xmleditor/download.shtml >
As of February 19, 2007, XMLmind editor is at version 3.5.2 and it can be downloaded in a non-WinXX specific zipped file: xxe-std-3_5_2.zip
The unzipped file will create a directory appropriately labeled xxe-std-3_5_2 in your current directory; consequently to avoid complexity be sure to unzip the file at the root of a drive with sufficient space. In my examples I used J: drive; please make appropriate modifications for your particular case.
Assuming your current drive is J: then, after unzipping the file into it, one changes directory to J:\xxe-std-3_5_2 and observes the directory structure. For an user the important directory is the bin directory since the executables are there.
Notwithstanding, those files in the bin directory are for Unix/Linux and WinXX --no OS/2 *.cmd script executables. Consequently, the first thing an OS/2er does is move the WinXX specific files out of the bin directory; those *.bat and *.exe are not compatible with OS/2.
This snapshot shows the WinXXspecific files that we move elsewhere; their names are as follows:
The next step is to replace those files with modified fies of the same name but with a .cmd file extension (we do not modify nor need xxe.jstart). If you know Rexx, you may come up with a more elegant solution than my hacked ones listed online below:
Please note that the default arguments that I set were five(5). If you need more simply add: %6 %7 %8 %9 etc..
I have uploaded a zipped flle XXE-STD-3_5_2-OS2.zip containing the OS/2 *.cmd files listed above that you can download. From your xxe-std-3_5_2 directory you can extract the file referenced above; those files will extract into your bin directory ( J:\xxe-std-3_5_2\bin in my example )
Please read the disclosure notice that I include by opening each unzipped files with a text editor.
In each file that extracted into your bin directory please change the drive letter to your appropriate drive where you extracted your XMLmind XML editor. As an example, if your XML editor is on drive C:, edit each line of your files in your bin directory that end in *.cmd; change the line that reads:
Additionally do not forget to modify your home variable to your specific existing directory but only if you do not have already an environment variable pointing to an OS/2 directory as your home.
If in doubt about the existence and validity of your HOME environment variable, open an OS/2 windowed session and at the command prompt, type:
the output should print a directory drive and path. Now, to check for the validity of that directory drive and path, type:
...and unless the output is something like:
SYS0002: The system cannot find the file specified.
then your HOME environment variable exists and points to a valid location.
Consequently only if you do not have already a home environment variable, the home directory in each of the *.cmd files must be activated by changing the line that reads:
REM SET HOME=F:\emx\usr
SET HOME=X:\<your existing home directory>
where naturally, you replace X: by your existing Drive: home directory that you want to use and also replace what is beteween the angled symbols (those inclusive) with a valid directory --this is important as all the configuration information for your XMLmind XML editor will be saved there.
After you save those changes, you can start your XML editor a couple of ways. It is assumed that your Java 1.4 and above is in your OS/2 PATH environment variable.
It is assumed that you current directory is xxe-std-3_5_2 in your appropriate drive. Hence, from there type:
and your XMLmind XML editor will open ready for you to open a file.
You may instead want to add the PATH to your XML edtor executables in the bin directory. Or you may opt to decide to do it dynamically for the current OS/2 windowed session as follows:
At your OS/2 window prompt type:
provided, of course, that you replace X in the line above to the Drive letter where you installed your XMLmind XML editor. Then, from anywhere you happen to be in your dierctory structure, simply type:
and your XML editor will start up. You can provide an xml file as an argument, obviously, by typing:
xxe.cmd <your XML file>
Note: I do not have any CLASSPATH environment variable set in my CONFIG.SYS --as recommende in my GCD native java OS/2 implementation instructions.