Thank you for the reply. I see that I will have to create some kind of workaround rather than believe I can craft a super XPath. That is actually helpful to know. In the real application I am actually looking for data that is relative to the node with the caret. For example something like this: (nod...

The users are all using text mode.

Hi, In a plugin I need to extract data from at document relative to the current node, i.e. the node at which the caret is. First I need to find that node. I am using evaluateXPath (). The problem is crafting the Xpath expression that will yield the correct node. I have found that the . operator will...

Thanks!

evaluateXPath() returns an array of Object. Exactly what object depends on the XPath expression but when the result is a sequence of nodes I seem to get classes from org.apache.xerces.dom. I'd like to use the appropriate methods on those objects. import org.apache.xerces.dom.*; // Compilte time erro...

This seems to work but there is a little catch. Both extensions are given the same name (the name of the plugin) on the plugins submenu of the context menu.

Is there a way I can give each extension a name?

That makes sense, thank you!

Hi, First I'd like to say i appreciate the add-on deployment feature of Oxygen. My users can easily add and update the plugins I create via Help->Manage add-ons... Now I want to create some plugins that depend on each other. I.e. each of them is not useful without the other. They will share one or m...

Could you elaborate on the use case? Currently we invoke a batch process as an external tool to process the XML file we are working on. Informative and error messages are displayed in the output pane. If we could format these messages the same way as for external validation engines we might have th...

Thank you,

Would it be hard to allow External Tools to use the Linked Output Message format similar to External Validation Engines?

Kudos to you for reflecting on customer input.

Hi Radu, Yes, that is a useful extension that we could benefit from. Your suggestion does not preclude a more general solution later on. I was already thinking (to myself) that a format for context menu extensions might look something like this: AddMenuItem: "Explain message msg999",URL:&q...

Thank you!

We are almost exclusively using the text mode. We have been able to create plugins that are accessible from a sub menu of the context menu in the editor. This particular request however is for the result pane as you mentioned.

Looking forward to future versions. Keep up the good work!

We are happy users of the custom validation engine feature. We use the linked output message format so that the user can click the message and be brought to the appropriate place in the XML source file. Nice. However, we would like to give the user more options. Here is what I envision: Let a linked...

I'd like to suggest a pair of editor variables to delimit part of the text that is returned by a selection plugin or code template. If we for the purpose of the following example name them ${ssel} for start selection and ${esel} for end selection you could create a code template like this: <xsl:choo...

The output to source mapping is a useful feature of the XSLT debugger. I can click on a piece of output and will be shown the corresponding data from both the input document and the XSLT stylesheet. However I am unable to get this to work when the stylesheet uses the <xsl:result-document> instructio...