Smalltalk-80: bits of history, words of advice
Smalltalk-80: bits of history, words of advice
Smalltalk-80: the language and its implementation
Smalltalk-80: the language and its implementation
SMALLTALK-80: the interactive programming environment
SMALLTALK-80: the interactive programming environment
POPL '81 Proceedings of the 8th ACM SIGPLAN-SIGACT symposium on Principles of programming languages
A type declaration and inference system for smalltalk
POPL '82 Proceedings of the 9th ACM SIGPLAN-SIGACT symposium on Principles of programming languages
An architecture for intelligent assistance in software development
ICSE '87 Proceedings of the 9th international conference on Software Engineering
ADAM: a graphical, object-oriented database-design tool and code generator
CSC '91 Proceedings of the 19th annual conference on Computer Science
Pecan: Program development systems that support multiple views
ICSE '84 Proceedings of the 7th international conference on Software engineering
Graphical program development with PECAN program development systems
SDE 1 Proceedings of the first ACM SIGSOFT/SIGPLAN software engineering symposium on Practical software development environments
Programming versus databases in the object-oriented paradigm
Information and Software Technology
| Hi-index | 0.00 |
There exists a buzzword in the user interface research community that symbolizes how the user should feel about a computer-based environment in which productive work can be carried out. The buzzword is “friendly.” It is a strange choice of word in that it seems to imply the existence of personal support for the user by a friend, who happens not to be made of flesh and blood, but of metal and electricity. Friends help us. Friends help us learn, help us develop positive situations, helps us understand and get out of negative situations. We like to be around them. The problem of creating a “friendly” programming environment centers on the kind of help the system provides, and the ease with which we can cause the effects we wish to cause. In order to support program development, help takes the form of methods for finding information, methods for accessing existing functionality, methods for describing new programs, and methods for discovering and fixing any faults in those programs. Ideas about the forms of help needed in a system define some of the functionality that ought to exist. In particular, we want to be able to help the user find out what went right, find out what went wrong, find out what can be done next, and find out something about any system component.