Re: [oXygen-user] [Oxygen-user] completion for XPath 2.0 functions and keywords in XSLT stylesheets?
Hi, Actually Oxygen's content completion of XPath in XSLT 2.0 does include the functions and axes of XPath 2.0. Make sure they are all enabled in Options -> Preferences -> Editor -> Content Completion -> XPath. It's also possible that you've found a context that we did not cover, or maybe a bug. Could provide a sample XSLT where this fails to work as expected? Regards, Adrian Adrian Buza oXygen XML Editor and Author support support@oxygenxml.com http://www.oxygenxml.com Lars Huttar wrote:
Hello,
I've been writing more stylesheets lately using XSLT 2.0, and trying to get into the habit of using the useful new features of XPath 2.0. However, I find that it's not as convenient as it could be in Oxygen 12, because Oxygen's completion of XPath syntax does not seem to include functions and keywords of XPath 2.0. Do you plan to add these soon?
This is in addition to a feature request I've made previously, that XSLT 2.0 instructions be included in the built-in code snippets and in XSLT tag completion.
Regards, Lars Huttar
_______________________________________________ Oxygen-user mailing list Oxygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
Adrian Buza wrote: Hi,
It's also possible that you've found a context that we did not cover, or maybe a bug. Could provide a sample XSLT where this fails to work as expected?
As far as I know, this completion is not available in XProc, in the contexts where an XPath expression is expected (like in the p:with-option/@select attribute for instance). It would be *very* nice to have the same support as in XSLT :-) Is there any way to augment the completion function database? I frequently use some functions, and I thought to add their prototypes and documentations to the ones known by oXygen. I was optimistic and hoped to find an XML file that recorded all those possible completion, and that it would be as simple as adding some entries to that file. But I never found such a file :-/ Is there any way to do that? Best regards, -- Florent Georges http://fgeorges.org/
Hi, Oxygen's content completion for XML is schema driven. But there is this part of XSLT content completion for XPath that was hard-coded in the appropriate locations. XProc did not yet receive this treatment and there's no way for the end user to augment this right now. I'll add a feature request for XPath content completion in XProc. And I'll also add a feature request for making the content completion customizable in the long term. Regards, Adrian Adrian Buza oXygen XML Editor and Author support support@oxygenxml.com http://www.oxygenxml.com Florent Georges wrote:
Adrian Buza wrote:
Hi,
It's also possible that you've found a context that we did not cover, or maybe a bug. Could provide a sample XSLT where this fails to work as expected?
As far as I know, this completion is not available in XProc, in the contexts where an XPath expression is expected (like in the p:with-option/@select attribute for instance). It would be *very* nice to have the same support as in XSLT :-)
Is there any way to augment the completion function database?
I frequently use some functions, and I thought to add their prototypes and documentations to the ones known by oXygen. I was optimistic and hoped to find an XML file that recorded all those possible completion, and that it would be as simple as adding some entries to that file. But I never found such a file :-/ Is there any way to do that?
Best regards,
Adrian Buza wrote:
And I'll also add a feature request for making the content completion customizable in the long term.
That'd be great, thank you! -- Florent Georges http://fgeorges.org/
Hello Adrian, Thanks for your reply. I just verified that all checkboxes on Options -> Preferences -> Editor -> Content Completion -> XPath are checked. An example where content completion does not include everything I expect is here: <xsl:function name="fn:difference" as="^"> The caret represents the cursor position. When I press Ctrl+Space here, I get a list of completions, including "item()*" and many "xs:*" options. However the list does not include "element()", which is the value I want. Moreover, if I type "ele" and press Ctrl+Space, no completion is offered. However, if I manually type "element()", and then validate the stylesheet, the expression is found to be valid. The same situation happens with <xsl:param name="n1" as="node()"/> and similar "as" attribute values, except that in this case, not even "item()*" was offered as a completion option. FYI I am using v 12.0, build 2010091411. Regards, Lars On 11/10/2010 8:55 AM, Adrian Buza wrote:
Hi,
Actually Oxygen's content completion of XPath in XSLT 2.0 does include the functions and axes of XPath 2.0. Make sure they are all enabled in Options -> Preferences -> Editor -> Content Completion -> XPath.
It's also possible that you've found a context that we did not cover, or maybe a bug. Could provide a sample XSLT where this fails to work as expected?
Regards, Adrian
Adrian Buza oXygen XML Editor and Author support support@oxygenxml.com http://www.oxygenxml.com
Lars Huttar wrote:
Hello,
I've been writing more stylesheets lately using XSLT 2.0, and trying to get into the habit of using the useful new features of XPath 2.0. However, I find that it's not as convenient as it could be in Oxygen 12, because Oxygen's completion of XPath syntax does not seem to include functions and keywords of XPath 2.0. Do you plan to add these soon?
This is in addition to a feature request I've made previously, that XSLT 2.0 instructions be included in the built-in code snippets and in XSLT tag completion.
Regards, Lars Huttar
_______________________________________________ Oxygen-user mailing list Oxygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
Lars, Thank you for providing details for this problem. It seems that content completion for type names was overlooked(besides the obvious xs:* types). I'm guessing "item()*" was manually added to that list of completions in that particular context. This problem needs to be addressed for types in general. I've logged this to our issue tracking tool and we'll fix it in a future version of Oxygen. I believe this will not make it in time for v12.1. Regards, Adrian Adrian Buza oXygen XML Editor and Author support support@oxygenxml.com http://www.oxygenxml.com Lars Huttar wrote:
Hello Adrian, Thanks for your reply.
I just verified that all checkboxes on Options -> Preferences -> Editor -> Content Completion -> XPath are checked.
An example where content completion does not include everything I expect is here:
<xsl:function name="fn:difference" as="^">
The caret represents the cursor position.
When I press Ctrl+Space here, I get a list of completions, including "item()*" and many "xs:*" options. However the list does not include "element()", which is the value I want. Moreover, if I type "ele" and press Ctrl+Space, no completion is offered.
However, if I manually type "element()", and then validate the stylesheet, the expression is found to be valid.
The same situation happens with
<xsl:param name="n1" as="node()"/>
and similar "as" attribute values, except that in this case, not even "item()*" was offered as a completion option.
FYI I am using v 12.0, build 2010091411.
Regards, Lars
On 11/10/2010 8:55 AM, Adrian Buza wrote:
Hi,
Actually Oxygen's content completion of XPath in XSLT 2.0 does include the functions and axes of XPath 2.0. Make sure they are all enabled in Options -> Preferences -> Editor -> Content Completion -> XPath.
It's also possible that you've found a context that we did not cover, or maybe a bug. Could provide a sample XSLT where this fails to work as expected?
Regards, Adrian
Adrian Buza oXygen XML Editor and Author support support@oxygenxml.com http://www.oxygenxml.com
Lars Huttar wrote:
Hello,
I've been writing more stylesheets lately using XSLT 2.0, and trying to get into the habit of using the useful new features of XPath 2.0. However, I find that it's not as convenient as it could be in Oxygen 12, because Oxygen's completion of XPath syntax does not seem to include functions and keywords of XPath 2.0. Do you plan to add these soon?
This is in addition to a feature request I've made previously, that XSLT 2.0 instructions be included in the built-in code snippets and in XSLT tag completion.
Regards, Lars Huttar
_______________________________________________ Oxygen-user mailing list Oxygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
On 11/12/2010 8:43 AM, Adrian Buza wrote:
Lars,
Thank you for providing details for this problem.
It seems that content completion for type names was overlooked(besides the obvious xs:* types). I'm guessing "item()*" was manually added to that list of completions in that particular context. This problem needs to be addressed for types in general. I've logged this to our issue tracking tool and we'll fix it in a future version of Oxygen. I believe this will not make it in time for v12.1.
Regards, Adrian
Thank you. Lars
participants (3)
-
Adrian Buza -
Florent Georges -
Lars Huttar