2002
1
Version 1.0 - April the 15th, 2002
Version 1.1 - May the 15th, 2002
Version 1.1.5 - May the 20th, 2002
Version 1.1.6 - May the 24th, 2002
Version 1.1.7 - May the 27th, 2002
Version 1.1.8 - June the 5th, 2002
Version 1.1.9 - June the 15th, 2002
Version 1.2 - June the 27th, 2002
Version 1.2.1 - September the 27th, 2002
Version 1.2.2 - October the 22nd, 2002
Version 1.2.3 - November the 27th, 2002
Version 1.2.4 - December the 17th, 2002
2003
2
Version 2.0 - April the 2nd, 2003
Version 2.0.1 - May the 15th, 2003
Version 2.0.2 - June the 9th, 2003
Version 2.0.3 - August the 14th, 2003
Version 2.0.4 - September the 19th, 2003
2004
3
Version 3.0 - January the 14th, 2004
Version 3.1 - February the 6th, 2004
4
Version 4.0 - April the 30th, 2004
Version 4.1 - June the 10th, 2004
Version 4.2 - July the 15th, 2004
5
Version 5.0 - October the 15th, 2004
Version 5.1 - January the 18th, 2005
2005
6
Version 6.0 - May the 22nd, 2005
Version 6.1 - July the 19th, 2005
Version 6.2 - September the 19th, 2005
2006
7
Version 7.0 - January the 13th, 2006
Version 7.1 - March the 2nd, 2006
Version 7.2 - June the 6th, 2006
8
Version 8.0 - November 20th, 2006
Version 8.1 - January 25th, 2007
Version 8.2 - May 7th, 2007
2007
9
Version 9.0 - November 2nd, 2007
Version 9.1 - December 18, 2007
Version 9.2 - May 9, 2008
Version 9.3 - July 2, 2008
2008
10
Version 10.0 - October 23, 2008
2009
11
Version 11.0 - October 9, 2009
11.1
Version 11.1 - December 17, 2009
2010
11.2
Version 11.2 - March 16, 2010
12
Version 12.0 - September 14, 2010
2011
12.1
Version 12.1 - January 12, 2011
12.2
Version 12.2 - May 19, 2011
13
Version 13.0 - August 29th, 2011
13.1
Version 13.1 - October 26th, 2011
2012
13.2
Version 13.2 - January 12th, 2012
14
Version 14.0 - June 27, 2012
14.1
Version 14.1 - October 19, 2012
2013
14.2
Version 14.2 - February 13, 2013
15
Version 15.0 - June 7, 2013
15.1
Version 15.1 - October 7, 2013
What was new in <oXygen/> XML Editor 8.2
May 7th, 2007
There are changes in:
Native XML Database support
XQuery Debugger Support
<oXygen/> XML Editor brought the first XQuery debugger against a
native XML database allowing users of the MarkLogic 3.2 (or higher) database to
debug their XQuery code based on the new MarkLogic Server 3.2 (or higher) XQuery
debugging API.
Support for the Native XML Storage for Oracle
In addition to organizing the XML data in tables, Oracle offers a
logical grouping of the XML resources in collections. You can open and edit
documents using the database explorer available in the database perspective. The
resources subtree is found under the node "XML Repository".
Limit the Number of Nodes Displayed in a Very Large Container
An Oracle XML container or a Tamino one can have millions of resources.
In order to improve the performance of browsing a container the maximum number of
nodes displayed in such a container in the Database Explorer view is limited to a
configurable value. The nodes set can be browsed with Up and Down buttons.
Type Selection for the Containers on Berkeley DB
You can choose the type of the containers you want to create from the
database browser. There are supported both the "Wholedoc" type containers and the
"Node" type containers.
Delete XML instances from a Tamino doctype
The XML instances stored in a Tamino doctype can be
deleted.
Support for the Tamino System Collection
Tamino system collections can be browsed using the database
explorer.
Filter XML instances of a Tamino doctype
An XQuery predicate can be set as filter for the XML instances of a
Tamino doctype presented in Database Explorer view.
Support for output parameters in stored procedures
Now output parameters are supported for stored procedures executed on a
database of type IBM DB2, SQL Server, Oracle, MySQL.
ISO Schematron support
Editing ISO Schematron Schemas [read more...]
<oXygen/> has a Schematron editor that detects automatically from the namespace
that the edited Schematron schema is ISO Schematron. It offers content completion
with documentation for the ISO Schematron elements, attributes and values and also
features continuous validation.
Validation
Validation Scenarios [read more...]
Validation scenarios are a very powerful feature and they solve
a number of important issues when working with XML and XML related technologies. They
allow working with modules and performing multiple validations in one action.
By default the validation of a document is done by using a
processor (XML parser, XSLT transformer, XQuery engine, etc.) to analyze the current
file. The validation scenario allows to specify a set of files to validate and for
each file what processor to use and whether or not to perform continuous validation.
Thus if you work on a module you can set the validation on the master file, the file
that refers that module. Also you can perform multiple validations with different
processors or on different files.
Editor Improvements
Large File Viewer [read more...]
Very large files (larger than a Gigabyte) that
cannot be opened in the editor panel can be viewed in the Large File Viewer without
loading the file in the memory. The Viewer is available from the Tools
menu.
Multi-line Find/Replace [read more...]
The Find/Replace is enhanced with multi-line capabilities.
Both the find and the replace expressions can cover multiple lines of the document.
This together with the regular expressions and XPath filtering support allow powerful
changes to be applied on the document content.
The Attribute Displayed in the Outline View Is Configurable
The Outline view presents a tree structure of the document updated in
real time as you edit your file. It presents also some information from the
attributes or from the text content for each element. Now <oXygen/> has a
priority list with attribute names and uses that to determine what attribute to
present instead of presenting the first attribute. This allows a better insight of
the document structure from the Outliner as you can easily see the relevant
information.
Shows the XPath of the current element
The XPath panel and the XPath Builder View can show the XPath that
matches the element at the current caret position. The expression is updated as
you move the caret through the document. For instance if you are inside a title
inside a section inside article you will see "article/section/title" and executing
that will show in the XPath results panel all the first level sections titles from
your article. The XPath expression is useful also to give you a quick hint of your
position in the document.
Option to Open the XML Files Directly into the Grid Editing Mode
You can specify the default opening mode for the XML files: text or
grid. Thus if you are mainly working with data files that are better suited for a
table layout you can open them directly in the grid editing mode.
Improvements for the WSDL SOAP Analyser
The analyser dialog is docked in the editor user
interface. You can move it wherever you consider to be handier. The requests are
associated with the port numbers, so if you change the port, the request for that port
is set into the analyser. Both the request and the response can be pretty-printed
using an action from the contextual menu.
Access Resources on FTP / SFTP / WebDAV Servers from the Eclipse
Plugin
The Eclipse plugin distribution of <oXygen/> is also able to browse
FTP / SFTP / WebDAV servers and open and save files on such servers.
Support for OASIS XML Catalogs version 1.1
The latest version of the OASIS XML Catalogs specification is
supported. Catalog elements like systemIdSuffix and uriSuffix are recognized in
XML catalog files. This makes possible the resolution of relative
locations.
Option for browsing application bundles as directories on Mac OS X
The option allows browsing application bundles as directories on Mac OS
X.
Pretty-Print
Pretty-Print JavaScript Files
The format and indent action can now be applied on JavaScript files.
There are a couple of options to control the formatting like the preserving or
striping of empty lines and the position for the start curly brace.
Pretty-print for HTML documents handles scripts and styles [read more...]
Usually an HTML document contains scripting and style
information. The format and indent operation that applies to HTML text content is not
suitable for formatting scripts and CSS styles. Therefore <oXygen/> detects these
sections and automatically pretty-prints the embedded JavaScript and CSS sections
using the JavaScript and CSS formatting options.
Component Updates
Updated Saxon 8 to version 8.9.0.3
The Saxon 8 XSLT and XQuery processor was updated to the latest
version: 8.9.0.3. Both Saxon 8 Basic and Schema Aware versions are supported,
including XSLT 2.0 and XQuery debugging and profiling and also schema validation
(for the Schema Aware version you need a separate license from
Saxonica).
Updated the Apache FOP transformer to version 0.93
The XSL-FO transformer from Apache was updated to the latest version:
0.93. Note for the TEI users: Because the TEI FO stylesheets are
not compatible with the latest FOP, it is recommended to download and configure
the FOP version 0.20.5 as an external FO processor and then change the
transformation scenarios to use it.
Updated the DocBook XML schemas to version 5.0CR3
The DocBook XML schemas were updated to the latest version:
5.0CR3.
Updated the DocBook XSL stylesheets to version 1.71.1
The DocBook XSL stylesheets were updated to the latest version:
1.71.1.
Updated the Apache XML Security library to version 1.4.0
The XML Security library from Apache was updated to the latest version:
1.4.0.
Updated the SVNKit library to version 1.1.2
The SVNKit library used in the SVN Client was updated to the latest
version: 1.1.2.
Starting from $488
