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

applied typos and spelling error fixes patch from Olly Betts

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@15779 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Vadim Zeitlin
2002-06-07 20:15:28 +00:00
parent f06ef5f4a3
commit 2edb0bdef6
158 changed files with 429 additions and 422 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/tech/tn0001.txt
View File

@@ -12,7 +12,7 @@ samples/ with demos/ where needed).
3. Create the makefiles for Windows compilers. There are several ways to do
it:
a) copy the makefiles from samples/minimal, replace all occurences of
a) copy the makefiles from samples/minimal, replace all occurrences of
minimal with foo
b) use makegen (sources are under utils/makegen)
c) use projgen

2
docs/tech/tn0003.txt
View File

@@ -58,7 +58,7 @@ v2.2.0 of wxWindows to use the -interactive switch
If you wish to generate documentation for wxHTML Help Viewer
(or Windows HTML Help), set htmlWorkshopFiles to true in your
tex2rtf.ini file. See also the wxHTML Notes section in the
wxWindows manual. To futher speed-up HTML help books loading
wxWindows manual. To further speed-up HTML help books loading
in your application, you may use hhp2cached (utils/hhp2cached).
src/msw/makefile.vc contains targets for generating various

8
docs/tech/tn0004.htm
View File

@@ -57,7 +57,7 @@ To make the samples</h2>
Solution 1</h3>
<h4>
<a href="http://biolpc22.york.ac.uk/wx/bc/download.html">Download</a> a zip file which contains modifed
<a href="http://biolpc22.york.ac.uk/wx/bc/download.html">Download</a> a zip file which contains modified
cpp, mak and bpr files - it will overwrite your wx distribution cpp files!</h4>
<h4>
@@ -185,12 +185,12 @@ add the location of the wx/include files in the&nbsp; project | options
</ul>
I found in CBuilder 1 that the <tt>idetomak</tt> utility did not manage
to convert all the samples, but <tt>idetobpr</tt> worked OK in CBuilder
3 and 4. I have a report that not all the bpr files made inb CBuilder 4
3 and 4. I have a report that not all the bpr files made in CBuilder 4
are correct
<h2>
Error with ODBC32</h2>
Sometimes you get an error saying that there are unreolved externals in
ODBC. The soltuion is to run a command prompt in your <b><tt>wx\lib </tt></b>directory
Sometimes you get an error saying that there are unresolved externals in
ODBC. The solution is to run a command prompt in your <b><tt>wx\lib </tt></b>directory
and use the <b><tt>implib </tt></b>command:
<p><tt>C:\wx\lib><b>implib odbc32 c:\windows\system\odbc32.dll</b></tt>
<p>This creates the necessary library, odbc32.lib

2
docs/tech/tn0007.txt
View File

@@ -13,7 +13,7 @@ First release Feb. 1999, detlev@reymann-online.de
=====================================
There are two IDE files. src\bc32.ide should help you to
create the wxWindows libraries from within the Ide of Borlands
create the wxWindows libraries from within the Ide of Borland's
C++, v. 5.x. Note that this doesn't include debugging code: you
need to change the settings if you wish to include debug
information. Previously, bc32d.ide was supplied with debug

14
docs/tech/tn0008.htm
View File

@@ -31,11 +31,11 @@ To: wx-users@wxwindows.org<BR>
Subject: Re: [wx-users] How to learn using wx-windows <BR>
Reply-To: wx-users@wxwindows.org<P>
> Reading the Linux Journal article on wxpython, and having used wxclips<BR>
> I got interested in wxwindows as a development interface. However, the<BR>
> programming experience I got is old, and from a former generation (For-<BR>
> tran). I'd like to refresh my experience and start in C++. Will<BR>
> wx-windows be a very high step to take?<P>
&gt; Reading the Linux Journal article on wxpython, and having used wxclips<BR>
&gt; I got interested in wxwindows as a development interface. However, the<BR>
&gt; programming experience I got is old, and from a former generation (For-<BR>
&gt; tran). I'd like to refresh my experience and start in C++. Will<BR>
&gt; wx-windows be a very high step to take?<P>
I'm new to wxWindows myself, but I'd like to answer this question
anyway. In the past two years I've learned two similar frameworks
@@ -54,7 +54,7 @@ iceberg.<P>
Besides the C++ Programming Language, by Bjarne Stroustrup, the
"official" guide to C++, I highly recommend Inside the C++ Object Model,
by Stanley B. Lippman. (Lipmann was one of the C++ honchos at Bell
by Stanley B. Lippman. (Lippman was one of the C++ honchos at Bell
Labs.) This book will tell you what _not_ to do, as well as why
everything in C++ is as it is. If you are confused by anything in C++,
Lippman's book is the cure.<P>
@@ -117,7 +117,7 @@ and then calling methods using those objects.<P>
Learn as much as you can about the String class; after using a good
String class you'll never want to use C's string functions again.
wxWindows contains other nifty utilty classes as well.<P>
wxWindows contains other nifty utility classes as well.<P>
The application class, wxApp, contains the main event loop. Learn about
event handling and event tables (reading sample code will help). Almost

2
docs/tech/tn0009.htm
View File

@@ -31,7 +31,7 @@ depths, and can be loaded from a file or loaded from the Windows resources compi
into the executable.<P>
You can decide to use only XPMs on Windows and Unix, or you could use XPMs on Unix and
Windows icons under Windows -- the latter will require some #idefs in your code or use of the wxICON macro.<P>
Windows icons under Windows -- the latter will require some #ifdefs in your code or use of the wxICON macro.<P>
If you are using a compiler such as Borland C++, Visual C++ or Watcom C++, you
can use the provided icon editor. However, if using Cygwin or Mingw32, there

4
docs/tech/tn0010.htm
View File

@@ -75,7 +75,7 @@ The <B>Additional include directories</B> field should contain the following:<P>
<PRE>
c:\wx2\include,c:\wx2\contrib\include
</PRE>
<P>(and of couse any other directories you wish to use in your project).<P>
<P>(and of course any other directories you wish to use in your project).<P>
<DT><B>C/C++: Precompiled Headers</B><DD>
@@ -166,7 +166,7 @@ The <B>Additional include directories</B> field should contain the following:<P>
<PRE>
../../include/base,../../include/msw
</PRE>
<P>(and of couse any other directories you wish to use in your project).<P>
<P>(and of course any other directories you wish to use in your project).<P>
<DT><B>C/C++: Precompiled Headers</B><DD>

2
docs/tech/tn0012.txt
View File

@@ -15,7 +15,7 @@ installed together.
To manage this sanely we need a sufficiently descriptive and logical
labelling convention for file and install path names -- this document (at
least at it's time of writing) describes the system we have adopted.
least at its time of writing) describes the system we have adopted.
It is not fine grained enough to include every possible build configuration
for wxWindows, but is encompassing enough to maintain a relatively complete