[oXygen-user] [ANN] oXygen XML Editor 7.0 beta

[George Cristian Bina]

Hi everybody,

I'm glad to let you know that oXygen 7 reached a beta status. We made a 
number of important changes since version 6.2 and I will try to 
summarize them below. I would like to take this opportunity to thank you 
for your support and to wish you Merry Christmas and a Happy New Year!

Please let us know if you encounter any issues. The release is planned 
for the beginning of 2006.

The oXygen beta 7 distributions are available from
http://www.oxygenxml.com/download-beta.html

You will also need a license key for version 7, you can find that here:

--- start license key ---

Registration_Name=oXygen version 7 beta user

Company=

Category=Professional

Component=XML-Editor, XSLT-Debugger

Version=7, 7

Number_of_Licenses=1

Date=12-21-2005

Duration=31

SGN=MCwCFEjLw7CJDM17s9NLdBPmJLWGtR5jAhRZdlpud98LczECHQlvWBS94eZwCw\=\=

--- end license key ---

==================
New in oXygen version 7
==================

Validation
=======

* Continuous validation
   The document validation is performed when the document is changed. 
The current error is presented in an editor auto-hideable status bar.

* Error markers and overview ruler
   The errors, including the ones generated by the continuous validation 
are marked in place by underlining the error location. The locations are 
also marked in an overview ruler that allows quick navigation between 
the error markers.

* Support for caching when validating against schemas
   By default the validate action will cache the parsed schemas. There 
is also a "Reset cache and validate" action provided to allow 
revalidation in development environments when the schema is changed.

* Support for multiple external validation engines
   (like LIBXML, XSV, SaxonSA, MSXML4.0, MSXML .NET, SQC).

* Support for ignoring the DTD for validation if other schema is specified
   Now it is possible to use the DTD for entities support only with any 
schema type (in version 6.2 this was possible only with XML schema).

* Support for DTDs for external validation
   It is possible to validate against a DTD even if the DTD is not 
specified inside the document.

* Support for associating DTDs for validation using the external schema 
association
   In version 6.2 the external associated DTDs were used only for 
content completion. Now they are used also for validation.

* Support for CSS validation
   Different CSS profiles are supported like CSS2, CSS3, etc. and 
different media types like Braille or screen for instance.

XPath
=====

* XPath context sensitive content completion
   When editing an XPath value oXygen offers the available elements, 
attributes, functions, axes, variables, etc. in that context. The 
context is computed taken into account all the ancestors that can change 
the context.

* Support for XPath default namespace
   For XPath 2.0 queries the XPath default namespace can be 
configured/automatically detected and used to write XPath queries.

* XPath execution in the context of the current element
   The XPath expressions are evaluated from the current element so 
relative expression can be evaluated in different contexts.

XSLT
====

* XSLT Input View
   Presents the tree structure of the XML document set as input for the 
current stylesheet in the associated transformation scenario. Elements 
and attributes from this view can be inserted in different XSLT 
constructs by dragging them from the XSLT Input View in the XSLT editor.

* Search References for XSLT
   This search is performed for any XSLT component that has references, 
like 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 Declarations for XSLT
   This search is performed for any XSLT component that has 
declarations, like 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 Occurrences for XSLT
   This provides a quick retrieval of all the declarations and 
references of a component in the current file.

* XSLT Refactoring: Rename Occurrences
    This allows renaming XSLT components like 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 viewing all the 
changes that will be done before 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.

* XSLT Refactoring: Create stylesheet from selection
   The selection will be placed in a new stylesheet that will be 
included in the current stylesheet.

* XSLT Refactoring: Create template from selection
   The selection will be placed in a named template and will be 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
   From the project panel it is possible to select multiple files and 
apply their associated transformation scenarios on each one.

* Apply a specified transformation scenario on a set of files
   From the project panel a set of files can be selected then a 
transformation scenario will be selected and applied on each of the 
selected files.

* Allow configuring the XSLT transformer options through oXygen 
preferences
   Processor specific options for Saxon, XSLTProc, MSXML and MSXML.NET 
can be configured through the oXygen preferences.

* Support the System.Xml 2.0 transformer
   The .NET 2.0 framework transformer can be used now from oXygen.

* Support for the latest version of Saxon 8
   Saxon 8.6.1 from Saxonica (http://www.saxonica.com) is now supported.

XQuery
=====

* XQuery Debugger
   Full debugging support similar with the XSLT Debugger.

* XQuery Profiler
   Profiling support similar with the XSLT profiling support.

Schema editors
===========

* Zoom support for diagrams
   The diagrams can be made smaller or larger depending on the zoom 
settings.

* Schema Components View
   The schema components were moved from the schema editor in a dockable 
view called Schema Components View.

Content completion
==============

* Support for showing recent content items
   The proposals that are actually used by the user are promoted at the 
top of the content completion list thus making their reuse easy.

* Handling of namespace prefixes
   The namespace prefixes are presented first in the list of proposals 
for elements, thus making editing really easy for documents that use 
prefixes for elements.

* Support for learning words
   You need to turn this on as it is disabled by default. All the words 
in the document will be indexed and when you write a prefix followed by 
CTRL+Space the words starting with that prefix are presented through the 
content completion window.

* Present #ID URI fragments for anyURI attribute values
   When an attribute value is of type anyURI (in both XML Schema and 
Relax NG schema) oXygen will present proposals of the form #ID for each 
defined ID value in the document.

* Look for type annotations if the elements or attributes do not have 
annotations
   When editing documents against an XML Schema oXygen will look as deep 
as needed in the type hierarchy for an element type or an attribute type 
if the respective element or attribute do not have an annotation and 
will present the first encountered annotation next to the content 
completion proposal.

* The content completion presents element values when using a relax NG 
schema
   The element values support on content completion was extended to work 
also when the document is edited against a Relax NG schema.

* Support for presenting the xsi:nil attribute for nillable elements
   If an element is defined as nillable in the associated XML Schema 
oXygen presents the xsi:nill attribute through the content completion 
for possible attributes for that element.

* Improved content completion for CSS
   The content completion provides now property values for each property.

GUI
===
* Dockable editors
   Not only the views can be moved around the interface but also the 
editors can be arranged as you need inside the editing area.

* Split editor in two
   It is possible to have two editors on the same file side by side so 
you can edit a different location in a file while looking at some other 
location in the same file in the other editor.

* The find dialog is not modal
   The Find dialog allows now going to the editor while it is still open 
and then allows resuming the search.

* Configurable GUI fonts
    It is possible to specify the fonts to be used not only for editor 
but also for GUI text components and for the other GUI components. This 
allows having a user friendly and accessible application even on 
configurations with a very small dpi (like my notebook for instance :).

* All the result views allow both table and tree layouts
   The information presented in the results view (like the errors after 
a validation action for instance) can be presented either in a table 
layout or in a tree layout that groups the messages by system ID. Also 
support for removing the selected items or all the items in a view is 
provided.

* Close icons for the editor tabs
   Editor tabs can be easily closed not only with a middle click but 
also using the X close icon that appears in each editor tab.

* System icons are used for files that are not handled by oXygen
   Instead of showing an unknown icon oXygen shows the system icons thus 
it is easy to identify for instance a PDF file in the project panel.

* Model View supports wrapping
   The element models were in general very large for complex schemas and 
that made the Model View show an horizontal scroll bar and the model 
information was always out of sight. Now by wrapping the model the 
information is always visible.

* Folding support for JavaScript and CSS
   The folding is based on curly braces.

Others
=====
* Allow different element colors depending on 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
   If a starting quote or apostrophe is entered the ending quote are, 
respectively apostrophe is automatically inserted.

* Image Preview View
   Images can be viewed in oXygen. It supports GIF, JPG, PNG, BMP and 
SVG images.

* Information View
   Shows some messages with what happens under the scene, for instance 
when a validation is performed it informs what file against what schema 
was validated.

* Properties View
   Shows information about the current editor like: filename, encoding, 
number of characters, indent size, etc.

* Open a file with a user specified editor
   No matter to what editor a file is associated in editor it can be 
opened with a specified oXygen editor using the project panel contextual 
"Open As" action.

* Spell-checking corrections on a mis-spelled word
   When a word is identified as mis-spelled by the spelling as you type 
support and is highlighted on the screen on the contextual menu there 
are presented now the possible correct replacements of that word.

* Support xml:id to define XInclude shorthand pointers for included 
document fragments that do not use DTDs.

* Extract XML Schema from a database structure
   This can be done either when importing data from a database or 
directly by selecting the database tables.

* More Select actions on the contextual menu
   Two more select actions were added: select parent and select attributes.

* Support for floating license over internet (not only on a local network)
   There is available a license server that can be installed. The 
floating license keys can be dropped there and the applications can be 
directed to the license server to get a license from.

* Support for  custom protocol plugin
   It will be possible to write a plugin for handling a custom protocol, 
for instance one can have a plugin to handle the cvs protocol thus 
providing support in oXygen to access files on a CVS server.

Best Regards,
George
---------------------------------------------------------------------
George Cristian Bina
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com