DOCSLIB.ORG

Integrating Carbon and Cocoa in Your Application

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Integrating Carbon and Cocoa in Your Application Integrating Carbon and Cocoa in Your Application Preliminary January 1, 2003 Simultaneously published in the United Apple Computer, Inc. States and Canada. © 2003, 2004 Apple Computer, Inc. Even though Apple has reviewed this manual, All rights reserved. APPLE MAKES NO WARRANTY OR REPRESENTATION, EITHER EXPRESS OR IMPLIED, WITH RESPECT TO THIS MANUAL, No part of this publication may be ITS QUALITY, ACCURACY, MERCHANTABILITY, OR FITNESS FOR A reproduced, stored in a retrieval system, or PARTICULAR PURPOSE. AS A RESULT, THIS transmitted, in any form or by any means, MANUAL IS SOLD ªAS IS,º AND YOU, THE mechanical, electronic, photocopying, PURCHASER, ARE ASSUMING THE ENTIRE RISK AS TO ITS QUALITY AND ACCURACY. recording, or otherwise, without prior IN NO EVENT WILL APPLE BE LIABLE FOR written permission of Apple Computer, Inc., DIRECT, INDIRECT, SPECIAL, INCIDENTAL, with the following exceptions: Any person OR CONSEQUENTIAL DAMAGES RESULTING FROM ANY DEFECT OR is hereby authorized to store documentation INACCURACY IN THIS MANUAL, even if on a single computer for personal use only advised of the possibility of such damages. and to print copies of documentation for THE WARRANTY AND REMEDIES SET personal use provided that the FORTH ABOVE ARE EXCLUSIVE AND IN LIEU OF ALL OTHERS, ORAL OR WRITTEN, documentation contains Apple’s copyright EXPRESS OR IMPLIED. No Apple dealer, agent, notice. or employee is authorized to make any modification, extension, or addition to this The Apple logo is a trademark of Apple warranty. Computer, Inc. Some states do not allow the exclusion or limitation of implied warranties or liability for Use of the “keyboard” Apple logo incidental or consequential damages, so the (Option-Shift-K) for commercial purposes above limitation or exclusion may not apply to you. This warranty gives you specific legal without the prior written consent of Apple rights, and you may also have other rights which may constitute trademark infringement and vary from state to state. unfair competition in violation of federal and state laws. No licenses, express or implied, are granted with respect to any of the technology described in this document. Apple retains all intellectual property rights associated with the technology described in this document. This document is intended to assist application developers to develop applications only for Apple-labeled or Apple-licensed computers. Every effort has been made to ensure that the information in this document is accurate. Apple is not responsible for typographical errors. Apple Computer, Inc. 1 Infinite Loop Cupertino, CA 95014 408-996-1010 Apple, the Apple logo, Aqua, Carbon, Cocoa, Mac, Mac OS, and QuickTime are trademarks of Apple Computer, Inc., registered in the United States and other countries. Objective-C is a trademark of NeXT Software, Inc. Java and all Java-based trademarks are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. Contents Chapter 1 Introduction to Carbon and Cocoa Integration 7 Chapter 2 Carbon and Cocoa Integration Concepts 9 Carbon and Cocoa Communication 9 C-Callable Wrapper Functions 12 Compiler Preprocessors 13 Interchangeable Data Types 13 Chapter 3 Carbon and Cocoa Integration Tasks 15 Using Cocoa Functionality in a Carbon Application 15 About the Spelling Checker Application 16 Writing a Cocoa Bundle 16 Making Your Carbon Code Access the Cocoa Bundle 20 Summary 24 Using Carbon Functionality in a Cocoa Application 24 Working With QuickTime Movies 25 Accessing a Resource Fork From Cocoa 26 Obtaining an FSSpec Structure 26 Managing Core Foundation Objects in Cocoa 27 Summary 28 Using a Cocoa User Interface in a Carbon Application 28 About the CocoaInCarbon Application 29 Writing the Cocoa Bundle 31 Setting Up the Carbon Application to Use the Cocoa Interface 36 Summary 39 Using a Carbon User Interface in a Cocoa Application 39 About the CarbonInCocoa Application 40 Creating the Carbon User Interface 41 Setting Up the Cocoa Application to Use the Carbon User Interface 41 Summary 44 Document Revision History 45 3 Preliminary © 2003, 2004 Apple Computer, Inc. All Rights Reserved. CONTENTS 4 Preliminary © 2003, 2004 Apple Computer, Inc. All Rights Reserved. Tables, Figures, and Listings Chapter 2 Carbon and Cocoa Integration Concepts 9 Figure 2-1 The path of user events in Mac OS X 10 Figure 2-2 Events communicated between Carbon and Cocoa 11 Table 2-1 Filename extensions and compilation 13 Table 2-2 Data types that can be used interchangeably between Carbon and Cocoa 14 Chapter 3 Carbon and Cocoa Integration Tasks 15 Figure 3-1 The user interface for the Spelling Checker application 16 Figure 3-2 The Carbon user interface for the CocoaInCarbon application 30 Figure 3-3 The Cocoa window for the CocoaInCarbon application 30 Figure 3-4 Connecting a button to a button-pressed action 36 Figure 3-5 The Cocoa user interface for the CarbonInCocoa application 40 Figure 3-6 The Carbon user interface for the CarbonInCocoa application 40 Listing 3-1 A C-callable wrapper function for the uniqueSpellDocumentTag: method 19 Listing 3-2 A C-callable wrapper function for the checkSpellingOfString:startingAt: method 19 Listing 3-3 A C-callable wrapper function for the sharedApplication method 20 Listing 3-4 A utility function to load a bundle from the application's Frameworks folder 21 Listing 3-5 Defining data types for function pointers 22 Listing 3-6 Declaring function pointers 22 Listing 3-7 Calling a C-wrapper function from your Carbon application 23 Listing 3-8 Building an array of track media types for a QuickTime movie 25 Listing 3-9 Calling Resource Manager functions from a Cocoa application 26 Listing 3-10 A Cocoa method to obtain an FSSpec structure 27 Listing 3-11 The contents of the common header for the Cocoa bundle and the Carbon application 32 Listing 3-12 Implementing the controller in the Cocoa bundle 32 Listing 3-13 Declaring the interface for the controller 33 Listing 3-14 C-callable wrapper functions for the Cocoa bundle 34 Listing 3-15 Calling the initializeBundle C-wrapper function using a function pointer 37 Listing 3-16 Calling the C-wrapper function to open the Cocoa window 38 Listing 3-17 A Carbon function that handles a Cocoa button press 38 Listing 3-18 The declaration for the controller 42 Listing 3-19 Loading a nib file for a Carbon window 42 5 Preliminary © 2003, 2004 Apple Computer, Inc. All Rights Reserved. TABLES, FIGURES, AND LISTINGS Table 3-1 C-callable wrapper functions for Cocoa methods 18 6 Preliminary © 2003, 2004 Apple Computer, Inc. All Rights Reserved. CHAPTER 1 Introduction to Carbon and Cocoa Integration No matter which development environment you choose to develop applicationsÐCocoa or CarbonÐyou may find the other development environment offers functionality you'd like to use in your application. Choosing the Cocoa or Carbon development environment to create new applications doesn't restrict you to using the API defined for that environment. You can use the Carbon API from a Cocoa application or the Cocoa API from a Carbon application. This document shows you how. There are a number of reasons you might want to integrate Cocoa and Carbon in an application, including the following: ■ You want to leverage existing code while getting the benefits of technologies offered by another framework. ■ You are developing a common service that you want to make available to both Carbon and Cocoa. ■ It's easier for you to do some tasks in Cocoa than in Carbon, or vice versa. ■ You already created a terrific user interface in one environment and want to access it from the other environment. ■ Your programming team consists of engineers with different skill setsÐCocoa and Carbon. You'll find, by reading the following chapters, that intermixing Carbon and Cocoa in an application is a relatively straightforward process. ■ Chapter 2, ªCarbon and Cocoa Integration Conceptsº, discusses how Carbon and Cocoa communicate between each other and provides information on C-callable wrapper functions, compiler preprocessors, and interchangeable data types. ■ Chapter 3, ªCarbon and Cocoa Integration Tasksº, provides information on how you can call Cocoa functions from a Carbon application and Carbon functions from a Cocoa application, including how to share user interface elements between the two environments. This document assumes you are programming for Cocoa in Objective-C and does not discuss Java integration issues. To get the full benefit of this document, you should have experience programming in either the Cocoa or Carbon environment. In addition, it is desirable that you have some basic knowledge of the other environment. See the Mac OS X Programming Getting Started website for tutorials, examples, and a reading list of essential documents: http://developer.apple.com/macosx/gettingstarted/ 7 Preliminary © 2003, 2004 Apple Computer, Inc. All Rights Reserved. CHAPTER 1 Introduction to Carbon and Cocoa Integration Important: This is a preliminary document. Although it has been reviewed for technical accuracy, it is not final. Apple Computer, Inc. is supplying this information to help you plan for the adoption of the technology described herein. This information is subject to change, and software implemented according to this document should be tested with final operating-system software and final documentation. You can check http://developer.apple.com/documentation/ for information about updates to this and other developer documents. To receive notification of documentation updates, you can sign up for ADC©s free Online Program and receive their weekly Apple Developer Connection News email newsletter. (See http://developer.apple.com/membership/ for more details about the Online Program.) 8 Preliminary © 2003, 2004 Apple Computer, Inc. All Rights Reserved. CHAPTER 2 Carbon and Cocoa Integration Concepts It has always been possible to integrate Cocoa and Carbon functionality in the same application, at least when it comes to functionality that doesn't handle user interface elements.
Load more

Recommended publications
  • 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]
  • 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]
  • 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]
  • Next-Generation Cryptographic Services I’M Going to Tell You, and I Won’T Kill You
    Next-Generation Cryptographic Services I’m going to tell you, and I won’t kill you Session 212 Jon Callas Security Privateer These are confidential sessions—please refrain from streaming, blogging, or taking pictures 1 Introduction • Learn about exciting changes to Apple’s cryptographic architecture • First major reworking of crypto in a decade 2 What You Will Learn • Changes to existing APIs • New Transform API • How to use Apple’s Transform library • How to create your own custom Transforms 3 CDSA Common Data Security Architecture 4 CDSA Is Deprecated • It is a creature of its time • That time is the late 1990s • It is a thinly used, Open Group standard ■ All of the costs, few of the benefits • Only a Mac OS API, not iOS 5 Deprecated Does Not Mean Canceled • CDSA is still available • Start migrating away now • Some parts of Security Framework have layering issues with CDSA ■ Those parts are deprecated, too 6 Requirements for a Replacement Design for the decades ahead • Less code • Faster code • Concurrent code • Flexible programming ■ Crypto includes ciphers, compression, XML, networking, REST, LDAP, databases… 7 New Crypto Architecture • Low-level (pointer, length) Security Framework Core Foundation • Basic core algorithms • FoundationOnly for on FIPS 140 Transforms Core Foundation validation Mac OS • Traditional crypto toolkit CommonCrypto C-language programming • Documentation in man pages ■ man CC_crypto 8 New CommonCrypto Architecture • Starts from Snow Leopard’s CommonCrypto • Recoded internals ■ Both Mac OS, iOS ■ NIST algorithm
    [Show full text]
  • Webobjects Bundle Reference
    WebObjects Bundle Reference 2006-10-03 Times is a registered trademark of Apple Computer, Inc. Heidelberger Druckmaschinen AG, © 2006 Apple Computer, Inc. available from Linotype Library GmbH. All rights reserved. Simultaneously published in the United States and Canada. No part of this publication may be Even though Apple has reviewed this document, reproduced, stored in a retrieval system, or APPLE MAKES NO WARRANTY OR transmitted, in any form or by any means, REPRESENTATION, EITHER EXPRESS OR IMPLIED, WITH RESPECT TO THIS mechanical, electronic, photocopying, DOCUMENT, ITS QUALITY, ACCURACY, recording, or otherwise, without prior MERCHANTABILITY, OR FITNESS FOR A written permission of Apple Computer, Inc., PARTICULAR PURPOSE. AS A RESULT, THIS DOCUMENT IS PROVIDED “AS IS,” AND with the following exceptions: Any person YOU, THE READER, ARE ASSUMING THE is hereby authorized to store documentation ENTIRE RISK AS TO ITS QUALITY AND ACCURACY. on a single computer for personal use only IN NO EVENT WILL APPLE BE LIABLE FOR and to print copies of documentation for DIRECT, INDIRECT, SPECIAL, INCIDENTAL, personal use provided that the OR CONSEQUENTIAL DAMAGES documentation contains Apple’s copyright RESULTING FROM ANY DEFECT OR INACCURACY IN THIS DOCUMENT, even if notice. advised of the possibility of such damages. The Apple logo is a trademark of Apple THE WARRANTY AND REMEDIES SET FORTH ABOVE ARE EXCLUSIVE AND IN Computer, Inc. LIEU OF ALL OTHERS, ORAL OR WRITTEN, EXPRESS OR IMPLIED. No Apple dealer, agent, Use of the “keyboard” Apple logo or employee is authorized to make any (Option-Shift-K) for commercial purposes modification, extension, or addition to this without the prior written consent of Apple warranty.
    [Show full text]
  • Mac OS X: an Introduction for Support Providers
    Mac OS X: An Introduction for Support Providers Course Information Purpose of Course Mac OS X is the next-generation Macintosh operating system, utilizing a highly robust UNIX core with a brand new simplified user experience. It is the first successful attempt to provide a fully-functional graphical user experience in such an implementation without requiring the user to know or understand UNIX. This course is designed to provide a theoretical foundation for support providers seeking to provide user support for Mac OS X. It assumes the student has performed this role for Mac OS 9, and seeks to ground the student in Mac OS X using Mac OS 9 terms and concepts. Author: Robert Dorsett, manager, AppleCare Product Training & Readiness. Module Length: 2 hours Audience: Phone support, Apple Solutions Experts, Service Providers. Prerequisites: Experience supporting Mac OS 9 Course map: Operating Systems 101 Mac OS 9 and Cooperative Multitasking Mac OS X: Pre-emptive Multitasking and Protected Memory. Mac OS X: Symmetric Multiprocessing Components of Mac OS X The Layered Approach Darwin Core Services Graphics Services Application Environments Aqua Useful Mac OS X Jargon Bundles Frameworks Umbrella Frameworks Mac OS X Installation Initialization Options Installation Options Version 1.0 Copyright © 2001 by Apple Computer, Inc. All Rights Reserved. 1 Startup Keys Mac OS X Setup Assistant Mac OS 9 and Classic Standard Directory Names Quick Answers: Where do my __________ go? More Directory Names A Word on Paths Security UNIX and security Multiple user implementation Root Old Stuff in New Terms INITs in Mac OS X Fonts FKEYs Printing from Mac OS X Disk First Aid and Drive Setup Startup Items Mac OS 9 Control Panels and Functionality mapped to Mac OS X New Stuff to Check Out Review Questions Review Answers Further Reading Change history: 3/19/01: Removed comment about UFS volumes not being selectable by Startup Disk.
    [Show full text]
  • Carbon Copy Cloner Documentation: English
    Carbon Copy Cloner Documentation: English Getting started with CCC System Requirements, Installing, Updating, and Uninstalling CCC CCC License, Registration, and Trial FAQs Trouble Applying Your Registration Information? Establishing an initial backup Preparing your backup disk for a backup of Mac OS X Restoring data from your backup What's new in CCC Features of CCC specific to Lion and greater Release History Carbon Copy Cloner's Transition to a Commercial Product: Frequently Asked Questions Credits Example backup scenarios I want to clone my entire hard drive to a new hard drive or a new machine I want to backup my important data to another Macintosh on my network I want to backup multiple machines or hard drives to the same hard drive I want my backup task to run automatically on a scheduled basis Backing up to/from network volumes and other non-HFS volumes I want to back up my whole Mac to a Time Capsule or other network volume I want to defragment my hard drive Backup and archiving settings Excluding files and folders from a backup task Protecting data that is already on your destination volume Managing previous versions of your files Automated maintenance of CCC archives Advanced Settings Some files and folders are automatically excluded from a backup task The Block-Level Copy Scheduling Backup Tasks Scheduling a task and basic settings Performing actions Before and After the backup task Deferring and skipping scheduled tasks Frequently asked questions about scheduled tasks Email and Growl notifications Backing Up to Disk Images
    [Show full text]
  • Video Capture 3-In-1 Video Capture
    Model: NV100C Video Capture 3-in-1 video capture Quick Start Guide 1 Table of Contents Overview ........................................................................................... 3 Package Contents ................................................................................................. 3 System Requirements ........................................................................................... 3 Use on Mac OS .................................................................................. 4 Hardware Installation ........................................................................................... 4 Driver Installation ................................................................................................. 4 Capture Video on QuickTime Player ..................................................................... 4 Use on Windows PC/Laptop ............................................................... 7 Hardware Installation ........................................................................................... 7 Driver Installation ................................................................................................. 7 Capture Video on CyberLink PowerDirector ......................................................... 7 Capture Video on VivaStation............................................................................. 10 Use on Android Device .................................................................... 12 Capture Video on VivaCAP ................................................................................
    [Show full text]
  • Using the Java Bridge
    Using the Java Bridge In the worlds of Mac OS X, Yellow Box for Windows, and WebObjects programming, there are two languages in common use: Java and Objective-C. This document describes the Java bridge, a technology from Apple that makes communication between these two languages possible. The first section, ÒIntroduction,Ó gives a brief overview of the bridgeÕs capabilities. For a technical overview of the bridge, see ÒHow the Bridge WorksÓ (page 2). To learn how to expose your Objective-C code to Java, see ÒWrapping Objective-C FrameworksÓ (page 9). If you want to write Java code that references Objective-C classes, see ÒUsing Java-Wrapped Objective-C ClassesÓ (page 6). If you are writing Objective-C code that references Java classes, read ÒUsing Java from Objective-CÓ (page 5). Introduction The original OpenStep system developed by NeXT Software contained a number of object-oriented frameworks written in the Objective-C language. Most developers who used these frameworks wrote their code in Objective-C. In recent years, the number of developers writing Java code has increased dramatically. For the benefit of these programmers, Apple Computer has provided Java APIs for these frameworks: Foundation Kit, AppKit, WebObjects, and Enterprise Objects. They were made possible by using techniques described later in Introduction 1 Using the Java Bridge this document. You can use these same techniques to expose your own Objective-C frameworks to Java code. Java and Objective-C are both object-oriented languages, and they have enough similarities that communication between the two is possible. However, there are some differences between the two languages that you need to be aware of in order to use the bridge effectively.
    [Show full text]