Gary Schnabl wrote:
There's a very simple solution to this tab/page/pane bit, and at the
same time the docs could be somewhat less verbose and shorter...
Simply tell the user what to do without continually bringing up the
words page or tab (or dialog box, etc., ad nauseum). It's quite
obvious that the user will be entering data or otherwise doing
something in a window/page/pane/dialog box that appears as a
consequence of doing something that preceded it. Why do the manuals
have to repeat over and over again that a such and such GUI component
appears or that such-and-such is on some GUI part? All this verbosity
is B-O-R-I-N-G, is tedious to enter for the writer, and it merely
takes up space.
Just tell the user to click on the name of the label/tab w/o using tab
or another such term, especially when it's totally obvious.
Gary
Totally agree. Problem is that when people use the guide as a reference
manual (and most do) they just jump to the section you are interested
in, expecting to find all the information they need. For this reason,
it makes sense to me to avoid saying that to change a gradient you open
the Area page/tab :-D if you just said 10 lines above that this is the
page to set the area properties, but I am sure someone will complain
about the quality of the manual if we did so.
Cheers,
Michele
