| 
|
Topic: Thesa's user interface
topics >
computer science >
programming >
types of user interfaces
Group:
user interface for hypertext
Topic:
history list in hypertext
Topic:
display of hypertext links
Topic:
information retrieval by following links
Topic:
hypertext as external memory
Topic:
windows for a UserInterface
Subtopic: programming vs. command language
Quote: Cedar user interface by a notifier that initiates asynchronous procedures that match input events in a TIP table [»swinDC7_1985] Quote: Cedar users often have several foreground tasks, e.g., multiple edits, debugging, and reading mail [»teitW3_1985] Quote: Cedar's Inscript package delivers time-stamped, input events; reduces missed and out-of-order events [»swinDC7_1985] Quote: a Cedar TIP table defines procedures for input events or event sequences [»swinDC7_1985]
Subtopic: open system
Quote: if programming and command languages are unified then calling a procedure is the same as running a program [»heerJ4_1985] Quote: there should be a single language for all aspects of software engineering from initial conception to use [»rossDT_1970]
Quote: a user should be able to observe and manipulate every accessible component [»ingaDH8_1981a] Quote: open system is understandable: reasons for action, help, commands
[»robeG5_1981]
Group: types of user interfaces (23 topics, 298 quotes)
Group: user interface for hypertext (5 topics, 109 quotes)Topic: history list in hypertext (26 items)
Topic: display of hypertext links (15 items)
Topic: information retrieval by following links (23 items)
Topic: hypertext as external memory (24 items)
Topic: windows for a UserInterface
(21 items)