Profiling/Conditional Text Filter: Customizing the list
Are you missing a feature? Request its implementation here.
Profiling/Conditional Text Filter: Customizing the list
Post by Anonymous1 »
Hello,
we have many different profilting/conditional text filters. However, only a few of them are relevant for each individual author. Currently, the text filter menu has two submenus to go through.
Feature request: Could you allow some sort of customizing for the menu so that only the important filters appear at the beginning of the menu.
I have attached the screenshot to show how our text filter menu currently looks like.
Ben
we have many different profilting/conditional text filters. However, only a few of them are relevant for each individual author. Currently, the text filter menu has two submenus to go through.
Feature request: Could you allow some sort of customizing for the menu so that only the important filters appear at the beginning of the menu.
I have attached the screenshot to show how our text filter menu currently looks like.
profiling-settings-list.png
Thanks,Ben
You do not have the required permissions to view the files attached to this post.
-
- Posts: 9434
- Joined: Fri Jul 09, 2004 5:18 pm
Re: Profiling/Conditional Text Filter: Customizing the list
Hi Ben,
Oxygen has no way of knowing which profiling filters are important for a certain technical writer.
The Preferences->"Editor / Edit Modes / Author / Profiling/Conditional Text / Attributes and Condition Sets" page can be saved at "Project options" so maybe you can have multiple project XPR files, one for each type of author, whenever a project file is opened in the Oxygen Project view a certain set of profiling condition sets saved in it would be used for editing.
If you have multiple main DITA Maps and multiple filters, but only certain combinations of DITA Map and filters make sense, maybe you can use our support for DITA OT project files:
A DITA OT project file defines contexts, each context having a pair of DITA Map and filter:
https://www.oxygenxml.com/doc/versions/ ... oject.html
And an older video presentation about DITA OT Project files:
https://www.youtube.com/watch?v=PZGhvhstOBU
DITA OT project files can be referenced in the Oxygen "Main Files" folder and the "Context" drop-down from the "DITA Maps Manager" view should show all combinations defined in the DITA OT project files.
Regards,
Radu
Oxygen has no way of knowing which profiling filters are important for a certain technical writer.
The Preferences->"Editor / Edit Modes / Author / Profiling/Conditional Text / Attributes and Condition Sets" page can be saved at "Project options" so maybe you can have multiple project XPR files, one for each type of author, whenever a project file is opened in the Oxygen Project view a certain set of profiling condition sets saved in it would be used for editing.
If you have multiple main DITA Maps and multiple filters, but only certain combinations of DITA Map and filters make sense, maybe you can use our support for DITA OT project files:
A DITA OT project file defines contexts, each context having a pair of DITA Map and filter:
https://www.oxygenxml.com/doc/versions/ ... oject.html
And an older video presentation about DITA OT Project files:
https://www.youtube.com/watch?v=PZGhvhstOBU
DITA OT project files can be referenced in the Oxygen "Main Files" folder and the "Context" drop-down from the "DITA Maps Manager" view should show all combinations defined in the DITA OT project files.
Regards,
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com
<oXygen/> XML Editor
http://www.oxygenxml.com
-
- Posts: 922
- Joined: Thu May 02, 2019 2:32 pm
Re: Profiling/Conditional Text Filter: Customizing the list
Post by chrispitude »
Hi B-E-N,
We are using Radu's suggested method of using project file <context> definitions to show only the applicable conditions for a map.
For us, this works quite well. We have 20-ish conditions and 80-ish books, and this has made conditional books much easier to work with.
The only drawback is that in the DITA Maps Manager, the context is "sticky" and stays even when you switch to another map. You must remember to update your context as you switch between maps. I wish that contexts were remembered map-by-map instead.
If you want, I can attach a .zip file with small Oxygen project showing how this feature works.
We are using Radu's suggested method of using project file <context> definitions to show only the applicable conditions for a map.
For us, this works quite well. We have 20-ish conditions and 80-ish books, and this has made conditional books much easier to work with.
The only drawback is that in the DITA Maps Manager, the context is "sticky" and stays even when you switch to another map. You must remember to update your context as you switch between maps. I wish that contexts were remembered map-by-map instead.
If you want, I can attach a .zip file with small Oxygen project showing how this feature works.
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