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.
Re: Use of Object Oriented Programming Terms in Documentation
Subject:Re: Use of Object Oriented Programming Terms in Documentation From:JPG3 <jpg3 -at- AOL -dot- COM> Date:Wed, 12 Oct 1994 08:39:02 -0400
In my experience, object properties are pretty easy concepts for people to
pick up since they're not really all that new. Many things have
properties, or values, or some other type of description assigned to them
that affect how/what they can do.
The biggest problem I've encountered is the lack of conceptual
understanding about whay you can do with objects, especially referencing
an object via a link. In our new object-oriented online information
service, you can compose an email message or discussion note (much like
this one) and include a link to a related article (e.g. a Dr. Dobbs
article on OO design). The reader can then double click on the link to
open the article.
IMHO, it's this need to understand how you can use the object-ness that's
more important than what it's innards look like. Of course, it depends on
who you're writing to....
John Garison
jgarison -at- zdi -dot- ziff -dot- com
