• 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
  • 2014

    15.2
    Version 15.2 - January 22, 2014
    16
    Version 16.0 - May 20, 2014
    16.1
    Version 16.1 - October 7, 2014

What was new in <oXygen/> XML Editor 4

Related Versions: 4.04.14.2

Version: 4.0

April the 30th, 2004

Debugging perspective.

provides a special layout when entering in debugging mode to show the source and the stylesheet documents side by side and to show also the results and special debugging views.

Multiple XSLT engine support for debugging.

Debugging can be done using Saxon 6.5.5 or Xalan 2.5.1 transformation engines

Full control over the debugging process.

All debugger capabilities are provided (step into, step over, step out, run, run to cursor, run to end, pause, stop).

Pause the debugger execution with breakpoints.

Breakpoints can be set on both XML or XSL documents used in the transformation.

Call stack debugger view.

The current stack containing both stylesheet and source nodes can be seen at any time during debugging. The advantage of this approach is that the source scope on which a stylesheet instruction is being executed (the last red colored node on the stack) is easily visible.

Trace history debugger view.

Entering and leaving node events are logged and made available in a view to show the history of the processor execution.

XPath watch debugger view.

XPath expressions are evaluated automatically during debugging. The debugger will update their values dynamically as the processor changes its source context.

Debugger support for imported/included stylesheets and for XML entities.

Once a node from an XML entity or an imported/included stylesheet is processed by the transformation engine, will open that resource in order to highlight the current node location.

Templates debugger view.

The list with all the templates used during the transformation and their corresponding number of calls are presented in the templates view. This allows to spot unused templates and also most frequently used templates as they are ordered based on the hits count.

Variables debugger view.

The debugger lists all variables and parameters visible in the current context together with their scope and actual value.

Dynamic output generation during debugging.

The output is dynamically presented as it is generated by the transformation process.

Multiple debugger output views.

The output can be seen both as text/xml and as rendered XHTML.

DocBook with XInclude support.

A mod file was added in docbook/dtd in the distribution that adds XInclude support to the DocBook DTD. There are also document templates (New from templates action) that allow easy creation of a DocBook document with XInclude support. Also a ready to use sample is provided in the samples/docbook directory giving you a head start when working with DocBook and XInclude.

Increased scenario reuse with editor variables.

The reuse of transformation scenarios increased dramatically by allowing variables in the transformation configuration dialog. It is possible now to configure once a scenario and use it to convert any DocBook document to a PDF file for instance. Another example is if one has an XML file called test.xml and a stylesheet called test.xsl and one wants to get as output test.html, all in the same directory, then one can define generically a transformation scenario using editor variables and specify the XSL (${cfd}/${cfn}.xsl) and the result file (${cfd}/${cfn}.html) and reuse the same scenario also to convert sample.xml using the sample.xsl stylesheet into sample.html.

Transformation scenarios allow multiple stylesheets.

It is possible now to define complex scenarios that involve more than a single stylesheet, thus a single action can execute multiple XSLT transformations and eventually also a FOP transformation.

Support for xml-stylesheet processing instruction.

The transformation scenarios dialog allows to specify to fetch the XSL automatically from the xml-stylesheet processing instruction. If an XML file does not have an associated transformation scenario then a default scenario will be created on the Apply Transformation action configured to use the stylesheet specified by the xml-stylesheet processing instruction.

Full content completion support for the XSLT target schema.

will present the elements defined in a target schema (Options/Preferences/Content Completion/XSL) as possible substitutes for xsl:element. More it will present for these elements the possible attributes and where available also possible attribute values according to the target schema.

Select the XSLT engine to be used for XSLT validation.

It is possible to select the XSLT engine to be used for XSLT validation (Saxon, Xalan or the one plugged in through JAXP). Saxon SA is bundled with <oXygen/> so schema aware XSLT 2.0 is available out of the box.

Improved support for tagging text.

The support for tagging text was improved, the surround in tag action has a keyboard (configurable) shortcut, CTRL+E by default, and offers a combo with the allowed elements where an element will be selected automatically based on the typed prefix. This together with the surround in last tag action (CTRL+/) can be productively used to markup unstructured text.

Improvement of the Relax NG driven content completion.

The content completion driven by a Relax NG schema will offer only the elements that can be children of the current element instead of all schema specified elements. In the future the content completion will present only the elements that keep the document valid in that context - as it does for XML Schemas and DTDs.

Automatically learn document structure.

If a schema or a DTD is not specified for a document, <oXygen/> will automatically learn its structure and use it to drive the content completion.

Control cursor position after inserting elements.

After inserting elements through the content completion the cursor is positioned differently depending whether the inserted element has attributes or not. Sometimes it is useful to have the cursor always between tags regardless the element attributes. This is possible now by enabling the "cursor position between tags" option.

Outliner improvements.

The outliner used to select and expand automatically the node containing the document change. With version 4.0 the user can select from tree synchronization options for the outliner selection: the node at caret position, the node containing the document change or no update. Also on the contextual menu there are available expand and collapse actions.

Smart home behavior.

When Home key is pressed for the first time on a line the cursor moves at the beginning of the text on that line. When Home is pressed again the cursor moves at the beginning of the line, that is position 0. This behavior is repeated at every Home key pressing.

Open resources at cursor (Eclipse only).

Along with open file at cursor it provides a new Open resource at cursor action that looks for fully specified Java classes and open their source files. This is useful for instance when editing/browsing configuration files that contain references to Java classes.

Search/replace in files improvement.

The search/replace dialog has a new filter that allows the action to be performed only on the selected project files.

The Tree Editor can be launched as a separate application.

The Tree Editor can now be launched as a standalone application. It can also be configured to enter in a read only mode if the user wants to use it only for browsing.

Choosing the line separator.

When working across operating systems, sharing for instance a Linux drive to Windows machines and editing the same file from both Windows and Linux it is possible to appear different line separator characters. Now it is possible to ignore the system default line separator and choose from Unix-like (\n) and Windows like (\r\n) line separators in the preferences dialog.

Open in browser option on project files.

To easily view a file in the configured browser a new contextual action, Open in browser, was added in the project view.

Easily associate new file types with editors.

When a file with an unknown extension is being opened, a dialog asking for what editor (XML, XSL, XSD, etc.) should be used appears. Now it is possible to permanently associate the file extension with the selected editor by just selecting the "associate file type with the editor" option in the same dialog.

New plugins

New plugins are available to help text processing: convert text to uppercase, to lowercase, capitalize lines, capitalize the first letter on every selected line, form words to capitalize the first letter of every word and form sentences to capitalize the first letter of the first word in every sentence. All these work on the current editor selection.

Copy location option for project files.

In the Project contextual menu a new action has been added: "Copy location". This allows copying the URL of the selected file into clipboard.

Better presentation for the result messages.

A tool tip has been added to the Results panel showing the whole message content.

More font options.

The font used in editors can be configured to enable text anti aliasing and also to make it bold.

Better support for adding files to project.

Adding directories/files to the current project supports now multiple selection. Also there are two contextual actions on the editor tabs that allow adding the current edited file and all the edited files to the current project.

New Emacs-like shortcuts.

There are some new Emacs key bindings added: cut next word - CTRL(META) + D, cut previous word - CTRL + W (only on Mac), cut to end of line - CTRL + K.

Digest authentication.

The editor can work with files located on HTTP servers that use digest authentication.

Changed content completion internals.

This is an internal change that is not necessary visible at first but it speeds up the editor and also makes it more robust. The content completion will work now even if part of the document before the caret position is not well formed.


Version: 4.1

June the 10th, 2004

XSLT Debugger in the Eclipse IDE.

adds a new perspective the Eclipse IDE providing a special layout that shows the source and the stylesheet documents side by side and also the results and special debugging views: "Context", "Call stack ", "Trace history", "XPath watch", "Templates ", "Variables", etc. All debugger capabilities are provided: step into, step over, step out, run, run to cursor, run to end, pause, stop.

Matching tag highlight and navigation.

When having the cursor inside a tag name both the start-tag and the end-tag are underlined. The user can move the cursor to the matching tag using an action from the contextual menu or a shortcut.

Support file system folders in the project.

The user may create linked folders in the project tree. A linked folder has a correspondent in the file system. When browsing the project tree the user will see the file system folders that exist in that folder. An option for refreshing the content is provided in the contextual menu.

Import remote folders into the project.

The user may choose to import a folder that exists on a WebDAV or FTP server. The project will have a logical structure similar to the content of the remote folder. The files from all the remote sub-folders are added into the correspondent logical folders.

Improved search support.

The find operation wraps when searching in the editor. A new option to search in the project files has been added to the contextual menu of the project tree.

Learn attribute values.

With this option enabled the learn document structure can learn also the values of the attributes and will present them in the content completion popup after a learn structure operation.

Handle BOM on save.

For documents with UTF-8 encoding the user can specify if the Byte Order Mark should be written or not or preserved if a BOM was present when the document was loaded.

Close editor tabs on middle button click.

This is a really handy way of closing the editors.

Improved German translation.

Almost all German messages were changed thanks to Thomas Becker.


Version: 4.2

July the 15th, 2004

Schema Model View.

The Model View provides schema related information for the document elements and attributes. The content model, the element type, the attributes, the attribute type and constraints are presented in a compact manner giving the user an insight in the document schema while editing or browsing the document. XML schema annotations are extracted and presented for both element and attributes thus offering an instant help to the document author.

Content completion shows schema documentation.

The XML Schema documentation is presented by the new content completion support. The content completion offers now additional information for the element and attribute proposals. It will look up the schema annotation and will make the documentation available to the author in a simple and elegant manner.

Annotated XML schemas

To take advantage of the schema documentation support bundles annotated schemas for XSLT stylesheets and XML schemas.

Contrast control

The contrast control options allow to change the transparency levels for markup or text. With a smart popup button located on the toolbar the user can easily change the focus of attention from markup to text and vice versa. The transparent markup option combined with locking the tags can be used for instance for safe and easy text only editing.

User control over the transformation in progress

After starting a transformation a new action becomes enabled allowing the user to stop that transformation. Thus the user is in control and can decide to stop a time consuming transformation at any time.

Improved search support

Support for finding all occurrences in a file was made available via the contextual menu and through a configurable shortcut. If no text is selected then the word at cursor will be automatically detected and searched for.

Breakpoint operations enhancements

Added support to easily add, toggle or remove breakpoints in the Breakpoints Panel.

Allow to define XSLT extensions locations

The XSLT processor's extensions paths can be specified using a system property. Please consult the User Manual for details.

Ready to use JSP 1.2 XML editing support

A new document template was added to allow easy creation of JSP 1.2 documents and the samples have now a JSP entry.


Video Tutorials
Upcoming Events
DITA-OT Day 2014
DITA-OT Day 2014
November 20, 2014
Munich, Germany
" oXygen XML Editor is the premier text editor for XML geeks, and an indispensable tool for O'Reilly's Production group. My team uses oXygen XML Editor for everything from simple XML editing to Schema validation and XSLT transformations. The digital production staff especially loves oXygen's built-in EPUB support, which eliminates a great deal of the grunt work that is usually entailed in editing EPUB files. The more we use oXygen, the more realize what a powerful tool it can be in digital and XML-based workflows."
Adam Witwer
Director of Content and Publishing Operations
O'Reilly Media