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: What is the best term to use? From:"Lauren" <lt34 -at- csus -dot- edu> To:"'Jan Cohen'" <najnehoc -at- yahoo -dot- com>, "'Janice Gelb'" <Janice -dot- Gelb -at- Sun -dot- COM>, <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Sun, 21 Oct 2007 22:03:57 -0700
I think the main issue here is that there is a *thing* in web applications
that does not have an effective name. A "tab" is too constricting and an
"applet" may be too broad. Neither is perfect. If it comes down to
weighing which term is more or less perfect, then which term has more weight
in describing the *thing*. Near as I can tell, "widget" is taken. How
about "tabular application interface"? A bit wordy, but it captures the
functionality.
"Tab" works well for components of applications. "Applet" works well for
short applications and applications within larger applications, like Java
applets within web browsers. But works well for a tabular interface that
has functions beyond that of setting parameters? Do we need a new word?
But anyway, the name of the function may require greater development than
what is provided in the current data dictionary for general application
functionality.
Lauren
_____
From: Jan Cohen [mailto:najnehoc -at- yahoo -dot- com]
Sent: Sunday, October 21, 2007 9:31 PM
To: Lauren; Janice Gelb; techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Re: What is the best term to use?
I'll buy that, as I can see what you're getting at here. But I'd still have
a pretty tough time calling "tabs" applets. I can see tabs being created by
an applet, or clicking on a tab to execute an applet, but I cannot see a tab
providing operational functionality. IMHO, a tab, itself, in the sense you
describe below, really is only that part of a user interface used to
*access* operational functionality, not provide the functionality itself.
Then, I'm not paying you your big bucks and if your client insists that a
tab be called an applet, who am I to argue? Let's be friends and agree to
disagree. 8^)
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-