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.
"Parent/child" already has a standard usage as technical
terminology, as a description of structure or derivation,
where control may or may not exist. A master/slave
relationship is a description of control, where structure
and derivation may or may not exist. For example, it is
possible for two components to have a parent/child
relationship where the child is the master and the parent
the slave (I'm talking about engineering here, not what
you see at the other table when you go to restaurants).
Gene Kim-Eng
----- Original Message -----
From: "Evelyn Lee Barney" <evbarney -at- comcast -dot- net>
> I have to say this is the only alternative I've heard that I thought
> worked. Like others on this list, I felt stuck with master/slave for
> clarity reasons. However, as parent/child is a common term in
> object-oriented programming, I bet this could catch on easily enough.
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-
