Daniel Lewis wrote:
Jean Hollis Weber wrote:
Daniel Lewis wrote:
OK, I have received the information I needed for "context" vs
"pop-up". So I had changed all of them from pop-up, but I will be
changing them all back before completing my review. Although
consistency would point to using "context", beginners would more
easily understand "pop-up". So understandability is the most
important factor for them.
The following is found on page 34:
1.
To change the font color for the headings: (this line is numbered
3 rather than the 1 shown here.)
1.
Right-click on a heading/ /and select *Modify* from the context
menu.
2.
On the Paragraph Style dialog, click the *Font Effects* tab.
Change the font color to Light Cyan.
3.
Click *OK* to close the dialog.
What is a dialog? I think I understand, but I really doubt most
readers of the Getting Started with Base chapter will understand. I
would prefer to use the term window since a window is created.
A dialog is a window-like box where the user selects items, types
info, clicks buttons, etc. It overlays (pops up on top of) a window
such as the main Writer window, the main Base windows, etc. The Styles
& Formatting window is a special case (re terminology).
We've had several long discussions about this on the list over the
years. I, and some of the other earlier contributors, personally
prefer "window" for almost everything (for the reason you mention,
which is the same reason as I prefer simplifying other terminology),
but the consensus was to use the term "dialog" and so all the user
guides use that terminology. And the Help does too.
BTW, I use "dialog" and NOT "dialog box" as Gary prefers because (a)
most of the Help AFAIK uses "dialog" and in any case "box" is a
redundant addition. "Dialog" instead of "window" is bad enough.
BTW, whenever I can avoid using any term for a dialog (or any
control), I do. I've especially purged terms like "radio button" from
the user guides. That can be a useful term in programmer-related docs,
but not user docs, where it conveys no useful information.
Lastly, if we ever decide to change from "dialog" to "window," we
should make that change when a major change in the program itself
occurs, because that's when we overhaul all the books.
--Jean
OK, this makes sense. So, to make sure the readers know what I am
talking about, I will be adding a screenshot of the dialog and an
explanation of what a dialog is in a Note in the text. (Note: as in a
Note/Tip/Caution "thing").
An explanation of what a dialog is is not necessary, though showing
the dialog itself may be helpful. None of the other chapters explain
in words what a dialog is, and they all show pictures of dialogs (and
the term is used in the text).
--Jean
