[ann] [beta] oXygen XML Editor version 14 beta is available for testing
Dear oXygen users, We are happy to announce that version 14 of oXygen XML Editor is almost ready for release. Because the new version introduces many new features, we decided to release this beta version and thus have the chance to receive your early feedback before the final release. Some of these new features will be presented at the oXygen Users Meetup in Paris, June 11: http://www.oxygenxml.com/oXygen-user-meetup-Paris2012.html Please see below for: * oXygen 14 beta download information * a license key for testing * a summary of the most important additions/new features in version 14 = Download = You can download version 14 beta for your platform from http://www.oxygenxml.com/download-beta.html Please install this side by side with your current oXygen installation. = License key = License key for version 14 beta ------START-LICENSE-KEY------ Registration_Name=oxygen 14 beta user Company= Category=Enterprise Component=XML-Editor, XSLT-Debugger, Saxon-SA Version=14 Number_of_Licenses=1 Date=05-17-2012 Trial=31 SGN=MCwCFAkZnxOqlYndXSHLSIhrGOC0I2/+AhQ0tEWVN8L4ToTKODltVOhFh7BvPg\=\= -------END-LICENSE-KEY------- = Main additions/new features in version 14 = *General* *Support for plugin and framework repositories* *Updates on Transformation and Validation scenarios* *EPUB 3.0* *Development* *Master files* *XSLT Unit Test* *XSLT 3.0* *Improved support for MarkLogic* *CTRL/CMD + click navigation* *In-place rename* *XPath/XQuery builder* *Authoring* *Change tracking and comment callouts* *Improved table editing* *New feedback-enabled WebHelp output for DITA* *Discontinuous selection* *XPath filter for Find/Replace in Author mode* *Author mode used for selecting DITA conref target elements* *Others* *Find and replace improvements* *Search results highlighted in editors* *Improved JavaScript support* *Updated Saxon-EE to its latest version* = General = *Plugin and framework repositories* As a developer you will be able to distribute your plugins and frameworks to users by placing them in a repository and publish that on your website. When you update your plugins or frameworks the users will be notified that a new version is available and they will have the option to update automatically to that new version. As a user, you can easily install new plugins and frameworks by just pointing oXygen with a URL to a repository. You will be able to browse available plugins and frameworks and select the ones you want to install. *Updates on Transformation and Validation scenarios* - Added the possibility to associate and execute multiple scenarios - Redesigned the transformation scenarios view and transformation and validation scenarios dialogs - Improved the management of the global, project and document type scenarios - Import and export operations *EPUB 3.0* The EPUB support was updated to include validation for EPUB 3.0 files. = Development = *Master files* In version 14 oXygen introduces a new innovative concept called "Master files" which simplifies the configuration and development of XML projects. The Master Files are defined at project level and are automatically used by oXygen to determine the context for operations such as validation, content-completion, refactoring or search for XSD, XSL and RNG modules. A "Master" file generally means the root of an import/include tree of modules. * Benefits: - When a module is validated oXygen will automatically identify the master files which include that module and it validates all of them, thus the module will be validated in the context it is used from. You will see from this how a change in that module affects your whole project. - When you edit a module the Outline view and the content completion will present all the components collected starting from the Master files which include that module, thus you get to see all the referable components even if they are defined in the main file or in other modules. - Search and refactoring actions, like search references or rename components operate by default on the scope defined by the Master Files * How to define the Master Files: - Drop files in the "Master Files" logical folder in the project - Use the "Add to Master Files" contextual menu action on a file that you want to mark as Master file - Use the "Add Files" contextual menu action available on the "Master File" logical folder * Best practices defining Master Files: - Add only the top level files, the ones which are the roots of the include/import graph - Keep the file set to a minimum. Do not add standalone files (the ones which do not import or include other files). Adding too many files may affect performance *XSLT Unit Test* oXygen 14 comes with XSpec to provide XSLT Unit Test support. You can easily create a test for an XSLT stylesheet by triggering the New -> XSLT Unit Test action from the contextual menu of the Project View when the selection is an XSLT stylesheet that you want to test. This will automatically generate an XSpec stub with the templates and functions from that stylesheet that you want to test. The editing of the XSpec is then assisted with content completion and a default transformation scenario is set on XSpec files which run the tests, generating as output the test report, so all you need to do to run your tests is to click on the "Apply transformation" button. *XSLT 3.0* If an XSLT stylesheet has the version attribute set to 3.0 then the XSLT 3.0 support will be enabled automatically providing - content completion for XSLT 3.0 - transformations and XSLT validation - updated Outline view and the search and refactoring actions to handle 3.0 additions *Improved support for MarkLogic* The support for developing XML and XQuery applications with MarkLogic was improved in many areas. - Remote debugging support - Remote editing - Improved XQuery validation *CTRL/CMD + click navigation* By pressing CTRL (CMD on Mac) in an XSL/XSD/RNG editor the components will become links where you can easily navigate to that component's definition by clicking on that link. *In-place rename* The rename action on components in the current file will perform an in-place rename. There is no additional dialog, the component is highlighted in the editor to mark that you are in rename mode and the rename is performed as you type. *XPath/XQuery builder* The XPath builder view was redesigned and it was extended to provide also XQuery support resulting in the new XPath/XQuery Builder. Some of the new additions are - history and favorites - evaluate as you type - expression error checking = Authoring = *Change tracking and comment callouts* The annotations/comments are presented in callouts next to the editing area, thus making it easy to collaborate on document editing and review. The callouts can be configured to present changes (insertions or deletions) as well as additional information e.g. the changed content or the date when that change or comment was created. *Improved table editing* Support for selecting columns and rows and moving them with drag and drop or cut/copy/paste actions. Delete on table selection removes only the values, the structure should be modified using the table specific actions, delete row, column, etc. *New feedback-enabled WebHelp output for DITA* By configuring a couple of parameters you can generate feedback-enabled webhelp. A sample feedback-enabled webhelp is available on our website: http://www.oxygenxml.com/doc/demo_webhelp/ *Discontinuous selection* It is possible to select multiple text ranges (discontinuous selection) or multiple elements in the Author page and cut/copy/paste them. *XPath filter for Find/Replace in Author mode* The XPath filter which was available only in Text mode is now available in the visual editing (Author) mode. *Author mode used for selecting conref target elements* The insertion of a DITA conref is easier as oXygen presents the target elements rendered through its Author mode, not the XML source, so you can preview the content you conref to as you create that conref. = Other = *Find and replace improvements* - Preview for "Replace all in Files" - Multi line support for "Find Replace in Files" *Search results highlighted in editors* The results of the XPath, Find, Search References/Declarations operations are highlighted in the editor and marked in the side bar, in both author and text mode. *Improved JavaScript support* Content Completion, Outliner and Validation for the JS script files. *Updated Saxon-EE to its latest version* oXygen is shipped with the latest Saxon Enterprise Edition, version 9.4.0.3. Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com
Thank you, SyncRO! I just installed XML Editor 14.0, build 2012051515 ("Linux", not "All" flavor) onto an Ubuntu 12.04 (amd64) system, and opened an existing file that had been edited in previous versions of oXygen. I quickly noticed that <?oxygen RNGSchema="../schema/mme.rnc" type="compact"?> doesn't find a schema, whereas both <?oxygen SCHSchema="../schema/mme.isosch"?> and <?xml-model href="../schema/mme.rnc" type="application/relax-ng-compact-syntax"?> do. (The sibling schema/ directory has both 'mme.rnc' and 'mme.isosch'; I'm not sure they are *valid* schemas, but they are there.) I have not checked to see if the same thing happens on my Mac OS X platformn yet.
We are happy to announce that version 14 of oXygen XML Editor is almost ready for release. Because the new version introduces many new features, we decided to release this beta version and thus have the chance to receive your early feedback before the final release. ...
Hi, I've just tested this with the v14 beta in Ubuntu 10.04 (this is what I had at my disposal), but could not reproduce the problem. I'll have to install Ubuntu 12 in a VM and try that as well. Do you have multiple "oxygen" or "xml-model" processing instructions in the same XML file? What's the error message or how did you arrive at the conclusion that the schema is not found/used? If you look in the Properties view (Window > Show View > Properties), does the correct schema URL appear for "Content Completion"? Regards, Adrian Adrian Buza oXygen XML Editor and Author Support Syd Bauman wrote:
Thank you, SyncRO!
I just installed XML Editor 14.0, build 2012051515 ("Linux", not "All" flavor) onto an Ubuntu 12.04 (amd64) system, and opened an existing file that had been edited in previous versions of oXygen. I quickly noticed that <?oxygen RNGSchema="../schema/mme.rnc" type="compact"?> doesn't find a schema, whereas both <?oxygen SCHSchema="../schema/mme.isosch"?> and <?xml-model href="../schema/mme.rnc" type="application/relax-ng-compact-syntax"?> do. (The sibling schema/ directory has both 'mme.rnc' and 'mme.isosch'; I'm not sure they are *valid* schemas, but they are there.)
I have not checked to see if the same thing happens on my Mac OS X platformn yet.
We are happy to announce that version 14 of oXygen XML Editor is almost ready for release. Because the new version introduces many new features, we decided to release this beta version and thus have the chance to receive your early feedback before the final release. ...
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi George, I'm checking out 14 beta and like all the new features. I'm having trouble understanding how Master Files should work, however. I've enabled Master Files for a project that contains DocBook docs that use xinclude and added the two "book" files. I see that I can validate or transform all the master files at once or individual master files, but don't see any other changes. For example, the outline view is the same when I'm editing a file included by one of the master files (I gather that's what a "module" is). When I validate a module, it does not appear to validate the master (e.g. if I put an xref in the module with a linkend value that would be valid only in the context of the master, it's marked as invalid). Am I misunderstanding how Master Files should work? Thanks, David On 05/18/2012 08:53 AM, George Cristian Bina wrote: ...
*Master files* In version 14 oXygen introduces a new innovative concept called "Master files" which simplifies the configuration and development of XML projects. The Master Files are defined at project level and are automatically used by oXygen to determine the context for operations such as validation, content-completion, refactoring or search for XSD, XSL and RNG modules. A "Master" file generally means the root of an import/include tree of modules. * Benefits: - When a module is validated oXygen will automatically identify the master files which include that module and it validates all of them, thus the module will be validated in the context it is used from. You will see from this how a change in that module affects your whole project. - When you edit a module the Outline view and the content completion will present all the components collected starting from the Master files which include that module, thus you get to see all the referable components even if they are defined in the main file or in other modules. - Search and refactoring actions, like search references or rename components operate by default on the scope defined by the Master Files * How to define the Master Files: - Drop files in the "Master Files" logical folder in the project - Use the "Add to Master Files" contextual menu action on a file that you want to mark as Master file - Use the "Add Files" contextual menu action available on the "Master File" logical folder * Best practices defining Master Files: - Add only the top level files, the ones which are the roots of the include/import graph - Keep the file set to a minimum. Do not add standalone files (the ones which do not import or include other files). Adding too many files may affect performance
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPvP5XAAoJEMHeSXG7afUhC+0IAIoo0jVNTvR8u086CaV8HJxf etKK+4CDGrgqDkKOwUhEuI9X6Mk12MDDTpHmsCaq5/xaQTzSrTw0PVq4EyYRkxrp 3hsNVPsHQTinQx+2FaD9QaB8wRIBHcVHnmN4rYegN4nsvoe6LwBqcMM5ybOjvzNX ul/iXFIhwbaVpLB6B5gabHJXIKaFeN8bmgv6NgI1T0ykjRnnnVVBKvF47iLRgkWz erW36CXaYtoHeIR5GJpugWO3FkaqLJVFdtA06VYcyo6hKE9NHuu8PBdTqkENEwAB VUWGjQDRlljpfxUYn8h0cR0B+uG6ZL2yDCdaYvDz2U/fgvzvLE3zyqe9OEncm+k= =DoMI -----END PGP SIGNATURE-----
Dear David, The master files support in version 14 will work only for XSLT, XSD and RNG. This will be extended to cover XML, DTDs, RNC, XQuery, etc. in future releases. Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 5/23/12 6:12 PM, David Cramer wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi George, I'm checking out 14 beta and like all the new features. I'm having trouble understanding how Master Files should work, however. I've enabled Master Files for a project that contains DocBook docs that use xinclude and added the two "book" files. I see that I can validate or transform all the master files at once or individual master files, but don't see any other changes.
For example, the outline view is the same when I'm editing a file included by one of the master files (I gather that's what a "module" is). When I validate a module, it does not appear to validate the master (e.g. if I put an xref in the module with a linkend value that would be valid only in the context of the master, it's marked as invalid).
Am I misunderstanding how Master Files should work?
Thanks, David
On 05/18/2012 08:53 AM, George Cristian Bina wrote: ...
*Master files* In version 14 oXygen introduces a new innovative concept called "Master files" which simplifies the configuration and development of XML projects. The Master Files are defined at project level and are automatically used by oXygen to determine the context for operations such as validation, content-completion, refactoring or search for XSD, XSL and RNG modules. A "Master" file generally means the root of an import/include tree of modules. * Benefits: - When a module is validated oXygen will automatically identify the master files which include that module and it validates all of them, thus the module will be validated in the context it is used from. You will see from this how a change in that module affects your whole project. - When you edit a module the Outline view and the content completion will present all the components collected starting from the Master files which include that module, thus you get to see all the referable components even if they are defined in the main file or in other modules. - Search and refactoring actions, like search references or rename components operate by default on the scope defined by the Master Files * How to define the Master Files: - Drop files in the "Master Files" logical folder in the project - Use the "Add to Master Files" contextual menu action on a file that you want to mark as Master file - Use the "Add Files" contextual menu action available on the "Master File" logical folder * Best practices defining Master Files: - Add only the top level files, the ones which are the roots of the include/import graph - Keep the file set to a minimum. Do not add standalone files (the ones which do not import or include other files). Adding too many files may affect performance
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJPvP5XAAoJEMHeSXG7afUhC+0IAIoo0jVNTvR8u086CaV8HJxf etKK+4CDGrgqDkKOwUhEuI9X6Mk12MDDTpHmsCaq5/xaQTzSrTw0PVq4EyYRkxrp 3hsNVPsHQTinQx+2FaD9QaB8wRIBHcVHnmN4rYegN4nsvoe6LwBqcMM5ybOjvzNX ul/iXFIhwbaVpLB6B5gabHJXIKaFeN8bmgv6NgI1T0ykjRnnnVVBKvF47iLRgkWz erW36CXaYtoHeIR5GJpugWO3FkaqLJVFdtA06VYcyo6hKE9NHuu8PBdTqkENEwAB VUWGjQDRlljpfxUYn8h0cR0B+uG6ZL2yDCdaYvDz2U/fgvzvLE3zyqe9OEncm+k= =DoMI -----END PGP SIGNATURE-----
George Cristian Bina wrote: Hi,
We are happy to announce that version 14 of oXygen XML Editor is almost ready for release. Because the new version introduces many new features, we decided to release this beta version and thus have the chance to receive your early feedback before the final release.
Thanks for sharing this beta!
*XSLT Unit Test* oXygen 14 comes with XSpec to provide XSLT Unit Test support.
That's good news!
a default transformation scenario is set on XSpec files which run the tests, generating as output the test report, so all you need to do to run your tests is to click on the "Apply transformation" button.
Well done! I note there are two kinds of scenarios for XSpec, either using Ant or using XProc. I guess XProc test harnesses are going to be the prefered and most maintained way of launching running XSpec test suites (IMHO the only "raison d'etre" of the Ant way is for systems without an XProc processor). But it looks to me like the XProc scenario is too closely related to the Saxon test harness. I guess the ideal situation would be to have radio buttons to select between the standard harnesses AND a file input if the user wants to provide his/her own pipeline harness. In addition, it would be very interesting to be able to configure some of the standard harnesses with details that come from oXygen's data sources. It would be very handy for a user to say: "I want to run this test suite on this or that data source". E.g. if the data source is an eXist data source, oXygen already knows all the details to pass to the XProc test harness, like the connection point, etc. Thank you for this new feature in oXygen! Regards, -- Florent Georges http://fgeorges.org/ http://h2oconsulting.be/
Hi Florent,
Well done! I note there are two kinds of scenarios for XSpec, either using Ant or using XProc. I guess XProc test harnesses are going to be the prefered and most maintained way of launching running XSpec test suites (IMHO the only "raison d'etre" of the Ant way is for systems without an XProc processor).
As we discussed at XML Prague, the main reason we went for ANT in favor of XProc was the ability to pass extensions libraries to the processor. Currently the only way you can do that for an XProc transformation is to edit an XML descriptor and put the jars in Oxygen lib. So we lack the dynamic configuration of the extensions. But the good news is that we intend to extend the XProc scenario to be able to specify the extension libraries that will be automatically loaded. As soon as we add this functionality we will be able to make the XProc scenario the default one.
But it looks to me like the XProc scenario is too closely related to the Saxon test harness. Currently we focused on the XSLT part and since Saxon is the only engine supported by XSpec, these are the default scenarios we added. The next version we will focus on the XQuery part.
In addition, it would be very interesting to be able to configure some of the standard harnesses with details that come from oXygen's data sources. That's a good idea! We did something similar for XSLT: if you generate an XSpec for an XSL with an associated transformation scenario, we take the Saxon configuration from the scenario and we create a custom XSpec scenario that will run with the same Saxon configuration (and the same the extensions). We will probably do the same for XQuery: we will detect the data source from the transformation scenario and we will use the proper harness (eXist, ML etc) configured as in that data source.
Best regards, Alex -- Alex Jitianu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 5/23/2012 7:57 PM, Florent Georges wrote:
George Cristian Bina wrote:
Hi,
We are happy to announce that version 14 of oXygen XML Editor is almost ready for release. Because the new version introduces many new features, we decided to release this beta version and thus have the chance to receive your early feedback before the final release. Thanks for sharing this beta!
*XSLT Unit Test* oXygen 14 comes with XSpec to provide XSLT Unit Test support. That's good news!
a default transformation scenario is set on XSpec files which run the tests, generating as output the test report, so all you need to do to run your tests is to click on the "Apply transformation" button. Well done! I note there are two kinds of scenarios for XSpec, either using Ant or using XProc. I guess XProc test harnesses are going to be the prefered and most maintained way of launching running XSpec test suites (IMHO the only "raison d'etre" of the Ant way is for systems without an XProc processor). But it looks to me like the XProc scenario is too closely related to the Saxon test harness. I guess the ideal situation would be to have radio buttons to select between the standard harnesses AND a file input if the user wants to provide his/her own pipeline harness.
In addition, it would be very interesting to be able to configure some of the standard harnesses with details that come from oXygen's data sources. It would be very handy for a user to say: "I want to run this test suite on this or that data source". E.g. if the data source is an eXist data source, oXygen already knows all the details to pass to the XProc test harness, like the connection point, etc.
Thank you for this new feature in oXygen!
Regards,
-- Florent Georges http://fgeorges.org/ http://h2oconsulting.be/ _______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
participants (6)
-
Adrian Buza -
Alex Jitianu -
David Cramer -
Florent Georges -
George Cristian Bina -
Syd Bauman