DOCSLIB.ORG

Objective-C Language and Gnustep Base Library Programming Manual

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Objective-C Language and Gnustep Base Library Programming Manual Objective-C Language and GNUstep Base Library Programming Manual Francis Botto (Brainstorm) Richard Frith-Macdonald (Brainstorm) Nicola Pero (Brainstorm) Adrian Robert Copyright c 2001-2004 Free Software Foundation Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim copying, provided also that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this manual into another lan- guage, under the above conditions for modified versions. i Table of Contents 1 Introduction::::::::::::::::::::::::::::::::::::: 3 1.1 What is Object-Oriented Programming? :::::::::::::::::::::::: 3 1.1.1 Some Basic OO Terminology :::::::::::::::::::::::::::::: 3 1.2 What is Objective-C? :::::::::::::::::::::::::::::::::::::::::: 5 1.3 History :::::::::::::::::::::::::::::::::::::::::::::::::::::::: 5 1.4 What is GNUstep? ::::::::::::::::::::::::::::::::::::::::::::: 6 1.4.1 GNUstep Base Library :::::::::::::::::::::::::::::::::::: 6 1.4.2 GNUstep Make Utility :::::::::::::::::::::::::::::::::::: 7 1.4.3 A Word on the Graphical Environment :::::::::::::::::::: 7 1.4.4 The GNUstep Directory Layout ::::::::::::::::::::::::::: 7 1.5 Building Your First Objective-C Program :::::::::::::::::::::: 8 2 The Objective-C Language ::::::::::::::::::: 11 2.1 Non OO Additions :::::::::::::::::::::::::::::::::::::::::::: 11 2.2 Objects ::::::::::::::::::::::::::::::::::::::::::::::::::::::: 11 2.2.1 Id and nil :::::::::::::::::::::::::::::::::::::::::::::::: 12 2.2.2 Messages ::::::::::::::::::::::::::::::::::::::::::::::::: 12 2.2.3 Polymorphism:::::::::::::::::::::::::::::::::::::::::::: 13 2.3 Classes:::::::::::::::::::::::::::::::::::::::::::::::::::::::: 13 2.3.1 Inheritance::::::::::::::::::::::::::::::::::::::::::::::: 13 2.3.2 Inheritance of Methods ::::::::::::::::::::::::::::::::::: 14 2.3.3 Overriding Methods :::::::::::::::::::::::::::::::::::::: 14 2.3.4 Abstract Classes ::::::::::::::::::::::::::::::::::::::::: 14 2.3.5 Class Clusters :::::::::::::::::::::::::::::::::::::::::::: 15 2.4 NSObject: The Root Class :::::::::::::::::::::::::::::::::::: 15 2.4.1 The NSObject Protocol :::::::::::::::::::::::::::::::::: 16 2.5 Static Typing ::::::::::::::::::::::::::::::::::::::::::::::::: 16 2.5.1 Type Introspection ::::::::::::::::::::::::::::::::::::::: 16 2.5.2 Referring to Instance Variables ::::::::::::::::::::::::::: 17 2.6 Working with Class Objects ::::::::::::::::::::::::::::::::::: 17 2.6.1 Locating Classes Dynamically :::::::::::::::::::::::::::: 18 2.7 Naming Constraints and Conventions:::::::::::::::::::::::::: 18 2.8 Strings in GNUstep ::::::::::::::::::::::::::::::::::::::::::: 19 2.8.1 Creating NSString Static Instances ::::::::::::::::::::::: 19 2.8.2 NSString +stringWithFormat: :::::::::::::::::::::::::::: 19 2.8.3 C String Conversion :::::::::::::::::::::::::::::::::::::: 20 2.8.4 NSMutableString::::::::::::::::::::::::::::::::::::::::: 20 2.8.5 Loading and Saving Strings::::::::::::::::::::::::::::::: 21 ii Objective-C GNUstep Base Programming Manual 3 Working with Objects::::::::::::::::::::::::: 23 3.1 Initializing and Allocating Objects :::::::::::::::::::::::::::: 23 3.1.1 Initialization with Arguments::::::::::::::::::::::::::::: 23 3.1.2 Memory Allocation and Zones :::::::::::::::::::::::::::: 24 3.1.3 Memory Deallocation::::::::::::::::::::::::::::::::::::: 25 3.2 Memory Management ::::::::::::::::::::::::::::::::::::::::: 25 3.2.1 Explicit Memory Management :::::::::::::::::::::::::::: 25 3.2.2 OpenStep-Style (Retain/Release) Memory Management::: 26 3.2.2.1 Autorelease Pools ::::::::::::::::::::::::::::::::::: 27 3.2.2.2 Avoiding Retain Cycles:::::::::::::::::::::::::::::: 28 3.2.2.3 Summary ::::::::::::::::::::::::::::::::::::::::::: 29 3.2.3 Garbage Collection Based Memory Management :::::::::: 29 3.2.4 Current Recommendations ::::::::::::::::::::::::::::::: 30 4 Writing New Classes :::::::::::::::::::::::::: 31 4.1 Interface :::::::::::::::::::::::::::::::::::::::::::::::::::::: 31 4.1.1 Interface Capabilities ::::::::::::::::::::::::::::::::::::: 31 4.1.2 Including Interfaces :::::::::::::::::::::::::::::::::::::: 33 4.1.3 Referring to Classes - @class :::::::::::::::::::::::::::::: 33 4.2 Implementation ::::::::::::::::::::::::::::::::::::::::::::::: 34 4.2.1 Writing an Implementation ::::::::::::::::::::::::::::::: 35 4.2.2 Super and Self ::::::::::::::::::::::::::::::::::::::::::: 35 4.2.3 Instance Initialization :::::::::::::::::::::::::::::::::::: 36 4.2.4 Flexible Initialization::::::::::::::::::::::::::::::::::::: 39 4.2.5 Instance Deallocation :::::::::::::::::::::::::::::::::::: 40 4.3 Protocols ::::::::::::::::::::::::::::::::::::::::::::::::::::: 41 4.3.1 Declaring a Formal Protocol :::::::::::::::::::::::::::::: 41 4.3.2 Implementing a Formal Protocol:::::::::::::::::::::::::: 42 4.3.3 Using a Formal Protocol ::::::::::::::::::::::::::::::::: 42 4.4 Categories :::::::::::::::::::::::::::::::::::::::::::::::::::: 43 4.4.1 Category Overrides::::::::::::::::::::::::::::::::::::::: 44 4.4.2 Categories as an Implementation Tool :::::::::::::::::::: 44 4.4.3 Categories and Protocols ::::::::::::::::::::::::::::::::: 45 4.5 Simulating Private and Protected Methods :::::::::::::::::::: 45 4.6 Simulating Class Variables :::::::::::::::::::::::::::::::::::: 46 5 Advanced Messaging :::::::::::::::::::::::::: 49 5.1 How Messaging Works :::::::::::::::::::::::::::::::::::::::: 49 5.2 Selectors :::::::::::::::::::::::::::::::::::::::::::::::::::::: 50 5.2.1 The Target-Action Paradigm ::::::::::::::::::::::::::::: 50 5.2.2 Obtaining Selectors :::::::::::::::::::::::::::::::::::::: 51 5.2.3 Avoiding Messaging Errors when an Implementation is Not Found :::::::::::::::::::::::::::::::::::::::::::::::::::::: 51 5.3 Forwarding ::::::::::::::::::::::::::::::::::::::::::::::::::: 52 5.4 Implementations :::::::::::::::::::::::::::::::::::::::::::::: 53 iii 6 Exception Handling, Logging, and Assertions :::::::::::::::::::::::::::::::::::::::::::::::: 55 6.1 Exceptions :::::::::::::::::::::::::::::::::::::::::::::::::::: 55 6.1.1 Catching and Handling Exceptions ::::::::::::::::::::::: 55 6.1.2 Passing Exceptions Up the Call Stack :::::::::::::::::::: 57 6.1.3 Where do Exceptions Originate?:::::::::::::::::::::::::: 57 6.1.4 Creating Exceptions :::::::::::::::::::::::::::::::::::::: 57 6.1.5 When to Use Exceptions ::::::::::::::::::::::::::::::::: 58 6.2 Logging ::::::::::::::::::::::::::::::::::::::::::::::::::::::: 59 6.2.1 NSLog ::::::::::::::::::::::::::::::::::::::::::::::::::: 59 6.2.2 NSDebugLog, NSWarnLog ::::::::::::::::::::::::::::::: 59 6.2.3 Last Resorts: GSPrintf and fprintf:::::::::::::::::::::::: 61 6.2.4 Profiling Facilities :::::::::::::::::::::::::::::::::::::::: 61 6.3 Assertions :::::::::::::::::::::::::::::::::::::::::::::::::::: 61 6.3.1 Assertions and their Handling :::::::::::::::::::::::::::: 61 6.3.2 Custom Assertion Handling :::::::::::::::::::::::::::::: 62 6.4 Comparison with Java :::::::::::::::::::::::::::::::::::::::: 62 7 Distributed Objects ::::::::::::::::::::::::::: 65 7.1 Object Interaction :::::::::::::::::::::::::::::::::::::::::::: 65 7.2 The GNUstep Solution :::::::::::::::::::::::::::::::::::::::: 65 7.2.1 Code at the Server ::::::::::::::::::::::::::::::::::::::: 66 7.2.2 Code at the Client ::::::::::::::::::::::::::::::::::::::: 67 7.2.3 Using a Protocol ::::::::::::::::::::::::::::::::::::::::: 69 7.2.4 Complete Code for Telephone Directory Application :::::: 70 7.2.5 GNUstep Distributed Objects Name Server ::::::::::::::: 71 7.2.6 Look Ma, No Stubs! :::::::::::::::::::::::::::::::::::::: 72 7.3 A More Involved Example::::::::::::::::::::::::::::::::::::: 72 7.3.1 Protocol Adopted at Client ::::::::::::::::::::::::::::::: 73 7.3.2 Protocol Adopted at Server::::::::::::::::::::::::::::::: 73 7.3.3 Code at the Client ::::::::::::::::::::::::::::::::::::::: 73 7.3.4 Code at the Server ::::::::::::::::::::::::::::::::::::::: 76 7.4 Language Support for Distributed Objects::::::::::::::::::::: 81 7.4.1 Protocol Type Qualifiers ::::::::::::::::::::::::::::::::: 81 7.4.2 Message Forwarding :::::::::::::::::::::::::::::::::::::: 83 7.5 Error Checking ::::::::::::::::::::::::::::::::::::::::::::::: 84 7.5.1 Vending the Server Object:::::::::::::::::::::::::::::::: 84 7.5.2 Catching Exceptions ::::::::::::::::::::::::::::::::::::: 84 7.5.3 The Connection Fails::::::::::::::::::::::::::::::::::::: 84 iv Objective-C GNUstep Base Programming Manual 8 Base Library ::::::::::::::::::::::::::::::::::: 85 8.1 Copying, Comparing, Hashing Objects::::::::::::::::::::::::: 85 8.2 Object Containers::::::::::::::::::::::::::::::::::::::::::::: 86 8.3 Data and Number Containers ::::::::::::::::::::::::::::::::: 87 8.3.1 NSData :::::::::::::::::::::::::::::::::::::::::::::::::: 87 8.3.2 NSValue ::::::::::::::::::::::::::::::::::::::::::::::::: 88 8.3.3 NSNumber ::::::::::::::::::::::::::::::::::::::::::::::: 88 8.3.4 NSRange, NSPoint, NSSize, NSRect :::::::::::::::::::::: 89 8.4 Date/Time Facilities :::::::::::::::::::::::::::::::::::::::::: 89 8.5 String Manipulation and Text Processing :::::::::::::::::::::: 89 8.5.1 NSScanner and Character Sets ::::::::::::::::::::::::::: 89 8.5.2 Attributed Strings:::::::::::::::::::::::::::::::::::::::: 89 8.5.3 Formatters :::::::::::::::::::::::::::::::::::::::::::::::
Load more

Recommended publications
  • Deserialization Vulnerability by Abdelazim Mohammed(@Intx0x80)
    Deserialization vulnerability By Abdelazim Mohammed(@intx0x80) Thanks to: Mazin Ahmed (@mazen160) Asim Jaweesh(@Jaw33sh) 1 | P a g e Table of Contents Serialization (marshaling): ............................................................................................................................ 4 Deserialization (unmarshaling): .................................................................................................................... 4 Programming language support serialization: ............................................................................................... 4 Risk for using serialization: .......................................................................................................................... 5 Serialization in Java ...................................................................................................................................... 6 Deserialization vulnerability in Java: ............................................................................................................ 6 Code flow work........................................................................................................................................... 11 Vulnerability Detection: .............................................................................................................................. 12 CVE: ........................................................................................................................................................... 17 Tools: .........................................................................................................................................................
    [Show full text]
  • Palmetto Tatters Guild Glossary of Tatting Terms (Not All Inclusive!)
    Palmetto Tatters Guild Glossary of Tatting Terms (not all inclusive!) Tat Days Written * or or To denote repeating lines of a pattern. Example: Rep directions or # or § from * 7 times & ( ) Eg. R: 5 + 5 – 5 – 5 (last P of prev R). Modern B Bead (Also see other bead notation below) notation BTS Bare Thread Space B or +B Put bead on picot before joining BBB B or BBB|B Three beads on knotting thread, and one bead on core thread Ch Chain ^ Construction picot or very small picot CTM Continuous Thread Method D Dimple: i.e. 1st Half Double Stitch X4, 2nd Half Double Stitch X4 dds or { } daisy double stitch DNRW DO NOT Reverse Work DS Double Stitch DP Down Picot: 2 of 1st HS, P, 2 of 2nd HS DPB Down Picot with a Bead: 2 of 1st HS, B, 2 of 2nd HS HMSR Half Moon Split Ring: Fold the second half of the Split Ring inward before closing so that the second side and first side arch in the same direction HR Half Ring: A ring which is only partially closed, so it looks like half of a ring 1st HS First Half of Double Stitch 2nd HS Second Half of Double Stitch JK Josephine Knot (Ring made of only the 1st Half of Double Stitch OR only the 2nd Half of Double Stitch) LJ or Sh+ or SLJ Lock Join or Shuttle join or Shuttle Lock Join LPPCh Last Picot of Previous Chain LPPR Last Picot of Previous Ring LS Lock Stitch: First Half of DS is NOT flipped, Second Half is flipped, as usual LCh Make a series of Lock Stitches to form a Lock Chain MP or FP Mock Picot or False Picot MR Maltese Ring Pearl Ch Chain made with pearl tatting technique (picots on both sides of the chain, made using three threads) P or - Picot Page 1 of 4 PLJ or ‘PULLED LOOP’ join or ‘PULLED LOCK’ join since it is actually a lock join made after placing thread under a finished ring and pulling this thread through a picot.
    [Show full text]
  • Scoping Changes with Method Namespaces
    Scoping Changes with Method Namespaces Alexandre Bergel ADAM Project, INRIA Futurs Lille, France [email protected] Abstract. Size and complexity of software has reached a point where modular constructs provided by traditional object-oriented programming languages are not expressive enough. A typical situation is how to modify a legacy code without breaking its existing clients. We propose method namespaces as a visibility mechanism for behavioral refine- ments of classes (method addition and redefinition). New methods may be added and existing methods may be redefined in a method namespace. This results in a new version of a class accessible only within the defining method namespace. This mechanism, complementary to inheritance in object-orientation and tradi- tional packages, allows unanticipated changes while minimizing the impact on former code. Method Namespaces have been implemented in the Squeak Smalltalk system and has been successfully used to provide a translated version of a library without ad- versely impacting its original clients. We also provide benchmarks that demon- strate its application in a practical setting. 1 Introduction Managing evolution and changes is a critical part of the life cycle of all software sys- tems [BMZ+05, NDGL06]. In software, changes are modeled as a set of incremental code refinements such as class redefinition, method addition, and method redefinition. Class-based object-oriented programming languages (OOP) models code refinements with subclasses that contain behavioral differences. It appears that subclassing is well adapted when evolution is anticipated. For example, most design patterns and frame- works rely on class inheritance to express future anticipated adaptation and evolution. However, subclassing does not as easily help in expressing unanticipated software evo- lution [FF98a, BDN05b].
    [Show full text]
  • Working with System Frameworks in Python and Objective-C
    Working with System Frameworks in Python and Objective-C by James Barclay Feedback :) j.mp/psumac2015-62 2 Dude, Where’s My Source Code? CODE https://github.com/futureimperfect/psu-pyobjc-demo https://github.com/futureimperfect/PSUDemo SLIDES https://github.com/futureimperfect/slides 3 Dude, Where’s My Source Code? CODE https://github.com/futureimperfect/psu-pyobjc-demo https://github.com/futureimperfect/PSUDemo SLIDES https://github.com/futureimperfect/slides 3 Dude, Where’s My Source Code? CODE https://github.com/futureimperfect/psu-pyobjc-demo https://github.com/futureimperfect/PSUDemo SLIDES https://github.com/futureimperfect/slides 3 Agenda 1. What are system frameworks, and why should you care? 2. Brief overview of the frameworks, classes, and APIs that will be demonstrated. 3. Demo 1: PyObjC 4. Demo 2: Objective-C 5. Wrap up and questions. 4 What’s a System Framework? …and why should you care? (OS X) system frameworks provide interfaces you need to write software for the Mac. Many of these are useful for Mac admins creating: • scripts • GUI applications • command-line tools Learning about system frameworks will teach you more about OS X, which will probably make you a better admin. 5 Frameworks, Classes, and APIs oh my! Cocoa CoreFoundation • Foundation • CFPreferences - NSFileManager CoreGraphics - NSTask • Quartz - NSURLSession - NSUserDefaults • AppKit - NSApplication 6 CoreFoundation CoreFoundation is a C framework that knows about Objective-C objects. Some parts of CoreFoundation are written in Objective-C. • Other parts are written in C. CoreFoundation uses the CF class prefix, and it provides CFString, CFDictionary, CFPreferences, and the like. Some Objective-C objects are really CF types behind the scenes.
    [Show full text]
  • Download the Specification
    Internationalizing and Localizing Applications in Oracle Solaris Part No: E61053 November 2020 Internationalizing and Localizing Applications in Oracle Solaris Part No: E61053 Copyright © 2014, 2020, Oracle and/or its affiliates. License Restrictions Warranty/Consequential Damages Disclaimer This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. Warranty Disclaimer The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. Restricted Rights Notice If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial
    [Show full text]
  • Investigating Powershell Attacks
    Investigating PowerShell Attacks Black Hat USA 2014 August 7, 2014 PRESENTED BY: Ryan Kazanciyan, Matt Hastings © Mandiant, A FireEye Company. All rights reserved. Background Case Study WinRM, Victim VPN SMB, NetBIOS Attacker Victim workstations, Client servers § Fortune 100 organization § Command-and-control via § Compromised for > 3 years § Scheduled tasks § Active Directory § Local execution of § Authenticated access to PowerShell scripts corporate VPN § PowerShell Remoting © Mandiant, A FireEye Company. All rights reserved. 2 Why PowerShell? It can do almost anything… Execute commands Download files from the internet Reflectively load / inject code Interface with Win32 API Enumerate files Interact with the registry Interact with services Examine processes Retrieve event logs Access .NET framework © Mandiant, A FireEye Company. All rights reserved. 3 PowerShell Attack Tools § PowerSploit § Posh-SecMod § Reconnaissance § Veil-PowerView § Code execution § Metasploit § DLL injection § More to come… § Credential harvesting § Reverse engineering § Nishang © Mandiant, A FireEye Company. All rights reserved. 4 PowerShell Malware in the Wild © Mandiant, A FireEye Company. All rights reserved. 5 Investigation Methodology WinRM PowerShell Remoting evil.ps1 backdoor.ps1 Local PowerShell script Persistent PowerShell Network Registry File System Event Logs Memory Traffic Sources of Evidence © Mandiant, A FireEye Company. All rights reserved. 6 Attacker Assumptions § Has admin (local or domain) on target system § Has network access to needed ports on target system § Can use other remote command execution methods to: § Enable execution of unsigned PS scripts § Enable PS remoting © Mandiant, A FireEye Company. All rights reserved. 7 Version Reference 2.0 3.0 4.0 Requires WMF Requires WMF Default (SP1) 3.0 Update 4.0 Update Requires WMF Requires WMF Default (R2 SP1) 3.0 Update 4.0 Update Requires WMF Default 4.0 Update Default Default Default (R2) © Mandiant, A FireEye Company.
    [Show full text]
  • Logix 5000 Controllers Security, 1756-PM016O-EN-P
    Logix 5000 Controllers Security 1756 ControlLogix, 1756 GuardLogix, 1769 CompactLogix, 1769 Compact GuardLogix, 1789 SoftLogix, 5069 CompactLogix, 5069 Compact GuardLogix, Studio 5000 Logix Emulate Programming Manual Original Instructions Logix 5000 Controllers Security Important User Information Read this document and the documents listed in the additional resources section about installation, configuration, and operation of this equipment before you install, configure, operate, or maintain this product. Users are required to familiarize themselves with installation and wiring instructions in addition to requirements of all applicable codes, laws, and standards. Activities including installation, adjustments, putting into service, use, assembly, disassembly, and maintenance are required to be carried out by suitably trained personnel in accordance with applicable code of practice. If this equipment is used in a manner not specified by the manufacturer, the protection provided by the equipment may be impaired. In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the use or application of this equipment. The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and requirements associated with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or liability for actual use based on the examples and diagrams. No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or software described in this manual. Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation, Inc., is prohibited. Throughout this manual, when necessary, we use notes to make you aware of safety considerations.
    [Show full text]
  • Bringing GNU Emacs to Native Code
    Bringing GNU Emacs to Native Code Andrea Corallo Luca Nassi Nicola Manca [email protected] [email protected] [email protected] CNR-SPIN Genoa, Italy ABSTRACT such a long-standing project. Although this makes it didactic, some Emacs Lisp (Elisp) is the Lisp dialect used by the Emacs text editor limitations prevent the current implementation of Emacs Lisp to family. GNU Emacs can currently execute Elisp code either inter- be appealing for broader use. In this context, performance issues preted or byte-interpreted after it has been compiled to byte-code. represent the main bottleneck, which can be broken down in three In this work we discuss the implementation of an optimizing com- main sub-problems: piler approach for Elisp targeting native code. The native compiler • lack of true multi-threading support, employs the byte-compiler’s internal representation as input and • garbage collection speed, exploits libgccjit to achieve code generation using the GNU Com- • code execution speed. piler Collection (GCC) infrastructure. Generated executables are From now on we will focus on the last of these issues, which con- stored as binary files and can be loaded and unloaded dynamically. stitutes the topic of this work. Most of the functionality of the compiler is written in Elisp itself, The current implementation traditionally approaches the prob- including several optimization passes, paired with a C back-end lem of code execution speed in two ways: to interface with the GNU Emacs core and libgccjit. Though still a work in progress, our implementation is able to bootstrap a func- • Implementing a large number of performance-sensitive prim- tional Emacs and compile all lexically scoped Elisp files, including itive functions (also known as subr) in C.
    [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]
  • GNU Guix Cookbook Tutorials and Examples for Using the GNU Guix Functional Package Manager
    GNU Guix Cookbook Tutorials and examples for using the GNU Guix Functional Package Manager The GNU Guix Developers Copyright c 2019 Ricardo Wurmus Copyright c 2019 Efraim Flashner Copyright c 2019 Pierre Neidhardt Copyright c 2020 Oleg Pykhalov Copyright c 2020 Matthew Brooks Copyright c 2020 Marcin Karpezo Copyright c 2020 Brice Waegeneire Copyright c 2020 Andr´eBatista Copyright c 2020 Christine Lemmer-Webber Copyright c 2021 Joshua Branson Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled \GNU Free Documentation License". i Table of Contents GNU Guix Cookbook ::::::::::::::::::::::::::::::: 1 1 Scheme tutorials ::::::::::::::::::::::::::::::::: 2 1.1 A Scheme Crash Course :::::::::::::::::::::::::::::::::::::::: 2 2 Packaging :::::::::::::::::::::::::::::::::::::::: 5 2.1 Packaging Tutorial:::::::::::::::::::::::::::::::::::::::::::::: 5 2.1.1 A \Hello World" package :::::::::::::::::::::::::::::::::: 5 2.1.2 Setup:::::::::::::::::::::::::::::::::::::::::::::::::::::: 8 2.1.2.1 Local file ::::::::::::::::::::::::::::::::::::::::::::: 8 2.1.2.2 `GUIX_PACKAGE_PATH' ::::::::::::::::::::::::::::::::: 9 2.1.2.3 Guix channels ::::::::::::::::::::::::::::::::::::::: 10 2.1.2.4 Direct checkout hacking:::::::::::::::::::::::::::::: 10 2.1.3 Extended example ::::::::::::::::::::::::::::::::::::::::
    [Show full text]
  • Emacs Speaks Statistics (ESS): a Multi-Platform, Multi-Package Intelligent Environment for Statistical Analysis
    Emacs Speaks Statistics (ESS): A multi-platform, multi-package intelligent environment for statistical analysis A.J. Rossini Richard M. Heiberger Rodney A. Sparapani Martin Machler¨ Kurt Hornik ∗ Date: 2003/10/22 17:34:04 Revision: 1.255 Abstract Computer programming is an important component of statistics research and data analysis. This skill is necessary for using sophisticated statistical packages as well as for writing custom software for data analysis. Emacs Speaks Statistics (ESS) provides an intelligent and consistent interface between the user and software. ESS interfaces with SAS, S-PLUS, R, and other statistics packages under the Unix, Microsoft Windows, and Apple Mac operating systems. ESS extends the Emacs text editor and uses its many features to streamline the creation and use of statistical software. ESS understands the syntax for each data analysis language it works with and provides consistent display and editing features across packages. ESS assists in the interactive or batch execution by the statistics packages of statements written in their languages. Some statistics packages can be run as a subprocess of Emacs, allowing the user to work directly from the editor and thereby retain a consistent and constant look- and-feel. We discuss how ESS works and how it increases statistical programming efficiency. Keywords: Data Analysis, Programming, S, SAS, S-PLUS, R, XLISPSTAT,STATA, BUGS, Open Source Software, Cross-platform User Interface. ∗A.J. Rossini is Research Assistant Professor in the Department of Biostatistics, University of Washington and Joint Assis- tant Member at the Fred Hutchinson Cancer Research Center, Seattle, WA, USA mailto:[email protected]; Richard M.
    [Show full text]
  • 1 What Is Gimp? 3 2 Default Short Cuts and Dynamic Keybinding 9
    GUM The Gimp User Manual version 1.0.0 Karin Kylander & Olof S Kylander legalities Legalities The Gimp user manual may be reproduced and distributed, subject to the fol- lowing conditions: Copyright © 1997 1998 by Karin Kylander Copyright © 1998 by Olof S Kylander E-mail: [email protected] (summer 98 [email protected]) The Gimp User Manual is an open document; you may reproduce it under the terms of the Graphic Documentation Project Copying Licence (aka GDPL) as published by Frozenriver. This document is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANT- ABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the Graphic Documentation Project Copying License for more details. GRAPHIC DOCUMENTATION PROJECT COPYING LICENSE The following copyright license applies to all works by the Graphic Docu- mentation Project. Please read the license carefully---it is similar to the GNU General Public License, but there are several conditions in it that differ from what you may be used to. The Graphic Documentation Project manuals may be reproduced and distrib- uted in whole, subject to the following conditions: The Gimp User Manual Page i Legalities All Graphic Documentation Project manuals are copyrighted by their respective authors. THEY ARE NOT IN THE PUBLIC DOMAIN. • The copyright notice above and this permission notice must be preserved complete. • All work done under the Graphic Documentation Project Copying License must be available in source code for anyone who wants to obtain it. The source code for a work means the preferred form of the work for making modifications to it.
    [Show full text]