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 understand the principles of OOP from an applications development point of
view, but your comprehensive analysis of the documentation procedure is
quite instructive. If I understand you correctly, only context-sensitive
online (help-type) documentation can provide the degree of portability and
adaptabiliy necessary to properly document an OO application, correct? And
would this be true whether writing for the developer or for the end user?
How about tutorials and collateral documentation?
Can you recommend a good reference volume on the design and creation of
context-sensitive documentation?
Thanks and Shalom,
Shmuel Ben-Artzi
Data Services Manager, Ulpan Akiva
Netanya, Israel
sba -at- netmedia -dot- net -dot- il
>Being that the functionality is portable, the documentation must also be
>portable. Therefore, the documentation for the text applet should keep
>focus on text construction, formatting, and modification and not be
>concerned with graphics, page layout, file format, and so forth (the
>graphics and document handler applet documentation addresses these).
>Mike Wing
TECHWR-L List Information
To send a message about technical communication to 2500+ list readers,
E-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send administrative commands
ALL other questions or problems concerning the list
should go to the listowner, Eric Ray, at ejray -at- ionet -dot- net -dot-
