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

Name change replacements

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@27090 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Julian Smart
2004-05-04 08:27:20 +00:00
parent e119d0498a
commit fc2171bd4c
268 changed files with 1372 additions and 1366 deletions
Download Patch File Download Diff File Expand all files Collapse all files

50
docs/x11/install.txt
View File

@@ -1,4 +1,4 @@
wxWindows 2.5 for X11 installation
wxWidgets 2.5 for X11 installation
----------------------------------
IMPORTANT NOTE:
@@ -9,7 +9,7 @@ IMPORTANT NOTE:
mailing wxwin-users or the author. Preferably, try to fix the
problem first and then send a patch to the author.
When sending bug reports tell us what version of wxWindows you are
When sending bug reports tell us what version of wxWidgets you are
using (including the beta) and what compiler on what system. One
example: wxX11 2.5.1, gcc 2.95.4, Redhat 6.2
@@ -18,16 +18,16 @@ First steps
- Download wxX11-x.y.z.tgz, where x.y.z is the version number.
Download documentation in a preferred format, such as
wxWindows-HTML.zip or wxWindows-PDF.zip.
wxWidgets-HTML.zip or wxWidgets-PDF.zip.
- Make a directory such as ~/wx and unarchive the files into this
directory.
- It is recommended that you install bison and flex; using yacc
and lex may require tweaking of the makefiles. You also need
libXpm if you want to have XPM support in wxWindows (recommended).
libXpm if you want to have XPM support in wxWidgets (recommended).
- You can now use configure to build wxWindows and the samples.
- You can now use configure to build wxWidgets and the samples.
Using configure is the recommended way to build the library. If it doesn't
work for you for whatever reason, please report it (together with detailed
@@ -40,7 +40,7 @@ COMPILING USING CONFIGURE
* The simplest case
-------------------
If you compile wxWindows on Linux for the first time and don't like to read
If you compile wxWidgets on Linux for the first time and don't like to read
install instructions just do (in the base dir):
> ./configure --with-x11
@@ -58,7 +58,7 @@ Afterwards you can continue with
> ldconfig
> exit
If you want to remove wxWindows on Unix you can do this:
If you want to remove wxWidgets on Unix you can do this:
> su <type root password>
> make uninstall
@@ -68,10 +68,10 @@ If you want to remove wxWindows on Unix you can do this:
* The expert case
-----------------
If you want to do some more serious cross-platform programming with wxWindows,
If you want to do some more serious cross-platform programming with wxWidgets,
such as for GTK and X11, you can now build two complete libraries and use
them concurrently. For this end, you have to create a directory for each build
of wxWindows - you may also want to create different versions of wxWindows
of wxWidgets - you may also want to create different versions of wxWidgets
and test them concurrently. Most typically, this would be a version configured
with --enable-debug_flag and one without. Note, that only one build can
currently be installed, so you'd have to use local version of the library for
@@ -122,12 +122,12 @@ g++ myfoo.cpp `wx-config --libs --cxxflags` -o myfoo
* General
---------
The Unix variants of wxWindows use GNU configure. If you have problems with
The Unix variants of wxWidgets use GNU configure. If you have problems with
your make use GNU make instead.
If you have general problems with installation, see the wxWindows website at
If you have general problems with installation, see the wxWidgets website at
http://www.wxwindows.org/
http://www.wxwidgets.org/
for newest information. If you still don't have any success, please send a bug
report to one of our mailing lists (see my homepage) INCLUDING A DESCRIPTION OF
@@ -137,12 +137,12 @@ YOU USE AND WHAT ERROR WAS REPORTED. I know this has no effect, but I tried...
* GUI libraries
---------------
wxWindows/X11 requires the X11 library to be installed on your system.
wxWidgets/X11 requires the X11 library to be installed on your system.
* Additional libraries
----------------------
wxWindows/X11 requires a thread library and X libraries known to work with
wxWidgets/X11 requires a thread library and X libraries known to work with
threads. This is the case on all commercial Unix-Variants and all
Linux-Versions that are based on glibc 2 except RedHat 5.0 which is broken in
many aspects. As of writing this, virtually all Linux distributions have
@@ -162,7 +162,7 @@ exit
Please send comments and question about the OS/2 installation
to Stefan Neis <Stefan.Neis@t-online.de> and patches to
the wxWindows mailing list.
the wxWidgets mailing list.
In the following list, the version numbers indicate the configuration that
was actually used by myself, newer version should cause no problems and
@@ -268,9 +268,9 @@ The following options handle the kind of library you want to build.
--disable-shared Do not create shared libraries.
--enable-monolithic Build wxWindows as single library instead
--enable-monolithic Build wxWidgets as single library instead
of as several smaller libraries (which is
the default since wxWindows 2.5.0).
the default since wxWidgets 2.5.0).
--disable-optimise Do not optimise the code. Can
sometimes be useful for debugging
@@ -310,7 +310,7 @@ The following options handle the kind of library you want to build.
such as gdb (or its many frontends).
--enable-debug_flag Define __DEBUG__ and __WXDEBUG__ when
compiling. This enable wxWindows' very
compiling. This enable wxWidgets' very
useful internal debugging tricks (such
as automatically reporting illegal calls)
to work. Note that program and library
@@ -321,11 +321,11 @@ The following options handle the kind of library you want to build.
-----------------
Many of the configure options have been thoroughly tested
in wxWindows snapshot 6, but not yet all (ODBC not).
in wxWidgets snapshot 6, but not yet all (ODBC not).
When producing an executable that is linked statically with wxX11
you'll be surprised at its immense size. This can sometimes be
drastically reduced by removing features from wxWindows that
drastically reduced by removing features from wxWidgets that
are not used in your program. The most relevant such features
are
@@ -396,7 +396,7 @@ password) and type
make install
You can remove any traces of wxWindows by typing
You can remove any traces of wxWidgets by typing
make uninstall
@@ -432,14 +432,14 @@ clean:
This is certain to become the standard way unless we decide
to stick to tmake.
If your application uses only some of wxWindows libraries, you can
If your application uses only some of wxWidgets libraries, you can
specify required libraries when running wx-config. For example,
`wx-config --libs=html,core` will only output link command to link
with libraries required by core GUI classes and wxHTML classes. See
the manual for more information on the libraries.
2) The other way creates a project within the source code
directories of wxWindows. For this endeavour, you'll need
directories of wxWidgets. For this endeavour, you'll need
GNU autoconf version 2.14 and add an entry to your Makefile.in
to the bottom of the configure.in script and run autoconf
and configure before you can type make.
@@ -456,7 +456,7 @@ and configure before you can type make.
# makewxx11
# Sets permissions (in case we extracted wxX11 from zip files)
# and makes wxX11.
# Call from top-level wxWindows directory.
# Call from top-level wxWidgets directory.
# Note that this uses standard (but commonly-used) configure options;
# if you're feeling brave, you may wish to compile with threads:
# if they're not supported by the target platform, they will be disabled
@@ -468,7 +468,7 @@ and configure before you can type make.
-------:x-----Cut here-----:x-----
This script will build wxX11 using shared libraries. If you want to build
a static wxWindows library, use --disable-shared.
a static wxWidgets library, use --disable-shared.
Troubleshooting
---------------

24
docs/x11/readme-nanox.txt
View File

@@ -14,12 +14,12 @@ The Microwindows web site is at
http://microwindows.org/
Nano-X is intended to work on devices with very small amounts
of memory. wxWindows is quite a large library, so if your
of memory. wxWidgets is quite a large library, so if your
memory is measured in KB instead of MB you will need to use
an alternative library, such as FLTK. However, with memory
capacity increasing all the time, wxWindows could become
capacity increasing all the time, wxWidgets could become
an appropriate embedded GUI solution for many projects.
Also, it's possible to think of ways to cut wxWindows
Also, it's possible to think of ways to cut wxWidgets
further down to size, such as disabling advanced controls
or rewriting utility functions. See the section on code size
below.
@@ -43,7 +43,7 @@ both at configuration time and at subsequent make time, so you
may find it convenient to put it in your .bash_profile or similar
file.
Typically, various features in wxWindows will be switched off to
Typically, various features in wxWidgets will be switched off to
conserve space. The sample script below calls configure with typical
options for Nano-X.
@@ -64,7 +64,7 @@ Port notes
==========
Nano-X has a different API from Xlib, although there
are many similarities. Instead of changing the wxWindows
are many similarities. Instead of changing the wxWidgets
code to reflect Nano-X conventions, a compatibility
layer has been added, in the form of these files:
@@ -105,14 +105,14 @@ Things to do:
Code Size
=========
Allow about 2.5 MB for a shared wxWindows library, with the
Allow about 2.5 MB for a shared wxWidgets library, with the
dynamically linked minimal sample taking about 24KB. If statically
linked, minimal takes up just over 1MB when stripped. This 1MB
includes all of wxWindows used in the minimal sample including some of
includes all of wxWidgets used in the minimal sample including some of
the wxUniversal widgets. As application complexity increases,
the amount of wxWindows code pulled into statically linked
the amount of wxWidgets code pulled into statically linked
executables increases, but for large applications, the overhead
of wxWindows becomes less significant.
of wxWidgets becomes less significant.
Sample sizes:
-------------
@@ -142,8 +142,8 @@ Strategies for reducing code size
- Rewrite functions or classes for alternative stripped-down
functionality.
- Remove unnecessary functionality or obsolete code from
wxWindows.
- Factor out wxWindows code to reduce repetition.
wxWidgets.
- Factor out wxWidgets code to reduce repetition.
- Add inlining, remove unnecessary empty functions.
- Separate code out into individual files so that all of
a .o file doesn't get pulled in, just because an app
@@ -162,7 +162,7 @@ Sample script for building wxNano-X
===================================
This script assumes that you will invoke it
from a build directory under the wxWindows
from a build directory under the wxWidgets
top level. So you might type:
% cd wx2

22
docs/x11/readme.txt
View File

@@ -1,16 +1,16 @@
Welcome to wxWindows/X11 2.5.1
Welcome to wxWidgets/X11 2.5.1
You have downloaded version 2.5.1 of the X11 port of
the wxWindows GUI library. This runs on X11 with no
the wxWidgets GUI library. This runs on X11 with no
Motif, Xt, GTK+ or any other standard widget set --
instead it uses the wxUniversal widgets. The intention
is to have it run on NanoX as well as desktop X11.
More information about the wxWindows project as a whole
More information about the wxWidgets project as a whole
can be found at:
http://www.wxwindows.org
http://www.wxwidgets.org
Information on how to install can be found in the file
install.txt, but if you cannot wait, this should work on
@@ -27,22 +27,22 @@ exit
When you run into problems, please read the install.txt and
follow those instructions. If you still don't have any success,
please send a bug report to one of our mailing lists (see
the wxWindows homepage) INCLUDING A DESCRIPTION OF YOUR SYSTEM AND
the wxWidgets homepage) INCLUDING A DESCRIPTION OF YOUR SYSTEM AND
YOUR PROBLEM, SUCH AS YOUR VERSION OF X, WHAT DISTRIBUTION YOU USE
AND WHAT ERROR WAS REPORTED. Alternatively, you may also use the bug
reporting system linked from the wxWindows web page.
reporting system linked from the wxWidgets web page.
The library produced by the install process will be called
libwx_x11univ[d].a (static) and libwx_x11univ[d]-2.3.so.0.0.0
(shared) so that once a binary incompatible version of
wxWindows/X11 comes out we'll augment the library version number
wxWidgets/X11 comes out we'll augment the library version number
to avoid linking problems.
Please send problems concerning installation, feature requests,
bug reports or comments to the wxWindows users list. Information
on how to subscribe is available from www.wxwindows.org.
bug reports or comments to the wxWidgets users list. Information
on how to subscribe is available from www.wxwidgets.org.
wxWindows/X11 doesn't come with any guarantee whatsoever. It might
wxWidgets/X11 doesn't come with any guarantee whatsoever. It might
crash your hard disk or destroy your monitor. It doesn't claim to be
suitable for any special or general purpose.
@@ -67,5 +67,5 @@ Some remaining issues:
Regards,
The wxWindows team
The wxWidgets team