date:20230109

Re: [oXygen-user] Going from FrameMaker to oXygen -- @type not added automatically

2023-01-09 Thread Oxygen XML Editor Support (Radu Coravu)


Hi Frank,


So:


Good to know that the Type and Format attributes are neither required 
nor good practice. /.../
There is a problem which may occur if you are using the @type attribute 
on and off inconsistently.


So let's say you have a DITA Map which uses it a lot like:



  
and then you decide not to use it anymore on topicrefs, so you might end 
up with something like this:




  
      
  
So the reference to "concept.dita" no longer has @type set on it, but 
the parent task.dita has type set on it. And the DITA specification 
states that in such cases the @type attribute value cascades to the 
child element. So when publishing the DITA Map content is interpreted as:




  
      
  

which will trigger a publishing warning.

Oxygen's "Validate and check for completeness" action from the "DITA 
maps manager" view should report such problems.


But in general, once you decide not to use @type in the DITA map, you 
should actively remove the attribute from the DITA Map otherwise you end 
up with @type attribute values cascading on to topicrefs which no longer 
have the @type attribute set.



I right-clicked in the Editor window and selected /"/Insert > Insert 
New DITA Resource", then I selected a custom framework template.



Thanks, I added your details to the already opened issue.


Regards,

Radu

Radu Coravu
Oxygen XML Editor


On 1/9/23 17:02, Frank Dissinger wrote:


Hi Radu,


Thank you for this clarification. Good to know that the Type and 
Format attributes are neither required nor good practice. This makes 
life easier.


/I tested and indeed, if in the DITA Maps Manager I insert a
reference to an existing topic file, the attributes are
automatically added, but if I use for example the contextual
action "Append child->New" to create a topic and insert a
reference to it, then indeed the attributes are not set on the
topicref. Is this close to how you are doing things on your side?/

I right-clicked in the Editor window and selected /"/Insert > Insert 
New DITA Resource", then I selected a custom framework template.


/
/

Regards,

Frank/

/


Am 04.01.2023 um 06:57 schrieb Oxygen XML Editor Support (Radu Coravu):


Hi Frank,


Please see some remarks below:


I understand that the "type" and "format" attributes are required or 
at least a good practice for "topicref" elements.



They are not required and they are not a best practice either.

From what I've experienced along these years, most end users who want 
these attributes to be added automatically are usually the ones 
migrating from Framemaker or using both Oxygen and Framemaker on the 
same set of DITA files.


My general best practice for these attributes would be:


1) For the "type" attribute, never set it on any link or topicref as 
the publishing engine will infer it from the target.


2) For the "format" attribute, Oxygen by default sets it on 
references to DITA Maps and non-DITA topics, but when referencing 
DITA topics, the @format attribute is not set automatically as it's 
default value when not set is "dita".





When I insert a new dita resource into a ditamap (i.e. a new topic 
or map which I create and insert in one go), oXygen should add these 
attributes automatically. I have set the options under "Options > 
Preferences > DITA > Maps" accordingly.



However, only "format" attributes are set, "type" attributes are not 
set although I have checked both options.
Checking those "Format" and "Type" checkboxes in the "Options > 
Preferences > DITA > Maps" preferences page should work...


I tested and indeed, if in the DITA Maps Manager I insert a reference 
to an existing topic file, the attributes are automatically added, 
but if I use for example the contextual action "Append child->New" to 
create a topic and insert a reference to it, then indeed the 
attributes are not set on the topicref. Is this close to how you are 
doing things on your side?


I added an internal issue to look into fixing this problem on our 
side, adding the issue ID below for future reference:



    EXM-52131 DITA Maps Manager creating new topic does not 
automatically add type and format attributes to topicref



Hope this helps.


Regards,

Radu

Radu Coravu
Oxygen XML Editor


On 1/3/23 21:08, Frank Dissinger wrote:


Hi list,


I understand that the "type" and "format" attributes are required or 
at least a good practice for "topicref" elements.



When I insert a new dita resource into a ditamap (i.e. a new topic 
or map which I create and insert in one go), oXygen should add these 
attributes automatically. I have set the options under "Options > 
Preferences > DITA > Maps" accordingly.



However, only "format" attributes are set, "type" attributes are not 
set although I have checked both options.



Is this a bug or am I missing something?


I use oXygen V25.


Regards,


Frank

--

*Frank Dissinger*

Documentation Manager

Re: [oXygen-user] Going from FrameMaker to oXygen / Outline View / Text duplicates

2023-01-09 Thread Oxygen XML Editor Support (Radu Coravu)


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

Re: [oXygen-user] Git addon on M1 Mac?

2023-01-09 Thread Oxygen XML Editor Support (Radu Coravu)


Hello Scott,

I'm using Oxygen 25 with the Git add-on on an M1 Mac every day and I 
don't seem to have any issues with it.


Can you maybe send us some details about the error? Maybe a screenshot?

In addition you can also use the Oxygen main menu "Help->Report problem" 
and report a problem to us, we will receive lots of details about your 
current Oxygen installation, this might help us debug the problem further.


Regards,

Radu

Radu Coravu
Oxygen XML Editor

On 1/10/23 04:00, Scott Prentice wrote:


Hi...

I'm seeing that when you install the Git addon, on Oxygen 25 installed 
on an M1 Mac, when you restart Oxygen, it generates an error and can't 
start the editor. This has been verified on two different systems. It 
works fine on a non-M1 Mac.


Is anyone else seeing this?

Oxygen .. is this something you're aware of?

Thanks!

...scott



___
oXygen-user mailing list
oXygen-user@oxygenxml.com
https://www.oxygenxml.com/mailman/listinfo/oxygen-user
___
oXygen-user mailing list
oXygen-user@oxygenxml.com
https://www.oxygenxml.com/mailman/listinfo/oxygen-user

[oXygen-user] Going from FrameMaker to oXygen -- Print-ready/Outline view issues

2023-01-09 Thread Frank Dissinger


Hi Kris,


Thank you for your reply.


I fully agree with the requirements you describe.


In FrameMaker I was used to work in WYSIWYG view with no tags displayed. 
The Structure View and the formatting styles in the Editor window gave 
me enough information about the DITA tags and structure. I used the 
Elements window to insert or wrap elements and edited Attributes using 
the Structure View or a DITA-FMx dialog.



When I now view my DITA topics in oXygen I would like to see them in a 
similar way just because otherwise I wouldn't be sure if it is really 
the same document. Sounds strange perhaps, but it is indeed extremely 
confusing to me to see something that seems to be different. Perhaps 
after some time, when I am conversant with oXygen, I may have more 
confidence in other views...



So in oXygen I prefer the "No tags" view. With this there are still lots 
of icons (for opening link targets, expand/collapse sections...) and 
additional text ("Short description", "Result", ...) which I would 
prefer to hide. Most of this can be done using the "Print-ready" style 
and lots of CSS code which I take from the CSS Inspector window and adapt.



However, this means that I would have to rely on the Outline view, the 
Attributes window and the breadcrumbs to see the structure. These tools 
do not give me the same information, convenience and capabilities that I 
am used in FrameMaker. I therefore thought it could be a workaround to 
quickly toggle my preferred view ("Print ready") and "Full tags" (or 
"Full tags with attributs") using a keyboard shortcut. However, there 
are no shortcuts for styles.



But I discovered that you can define keyboard shortcuts for "No tags", 
"Full tags", etc. And Radu gave me CSS code that creates a button in 
every topic that toggles between "No tags" and the last tags view chosen 
for the topic. I was able to get rid of some texts like "Short 
description" (which I indicate using a color) and the like using some 
more CSS code. The extra icons are still there, but they do not take up 
much room so I can live with them (and they are usful).



Best regards,


Frank



Am 04.01.2023 um 06:42 schrieb Kristen James Eberlein:


Hi, Frank.

I have not used FrameMaker for almost two decades, so I cannot be of 
much help in your quest to “set up the Author mode in a way which 
comes close to what I was used in FrameMaker”. Whether or not you can 
do that, I truly don’t know.


It might be the case that it would be helpful for you to state your 
needs as functional requirements – While Oxygen might not offer the 
same authoring nuances/interface as FrameMaker, if it can be done in 
XML, Oxygen offers a way to do it!


For example, here are the requirements that I inferred from your e-mail:

  * As an author, I want to have a WYSIWYG interface that looks
similar to how content is rendered for my company. (Easy to do
with CSS and an Oxygen framework.)
  * As an author, I want to easily navigate in a lengthy XML document.
(This is what the Outline view is optimized for, to enable you to
locate a specific element rapidly.)
  * As an author, I want to have a WYSIWYG view where I can easily
view the underlying structure, both elements and attributes. (For
me, here is where I use the authoring view with full tags and
attributes turned on.)

Some of this, of course, might depend on what you mean by WYSWYG … 
Does WYSIWYG encompass the Oxygen Author view with “full tags and 
attributes”? Or are you primarily interested in the “no tags” view? If 
the latter, you can view the structure by looking at the breadcrumbs 
that are displayed at the top of the window, under the topic title, 
and the attributes by keeping the “Attributes” view open.


I think all Oxygen users have slightly different preferences, and they 
certainly can also be affected by whether one has an external monitor 
or is simply working within the confines of a small laptop or tablet 
screen.


Change is hard. Inevitably, when you switch tools, I think you run 
into a need to shift at least a little of your habits and preferences.


Best,

Kris

Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Owner, Eberlein Consulting LLC
k...@eberleinconsulting.com

Skype: kriseberlein; voice: +1 (919) 622-1501

*From:* oXygen-user  *On Behalf Of 
*Frank Dissinger

*Sent:* Tuesday, January 3, 2023 12:36 PM
*To:* Oxygen User Mailing List 
*Subject:* [oXygen-user] Going from FrameMaker to oXygen -- 
Print-ready/Outline view issues


Hi all,

This is my first posting to this list.

I am in the process of switching from FrameMaker V11 + DITA-FMx to 
oXygen V25 as my DITA editing tool. I have been using oXyen for quite 
a while as a transformation engine, but not as an editor. So in this 
respect I am still at the bottom of the learning curve.


I'd like to set up the Author mode in a way which comes close to what 
I was used in

[oXygen-user] Going from FrameMaker to oXygen / Outline View / Text duplicates

2023-01-09 Thread Frank Dissinger


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).

[oXygen-user] Git addon on M1 Mac?

2023-01-09 Thread Scott Prentice


Hi...

I'm seeing that when you install the Git addon, on Oxygen 25 installed 
on an M1 Mac, when you restart Oxygen, it generates an error and can't 
start the editor. This has been verified on two different systems. It 
works fine on a non-M1 Mac.


Is anyone else seeing this?

Oxygen .. is this something you're aware of?

Thanks!

...scott


___
oXygen-user mailing list
oXygen-user@oxygenxml.com
https://www.oxygenxml.com/mailman/listinfo/oxygen-user

[oXygen-user] Going from FrameMaker to oXygen -- @type not added automatically

2023-01-09 Thread Frank Dissinger


Hi Radu,


Thank you for this clarification. Good to know that the Type and Format 
attributes are neither required nor good practice. This makes life easier.


   /I tested and indeed, if in the DITA Maps Manager I insert a
   reference to an existing topic file, the attributes are
   automatically added, but if I use for example the contextual action
   "Append child->New" to create a topic and insert a reference to it,
   then indeed the attributes are not set on the topicref. Is this
   close to how you are doing things on your side?/

I right-clicked in the Editor window and selected /"/Insert > Insert New 
DITA Resource", then I selected a custom framework template.


/
/

Regards,

Frank/

/


Am 04.01.2023 um 06:57 schrieb Oxygen XML Editor Support (Radu Coravu):


Hi Frank,


Please see some remarks below:


I understand that the "type" and "format" attributes are required or 
at least a good practice for "topicref" elements.



They are not required and they are not a best practice either.

From what I've experienced along these years, most end users who want 
these attributes to be added automatically are usually the ones 
migrating from Framemaker or using both Oxygen and Framemaker on the 
same set of DITA files.


My general best practice for these attributes would be:


1) For the "type" attribute, never set it on any link or topicref as 
the publishing engine will infer it from the target.


2) For the "format" attribute, Oxygen by default sets it on references 
to DITA Maps and non-DITA topics, but when referencing DITA topics, 
the @format attribute is not set automatically as it's default value 
when not set is "dita".





When I insert a new dita resource into a ditamap (i.e. a new topic or 
map which I create and insert in one go), oXygen should add these 
attributes automatically. I have set the options under "Options > 
Preferences > DITA > Maps" accordingly.



However, only "format" attributes are set, "type" attributes are not 
set although I have checked both options.
Checking those "Format" and "Type" checkboxes in the "Options > 
Preferences > DITA > Maps" preferences page should work...


I tested and indeed, if in the DITA Maps Manager I insert a reference 
to an existing topic file, the attributes are automatically added, but 
if I use for example the contextual action "Append child->New" to 
create a topic and insert a reference to it, then indeed the 
attributes are not set on the topicref. Is this close to how you are 
doing things on your side?


I added an internal issue to look into fixing this problem on our 
side, adding the issue ID below for future reference:



    EXM-52131 DITA Maps Manager creating new topic does not 
automatically add type and format attributes to topicref



Hope this helps.


Regards,

Radu

Radu Coravu
Oxygen XML Editor


On 1/3/23 21:08, Frank Dissinger wrote:


Hi list,


I understand that the "type" and "format" attributes are required or 
at least a good practice for "topicref" elements.



When I insert a new dita resource into a ditamap (i.e. a new topic or 
map which I create and insert in one go), oXygen should add these 
attributes automatically. I have set the options under "Options > 
Preferences > DITA > Maps" accordingly.



However, only "format" attributes are set, "type" attributes are not 
set although I have checked both options.



Is this a bug or am I missing something?


I use oXygen V25.


Regards,


Frank

--

*Frank Dissinger*

Documentation Manager



*CGS Publishing Technologies International GmbH*

*Email *frank.dissin...@cgs-oris.com | *Web* www.cgs-oris.com 



*Address* Kettelerstr. 24 | D-63512 Hainburg | Germany

*Phone* +49 6182 9626-27 | *Fax* +49 6182 9626-99

*Commercial register* Offenbach, HRB no. 21495

*Managing directors* Bernd Rückert, Christoph Thommessen


https://www.cgs-oris.com/Signatur.png ___
oXygen-user mailing list
oXygen-user@oxygenxml.com
https://www.oxygenxml.com/mailman/listinfo/oxygen-user

[oXygen-user] Going from FrameMaker to oXygen -- Print-ready/Outline view issues

2023-01-09 Thread Frank Dissinger


Thank you, Radu, for the CSS code.


I have successfully implemented this button and it is a good workaround 
until a keyboard shortcut is available.



I have made it to always stick at the top right of the Editor window 
using the CSS property "position: fixed".



Unfortunately, this CSS code does not work with the "Print ready" style, 
only when it is disabled. As a result, I had to adjust a few more CSS 
styles to reimplement the visual representation that I wanted.



Regards,


Frank



Am 04.01.2023 um 07:54 schrieb Oxygen XML Editor Support (Radu Coravu):


Hi Frank,


About this specific request:


So I thought maybe I could perhaps quickly toggle the "Print-ready" 
style on and off to see the tags and better find the correct cursor 
position. Can I create a keyboard shortcut for doing this?



We do not yet have a means to set a certain keyboard shortcut for 
applying a CSS layer, we have an internal issue for this, I added your 
contact details to it and I'm pasting the issue ID below for future 
reference:



    EXM-22482 Assign hot keys for the alternate styles (CSS API)


There are other ways in which someone could for example create a 
custom Author action which sets a certain pseudo class on an element 
and then the CSS selectors can use that pseudo class to enable or 
disable certain properties. For example with the "custom.css" file I'm 
attaching I added a button directly in the Author visual editor and 
when the button is clicked, a certain CSS pseudo class is set on the 
root element and the tags are shown or hidden based on it.



Regards,

Radu

Radu Coravu
Oxygen XML Editor
On 1/3/23 19:36, Frank Dissinger wrote:


Hi all,


This is my first posting to this list.


I am in the process of switching from FrameMaker V11 + DITA-FMx to 
oXygen V25 as my DITA editing tool. I have been using oXyen for quite 
a while as a transformation engine, but not as an editor. So in this 
respect I am still at the bottom of the learning curve.



I'd like to set up the Author mode in a way which comes close to what 
I was used in FrameMaker. I mainly worked in WYSIWYG view and with 
the Structure View, Elements and Attributes windows.



I have spent some effort on making oXygen's "Print-ready" view for 
the Editor window (in Author mode) look as WYSIWYG-ish as possible, 
with custom CSS styles that give me visual clues to the underlying 
XML structure. I then thought that I could use oXygen's Outline view 
in a similar way as FM's Structure View, but I feel quite lost in 
this window.


  * It does not allow me to position the cursor between the elements
  * It shows only a single attribute, not all attributes that are set
  * It shows only the attribute value, not the name
  * ...

I therefore find it hard to see the XML structure in the Outline view 
and to place the cursor precisely when I want to insert new elements.



So I thought maybe I could perhaps quickly toggle the "Print-ready" 
style on and off to see the tags and better find the correct cursor 
position. Can I create a keyboard shortcut for doing this?



Thank you.


Regards,


Frank


--

*Frank Dissinger*

Documentation Manager



*CGS Publishing Technologies International GmbH*

*Email *frank.dissin...@cgs-oris.com | *Web* www.cgs-oris.com 



*Address* Kettelerstr. 24 | D-63512 Hainburg | Germany

*Phone* +49 6182 9626-27 | *Fax* +49 6182 9626-99

*Commercial register* Offenbach, HRB no. 21495

*Managing directors* Bernd Rückert, Christoph Thommessen


https://www.cgs-oris.com/Signatur.png 



___
oXygen-user mailing list
oXygen-user@oxygenxml.com
https://www.oxygenxml.com/mailman/listinfo/oxygen-user


___
oXygen-user mailing list
oXygen-user@oxygenxml.com
https://www.oxygenxml.com/mailman/listinfo/oxygen-user

--

*Frank Dissinger*

Documentation Manager



*CGS Publishing Technologies International GmbH*

*Email *frank.dissin...@cgs-oris.com | *Web* www.cgs-oris.com 



*Address* Kettelerstr. 24 | D-63512 Hainburg | Germany

*Phone* +49 6182 9626-27 | *Fax* +49 6182 9626-99

*Commercial register* Offenbach, HRB no. 21495

*Managing directors* Bernd Rückert, Christoph Thommessen


https://www.cgs-oris.com/Signatur.png ___
oXygen-user mailing list
oXygen-user@oxygenxml.com
https://www.oxygenxml.com/mailman/listinfo/oxygen-user

Re: [oXygen-user] Going from FrameMaker to oXygen / FM Structure View vs. oXy Outline View / Feature request

2023-01-09 Thread Radu Coravu


Hi Frank,


We have an internal issue about making various improvements to our 
Outline side view and I added your comments to it.


Adding below a reference to the internal issue ID for future reference:


    EXM-44795 Improve Author Outline view to allow editing attributes, 
placing caret



Regards,

Radu

Radu Coravu
Oxygen XML Editor


On 1/9/23 11:37, 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).


I'll try to dig a bit deeper into this matter and will collect the 
questions and issues as I get on with this. I'll then come back to you.


Best regards,

Frank


Am 06.12.2022 um 17:42 schrieb Frank Dissinger:

Hi all,

Are there any passionate long-term structured FrameMaker users who 
have changed to oXygen as a DITA editor? Has anybody tried to set 
up the oXygen authoring environment as close as possible to 
FrameMaker's WYSIWYG view? Or at least in a way that makes the 
switch as painless as possible for a FrameMaker user?


I've been using FrameMaker V11+DITA-FMx as a DITA editor for many 
years -- until recently also as a PDF transformation engine, which 
I have now replaced with MiramoPDF. I have used oXygen for a few 
years only and mostly as a transformation engine. With FM I am 
stuck with an old DITA implementation and the DITA-FMx plug-in is 
not developed any further. This is why I would like to use oXygen 
as a DITA editor instead. But I find it very hard to make the 
switch: The way DITA maps, topics, tags, structures... are 
presented is so different and I haven't the time to learn oXygen 
properly and in full detail. It's such a powerful tool with tons of 
features. So I thought there may be someone who can help me getting 
started -- at least with setting up the user interface and 
authoring environment.


A few examples of things I am struggling with right away when I 
look at how oXygen presents my DITA files:


  * It seems that a DITA map loads all the referenced submaps and
displays all of these

[oXygen-user] Going from FrameMaker to oXygen / FM Structure View vs. oXy Outline View / Feature request

2023-01-09 Thread Frank Dissinger


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).


I'll try to dig a bit deeper into this matter and will collect the 
questions and issues as I get on with this. I'll then come back to you.


Best regards,

Frank


Am 06.12.2022 um 17:42 schrieb Frank Dissinger:

Hi all,

Are there any passionate long-term structured FrameMaker users who 
have changed to oXygen as a DITA editor? Has anybody tried to set up 
the oXygen authoring environment as close as possible to 
FrameMaker's WYSIWYG view? Or at least in a way that makes the 
switch as painless as possible for a FrameMaker user?


I've been using FrameMaker V11+DITA-FMx as a DITA editor for many 
years -- until recently also as a PDF transformation engine, which I 
have now replaced with MiramoPDF. I have used oXygen for a few years 
only and mostly as a transformation engine. With FM I am stuck with 
an old DITA implementation and the DITA-FMx plug-in is not developed 
any further. This is why I would like to use oXygen as a DITA editor 
instead. But I find it very hard to make the switch: The way DITA 
maps, topics, tags, structures... are presented is so different and 
I haven't the time to learn oXygen properly and in full detail. It's 
such a powerful tool with tons of features. So I thought there may 
be someone who can help me getting started -- at least with setting 
up the user interface and authoring environment.


A few examples of things I am struggling with right away when I look 
at how oXygen presents my DITA files:


  * It seems that a DITA map loads all the referenced submaps and
displays all of these maps in a single window panel (as if this
was a single file). In FM I see only the references and open the
submaps as separate files by double-clicking on them.
  * I feel lost in these maps. There are lots of big fonts, frames,
colored backgrounds, icons... Can I customize the appearance?
For example, by defining CSS-like styles for the DITA elements
displayed on the screen?

Re: [oXygen-user] Going from FrameMaker to oXygen -- @type not added automatically

Re: [oXygen-user] Going from FrameMaker to oXygen / Outline View / Text duplicates

Re: [oXygen-user] Git addon on M1 Mac?

[oXygen-user] Going from FrameMaker to oXygen -- Print-ready/Outline view issues

[oXygen-user] Going from FrameMaker to oXygen / Outline View / Text duplicates

[oXygen-user] Git addon on M1 Mac?

[oXygen-user] Going from FrameMaker to oXygen -- @type not added automatically

[oXygen-user] Going from FrameMaker to oXygen -- Print-ready/Outline view issues

Re: [oXygen-user] Going from FrameMaker to oXygen / FM Structure View vs. oXy Outline View / Feature request

[oXygen-user] Going from FrameMaker to oXygen / FM Structure View vs. oXy Outline View / Feature request

10 matches

Site Navigation

Mail list logo

Footer information