XSLT template inspector
Are you missing a feature? Request its implementation here.
-
- Posts: 280
- Joined: Thu Nov 28, 2013 9:32 am
- Location: Hamburg/Germany
- Contact:
XSLT template inspector
Hi,
this is more a vague idea than a request, but it might be usefull...
While the template pattern mechanism of XSLT is very comfortable to extend it has the same deficit as CSS has: On large projects it is difficult to maintain the overview which template will match (first) on a specific node. For instance on the PDF transformation for DITA-OT you can spend quite some time on finding the right template you need to overwrite.
For CSS you have already provided the CSS inspector which helps a lot when modifying your stylesheets. And I could imagine this would also be the case for XSLT.
So the idea would be that you can place the cursor on some XML node and have an XSLT-file (or project) selected. Now oXygen will display for each mode (e.g. in different tabs) the list of templates that would match this node - ordered by their priority, considering includes and imports, default priority, default templates, ...
As I said: just an uidea you might think about.
Patrik
this is more a vague idea than a request, but it might be usefull...
While the template pattern mechanism of XSLT is very comfortable to extend it has the same deficit as CSS has: On large projects it is difficult to maintain the overview which template will match (first) on a specific node. For instance on the PDF transformation for DITA-OT you can spend quite some time on finding the right template you need to overwrite.
For CSS you have already provided the CSS inspector which helps a lot when modifying your stylesheets. And I could imagine this would also be the case for XSLT.
So the idea would be that you can place the cursor on some XML node and have an XSLT-file (or project) selected. Now oXygen will display for each mode (e.g. in different tabs) the list of templates that would match this node - ordered by their priority, considering includes and imports, default priority, default templates, ...
As I said: just an uidea you might think about.
Patrik
-
- Posts: 9434
- Joined: Fri Jul 09, 2004 5:18 pm
Re: XSLT template inspector
Hi Patrik,
We'll consider this although XSLT is complex and this can probably be done only if we run a transformation to the end and somehow retain all places in the XSLT where the XML element was processed.
The closest we have to this if you use our XSLT debugger and run the debugger to end is that you can move the caret in the "Output" tab and see which parts of XML and XSLT were used to generate it.
Regards,
Radu
We'll consider this although XSLT is complex and this can probably be done only if we run a transformation to the end and somehow retain all places in the XSLT where the XML element was processed.
The closest we have to this if you use our XSLT debugger and run the debugger to end is that you can move the caret in the "Output" tab and see which parts of XML and XSLT were used to generate it.
Regards,
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com
<oXygen/> XML Editor
http://www.oxygenxml.com
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service