TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
On July 18, Joy Switzer said:
>>....in the new documentation for a piece of software
my co has developed we are confused on the use of the words "icons" and
"buttons". We feel that an icon is a graphical representation of the action
that will take place when you click it. A button has text on it to describe
what it will do. Are we right in our assumption...what standard have some of
you used in your
In the application that I am currently documenting, we have icons on the main
menu bar. Each of these icons is a graphical representation of a subsystem.
When the user clicks on the icon, a sub-menu is displayed from which the user
can select a screen or window. This is the only place in the system that we
have something called icons.
We also have buttons, which are on our GUI windows. These buttons either
perform some action or display a sub-menu from which an action can be selected.
These buttons have only text on them.
In summary, we use icons as a graphical representation of a subsystem, and we
use textual buttons for all functions and sub-menus. I don't think that there
are any rules as to what icons or buttons are used for; it just depends on
whatever standards you decide upon.
Chuck Blessing - chuck -dot- blessing -at- cbis -dot- com OR cjb -at- one -dot- net
Cincinnati Bell Information Systems, Inc. (CBIS) - Cincinnati, Ohio
TECHWR-L List Information
To send a message about technical communication to 2500+ list readers,
E-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send administrative commands
ALL other questions or problems concerning the list
should go to the listowner, Eric Ray, at ejray -at- ionet -dot- net -dot-