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.
Subject:Re: FrameMaker Menu capture From:Michael Cooperman <michael_cooperman -at- MATHWORKS -dot- COM> Date:Wed, 15 Jun 1994 15:35:19 -0500
Subject: Reply Form Time:3:31 PM
RE>>FrameMaker Menu capture prob Date:6/15/94
I've worked on a couple books that document GUIs and both have included
menus, opened to show all their items. I've begun working on a third and
someone (finally) asked me why we bother to include menus in written
documentation. I have to admit, I now wonder too. Maybe we should all
consider whether pictures of menus adds enough to our documentation to
justify the time (and, sometimes, aggravation) it takes to get them.
Otherwise, we've used a utility called Flash-It that does a decent job. One
of our writers prefers xv.