Re: Issue-#175 Display StdLink command in status line
Posted: Tue Oct 03, 2017 9:54 am
> 1 - In line 2 of Links & Targets it says "link resp. target". I don't like the abbreviation, so it would be better to say "link or respectively target". Actually it would be even better to simply say "link or target".
fixed
> 2 - The file name should be changed from "/Docu/LinksAndTargets" to something like "/Docu/Links-Dialog". The reason is so that it appears in a more suitable place when using the Repository Tool.
fixed.
I noticed that this also applies to the Tab dialog. TODO
3 - In line 3 replace "Text -> Show Marks." by Text -> Show Marks".
fixed
4 - Add a link to this Docu in "/Std/Docu/Sys-Map".
fixed
5 - "If you click the right mouse button on a link, a dialog is opened that allows for inspecting and editing the link's properties."
should be something like
"If you click the right mouse button on a link or target, a dialog is opened that allows for inspecting and editing the link or target's properties. This dialog is described more fully in <add link>".
Link added.
There is a problem with targets here.
The top part of the StdLinks docu deals only with links. Targets are introduced further below.
Mentioning targets here is too early unless the docu is reorganized completely, which I tried to avoid.
I have added a small refinement below where targets are introduced:
"... which are created in a similar way as link views."
changed to
"... which are created and handled in a similar way as link views."
6 - On the next line the phrase "The Target property contains ..." is confusing. Why call it a Target property for a link?
fixed. It is the "Link" property.
7 - A few lines later there is an explanation of using the menu option "Tools->Create Link", but this is no longer the preferred way of using this option.
Add:
<<A possibly simpler way to create this link is to enter, then select, the text "beep beep" (without the quotes), then use the menu option "Tools->Create Link"; then type into the "Link:" field "Dialog.Beep; Dialog.Beep" (without the quotes); then click "Apply". The blue coloring and underlining are applied automatically.>>.
fixed
8 - It would be helpful if it had a link to "/Std/Docu/Links".
This would mean to mix the user docu with the developer docu. IMHO, this should be avoided.
9 - It would be helpful to give examples of the placeholder "<pathAndName>". I am particularly thinking about both absolute and relative path examples, and of showing that the file name extension is not always (not often ?) required.
Examples are OK, I think. I have added some.
Replicating part of the docu of OpenBrowser etc. would be too much. Where does it stop?
See diffs at https://redmine.blackboxframework.org/p ... 8b8293a5d3.
- Josef
fixed
> 2 - The file name should be changed from "/Docu/LinksAndTargets" to something like "/Docu/Links-Dialog". The reason is so that it appears in a more suitable place when using the Repository Tool.
fixed.
I noticed that this also applies to the Tab dialog. TODO
3 - In line 3 replace "Text -> Show Marks." by Text -> Show Marks".
fixed
4 - Add a link to this Docu in "/Std/Docu/Sys-Map".
fixed
5 - "If you click the right mouse button on a link, a dialog is opened that allows for inspecting and editing the link's properties."
should be something like
"If you click the right mouse button on a link or target, a dialog is opened that allows for inspecting and editing the link or target's properties. This dialog is described more fully in <add link>".
Link added.
There is a problem with targets here.
The top part of the StdLinks docu deals only with links. Targets are introduced further below.
Mentioning targets here is too early unless the docu is reorganized completely, which I tried to avoid.
I have added a small refinement below where targets are introduced:
"... which are created in a similar way as link views."
changed to
"... which are created and handled in a similar way as link views."
6 - On the next line the phrase "The Target property contains ..." is confusing. Why call it a Target property for a link?
fixed. It is the "Link" property.
7 - A few lines later there is an explanation of using the menu option "Tools->Create Link", but this is no longer the preferred way of using this option.
Add:
<<A possibly simpler way to create this link is to enter, then select, the text "beep beep" (without the quotes), then use the menu option "Tools->Create Link"; then type into the "Link:" field "Dialog.Beep; Dialog.Beep" (without the quotes); then click "Apply". The blue coloring and underlining are applied automatically.>>.
fixed
8 - It would be helpful if it had a link to "/Std/Docu/Links".
This would mean to mix the user docu with the developer docu. IMHO, this should be avoided.
9 - It would be helpful to give examples of the placeholder "<pathAndName>". I am particularly thinking about both absolute and relative path examples, and of showing that the file name extension is not always (not often ?) required.
Examples are OK, I think. I have added some.
Replicating part of the docu of OpenBrowser etc. would be too much. Where does it stop?
See diffs at https://redmine.blackboxframework.org/p ... 8b8293a5d3.
- Josef