349 CS 10 Some History
Byron Weber Becker Spring 2009
Slides mostly by Michael Terry
CS 349 Spring 2009 10_History
1
The History of Interaction
History of interaction is the history of making the input and output languages of the machine closer to the language of the user and their tasks Interaction has evolved from forms that favored the machine (when its time was more valuable) to those that favor the user
CS 349 Spring 2009 10_History
2
Interactive Cycle
From Dix, Finlay, Abowd, & Beale (2004) CS 349 Spring 2009 10_History
3
Interactive Cycle: Steps
1. User formulates a goal, plans a method to achieve goal 2. User translates task into system input language 3. System performs instructions, changes its state
CS 349 Spring 2009 10_History
4
Interactive Cycle: Steps
4. System translates its state into its output language 5. User interprets result, repeats the cycle
CS 349 Spring 2009 10_History
5
Interaction
Where do translations occur in this process?
CS 349 Spring 2009 10_History
6
Interaction
Translations occur:
From intention to system input language From input language to core system language From core system language to output channel From output channel to users interpretation of output
CS 349 Spring 2009 10_History
7
Interaction
Input/output channels affect what can, cannot be expressed
Can result in an interactive language far removed from task domain User may need to expend effort translating between task domains language and that of the system Examples?
Example: Doctor remotely examining a patient
May wish to physically examine patient, but cannot actually touch, feel patient
CS 349 Spring 2009 10_History
8
A (Brief) History of Interaction
History of interactive interfaces is history of moving systems interactive language closer to users language, needs, expectations, and the task domain Major paradigms of interaction
Batch interfaces Conversational interfaces Graphical interfaces Ubicomp
Visionaries who inspired advances
Vannevar Bush, Douglas Engelbart, Alan Kay, Mark Weiser
CS 349 Spring 2009 10_History
9
Batch Interfaces
Time period: ca. 1945-1965 Interaction style
Set of instructions prepared a priori, fed to computer via punch cards, paper tape, magnetic tape Response typically received via paper printout No real interaction possible as system executes instructions Responses received in hours, days
Users
Only used by highly trained individuals
System time costs more than human time
$100s/hr vs. $10-30/hr
CS 349 Spring 2009 10_History
10
Conversational Interfaces
Time period: ca. 1965 1985+ Command line interface
First commonly used interactive style
Interaction style
User types command, waits for response Programs usually run to completion Feedback can be given during execution User can be prompted for information during execution
User is guided through heavily scripted / structured interaction
CS 349 Spring 2009 10_History
11
Conversational Interface
First commonly used interactive style Advantages
Highly flexible: Can combine commands to create sophisticated sets of operations
Disadvantages
Requires recall rather than recognition
What does this mean and what are consequences?
System in control during execution: User cannot refine execution / make modifications during program execution
CS 349 Spring 2009 10_History
12
Recognizing User Needs
Batch and Conversational interfaces offer interaction language closer to system language than task language
Onus on user to conform to system
These interfaces were common at a time when computers time was more expensive than a persons time Several visionaries imagined a different form of humancomputer interaction
CS 349 Spring 2009 10_History
13
Vannevar Bush
Headed Office of Scientific Research and Development
Manhattan project, other WWII science efforts
1945 article, As We May Think in The Atlantic inspires computer scientists to present day (http:// www.theatlantic.com/doc/194507/ bush) Goal was to augment human intellect
CS 349 Spring 2009 10_History
14
Vannevar Bush
A memex is a device in which an individual stores all his books, records, and communications It is an enlarged intimate supplement to his memory. Proposes associative links between content Dual display setup! Direct annotation of stored content Proposes direct connection to nervous system But hardware a long way off
CS 349 Spring 2009 10_History
15
Douglas Engelbart
By augmenting human intellect we mean increasing the capability of a man to approach a complex problem situation, to gain comprehension to suit his particular needs, and to derive solutions to problems [We seek] more-rapid comprehension, better comprehension, the possibility of gaining a useful degree of comprehension in a situation that previously was too complex, speedier solutions, better solutions, and the possibility of finding solutions to problems that before seemed insoluble
Augmenting Human Intellect, 1962 SRI Report
CS 349 Spring 2009 10_History
16
Douglas Engelbart
Known for Creating the mouse, chording keyboard Demonstrates concepts such as copy/paste, computer-supported collaborative work in a 1968 live demo
CS 349 Spring 2009 10_History
17
Beyond the Knowledge Worker
Ivan Sutherlands Sketchpad (1963)
Light pen Direct manipulation WYSIWYG
Early Expands computer domain to include artists, draftsmen, and more Language of interface moves substantially closer to task domains
CS 349 Spring 2009 10_History
18
Graphical User Interface
Time period: ca. 1984 present Hardware interface
High resolution, high refresh graphics display Keyboard Pointing device (e.g., mouse)
Typical instantiation: WIMP interface
Windows, Icons, Menus, and Pointer
First instantiation of WIMP interface?
CS 349 Spring 2009 10_History
19
Source: http://www.guidebookgallery.org/site/about
CS 349 Spring 2009 10_History
20
Graphical User Interfaces
Xeroxs 8010 Star Information System (1981) first commercial WIMP offering
Xeroxs Alto the experimental precursor Many ideas from Engelbarts earlier work
Apples Macintosh follows years later, brings the GUI to the masses
(See http://www.digibarn.com/stories/finalstardemo for videos of these early systems)
CS 349 Spring 2009 10_History
21
Graphical User Interfaces
Interaction style
User in control: System waits for input, responds Recognition over recall enables discovery of options, experimentation Simulated world metaphor employed
What does this mean and what are its consequences for interaction?
CS 349 Spring 2009 10_History
22
Graphical User Interfaces
Interaction style continued
Simulated world metaphor uses real-world metaphors to represent data, enable interaction Interaction language closer to users own language, closer to task domain Examples:
Files, folders, trashcan How to refile a file?
Users
Language of interaction opens interface up to broader audience
CS 349 Spring 2009 10_History
23
Direct Manipulation
Defining characteristic of many GUIs is direct manipulation Direct manipulation (Shneiderman, 1982)
Sense of directly manipulating objects of interest
CS 349 Spring 2009 10_History
24
Direct Manipulation
Objects of interest visible Incremental action with rapid feedback Reversibility of all actions
Users can explore without severe consequences
Syntactic correctness of all actions
Every user action is a legal operation
Complex command languages replaced by directly manipulating visible objects
What is, is not, direct manipulation in modern UIs?
CS 349 Spring 2009 10_History
25
Interaction: Now What?
Where can we go from here? What other paradigms are possible?
CS 349 Spring 2009 10_History
26
1990s: Get off the Desktop
Two visions of the future digital age
Virtual reality Ubiquitous computing
CS 349 Spring 2009 10_History
27
Mark Weiser
The most profound technologies are those that disappear. They weave themselves into the fabric of everyday life until they are indistinguishable from it. (Scientific American, 1991) Envisions computing on three scales: inches, feet, yards Computing as natural as writing, fading into the environment
CS 349 Spring 2009 10_History
28
Ubicomp
Ubiquitous computing (ubicomp) highly active research area now Goal is to create language of interaction so close to task domain that the computer and its interface essentially become invisible
Not conscious of the fact that we are interacting with a computer
How can this be achieved?
CS 349 Spring 200...