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.
You are looking for the Windows Interface Guidelines for Software Design.
Microsoft Press. 1995. ISBN 1-55615-679-0. You can get it from
www.Amazon.com for about $25.00.
My bible. I carry it to all clients sites. It really makes my point that
this interface is too hard to document and here is how it is supposed to
look. Amazing how many Windows programmers don't know that MS has standards
for the GUI.
sharon
Sharon Burton
Anthrobytes Consulting
Home of RoboNEWS(tm), the unofficial RoboHELP newsletter
www.anthrobytes.com
Check out www.WinHelp.net!
-----Original Message-----
From: Eric Thomas <eathomas -at- DBITS -dot- COM>
To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU <TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU>
Date: Wednesday, 26 August, 1998 8:09 AM
Subject: GUI standards book?
>Hi all.
>I know this might be somewhat off topic for tech-writing, but it's part of
>my job right now, so I'm posting here in hope of some help. I work for a
>software company, and we need to get our GUI standards in order. We've
>decided we need to have a starting point - a GUI standards book of some
>sort - which we will refer to before we make up our own standards.
>Something like the Microsoft Manual of Style, but focused on the GUI.
>Unfortunately, in my travels, I haven't been able to find a book that is
>more "standards-based" rather than "these are ideas you should keep in
>mind." The CEO of our company mentioned IBM's old CYA manual... but I
>haven't been able to find any info about that so far. Regardless, unless I
>can find an actual standards manual that makes statements similar to: "Save
>is only enabled in a dialog box if a state change has taken place," then
>I'm going to end up having to write one from scratch.
>Any suggestions on what to look at? I've already bought and looked at
>About Face by Alan Cooper, GUI Design Essentials by Susan Weinschenk,
>Pamela Jamar and Sarah Yeo, and Tog on Interface by Bruce Tognazzini - and
>these are great but don't provide the hard and fast standards our CEO and
>engineers want.
>Thanks in advance.
>-Eric
>
>---------------------------------------------------------------
>Eric A. Thomas
>eathomas -at- dbits -dot- com
>http://www.dbits.com
>E-mail overload?
>Your customers expect ResponseNow!
>---------------------------------------------------------------
>
>From ??? -at- ??? Sun Jan 00 00:00:00 0000==
>
>
>