Scenario tree
Are you missing a feature? Request its implementation here.
-
- Posts: 4
- Joined: Thu Oct 08, 2015 11:01 am
Scenario tree
Hello!
I wonder if there a feature in xml editor that allows to organize scenarios (into folders for example). If there isn't, then maybe there is some workaround that allows to do so? In any case it would be nice to add such option in "Transformation scenarios" window and even more greater to allow to bind xslt files to it. It is more logical to make xsl transformation as part of scenario than otherwise.
I wonder if there a feature in xml editor that allows to organize scenarios (into folders for example). If there isn't, then maybe there is some workaround that allows to do so? In any case it would be nice to add such option in "Transformation scenarios" window and even more greater to allow to bind xslt files to it. It is more logical to make xsl transformation as part of scenario than otherwise.
-
- Posts: 2879
- Joined: Tue May 17, 2005 4:01 pm
Re: Scenario tree
Hi,
It's not possible to create folders in the transformation scenarios view/dialog. A simple workaround is to use a certain prefix in the name of the scenarios so that they get grouped together.
e.g.
MY DITA Map PDF
MY DITA Map WebHelp
Not sure what you mean by "bind xslt files to it". It's the transformation scenario that is associated with the currently edited file (XML or XSL), not the other way around.
Note that there are two types of XML+XSLT transformation scenarios, one where the XML is the current file (XML transformation with XSLT) and another where the XSLT is the current file (XSLT transformation).
If you want the XSLT file to be associated with the scenario, open the XSLT and from its point of view create an XSLT transformation scenario.
Regards,
Adrian
It's not possible to create folders in the transformation scenarios view/dialog. A simple workaround is to use a certain prefix in the name of the scenarios so that they get grouped together.
e.g.
MY DITA Map PDF
MY DITA Map WebHelp
Not sure what you mean by "bind xslt files to it". It's the transformation scenario that is associated with the currently edited file (XML or XSL), not the other way around.
Note that there are two types of XML+XSLT transformation scenarios, one where the XML is the current file (XML transformation with XSLT) and another where the XSLT is the current file (XSLT transformation).
If you want the XSLT file to be associated with the scenario, open the XSLT and from its point of view create an XSLT transformation scenario.
Regards,
Adrian
Adrian Buza
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com
-
- Posts: 4
- Joined: Thu Oct 08, 2015 11:01 am
Re: Scenario tree
I have about 3000 scenarios (organized in my company's web back office) and only 800 xsl stylesheets, so the only workaround I can think of is to create symlinks on xsl files(on my local PC) and bind to them different scenarios (works in Linux). But this is sometimes pain as 1 xsl file can be bind to 20 scenarious and since I haven't write a script that translates DB data to project I do it by hand.
-
- Posts: 2879
- Joined: Tue May 17, 2005 4:01 pm
Re: Scenario tree
Hi,
3000 scenarios seems excessive. Maybe separate the scenarios in several Oxygen projects.
To be honest, we never even considered thousands of scenarios within the same project.
Other than using the filter search at the top, I don't have a solution for locating a scenario in such a large scenario base.
Regards,
Adrian
3000 scenarios seems excessive. Maybe separate the scenarios in several Oxygen projects.
To be honest, we never even considered thousands of scenarios within the same project.
Other than using the filter search at the top, I don't have a solution for locating a scenario in such a large scenario base.
Regards,
Adrian
Adrian Buza
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
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