X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/bbc5b7f89717d555d19b08cd6172cb4cf1719099..f87ddf1834c677a33f0c8d243d580d6d105447ef:/docs/doxygen/mainpages/platdetails.h diff --git a/docs/doxygen/mainpages/platdetails.h b/docs/doxygen/mainpages/platdetails.h index ce9dbb56bc..9eb787eb69 100644 --- a/docs/doxygen/mainpages/platdetails.h +++ b/docs/doxygen/mainpages/platdetails.h @@ -3,7 +3,7 @@ // Purpose: Platform details page of the Doxygen manual // Author: wxWidgets team // RCS-ID: $Id$ -// Licence: wxWindows license +// Licence: wxWindows licence ///////////////////////////////////////////////////////////////////////////// @@ -19,11 +19,11 @@ requires. This chapter collects notes about differences among supported platform and ports. @li @ref page_port_wxgtk -@li @ref page_port_wxmac -@li @ref page_port_wxcocoa +@li @ref page_port_wxosx @li @ref page_port_wxos2 @li @ref page_port_wxmgl @li @ref page_port_wxx11 +@li @ref page_port_wxmotif @li @ref page_port_wxmsw @li @ref page_port_nativedocs @@ -35,7 +35,7 @@ and ports. @section page_port_wxgtk wxGTK @htmlonly - + @endhtmlonly wxGTK is a port of wxWidgets using the GTK+ library. @@ -53,10 +53,10 @@ You will need GTK+ 2.6 or higher which is available from: http://www.gtk.org The newer version of GTK+ you use, the more native widgets and -features will be utilized. We have gone to a great extent to -allow compiling wxWidgets applications with a latest version of +features will be utilized. We have gone to great lengths to +allow compiling wxWidgets applications with the latest version of GTK+, with the resulting binary working on systems even with a -much lower version of GTK+. You will have to ensure that the +much earlier version of GTK+. You will have to ensure that the application is launched with lazy symbol binding for that. In order to configure wxWidgets to compile wxGTK you will @@ -66,48 +66,61 @@ This is the default for many systems. GTK+ 1.2 can still be used, albeit discouraged. For that you can pass @c --with-gtk=1 to the @c configure script. -For further information, please see the files in docs/gtk +For further information, please see the files in @c docs/gtk in the distribution. - - -@section page_port_wxmac wxMac +@section page_port_wxosx wxOSX @htmlonly - @endhtmlonly -wxMac is a port of wxWidgets for the Macintosh OS platform. -Currently MacOS X 10.4 or higher are supported. wxMac can +@subsection page_port_wxosx_carbon wxOSX/Carbon + +wxOSX/Carbon is a port of wxWidgets for the Macintosh OS platform. +Currently MacOS X 10.4 or higher are supported. wxOSX/Carbon can be compiled both using Apple's command line developer tools -as well as Apple's XCode IDE. wxMac supports both the Intel +as well as Apple's Xcode IDE. wxOSX/Carbon supports both the Intel and PowerPC architectures and can be used to produce "universal binaries" in order create application which can run -both architecture. Unfortunately, wxMac does not support any +both architecture. Unfortunately, wxOSX/Carbon does not support any 64-bit architecture since Apple decided not to port its Carbon API entirely to 64-bit. -For further information, please see the files in docs/mac +@note Carbon has been deprecated by Apple as of OS X 10.5 and will likely +be removed entirely in a future OS version. It's recommended you look into +switching your app over to wxOSX/Cocoa as soon as possible. + +For further information, please see the files in @c docs/osx in the distribution. -@section page_port_wxcocoa wxCocoa +@subsection page_port_wxosx_cocoa wxOSX/Cocoa -@htmlonly - -@endhtmlonly - -wxCocoa is another port of wxWidgets for the Macintosh OS -platform. But in contrat to wxMac, it uses the Cocoa API. -Much work has gone into this port and many controls are -functional, but the port has not reached the maturity -of the wxMac port yet. It should be possible to use wxCocoa +wxOSX/Cocoa is another port of wxWidgets for the Macintosh OS +platform. In contrast to wxOSX/Carbon, it uses the Cocoa API +in place of Carbon. Much work has gone into this port and many +controls are functional, but the port has not reached the maturity +of the wxOSX/Carbon port yet. It is possible to use wxOSX/Cocoa on 64-bit architectures. +In order to configure wxWidgets to compile wxOSX/Cocoa you will +need to type: + +@verbatim configure --with-osx_cocoa @endverbatim + +For further information, please see the files in @c docs/osx +in the distribution. + +@note There was a previous effort towards a Cocoa port called +wxCocoa, which was implemented totally with Cocoa API unlike the OSX/Cocoa port +which uses OS X C APIs to share code, and while it is no longer being actively +developed, docs for it are available in @c docs/cocoa in the distribution. + + @section page_port_wxmgl wxMGL @@ -130,7 +143,7 @@ need to type: Under DOS, wxMGL uses a dmake based make system. -For further information, please see the files in docs/mgl +For further information, please see the files in @c docs/mgl in the distribution. @@ -140,12 +153,15 @@ in the distribution. wxOS2 is a port of wxWidgets for the IBM OS/2 Warp3 and Warp4 platforms. This port is currently under construction and in beta phase. +For further information, please see the files in @c docs/os2 +in the distribution. + @section page_port_wxx11 wxX11 @htmlonly - + @endhtmlonly wxX11 is a port of wxWidgets using X11 (The X Window System) @@ -160,28 +176,40 @@ need to type: @verbatim configure --with-x11 --with-universal @endverbatim -For further information, please see the files in docs/x11 +For further information, please see the files in @c docs/x11 in the distribution. There is also a page on the use of wxWidgets for embedded applications on the wxWidgets web site. +@section page_port_wxmotif wxMotif + +@htmlonly + +@endhtmlonly + +wxMotif is a port of wxWidgets for X11 systems using Motif libraries. +Motif libraries provide a clean and fast user interface at the expense +of the beauty and candy of newer interfaces like GTK. + +For further information, please see the files in @c docs/motif +in the distribution. + + @section page_port_wxmsw wxMSW @htmlonly - + @endhtmlonly -wxMSW is a port of wxWidgets for the Windows platforms -including Windows 95, 98, ME, 2000, NT, XP in ANSI and -Unicode mode (for Windows 95 through the MSLU extension -library). wxMSW ensures native look and feel for XP -as well when using wxWidgets version 2.3.3 or higher. -wxMSW can be compile with a great variety of compilers -including MS VC++, Borland 5.5, MinGW32, Cygwin and -Watcom as well as cross-compilation with a Linux hosted +wxMSW is a port of wxWidgets for the Windows platforms including Windows 95, +98, ME, 2000, NT, XP and Vista in ANSI and Unicode modes (for Windows 9x and +ME through the MSLU extension library). wxMSW ensures native look and feel for +XP when using wxWidgets version 2.3.3 or higher.wxMSW can be compiled with a +great variety of compilers including Microsoft Studio VC++, Borland 5.5, +MinGW32, Cygwin and Watcom as well as cross-compilation with a Linux-hosted MinGW32 tool chain. For further information, please see the files in docs/msw @@ -196,7 +224,7 @@ separate the client area's scrollbars from the border. If you don't specify a border style for a wxTextCtrl in rich edit mode, wxWidgets now gives the control themed borders automatically, where previously they would take the Windows 95-style -sunken border. Other native controls such as wxTextCtrl in non-rich edit mode, and wxComboBox, +sunken border. Other native controls such as wxTextCtrl in non-rich edit mode, and wxComboBox already paint themed borders where appropriate. To use themed borders on other windows, such as wxPanel, pass the @c wxBORDER_THEME style, or (apart from wxPanel) pass no border style. @@ -401,7 +429,7 @@ or with transparency (for example, using XPMs). @li Adding controls to wxToolMenuBar is not supported. However, wxToolBar supports controls. -Unlike in all other ports, a wxDialog has a wxToolBar, automatically created +Unlike in all other ports, a wxDialog has a wxToolBar automatically created for you. You may either leave it blank, or access it with wxDialog::GetToolBar() and add buttons, then calling wxToolBar::Realize(). You cannot set or recreate the toolbar. @@ -548,7 +576,7 @@ Also change the Linker/Input/Additional Dependencies property to something like commctrl.lib winsock.lib wininet.lib (since the library names in the wxWidgets workspace were changed by VS 2005). -Alternately, you could could edit all the names to be identical to the original eVC++ +Alternately, you could edit all the names to be identical to the original eVC++ names, but this will probably be more fiddly. @subsubsection page_port_wxmsw_wince_issues Remaining issues @@ -616,9 +644,14 @@ used by wxWidgets to e.g. use toolkit-specific features. In such case (or when you want to e.g. write a port-specific patch) it can be necessary to use the underlying toolkit API directly: -@li wxMSW port uses win32 API: see MSDN docs at http://msdn2.microsoft.com/en-us/library/ms649779.aspx -@li wxGTK port uses GTK+: see GTK+ 2.x docs at http://developer.gnome.org/doc/API/2.0/gtk/index.html -@li wxMac port uses the Carbon API: see Carbon docs at http://developer.apple.com/carbon -@li wxCocoa port uses the Cocoa API: see Cocoa docs at http://developer.apple.com/carbon +- wxMSW port uses win32 API: see MSDN docs at http://msdn2.microsoft.com/en-us/library/ms649779.aspx +- wxGTK port uses GTK+ and other lower-level libraries; see + - GTK+ docs at http://library.gnome.org/devel/gtk/unstable/ + - GDK docs at http://library.gnome.org/devel/gdk/unstable/ + - GLib docs at http://library.gnome.org/devel/glib/unstable/ + - GObject docs at http://library.gnome.org/devel/gobject/unstable/ + - Pango docs at http://library.gnome.org/devel/pango/unstable/ +- wxMac port uses the Carbon API: see Carbon docs at http://developer.apple.com/carbon +- wxCocoa port uses the Cocoa API: see Cocoa docs at http://developer.apple.com/cocoa */