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: Question on Naming From:Robert Lauriston <robert -at- lauriston -dot- com> To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Thu, 7 Jan 2010 05:51:45 -0800
Generally, if a UI has been around for a while, or is similar to
something that has, you should not need to make up terms to describe
"Screen" pretty universally means the display as a whole, so would be
ambiguous. "Pane," "panel," "dialog," or "menu," among other terms,
might be standard depending on exactly what's happening.
Could you be a little more specific about the architecture? Is the UI
created with a toolkit or framework such as Visual Studio, Swing,
NetBeans, Eclipse, or Oracle Forms? Browser-based or executable?
OS-specific? When you choose one of these "action items" does the
"screen" that appears replace it or appear in some other part of the
workspace, and if the latter is the "screen" in a separate overlapping
window or in a different area of the same window?
On Wed, Jan 6, 2010 at 8:48 PM, Robert Courtney <bobsc1 -at- earthlink -dot- net> wrote:
> From the one screen you can do several things. It is dynamic in the
> things you do you. You can lock records, you can approve records
> (multiple from a list), submit records for processing, or export records
> to external programs. That's why I call them "Action Items." You can do
> several action from them. But, they are screens. And I wonder if using
> screen is better to describe the area they are going to because they
> understand that better or can I create a definition and the user accept
> it willingly. They do many actions from the screen.
Are you looking for one documentation tool that does it all? Author,
build, test, and publish your Help files with just one easy-to-use tool.
Try the latest Doc-To-Help 2009 v3 risk-free for 30-days at: http://www.doctohelp.com/
Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at: http://www.ModernAnalyst.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-