QuoteRef: pikeR1_1994

topics > all references > ThesaHelp: references p-r

references p-r
windows for a UserInterface
tiled vs. overlapping windows
file directory
multi-processing for a user interface
mouse as the user interface
incremental execution
search algorithms
selecting text with a mouse
interactive response time
test scripts
keyboard macros
event controlled processing
communicating sequential processes
event loop for a user interface
parallel processing
undoing actions in a UserInterface
text editing


Pike, R., "Acme: a user interface for programmers", 1994 Winter USENIX, January 1994, pp. 223-234. Google

Other Reference

QuoteRef: pikeR6_1991a

225 ;;Quote: Acme automatically creates windows in a column with a single mouse click; easily rearranged by dragging a layout box
225 ;;Quote: each Acme window, column, and display has a tag that names the window with its file, contains built-in commands, and provides an editable scratch area
225 ;;Quote: every Acme command is interpreted in the directory named by the corresponding window tag
225 ;;Quote: Acme use a standard left mouse button, a middle button to execute commands, and a right button to locate and select files and text
226 ;;Quote: text swept with the middle mouse button is executed on button release; any text may be a command
226+;;Quote: Acme binds some actions to chords of mouse buttons
226 ;;Quote: Acme executes non-builtin commands in the window's directory; each window has related windows for standard output and standard error output
226 ;;Quote: the right mouse button indicates arguments to a generalized search facility that locates files, file locations, and text
226 ;;Quote: Acme avoids needless clicking; no click-to-type, no pull-down menus, automatic window placement, context-dependent selection
226 ;;Quote: Acme's window placement: new windows created in the active column, 'execute' and 'search' do not change active window, output windows to the right, large blank spaces consumed
228 ;;Quote: programmable control of Acme through predefined files for each window: body text, tag text, character address, data at address, control, and events
229 ;;Quote: the 'event' file for an Acme window records all changes, execute, and search events for the window
229+;;Quote: Acme reports changes to a window/file after the change is made; allows multiple agents to make changes in response to changes
229 ;;Quote: if a program opens a file in the 'acme/new' directory, a window is also created
232 ;;Quote: Acme is written in Alef, a concurrent object-oriented language similar to C; worked out well
232+;;Quote: avoid the clumsy top-level event loop via concurrent processing
232+;;Quote: Acme uses a new process for each I/O request; its state encodes the state of the I/O request and removes the need for queues
233 ;;Quote: implement 'undo' with an undo transcript, redo transcript, and sequence numbers; e.g., global substitution in reverse order
233 ;;Quote: for editing large files, use a temporary file to hold the text of the visible portion

Related Topics up

ThesaHelp: references p-r (245 items)
Topic: windows for a UserInterface (21 items)
Topic: tiled vs. overlapping windows (21 items)
Topic: file directory (42 items)
Topic: multi-processing for a user interface (14 items)
Topic: mouse as the user interface (13 items)
Topic: incremental execution (22 items)
Topic: search algorithms (40 items)
Topic: selecting text with a mouse (14 items)
Topic: interactive response time (32 items)
Topic: test scripts (13 items)
Topic: keyboard macros (12 items)
Topic: event controlled processing (46 items)
Topic: communicating sequential processes (33 items)
Topic: event loop for a user interface (11 items)
Group: parallel processing   (41 topics, 1116 quotes)
Topic: undoing actions in a UserInterface (23 items)
Topic: text editing (34 items)

Collected barberCB 8/97
Copyright © 2002-2008 by C. Bradford Barber. All rights reserved.
Thesa is a trademark of C. Bradford Barber.