MacApp Programmer's Guide. Apple Computer, 1986. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Investigating Reading Techniques for Object-Oriented.. - Shull, Lanubile, Basili (Correct)
....techniques and focus them on aspects of the framework which are most important. 1. Patterns and recipes: Beck and Johnson [6, 23] advocate the use of patterns (interlocking descriptions of problem solution pairs, similar to object oriented design patterns [17] or cookbook recipes, e.g. [1]) to describe frameworks. Each pattern describes a functionality supported by the framework, demonstrates how to implement the functionality, and discusses the impact of the implementation on the system. This seems a promising approach, because it seems capable of both showing the developer only ....
MacApp Programmer's Guide. Apple Computer, 1986.
Handheld, Mobile Video Conferencing - Faichney (1998) (Correct)
....sleep hardware subsystems that are not in use [24] Video conferencing, which is a CPU intensive application, must use algorithms that are of low complexity. If possible, control needs to be returned to the operating system regularly so that relevant hardware components can be put into sleep mode [25]. The chart in Figure 15 shows that the Apple 21 Newton MessagePad 2100 will last for 24 hours on a fully charged battery through normal use. However an experiment conducted by the author shows that the battery life is reduced to 4 hours when the CPU is used constantly while other hardware ....
Newton Programmer's Reference, Apple Computer, ch. 8, p. 8-68, 1996.
Video Coding for Mobile Handheld Conferencing - Faichney, Gonzalez (1999) (Correct)
....in addition to hardware, must also be designed to reduce the power consumption of the device. The operating system and applications must sleep hardware subsystems that are not in use [12] Also applications must return control regularly to the operating system so that this may be achieved [13]. The impact of such methods was tested on the Newton MessagePad 2100. Normal use of the PDA will result in a battery life of 24 hours. However when the device is continuously processing and using other hardware subsystems such as serial communications the battery life is reduced to 4 hours ....
Newton Programmer's Reference, Apple Computer, ch. 8, p. 8-68, 1996.
A Toolset for Experimental Prototyping of Database-Based.. - Hermann Sikora (Correct)
....(interface editor) AudoX (automatic documentation) Most parts of OOSEE 4 were implemented on Sun SPARCstations under SunOS 4.1 using AT T C 2.0 and the application framework ET 2.2 [Wein88, Wein89, Gamm91] Only AudoX was implemented on an Apple Macintosh using C 2.0 under MPW 3. 1 [APDA89] and the application framework MacApp 2.0 [Appl90a, Appl90b] Figure 1 shows the present basic architecture of OOSEE 4. It is by no means a final architecture. OOSEE 4 is because of it s object oriented implementation and common information interchange mechanism (see below) easily expandable ....
Apple Programmer's and Developer's Association: Macintosh Programmer's Workshop C++ Reference, Apple Computer, Inc., Cupertino, California, 1989
Investigating Reading Techniques for Framework Learning - Shull, Lanubile, Basili (1998) (Correct)
....and focus them on aspects of the framework which are most important. 1. Patterns and recipes: Beck and Johnson [Johnson92, Beck94] advocate the use of patterns (interlocking descriptions of problem solution pairs, similar to object oriented design patterns [Gamma95] or cookbook recipes, e.g. [Apple86]) that describe a functionality supported by the framework, demonstrate how to implement the functionality, and discuss the impact of the implementation on the system) to describe frameworks. This seems a promising approach, because it seems capable both of showing the developer only as much ....
MacApp Programmer's Guide. Apple Computer, 1986.
Documenting Frameworks using Patterns - Johnson (1992) (102 citations) (Correct)
....once the framework itself is understood, and that the best way to get a general understanding of a framework is to use it. Thus, we need to explain how to use a framework without explaining how it works. This is not a new idea; the documentation for MacApp has long contained a cookbook [Apple] and the first documentation for Model ViewController (MVC) was called a Cookbook for Model View Controller [Krasner and Pope] Patterns are more like the MacApp cookbook than the MVC cookbook. The MCV cookbook is a collection of examples, but is still a tutorial designed to be read as a unit. ....
....Drawings, Handles, and Tools, must be described in the very first pattern, but most of it can be moved to subsequent patterns without using forward references. 3. The Role of Examples Examples play a key role in the documentation of frameworks. The documentation for MVC [Krasner and Pope] MacApp [Apple] and Unidraw [Vlissides] all include many large examples. Examples make frameworks more concrete, make it easier to understand the flow of control, and help the reader to determine whether he or she understands the rest of the documentation. Examples are also important in documentation based on ....
MacApp Programmer's Guide. Apple Computer, 1986.
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