The Application Kit is the starting point for writing native Haiku GUI applications. More...
|A container object for an application. More...|
|Used for short-term data storage between documents and applications via copy and paste operations. More...|
|BCursor describes a view-wide or application-wide cursor. More...|
|Handles messages that are passed on by a BLooper. More...|
|Receive and process messages in a separate thread. More...|
|A container that can be send and received using the Haiku messaging subsystem. More...|
|Describes a message filter for BLooper and BHandler. More...|
|A container that maintains a queue of messages. More...|
Provides the BApplication class.
Provides the BClipboard class.
Provides the BCursor class.
Provides the BHandler class.
Provides the BLooper class.
Provides the BMessage class.
Provides BMessageFilter class.
Provides the BMessageQueue class.
The Application Kit is the starting point for writing native Haiku GUI applications.
The application kit is exactly what its name suggests — it is the basis of Haiku applications. You should first read through this document and the references here before moving on to the other parts of the API.
The Application Kit classes can be divided into two groups: the messaging classes and the system interaction classes. The larger of the two groups is the messaging classes. Since the Haiku API relies on pervasive multithreading messaging is an essential topic for any application. Have a look at the Introduction to Messaging for more information.
The following messaging classes which allow you to easily and securely communicate between threads.
The second group is the system interaction classes. These classes provide hooks for your application to interact with the rest of the system. The most important class in this group is BApplication. Below is a list of all system interaction classes: