]>
Commit | Line | Data |
---|---|---|
1 | \chapter{Platform details}\label{platformdetails} | |
2 | \setheader{{\it CHAPTER \thechapter}}{}{}{}{}{{\it CHAPTER \thechapter}}% | |
3 | \setfooter{\thepage}{}{}{}{}{\thepage}% | |
4 | ||
5 | wxWidgets defines a common API across platforms, but uses the native graphical | |
6 | user interface (GUI) on each platform, so your program will take on the native | |
7 | look and feel that users are familiar with. Unfortunately native toolkits and | |
8 | hardware do not always support the functionality that the wxWidgets API | |
9 | requires. This chapter collects notes about differences among supported platforms and ports. | |
10 | ||
11 | \input wxgtk.tex | |
12 | \input wxmsw.tex | |
13 | \input wxmac.tex | |
14 | \input wxpalm.tex | |
15 | \input wxos2.tex | |
16 | \input wxmgl.tex | |
17 | \input wxx11.tex | |
18 | ||
19 | \subsection{Documentation for the native toolkits}\label{nativedocs} | |
20 | ||
21 | It's sometimes useful to interface directly with the underlying toolkit | |
22 | used by wxWidgets to e.g. use toolkit-specific features. | |
23 | In such case (or when you want to e.g. write a port-specific patch) it can be | |
24 | necessary to use the underlying toolkit API directly: | |
25 | ||
26 | \begin{description}\itemsep=0pt | |
27 | \item[{\bf wxMSW}] | |
28 | wxMSW port uses win32 API: \urlref{MSDN docs}{http://msdn2.microsoft.com/en-us/library/ms649779.aspx} | |
29 | ||
30 | \item[{\bf wxGTK}] | |
31 | wxGTK port uses GTK+: \urlref{GTK+ 2.x docs}{http://developer.gnome.org/doc/API/2.0/gtk/index.html} | |
32 | ||
33 | \end{description} |