| 
|
QuoteRef: myerBA_1992
topics >
all references >
ThesaHelp:
references m-o
Topic:
user-defined languages
Topic:
scripting language
Topic:
customized user interfaces
Topic:
children vs. adults
Topic:
user interface design
Topic:
direct engagement and theater in a user interface
Group:
types of user interfaces
Topic:
ease of learning
Topic:
spreadsheet
Topic:
ease of use
Topic:
words in natural languages
Group:
graphical user interface
Topic:
interprocess communication
Topic:
editing by cut and paste
Topic:
abstraction in programming language
Topic:
state
Topic:
direct manipulation for a UserInterface
Topic:
expression language
Topic:
running programs in a workspace or environment
Topic:
names defined by context
Topic:
pronoun reference
Topic:
open systems
Topic:
functional side effects
Reference
Myers, B.A., Smith, D.C., Horn, B., "Report of the "End-user programming" working group", pp. 343-366, in Myers, B.A. (ed.), Languages for developing user interfaces. Google
Other Reference
Based on papers from a SIGCHI workshop
345 ;;Quote: the goal of end-user programming is to allow the user to significantly customize the system
345+;;Quote: user customization hits a barrier when customization becomes impossible or it requires new techniques; e.g., HyperTalk in HyperCard, or macro language in a spreadsheet
346 ;;Quote: why do children love Legos? immediate, universal, simple, incremental, kinesthetic, visible, quick, examples, safe, fun
346+;;Quote: every Lego set shows examples of what can be built with the pieces in the set
348 ;;Quote: why are spreadsheets easy to use? visible, up-to-date, one cell at a time, modeless, direct action, no conditionals, independent cells, any data type, natural model, smart assistance, multiple views
350 ;;Quote: noun-verb interaction with generic commands mirrors natural languages: many nouns for data, a few verbs for data transformations that are inherently complex; e.g., Xerox Star and Apple Macintosh
350 ;;Quote: the Macintosh introduced the clipboard and clipboard-standard data types; allows interoperability between applications
351 ;;Quote: MacPaint is concrete: the only data structure is bits on the screen, and the user's sole goal is to turn those bits on and off; literally no state to remember
351 ;;Quote: every function in HyperTalk sets 'it' implicitly; turns expressions into a sequence of statements
355 ;;Quote: want an architecture that allows users to open up and modify any module; without a "wall" that prevents further progress
357 ;;Quote: no side effects to spreadsheet formulas. In general, want to minimize side effects, provide clear cause-and-effect relations, and trace/debug the results
ThesaHelp: references m-o (268 items)
Topic: user-defined languages (38 items)
Topic: scripting language (27 items)
Topic: customized user interfaces (10 items)
Topic: children vs. adults (33 items)
Topic: user interface design (36 items)
Topic: direct engagement and theater in a user interface (35 items)
Group: types of user interfaces (23 topics, 298 quotes)
Topic: ease of learning (36 items)
Topic: spreadsheet (28 items)
Topic: ease of use (46 items)
Topic: words in natural languages (40 items)
Group: graphical user interface (24 topics, 510 quotes)
Topic: interprocess communication (29 items)
Topic: editing by cut and paste (8 items)
Topic: abstraction in programming language (47 items)
Topic: state (35 items)
Topic: direct manipulation for a UserInterface (56 items)
Topic: expression language (13 items)
Topic: running programs in a workspace or environment (14 items)
Topic: names defined by context (36 items)
Topic: pronoun reference (23 items)
Topic: open systems (32 items)
Topic: functional side effects (11 items)