Amebis/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Applied documentation typo/grammer corrections from charles (#10439).

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@58467 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Bryan Petty
2009-01-27 19:46:05 +00:00
parent 797c0bde0d
commit 7ecc54dfac
1 changed files with 13 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
docs/doxygen/mainpages/platdetails.h
View File

@@ -54,10 +54,10 @@ You will need GTK+ 2.6 or higher which is available from:
http://www.gtk.org http://www.gtk.org
The newer version of GTK+ you use, the more native widgets and The newer version of GTK+ you use, the more native widgets and
features will be utilized. We have gone to a great extent to features will be utilized. We have gone to great lengths to
allow compiling wxWidgets applications with a latest version of allow compiling wxWidgets applications with the latest version of
GTK+, with the resulting binary working on systems even with a 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. application is launched with lazy symbol binding for that.
In order to configure wxWidgets to compile wxGTK you will In order to configure wxWidgets to compile wxGTK you will
@@ -103,7 +103,7 @@ in the distribution.
@endhtmlonly @endhtmlonly
wxCocoa is another port of wxWidgets for the Macintosh OS wxCocoa is another port of wxWidgets for the Macintosh OS
platform. But in contrast to wxMac, it uses the Cocoa API. platform. In contrast to wxMac, it uses the Cocoa API.
Much work has gone into this port and many controls are Much work has gone into this port and many controls are
functional, but the port has not reached the maturity functional, but the port has not reached the maturity
of the wxMac port yet. It should be possible to use wxCocoa of the wxMac port yet. It should be possible to use wxCocoa
@@ -195,14 +195,12 @@ in the distribution.
<img src="logo_win.png" alt="Windows logo" title="Windows logo" class="logo"> <img src="logo_win.png" alt="Windows logo" title="Windows logo" class="logo">
@endhtmlonly @endhtmlonly
wxMSW is a port of wxWidgets for the Windows platforms wxMSW is a port of wxWidgets for the Windows platforms including Windows 95,
including Windows 95, 98, ME, 2000, NT, XP in ANSI and 98, ME, 2000, NT, XP and Vista in ANSI and Unicode modes (for Windows 9x and
Unicode mode (for Windows 95 through the MSLU extension ME through the MSLU extension library). wxMSW ensures native look and feel for
library). wxMSW ensures native look and feel for XP XP when using wxWidgets version 2.3.3 or higher.wxMSW can be compiled with a
as well when using wxWidgets version 2.3.3 or higher. great variety of compilers including Microsoft Studio VC++, Borland 5.5,
wxMSW can be compile with a great variety of compilers MinGW32, Cygwin and Watcom as well as cross-compilation with a Linux-hosted
including MS VC++, Borland 5.5, MinGW32, Cygwin and
Watcom as well as cross-compilation with a Linux hosted
MinGW32 tool chain. MinGW32 tool chain.
For further information, please see the files in docs/msw For further information, please see the files in docs/msw
@@ -217,7 +215,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 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 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 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. as wxPanel, pass the @c wxBORDER_THEME style, or (apart from wxPanel) pass no border style.
@@ -422,7 +420,7 @@ or with transparency (for example, using XPMs).
@li Adding controls to wxToolMenuBar is not supported. However, wxToolBar supports @li Adding controls to wxToolMenuBar is not supported. However, wxToolBar supports
controls. 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() 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 and add buttons, then calling wxToolBar::Realize(). You cannot set or recreate
the toolbar. the toolbar.
@@ -569,7 +567,7 @@ Also change the Linker/Input/Additional Dependencies property to something like
commctrl.lib winsock.lib wininet.lib</tt> commctrl.lib winsock.lib wininet.lib</tt>
(since the library names in the wxWidgets workspace were changed by VS 2005). (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. names, but this will probably be more fiddly.
@subsubsection page_port_wxmsw_wince_issues Remaining issues @subsubsection page_port_wxmsw_wince_issues Remaining issues