REALbasic Developer’s Guide Documentation by Geoff Perlman and David Brandt. © 1999-2000 by REAL Software, Inc. All rights reserved. Printed in U.S.A. Mailing Address REAL Software, Inc. 3300 Bee Caves Road Suite 650-220 Austin, TX 78746 Web Site http://www.realsoftware.com ftp Site ftp://ftp.realsoftware.com Support support@realsoftware.com Bugs/ bugs@realsoftware.com Feature Requests Sales sales@realsoftware.com Phone 512-263-1233 Fax 512-263-1441 V2.1, April, 2000 Contents CHAPTER 1 Introduction . . . . . . . . . . . . . . 9 Contents . . . . . . . . . . . . . . . . . . . . 9 Welcome to REALbasic . . . . . . . . . . . . 10 Installing REALbasic . . . . . . . . . . . . . 11 Where to Begin . . . . . . . . . . . . . . . 12 Documentation Conventions . . . . . . . . 12 Using the On-Line Help . . . . . . . . . . . 14 Other Helpful Resources . . . . . . . . . . . 17 Contacting REAL Software . . . . . . . . . 20 CHAPTER 2 Getting Started with REALbasic . . . . . . . . . . . . . . . 23 Concepts . . . . . . . . . . . . . . . . . . . 24 The Development Environment . . . . . . . 26 Working with Projects . . . . . . . . . . . . 31 CHAPTER 3 Building a User Interface . . . 35 Working with Windows . . . . . . . . . . . 36 Interacting with the User Through Controls 43 Object Binding . . . . . . . . . . . . . . . 110 Adding Menus and Menu Items . . . . . . 118 Apple’s Macintosh User Interface Guidelines. 125 REALbasic Developer’s Guide iii Contents CHAPTER 4 BASIC Programming Concepts 127 Contents . . . . . . . . . . . . . . . . . . 127 BASIC versus REALbasic . . . . . . . . . . 128 Storing Values in Properties and Variables 129 Executing Instructions with Methods . . . 142 Comparison Operators . . . . . . . . . . . 147 Executing Instructions Repeatedly with Loops 149 Making Decisions with Branching . . . . . 156 CHAPTER 5 Programming with Events and Objects . . . . . . . . . . . . . 161 Contents . . . . . . . . . . . . . . . . . . 162 Understanding Event-Driven Programming 162 Using The Code Editor . . . . . . . . . . . 163 Printing Your Code . . . . . . . . . . . . . 179 Importing and Exporting Your Clas…

Magnifique Developerʼs Guide So, you want to develop a theme. Developers are important, Magnifique would not be here without them. Weʼve made the theme making process as easy as possible. To create basic theme files you do not need to know any coding whatsoever. Hereʼs how to start. The only real part the developer needs to do is create a “root” folder. The root folder contains everything the theme will install. Hereʼs a basic tree map of what a root folder CAN contain (doesnʼt have to contain everything, but this is what its possible to contain): root -- window --- ArtFile.bin --- AquaUI.bundle --- Extras.rsrc --- Extras2.rsrc --- LeopardUI.bundle --- SArtFile.bin -- dock --- <any dock resource file> -- custom --- <any custom files organized by directory structure> -- scripts --- preinstall --- postinstall --- restore Hereʼs a real Finder picture of what this would look like: The “window” folder = Main system (window theme), “dock” folder = Dock theme and “custom” and “scripts” folders go together, they = custom theme. You can have one or any combination of these 3 to use (again, not all the files have to be there, only the ones you will use). Note that each of these 3 will be presented as options on the “Apply Theme” dialog, and they all wonʼt just automatically installed (you can pick and choose Dock, main system-window theme, and custom mods, choosing one, two, or all three) Letʼs go through each of the 3 in order. Window (main system theme). This has the ability to install ArtFile.bin, SArtFile,bin, Extras.rsrc, Extras2.rsrc, LeopardUI.bundle, AquaUI.bundle. You donʼt need to include all the files, only the ones you modified. For example here is the root >> window folder of the iLeopard theme: Just like it looks, create a “window” folder inside the root folder and put the files in there. Note that this “window” folder will ONLY install the files mentioned above, it will not install anything else. Dock theme This adds a Dock theme. Simply create a “dock” folder inside the root folder and put your modified Dock resource files in there. Anything in the “dock” folder will be installed to /System/Library/CoreServices/Dock.app/Contents/Resources/ overwriting any existing files. Here is a screenshot of some of the files in a dock theme: Custom theme The most flexible, and also the hardest one to do. This allows you to install ANY file to the system. 2 sections for this, placing the files, and writing scripts. -- Placing files For custom, files are placed in a hierarchal directory structure. For example, lets say you had the custom file “/System/Library/CustomFile.X”. To do this you would use a structure like this: root -- custom --- System ---- Library ---- CustomFile.X So…