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