2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
Continuous Validation [read more...]
Oxygen can be configured to continuously report validation errors in an edited document as you modify it. By selecting the Enable automatic validation option, validation errors will automatically be displayed as you type, after a configurable delay.
Error Markers and Overview Ruler [read more...]
The location of errors, including those that are generated by continuous validation, are marked in-place with an underline. The error locations are also marked in red on the right side of the editing view, in an overview ruler that allows you to quickly navigate between the errors.
Support for Caching When Validating Against Schemas
Multiple External Validation Engines [read more...]
Oxygen has built-in support for various external validation engines, including Xerces, LIBXML, XSV, Saxon SA, MSXML4.0, MSXML .NET and SQC.
Ignore the DTD for Validation if Other Schema is Specified
External Validation Against DTDs
Associate DTDs for Validation Using the External Schema Association Rules
Support for CSS Validation [read more...]
Various CSS profiles are supported (CSS2, CSS3, etc.), as well as various media types (for instance, 'Braille' or 'screen'). You can also choose the verbosity level of the validation warnings.
The validation results are descriptive and in accordance with the W3C specifications. Along with the automatic validation feature, spotting and fixing errors in the Oxygen CSS editor is a simple task.
XPath-Aware Content Completion Assistant
Editing XPath expressions for the "match", "select", or "test" attributes is not always straight forward. Oxygen XSLT Editor makes this task easier by showing the proposed list of XPath functions in the Content Completion Assistant, all documented with sections from the W3C specifications.
If you have configured a scenario for the edited stylesheet, then the proposal list contains also the names of the elements from the input document that are currently accepted in the XPath expression.
Support for XPath Default Namespace
XPath Execution in the Context of the Current Element [read more...]
The XPath expressions are evaluated from the context of the current element, thus relative expressions can be evaluated in various contexts.
XSLT Input Document View
This view displays the tree structure of the XML document set as input for the current stylesheet in the associated transformation scenario.
You can create templates or other XSLT snippets by dragging the nodes from the tree into the stylesheet. The generated XPath expressions are context aware.
Search XSLT References
This search is performed for any XSLT component that has references (variables, functions, named templates, attribute sets, etc.) The search scope can be the current file, the project, or all the imported/included files starting from the current file or from a specified file.
Search XSLT Declarations
This search is performed for any XSLT component that has declarations (variables, functions, named templates, attribute sets, etc.) The search scope can be the current file, the project, all the imported/included files starting from the current file or from a specified file.
Search XSLT Occurrences
This provides a quick retrieval of all the declarations and references of a component in the current file.
Rename XSLT Occurrences
This allows renaming XSLT components such as variables, templates, functions, etc. The user is fully in control of the changes as the modified files are presented in a Diff view that allows inspecting all the changes that will be done before actually performing them. The scope can be the current file, the project, all the imported/included files starting from the current file or from a specified file.
Create XSLT Stylesheet from Selection
The selection is placed in a new stylesheet that is then included in the current stylesheet.
Create XSLT Template from Selection
The selection is placed in a named template and is replaced with a call-template instruction. The variables and parameters used inside the selection will be passed as template parameters.
Apply the Transformation Scenarios for Multiple Files in One Action
Apply a Specified Transformation Scenario on a Set of Files
Allow Configuring the XSLT Transformer Options Through Preferences
Support the System.Xml 2.0 Transformer
Support for the Latest Version of Saxon 8
XQuery Debugging Perspective [read more...] Save time when developing complicated XQuery expressions by using the Oxygen XQuery debugger. Oxygen can debug and profile expressions run over MarkLogic or Berkeley XML databases, or using the Saxon EE processors. |
XQuery Profiler [read more...]
You can profile your XQuery queries to identify the performance issues by using two comprehensive data views of the activated templates: an Invocation Tree view and a Hotspots view. The profiling information can be saved to XML or HTML formats.
Profiling is available only for the Saxon XQuery processor that is bundled with Oxygen.
Schema Components View
Support for Showing Recent Content Items [read more...]
The proposals that have previously been used are promoted at the top of the content completion list, thus allowing for efficient re-use. For example, when editing an XSLT stylesheet, you use a small fraction from the entire set of XSLT and HTML elements. By sorting the recently used proposals to appear at the top of the list, it makes it easier to find them the next time you want to use them.
Handling of Namespace Prefixes
Present #ID URI Fragments for anyURI Attribute Values
Look for Type Annotations if the Elements or Attributes Don't Have Annotations
The Content Completion Assistant Displays Element Values When Using a Relax NG Schema
Support for Presenting the xsi:nil Attribute for Nillable Elements
Improved CSS Content Completion Assistance [read more...]
The Content Completion Assistant provides property values associated with the property name. All the property names are annotated with descriptions from the CSS specification.
Dockable Editors [read more...]
Not only can the views be moved around the interface but the editors can also be arranged inside the overall editing area.
Additionally, each editor can be split horizontally or vertically. Splitting an editor allows you to easily copy or move text and markup between two sections of the same document.
Split Editor in Two
The Find Dialog Box is not Modal
Configurable GUI Fonts
All the Result Views Allow Both Table and Tree Layouts
Close Icons for the Editor Tabs
Folding Support for JavaScript and CSS
Allow Different Element Colors Depending on XML Prefix
This allows, for instance, to have the XSLT elements in a different color than the result elements, or the XML Schema elements different from the elements used inside annotations.
Automatic Insertion of Ending Quotes or Apostrophes
Image Preview View [read more...]
Images can be viewed in an image preview panel. It supports GIF, JPG, PNG, BMP and SVG images.
Information View [read more...]
The Information view shows messages for what happens behind the scenes (for instance, when a validation is performed, it informs you of what file was validated and the schema it was validated against).
Properties View [read more...]
The Properties view shows information about the current editor (file name, encoding, number of characters, indent size, etc.)
Open a File with a User-Specified Editor
Spell-Checking Corrections on a Misspelled Word
XInclude Shorthand Pointers
More Select Actions on the Contextual Menu
Support for Floating License over Internet (not only on a Local Network)
Support for Custom Protocol Plugin