MacApp 2.0 ViewEdit User's Guide ViewEdit User's Guide preliminary draft 1 •WARNING• This is the first alpha release of ViewEdit. It is untested and not yet beta quality. It should be used with extreme caution: it may crash your system or even erase files from your hard disk. Save your work often and don't use ViewEdit when a system crash would cause you to lose data. Preface Welcome to the ViewEdit User's Guide, and to the power of ViewEdit. ViewEdit is a MacApp utility program that allows you to create view hierarchies in a what-you-see-is-what-you-get editing environment, rather than in a compiled resource file. ViewEdit gives you as much view-editing power as Rez but provides Commando-like dialogs for entering values into each 'view' resource field. This relieves you of having to remember which fields and values are associated with which 'view' types. ViewEdit also allows you to draw, resize, and move your views using the standard Macintosh interface. It even creates and rearranges your view hierarchies as you go! Before you read this document, you should understand these concepts: • View hierarchies. These are introduced in the "Architecture" section of Chapter 4 of the MacApp 2.x Manual (Interim Version). · • View classes. These are described in the MacApp® 2.0BS Display Architecture Release Notes. • View resources. These are explained in the "Creating View Templates" recipe in Chapter 7, "The CookBook", in the MacApp 2.x Manual (Interim Version). This guide is divided into two parts: a step-by-step tutorial and a command reference. ViewEdit is simple enough to use that you may find you won't need to refer to this manual frequently. However, you should read through this manual at least once, for there are many shortcuts and features hidden in ViewEdit, as well as a few eccentricities. 1 © 1988 Apple Computer August 31, 1988 MacApp 2.0 ViewEdit User's Guide A first look at ViewEdit This section shows you how to use ViewEdit to edit the view resources in the DemoDialogs sample application. Before you begin this tutorial, you should build the DemoDialogs sample. If you are new to MacApp and the l\.1PW environment. Chapter 6, of the MacApp 2.x Manual (Interim Version), "How to Install and Use MacApp", will show you how to build the sample applications. After building DemoDialogs, open the VicwEdit application by double-clicking on its icon. The resource file window The first thing that you will see after starting ViewEdit is the empty "Untitled-I" window. Close this window and choose the Open command from the File menu. Then select the DemoDialogs application from the Standard File dialog. The window that appears is reminiscent of the resource file window in ResEdit There is an icon for each type of resource in DemoDialogs. The icon for 'view' resources is always in the upper-left hand comer (and if you have a color screen, you will see it is also the only colored icon). Here is the resource file window from DemoDialogs: DemoDialogs…

MacApp 2.0 Memory Management Any of the following situations can cause an application to stop with a System Error alert, without any chance for that application to gain control: · Not enough memory to load a code segment. Not enough memory to load a PACK resource. Not enough memory to save the bits under a menu which is pulled down. Not enough memory to load a defproc (WDEF, MDEF, CDEF, LDEF). Not enough memory for Standard File to create its file list Add your personal favorite here. Not all commercial Macintosh applications deal correctly with these issues, in large part because doing so involves some rather complicated code. MacApp contains a memory management mechanism which is designed to help keep a MacApp application from getting into these critical memory situations. It does require some work on your part, but makes it much, much easier to produce a robust application than if you did your own memory management from scratch. MacApp's scheme works by dividing available heap space into permanent memory and temporary memory (also known as code reserve). Permanent memory is the space occupied by data which your application allocates: objects and any subsidiary data structures you may create. Temporary memory is reserved for your code segments plus any resources and/or memory needed by the Macintosh Toolbox for a short period of time. MacApp makes sure that your application can't crash for one of the above reasons by always reserving enough space for temporary memory requests to be satisfied. You tell MacApp how much memory needs to be reserved, and it does the rest It only needs to know whether a given memory request is permanent or temporary. Objects created via New (as well as TObjectShallowClone and all other MacApp methods which allocate memory) are automatically taken from permanent memory. You can ask for a new handle from permanent memory by calling NewPermHandle instead of NewHandle; for other kinds of requests you set the "permanent" flag by calling PermAllocation(TRUE). make the request, then set the flag back (PermAllocation returns the previous value of the flag as its result). Any other requests (such as those made by the ROM) default to temporary memory. Note that it is dangerous to have the permanent flag TRUE for any length of time, as any toolbox call which allocates memory or any procedure call which could load a segment will then operate just as it would with no memory management mechanism. For example, calling a procedure in another segment which isn't loaded when the flag is TRUE and there is no permanent memory available will cause a segment loader bomb, even if plenty of temporary memory is available. When debugging is on, MacApp checks for the flag being TRUE in the main event loop or when a segment is loaded and drops into the debugger if it is. If you need to call a routine which allocates both permanent and temporary memory (such as TextEdit, which allocates permanent data structures and which also loads temporary re…

( MacApp® 2.0bS UGridView Release Notes Deb Orton Overview The purpose of the UGridView module is to provide the view that goes "on top" of a list or grid framework. UGridView knows nothing about the underlying cell contents (with the exception of the text methods which work for text grids or lists only); therefore, the user must (at least) provide a DrawCell method (or a GetText method in the TextView cases). The height and width of rows and columns are variable although optimized for a fixed value. The standard cell selection algorithms are provided (as described by the List Manager in Inside Macintosh. Volume IV), as well as a method for enabling single cell selection only. Selection through a method call is provided. View templates exist for all the view objects in this unit. The following classes are defined in UGridView: TGridView For displaying a 1- or 2-dimensional grid of cells containing anything (text, picts, subviews, and so on). TTextGridView For displaying a 1- or 2-dimensional grid of cells containing only text. TTextListView For displaying a I-dimensional grid of cells containing only text. TGridSelectCommand For building the other command objects. TCellSelectCommand For selecting a cell. TRowSelectComrnand For selecting a row divider. TColSelectComrnand For selecting a column divider. TVertexSelectComrnand For selecting a row and column divider. Wed, Aug 3, 1988 © 1988 ti Apple Computer, Inc. 1 TGridView Types GridCell = Point; A cell in the grid. GridViewPart = (badChoice, inCell, inRow, inColumn, inVertex); Used to type mouse clicks. RunArrayChunk RunArray contents (private). RECORD count: size: INTEGER; INTEGER; END; RunArray =ARRAY [0 .. 100000] OF RunArrayChunk; For casting use (private). PRunArray "RunArray; Pointer to run array (private). HRunArray "PRunArray; A handle to a run array (private). Template Types GridViewTemplate PACKED RECORD numOfRows: INTEGER; numOfCols: INTEGER; rowHeight: INTEGER; colWidth: INTEGER; rowinset: INTEGER; colinset: INTEGER; adornRows: BOOLEAN; adornCols: BOOLEAN; singleSelection: BOOLEAN; filler: 0 .. 8191; END; GridViewTemplatePtr = "GridViewTemplate; TextGridViewTemplate itsFontFace: itsFontSize: itsFontColor: itsFontName: END; PACKED RECORD Style; INTEGER; RGBColor; Str255; TextGridViewTemplatePtr Wed, Aug 3, 1988 "TextGridViewTemplate; © 1988 4i Apple Computer, Inc. () 2 Constants ( Template identifiers for views defined in this unit: 'TGridView'; kGridView = 'TTextGridView'; kTextGridView 'TTextListView' ; kTextListView For setting column/row width/height in only one row/column: 1; kOneRow 1; kOneCol = Select Command Identifiers: cCellSelect = cRowSelect = cColumnSelect cVertexSelect 1; 2; 3; 4; Booleans for SetSelection: kExtend = kDontExtend = kHighlight = kDontHighlight kSelect = kDeSelect TRUE; FALSE; TRUE; FALSE; TRUE; FALSE; Booleans for CreateHighlightRgn: kWholeRect = kNotWholeRect = TRUE; FALSE; Fields fnumOfRows: fnumOfCols…

( MacApp™ 2.0b5 Source Listings The following page is a letter from Apple's Software Licensing department which discusses distribution of MacApp. Please note that the source code in these listings is provided for your own use--this package does not give you any rights to distribute them in any form. The MacApp 2.0b5 Source Listings consists of 482 pages of cross-referenced source listings which were created using PasRef, an MPW tool included with the MPW Pascal product. The cross-reference includes the following source files of MacApp and MacApp building blocks (which can be found on the disks contained in the MacApp 2.0b5 product): f (~ 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. 31. 32. 33. 34. 35. 36. 37. 38. UAssociation.p UAssociation.inc1 .p UBusyCursor.p UBusyCursor.inc1 .p UDialog.p UDialog.inc1 .p UFailure.p UFailure.inc1 .p UGridView.p UGridView.inc1 .p Ulist.p Ulist.inc1 .p UMacApp.p UMacApp.Globals.p UMacApp. TEvtHandler.p UM acApp. T Application .p UMacApp.TDocument.p UMacApp.TView.p UMacApp.TWindow.p UMacApp.TScroller.p UMacApp.TControls.p UMacApp. TCommand.p UMacApp.TDeskScrapView.p UMacApp. TPrintHandler.p UMAUtil.p UMAUtil.inc1 .p UMemory.p UMemory.inc1 .p UMenuSetup.p UMenuSetup.inc1 .p UObject.p UObject.inc1 .p Objlib.inc1 .p UPatch.p UPatch.inc1 .p UPrinting.p UPrinting.inc1 .p UTEView.p Page Pages Pages Pages Pages Pages Pages Pages Pages Pages Pages Pages Pages Pages Pages Pages Pages Pages Pages Pages Pages Pages Pages Pages Pages Pages Pages Pages Pages Pages Pages Page Pages Pages Pages Pages Pages Pages 1 2 6 8 12 20 56 59 63 71 104 108 116 147 161 165 200 216 236 247 254 269 271 275 278 284 298 302 314 317 324 326 326 333 335 338 344 367 to 5 7 to to 11 to 19 to 55 to 58 to 62 to 70 to 103 to 107 to 115 to 146 to 160 to 164 to 199 to 215 to 235 to 246 to 253 to 268 to 270 to 274 to 277 to 283 to 297 to 301 to 313 to 316 to 323 to 325 and pages 328 to 333 to 328 to 334 to 337 to 343 to 366 to 373 39. 40. 41. 42. UTE View .Globals.p UTEView.TTEView.p UTEView.TTECommand.p UViewCoords .p Pages Pages Pages Page 374 to 376 377 to 393 394 to 403 404 Each line in the source files is preceded by the number of the file it came from (using the above numbers) and the line number within that file. The cross-reference contains an alphabetical list of all identifiers used in the source files. Following each identifier is a list of the line number with file numbers in parentheses. An asterisk (*) following a line number indicates a definition of the variable or routine. An equal sign (=) indicates an assignment. A line number with nothing following it means a reference to an identifier. Note that the following assembly language and MacApp debugger source files were not included in the listing (interested users can list them from the files on the MacApp 2.0bS disks): CommonObjlib.a Macros.a UBusyCursor.a UFailure.a Ulnspector.p Ulnspector.inc1 .p UMAUtil.a …

Macintosh® Introduction to MacApp 2.0 and Object-Oriented Programming_ ( .. , • (! Draft April 14, 198<) Developer Technical Publications © Apple Computer, Inc. 1989 S APPLE COMPUTER, INC. This manual and the software described in it are copyrighted, with all rights reserved. Under the copyright laws, this manual or the software may not be copied, in whole or part, without written consent of Apple, except in the normal use of the software or to make a backup copy of the software. The same proprietary and copyright notices must be affixed to any permitted copies as were affixed to the original. This exception does not allow copies to be made for others, whether or not sold, but all of the material purchased (with all backup copies) may be sold, given, or loaned to another person. Under the law, copying includes translating into another language or format. You may use the software on any computer owned by you, but extra copies cannot be made for this purpose. The Apple logo is a registered trademark of Apple Computer, Inc. Use of the "keyboard" Apple logo (Option-Shift-K) for commercial purposes without the prior written consent of Apple may constitute trademark infringement and unfair competition in violation of federal and state laws. © Apple Computer, Inc., 1989 20525 Mariani Avenue Cupertino, CA 95014-6299 (408) 996-1010 Apple, the Apple logo, A/UX, I.aserWriter, MacApp, and Macintosh are registered trademarks of Apple Computer, Inc. APDA, AppleTalk, MPW, Finder, MultiFinder, ResEdit, and Rez are trademarks of Apple Computer, Inc. Adobe Illustrator is a trademark of Adobe Systems Incorporated. ITC Garamond and ITC Zapf Dingbats are registered trademarks of International Typeface Corporation. Microsoft is a registered trademark of Microsoft Corporation. POSTSCRIPT is a registered trademark of Adobe Systems Incorporated. UNIX is a registered trademark of AT&T Information Systems. Simultaneously published in the United States and Canada. Contents Figures and tables ix Preface xiii Prerequisites xv Hardware xv · Software xv What you should already know xvi Other books you should have xvii What this manual contains xvii How to use this manual xviii Nomenclature and typographic conventions xix Conventions in the MacApp code xix Graphical conventions xx Where to get information xxii About APDA xxii About Developer Programs xxii 1 Why MacApp? 1 What is MacApp? 3 Programming without MacApp 4 Programming with MacApp 5 The division of labor 5 The benefits of MacApp 7 ill 2 An Introduction to Object-Oriented Programming 9 The big picture 11 Record types and record variables 12 Classes and Instances 13 Flow of control in object.oriented programs 17 Classes 27 Inheritance 28 Method definitions 31 Override methods 32 Objects 34 An instance method 3S Inheritance and override methods 37 Override methods that don't call their inherited method 37 Override methods that do call their inherited method 38 Privacy between instances 41 Ramifications of …

MacApp® 2.0bS Printing Release Notes Curt Bianchi This ERS is separated into three parts. The first part is a general overview of how printing works in MacApp. I felt this was necessary since the original MacApp manual had very limited documentation on printing. The second section describes the view methods related to printing, and the third section describes the TStd.PrintHandler class. How Printing Works in MacApp Printing in MacApp is accomplished by objects called print handlers. MacApp supplies two print handler classes. TP r intHandle r is a "null" print handler that isn't capable of printing: it simply defines the minimal print handler interface. TStdPrintHandler, in the UPrinting unit, fully implements standard Macintosh printing for spooled (ImageWriter®) and non-spooled (LaserWriter®) devices, as well as handling printing-related issues such as page setup and screen feedback of printing infonnation. Printing is accomplished through the cooperation of a print handler and a view. A print handler must always be coupled to a view; otherwise the print handler has nothing to print. Print handlers handle all of the mechanics of printing (the print loop, spooling, communicating with the Print Manager, and so on), while the view performs the actual drawing within each page. A set of view methods exists that are called from the print handler. These methods allow you to customize many aspects of printing for a particular view, without the need to override TStd.PrintHandler. To customize print behavior it is usually sufficient to override the view methods related to printing. It is rare that TStdP rintHandler must be overridden, but you certainly aren't prevented from doing so. A print handler is usually created along with the view it prints, in the document's DoMakeViews method. Only one print handler needs to be created for a hierarchy of views. The print handler will print the view with which it is associated and all of its subviews. Types of Printing Setup Supported by TStdPrintHandler Printing is performed by calling the print handler's Print method. Generally you don't call Print directly. It is called for you by the print handler's DoMenuCommand, in response to Print or Print One commands, or when Finder printing. MacApp will perform different types of setup before calling Print. The types of setup are as follows: Normal Before Print is called, PoseJobDialog is called to gather print job information. This is the technique used when the user chooses the Print menu command Print One No job dialog is displayed. The print job information is set up by validating the print record and forcing all pages to be printed. Therefore, any valid print record information will be carried forward from the last time the print handler printed. This is the technique used when the user chooses the Print One menu command. ( ") , Wed, Aug 3, 1988 © 1988 ti Apple Computer 1 Finder The page setup and job dialogs may be posed before printing. The use of th…

MacApp 2.0 Globals ( © 1988 Apple Computer. Inc. The MacApp unit defines a number of global constants, variables, types, procedures, and functions. The globals documented here are described for your reference, but you will probably not use many of them directly. MacApp methods use the globals, while the application code very rarely, if ever. Constants This section documents the constants defined as part of the MacApp package. Although the values of the constants are given here for your information, those values are subject to change. (In some cases, when the values are very likely to change, they are not given here.) Normally, you should simply use the constant identifier and not concern yourself with its value. The constants are categorized according to purpose. Copyright constant kcopyright = •copyright 1984, 1985, 1986, 1987, 1988 Apple Computer Inc.•; Used to store the copyright notice for MacApp. Menu constants kMBaroisplayed "' 128; kMBarNotDisplayed 129; = Identifies the menu bar resource that holds the menus that are initially displayed. Identifies the menu bar resource that holds menus that are not initially displayed. These menus include buzzword menus and menus that may be displayed later. Identifies menu bar resource that holds menus that are submenus or pop-up menus. These menus will be installed when the application is initializ.ed. The following constants identify the standard menus shared by all Macintosh applications. kMBarHierarchical mApple "' l; mFile 2; mEdit = 3; mLastMenu = 63; mDebug = 900; Identifies the Apple menu, the leftmost menu in the menu bar. Identifies the File menu. Identifies the Edit menu. Identifies the last menu managed by MacApp's DoSetupMenus methods. This commands in menus above this number are never unchecked or disabled by MacApp. Identifies the Debug menu. (~. MacApp 2.0 Globals 10/3/88 Page 1 Command numbers The command numbers listed here are passed to your methods, generally to gTarget.DoMenuCommand. Most are passed as a result of the user picking a menu command; . command numbers are also used for other types of commands, such as typing or mouse commands. When the description says "MacApp catches this," that means that the MacApp DoMenuCommand methods will handle those command numbers, often by calling application methods. cNocommand Command number representing no command. MacApp catches this. cAboutApp Identifies the About <AppNme>... command. MacApp catches this. File menu commands Identifies the New command MacApp catches this. (See also cNew = 10; cNewLaat.) cNewLast = 19; csave = 30; cClose = 31; cSaveAs = 32; cSaveCopy = 33; cRevert = 34; cOpen = 20; cOpenLast = 29; cPageSetup = 176; cPrintOne = 177; cPrint = 178; cPrintToFile • 179; cPrFileBase a 176; cPrFileMax = 195; cPrViewBase = 201; cPrViewMax = 250; cQuit = 36; MacApp 2.0 Globals Identifies the last New command. MacApp provides a range of New commands for applications that have different documen…

, •® Macintosh® The MacApp® Interim Manual (:' Working Draft 4 (APDA) June 14, 1988 ©Apple Computer, Inc. 1988 S APPLE COMPUTER, INC. This manual and the software described in it are copyrighted, with all rights reserved. Under the copyright laws, this manual or the software may not be copied, in whole or in part, without written consent of Apple, except in the normal use of the software or to make a backup copy of the software. The same proprietary and copyright notices must be affixed to any permitted copies as were affixed to the original. This exception does not allow copies to be made for others, whether or not sold, but all of the material purchased (with all backup copies) may be sold, given, or loaned to another person. Under the law, copying includes translating into another language or format. You may use the software on any computer owned by you, but extra copies cannot be made for this purpose. ©Apple Computer, Inc., 1988 20525 Mariani Avenue Cupertino, CA 95014 (408) 996-1010 Apple, the Apple logo, LaserWriter, Lisa, MacApp, and Macintosh are registered trademarks of Apple Computer, Inc. APDA, MPW, MultiFinder, RESEDIT are trademarks of Apple Computer, Inc. ITC Avant Garde Gothic, ITC Garamond, and ITC Zapf Dingbats are registered trademarks of International Typeface Corporation. Microsoft is a registered trademark of Microsoft Corporation. POSTSCRIPT is a registered trademarlc of Adobe Systems Incorporated. Varityper is a registered trademark, and VT600 is a trademarlc, of AM International, Inc. Simultaneously published in the United States and Canada. 6/14/88 Table of Contents Preface About This Manual ix Prerequisites x Hardware x Software x What you should already know x1 What this manual contains xii How to use this manual xii Notation xiii Conventions in the MacApp code xiv Other books you should have xiv 0 Chapter 1 Why MacApp? 1 What is MacApp? 2 Programming without MacApp 3 Programming with MacApp 4 The division of labor 5 The benefits of MacApp 7 Chopter2 An Introduction to Object-Oriented Programming 9 The big picture 10 Record types and record variables 12 Object classes and object instances 13 Flow of control in object-oriented programs 18 Working Draft 4 (APDA) 6/14/88 MacApp 2.0 Tutorial Object classes 30 Inheritance 31 Method definitions 35 Override methods 36 Object instances 39 An instance method 40 Override methods 43 Override methods that don't call their inherited method 43 Override methods that do call their inherited method 44 Privacy between instances 47 Ramifications of object-oriented programming 47 Chapter3: Object Pascal 49 Object Pascal file organization 50 Object class definitions 55 Field declarations 56 Method declarations 56 Override method declarations 58 Object Instances 59 Record handles and record instantiations 59 Instantiation through record variables 59 Instantiation through record pointers 60 Instantiation through record handles 60 Object references and object insta…

( MacApp 2.0bS View Architecture Release Notes Curt Bianchi Introduction This document describes the architecture for MacApp 2.0's view classes, and describes all methods and fields of the view classes defmed in UMacApp. This represents the major change between MacApp 1.x and MacApp 2.0. The motivations for introducing the new architecture are To simplify the architecture To provide a class that is suitable as the basis for all displayed objects, from windows to controls To have a single nesting and layering mechanism for display objects To support large coordinate systems To simplify the implementation of display objects within views, including controls and fields The MacApp 1.x Display Achitecture If you're already familiar with the MacApp 1.x display architecture, you should skip this section. If you're not, here it is in a nutshell. The old display architecture consists basically of three classes: TWindow, TF rame, and TView. TWindow A TWindow object represents a Window Manager window. As such, it handles opening, closing, moving, resizing, activating, and deactivating a window. TFrame A TFrame object is a rectangular area within a window, handling scrolling and coordinate transformations. TFrame objects are similar to QuickDraw grafports in that each has its own coordinate system. Frames typically tile windows. In the simplest case, windows have a single frame whose size is that of the window's content rectangle. However, windows can be subdivided into sections by using multiple frames. Furthermore, frames can be nested inside one another. Within frames are displayed Control Manager controls (for example, scroll bars) and a portion of a view, or a collection of subframes, or both. TView A TView object renders the display image of a document's data and responds to mouse clicks and keystrokes in the display image. It is a rectangular area of any size up to 30,000 pixels in each dimension. A view is always displayed in a frame. The frame's scroll bars determine what part of the view is actually visible, since large views cannot be displayed in their entirety. Wed, Aug 3, 1988 © 1988S Apple Computer 1 -o MDemoTeHt.p PROGRAM DemoText; USES {$LOAD Mac I ntf.LOAD} MemTypes, QuickDraw, OSI ntf, Tooll ntf, Pack I ntf, {$LOAD UMscApp.LOAD} UObject, ULfat, UMacApp, {$LOAD} UPri nti ng, tQ:. ~MN, ~ MDemoTeHt.p TWindow TFrame Niew PROGRAM DemoText; USES {$LOAD Mee I ntf.LOAD} MemTypes, QuickDraw, OSlntf, Toollntf, Pecklntf, {$LOAD UMecApp.LOAD} UObject, Ulist, UMecApp, {$LOAD} UPri nti ng, UTEView, UDemoText; VAR gDemoTextApplication: TDemoTextA ppli ceti on; {$S Main} BEGIN I nitTool box( 8); I nit Printing; New(gDemoTextApplication); gDemoTextApplicetion .I De moTextAppl ication; gDe moTextAp plication.Run; END. Figure l: Old MacApp Display Architecture Wed.Aug 3.1988 © 1988 S Apple Computer 2 Figure 1 shows a typical text edit window and the MacApp objects used to build it. Here, the TWindow object displays the grow icon (…

Apple Confidential ti. Apple. Macintosh Coprocessor Platform™ Developer's Guide Final Draft February 20, 1989 . o APPLE COMPUTER, INC. This manual is copyrighted by Apple, with all rights reserved Under the copyright laws, this manual may not be copied, in whole or in part, without the wrinen consent of Apple Computer, Inc. This exception does not allow copies to be made for others, whether or not sold, but all of the material purchased may be sold, given or lent to another person. Under the law, copying includes translating into another language. © Apple Computer, Inc., 1987, 1988 20525 Mariani Avenue Cupertino, California 95014 (408) 996-1010 Apple, the Apple logo, AppleTalk, LaserWriter, and Macintosh are registered trademarks of Apple Computer, Inc. LocalTalk, the Macintosh Coprocessor Platform, MR-DOS, and MPW are trademarks of Apple Computer, Inc. AST and AST-ICP are trademarks of AST Research, Inc. DEC is a trademark of the Digital Equipment Corporation. EtherTalk ls a trademark of ?? Magnetic Resonance Imaging (MRI) -ls this trademarked at all, or just an industry term? NuBus is a trademark of Texas Instruments. Open Systems Integration (OSI) - trademark? or any acknowledgement for this proposed standard Systems Network Architecture (SNA) is a registered trademark of International Business Machines Corporation. just the initials or the whole thing? Simultaneously published in the United States and Canada. ( Contents Figures and tables I xx Preface I I 1 What Is MCP? I 1-1 The components of MCP I 1-2 The MCP hardware I 1-3 The MCP software I 1-4 MR-DOS I 1-4 Apple IPC I 1-6 Developmental diagnostics I 1-6 .. Developing with MCP I 1-6 Development opportunities and applications I 1-7 Off-loading task processing I 1-8 Parallel processing I 1-8 Interfacing or controlling I 1-8 Data acquisition I 1-9 Intemetworking I 1-9 Limitations I 1-9 2 Getting Started I 2-1 Preparing to use MCP I 2-2 Installing the MCP card I 2-2 Installing MCP software I 2-5 Installing the Apple IPC driver I 2-6 Running a sample program I 2-6 Selecting files for the sample exercise I 2-7 Downloading files to the card I 2-9 Verifying the sample exercise I 2-9 Where do you go from here? I 2-12 1 Contents 3 Introduction to the MCP Software Interface I 3-1 What is MR-DOS? I 3-2 MR-DOS primitives I 3-2 MR-DOS utilities I 3-3 MR-DOS managers I 3-3 Echo Manager I 3-4 IncerCard Communications Manager OCCM) I 3-4 Name Manager I 3-5 Print Manager I 3-5 Remote System Manager (RSM) I 3-5 Timer library and Timer Manager I 3-6 Trace Manager I 3-6 What is Apple IPC? I 3-7 Apple IPC driver I 3-7 Apple IPC library I 3-8 . Apple IPC managers I 3-8 Functions of MCP software I 3-9 Using messages for interprocess communication I 3-9 Message structures I 3-9 Mechanisms for data transfer I 3-14 Message and status codes I 3-14 The client/server relationship I 3-15 Clients and servers running on a smart card under MR-DOS I 3-15 Clients and servers running on the Macintosh II…