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: User interface From:Alexander von Obert <avobert -at- MSN -dot- SUB -dot- ORG> Date:Mon, 22 May 1995 09:39:44 GMT
Margaret Gerard <margaret%mailhost -at- toshiba -dot- tic -dot- oz -dot- au> wrote:
>In past discussions of the scope of tech writer work, people have
>occasionally mentioned being involved in the design and creation of the
>user interface for the system they are documenting.
I see it as a logical extension of my work: User interfaces should do
most of the things manuals were expected to in the past. And if you do
the user interface right, your manual (and online documentation)
>One tool under consideration is "Open Interface Elements" from a US company
>called Neuron Data. The tool is used to place elements like push buttons,
>radio buttons, scroll bars, data entry fields etc. in a window (and link
>to database). Has anybody used "Open Interface Elements"? Would you mind
>sharing your experiences?
>Can anybody point me to any other tool for this purpose?
At least one of my customers uses Visual Basic for that purpose.
Greetings from Germany,
avobert -at- msn -dot- sub -dot- org (Alexander von Obert)
Nuernberg, Germany, Europe, FIDO 2:2490/1719