Schmucker, K. MacApp: An Application Framework. Byte 11,8 (1986), pp. 189-193.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....FRAMEWORK Object oriented application frameworks provides a powerful medium for implementing a software framework that divides responsibility between an architecture and a particular instantiation of that architecture. A number of object oriented application frameworks (including MacApp[10] and Unidraw[25] have success fully demonstrated this in various domains. Moreover, there has been a long association between the object oriented programming paradigm and the objectoriented user interface metaphor. It seemed only natural that we use object oriented technology to build an ....

K.Schmucker. Macapp: An application framework. Byte, pages 189-192, August 1986.

....Typically, it will provide help with creating and managing the insides of application windows. Some tool makers have reported significant gains in productivity by users of their tools. For example, the MacApp tool from Apple has been reported to reduce development time by a factor of four or five [13]. As another example, designers were able to create new, custom widgets about 15 times faster with the experimental Peridot system than by coding the widget using conventional techniques [7] SURVEY METHODOLOGY A draft of the survey was circulated on the SIGCHI electronic mailing list, and a ....

Kurt J. Schmucker. "MacApp: An Application Framework". Byte 11, 8 (Aug. 1986), 189-193.

....collection of object oriented classes that cooperate in the problem s solution by means of inheritance and message passing. The first software systems that were called frameworks were application frameworks, which address the general problem of building applications on a particular platform [21]. Application frameworks usually also contain a class library of user interface components that allow developers to start from the null application, that does everything that an application must do in a completely generic way, customizing the application for their own needs. Frameworks need not ....

K. J. Schmucker. Macapp: An application framework. BYTE, 11(8):189--193, Aug. 1986.

....along its design, development, and execution phases. The object oriented technology has proliferated in the UI area and has already shown to be helpful for UI developers in the design and construction process. Some systems reflect this approach and provide a flat object oriented structure: MacApp [7], ET [8] or InterViews [9] The main drawback that emerges from this structure is that it gives few guidelines for the design of a UI [10] Other systems, e.g. GWUIMS [11] or IMAGES, rely on classical UI models like Foley [12] Seeheim [13] or the reference model [14] and apply ....

K. J. Schmucker, "MacApp: An Application Framework," Byte, vol. 11, no. 8, pp. 189-193, August 1986.

....as the NeXT interface Builder [35] because, as pointed out in the introduction, these toolkits cannot support the specification of arbitrary applications graphics or behavior. The majority of the interfaces shown in Figures 1 and 2 would have to be created using a toolkit such as Apple s MacApp [39]. An informal experiment reported in [26] found that it would take a programmer using a toolkit such as MacApp 10 20 hours to create the type of boxes and arrows editor shown in Figure 1. As reported in Section 8, a person using Lapidary can create this application in 40 minutes. 9.2 Learning ....

Kurt J. Schmucker. "MacApp: An Application Framework". Byte 11, 8 (Aug. 1986), 189-193.

....operation is warning the user of a possible problem and soliciting a reply. This operation involves many toolkit level components (e.g. buttons, text and graphics displays, special event handling, and perhaps even text input) An application framework such as PICASSO [20] Garnet [12] MacApp [23], NextStep [27] or Smalltalk [5] provides higher level abstractions (such as a dialog box) to relieve the programmer of the burden of creating them from low level toolkit abstractions. 3 At the same time, an application framework supports the development of applications with a consistent ....

Schmucker, K. J. MacApp: An application framework. Byte, August 1986. -27-

.... message which has caused an error [7] The X Window System s drawing operations use GraphicsContexts to package up a large number of arguments such as the font, colour, line width, and clip region [14] MacApp uses Event objects to package the arguments sent to widgets in response to user actions [15]. The following three patterns describe how Protocol Object can be applied in common situations. Arguments Object (7) captures arguments which are often passed together. Selector Object (8) groups messages which differ only in their names. Curried Object (9) introduces an intermediary which can ....

K. Schmucker. MacApp: an application framework. Byte, 11(8), 1986.

....as appropriate. As with all these patterns, this pattern introduces an additional object into the design, requiring modifications to the program and increasing runtime space and time costs. Known Uses MacApp uses Event objects to package the arguments sent to widgets in response to user actions [22]. The X Window System s drawing operations use GraphicsContexts to package up a large number of arguments such as the font, colour, line width, and clip region [21] Smalltalk s Point and Rectangle objects can be seen as Arguments Objects which package up two or four integer arguments to describe ....

Kurt Schmucker. MacApp: an application framework. Byte, 11(8), 1986.

....requirements and design phases, task models such as GOMS [Card 83] and MAD [PierretGoldreich 89] provide useful ways to structure the task space. Implementation is supported by an even wider variety of tools ranging from toolboxes such as Motif [Motif 90] to application skeletons such as MacApp [Schmucker 86] and UI management systems such as SIROCCO [Normand 92] or Interface Builder [Webster 89] On the other hand, the software engineering community has placed little emphasis on the evaluation of UI. For the purpose of this article, we will organise the evaluation methods around the taxonomy ....

K. Schmucker, "MacApp: an application framework", Byte 11(8), 1986, pp.#189-193

....1986] does not enforce the distinction between task domain concepts and presentation specific issues. Thus, without an adequate software framework, the resulting interactive system may be an incredible mixture of concerns. In order to exploit object oriented application frameworks like MacApp [Schmucker 1986], the programmer needs to reverse engineer the architecture of the existing code. This task can be made easier if the underlying organisation of the environment were made explicit to programmers. A good example is the MVC model that structures the Smalltalk programming environment in a systematic ....

K. Schmucker, "MacApp: An Application Framework", Byte, 11(8), 1986, pp. 189-193.

....the design model in a given programming language. This chapter discusses the object oriented implementation of the presented case study. 4. 1 Concepts Used The CMS was implemented on an Apple MacIntosh using the object oriented programming language MPW Pascal and the application framework MacApp [11]. Figure 9 shows the used classes of MacApp. All MPW Pascal classes are subclasses of the class TObject. The class TApplication is a subclass of TObject as well. The dashed line indicates that Check out Check out Product Version Shipment Workingspace Check out Cancel Select Product Version . ....

K.J. Schmucker. MacApp: An Application Framework. Byte, August 1986.

No context found.

Schmucker, K. MacApp: An Application Framework. Byte 11,8 (1986), pp. 189-193.

No context found.

K. J. Schmucker. MacApp: An application framework. In R. M. Baecker, W. A. Buxton, editors, Readings in Human-Computer Interaction. pp. 591-594. Morgan Kaufmann Publishers, Inc. 1987.

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