A. Goldberg. Smalltalk-80: The Interactive Programming Environment. Computer Science. Addison-Wesley Publishing Co., 1984.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....procedural languages are often inappropriate for object oriented programs because they work at an inappropriate level of abstraction. Tools that are directed at object oriented software development have focused primarily on static code structure (for example, class browsers and inheritance viewers [10, 4, 15], To appear in ACM OOPSLA 93 Conference Proceedings. affinity browsers [7] and on breakpoint debugging and object inspection [1] which provide only microscopic views of the program at disjoint points in time. We believe tools that focus on the dynamic behavior of an object oriented system are ....

Adele J. Goldberg. Smalltalk-80: The Interactive Programming Environment. Addison-Wesley, Reading, MA, 1984.

....process like objects. Quicktalk: A compilable dialect of Smalltalk, from Tektronix. Ball86] Simula: A simulation language with object classes. Birt73] Smalltalk: Programming language and environment from Xerox PARC. Some references detail experinces with implementation details. [Atki86 BYTE81 Born82a Born82b Caud86 Deco86 Deut84 Gold80b Gold83 Gold84 John86 Kaeh86 Kras83 Pasc86 Tesl81 Vegd86] Smallworld: Smalltalk descendent from IBM Yorktown. La#85] Spool: A Prolog based object oriented language from IBM Japan. Fuku86] Squeak: An object oriented language for communicating with mice. Card85a] Strobe: A language providing object oriented support for Lisp. See also Impulse 86. ....

A. Goldberg, Smalltalk 80: the Interactive Programming Environment, AddisonWesley, 1984.

....of an object s permanent state, and even the messages objects use to communicate with. If concurrency and distribution are at issue, each object may be an active entity that sits on top of a message passing process, called an actor . Examples of fully integrated languages are Smalltalk [1, 9, 10] and Loops [13] Smalltalk does not support concurrency, distribution or multiple inheritance, but it does provide a strongly homogeneous view of its language, in which even control structures are objects. Languages like Ada [2] support data abstraction, but no multiple instantiation or ....

A. Goldberg, Smalltalk 80: the Interactive Programming Environment, Addison-Wesley, 1984.

....the concern, or evaluating the cost of a planned change [2] among other tasks. Several approaches are available to help software developers locate and manage scattered concern code. Lexical searching tools, such as grep [1] code browsers, such as the Smalltalk integrated development environment [13], cross reference databases, such as CIA [7] and slicers [26] can each help a developer identify relevant points in the code and can help elicit the relationships between the different parts of a program. Alternatively, a developer may be able to leverage the identification of the change from a ....

....code analyzers and cross reference tools, such as CIA [7] or the framework of Canfora and colleagues [5] FEAT does not rely on a program database. Rather, it uses the compiled representation (bytecode) of the program directly, and is thus more similar to browsers for languages such as Smalltalk [13], or Trellis [19] FEAT is implemented in Java. It uses IBM s Jikes Bytecode Toolkit [17] to represent and manipulate Java classes at run time. Section 5.3 discusses the memory consumption issues related to this approach. To resolve the targets of virtual method calls, FEAT uses a simplified ....

[Article contains additional citation context not shown here]

A. Goldberg. Smalltalk-80: The Interactive Programming Environment. Addison-Wesley, 1984.

....of Distributed Smalltalk. Discussion of two of Smalltalk s important characteristics that influenced this work, inheritance and reactiveness, will be largely deferred to Chapter 4. Several books describe the Smalltalk 80 programming language and environment more broadly [Goldberg 83a, Kaehler 86b, Goldberg 83b] 3.1 Object Structure and Naming Objects in Smalltalk, as in most of the systems we examined in Chapter 2, are abstractions that conceptually encapsulate data and a set of operations defined on that data. In Smalltalk, however, all entities are named objects. In many other systems there exists ....

....shared by all instances of a class. global variables Global variables are shared by all objects. pool variables Pool variables are shared by all instances of some subset of the classes in the system. The majority of shared variables in Smalltalk are either class variables or global variables [Goldberg 83b] In addition to the kinds of variables we have mentioned, Smalltalk defines several pseudo variables. Pseudo variables are used to represent special message recipients. The pseudo variable self allows a method (the code that defines the behavior of a particular operation) within an object to ....

[Article contains additional citation context not shown here]

Adele Goldberg, David Robson, and Dan Ingalls. Smalltalk-80: The Interactive Programming Environment. Addison Wesley, Palo Alto, California, 1983.

....it wishes to serve, depending on its internal state. Our specification of active objects is fairly traditional. The advent of popular object oriented paradigms like C , often makes it necessary to remind their users that one of the archetypes of object oriented programming, Smalltalk 80 [9], makes use, at least conceptually, of active objects. Our definition follows the same ideas, using paradigms for message passing and for the control of received messages that are well known in the concurrent programming community. The only unusual feature of our model, compared to traditional ....

A. Goldberg, Smalltalk-80: The Interactive Programming Environment. Reading, Massachusetts: Addison-Wesley, 1984.

....here goes beyond these references in that it refines the framelet concept in the light of experience from a real product line. The relationship of implementation cases to use cases has already been mentioned. Additionally, implementation cases have an antecedent in the cookbook recipes of [11,21]. The latter, however, were proposed as ways of documenting product lines providing how to examples of their use for application developers. Implementation cases are more ambitious. They can certainly serve as cookbook recipes but their primary value is as tools for the continuous verification ....

A. Goldberg, Smalltalk-80 / The Interactive Programming Environment, AddisonWesley, 1984

....by that class. Thus an implementation can perfectly match the interface but have an entirely different behavior than another similar implementation because 8 it is composed with different primitives. Some of the founding object based languages, such as SIMULA [KO62] and SmallTalk [GAR83] KG83] GA84] GAR89] tried to replace the implicit architecture of a call frame stack with a message passing queue. In this architecture, methods are evoked by passing messages between objects. However, the architecture is still implicit and under defined leading to no choice in an alternative behaviors. ....

Goldberg and Adele. Smalltalk-80: The Interactive Programming Environment. Addison-Wesley, 1984. ISBN 0-201-11372-4.

....chapter is not a complete description of these frameworks; such a presentation would not be possible here. There is also a large number of frameworks which are not mentioned here at all. MVC The Smalltalk 80 user interface framework called Model View Controller (MVC) was developed around 1980 [Gol84, KrP88, LaP91] It was the first widely used framework and it showed that object oriented programming is well suited for implementing graphical user interfaces. MVC uses a paradigm in which the input, the actual system core, and the visual feedback are explicitly separated and handled by three ....

Goldberg A.: Smalltalk-80: The Interactive Programming Environment. AddisonWesley, 1984. 34

....in an object oriented language. We also assume that a particular software repository, the Software Information Base (SIB) is included in the development environment. Small to medium size collections of software classes can be organized by fairly simple schemes in the style of Smalltalk 80 [Gold84]. Classes are hierarchically organized by inheritance and are grouped by functionality into possibly overlapping categories. The class browser allows the selection and exploration of reusable classes. Various approaches have been proposed for addressing the selection problems arising in large ....

A. Goldberg, Smalltalk-80: The Interactive Programming Environment, Addison-Wesley, Reading, Massachusetts, 1984.

....parallelism and distribution are convenient mechanisms for supporting the iterative design of user interfaces, for implementing physically distributed applications, and for handling multi threaded dialogues. A number of agent based models and tools have been developed along these lines. MVC [14], PAC [5] ALV [15] the LIM [19] and York [10] models are typical agentbased styles. All of the agent based styles and tools push forward the functional separation of concerns advocated by Seeheim. They generalise the distinction between concepts and presentation techniques by applying the ....

Goldberg, A., Smalltalk-80: The Interactive Programming Environment, Addison-Wesley Publ., 1984.

....influence the performance of an example based approach as well. One fourth of all the teams in our study had trouble making use of the examples because the example set provided did not conform to a consistent organization or structure. Some examples were based on Model View Controller interaction [20] while others were not constrained by any such separation of functionality, and different examples seemed to achieve the same functionality by using different classes from the framework hierarchy. As others [35] have pointed out, learning how to implement functionality from existing applications ....

A. Goldberg, Smalltalk-80: The Interactive Programming Environment. Reading, MA: AddisonWesley, 1984.

....it becomes desirable to aggregate them into higher level ones. These higher level abstractions help developers cope with the size and complexity of software systems, which is important both during development and future maintenance. Examples of programming environments 1 include Smalltalk [11] and Interlisp [28] from Xerox Parc, Integral C [25] from Tektronics, and the Turbo environments from Borland such as that for Prolog [1] A well known programming environment developed at 1 For surveys of programming environments, and software engineering environments in general, readers are ....

Goldberg, A. Smalltalk--80: The Interactive Programming Environment. Addison--Wesley Publishing Company, Reading, Massachusetts, 1983.

....make good use of screen space, and are easier to use. Introduction This paper presents seven patterns for graphical user interface, each inspired by the GOF 1 pattern of the same name. These patterns have been used widely in GUIs beginning with the early work on the Star [10] and Smalltalk [9], and we have illustrated these patterns with examples from more recent GUIs. To derive these GUI patterns from the GOF patterns, we have translated the GOF patterns from the domain of OO software design to that of GUI design. Although both the GOF patterns and our GUI patterns are expressed in ....

Adele Goldberg. Smalltalk-80: The Interactive Programming Environment. AddisonWesley, 1983.

....of a hypermedia tool with support for multi user hypertext editing and video conferencing. Moving the focus from editing systems to programming environments, we have to mention two environments as further milestones for the development of modern user interfaces. The Smalltalk environment [44] was the first one which used overlapping windows, whereas the Cedar environment [103] introduced the less successful concept of tiling windows. These windows do not overlap, but rearrange themselves semiautomatically such that the available space is always completely covered. The program ....

A. Goldberg. Smalltalk 80 - The Interactive Programming Environment. Addison Wesley, Reading, MA, 1984.

....are plugged in. The developers code gets called by the framework code. The framework determines the overall structure and flow of control of the program. The first widely used framework, developed in the late 70 s, was the Smalltalk80 user interface framework called Model View Controller (MVC) Gol84, KP88, LP91] MVC showed that object oriented programming was well suited for implementing graphical user interfaces. It divides a user interface into three kinds of components; models, views and controllers. These objects work in trios consisting of a view and controller interacting with a ....

Adele Goldberg. Smalltalk-80: The Interactive Programming Environment. Addison-Wesley, Reading, Massachusetts, 1984.

.... discrete event simulation models are built using an object oriented language, namely Simula [Pooley,87] Despite the availability of object oriented programming languages such as Simula from the mid sixties [Nygaard,81] and the follow up 41 development of the Smalltalk language and environment [Goldberg,84] in the seventies, the object oriented paradigm has only really been accepted towards the mid 80s. In the rest of this section, we shall address the concepts behind the object oriented concept. We shall first present the object model, then lead to some of the object oriented languages and then ....

.... has been further aided by the advent of programming languages such as Smalltalk 80 [Goldberg,83] where the object oriented structure lends itself to decomposition and therefore facilitates the building of libraries of objects, for example graphics objects, that can be easily retrieved and re used [Goldberg,84] These library objects could then be put together, very quickly, to build prototypes for experimentation. Smalltalk also provides a WIMP interface that facilitates this process further. Other efforts include of some high level constructs for fast experimentation, for example the use of Petri ....

Goldberg, A., Smalltalk-80: The Interactive Programming Environment, Addison-Wesley, (1984).

No context found.

A. Goldberg. Smalltalk-80: The Interactive Programming Environment. Computer Science. Addison-Wesley Publishing Co., 1984.

No context found.

A. Goldberg. Smalltalk-80: The Interactive Programming Environment. Addison-Wesley, Reading, Massachusetts, 1984.

No context found.

A. Goldberg. Smalltalk-80: The Interactive Programming Environment. Addison-Wesley, 1984.

No context found.

A. Goldberg. Smalltalk-80: The Interactive Programming Environment. AddisonWesley, Reading, Mass., 1984.

No context found.

Adele Goldberg. Smalltalk-80: The Interactive Programming Environment. Addison Wesley, 1984.

No context found.

Goldberg, A., Smalltalk-80: The Interactive Programming Environment, Addison-Wesley, Reading 1984.

No context found.

A. Goldberg, Smalltalk-80: The Interactive Programming Environment, Addison-Wesley, Reading, Massachusetts, 1984.

No context found.

Goldberg, A., Smalltalk-80: The Interactive Programming Environment, AddisonWesley, Reading 1984.

First 50 documents  Next 50

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC