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.
I've been in the middle of this argument myself. I convinced them to use
window or screen, because inexperienced users got confused about whether
they were filling out a form that would be printed and sent off somewhere or
completing a data entry task that had nothing to do with printing. A great
deal depends on the audience for the application--what are they trying to
do, and how familiar are they with terminology?
My .02
Connie Giordano
-----Original Message-----
From: wigser -dot- sarahb -at- kendle -dot- com [mailto:wigser -dot- sarahb -at- kendle -dot- com]
Sent: Friday, March 24, 2000 7:45 AM
To: TECHWR-L
Subject: Form or Screen?
Hi All,
I'm having a difference of opinion with two project leads (actually,
they're having the difference of opinion but I'm in the middle) so I
thought I would poll the general techwr-l community.
I'm documenting a Visual Basic application. We document the different
forms the user can access to view data, edit data, etc. One project lead
likes forms (I'm partial to it myself). The other project lead is adamant
that it needs to be changed to screens - I disagree but don't have any real
reason.
Example: Site Level Form vs. Site Level Screen. Common sense tells me the
user is working with a form, not a screen.
