DOCSLIB.ORG

Macintosh Technical Notes • Developer Technical Support Index June 1992

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Macintosh Technical Notes • Developer Technical Support Index June 1992 Macintosh Technical Notes • Developer Technical Support Index June 1992 Note: Trap names can appear in two different places: under the name of the trap alphabetically and at the end of the index, prececded by an underscore U. 107,744 280 abusive 276 %_InitObj 105 accelerator upgrades 285 %_MethTables 93, 105 acceptChildDiedEvents 205 %_SeIProcs 93 acceptSuspendResumeEvents 205 '030 129,230 access error 292 -mc68881 146 access privileges 186 .Aout driver 249 accRun 248 .ATP driver 224, 250 AClose 311 .Bout driver 102, 102 Action Atom 75 .ENET driver 271 Activate Palette 211 .MPP driver 224, 250, 311 ad-hoc 292 .Print driver 102 ADB 143, 160,206,266 .XPP driver 250, 270 boot process 206 /BERR 292 cables 206 /HALT 292 driver installation 206 1.4 MB 230 microcontroller 206 1.44 MB 230 references 206 128K ROM 198, 224,232 service routine 206 24-bit addressing 212, 213, 285 ADBReInit. 143 24-bit mode 213, 228,229 ADBS 206 • 32-bitaddressing 212,275,285 AddDrive 36, 108 32-bit bus 230 AddNocIe 311 32-bit c1ean 212 AddReference 2 32-bit clean ROM 176 AddResMenu 191, 198 32-bit mode 205, 213, 228, 229 address arithmetic 213 32-Bit QuickDraw 193,229, 275, 276, 277, 289 addressing 212, 213 32K barrier 256 24-bit. 212, 213 4 Mbit DRAMs .176 32-bit. 213 400K disk 70 ADelNode .311 68000 PDS 230 AEP 270 68030 PDS 230 ADEV .311 80-bit format 146 AFP 186, 195 800K disk 70 afraid to ask 171 8·24 GC Display Card 289 AGetInfo 311 96-bit format. 146 AGetN"odeRef 311 @ operator 42, 117 AInstall .311 AIUX 212, 229,278,283,284 Alarm Clock 85, 184 system calls 283 Allegro Common Lisp 231 AO 228 AllocContig 218 A5 25, 136, 180, 208,239,256 allSlaveBlockSizes 288 A5Init 256 alpha version 189 A5Size 256 ALRT 23 AAddNode 3II alternate screen 113 ABPasIntf. 132 alternate screen buffer.. 2, 126 ABridge 9 alternate sound buffer 2, 126 • absolute pointing device 266 ANSI 208 Index 1 of 19 Macintosh Technical Notes ANSI C 246,3l3 audio CD-ROM 66 AOpen 311 auto-polling 206 app4Evt. 158 automatic style substitution 198 APPL 29 autoTrack 196 Apple Desktop Bus 160, 206, 266, 271 auxiliary window list 227 Apple Desktop Bus Manager 206 AUX_FS_FREE_SPACE 229 • Apple HD SC Setup 134 back off algorithm 270 Apple menu 85, 180, 184 BackColor 73 Apple Sound Chip 19, 230, 268 background 158. 180, 192 AppieCD SC 293 printing 192 AppleShare 66, 114, 115, 116, process 180 ................................137, 165, 167, 186,216,229 bad block sparing 287 AppleTalk 9,20, 121. 132; 133, 142, 195. 199, badMoveErr 229 .........................201,224.225,250,270,311,313 baseAddr 41.275 AppleTalk Echo Protocol., .270 BCD 189,293 AppleTalk Filing Protocol.. 186. 195 BCLR 2 AppleTalk Manager..........9. 195. 199.201.224,225, Berkeley 4.2 File System 229 ............................................................250.270 beta version 189 AppleTalk Phase 2 249.250.270, 311 bHasPersonalAccessPrivileges 186 AppleTalk Session Protocol.. 195 BigBro 256 AppleTalk Transaction Proto 9, 20, 270 binary coded decimal 293 AppleTalk Transition Queue .250, 311 bitmap .41, 117. 120, 193,277 Apple_Driver 258 BitMapRgn 193 appIFont. 191 BitMapToRegion 193 application 29, 48.192,211,242 black and white 276 font 192, 242 Black Lectroids 247 palette 2ll blessed folder 20. 67, 129. 229 signature 29, 48 block servers 20 application parameters 256 block transfers 288 ApplZone 2 BNDL 29. 48, 147.210.217 array-dialog-item 231 Bo3bdar 139 arrow keys 160 boards 234 artificial intelligence 231 boot blocks I13,134 ASC 19 boot time 247 • asexual 247 BootDrive 77 ASIC 271,291 booting 134 ASP 195 brain-damaged 248 assembly language 200, 223 break, serial. 56 asynchronous 249, 271 BSET 2 driver 249 BufPtr 2, 81, 285 I/O 271 bug serial communication 249 ADB 206 atDrvrVersNum 129,250 Allegro Common Lisp 231 atom 75,75 AppleShare 137 ATP 9,20,270 ChangedResource 188 ATPGetRequest 20 FCBPBRec 87 ATPLoad 20,224 GetVlnfo 157 ATPPBPtr 199 LaserWriter 192 ATPResponse 20 LaserWriter ROMs 123 ATPUserData 250 MacApp 280 ATTransCableChange 311 MPW 200 ATTransCancelClose .311 PBLockRange 186 ATTransCancelNameChange .311 PrGeneral 173 ATTransClose 31 I Script Manager 264 ATTransClosePrep .31 I SCSI 96 ATTransNameChangeAskTask 311 SCSI Manager 258 ATTransNameChangeTellTask 3ll TEScroll 22 ATTransNetworkTransition .311 TextEdit 82, 131, 267 ATTransOpen 311 WaitNextEvent 177 ATTransSpecdChange .311 bundle .40.48, 147. 189 • 2 of 19 Index Developer Technical Support June 1992 Bus Error Exception Processing 292 CInfoPBRec 204 bus error handler.. .292 ckid 269 bus locking 221 Class Info Table 239 bus master 288 C1eanupDeRezzedViews 280 byte smearing 282 clearDev 215 • byteCount. 171 click-click mode 260 C 164, 166,200, 246, 265 clikLoop 82 C++ 265 clikS tuff 127 C++ 281 clip region 59, 72 cable 10, 65 clipping 72 video .144 ClipRect. 59 Cable Range Transition Event .311 CLOS 231 cache 117,261 Close 278 CacheCom 81 close transition 250 caching 81 CloseASWorld 256 calcCRgns 212 CloseResFi1e 116 CallAddr 250 C1oseWD 218 callback procedures 265 CLUT 120,244 callback routines 256 clut. 277 calling conventions 256 CMOS 291 canBackground 158, 180,205,231 CODE 220, 228, 256 canceling 263 code card power allocation 260 segment. 53 cards 234 self modifying 117 NuBus 288 code module 256 caring 161 color 277 case sensitive 229 cursor. 244 CatMove 218 dialog 231 CCR 2 look-up table 120, 277 CD-ROM 66,229,293 mapping 277 disc formats 209 menu 231 driver 271,293 models 259 Foreign File Access 209, 293 printing 73, 120 • formats 209 table 277 High Sierra 209 Color QuickDraw 41, 73, 120, 129, 163, ISO 9660 209 . .......................................230, 244, 259, 275, 277 Primary Vol. Descriptor .209 colorization 163, 277 Standard Identifer Field 209 Command key 263 Val idator. 209 Command-period 263 CD001 209 Common Lisp Object System 231 CDEF 23, 196,212 common signal 230 message parameter 196 compact disc 209, 293 param parameter .196 CompactMem 51 cdev 215, 251 compatibility 2, 25, 83, 103, 117, 126, 129, IIfx Serial Switch 271, 284 .................155, 156, 176,212,227,229,230,232, keyboard 160 .......................................268,271,273,282,284 messages 215 HFS 44 cdFlags .277 large-screen displays 100 cell rectangle pointer .279 Standard File 47 CGrafPort 120, 211,259 compleat. 274 ChangedResource 188 completion routine 180 Char2Pixel 207 compressed data 171 charcter spacing 72 condition code register 2 CharWidth 26, 82 configuration fi1e 115 CheckRsIRecord 173 Connect Control Blocks 161 checksum 7, 258 connector, external drive 10 checkS umFlag 311 consenting user 276 Chooser 197 control call 272 ChooserBits .250 control definition functions 196 • cicn 275 Control Manager. 196, 203, 212 Index 3 of 19 Macintosh Technical Notes Control Panel.. 134, 215, 251 deathdwarf 168 Control Panel Device 215, 251 debugger FKEY 256 controlErr 161 debugging 7,42,51, 151,235 ControlHandle 197 Declaration ROM 230 controls 197 declaration ROM 288 coprocessor 235, 236 decoding PICTs 171 • copy protection 117 deferred task 221 CopyBits 55, 163 Deferred Task Manager 271 copyDev 215 definition procedure 227 CopyMask 163 Delay 2 CopyPalette 211 depth 276 Coral Software 231 dereferenced handle 232 countryCode 189 dereferencing 213 CPUFlag 2 design 227 CreateResFile .101, 214 derived class 307 creator 29 desk accessory 5, 23, 184,248 csCode 272 DeskHook 247 csParam 262, 272 Desktop 194, 210, 247 CTRL 23 Desktop Bus 206 CTS 56 Desktop file 29,48, 134,210 ctseed 277 limitations 210 CurDirStore 80 destRect. 237 CurrentA5 25, 136 development version 189 CURS 215 Device Control Entry 248, 272 cursing 244 device driver 56, 71, 184, 187,229,258,262,278 cursorDev 215 Device Manager 197,257,262,272,293 curSysEnvVers 129 device packages 197 CUST 135 device server 20 custom WDEF 290 device-independent printing 122, 152 cutDev 215 Diagnostic Raw Track Dump 272 CWindow 211 dialog CWindowPtr 120 filter 34 damn the fragmentation 281 hook 47 DashedLine 91 item 112 • DashedStop " 91 item text behavior 267 data cache 261 modeless 5 Data Cycle Fault Address 292 user item 34 Data Delivery Protocol 270 Dialog Manager 203,251,267 Data Fork 203 DialogSelect. 34 data server 20 DIBadMount. 70 data structures 227 DirCreate " " 218 Datagram Delivery Protocol 9, 270 direct color device 275 dataHandle, in WindowRecord 79 Direct Memory Access 285 dates 264 directory name 226 DB-19 10 DirID 69, 77, 140,229,238,246 DB-25 10 disc 209 DB-9 10 discipline 117,151 dBoxProc 180 disk drive, foreign 28 DCE 71, 108, 187,248,250,272 Disk Driver 272 dCtIDriver 71, 248 disk driver 287 DCtIEntry 266 SCSI 285 dCtlPosition 187, 272 disk errors 287 OCtlQHdr 250 Disk First Aid 94, 134 dCtIRefNum 56 disk initialization 70 dCtIStorage 266 Disk Initialization Package 287 DDP 9,270 DisposeA5World 256 dead key 160 ditherCopy 275,277 dead keys 263 DITL 23,251 death 276 DIZero 70 death by ROM .117 DlgCopy 215 • 4 of 19 Index Developer Technical Support June 1992 DIgCut. 215 envMacIIcx 129 DlgDelete 215 envMacIIfx 129 DIgPaste 215 env MacIIx 129 DLOG 23 envPortable 129 DMA 221, 261, 285 envPortADBKbd 129 • burst transfer 230 envPortISOADBKbd 129 dNeedTirne 248 envSE30 129 DoCaret. 82 envSeITooBig 129 DoDraw 82 envStdISOADBKbd 129 doFace 207 EOF 188 doToggle 207 Erase calls 72 double-sided disk 70 Erase Disk 287 downloading font... 217 ERIK 126 dQDrvSize 36 error handling, bus errors 292 draft mode 72 errors, NuBus 292 DraftBi ts .128 ETAB 84 DragHook 247 EtherTalk 250, 271, 311 DRAM 176 event dRamBased 71 key code 160 DrawChar 26 key-down 263 drawCntl 196 mask 202 DrawControls 203 mouse-moved 205 drawing 41,60,275,277 network 142 icons 55 queue 229 offscreen 120,277 Event Manager 202,229 on the desktop 194 EventAvail.
Load more

Recommended publications
  • Automated Support for Software Development with Frameworks
    Automated Support for Software Development with Frameworks Albert Schappert and Peter Sommerlad Wolfgang Pree Siemens AG - Dept.: ZFE T SE C. Doppler Laboratory for Software Engineering D-81730 Munich, Germany Johannes Kepler University - A-4040 Linz, Austria Voice: ++49 89 636-48148 Fax: -45111 Voice: ++43 70 2468-9431 Fax: -9430 g E-mail: falbert.schappert,peter.sommerlad @zfe.siemens.de E-mail: [email protected] Abstract However, the object–oriented concepts and frameworks intro- duce additional complexity to software development. A framework This document presents some of the results of an industrial research gains its functionality by the cooperation of different components. project on automation of software development. The project’s ob- Thus, the use of a single component may be based on its interrela- jective is to improve productivity and quality of software devel- tionships with others that must be understood and mastered by the opment. We see software development based on frameworks and application developer. libraries of prefabricated components as a step in this direction. Present work on software architecture also emphasizes the in- An adequate development style consists of two complementary terrelationships between software components depending on each activities: the creation of frameworks and new components for other to get control on this additional complexity. There the term de- functionality not available and the composition and configuration sign pattern is used to describe and specify component interaction of existing components. mechanisms in an informal way[Pree, 1994a][Buschmann et al., Just providing adequate frameworks and components does not 1994][Gamma et al., 1994].
    [Show full text]
  • Comprehensive Support for Developing Graphical Highly
    AN ABSTRACT OF THE THESIS OF J-Iuan -Chao Keh for the degree of Doctor of Philosophy in Computer Science presented on July 29. 1991 Title:Comprehensive Support for Developing Graphical. Highly Interactive User Interface Systems A Redacted for Privacy Abstract approved: ed G. Lewis The general problem of application development of interactive GUI applications has been addressed by toolkits, libraries, user interface management systems, and more recently domain-specific application frameworks. However, the most sophisticated solution offered by frameworks still lacks a number of features which are addressed by this research: 1) limited functionality -- the framework does little to help the developer implement the application's functionality. 2) weak model of the application -- the framework does not incorporate a strong model of the overall architecture of the application program. 3) representation of control sequences is difficult to understand, edit, and reuse -- higher-level, direct-manipulation tools are needed. We address these problems with a new framework design calledOregon Speedcode Universe version 3.0 (OSU v3.0) which is shown, by demonstration,to overcome the limitations above: 1) functionality is provided by a rich set of built-in functions organizedas a class hierarchy, 2) a strong model is provided by OSU v3.0 in the form ofa modified MVC paradigm, and a Petri net based sequencing language which together form the architectural structure of all applications produced by OSU v3.0. 3) representation of control sequences is easily constructed within OSU v3.0 using a Petri net editor, and other direct manipulation tools builton top of the framework. In ddition: 1) applications developed in OSU v3.0 are partially portable because the framework can be moved to another platform, and applicationsare dependent on the class hierarchy of OSU v3.0 rather than the operating system of a particular platform, 2) the functionality of OSU v3.0 is extendable through addition of classes, subclassing, and overriding of existing methods.
    [Show full text]
  • Evolution and Composition of Object-Oriented Frameworks
    Evolution and Composition of Object-Oriented Frameworks Michael Mattsson University of Karlskrona/Ronneby Department of Software Engineering and Computer Science ISBN 91-628-3856-3 © Michael Mattsson, 2000 Cover background: Digital imagery® copyright 1999 PhotoDisc, Inc. Printed in Sweden Kaserntryckeriet AB Karlskrona, 2000 To Nisse, my father-in-law - who never had the opportunity to study as much as he would have liked to This thesis is submitted to the Faculty of Technology, University of Karlskrona/Ronneby, in partial fulfillment of the requirements for the degree of Doctor of Philosophy in Engineering. Contact Information: Michael Mattsson Department of Software Engineering and Computer Science University of Karlskrona/Ronneby Soft Center SE-372 25 RONNEBY SWEDEN Tel.: +46 457 38 50 00 Fax.: +46 457 27 125 Email: [email protected] URL: http://www.ipd.hk-r.se/rise Abstract This thesis comprises studies of evolution and composition of object-oriented frameworks, a certain kind of reusable asset. An object-oriented framework is a set of classes that embodies an abstract design for solutions to a family of related prob- lems. The work presented is based on and has its origin in industrial contexts where object-oriented frameworks have been developed, used, evolved and managed. Thus, the results are based on empirical observations. Both qualitative and quanti- tative approaches have been used in the studies performed which cover both tech- nical and managerial aspects of object-oriented framework technology. Historically, object-oriented frameworks are large monolithic assets which require several design iterations and are therefore costly to develop. With the requirement of building larger applications, software engineers have started to compose multiple frameworks, thereby encountering a number of problems.
    [Show full text]
  • 51. Graphical User Interface Programming
    Brad A. Myers Graphical User Interface Programming - 1 51. Graphical User Interface Programming Brad A. Myers* Human Computer Interaction Institute Carnegie Mellon University 5000 Forbes Avenue Pittsburgh, PA 15213 [email protected] http://www.cs.cmu.edu/~bam (412) 268-5150 FAX: (412) 268-1266 *This paper is revised from an earlier version that appeared as: Brad A. Myers. “User Interface Software Tools,” ACM Transactions on Computer-Human Interaction. vol. 2, no. 1, March, 1995. pp. 64-103. Draft of: January 27, 2003 To appear in: CRC HANDBOOK OF COMPUTER SCIENCE AND ENGINEERING – 2nd Edition, 2003. Allen B. Tucker, Editor-in-chief Brad A. Myers Graphical User Interface Programming - 2 51.1. Introduction Almost as long as there have been user interfaces, there have been special software systems and tools to help design and implement the user interface software. Many of these tools have demonstrated significant productivity gains for programmers, and have become important commercial products. Others have proven less successful at supporting the kinds of user interfaces people want to build. Virtually all applications today are built using some form of user interface tool [Myers 2000]. User interface (UI) software is often large, complex and difficult to implement, debug, and modify. As interfaces become easier to use, they become harder to create [Myers 1994]. Today, direct manipulation interfaces (also called “GUIs” for Graphical User Interfaces) are almost universal. These interfaces require that the programmer deal with elaborate graphics, multiple ways for giving the same command, multiple asynchronous input devices (usually a keyboard and a pointing device such as a mouse), a “mode free” interface where the user can give any command at virtually any time, and rapid “semantic feedback” where determining the appropriate response to user actions requires specialized information about the objects in the program.
    [Show full text]
  • Design and Implementation of ET++, a Seamless Object-Oriented Application Framework1
    Design and Implementation of ET++, a Seamless Object-Oriented Application Framework1 André Weinand, Erich Gamma, Rudolf Marty Abstract: ET++ is a homogeneous object-oriented class library integrating user interface building blocks, basic data structures, and support for object input/output with high level application framework components. The main goals in designing ET++ have been the desire to substantially ease the building of highly interactive applications with consistent user interfaces following the well known desktop metaphor, and to combine all ET++ classes into a seamless system structure. Experience has proven that writing a complex application based on ET++ can result in a reduction in source code size of 80% and more compared to the same software written on top of a conventional graphic toolbox. ET++ is im- plemented in C++ and runs under UNIX™ and either SunWindows™, NeWS™, or the X11 window system. This paper discusses the design and implementation of ET++. It also reports key experience from working with C++ and ET++. A description of code browsing and object inspection tools for ET++ is included as well. ET++ is available in the public domain.2 Key Words: application framework, user interfaces, user interface toolkits, object-oriented programming, C++ programming language, programming environment 1 Introduction Making computers easier to use is one of the reasons for the current interest in interactive and graphical user interfaces that present information as pictures instead of text and numbers. They are easy to learn and fun to use. Constructing such interfaces, on the other hand, often requires considerable effort because they must not only provide the functionality of conventional programs, but also have to show data as well as manipulation concepts in a pictorial way.
    [Show full text]
  • Rhapsody Developer's Guide
    Jesse Feiler AP PROFESSIONAL AP Professional is a division of Academic Press Boston San Diego New York London Sydney Tokyo Toronto Find us on the Web! http:/ /www.apnet.com This book is printed on acid-free paper. @ Copyright © 1997 by Academic Press. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopy, recording, or any information storage and retrieval system, without permission in writing from the publisher. Excerpts from Chartsmith are copyright © 1997 by Blacksmith, Inc. All rights reserved. Excerpts from OpenBase are copyright © 1997 by OpenBase International, Ltd. All rights reserved. Excerpts from Create are copyright © 1997 by Stone Design, Inc. All rights reserved. Excerpts from OmniWeb are copyright © 1997 by Omni Development, Inc. All rights reserved. Excerpts from TIFFany are copyright © 1997 by Caffeine Software. All rights reserved. All brand names and product names mentioned in this book are trademarks or registered trademarks of their respective companies. Academic Press 525 B Street, Suite 1900, San Diego, CA 92101-4495 1300 Boylston Street, Chestnut Hill, MA 02167 United Kingdom Edition published by ACADEMIC PRESS LIMITED 24-28 Oval Road, London NW1 7DX ISBN 0-12-251334-7 Printed in the United States of America 97 98 99 00 CP 9 8 7 6 5 4 3 2 1 Table of Contents Advanced Mac Look and Feel i Y e llo w Box Mac OS 0P6NSTgP based JaCT^ Core OS: Microkernel, ^0, Fiie System... |Power Macintosh, PowerPC Piatform Hardware Semantics T ables ........................................................................................... xv Preface...........................................................................................................
    [Show full text]
  • Garnet Comprehensive Support for Graphical, Highly Interactive User Interfaces
    Garnet Comprehensive Support for Graphical, Highly Interactive User Interfaces Brad A. Myers, Dario A. Giuse, Roger B. Dannenberg, Brad Vander Zanden, David S. Kosbie, Edward Pervin, Andrew Mickish, and Philippe Marchal Carnegie Mellon University ser interface software is difficult terface Builder, Smethers Barnes’ Proto- and expensive to implement.’ typer for the Macintosh, and UIMX for X U Highly interactive interfaces are Windows. These programs let a designer among the hardest to create, since they Garnet helps create place only preprogrammed interaction must handle at least two asynchronous in- techniques in windows, and they usually put devices (such as a mouse and key- highly interactive user allow only a few parameters to be set. board), real-time feedback, multiple win- interfaces by Often, a designer will type the name of a dows, and elaborate, dynamic graphics. procedure to be called when the interaction The Garnet research project is creating a emphasizing easy technique is executed. Designers cannot set of tools to aid the design and implemen- modify or design the interaction techniques tation of highly interactive, graphical, di- specification of object themselves, and the interface builders do rect manipulation user interfaces. Garnet behavior, often by not address application-specific graphics also helps designers rapidly prototype dif- at all. ferent interfaces and explore various user demonstration and A user interface management system interface metaphors during early product without programming. helps a designer handle the dialogue, or design. sequencing, aspects of the user interface Most graphical interfaces are created - that is, what happens after each user using toolkits, collections of interaction action. Such systems have generally not techniques (sometimes called “widgets” or addressed the creation of toolkit compo- “gadgets”) such as menus, scroll bars, and nents (menus, scroll bars, etc.) or the spec- buttons.
    [Show full text]
  • Program Frameworks
    7. Program Frameworks Overview: 7.1 Introduction to program frameworks 7.2 Program frameworks for User Interfaces: - Architectural properties of GUIs - Abstract Window Toolkit of Java Many software systems • have similar subtasks • use common communication mechanisms • share components • are based on the same architectural pattern For example, many software systems • have a graphical user interface • communicate via remote procedure call • have applications that share components • are based on the three-tier architectural pattern 29.06.15 © A. Poetzsch-Heffter, TU Kaiserslautern 1 If systems share properties, there is a chance to reuse • architectural and design knowledge • implementation techniques • implementation parts • communication infrastructure An important method to support reuse is the construc- tion of frameworks that capture the shared properties. 7.1 Introduction to Program Frameworks • Program frameworks are an important technique for software reuse. • They are usually developed for certain tasks or domains. • From a static point of view, a program framework is an extensible and adaptable system of modules or classes that implement the core functionality and communication mechanisms of a general task or domain. 29.06.15 © A. Poetzsch-Heffter, TU Kaiserslautern 2 Program frameworks are written in some programming language (e.g. C, C++, or Java). Depending on the language, the elements of a program framework are • procedures, • modules, • classes, • interfaces, • or similar programming elements. In the following, we give answers to two questions: 1. What is the distinction between a program framework and an arbitrary set of library classes? 2. What is the distinction between program frameworks and other kinds of frameworks? Both answers will help to understand the relation between architectural properties and program frameworks.
    [Show full text]
  • Carbon: an Essential Element of Mac OS X
    ADC March 2001 2/6/01 1:44 PM Page 1 Apple Developer Connection Direct Carbon: An Essential Element of Mac OS X ne of the things that makes Mac OS X unique is its integra- developers, while at the same time delivering tion of five separate application runtime environments: all the performance, features, and reliability OCarbon, Cocoa, Classic, Java, and BSD. Never before has an that Mac OS X has to offer. About 70 percent operating system offered developers so many options. This series of of the classic Mac OS APIs are fully support- articles will give you the information you need to make an informed ed, and Carbon adds many new APIs specifi- decision as to which of these environments is right for your applica- cally to take advantage of Mac OS X. tion on Mac OS X. This month, I’m going to talk about Carbon and what it offers you as a Macintosh developer. What Diamonds Are Made Of A Brief History of Carbon Carbon offers a wealth of features to support and accelerate your Carbon represents the evolution of the Mac OS API, from a single- Mac OS X development efforts. Whether you’re new to the platform, user, cooperatively scheduled system, to a modern multi-user system or an old-timer, here are some of the reasons why you’ll find Carbon with memory protection and preemptive multitasking. Carbon a solid foundation for your software product: sprang from Apple’s desire to provide a gentle migration path for • Broad Language Support Apple provides interfaces, compilers, and tools for Carbon programming in C and C++, while other languages such as BASIC and FORTRAN are offered by other tool vendors.
    [Show full text]
  • Develop-17 9403 March 1994.Pdf
    develop, The Apple Technical Journal, E D I T O R I A L S T A F F a quarterly publication of Apple Computer’s Editor-in-Cheek Caroline Rose Developer Press group, is published in March, Technical Buckstopper Dave Johnson June, September, and December. Our Boss Greg Joswiak This issue’s CD. The develop Bookmark CD (or His Boss Dennis Matthews the Developer CD Series disc, Reference Library Review Board Pete (“Luke”) Alexander, edition) for March 1994 or later contains this Jim Reekes, Bryan K. (“Beaker”) Ressler, issue and all back issues of develop along with the Larry Rosenstein, Andy Shebanow, Gregg code that the articles describe. The develop issues Williams, Dean Yu and code are also available on AppleLink and via Managing Editor Cynthia Jasper anonymous ftp on ftp.apple.com. Note that some Contributing Editors Lorraine Anderson, software and documentation referred to as being Toni Haskell, Judy Helfand, Elaine Meyer, on this issue’s CD may be located on the Tool Rebecca Pepper Chest edition rather than the Reference Library Indexer Marc Savage edition of the Developer CD Series disc. Macintosh Technical Notes. Where references to Macintosh Technical Notes in develop are A R T & P R O D U C T I O N followed by something like “(Memory 13),” this Production/Art Director Diane Wilcox indicates the category and number of the Note Technical Illustration Shawn Morningstar, on this issue’s CD. John Ryan E-mail addresses. Most e-mail addresses Formatting Forbes Mill Press mentioned in develop are AppleLink addresses; Film Services Aptos Post, Inc.
    [Show full text]
  • UI Programming
    UI Programming (part of this content is based on previous classes from Anastasia, S. Huot, M. Beaudouin-Lafon, N.Roussel, O.Chapuis) Assignment 1 is out! Design and implement an interactive tool for creating the layout of comic strips https://www.lri.fr/~fanis/teaching/ISI2014/assignments/ass1/ Graphical interfaces GUIs: input is specified w.r.t. output Input peripherals specify commands at specific locations on the screen (pointing), where specific objects are drown by the system. Familiar behavior from physical world WIMP interfaces WIMP: Window, Icons, Menus and Pointing Presentation ! Windows, icons and other graphical objects Interaction ! Menus, dialog boxes, text input fields, etc Input ! pointing, selection, ink/path Perception-action loop ! feedback Software layers Application Applications/Communication (MacApp) Builders, Java Swing, JavaFX, Qt (C++), Interface Tools & Toolkits GTK+, MFC, Cocoa Graphics Library GDI+, Quartz, GTK+/Xlib, OpenGL Windowing System X Windows (+KDE or GNU) Input/Output Operating System Windows, Mac OS, Unix, Linux, Android, iOS, WindowsCE Software layers Application Interface Tools & Toolkits Graphics Library Windowing System Input/Output Operating System Input/output peripherals Input: where we give commands Output: where the system shows information & reveals its state Interactivity vs. computing Closed systems (computation): ! read input, compute, produce result ! final state (end of computation) Open systems (interaction): ! events/changes caused by environment ! infinite loop, non-deterministic
    [Show full text]
  • FDK 10 Installation Guide
    FDK Installation Guide VERSION 10 Frame Developer’s Kit, Adobe Systems Incorporated March 2012 Corporate Headquarters 345 Park Avenue San Jose, CA 95110-2704 (408) 536-6000 © 2012 Adobe Systems Incorporated and its licensors. All rights reserved. Adobe® FrameMaker® 10 for Windows® Frame Developer’s Kit for Windows This manual is protected under copyright law, furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by Adobe Systems Incorporated. Adobe Systems Incorporated assumes no responsibility or liability for any errors or inaccuracies that may appear in the informational content contained in this manual. This manual is licensed for use under the terms of the Creative Commons Attribution Non-Commercial 3.0 License. This License allows users to copy, distribute, and transmit the manual for noncommercial purposes only so long as (1) proper attribution to Adobe is given as the owner of the manual; and (2) any reuse or distribution of the manual contains a notice that use of the manual is governed by these terms. The best way to provide notice is to include the following link. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc/3.0/us/ Adobe, the Adobe logo, Adobe AIR, Adobe Captivate, Adobe Type Manager, Acrobat, AIR, Creative Suite, Distiller, Flash, FrameMaker, Illustrator, PageMaker, Photoshop, PostScript, Reader, RoboHelp, and RoboScreenCapture are trademarks of Adobe Systems Incorporated in the United States and/or other countries. Microsoft, Windows, and Windows Vista are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
    [Show full text]