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