haiku/docs/user/app/_app_intro.dox
John Scipione 820dca4df6 Big docs cleanup.
* Fixed headers including:
  - All rights reserved not All Rights Reserved.
  - name, email@domain.com not name <email@domain.com>
  - tabs and spaces
  - Authors: not Documented by:
* Renamed string.dox to String.dox
* Renamed midixxx.dox files to MidiXxx.dox
* Moved images into images subdirectories and updated Doxfile.
* Re-format all files with tabs instead of spaces.
* Fix many spelling mistakes.
* Added all files, classes, structs, and enums to libbe group.
2013-02-07 02:01:19 -05:00

43 lines
1.3 KiB
Plaintext

/*
* Copyright 2007 Haiku, Inc. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
* Niels Sascha Reedijk, niels.reedijk@gmail.com
*/
/*!
\page app_intro Introduction to the Application Kit.
The Application Kit should be your starting point if you want to write
native Haiku applications with a GUI. The application kit does
exactly as its name suggests; it is the basis for Haiku applications. You
should read through this document and the documents referenced here before
moving on to any other part of the API.
The Application Kit classes can be divided into two groups: the "messaging"
classes and the "system interaction" classes. The larger group contains
the messaging classes. Have a look at the \link app_messaging
Introduction to Messaging \endlink for more information.
The following classes are messaging classes:
- BHandler
- BInvoker
- BLooper
- BMessage
- BMessageFilter
- BMessageQueue
- BMessageRunner
- BMessenger
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 is BApplication. This is a list of all the
system interaction classes:
- BApplication
- BClipboard
- BCursor
- BPropertyInfo
- BRoster
*/