AuroraMiddleware/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Doc updates

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@33695 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Julian Smart 2005-04-17 10:34:19 +00:00
parent 23eaaaaf5f
commit 5147354ced
8 changed files with 166 additions and 112 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
docs/html/faqgen.htm
View File

@ -1,4 +1,3 @@
<HTML>
<HEAD>
@ -54,7 +53,7 @@ so your program will take on the native &#39;look and feel&#39; that users are f
Although GUI applications are mostly built programmatically, there are several dialog editors to help
build attractive dialogs and panels. Robert Roebling&#39;s <a href="http://www.roebling.com">wxDesigner</a>
and Anthemion Software's <a href="http://www.anthemion.co.uk/dialogblocks/" target=_new>DialogBlocks</a>
and Anthemion Software&#39;s <a href="http://www.anthemion.co.uk/dialogblocks/" target=_new>DialogBlocks</a>
are two commercial examples, but there are others: see the <a href="lnk_tool.htm">Useful Tools</a> page.<P>
You don&#39;t have to use C++ to use wxWidgets: there is a <a href="http://wxpython.org">Python interface</a> for wxWidgets 2,
@ -277,29 +276,29 @@ from Java, and the level of interest in wxWidgets is as high as ever.<P>
Microsoft is spending a lot on promoting the .NET initiative, which
is a set of languages, APIs and web service components for Windows.
Ximian has started an open source version of .NET, mostly for Linux.
C&#35; is Microsoft's alternative to Java, supporting 'managed code',
C&#35; is Microsoft&#39;s alternative to Java, supporting &#39;managed code&#39;,
garbage collection and various other Java-like language features.<P>
Although this may be attractive to some developers, there
is a variety of reasons why the .NET/Mono combination is unlikely
to make wxWidgets redundant. Please note that the following comments
are Julian Smart's opinions.<P>
are Julian Smart&#39;s opinions.<P>
<ol>
<li>Not everyone wants or needs net services.
<li>C++ will be used for a long time to come; compared with C++, C&#35; is a recent development and its future is not certain.
<li>Mono Forms may only target Winelib (at least to begin with), so the end result is not as native as
wxWidgets (I'm aware there is GTK&#35; for use with the C&#35; language).
wxWidgets (I&#39;m aware there is GTK&#35; for use with the C&#35; language).
<li>C&#35; is usually byte-compiled and therefore slower. Plus, .NET adds a layer of overhead to the client computer
that wxWidgets does not require.
<li>Mono hasn't proven its long-term viability yet (it's a complex system of components); wxWidgets is ready now.
<li>Mono hasn&#39;t proven its long-term viability yet (it&#39;s a complex system of components); wxWidgets is ready now.
<li>You may not wish to buy into Microsoft marketing spin and APIs.
<li>Microsoft may at some point sue developers of non-Microsoft .NET implementations. After all,
platform-independence is not in Microsoft's interest.
platform-independence is not in Microsoft&#39;s interest.
<li>.NET might never be implemented on some platforms, especially Mac and embedded variants of Linux.
<li>wxPython and other language variants provide further reasons for wxWidgets to continue.
<li>The same issue exists for Qt: if Qt sales remain strong, it's a good indication that
the market for a C++-based approach is still there. (Either that, or everyone's turning to wxWidgets!)
<li>The same issue exists for Qt: if Qt sales remain strong, it&#39;s a good indication that
the market for a C++-based approach is still there. (Either that, or everyone&#39;s turning to wxWidgets!)
</ol>
There is nothing to stop folk from developing a C&#35; version of the wxWidgets API;
@ -322,7 +321,7 @@ has specific suggestions. Also please read the <a href="standard.htm">coding sta
<P>
Each port consists of a platform-specific part (e.g. src/msw, include/wx/msw),
a generic set of widgets and dialogs for when the port doesn't support
a generic set of widgets and dialogs for when the port doesn&#39;t support
them natively (src/generic, include/wx/generic) and the common code
that all ports use (src/common, include/wx). By browsing the source
you should get a good idea of the general pattern.<P>
@ -335,7 +334,7 @@ Perhaps it will still save you time to clean up wxStubs, and
others may benefit from this too.<P>
You will need to define a symbol for the new port, e.g. __WXXBOX__.
Look at files such as wx/defs.h, wx/wxchar.h for areas where you'll
Look at files such as wx/defs.h, wx/wxchar.h for areas where you&#39;ll
need to add to existing conditionals to set up wide character
support and other issues. If the GUI runs on a Unix variant,
define the __UNIX__ variable in your makefile.<P>
@ -357,7 +356,7 @@ wxMGL, and wxMSW/Univ for sample wxUniversal ports.<P>
To begin with, you can use whatever makefiles or project
files work for you. Look at existing makefiles to see what
generic/common/Unix files need to be included. Later, you'll want to integrate support
generic/common/Unix files need to be included. Later, you&#39;ll want to integrate support
for your port into configure (Unix-like systems and gcc under Windows),
and bakefile (for other makefiles on Windows).<P>

7
docs/html/faqgtk.htm
View File

@ -1,4 +1,3 @@
<HTML>
<HEAD>
@ -21,7 +20,7 @@
<P>
See also <a href="faq.htm">top-level FAQ page</a>
See also <a href="faq.htm">top-level FAQ page</a>
and <a href="faqunx.htm">Unix FAQ page</a>.
<hr>
<h3>List of questions in this category</h3>
@ -86,13 +85,13 @@ This problem can be solved by updating GTK with an official distribution of the
Robert Roebling replies:<P>
"The important thing is the libc version that your app
&#34;The important thing is the libc version that your app
is linked against. The most recent version is 2.2.5
and programs linked against it will not run with version
2.1.X so that you will fare best if you compile your app
on a 2.1.X system. It will then run on practically all
Linux distros (if you link you app statically against
the image libraries and std C++ lib)."
the image libraries and std C++ lib).&#34;
<P>
<h3><a name="#static">Can I statically link the GTK+ library?</a></h3>

23
docs/html/faqmsw.htm
View File

@ -1,4 +1,3 @@
<HTML>
<HEAD>
@ -45,9 +44,9 @@ See also <a href="faq.htm">top-level FAQ page</a>.
<li><a href="#shortcutproblem">Why are menu hotkeys or shortcuts not working in my application?</a></li>
<li><a href="#regconfig">Why can I not write to the HKLM part of the registry with wxRegConfig?</a></li>
<li><a href="#access">Is MS Active Accessibility supported?</a></li>
<li><a href="#dspfmt">Why does Visual C++ complain about corrupted project files{/a></li>
<li><a href="#dspfmt">Why does Visual C++ complain about corrupted project files?</a></li>
<li><a href="#crtmismatch">Visual C++ gives errors about multiply defined symbols, what can I do?</a></li>
<li><a href="#directx">Why do I get compilation erros when using wxWidgets with DirectShow?</a></li>
<li><a href="#directx">Why do I get compilation errors when using wxWidgets with DirectShow?</a></li>
<li><a href="#handlewm">How do I handle Windows messages in my wxWidgets program?</a></li>
</ul>
<hr>
@ -342,7 +341,7 @@ example) and regenerate the makefile using tmake.<P>
tmake can be found at
<a href="http://www.troll.no/freebies/tmake.html" target=_new>www.troll.no/freebies/tmake.html</a>.
It&#39;s a Perl5 program and so it needs Perl (doh). There is a binary for
It&#39;s a Perl5 program and so it needs Perl (doh). There is a binary for
Windows (available from the same page), but I haven&#39;t used it, so
I don&#39;t know if it works as flawlessly as "perl tmake" does (note
for people knowing Perl: don&#39;t try to run tmake with -w, it won&#39;t
@ -351,7 +350,7 @@ just go to distrib/msw/tmake and type<P>
<pre>tmake -t b32 wxwin.pro -o ../../src/msw/makefile.b32</pre><P>
The makefiles are untested - I don&#39;t have any of Borland, Watcom or
The makefiles are untested - I don&#39;t have any of Borland, Watcom or
Symantec and I don&#39;t have enough diskspace to recompile even with
VC6 using makefiles. The new makefiles are as close as possible to the
old ones, but not closer: in fact, there has been many strange things
@ -458,7 +457,7 @@ First, you can use wxRegKey directly, for example:
regKey.SetName(idName);
{
wxLogNull dummy;
wxLogNull dummy;
if (!regKey.Create())
{
idName = wxT("HKEY_CURRENT_USER\\SOFTWARE\\My Company\\My Product\\Stuff\\");
@ -504,7 +503,7 @@ for the current status.
<P>
<h3><a name="#dspfmt">Why does Visual C++ complain about corrupted project files{/a></h3>
<h3><a name="#dspfmt">Why does Visual C++ complain about corrupted project files?</a></h3>
If you have downloaded the wxWidgets sources from the cvs using a Unix cvs
client or downloaded a daily snapshot in <tt>.tar.gz</tt> format, it is likely
@ -543,11 +542,11 @@ slightly smaller and faster.
But the most important thing is to use the <strong>same</strong> CRT setting for
all components of your project.
<h3><a name="#directx">Why do I get compilation errors when using wxWidgets with DirectShow?</a></h3>
<h3><a name="#directx">Why do I get compilation erros when using wxWidgets with DirectShow?</a></h3>
If you get errors when including Microsoft DirectShow or DirectDraw headers,
the following message from Peter Whaite could help:
<blockquote><pre>
<blockquote>
&gt; This causes compilation errors within DirectShow:
&gt;
&gt; wxutil.h(125) : error C2065: &#39;EXECUTE_ASSERT&#39; : undeclared identifier
@ -555,11 +554,11 @@ the following message from Peter Whaite could help:
The reason for this is that __WXDEBUG__ is also used by the DXSDK (9.0
in my case) to &#39;#pragma once&#39; the contents of
DXSDK/Samples/C++/DirectShow/BaseClasses/wxdebug.h. So if __WXDEBUG__
DXSDK/Samples/C++/DirectShow/BaseClasses/wxdebug.h. So if __WXDEBUG__
is defined, then wxdebug.h doesn&#39;t get included, and the assert macros
don&#39;t get defined. You have to #undef __WXDEBUG__ before including the
don&#39;t get defined. You have to #undef __WXDEBUG__ before including the
directshow baseclass&#39;s &lt;streams.h&gt;.
</pre></blockquote>
</blockquote>
<h3><a name="#handlewm">How do I handle Windows messages in my wxWidgets program?</a></h3>

89
docs/html/index.htm
View File

@ -13,11 +13,11 @@
<IMG src="logo.gif" align=right hspace=10 vspace=0>
<b>Welcome to wxWidgets 2, the premi&egrave;re cross-platform GUI C++ framework.</b><P>
<b>Welcome to wxWidgets, the premi&egrave;re cross-platform GUI C++ framework.</b><P>
This is an index of
the plain text, HTML, Windows Help and Acrobat documentation: availability depends on what you've
downloaded from the <a href="http://www.wxwindows.org">wxWidgets Web site</a>.<br clear=all><P>
downloaded from the <a href="http://www.wxwidgets.org">wxWidgets Web site</a>.<br clear=all><P>
<CENTER>
<FONT size=-1>
@ -25,6 +25,7 @@ downloaded from the <a href="http://www.wxwindows.org">wxWidgets Web site</a>.<b
[<a href="#manuals">Manuals</a>]
[<a href="#technotes">Technical Notes</a>]
[<a href="#thirdparty">3rd party tools</a>]
[<a href="#contribs">Optional Libraries</a>]
[<a href="#samples">Samples</a>]
[<a href="#demos">Demos</a>]
</FONT>
@ -53,22 +54,24 @@ for how to do this.
<ul>
<li>ReadMe: <a href="../readme.txt"><b>General ReadMe</b></a>,
<a href="../msw/readme.txt">wxMSW</a>,
<a href="../gtk/readme.txt">wxGTK</a>,
<a href="../mac/readme.txt">wxMac</a>,
<a href="../cocoa/readme.txt">wxCocoa</a>,
<a href="../mgl/readme.txt">wxMGL</a>,
<a href="../motif/readme.txt">wxMotif</a>,
<a href="../x11/readme.txt">wxX11</a>,
<a href="../x11/readme-nanox.txt">wxNanoX</a>,
<a href="../msw/readme.txt">wxMSW</a>,
<a href="../mac/readme.txt">wxMac</a>,
<a href="../mgl/readme.txt">wxMGL</a>,
<a href="../univ/readme.txt">Univ</a>
<li>Installation: <a href="../gtk/install.txt">wxGTK</a>,
<li>Installation:
<a href="../msw/install.txt">wxMSW</a>,
<a href="../gtk/install.txt">wxGTK</a>,
<a href="../motif/install.txt">wxMotif</a>,
<a href="../x11/install.txt">wxX11</a>,
<a href="../msw/install.txt">wxMSW</a>,
<a href="../mac/install.txt">wxMac</a>,
<a href="../cocoa/install.txt">wxCocoa</a>,
<a href="../mgl/install.txt">wxMGL</a>,
<a href="../os2/install.txt">wxOS2</a>
<li><a href="../changes.txt"><b>General change log</b></a>, <a href="../gtk/changes.txt">wxGTK change log</a>
<li><a href="../changes.txt"><b>General change log</b></a>
<li>Licence: <a href="../preamble.txt">Preamble</a>,
<a href="../licence.txt">Licence</a>,
<a href="../licendoc.txt">Documentation Licence</a>,
@ -77,18 +80,18 @@ for how to do this.
<li><a href="faq.htm"><B>FAQ</B></a>:
<ul>
<li><a href="faqgen.htm">General questions</a>
<li><a href="faqgtk.htm">wxWidgets 2 for GTK+</a>
<li><a href="faqmsw.htm">wxWidgets 2 for Windows</a>
<li><a href="faqmot.htm">wxWidgets 2 for Motif</a>
<li><a href="faqx11.htm">wxWidgets 2 for X11</a>
<li><a href="faqmac.htm">wxWidgets 2 for Mac</a>
<li><a href="faqcmn.htm">Questions common to all platforms</a>
<li><a href="faqmsw.htm">wxWidgets for Windows</a>
<li><a href="faqgtk.htm">wxWidgets for GTK+</a>
<li><a href="faqmot.htm">wxWidgets for Motif</a>
<li><a href="faqx11.htm">wxWidgets for X11</a>
<li><a href="faqunx.htm">wxWidgets for Unix</a>
<li><a href="faqmac.htm">wxWidgets for Mac</a>
</ul>
<li>ToDo: <a href="../todo.txt"><b>General ToDo</b></a>,
<a href="../gtk/todo.txt">wxGTK</a>,
<a href="../motif/todo.txt">wxMotif</a>,
<a href="../msw/todo.txt">wxMSW</a>,
<a href="../mac/todo.txt">wxMac</a>
<li>List of <a href="../symbols.txt">preprocessor symbols</a> used in wxWidgets
</ul>
Further platform-specific notes:
@ -115,11 +118,6 @@ To use manuals in wxHTML Help form (extension htb), you can use the <b>HelpView<
application, either compiling it from utils/helpview in the distribution,
or downloading a binary, for example from <a href="http://www.storylinescentral.com/helpview.htm">here</a>.<P>
See also the <a href="../pdf/wxTutorial.pdf">wxWidgets Tutorial</a>
by Franky Braem, in PDF format.<P>
<P>
<table border=0 cellpadding=5 cellspacing=0>
<tr>
@ -273,6 +271,37 @@ by Franky Braem, in PDF format.<P>
<P>
<table width=100% border=0 cellpadding=3 cellspacing=0>
<tr>
<td bgcolor="#004080" align=left height=24 background="images/bluetitlegradient.gif">
<font size=+1 face="Arial, Lucida Sans, Helvetica" color="#FFFFFF">
<b><a name="contribs">Optional Libraries</a></b>
</font>
</td>
</tr>
</table>
<P>
These are the optional libraries in the <a href="../../contrib">contrib</a> hierarchy.<P>
<ul>
<li><a href="../../contrib/src/animate">animate</a>: a flip-book animation class, with animated GIF player.
<li><a href="../../contrib/src/deprecated">deprecated</a>: deprecated classes including the old WXR resource system and property sheet classes.
<li><a href="../../contrib/src/fl">fl</a>: a frame layout/docking library.
<li><a href="../../contrib/src/foldbar">foldbar</a>: wxFoldPanel class for economical layout of controls.
<li><a href="../../contrib/src/gizmos">gizmos</a>: a variety of GUI classes including wxDynamicSashWindow, wxLEDNumberCtrl, wxEditableListBox, wxStaticPicture
and a split tree/content view.
<li><a href="../../contrib/src/mmedia">mmedia</a>: deprecated library for playing audio and video.
<li><a href="../../contrib/src/net">net</a>: wxEmail class.
<li><a href="../../contrib/src/ogl">ogl</a>: Object Graphics Library (for drawing connected shapes).
<li><a href="../../contrib/src/plot">plot</a>: simple plotting class.
<li><a href="../../contrib/src/stc">stc</a>: wxStyledTextControl, a wrapper for the Scintilla code editor control.
<li><a href="../../contrib/src/svg">svg</a>: wxSVGFileDC class for drawing vector graphics into a SVG file.
</ul>
<P>
<table width=100% border=0 cellpadding=3 cellspacing=0>
<tr>
<td bgcolor="#004080" align=left height=24 background="images/bluetitlegradient.gif">
@ -288,6 +317,7 @@ by Franky Braem, in PDF format.<P>
Each of the following samples demonstrates one or more aspect of wxWidgets.<P>
<ul>
<li><a href="../../samples/access">access</a>: Active Accessiblity sample (Windows only).
<li><a href="../../samples/artprov">artprov</a>: shows how you can customize the look of standard
wxWidgets dialogs by replacing default bitmaps/icons with your own versions.
<li><a href="../../samples/calendar">calendar</a>: a sample to test the wxCalendarCtrl class.
@ -300,11 +330,13 @@ defaults to wxRegConfig on WIN32 (optionally wxIniConfig), and wxFileConfig on o
console-mode (no-GUI) compilation of wxWidgets.
<li><a href="../../samples/controls">controls</a>: sample showing a variety of controls, including
wxNotebook.
<li><a href="../../samples/db">db</a>: wxDB ODBC sample.
<li><a href="../../samples/db">db</a>: wxODBC sample.
<li><a href="../../samples/debugrpt">debugrpt</a>: wxDebugReport sample.
<li><a href="../../samples/dialogs">dialogs</a>: shows some of the common dialogs available -- wxFontDialog,
wxColourDialog, wxFileDialog, wxDirDialog, wxMessageBox, wxTextEntryDialog, wxSingleChoiceDialog.
For printing-related dialogs, see the printing sample.
<li><a href="../../samples/dialup">dialup</a>: wxDialUpManager demo.
<li><a href="../../samples/display">display</a>: wxDisplay demo.
<li><a href="../../samples/dnd">dnd</a>: demonstrates drag and drop on supported platforms.
<li><a href="../../samples/docview">docview</a>: demonstrates use of the document view classes,
using wxFrame.
@ -314,7 +346,9 @@ using wxMDIParentFrame, wxMDIChildFrame.
<li><a href="../../samples/drawing">drawing</a>: tests device context drawing.
<li><a href="../../samples/dynamic">dynamic</a>: shows how to connect events to member functions
dynamically.
<li><a href="../../samples/erase">erase</a>: Window erasing sample.
<li><a href="../../samples/event">event</a>: demonstrates event handling.
<li><a href="../../samples/except">exept</a>: demonstrates exception handling.
<li><a href="../../samples/exec">exec</a>: demonstrates wxExecute.
<li><a href="../../samples/font">font</a>: tests fonts, font enumerator, font encodings.
<li><a href="../../samples/grid">grid</a>: demonstrates the wxGrid class.
@ -331,6 +365,7 @@ applications and also as a help facility.
<li><a href="../../samples/html/widget">widget</a>: demonstrates the use of controls in HTML pages.
<li><a href="../../samples/html/zip">zip</a>: shows how help files can be packaged in zip archives.
</ul>
<li><a href="../../samples/htlbox">htlbox</a>: demonstrates wxHtmlListBox.
<li><a href="../../samples/image">image</a>: shows off the cross-platform wxImage class.
<li><a href="../../samples/ipc">ipc</a>: shows the DDE-like protocol in action, both using real
DDE on Windows, and TCP/IP on all platforms. Edit <a href="../../samples/ipc/ddesetup.h">ddesetup.h</a>
@ -342,6 +377,7 @@ to switch between compilation modes.
<li><a href="../../samples/listctrl">listctrl</a>: demonstrates the wxListCtrl (implemented natively on
WIN32, and using a generic version on other platforms).
<li><a href="../../samples/menu">menu</a>: tests menus.
<li><a href="../../samples/mediaplayer">mediaplayer</a>: demonstrates wxMediaCtrl, for playing movies and audio files in a window.
<li><a href="../../samples/mdi">mdi</a>: shows off the MDI (Multiple Document Interface) classes. On Windows, the regular MDI
scheme is used whereby child windows have full sizing and moving rights within the main
window. On other platforms, tabbed windows are used, where the children are always maximized.
@ -353,6 +389,7 @@ platforms that don't support it, a normal-sized title bar is displayed.
<li><a href="../../samples/minimal">minimal</a>: just shows a frame, a menubar, and a statusbar. About as
small a wxWidgets application as you can get.
<li><a href="../../samples/mobile">mobile</a>: mini applications for embedded platforms.
<li><a href="../../samples/multimon">multimon</a>: demo showing how to use multiple monitors.
<li><a href="../../samples/nativdlg">nativdlg</a>: shows how wxWidgets can load a standard Windows
dialog resource, translating the controls into wxWidgets controls (Windows only).
<li><a href="../../samples/notebook">notebook</a>: shows the wxNotebook (tabbed window) control.
@ -363,9 +400,10 @@ Excel to be present).
<li><a href="../../samples/printing">printing</a>: shows printing and previewing.
<li><a href="../../samples/propsize">propsize</a>: demonstrates proportional sizer classes.
<li><a href="../../samples/regtest">regtest</a>: tests the low-level Windows registry functions (Windows only).
<!-- <li><a href="../../samples/richedit">richedit</a>: a work-in-progress rich text editor with plain text and HTML export
<li><a href="../../samples/render">render</a>: shows how to use wxRenderer to implement controls consistent with the
platform's native look.
<li><a href="../../samples/richedit">richedit</a>: a work-in-progress rich text editor with plain text and HTML export
facilities.
-->
<li><a href="../../samples/rotate">rotate</a>: demonstrates interpolated and non-interpolated
rotation of a wxImage.
<li><a href="../../samples/sashtest">sashtest</a>: demonstrates use of the wxSashWindow class to allow
@ -373,7 +411,9 @@ the user to resize subwindows.
<li><a href="../../samples/scroll">scroll</a>: demonstrates wxScrolledWindow.
<li><a href="../../samples/scrollsub">scrollsub</a>: demonstrates the use of wxScrolledWindow to scroll
an embedded window.
<li><a href="../../samples/shaped">shaped</a>: demonstrates non-rectangular windows using wxFrame::SetShape.
<li><a href="../../samples/sockets">sockets</a>: demonstrates the TCP/IP family of classes.
<li><a href="../../samples/sound">sound</a>: demonstrates use of wxSound.
<li><a href="../../samples/splash">splash</a>: demonstrates use of the wxSplashScreen class.
<li><a href="../../samples/splitter">splitter</a>: demonstrates the wxSplitterWindow class.
<li><a href="../../samples/statbar">statbar</a>: demonstrates the wxStatusBar class.
@ -389,6 +429,7 @@ programming.
<li><a href="../../samples/typetest">typetest</a>: tests various data type classes, including
wxTime, wxDate and wxVariant.
<li><a href="../../samples/validate">validate</a>: shows simple use of validation.
<li><a href="../../samples/vscroll">vscroll</a>: shows use of wxVScrolledWindow.
<li><a href="../../samples/wizard">wizard</a>: demonstrates the wxWizard class.
<li><a href="../../samples/xrc">xrc</a>: demonstrates the XRC resource system.
</ul>

15
docs/html/platform.htm
View File

@ -1,3 +1,4 @@
<html>
<head>
<title>Platforms supported by wxWindows 2.4</title>
@ -133,10 +134,18 @@ often don&#39;t work.
</tr>
<tr bgcolor="#f0f0f0">
<td align=center valign=center rowspan=2>HP-UX 10.20</td>
<td>wxGTK with HP CC A.10.22<br>or HP aCC B3910B A.01.18</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td>Staf Verhaegen</td>
<td align=center valign=center rowspan=5>HP-UX</td>
<tr bgcolor="#f0f0f0">
<td>HP-UX 10.20 wxGTK with HP CC A.10.22<br>or HP aCC B3910B A.01.18</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td>Staf Verhaegen</td>
<td>you need to add <tt>-Aa -D_HPUX_SOURCE</tt> to <tt>CFLAGS</tt></td>
<tr bgcolor="#f0f0f0"> <td>wxGTK with gcc</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td>Julian Albo Garcia</td><td><br></td>
<tr bgcolor="#f0f0f0"> <td>HP-UX 10.20 wxGTK with gcc</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td>Julian Albo Garcia</td><td><br></td>
<tr bgcolor="#f0f0f0"> <td>HP-UX 11i v1 PA-RISC, wxMotif 2.5.4, tried aCC A.03.57 and g++ 3.4.2</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td>Ian, Mike</td>
<td>For a 32-bit PA-RISC build, if you want to use <tt>SHLIB_PATH</tt> to make it easier to use
wxWidgets without installing it, then add <tt>LDFLAGS=-Wl,+s</tt><br>
If you want to compile the test suite then aCC A.03.57 requires <tt>CXX='aCC -AA'</tt><br>
aCC can also be used as the C compiler instead of cc by adding <tt>CC='aCC -Ae'</tt>
</td>
<tr bgcolor="#f0f0f0"> <td>HP-UX 11i v2 IA64, wxMotif 2.5.4, aCC A.06.00</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td>Mike</td><td><br></td>
</tr>
<tr>

48
docs/msw/install.txt
View File

@ -1,8 +1,11 @@
Installing wxWidgets 2.6.0
--------------------------
-----------------------------------------------------------
This is wxWidgets 2.6.0 for Microsoft Windows 9x/ME, Windows NT, Windows 2000
and Windows XP.
This is wxWidgets 2.6.0 for Microsoft Windows 9x/ME, Windows NT,
Windows 2000, Windows XP and Windows CE.
These installation notes can be found in docs/msw/install.txt
in your wxWidgets distribution.
IMPORTANT NOTE: If you experience problems installing, please
re-read this instructions and other related files (changes.txt,
@ -17,7 +20,7 @@ Please report bugs using the SourceForge bug tracker:
http://sourceforge.net/bugs/?group_id=9863
Unarchiving
===========
============================================================
A setup program is provided (setup.exe) to automatically copy
files to a directory on your hard disk. Do not install into a
@ -105,7 +108,7 @@ Below are compiler specific notes followed by customizing instructions that
apply to all compilers (search for "Configuring the build").
Microsoft Visual C++ compilation
--------------------------------
----------------------------------------------------------------
You may wish to visit http://wiki.wxwindows.org/wiki.pl?MSVC for a more
informal and more detailed description of the process summarized below.
@ -184,7 +187,7 @@ files from an existing wxWidgets sample and adapt them, or
visit http://wiki.wxwindows.org/wiki.pl?MSVC.
Borland C++ 5.0/5.5 compilation
-------------------------------
----------------------------------------------------------------
Compiling using the makefiles (updated 24 Sept 02):
@ -228,13 +231,13 @@ the following preprocessor directive:
more details)
Borland 16 Bit compilation for Windows 3.1
------------------------------------------
----------------------------------------------------------------
The last version of wxWidgets to support 16-bit compilation with Borland was
2.2.7 - Please download and read the instructions in that release
Watcom C++ 10.6/11 and OpenWatcom compilation
---------------------------------------------
----------------------------------------------------------------
1. Change directory to build\msw. Type 'wmake -f makefile.wat' to
make the wxWidgets core library.
@ -258,9 +261,9 @@ Note (4): if Watcom can't read the precompiled header when building a sample,
the sample again.
Metrowerks CodeWarrior compilation
----------------------------------
----------------------------------------------------------------
1. CodeWarrior Pro7 project files in XML format are already
1. CodeWarrior Pro 7 project files in XML format are already
included in wxMSW-2.6.0.zip and the setup version.
2. Review the file include\wx\msw\setup.h (or include\wx\msw\setup0.h if
@ -322,7 +325,7 @@ Metrowerks CodeWarrior compilation
Cygwin/MinGW compilation
------------------------
----------------------------------------------------------------
wxWidgets supports Cygwin (formerly GnuWin32) betas and
releases, and MinGW. Cygwin can be downloaded from:
@ -351,7 +354,7 @@ If using MinGW, you can download the add-on MSYS package to
provide Unix-like tools that you'll need to build wxWidgets using configure.
Using makefiles directly
------------------------
----------------------------------------------------------------
NOTE: The makefile.gcc makefiles are for compilation under MinGW using
native make and Windows command interpreter (command.com/cmd.exe), they
@ -383,7 +386,7 @@ All targets have 'clean' targets to allow removal of object files
and other intermediate compiler files.
Using configure
---------------
----------------------------------------------------------------
Instead of using the makefiles, you can use the configure
system to generate appropriate makefiles, as used on Unix
@ -477,7 +480,8 @@ OLD VERSIONS:
Symantec & DigitalMars C++ compilation
--------------------------------------
----------------------------------------------------------------
The DigitalMars compiler is a free succssor to the Symantec compiler
and can be downloaded from http://www.digitalmars.com/
@ -505,7 +509,7 @@ using bakefile tool according to the instructions in build\bakefiles\README:
16-bit compilation is no longer supported.
Configuring the build
=====================
================================================================
So far the instructions only explained how to build release DLLs of wxWidgets
and did not cover any configuration. It is possible to change many aspects of
@ -515,7 +519,7 @@ and the only difference between them is in object files and library directory
names and in make invocation command.
Changing the settings
---------------------
----------------------------------------------------------------
There are two ways to modify the settings: either by passing the values as
arguments when invoking make or by editing build\msw\config.$(compiler) file
@ -553,7 +557,7 @@ Brief explanation of options and possible values is in every
build\msw\config.* file; more detailed description follows.
Basic options
-------------
----------------------------------------------------------------
BUILD=release
Builds release version of the library. It differs from default 'debug'
@ -578,7 +582,7 @@ WXUNIV=1
http://www.wxwidgets.org/wxuniv.htm for more information).
Advanced options
----------------
----------------------------------------------------------------
MONOLITHIC=1
Starting with version 2.5.1, wxWidgets has the ability to be built as
@ -656,7 +660,7 @@ CFG=<configuration name>
directories" below for more information.
Compiler specific options
-------------------------
----------------------------------------------------------------
* MinGW
@ -678,7 +682,7 @@ DEBUG_RUNTIME_LIBS=1
setting makes it possible.
Fine-tuning the compiler
------------------------
----------------------------------------------------------------
All makefiles have variables that you can use to specify additional options
passed to the compiler or linker. You won't need this in most cases, but if you
@ -686,7 +690,7 @@ do, simply add desired flags to CFLAGS (for C compiler), CXXFLAGS (for C++
compiler), CPPFLAGS (for both C and C++ compiler) and LDFLAGS (the linker).
Object and library directories
------------------------------
----------------------------------------------------------------
All object files produced during library build are stored in a directory under
build\msw. It's name is derived from build settings and CFG variable and from
@ -736,7 +740,7 @@ enabled (without CFG, both of them would be put into same directory and there
would be conflicts between the files).
General Notes
=============
=================================================================
- Debugging: under Windows 95, debugging output isn't output in
the same way that it is under NT or Windows 3.1.

66
docs/readme.txt
View File

@ -1,9 +1,9 @@
wxWidgets 2.6.0
---------------
---------------------------------------------------------
Welcome to wxWidgets, a sophisticated cross-platform C++
framework for writing advanced GUI applications using (where
possible) the native controls.
framework for writing advanced GUI applications using
native controls where possible.
In addition to common and advanced GUI facilities such as
frames, scrolling windows, toolbars, tree controls, icons,
@ -22,20 +22,23 @@ for a list of important documents and samples.
Changes in this release
-----------------------
Please see changes.txt for details.
Please see changes.txt and "Changes since 2.4" in the manual
for details.
Platforms supported
-------------------
wxWidgets currently supports the following platforms:
- Windows 95/98/ME, Windows NT, Windows 2000, Windows XP, Pocket PC
- Windows 95/98/ME, Windows NT, Windows 2000, Windows XP,
Pocket PC, Smartphone
- Most Unix variants with GTK+ 1 and GTK+ 2
- Most Unix variants with X11 (beta)
- Most Unix variants with Motif/Lesstif
- MacOS 9.x and 10.x using Carbon (10.3 and above preferred)
- MacOS 10.x using Cocoa (beta)
- OS/2 (beta)
- PalmOS (alpha)
Most popular C++ compilers are supported; see the install.txt
file for each platform (available via docs/html/index.htm) for details.
@ -62,6 +65,7 @@ see the install.txt file in the individual directories:
docs/x11
docs/mgl
docs/os2
docs/palmos
Licence information
-------------------
@ -75,35 +79,37 @@ For licensing information, please see the files:
docs/lgpl.txt
Although this may seem complex, it is there to allow authors of
proprietary/commercial applications to use wxWidgets in
addition to those writing GPL'ed applications. In summary,
the licence is LGPL plus a clause allowing unrestricted
distribution of application binaries. To answer a FAQ, you
don't have to distribute any source if you wish to write
commercial applications using wxWidgets.
proprietary/commercial applications to use wxWidgets in addition
to those writing GPL'ed applications. In summary, the licence is
LGPL plus a clause allowing unrestricted distribution of
application binaries. To answer a FAQ, you don't have to
distribute any source if you wish to write commercial
applications using wxWidgets.
However, if you distribute wxGTK or wxMotif (with Lesstif) version
of your application, don't forget that it is linked against
GTK+ (or Lesstif) which is covered by LGPL *without* exception
notice. Under Linux systems your app is probably linked
against LGPL glibc as well. Please read carefully LGPL, section 6.
which describes conditions for distribution of closed source applications
linked against LGPL library. Basically you should link dynamically and
include source code of LGPL libraries with your product (unless it is
already present in user's system - like glibc usually is).
If compiled with --enable-odbc (Unix only), wxWidgets library will
contain iODBC library which is covered by LGPL.
However, if you distribute wxGTK or wxMotif (with Lesstif)
version of your application, don't forget that it is linked
against GTK+ (or Lesstif) which is covered by LGPL *without*
exception notice. Under Linux systems your app is probably linked
against LGPL glibc as well. Please read carefully LGPL, section
6. which describes conditions for distribution of closed source
applications linked against LGPL library. Basically you should
link dynamically and include source code of LGPL libraries with
your product (unless it is already present in user's system -
like glibc usually is). If compiled with --enable-odbc (Unix
only), wxWidgets library will contain iODBC library which is
covered by LGPL.
If you use TIFF image handler, please see src/tiff/COPYRIGHT
for libtiff licence details.
If you use JPEG image handler, documentation for your program should
contain following sentence: "This software is based in part on the work of
the Independent JPEG Group". See src/jpeg/README for details.
If you use JPEG image handler, documentation for your program
should contain following sentence: "This software is based in
part on the work of the Independent JPEG Group". See
src/jpeg/README for details.
If you use wxRegEx class on a system without native regular expressions
support (i.e. MS Windows), see src/regex/COPYRIGHT file for Henry Spencer's
regular expression library copyright.
If you use wxRegEx class on a system without native regular
expressions support (i.e. MS Windows), see src/regex/COPYRIGHT
file for Henry Spencer's regular expression library copyright.
If you use wxXML classes or XRC, see src/expat/COPYING for licence details.
@ -120,8 +126,10 @@ The wxWidgets bug database can be browsed at:
http://sourceforge.net/bugs/?group_id=9863
The Windows help files are located in docs/winhelp.
The Windows HTML Help files are located in docs/htmlhelp.
The Windows Help files are located in docs/winhelp.
The PDF help files are located in docs/pdf.
The HTB (wxWidgets HTML Help) files are located in docs/htb.
Further information
-------------------

7
docs/todo.txt
View File

@ -7,14 +7,9 @@ Please see also:
docs/motif/todo.txt
docs/msw/todo.txt
- Fix wxStream mess: problems with Eol(), LastCount(), buffering
- Fix wxStream: problems with Eol(), LastCount(), buffering
- Fix wxHTTP/wxFTP which are currently broken, fix/rewrite wxURL
- Add 3-state wxCheckBox
- In doc/view file selector, document type is selected by
extension, not the type selected in the (Windows) file selector.
- Add wxUSE_HOTKEY and any other missing options to configure.