[ann] oXygen version 16 is available
Hi all, I am happy to let you know that oXygen XML Editor version 16 is available from our website: http://www.oxygenxml.com The new version introduces quick fix support and implements quick fixes for the XSLT editor. We expect the support to be extended in the following releases to cover other editors like XML Schema, Relax NG, etc. and also XML itself. A very interesting work in this area is the Schematron quick fixes that will allow a Schematron schema author not only to provide human readable error messages but also a set of actions to allow users to fix the identified issue, for details please see http://www.w3.org/community/quickfix/. In the meanwhile you can get an idea on how XSLT quick fixes work in oXygen 16 in this short video http://oxygenxml.com/demo/XSLT_Quick_Fix_Support.html The Ant editor is also a very important addition in oXygen 16. If you work with Ant scripts give oXygen 16 a try. You can even edit Ant modules in context as we extended also the master files support to include Ant scripts. Here it is a short video that gives you an overview of the new Ant editing support http://oxygenxml.com/demo/Ant_Support.html XPath on multiple files is another nice addition in oXygen 16. You can select a scope in the XPath query field in the toolbar or in the XPath Builder view and the XPath expression will be executed on all the files selected by that scope. Predefined scopes include all open files, current project selection, all project files and you can also define your custom working sets. On the XML authoring we added better support for working with conditional content by allowing you to define colors and styles for specific profiling conditions and then apply those automatically to you can easily spot which part of the content goes to which deliverable. Also, when you focus on a specific deliverable you have the option to completely hide the content that is excluded from that. Here it is a video demo to show this in action http://oxygenxml.com/demo/Colors_and_Styles_for_Profiled_Content.html The oXygen WebHelp transformation from DITA and DocBook are very populat but a lot of users wanted to customize the styles of the WebHelp output. The new WebHelp skin builder allows to do that visually, see the demo at http://oxygenxml.com/demo/Skin_Builder.html or give it a try at http://oxygenxml.com/webhelp-skin-builder/ For the complete release notes please see http://oxygenxml.com/whatisnew16.0.html Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com
On Tue, 20 May 2014, George Cristian Bina wrote:
XPath on multiple files is another nice addition in oXygen 16.
Hallelujah! This will be very helpful for quick consistency/quality assurance checks across multiple files when one doesn't want to spend the time to write up a Schematron schema. David -- David Sewell, Editorial and Technical Manager ROTUNDA, The University of Virginia Press PO Box 400314, Charlottesville, VA 22904-4314 USA Email: dsewell@virginia.edu Tel: +1 434 924 9973 Web: http://rotunda.upress.virginia.edu/
I have been using the new "XPath on multiple files" feature in oXygen 16.0 today. It works beautifully on project files, and very fast. Is there a way to get it to operate on an EPUB (or other zip file) that is open in Archive Browser? I tried to do this by creating a working set using "path of the current archive" and a couple of other options, but that didn't work. -- David Sewell, Editorial and Technical Manager ROTUNDA, The University of Virginia Press PO Box 400314, Charlottesville, VA 22904-4314 USA Email: dsewell@virginia.edu Tel: +1 434 924 9973 Web: http://rotunda.upress.virginia.edu/
Hi all, On 2014-05-22, http://www.oxygenxml.com/whatisnew16.0.html said:
Editor Variable for Evaluating XPath 3.0 Expressions
The xpath_eval(expression) editor variable allows you to evaluate XPath 3.0 expressions either statically, in non-XML contexts, or dynamically, relative to the current element, in XML contexts. As an example, this gives you access to all standard XPath functions like replace(), substring() or upper-case() when you compute the output file name of a transformation.
Is this supposed to work in author actions as well? I have tried to define an action using ro.sync.ecss.extensions.commons.operations.ShowElementDocumentationOperation with the URL pattern parameter: http://www.google.com/search?tbm=bks&q=${xpath_eval('ancestor-or-self::*:TEI/*:teiHeader/*:fileDesc/*:titleStmt/*:title[type="main"]')} but the ${xpath_eval()} is just passed as-is to google. Thanks for any insight, Andreas -- Dr. Andreas Wagner Project "The School of Salamanca" Academy of Sciences and Literature, Mainz and Institute of Philosophy Goethe University Frankfurt http://salamanca.adwmainz.de Grüneburgplatz 1 (Pf 116, R. 2.455) 60629 Frankfurt am Main Tel. +49 (0)69/798-32774 Fax +49 (0)69/798-32794
Hi Andreas, The XPath value inside the xpath_eval method should not be surrounded by single quotes, it should be like:
The XPath processor obtains the value exactly as it is (Oxygen does not remove starting and ending quotes) and in your case it received the value as a single quoted literal string which was evaluated and returned as such. Regards, Radu Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 5/22/2014 4:47 PM, Andreas Wagner wrote:
Hi all,
On 2014-05-22, http://www.oxygenxml.com/whatisnew16.0.html said:
Editor Variable for Evaluating XPath 3.0 Expressions
The xpath_eval(expression) editor variable allows you to evaluate XPath 3.0 expressions either statically, in non-XML contexts, or dynamically, relative to the current element, in XML contexts. As an example, this gives you access to all standard XPath functions like replace(), substring() or upper-case() when you compute the output file name of a transformation.
Is this supposed to work in author actions as well? I have tried to define an action using ro.sync.ecss.extensions.commons.operations.ShowElementDocumentationOperation
with the URL pattern parameter:
but the ${xpath_eval()} is just passed as-is to google.
Thanks for any insight,
Andreas
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
Hi Radu, * Oxygen XML Editor Support (Radu Coravu) dixit [2014-05-22 16:05]:
The XPath value inside the xpath_eval method should not be surrounded by single quotes, it should be like:
The XPath processor obtains the value exactly as it is (Oxygen does not remove starting and ending quotes) and in your case it received the value as a single quoted literal string which was evaluated and returned as such.
I have just tried this now but the whole, unparsed string following "...q=" is passed on as the target url to the browse, so I end up at a google search for (literally): ${xpath_eval(ancestor-or-self::*:TEI/*:teiHeader/*:fileDesc/*:titleStmt/*:title[type="main"])} I hope I am not expecting something to work that is not supposed to do so in the first place...? Andreas -- Dr. Andreas Wagner Project "The School of Salamanca" Academy of Sciences and Literature, Mainz and Institute of Philosophy Goethe University Frankfurt http://salamanca.adwmainz.de Grüneburgplatz 1 (Pf 116, R. 2.455) 60629 Frankfurt am Main Tel. +49 (0)69/798-32774 Fax +49 (0)69/798-32794
Hi Andreas, So you are using Oxygen 16.0, right? What I did to test was to edit the DITA document type association and define a new action which invokes "ro.sync.ecss.extensions.commons.operations.ShowElementDocumentationOperation" with the "URL pattern" parameter set to:
http://www.google.com/search?tbm=bks&q=${xpath_eval(name())}
Then I invoked the action when placing the caret in a DITA paragraph <p> element. The web browser was opened with the URL:
So it worked for me. Regards, Radu Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 5/22/2014 5:20 PM, Andreas Wagner wrote:
Hi Radu,
* Oxygen XML Editor Support (Radu Coravu) dixit [2014-05-22 16:05]:
The XPath value inside the xpath_eval method should not be surrounded by single quotes, it should be like:
The XPath processor obtains the value exactly as it is (Oxygen does not remove starting and ending quotes) and in your case it received the value as a single quoted literal string which was evaluated and returned as such.
I have just tried this now but the whole, unparsed string following "...q=" is passed on as the target url to the browse, so I end up at a google search for (literally):
${xpath_eval(ancestor-or-self::*:TEI/*:teiHeader/*:fileDesc/*:titleStmt/*:title[type="main"])}
I hope I am not expecting something to work that is not supposed to do so in the first place...?
Andreas
Hi Radu, hi all, * Oxygen XML Editor Support (Radu Coravu) dixit [2014-05-22 16:29]:
So you are using Oxygen 16.0, right?
Duh; I feel so stupid. I had installed 16.0, confirming the de-installation of my old 15.2 when I was asked about it. So I thought I just must be using 16.0. It just so happened that I was launching oXygen via a self-made symlink called "oxygen" (without version number) and that pointed to the 15.2 symlink which in turn pointed to the 15.2 binary, which were to my surprise all still around... Now I redirected my "oxygen" symlink and, tadaaa, it works. Just for the record (and perhaps for showing off the power of the ${xpath_eval()} variable), I am using the following as "URL pattern" parameter: https://www.google.de/search?tbm=bks&q=${xpath_eval( normalize-space( concat( ancestor-or-self::TEI/teiHeader/fileDesc/titleStmt/title[@type="main"]/text(), ", ", string-join( ancestor-or-self::TEI/teiHeader/fileDesc/titleStmt/author, " " ) ) ) )} When launching my action from anywhere within the document, this opens the web browser at http://www.google.de/search?tbm=bks&q=Summa%20Theologiae%20Moralis,%20Enrique%20Henr%C3%ADquez A thousand ideas coming to my mind right now as to what else can be done with this wonderful new feature. Thank you a lot - and please excuse my dumbness in not realizing I had still been running the old version all the time. Andreas -- Dr. Andreas Wagner Project "The School of Salamanca" Academy of Sciences and Literature, Mainz and Institute of Philosophy Goethe University Frankfurt http://salamanca.adwmainz.de Grüneburgplatz 1 (Pf 116, R. 2.455) 60629 Frankfurt am Main Tel. +49 (0)69/798-32774 Fax +49 (0)69/798-32794
participants (4)
-
Andreas Wagner -
David Sewell -
George Cristian Bina -
Oxygen XML Editor Support (Radu Coravu)