Topic: prompted input

Summary

A standard paradigm for interactive input is: prompt, read-input, check-input-for-errors, and response. Prompted input tells the user what kind of input is expected and indicates a waiting processor. Additional help documentation can be associated with the prompt.

Prompting is especially important with destructive commands. The confirmation-request prompt would not be fixed since frequent users will treat the confirmation sequence as a single command. Instead confirmation-prompts should include information familiar to the user. Unexpected information will hopefully prevent automatic user response. (cbb 5/80)

Subtopic: prompt and read input

Quote: the standard paradigm for interactive input is PROMPT..READ..CHECK..ECHO [»floyRW8_1979]

QuoteRef: muchSS_1976 ;;368 The system should prompt for command arguments not immediately supplied(or defaulted) by the user

QuoteRef: sammJE_1969 ;;571 Display string-to-console reply variable-to-receive reply event event-name-to-signal-completion

Subtopic: progressive disclosure

Quote: Star uses progressive disclosure; e.g., replacement text parameters displayed when CHANGE IT is selected [»smitDC_1982]

Subtopic: switches as input

Quote: use switches for experimenter input; e.g., finding zero of a function or playing chess [»turiA3_1951]

Related Topics

Topic: dialog boxes in a user interface (15 items)
Topic: menus for a UserInterface (31 items)
Topic: modes in a user interface (40 items)
Topic: preventing accidental errors (37 items)
Topic: programming with forms
(26 items)