projects / wxWidgets.git / blame
| Commit | Line | Data |
|---|---|---|
| 15b6757b FM |
1 | ///////////////////////////////////////////////////////////////////////////// |
| 2 | // Name: aui | |
| 3 | // Purpose: topic overview | |
| 4 | // Author: wxWidgets team | |
| 5 | // RCS-ID: $Id$ | |
| 6 | // Licence: wxWindows license | |
| 7 | ///////////////////////////////////////////////////////////////////////////// | |
| 8 | ||
| 9 | /*! | |
| 36c9828f | 10 | |
| 15b6757b | 11 | @page aui_overview wxAUI overview |
| 36c9828f | 12 | |
| 15b6757b FM |
13 | Class: #wxAuiManager, #wxAuiPaneInfo |
| 14 | wxAUI stands for Advanced User Interface and the wxAUI framework | |
| 15 | aims to give its user a cutting edge interface for use with the | |
| 16 | wxWidgets based applications. The original wxAUI sources have | |
| 17 | kindly been made available under the wxWindows licence | |
| 18 | by Kirix Corp. and they have since then been integrated into | |
| 19 | wxWidgets CVS and further improved. | |
| 20 | wxAUI attempts to encapsulate the following aspects of the user interface: | |
| 21 | @b Frame Management: | |
| 22 | Frame management provides the means to open, move and hide common | |
| 23 | controls that are needed to interact with the document, and allow these | |
| 24 | configurations to be saved into different perspectives and loaded at a | |
| 25 | later time. | |
| 26 | @b Toolbars: | |
| 27 | Toolbars are a specialized subset of the frame management system and | |
| 28 | should behave similarly to other docked components. However, they also | |
| 29 | require additional functionality, such as "spring-loaded" rebar support, | |
| 30 | "chevron" buttons and end-user customizability. | |
| 31 | @b Modeless Controls: | |
| 32 | Modeless controls expose a tool palette or set of options that float | |
| 33 | above the application content while allowing it to be accessed. Usually | |
| 34 | accessed by the toolbar, these controls disappear when an option is | |
| 35 | selected, but may also be "torn off" the toolbar into a floating frame | |
| 36 | of their own. | |
| 37 | @b Look and Feel: | |
| 38 | Look and feel encompasses the way controls are drawn, both when shown | |
| 39 | statically as well as when they are being moved. This aspect of user | |
| 40 | interface design incorporates "special effects" such as transparent | |
| 41 | window dragging as well as frame animation. | |
| 42 | wxAUI adheres to the following principles: | |
| 43 | Use native floating frames to obtain a native look and feel for all | |
| 44 | platforms. Use existing wxWidgets code where possible, such as sizer | |
| 45 | implementation for frame management. Use classes included in wxCore | |
| 46 | and wxBase only. Use standard wxWidgets coding conventions. | |
| 36c9828f | 47 | |
| 15b6757b | 48 | */ |
| 36c9828f FM |
49 | |
| 50 |