Re: [oXygen-user] Going from FrameMaker to oXygen / Outline View / Text duplicates
Hi Frank, I added an internal issue to consider adding a new setting based on what you want: EXM-52156 Outline - Setting to avoid showing text of element on ancestor element The purpose of the current behavior is to make it easier to figure out what text content is inside a certain node hierarchy without the need to expand nodes. So in this case I know what text is inside the element's structure without expanding it. Regards, Radu Radu Coravu Oxygen XML Editor On 1/9/23 18:47, Frank Dissinger wrote: Hi Jang, Just to be sure we are talking about the same thing: Current behavior: What I want is this: I see no point in the current behavior. Why are empty elements marked as "filled" elements in oXygen? *@SyncroSoft* Feature request : Can the current behavior of the Outline view be changed to show empty elements as empty? If the current behavior is required (for whichever reason...), I understand that I'd need to implement DITA contstraints. Can you be more specific about that? How would I do this with oXygen? Regards, Frank Am 09.01.2023 um 11:27 schrieb 4everJang: Hello Frank, About the last point in your missing features list: the DITA specs allow plain text as well as block elements like inside an . If you create constraints that disallow plain text (and inline elements) in the you should get rid of the extra Text indicators in oXygen’s author view. And I do suggest everyone to create constraints before starting to work with DITA, as the definitions in the so-called standard DITA packages allows almost everything and is not meant to be a useful subset of elements for anyone’s specific content domain. The first step in any useful DITA implementation is defining constraints and possibly specialisations. I often get the reply from newbie DITA users that they want to stick with standard DITA. Fact is that constraints, and even specialisations, do not take you away from the standard. DITA was intended to be customised, i.e. adapted to your particular content domain, so that it will become as useful as possible - without pushing you out of the standard. Any DITA tool should support constraints and specialisations (as long as you create them in the defined manner), otherwise they cannot claim to be DITA compliant at all. Good luck with the transition from FM to oXygen. *4everJang* *Amsterdam, Netherlands* On 9 Jan 2023, 10:37 +0100, Frank Dissinger , wrote: Hi Alan, Thank you for your reply. I fully agree with what you wrote about FM's Structure View. An excellent tool. It would be great if oXygen could enhance its Outline View and make it work in a similar way. I am especially missing the following features: * Allow users to place the cursor between tags, or at the beginning/end of the element contents, and indicate the position * Display attributes: Toggle between all/all with a value/none (no need to waste room on the screen for a separate Attributes window) * Expand/collapse complete tree of elements or attributes in one go (Shift-click) * Element content should not be repeated for empty wrapping elements, this is confusing (show it only once) For exmaple, for Text..., the "Text" is shown both for and . It should only be shown for . Can I add this as feature request? I have now switched to the oXygen Users Mailing List and will post any further oXygen-related issues there. Regards, Frank Am 04.01.2023 um 22:05 schrieb Alan Houser: Chiming in a bit late here. Longtime structured FrameMaker and oXygen user... *Frank mentions the FrameMaker structure view. IMO, this is the best and most distinctive part of the FrameMaker structured authoring interface. Easy access to any part of the document. Expand/collapse at any level of the document hierarchy; locally or globally (e.g. expand/collapse "this" section; expand/collapse all sections). Full navigation capabilities. Visual feedback (and shortcut control) over cursor location -- beginning, middle, or end of an element. Configurable and interactive attribute display.* * * *While most XML editors provide some sort of outline view, I've never seen one as full-featured and useful as the FrameMaker structure view.* I occasionally use the oXygen Outline View for quick navigation in larger XML documents. And the "folding" feature in the edit window to expand/collapse content. But these don't fully replace what one can do with the FrameMaker structure view. I think you will find that oXygen provides more and different features than Structured FrameMaker, many of which you will come to appreciate. I suggest (as you are doing) learning how to be most productive with the oXygen features and workflow. And be prepared to miss the FrameMaker structure view. 🙁 -Alan -- Alan Ho
[oXygen-user] Going from FrameMaker to oXygen / Outline View / Text duplicates
Hi Jang, Just to be sure we are talking about the same thing: Current behavior: What I want is this: I see no point in the current behavior. Why are empty elements marked as "filled" elements in oXygen? *@SyncroSoft* Feature request : Can the current behavior of the Outline view be changed to show empty elements as empty? If the current behavior is required (for whichever reason...), I understand that I'd need to implement DITA contstraints. Can you be more specific about that? How would I do this with oXygen? Regards, Frank Am 09.01.2023 um 11:27 schrieb 4everJang: Hello Frank, About the last point in your missing features list: the DITA specs allow plain text as well as block elements like inside an . If you create constraints that disallow plain text (and inline elements) in the you should get rid of the extra Text indicators in oXygen’s author view. And I do suggest everyone to create constraints before starting to work with DITA, as the definitions in the so-called standard DITA packages allows almost everything and is not meant to be a useful subset of elements for anyone’s specific content domain. The first step in any useful DITA implementation is defining constraints and possibly specialisations. I often get the reply from newbie DITA users that they want to stick with standard DITA. Fact is that constraints, and even specialisations, do not take you away from the standard. DITA was intended to be customised, i.e. adapted to your particular content domain, so that it will become as useful as possible - without pushing you out of the standard. Any DITA tool should support constraints and specialisations (as long as you create them in the defined manner), otherwise they cannot claim to be DITA compliant at all. Good luck with the transition from FM to oXygen. *4everJang* *Amsterdam, Netherlands* On 9 Jan 2023, 10:37 +0100, Frank Dissinger , wrote: Hi Alan, Thank you for your reply. I fully agree with what you wrote about FM's Structure View. An excellent tool. It would be great if oXygen could enhance its Outline View and make it work in a similar way. I am especially missing the following features: * Allow users to place the cursor between tags, or at the beginning/end of the element contents, and indicate the position * Display attributes: Toggle between all/all with a value/none (no need to waste room on the screen for a separate Attributes window) * Expand/collapse complete tree of elements or attributes in one go (Shift-click) * Element content should not be repeated for empty wrapping elements, this is confusing (show it only once) For exmaple, for Text..., the "Text" is shown both for and . It should only be shown for . Can I add this as feature request? I have now switched to the oXygen Users Mailing List and will post any further oXygen-related issues there. Regards, Frank Am 04.01.2023 um 22:05 schrieb Alan Houser: Chiming in a bit late here. Longtime structured FrameMaker and oXygen user... *Frank mentions the FrameMaker structure view. IMO, this is the best and most distinctive part of the FrameMaker structured authoring interface. Easy access to any part of the document. Expand/collapse at any level of the document hierarchy; locally or globally (e.g. expand/collapse "this" section; expand/collapse all sections). Full navigation capabilities. Visual feedback (and shortcut control) over cursor location -- beginning, middle, or end of an element. Configurable and interactive attribute display.* * * *While most XML editors provide some sort of outline view, I've never seen one as full-featured and useful as the FrameMaker structure view.* I occasionally use the oXygen Outline View for quick navigation in larger XML documents. And the "folding" feature in the edit window to expand/collapse content. But these don't fully replace what one can do with the FrameMaker structure view. I think you will find that oXygen provides more and different features than Structured FrameMaker, many of which you will come to appreciate. I suggest (as you are doing) learning how to be most productive with the oXygen features and workflow. And be prepared to miss the FrameMaker structure view. 🙁 -Alan -- Alan Houser Group Wellesley, Inc. Consultant and Trainer, Technical Publishing arh on Twitter 412-450-0532 On Dec 8, 2022, at 10:37 AM, Frank Dissinger wrote: Thank you, Chris Radu Stefan Thomas Yves for your replies, this valuable information and for offering me your help. I have already made some initial progress. I have successfully created a custom framework with my own CSS file and are getting my topic editor window panel look more and more the way I like (using the 'print-ready' display style).
