conventions

[John Prince <prince1 -at- WEBTV -dot- NET>]

I completely agree with  writing a "Conventions Used in this Book"
section.

In fact, I also include a "Dialog Box Elements" section, which explains
each of the elements that appear on the various dialogs . . . and how to
use them, such as spin boxes, drop-down list boxes, option buttons, etc.

I have found this useful.  For example, you write: "Use the up and down
arrows in the Date spin box to select a value. You may also highlight
the default value and type a valid value."  The reader may not know what
a spin box is.

Also, as for functionality, it certainly doesn't help to let the readers
know what the limits are for each element.

Some may feel it's not "chic" in the TW world to do so, but my main
concern is the reader, and the usability of both the product and the
book.

I think that even a basic user who is confused at what bold text means
might look in the index under "bold text" and find that it represents
commands and dialog box names.

I understand that most users probably don't read these sections.  But I
that shouldn't take away the opportunity to read it if so desired should
it?

My feelings are that any bit of confusion that can be eliminated should
be done.

John
http://members.tripod.com/~princej/DC.html (The Great Dallas Cowboys)