Introduction

The Application Kit is the starting point for all applications. Its classes establish an application as an identifiable entity, one that can cooperate and communicate with other applications.

The Application Kit is divided into these topics:

BApplication. All but the simplest of applications must have one (and only one) BApplication object. This object is typically an instance of a BApplication subclass that you create especially for your application. The BApplication object makes a connection to the App Server and runs the application’s main message loop.

Messaging. The kit provides a messaging service that lets threads talk to each other. This service can deliver messages within your own application, or from one application to another. It’s also used by the system to deliver user event messages (key clicks, mouse moves) to your application. Most of the Application Kit’s classes are involved in the messaging system.

Scripting. The objects that you create can be controlled by commands issued from other applications.

BRoster. The BRoster object keeps track of all running applications. It can identify applications, launch them, and provide the information needed to set up communications with them.

BClipboard. The BClipboard object provides an interface to the clipboard where cut and copied data can be stored, and from which it can be pasted.

BCursor. You use BCursor objects to represent distinct cursors. Functions defined by BApplication and BView let you assign your cursors to your entire application, or to individual views.