Special

Introducing the “Welcome to Xojo” Bundle!

New to Xojo and looking for guidance? We've put together a terrific bundle to welcome you! Xojo Bundle

This bundle includes six back issues of the magazine -- all of year 18 in printed book and digital formats -- plus a one-year subscription (beginning with 19.1) so you'll be learning all about Xojo for the next year. It's the perfect way to get started programming with Xojo. And you save as much as $35 over the non-bundle price!

This offer is only available for a limited time as supplies are limited, so hurry today and order this special bundle before the offer goes away!

Article Preview


Buy Now

Issue 1.6

COLUMN

AppleScriptable Applications

Implementing classes and events from the Standard Suite

Issue: 1.6 (June/July 2003)
Author: Thomas Reed
Author Bio: Thomas Reed has been programming as a hobbyist for more than 20 years, and fell in love with the Mac in 1984. Thanks to Patrick Wynne for help with some of the concepts in this article!
Article Description: No description available.
Article Length (in bytes): 9,927
Starting Page Number: 30
Article Number: 1615
Resource File(s):

Download Icon 1615.zip Updated: 2013-03-11 19:07:56

Related Web Link(s):

http://www.panix.com/~gmcgath/EightyRez.html
http://www.westcodesoft.com/downloads/
http://developer.apple.com/techpubs/mac/IAC/IAC-2.html

Excerpt of article text...

Last issue's column discussed the basics of creating an AppleScriptable application. This issue will expand on that information, demonstrating how to define and handle standard AppleScript commands, which are more complex. The primary focus of this column will be the implementation of classes in your application's AppleScript interface.

A class in AppleScript acts as a container for properties, much like a class in REALbasic. However, it does not define events or methods as can be present in a REALbasic class. In the sample ArbieText application from the last issue, the AppleScript commands only interact with windows and their contents; thus, a window class is obviously called for.

Before defining a class in the 'aete' resource, a suite must be defined to contain it. Since we want to give ArbieText a more standard AppleScript interface, objects and classes from the Standard Suite should be used. Therefore, the first step in building the new 'aete' resource is to define this suite.

...End of Excerpt. Please purchase the magazine to read the full article.