Features
What's new in <oXygen/> 1.2.2
- XML Schema Code Insight improving .
- It is now possible to make the tags read only . In this way it can be edited only the text content of the document.
- There can be specified parameters for the XSL transformation and is possible to append a header and a footer
to the XSL transformation result.
- The pretty print operation keeps the cursor in the same location as before. In the last release, after the operation completed, the cursor was moved to the first line.
- Better undo/redo mechanism.
- Changed the Copy/Paste to support large data sections.
- Proxy configuration. It allows editing of documents with DTD or schemas located on other sites,
when you do not have a direct connection to the Internet.
- Specific to Mac OS X:
- Fixed a bug concerning the use of the contextual menu for Copy, Paste, or "Enclose in".
- Fixed a bug that made printing on Mac OS X impossible.
- Files are opened now using the standard file open dialog.
What's new in <oXygen/> 1.2.1
- XPath
support was improved. The result list of nodes is presented in
a tab located at the bottom of the editor. When the user clicks
on an item from the list, the text section corresponding to the
selected node will be highlighted. Double-clicking or pressing
ENTER over the selection will move the cursor at the beginning
of the highlight.
- Schema
driven code insight follows closely the schema structure. Now
only the valid elements in a given context are presented by the
code insight instead of all possible elements in a given context.
For instance if a given element has as model a sequence formed
by "a", "b" and "c" the code insight will offer only element "a"
immediately after the given element. Before all three elements
were offered.
- Mac
OSX support. We addressed some of the specific problems on Mac
OSX, the most important being the empty dialogs that used to appear
for some of the options.
-
No more interference from Java extensions.
We use our custom class loader to load the application classes so there
will not be problems anymore with extensions loaded instead of the
application jars.
What's new in <oXygen/> 1.2
- The editor can be used as an applet. Corporations can use it to reduce the overhead of
installing and upgrading the editor on a large number of workstation.
- FOP. The editor has built-in support for Formatting Objects processing. Allows generation
of the PDF, PS, TXT from the result of an XSLT or directly from a FO file. One or more supplementary external FO processors can be specified
- Makes persistent the XML transformation settings for the edited file. For example you can
choose the stylesheet to be applied over an edited XML file and the next time you will edit it, the editor will use the specified stylesheet.
- Easily transform text content into an XML document, by using the "enclose in" option in the
context menu. This is similar to the CodeInsight mechanism, and is accessible on the right-click popup menu after selecting some text
- Projects are much easy to use. The editor will load automatically the last project.
What's new in <oXygen/> 1.1.9
- The checks for valid and well formed documents and the apply stylesheet operations run on a different thread so that the GUI remains usable
- Acknowledgements of the above operations are replaced with notifications in status bar to avoid interruptions.
- Schema driven code insight is improved to offer attribute values in case of enumeration and default values and to handle multiple namespaces.
- Registration form in application - now, you can get your license submiting informations using a registration form which is loaded if no license detected.
- Improved GUI
- Handle properly document URLs containing spaces
- Add printing scale factor
What's new in <oXygen/> 1.1.8
- Fix some code insight problems
What's new in <oXygen/> 1.1.7
- Handle unknown encodings
- Add configuration options for Pretty Print
- Add Print Results item in the File menu
What's new in <oXygen/> 1.1.6
- DTD Validation support
- Associate extensions with <oXygen/> (Windows only)
- Make last visited directory persistent between different runs.
What's new in <oXygen/> 1.1.5
- XHTML support - one can use the copy.xsl stylesheet to view an XHTML document in the HTML result panel.
- Support for choosing the editor font - usefull for editing documents with special characters (e.g. Japanese)
- Unicode support
What's new in <oXygen/> 1.1
- Customization panel. The user can choose the colors/styles he/she wants for the syntax highlight at the XML token level. All editor options will be modified from a centralized frame
- Print of the editor views, and the possibility of printing results
- Improved syntax highlight
- XSL output window associated to an XML document. This allows the user to see the result of applying a stylesheet over the document when editing, as he/she types
- The possibility of generating a DTD or XML Schema file describing the structure of an XML document without DOCTYPE or schema
- Project panel. Allows the user to organize the project as a tree of URLs
- Code Insight over the XML documents validated using XML Schema
- Improving validation of XML Schema (In <oXygen/> 1.0 it is done by validating the XML Schema against a DTD)
- Large documents support
<oXygen/> 1.0
- Support for XML, XSL, TXT and DTD documents
- Syntax highlight. Element names, comments are displayed with different colors. This is done at the time the user types in the text. The color palette is changed when the user edits DTD or XML/XSL.
- Code-Insight. At the time the user types in an element name, the editor will popup a list from which the user can choose one of the elements that are can be inserted in that section of the document. Examining the DTD and the context of the parent node does this. This is extended at for the attributes names. In the case the document represents a XSL, then the list contains all the elements from the XSL namespace.
- End-Tag-Auto-Completion. If the user types in an element name, then the editor will automatically insert the end tag.
- Xpath console to query xml content
- Pretty printing. The editor can organize the XML source as a tree.
- Apply style sheet on a selected XML and display result both as text and as HTML.
- Learn document structure and offer auto complete and code-insight even if there is no DTD.
- Check for valid and well formed XML content.
- Error reporting with line number information (where available).
- Multiple document interface (MDI).
- Word wrap.
- Help available
- Available languages: English, French, German, Italian and Romanian.
- All the usual editor capabilities (cut, copy, paste, find, replace, windows management)