Posted 17 years ago
by John Carpenter
Hello,
Should SyntaxEditor be able to work with XSL files? I seem to have two problems at the moment:
1. I have an XSLT schema but obviously it won't know what my end result schema is going to be. Can I merge 2 schemas together? I know I can load more than one in, but the intellisense only appears to work at the root level. EG if I load xhtml.xsd and my xslt.xsd together I don't get any XHTML intellisense appearing in an xsl:template.
2. This may be related to 1. and may not be a bug, but if I am within an XHTML element, I lose the "xsl" prefix. Eg:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:msxsl="urn:schemas-microsoft-com:xslt" version="1.0">
<xsl:template match="/">
<table>
</table>
</xsl:template>
</xsl:stylesheet>
In this example, when my cursor is between the 2 table tags, intellisense pops up but doesn't display the "xsl:" prefix (e.g. it shows "value-of") whereas if my cursor is anywhere else it displays the "xsl" prefix. This could be my schema though.
I get the impression that SyntaxEditor is extensible enough to support whatever I want to do but I'm not really sure where to start and don't want to rewrite something that already exists. (Also if I need to write my own XSL handler I may not need to buy the web extensions pack)
Sorry to ask a bit of a newbie question... I'm still in my evaluation period (just!) and want to make sure it will fully support XSL before splashing out. I'm not able to devote a huge amount of time to working with it.
John
Should SyntaxEditor be able to work with XSL files? I seem to have two problems at the moment:
1. I have an XSLT schema but obviously it won't know what my end result schema is going to be. Can I merge 2 schemas together? I know I can load more than one in, but the intellisense only appears to work at the root level. EG if I load xhtml.xsd and my xslt.xsd together I don't get any XHTML intellisense appearing in an xsl:template.
2. This may be related to 1. and may not be a bug, but if I am within an XHTML element, I lose the "xsl" prefix. Eg:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:msxsl="urn:schemas-microsoft-com:xslt" version="1.0">
<xsl:template match="/">
<table>
</table>
</xsl:template>
</xsl:stylesheet>
In this example, when my cursor is between the 2 table tags, intellisense pops up but doesn't display the "xsl:" prefix (e.g. it shows "value-of") whereas if my cursor is anywhere else it displays the "xsl" prefix. This could be my schema though.
I get the impression that SyntaxEditor is extensible enough to support whatever I want to do but I'm not really sure where to start and don't want to rewrite something that already exists. (Also if I need to write my own XSL handler I may not need to buy the web extensions pack)
Sorry to ask a bit of a newbie question... I'm still in my evaluation period (just!) and want to make sure it will fully support XSL before splashing out. I'm not able to devote a huge amount of time to working with it.
John