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:Jan Cohen <najnehoc -at- yahoo -dot- com> To:Ned Bedinger <doc -at- edwordsmith -dot- com> Date:Mon, 22 Oct 2007 02:54:35 -0700 (PDT)
That's more in-line with my thoughts. But like Janice suggested, we probably now ought to wait until Zen chimes in.
In the meantime, client-server sounded too much like patron-waiter to me, and my thoughts have all gone south. It's time to get something to eat.
jan c.
----- Original Message ----
From: Ned Bedinger <doc -at- edwordsmith -dot- com>
To: Jan Cohen <najnehoc -at- yahoo -dot- com>
Cc: Lauren <lt34 -at- csus -dot- edu>; Janice Gelb <Janice -dot- Gelb -at- Sun -dot- COM>; techwr-l -at- lists -dot- techwr-l -dot- com
Sent: Monday, October 22, 2007 3:39:11 AM
Subject: Re: What is the best term to use?
Jan Cohen wrote:
>
> 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.
>
It would be useful, in order to put some of these concerns to bed, to
know the architecture of the tabbed program--is the tabbed interface
superficial, like a front end? Or another possibility that appeals to
me
is calling the tabs 'gateways', if they give access but don't provide
the main programs' functions themselves.
If the tabbed application is developed as a client server design, then
those tabs and program functions could be described and called by their
functional role. I think that calling the tabs 'clients' would have a
salutory and invigorating effect on users. But I'm afraid that calling
them tabs or applets wouldn't have that same beneficial effect, at
least
not on me, but as always, YMMV.
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-