]> git.saurik.com Git - wxWidgets.git/blame - docs/doxygen/platdetails.h
add meta to manifests
[wxWidgets.git] / docs / doxygen / platdetails.h
CommitLineData
15b6757b
FM
1/////////////////////////////////////////////////////////////////////////////
2// Name: platdetails.h
3// Purpose: Platform details page of the Doxygen manual
4// Author: wxWidgets team
5// RCS-ID: $Id$
6// Licence: wxWindows license
7/////////////////////////////////////////////////////////////////////////////
8
9
10/*!
11
12 @page platformdetails_page Platform details
13
14 wxWidgets defines a common API across platforms, but uses the native graphical
15 user interface (GUI) on each platform, so your program will take on the native
16 look and feel that users are familiar with. Unfortunately native toolkits and
17 hardware do not always support the functionality that the wxWidgets API
36c9828f 18 requires. This chapter collects notes about differences among supported platforms
15b6757b
FM
19 and ports.
20
21 @li @ref nativedocs
22
23
24 <hr>
25
26 \input wxgtk.tex
27 \input wxmsw.tex
28 \input wxmac.tex
29 \input wxpalm.tex
30 \input wxos2.tex
31 \input wxmgl.tex
32 \input wxx11.tex
36c9828f 33
15b6757b
FM
34
35 @section nativedocs Documentation for the native toolkits
36c9828f 36
15b6757b
FM
37 It's sometimes useful to interface directly with the underlying toolkit
38 used by wxWidgets to e.g. use toolkit-specific features.
39 In such case (or when you want to e.g. write a port-specific patch) it can be
40 necessary to use the underlying toolkit API directly:
36c9828f 41
15b6757b
FM
42 @li wxMSW port uses win32 API: see MSDN docs at http://msdn2.microsoft.com/en-us/library/ms649779.aspx
43 @li wxGTK port uses GTK+: see GTK+ 2.x docs at http://developer.gnome.org/doc/API/2.0/gtk/index.html
44
45*/