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