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: Command Line Interfaces From:"David M. Brown" <dmbrown -at- brown-inc -dot- com> To:Techwr-L post <techwr-l -at- lists -dot- raycomm -dot- com> Date:Wed, 31 May 2000 16:39:55 -0700
Janet Valade wrote:
>
> A user using a command line interface is looking at nothing.
> There are no cues what to do next.
Sure--DOS that leaves you hanging :) but a good command-line interface includes prompts for each required bit of information and vvalidates input for uer error.
Command-line interfaces may not be as *pretty* as GUIs, but they can be just as "friendly."
--David
=============================
David M. Brown - Brown Inc.
dmbrown -at- brown-inc -dot- com
=============================
