DOCSLIB.ORG

Cocoa® Programming Developer's Handbook

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Cocoa® Programming Developer's Handbook Cocoa® Programming Developer’s Handbook This page intentionally left blank Cocoa® Programming Developer’s Handbook David Chisnall Upper Saddle River, NJ • Boston • Indianapolis • San Francisco New York • Toronto • Montreal • London • Munich • Paris • Madrid Capetown • Sydney • Tokyo • Singapore • Mexico City Cocoa® Programming Developer’s Handbook Editor-in-Chief Copyright © 2010 Pearson Education, Inc. Mark L. Taub All rights reserved. No part of this book shall be reproduced, stored in a retrieval system, Managing Editor or transmitted by any means, electronic, mechanical, photocopying, recording, or otherwise, John Fuller without written permission from the publisher. No patent liability is assumed with respect to Full-Service the use of the information contained herein. Although every precaution has been taken in Production the preparation of this book, the publisher and author assume no responsibility for errors Manager or omissions. Nor is any liability assumed for damages resulting from the use of the Julie B. Nahil information contained herein. Technical Reviewer ISBN-13: 978-0-321-63963-9 Gregory ISBN-10: 0-321-63963-4 Casamento Book Designer Library of Congress Cataloging-in-Publication Data Gary Adair Chisnall, David. Composition Cocoa programming developer’s handbook / David Chisnall. David Chisnall p. cm. Includes index. ISBN 978-0-321-63963-9 (pbk. : alk. paper) 1. Cocoa (Application development environment) 2. Object-oriented programming (Computer science) 3. Application program interfaces (Computer software) 4. Mac OS. I. Title. QA76.64.C485 2010 005.26’8—dc22 2009042661 Printed in the United States on recycled paper at Edwards Brothers in Ann Arbor, Michigan. First Printing December 2009 Trademarks All terms mentioned in this book that are known to be trademarks or service marks have been appropriately capitalized. Pearson cannot attest to the accuracy of this information. Use of a term in this book should not be regarded as affecting the validity of any trademark or service mark. Warning and Disclaimer Every effort has been made to make this book as complete and as accurate as possible, but no warranty or fitness is implied. The information provided is on an “as is” basis. The author and the publisher shall have neither liability nor responsibility to any person or entity with respect to any loss or damages arising from the information contained in this book. Bulk Sales Pearson offers excellent discounts on this book when ordered in quantity for bulk purchases or special sales. For more information, please contact us by phone or email: U.S. Corporate and Government Sales 1-800-382-3419 [email protected] For sales outside of the U.S., please contact the International Sales group: International Sales [email protected] Contents List of Figures xvii List of Tables xxiii Preface xxv I Introducing Cocoa 1 1 Cocoa and Mac OS X 3 1.1 UnderstandingWhentoUseCocoa................ 3 1.1.1 Carbon............................. 3 1.1.2 Java............................... 5 1.1.3 Cocoa.............................. 5 1.1.4 UNIX APIs ........................... 7 1.1.5 OtherChoices......................... 8 1.2 Understanding Cocoa’s Role in Mac OS X . ........... 9 1.2.1 Cocoa.............................. 9 1.2.2 Quartz.............................. 11 1.2.3 CoreFoundation........................ 13 1.2.4 Darwin ............................. 14 1.2.5 XNU............................... 15 1.3 Overview............................... 16 2 Cocoa Language Options 17 2.1 ObjectOrientation......................... 17 2.2 Objective-C............................. 19 2.2.1 Objective-C Compiler Choices . ............. 20 2.2.2 DifferencesfromJavaandC++................ 22 2.2.3 Objective-C2.0......................... 23 2.3 RubyandPython.......................... 24 v vi Contents 2.4 Summary............................... 25 3 Using Apple’s Developer Tools 27 3.1 ObtainingApple’sDeveloperTools................ 28 3.2 InterfaceBuilder........................... 28 3.2.1 Outlets and Actions ...................... 30 3.2.2 CocoaBindings......................... 31 3.2.3 DrawingaSimpleApplication................. 34 3.3 XCode................................ 37 3.3.1 CreatingaSimpleProject................... 37 3.3.2 OpenStep Bundles . ...................... 39 3.3.3 DeveloperExamples...................... 41 3.3.4 Building Without XCode ................... 42 3.4 Objective-C............................. 43 3.4.1 Why Learn Objective-C? ................... 44 3.4.2 AdditionstoC......................... 44 3.4.3 ExceptionsandSynchronization............... 52 3.4.4 Introspection.......................... 55 3.4.5 Objective-CinC........................ 58 3.4.6 Objective-C2.0......................... 60 3.4.7 Blocks.............................. 63 3.4.8 Objective-C++......................... 66 3.5 CocoaConventions......................... 66 3.5.1 Naming . ............................ 66 3.5.2 Memory Management . .................. 70 3.5.3 Constructors and Initializers . ............... 72 3.6 Summary............................... 74 II The Cocoa Frameworks 77 4 Foundation: The Objective-C Standard Library 79 4.1 GeneralConcepts.......................... 79 4.1.1 Mutability . .......................... 80 4.1.2 ClassClusters.......................... 80 4.2 CoreFoundationTypes....................... 85 4.3 Basic Data Types .......................... 85 4.3.1 Non-Object Types . .................... 86 4.3.2 Strings.............................. 87 4.3.3 BoxedNumbersandValues.................. 88 4.3.4 Data............................... 90 4.3.5 CachesandDiscardableData................. 90 Contents vii 4.3.6 DatesandTime........................ 91 4.4 Collections.............................. 93 4.4.1 Comparisons and Ordering . ............... 93 4.4.2 Primitive Collections ...................... 96 4.4.3 Arrays.............................. 97 4.4.4 Dictionaries........................... 98 4.4.5 Sets............................... 99 4.5 Enumeration............................. 100 4.5.1 Enumerating with Higher-Order Messaging . ........ 101 4.5.2 EnumeratingwithBlocks................... 104 4.5.3 SupportingFastEnumeration................. 105 4.6 PropertyLists............................ 111 4.6.1 Serialization........................... 112 4.6.2 User Defaults .......................... 114 4.7 InteractingwiththeFilesystem.................. 117 4.7.1 Bundles............................. 117 4.7.2 Workspace and File Management ............... 120 4.7.3 Working with Paths . .................... 122 4.7.4 FileAccess........................... 123 4.8 Notifications............................. 124 4.8.1 Requesting Notifications . ................... 125 4.8.2 SendingNotifications......................126 4.8.3 Sending Asynchronous Notification . ........... 127 4.8.4 DistributedNotifications....................130 4.9 Summary............................... 132 5 Application Concepts 133 5.1 RunLoops.............................. 133 5.2 ApplicationsandDelegates..................... 140 5.3 TheResponderChain........................ 142 5.3.1 EventDelivery......................... 142 5.3.2 TargetsandActions...................... 146 5.3.3 Becoming First Responder ................... 147 5.4 RunLoopsinApplications..................... 147 5.5 DelegatesandNotifications..................... 151 5.6 TheViewHierarchy......................... 154 5.6.1 Windows............................ 154 5.6.2 Views.............................. 155 5.6.3 Cells............................... 156 5.7 Summary............................... 157 6 Creating Graphical User Interfaces 159 viii Contents 6.1 PositioningViews.......................... 159 6.2 NestedViews............................ 164 6.2.1 ClippedViews......................... 164 6.2.2 ScrollViews........................... 165 6.2.3 TabViews............................ 166 6.2.4 SplitViews........................... 167 6.2.5 Boxes.............................. 169 6.3 CreatingViews........................... 169 6.3.1 Buttons............................. 170 6.3.2 TextViews........................... 172 6.3.3 DataViews........................... 172 6.3.4 Menus.............................. 181 6.4 CocoaBindings........................... 184 6.4.1 Key-ValueCoding....................... 185 6.4.2 Key-ValueObserving......................190 6.4.3 ExposingBindings....................... 193 6.4.4 GenericControllers.......................194 6.4.5 Bindings and User Defaults . ................. 195 6.4.6 Using Bindings in Interface Builder . ............ 196 6.5 Summary............................... 202 7 Windows and Menus 203 7.1 UnderstandingWindows...................... 204 7.1.1 TypesofWindows....................... 207 7.2 Creating Windows .......................... 208 7.3 Creating Window Objects . .................. 208 7.3.1 Displaying Windows ...................... 210 7.3.2 Hiding Windows ........................ 212 7.3.3 UnderstandingWindowControllers..............214 7.3.4 CreatingaSimpleWindowFactory..............214 7.3.5 Saving a Window’s Position .................. 218 7.4 Panels................................ 219 7.4.1 DisplayingStandardPalettes................. 220 7.5 Sheets................................ 223 7.5.1 CreatingSheets......................... 223 7.5.2 ShowingStandardSheets................... 224 7.6 AlertDialogs............................. 229 7.7 Menus................................ 232 7.7.1 The Structure of a Menu . ................ 232 7.7.2
Load more

Recommended publications
  • Analyzing Safari 2.X Web Browser Artifacts Using SFT
    Analyzing Safari 2.x Web Browser Artifacts using SFT. Copyright 2007 - Jacob Cunningham (v1.0) Table of Contents Introduction:...............................................................................................................................................3 Safari Forensic Tools................................................................................................................................. 3 OSX Property List files..............................................................................................................................3 Safari Related Files.................................................................................................................................... 4 The Safari Preferences files....................................................................................................................... 5 Browser History......................................................................................................................................... 7 Downloads history:.................................................................................................................................... 8 Bookmarks file ........................................................................................................................................10 Cookies file:............................................................................................................................................. 11 Browser Cache........................................................................................................................................
    [Show full text]
  • Apple Software Design Guidelines
    Apple Software Design Guidelines May 27, 2004 Java and all Java-based trademarks are Apple Computer, Inc. trademarks or registered trademarks of Sun © 2004 Apple Computer, Inc. Microsystems, Inc. in the U.S. and other All rights reserved. countries. OpenGL is a trademark of Silicon Graphics, No part of this publication may be Inc. reproduced, stored in a retrieval system, or transmitted, in any form or by any means, PowerPC and and the PowerPC logo are mechanical, electronic, photocopying, trademarks of International Business recording, or otherwise, without prior Machines Corporation, used under license written permission of Apple Computer, Inc., therefrom. with the following exceptions: Any person Simultaneously published in the United is hereby authorized to store documentation States and Canada. on a single computer for personal use only Even though Apple has reviewed this manual, and to print copies of documentation for APPLE MAKES NO WARRANTY OR personal use provided that the REPRESENTATION, EITHER EXPRESS OR IMPLIED, WITH RESPECT TO THIS MANUAL, documentation contains Apple's copyright ITS QUALITY, ACCURACY, notice. MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. AS A RESULT, THIS The Apple logo is a trademark of Apple MANUAL IS SOLD ªAS IS,º AND YOU, THE PURCHASER, ARE ASSUMING THE ENTIRE Computer, Inc. RISK AS TO ITS QUALITY AND ACCURACY. Use of the ªkeyboardº Apple logo IN NO EVENT WILL APPLE BE LIABLE FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, (Option-Shift-K) for commercial purposes OR CONSEQUENTIAL DAMAGES without the prior written consent of Apple RESULTING FROM ANY DEFECT OR may constitute trademark infringement and INACCURACY IN THIS MANUAL, even if advised of the possibility of such damages.
    [Show full text]
  • What Are the Problems with Embedded Linux?
    What Are the Problems with Embedded Linux? Every Operating System Has Benefits and Drawbacks Linux is ubiquitous. It runs most internet servers, is inside Android* smartphones, and is used on millions of embedded systems that, in the past, ran Real-Time Operating Systems (RTOSes). Linux can (and should) be used were possible for embedded projects, but while it gives you extreme choice, it also presents the risk of extreme complexity. What, then, are the trade-offs between embedded Linux and an RTOS? In this article, we cover some key considerations when evaluating Linux for a new development: ■ Design your system architecture first ■ What is Linux? ■ Linux vs. RTOSes ■ Free software is about liberty—not price ■ How much does Embedded Linux cost? ■ Why pay for Embedded Linux? ■ Should you buy Embedded Linux or roll-your-own (RYO)? ■ To fork or not to fork? ■ Software patching ■ Open source licensing ■ Making an informed decision The important thing is not whether Linux or an RTOS is “the best,” but whether either operating system—or both together—makes the most technical and financial sense for your project. We hope this article helps you make an informed decision. Design Your System Architecture First It is important to design your system architecture first—before choosing either Linux or an RTOS—because both choices can limit architectural freedom. You may discover that aspects of your design require neither Linux nor an RTOS, making your design a strong candidate for a heterogeneous approach that includes one or more bare-metal environments (with possibly a Linux and/or RTOS environment as well).
    [Show full text]
  • Extending the UHC LLVM Backend: Adding Support for Accurate Garbage Collection
    Extending the UHC LLVM backend: Adding support for accurate garbage collection Paul van der Ende MSc Thesis October 18, 2010 INF/SCR-09-59 Daily Supervisors: Center for Software Technology dr. A. Dijkstra Dept. of Information and Computing Sciences drs. J.D. Fokker Utrecht University Utrecht, the Netherlands Second Supervisor: prof. dr. S.D. Swierstra Abstract The Utrecht Haskell Compiler has an LLVM backend for whole program analyse mode. This backend pre- viously used the Boehm-Weiser library for heap allocation and conservative garbage collection. Recently an accurate garbage collector for the UHC compiler has been developed. We wanted this new garbage collection library to work with the LLVM backend. But since this new collector is accurate, it needs cooperation with the LLVM backend. Functionality needs to be added to find the set of root references and traversing all live references. To find the root set, the bytecode interpreter backend currently uses static stack maps. This is where the problem arises. The LLVM compiler is known to do various aggressive transformations. These optimizations might change the stack layout described by the static stack map. So to avoid this problem we wanted to use the shadow-stack provided by the LLVM framework. This is a dynamic structure maintained on the stack to safely find the garbage collection roots. We expect that the shadow-stack approach comes with a runtime overhead for maintaining this information dynamically on the stack. So we did measure the impact of this method. We also measured the performance improvement of the new garbage collection method used and compare it with the other UHC backends.
    [Show full text]
  • Cocoa Touch & Iphone
    Music Appreciation 243: Introduction to Rick Astley Evan Doll [email protected] Alan Cannistraro [email protected] Thursday, April 2, 2009 Thursday, April 2, 2009 Welcome to CS193P: iPhone Application Development Evan Doll [email protected] Alan Cannistraro [email protected] Thursday, April 2, 2009 Staff • Lecturers ■ Evan Doll [email protected] ■ Alan Cannistraro [email protected] • Student TAs ■ Troy Brant [email protected] ■ Paul Salzman [email protected] • “Professor Emeritus” ■ Paul Marcos [email protected] Thursday, April 2, 2009 How many of you... • Are familiar with object-oriented programming? • Have developed software with Mac OS X? • Have developed apps for the iPhone? Thursday, April 2, 2009 Lectures, Sections, Office Hours • Lectures ■ 320-105, Monday & Wednesday 3:15 – 4:30 PM • Optional Section ■ 200-205, Friday 3:15 – 4:05 PM as announced ■ Guest speakers, additional topics ■ First one will be next Friday 4/10 • Office Hours ■ Troy and Paul will be holding office hours ■ Time & location TBD, check website for details Thursday, April 2, 2009 Requirements • Prerequisite: CS 106B/X • Recommended Book: None, we’ll use Apple documentation • You must have access to an Intel-based Macintosh ■ Running Mac OS X 10.5 Leopard ■ iPhone SDK (Not available on cluster computers!) • Owning an iPhone or iPod Touch is not required ■ Assignments may be done with the iPhone Simulator ■ Loaner iPod Touches should be available, more details to come Thursday, April 2, 2009 Enrollment • Response has been phenomenal again
    [Show full text]
  • Membrane: Operating System Support for Restartable File Systems Swaminathan Sundararaman, Sriram Subramanian, Abhishek Rajimwale, Andrea C
    Membrane: Operating System Support for Restartable File Systems Swaminathan Sundararaman, Sriram Subramanian, Abhishek Rajimwale, Andrea C. Arpaci-Dusseau, Remzi H. Arpaci-Dusseau, Michael M. Swift Computer Sciences Department, University of Wisconsin, Madison Abstract and most complex code bases in the kernel. Further, We introduce Membrane, a set of changes to the oper- file systems are still under active development, and new ating system to support restartable file systems. Mem- ones are introduced quite frequently. For example, Linux brane allows an operating system to tolerate a broad has many established file systems, including ext2 [34], class of file system failures and does so while remain- ext3 [35], reiserfs [27], and still there is great interest in ing transparent to running applications; upon failure, the next-generation file systems such as Linux ext4 and btrfs. file system restarts, its state is restored, and pending ap- Thus, file systems are large, complex, and under develop- plication requests are serviced as if no failure had oc- ment, the perfect storm for numerous bugs to arise. curred. Membrane provides transparent recovery through Because of the likely presence of flaws in their imple- a lightweight logging and checkpoint infrastructure, and mentation, it is critical to consider how to recover from includes novel techniques to improve performance and file system crashes as well. Unfortunately, we cannot di- correctness of its fault-anticipation and recovery machin- rectly apply previous work from the device-driver litera- ery. We tested Membrane with ext2, ext3, and VFAT. ture to improving file-system fault recovery. File systems, Through experimentation, we show that Membrane in- unlike device drivers, are extremely stateful, as they man- duces little performance overhead and can tolerate a wide age vast amounts of both in-memory and persistent data; range of file system crashes.
    [Show full text]
  • 706 What's New in Security 07 FINAL.Key
    System Frameworks #WWDC16 What’s New in Security Session 706 Lucia Ballard Secure Transports Engineering Manager Simon Cooper Trusted Execution Engineering Manager © 2016 Apple Inc. All rights reserved. Redistribution or public display not permitted without written permission from Apple. What’s New in Security? What’s New in Security? Network Security What’s New in Security? Network Security Cryptography APIs What’s New in Security? Network Security Cryptography APIs Platform Security on macOS What’s New in Network Security Lucia Ballard Secure Transports Engineering Manager Secure Communications Secure Communications HTTPS is the new HTTP • Confidentiality • Data integrity Secure Communications HTTPS is the new HTTP • Confidentiality • Data integrity Not all HTTPS is created equal App Transport Security Current standards App Transport Security Current standards For NSURLSession and NSURLConnection APIs App Transport Security Current standards For NSURLSession and NSURLConnection APIs • TLS v1.2 App Transport Security Current standards For NSURLSession and NSURLConnection APIs • TLS v1.2 • Strong crypto—AES-128 and SHA-2 App Transport Security Current standards For NSURLSession and NSURLConnection APIs • TLS v1.2 • Strong crypto—AES-128 and SHA-2 • Forward secrecy—ECDHE App Transport Security Current standards For NSURLSession and NSURLConnection APIs • TLS v1.2 • Strong crypto—AES-128 and SHA-2 • Forward secrecy—ECDHE Exceptions—global or for particular domains App Transport Security Enforcement App Transport Security Enforcement Enforced
    [Show full text]
  • Improving Memory Management Security for C and C++
    Improving memory management security for C and C++ Yves Younan, Wouter Joosen, Frank Piessens, Hans Van den Eynden DistriNet, Katholieke Universiteit Leuven, Belgium Abstract Memory managers are an important part of any modern language: they are used to dynamically allocate memory for use in the program. Many managers exist and depending on the operating system and language. However, two major types of managers can be identified: manual memory allocators and garbage collectors. In the case of manual memory allocators, the programmer must manually release memory back to the system when it is no longer needed. Problems can occur when a programmer forgets to release it (memory leaks), releases it twice or keeps using freed memory. These problems are solved in garbage collectors. However, both manual memory allocators and garbage collectors store management information for the memory they manage. Often, this management information is stored where a buffer overflow could allow an attacker to overwrite this information, providing a reliable way to achieve code execution when exploiting these vulnerabilities. In this paper we describe several vulnerabilities for C and C++ and how these could be exploited by modifying the management information of a representative manual memory allocator and a garbage collector. Afterwards, we present an approach that, when applied to memory managers, will protect against these attack vectors. We implemented our approach by modifying an existing widely used memory allocator. Benchmarks show that this implementation has a negligible, sometimes even beneficial, impact on performance. 1 Introduction Security has become an important concern for all computer users. Worms and hackers are a part of every day internet life.
    [Show full text]
  • Mac OS X Server Administrator's Guide
    034-9285.S4AdminPDF 6/27/02 2:07 PM Page 1 Mac OS X Server Administrator’s Guide K Apple Computer, Inc. © 2002 Apple Computer, Inc. All rights reserved. Under the copyright laws, this publication may not be copied, in whole or in part, without the written consent of Apple. The Apple logo is a trademark of Apple Computer, Inc., registered in the U.S. and other countries. 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, the Apple logo, AppleScript, AppleShare, AppleTalk, ColorSync, FireWire, Keychain, Mac, Macintosh, Power Macintosh, QuickTime, Sherlock, and WebObjects are trademarks of Apple Computer, Inc., registered in the U.S. and other countries. AirPort, Extensions Manager, Finder, iMac, and Power Mac are trademarks of Apple Computer, Inc. Adobe and PostScript are trademarks of Adobe Systems Incorporated. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. Netscape Navigator is a trademark of Netscape Communications Corporation. RealAudio is a trademark of Progressive Networks, Inc. © 1995–2001 The Apache Group. All rights reserved. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company, Ltd. 062-9285/7-26-02 LL9285.Book Page 3 Tuesday, June 25, 2002 3:59 PM Contents Preface How to Use This Guide 39 What’s Included
    [Show full text]
  • Programming Java for OS X
    Programming Java for OS X hat’s so different about Java on a Mac? Pure Java applica- tions run on any operating system that supports Java. W Popular Java tools run on OS X. From the developer’s point of view, Java is Java, no matter where it runs. Users do not agree. To an OS X user, pure Java applications that ignore the feel and features of OS X are less desirable, meaning the customers will take their money elsewhere. Fewer sales translates into unhappy managers and all the awkwardness that follows. In this book, I show how to build GUIs that feel and behave like OS X users expect them to behave. I explain development tools and libraries found on the Mac. I explore bundling of Java applications for deployment on OS X. I also discuss interfacing Java with other languages commonly used on the Mac. This chapter is about the background and basics of Java develop- ment on OS X. I explain the history of Java development. I show you around Apple’s developer Web site. Finally, I go over the IDEs commonly used for Java development on the Mac. In This Chapter Reviewing Apple Java History Exploring the history of Apple embraced Java technologies long before the first version of Java on Apple computers OS X graced a blue and white Mac tower. Refugees from the old Installing developer tan Macs of the 1990s may vaguely remember using what was tools on OS X called the MRJ when their PC counterparts were busy using JVMs. Looking at the MRJ stands for Mac OS Runtime for Java.
    [Show full text]
  • Intelligent OS X Malware Threat Detection with Code Inspection
    This is a repository copy of Intelligent OS X malware threat detection with code inspection. White Rose Research Online URL for this paper: http://eprints.whiterose.ac.uk/128371/ Version: Published Version Article: Pajouh, H.H., Dehghantanha, A. orcid.org/0000-0002-9294-7554, Khayami, R. et al. (1 more author) (2018) Intelligent OS X malware threat detection with code inspection. Journal of Computer Virology and Hacking Techniques, 14 (3). pp. 213-223. ISSN 2274-2042 https://doi.org/10.1007/s11416-017-0307-5 Reuse This article is distributed under the terms of the Creative Commons Attribution (CC BY) licence. This licence allows you to distribute, remix, tweak, and build upon the work, even commercially, as long as you credit the authors for the original work. More information and the full terms of the licence here: https://creativecommons.org/licenses/ Takedown If you consider content in White Rose Research Online to be in breach of UK law, please notify us by emailing [email protected] including the URL of the record and the reason for the withdrawal request. [email protected] https://eprints.whiterose.ac.uk/ J Comput Virol Hack Tech DOI 10.1007/s11416-017-0307-5 ORIGINAL PAPER Intelligent OS X malware threat detection with code inspection Hamed Haddad Pajouh1 · Ali Dehghantanha2 · Raouf Khayami1 · Kim-Kwang Raymond Choo3,4 Received: 31 July 2017 / Accepted: 27 September 2017 © The Author(s) 2017. This article is an open access publication Abstract With the increasing market share of Mac OS X over 91% detection accuracy with 3.9% false alarm rate.
    [Show full text]
  • Chapter 1. Origins of Mac OS X
    1 Chapter 1. Origins of Mac OS X "Most ideas come from previous ideas." Alan Curtis Kay The Mac OS X operating system represents a rather successful coming together of paradigms, ideologies, and technologies that have often resisted each other in the past. A good example is the cordial relationship that exists between the command-line and graphical interfaces in Mac OS X. The system is a result of the trials and tribulations of Apple and NeXT, as well as their user and developer communities. Mac OS X exemplifies how a capable system can result from the direct or indirect efforts of corporations, academic and research communities, the Open Source and Free Software movements, and, of course, individuals. Apple has been around since 1976, and many accounts of its history have been told. If the story of Apple as a company is fascinating, so is the technical history of Apple's operating systems. In this chapter,[1] we will trace the history of Mac OS X, discussing several technologies whose confluence eventually led to the modern-day Apple operating system. [1] This book's accompanying web site (www.osxbook.com) provides a more detailed technical history of all of Apple's operating systems. 1 2 2 1 1.1. Apple's Quest for the[2] Operating System [2] Whereas the word "the" is used here to designate prominence and desirability, it is an interesting coincidence that "THE" was the name of a multiprogramming system described by Edsger W. Dijkstra in a 1968 paper. It was March 1988. The Macintosh had been around for four years.
    [Show full text]