Page 1 of 1

XSLT 2.0 support?

Posted: Sun Dec 05, 2004 4:40 am
by Dimitre
Does Oxygen support XSLT/XPath 2.0 and to what extent?

I couldn't find any mentioning of this on your site.


Cheers,
Dimitre.

dnovatchev@gmail.com

Posted: Sun Dec 05, 2004 10:16 am
by george
Hi Dimitre,

Oxygen uses the latest SaxonB (8.1.1) for XSLT 2.0 and XPath 2.0 support.
It automatcally detects SaxonSA and presents it in the list of available XSLT 2.0 processors (in the preferences for stylesheet validation and in the transformation scenarios) if it is placed in the oXygen lib directory.
SaxonB 8.1.1 is available also for debugging in the XSLT Debugger. All debugger fuctionality is available for SaxonB 8.1.1 including the mapping from the output result to the source and stylesheet locations.

Best Regards,
George

Posted: Sun Dec 05, 2004 2:25 pm
by dimitre
Hi George,

george wrote:Hi Dimitre,

Oxygen uses the latest SaxonB (8.1.1) for XSLT 2.0 and XPath 2.0 support.
It automatcally detects SaxonSA and presents it in the list of available XSLT 2.0 processors (in the preferences for stylesheet validation and in the transformation scenarios) if it is placed in the oXygen lib directory.
SaxonB 8.1.1 is available also for debugging in the XSLT Debugger. All debugger fuctionality is available for SaxonB 8.1.1 including the mapping from the output result to the source and stylesheet locations.

Best Regards,
George
This is fantastic. You may be losing many customers by not providing this information on your front web page.

Does Oxygen also provide XSLT2.0/XPath 2.0 syntax colouring and intellisense?

I am looking for a good XSLT 2.0 .


Cheers,
Dimitre.

Posted: Sun Dec 05, 2004 5:57 pm
by george
Hi Dimitre,

The XSLT 2.0 and XPath 2.0 support is mentioned on the front page in the section that covers the new additions in version 5.0:
http://www.oxygenxml.com/index.html#new-version

If the stylesheet version is set to 2.0 then Oxygen will automatically switch to the XSLT 2.0 schema for content completion. All the XSLT 2.0 elements and attributes were annotated with their description from the spec and you will be able to see that both in the model view and in the content completion documentation window when you edit the stylesheet.

There is no special syntax coloring for XSLT, Oxygen uses the same coloring as for XML. Also there is no content completion inside XPath but we plan to add this.

The content completion was enhanced in 5.0 to offer information extracted from the edited document. For instance it will give you all the template names when you edit a xsl:call-template/@name value.

Best Regards,
George

Posted: Sun Dec 05, 2004 10:50 pm
by dimitre
george wrote:Hi Dimitre,

The XSLT 2.0 and XPath 2.0 support is mentioned on the front page in the section that covers the new additions in version 5.0:
http://www.oxygenxml.com/index.html#new-version

If the stylesheet version is set to 2.0 then Oxygen will automatically switch to the XSLT 2.0 schema for content completion. All the XSLT 2.0 elements and attributes were annotated with their description from the spec and you will be able to see that both in the model view and in the content completion documentation window when you edit the stylesheet.

There is no special syntax coloring for XSLT, Oxygen uses the same coloring as for XML. Also there is no content completion inside XPath but we plan to add this.

The content completion was enhanced in 5.0 to offer information extracted from the edited document. For instance it will give you all the template names when you edit a xsl:call-template/@name value.

Best Regards,
George
That's really nice, but the viewers have to scroll one page down in order to reach the mentioning of the XSLT 2.0 support -- most people (like me) are lazy and never go beyond the first page -- a fact also well known and discussed in the area of presenting search engines results.

Therefore, the most important and sellable features are best put on the first ever screen that will be displayed to the viewer.

As for content completion, there are more possibilities -- e.g. prompting the names of all parameters in xsl:with-param, or the name for an xsl:template from all names used on xsl:call-template, that do not have a xsl:template defined with that name.

Does the debugger step through in an imported stylesheet module?


Cheers,
Dimitre.

Posted: Mon Dec 06, 2004 12:10 am
by george
Hi Dimitre,

Yes, the debugger goes inside imported stylesheets. Oxygen is able to work with complex stylesheets, it was tested without problems with DocBook. As far as I know it is the only XSLT Debugger that can handle DocBook.

We will consider both impoving the content completion as you suggested and also making more visible the XSLT 2.0 and XPath 2.0 support.

Best Regards,
George

Posted: Mon Dec 06, 2004 12:32 pm
by dimitre
george wrote:Hi Dimitre,

Yes, the debugger goes inside imported stylesheets. Oxygen is able to work with complex stylesheets, it was tested without problems with DocBook. As far as I know it is the only XSLT Debugger that can handle DocBook.

We will consider both impoving the content completion as you suggested and also making more visible the XSLT 2.0 and XPath 2.0 support.

Best Regards,
George
Hi George,

I downloaded the trial version and hope will have time to play with it.

I will certainly buy Oxygen, if I like it.

Keep up the good work,

Cheers,
Dimitre.