Well, I think it's actually somewhat important to others. I mean, why
not educate the reader in the terminology that's commonly used so that
there isn't any confusion later? From my understanding, the term
dialog, in reference to a computer program, is fairly standard in the
industry, and Gary's definition is accurate--the program is attempting
to have a dialog with its user so that it can continue its operation.
Beyond a user picking up another book about a different computer
program, the help OOo documentation authors saw it fit to use the term
dialog in its proper context, so if a reader tries to use the help in
conjunction with one of the manuals or the getting started guides, isn't
there an increased possibility for confusion? I think that's where
consistency is important.
Granted, I agree with Jean to a certain extent. My 76 year old mother
doesn't understand when I mention a "dialog" in the context of using a
computer program. But then she struggles with "window" too. To her,
they're all boxes on a screen. And as Jean also pointed out, different
boxes appear on the computer screen with varying content, and sometimes
programmers don't use them the same way. One program may use a window
that might be better as a dialog, or vice versa. In my view, all the
more reason for consistency among the various forms of documentation for
the program we all love. :)
Anyway, just my thoughts on the discussion, but to me the dialog is a
valid term, even still today, no matter how old-fashioned it may appear.
Obviously, things are changing with the increased use of web
applications, and as new interfaces are developed that use different
methods of input and output and other user interaction. Still, as
authors trying to educate users of a software program, I think it's
important to use terms that are sensible in the right places. It may be
a quibble, but I think it helps the users in the long run, even if at a
sub-conscious level.
Thanks,
Sak.
Jean Hollis Weber wrote:
Thanks, Gary, I keep forgetting that distinction, which is technically
correct and IMO only relevant and important to programmers.
IMO the distinction is totally irrelevant to most people who are simply
trying to use the app. And those people more accustomed to using web
apps may rarely encounter the term "dialog" in other programs and thus
are likely to consider it an odd term. That's another reason why I
personally prefer calling them "windows," though in web apps, the term
is just as likely to be "page" as "window."
To me, the term "dialog" is almost as old-fashioned as "screen" and of
about the same relevance to many users: almost none... despite its
usefulness to those to whom the distinction does matter.
