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

2.4.3 and image changes

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/branches/WX_2_4_BRANCH@34193 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Julian Smart
2005-05-20 09:17:34 +00:00
parent d868e63b87
commit b32925c3da
48 changed files with 527 additions and 843 deletions
Download Patch File Download Diff File Expand all files Collapse all files

82
docs/gtk/changes.txt
View File

@@ -1,5 +1,5 @@
*** wxWindows 2.3.3 ***
*** wxWidgets 2.3.3 ***
Look at the General changes file for more encompassing on
the changes that have taken place in 2.3.3. This file has
@@ -78,13 +78,13 @@ wxStaticBox honours wxALIGN_XXX styles
Reworked wxConfig class interface.
Reworked wxDynamicLibary class for loading classes (particularly
wxWindows classes) from dynamic libraries.
wxWidgets classes) from dynamic libraries.
Removed wxObjectStream class.
Further improvements to wxFileName class.
*** wxWindows 2.3.2 ***
*** wxWidgets 2.3.2 ***
Addition of wxFileName class to handler DOS, Unix, Mac and VMS filenames
and paths in a platform independent way.
@@ -92,7 +92,7 @@ and paths in a platform independent way.
Addition of a wxPopupWindow class to imitate temporary windows such
as those used combo boxes or in tool tips.
Addition of wxToggleButton which was missing in wxWindows 2.2.
Addition of wxToggleButton which was missing in wxWidgets 2.2.
Support for virtual lists in wxListCtrl.
@@ -122,15 +122,15 @@ cross compilations.
Improved wxSizer-based layout system for better support for dynamic
layout.
*** wxWindows 2.3.0 ***
*** wxWidgets 2.3.0 ***
scaling for map modes other than wxMM_TEXT works correctly (Derry Bryson)
*** wxWindows 2.2.6 ***
*** wxWidgets 2.2.6 ***
wxGauge now supports wxGA_VERTICAL (Shane Forsythe)
*** 29th January 2001: wxWindows 2.2.5 released ***
*** 29th January 2001: wxWidgets 2.2.5 released ***
Synchronized with wxMSW 2.2.5, include macros
for upwards 2.4.0 compatibility.
@@ -140,7 +140,7 @@ Added missing wxEntry prototype to wx/gtk/app.h.
Fixed compilation with --enable-no_rtti/no_exceptions
with older egcs.
*** 15th January 2001: wxWindows 2.2.4 released ***
*** 15th January 2001: wxWidgets 2.2.4 released ***
Corrected wxYield() to handle recursive calls
more gracefully (and with a warning in debug mode).
@@ -172,7 +172,7 @@ Various other fixes.
Synchronized release with wxMSW again.
*** 3rd November: wxWindows 2.2.3 released ***
*** 3rd November: wxWidgets 2.2.3 released ***
Fixed bugs in HTTP code.
@@ -199,7 +199,7 @@ Updated AFM font metrics for Ghostscript fonts and let
Linux and FreeBSD default to using GS fonts (and not
Adobe fonts).
*** 20th September: wxWindows 2.2.2 released ***
*** 20th September: wxWidgets 2.2.2 released ***
Fixed wxSizer bug that made items with option
flags greater than 1 report a wrong size.
@@ -217,7 +217,7 @@ Fixed wxListCtrl::HitTest() for report mode.
Other minor fixes.
*** 20th August 2000: wxWindows 2.2.1 released ***
*** 20th August 2000: wxWidgets 2.2.1 released ***
Minor build fixes.
@@ -250,7 +250,7 @@ Minor correction to doc-view architecture.
Minor wxCommandLineParser changes.
*** 10th July 2000: wxWindows 2.2.0 released ***
*** 10th July 2000: wxWidgets 2.2.0 released ***
Added code for writing BMP images.
@@ -281,7 +281,7 @@ Various fixes to the new wxGrid class.
Bug-fixes.
*** 4th June 2000: wxWindows pre-2.2 release ***
*** 4th June 2000: wxWidgets pre-2.2 release ***
Complete freeze now. Only vital bug-fixes allowed.
@@ -293,12 +293,12 @@ Reworked wxURL.
MANY bugfixes.
*** 22th March 2000: wxWindows 2.1.15 released ***
*** 22th March 2000: wxWidgets 2.1.15 released ***
Build fix. RPMs no longer require GTK's include files.
An extra library for the OpenGl class now gets built
*** 19th March 2000: wxWindows 2.1.14 released ***
*** 19th March 2000: wxWidgets 2.1.14 released ***
An extra library for the OpenGl class now gets built
and installed. There is also an extra RPM for this
@@ -359,7 +359,7 @@ style when using the default.
The L-GPL iODBC library must now be enables explicitly so as
to not mislead people into reading the license wrong.
*** 24th January '2000: wxWindows 2.1.13 released ***
*** 24th January '2000: wxWidgets 2.1.13 released ***
Corrections to TAB handling in notebooks.
@@ -404,7 +404,7 @@ Updates to the ODBC classes (George Tasker).
Build-fixes for various platforms and compilers.
*** 6th January '2000: wxWindows 2.1.12 released ***
*** 6th January '2000: wxWidgets 2.1.12 released ***
Who has a BigEndian computer (e.g. Sparc or PowerPC) that runs a 15
and/or 16 bit colour mode? I need this for testing purposes, i.e. this
@@ -515,7 +515,7 @@ More minor changes and fixes.
Began work on a new dialog and resource editor (wxDesigner).
*** 7st November '99: wxWindows 2.1.11 released ***
*** 7st November '99: wxWidgets 2.1.11 released ***
There is still an unresolved problem with bitmap to image
conversion on big-endian architectures (such as Solaris),
@@ -524,14 +524,14 @@ one as I have no BE computer.
Enlightenment has struck the majority of the developers and
they have chosen to use the Linux kernel numbering scheme
for wxWindows from now on. This means that the next stable
release will be called wxWindows 2.2.X, development snapshots
for wxWidgets from now on. This means that the next stable
release will be called wxWidgets 2.2.X, development snapshots
will be called 2.1.X.
A lot of discussion has been wasted on how to maintain a
once released stable version. It was almost universally
agreed that only a commercial entity will have the motivation
($$$) to do that - so far there is no wxWindows Inc.
($$$) to do that - so far there is no wxWidgets Inc.
Support for GTK 1.0 has been dropped. This version has
been tested with GTK 1.2.3 and GTK 1.2.6 - it might
@@ -553,7 +553,7 @@ try again, poor AIX, HP-UX and *BSD users, but don't reckon
with immediate success. Actually, when using GNU compilers,
your chances are quite good.
My rewrite of the wxWindows underlying GTK widget
My rewrite of the wxWidgets underlying GTK widget
has turned scrolling including subwindows from barely
functional to pretty and fast. I also added scrolling
of foreign windows to wxScrolledWindow.
@@ -573,7 +573,7 @@ can now use wxODBC from wxMSW and wxGTK.
Several printing things fixed. More work needs to be done
here..
HTML widget and the wxWindows' help system based upon
HTML widget and the wxWidgets' help system based upon
it have been reorganized and improved for easier use
from Python and C++. Also HTML printing has been added.
@@ -588,14 +588,14 @@ without shadow affect).
Michael is writing a complete rewrite of the antiquated
wxGrid. This is still work-in-progress and might not make
it into wxWindows 2.2, we'll see. Help would be welcome
it into wxWidgets 2.2, we'll see. Help would be welcome
to make that happen.
Made wxMenu code lose less memory, also added wxMenu::Delete().
Added code to send wxActivateEvent to MDI windows.
Vadim added configure things to compile wxWindows without any
Vadim added configure things to compile wxWidgets without any
GUI library. This is probably work in progress. He'll also add
a wxFontEnumerator class and has enhanced wxFont to make use
of char-encodings.
@@ -823,7 +823,7 @@ Implemented global cursors and wxBusyCursor etc. Also removed
another cursor misbehaviour.
Updated many parts of the documentation to reflect changes
in wxWindows 2.1, wxPython and more exact description of
in wxWidgets 2.1, wxPython and more exact description of
cross-platform issues as well as platform differences.
Many other fixes, mainly by others...
@@ -935,7 +935,7 @@ Note that the next release might bring about changes to keyboard
handling and scroll event intercepting from wxScrolledWindow.
By and large much of the code has stabilized and won't be much
*** different in the final wxWindows 2.1 release. Please test as ***
*** different in the final wxWidgets 2.1 release. Please test as ***
much as you can.
The next release will have a new build system.
@@ -981,7 +981,7 @@ This no longer forces wxGTK applications to sleep (by having
to call usleep()) in idle time - giving more CPU slices to
the application if desired.
wxGLCanvas (the OpenGl for wxWindows) now accepts keyboard input.
wxGLCanvas (the OpenGl for wxWidgets) now accepts keyboard input.
The usual number of compile and bug fixes from all involved.
@@ -1026,7 +1026,7 @@ wxPython still doesn't compile, I think.
12th April '99: First wxGTK 2.1 snapshot released
This is the first developers' version of wxWindows 2.1 for GTK. It's main
This is the first developers' version of wxWidgets 2.1 for GTK. It's main
new feature is that it supports GTK 1.2 (as opposed to GTK 1.0) which
will make development within the GNOME environment a lot easier.
@@ -1062,16 +1062,16 @@ goodies, possibly world domination.
*** 5th March '99: wxWindows 2.0 released ***
*** 5th March '99: wxWidgets 2.0 released ***
This is the final version of wxWindows 2.0 for GTK. The versions for
This is the final version of wxWidgets 2.0 for GTK. The versions for
Windows and Motif (and also this version) are available form Julian Smart's
site. The Mac version is still under development.
*** 19th February '99: wxWindows 2.0 beta 5 ***
*** 19th February '99: wxWidgets 2.0 beta 5 ***
This is the fifth beta release and it contains mostly bug fixes and
@@ -1081,7 +1081,7 @@ Applied compile fixes for Solaris (different flavours and compilers).
*** 12th February '99: wxWindows 2.0 beta 4 ***
*** 12th February '99: wxWidgets 2.0 beta 4 ***
This is the fourth beta release and it contains mostly bug fixes and
@@ -1100,7 +1100,7 @@ Fixed many bugs. You guessed it.
*** 29th January '99: wxWindows 2.0 beta 3 ***
*** 29th January '99: wxWidgets 2.0 beta 3 ***
This is the third beta release and it contains mostly bug fixes.
@@ -1109,7 +1109,7 @@ There is one field where we haven't been able to fix the API yet, and that
it Drag'n'Drop. This is mostly due to the fact that DnD in
GTK 1.0 is hardly usable and much different from GTK 1.2 which means that
we have to design a common API for Windows, GTK 1.0 and GTK 1.2. Although
we are trying to prevent that, it is possible that wxWindows 2.0 (being
we are trying to prevent that, it is possible that wxWidgets 2.0 (being
based on GTK 1.0) will not have proper DnD support.
The major changes are that tool tips have been added, threads have been completely
@@ -1141,7 +1141,7 @@ SuSE 6.0 as SuSE decided to ship 6.0 with a broken GTK+ package.
*** 6th January '99: wxWindows 2.0 beta 2 ***
*** 6th January '99: wxWidgets 2.0 beta 2 ***
This is the second beta release and contains it mostly build and
@@ -1150,7 +1150,7 @@ commercial Unices and Windows.
*** 20th December '98: wxWindows 2.0 beta 1 ***
*** 20th December '98: wxWidgets 2.0 beta 1 ***
This is the first beta release and we have used the time before
@@ -1164,7 +1164,7 @@ program statically with wxGTK.
We changed the name of the shared library to include the version of
the GTK used so that no conflicts emerge with simultaneous
versions of wxWindows for GTK 1.0 and for GTK 1.2 and so on.
versions of wxWidgets for GTK 1.0 and for GTK 1.2 and so on.
As you can see, we have not moved to GTK 1.1.X as the different
development versions are too different and buggy to be useful. We'll
@@ -1175,7 +1175,7 @@ wxGTK now compiles without problems on anything between gcc 2.7.2 on
Linux-x86 and egcs 1.1 on Linux-Alpha and egcs 1.0 on Sparc. This isn't
as easy as it sounds...
Available form this site are the Python bindings of wxWindows.
Available form this site are the Python bindings of wxWidgets.
Thanks to Robin Dunn for this tremendous contribution.
Tkinter is dead, Java is dead, wxPython rules! That's all there is to say.
@@ -1217,9 +1217,9 @@ resulting in unexpected behaviour so it was decided to remove these
constructors.
As the number of users and the number of test programs and samples
is steadily rising the core classes of wxWindows for MSW and GTK 1.0
is steadily rising the core classes of wxWidgets for MSW and GTK 1.0
can be considered to be very stable if not outright bug-free. I haven't
seen a crash for weeks now and wxWindows' internal debug features also
seen a crash for weeks now and wxWidgets' internal debug features also
have improved every week, making stepping-through with a debugger almost
completely unnecessary as the library reports possible errors itself
(when in debug mode).

38
docs/gtk/install.txt
View File

@@ -1,4 +1,4 @@
wxWindows 2.4 for GTK installation
wxWidgets 2.4 for GTK installation
----------------------------------
IMPORTANT NOTE:
@@ -9,14 +9,14 @@ 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: wxGTK 2.4.0, gcc 2.95.4, Redhat 6.2
* 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-gtk
@@ -34,7 +34,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
@@ -44,7 +44,7 @@ If you want to remove wxWindows on Unix you can do this:
* The GTK+ 2 case
-----------------
wxGTK 2.4.2 has support for the new version 2.0.X of GTK+. This means
wxGTK 2.4.3 has support for the new version 2.0.X of GTK+. This means
that wxGTK apps can now make use Unicode as the underlying encoding
for all text operations. This is a very fundamental change and will
need time to stabilize, so be careful. Anyways, after installing a
@@ -68,10 +68,10 @@ Expect problems.
* 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 Motif, 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 and one without. Note, that only one build can
currently be installed, so you'd have to use local version of the library for
@@ -114,7 +114,7 @@ LD_LIBRARY_PATH or equivalent variable contains the path to GTK+ libraries if
they were installed in a non default location.
You get errors from make: please use GNU make instead of the native make
program. Currently wxWindows can be built only with GNU make, BSD make and
program. Currently wxWidgets can be built only with GNU make, BSD make and
Solaris make. Other versions might work or not (any which don't have VPATH
support definitely won't).
@@ -142,7 +142,7 @@ 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, read my homepage at
@@ -158,7 +158,7 @@ but I tried...
* GUI libraries
---------------
wxWindows/GTK requires the GTK+ library to be installed on your system. It has
wxWidgets/GTK requires the GTK+ library to be installed on your system. It has
to be a stable version, preferably version 1.2.10 (at least 1.2.3 is required,
1.2.7 is strongly recommended).
@@ -172,7 +172,7 @@ at my homepage.
* Additional libraries
----------------------
wxWindows/Gtk requires a thread library and X libraries known to work with
wxWidgets/Gtk 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, these Linux distributions have correct glibc
@@ -198,7 +198,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
@@ -271,8 +271,8 @@ to see all the options please use:
./configure --help
It is recommended to build wxWindows in another directory (maybe a
subdirectory of your wxWindows installation) as this allows you to
It is recommended to build wxWidgets in another directory (maybe a
subdirectory of your wxWidgets installation) as this allows you to
have multiple configurations (for example, debug and release or GTK
and Motif) simultaneously.
@@ -339,7 +339,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
@@ -357,14 +357,14 @@ The following options handle the kind of library you want to build.
When producing an executable that is linked statically with wxGTK
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
--with-odbc Enables ODBC code. This is disabled
by default because iODBC is under the
L-GPL license which is less liberal than
wxWindows license.
wxWidgets license.
--without-libpng Disables PNG image format code.
@@ -433,7 +433,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
@@ -470,7 +470,7 @@ This is certain to become the standard way unless we decide
to stick to tmake.
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.

16
docs/gtk/readme.txt
View File

@@ -1,20 +1,20 @@
Welcome to wxWindows/Gtk 2.4
Welcome to wxWidgets/Gtk 2.4
you have downloaded version 2.4 of the GTK port of the
wxWindows GUI library.
wxWidgets GUI library.
wxWindows no longer supports GTK 1.0 (as did some early
wxWidgets no longer supports GTK 1.0 (as did some early
snapshots) so that you will need GTK 1.2 when using it.
GTK 1.2.6 or above is recommended although some programs
will work with GTK 1.2.3 onwards. There is now support
for GTK 2.0.
More info about the wxWindows project (and the Windows
More info about the wxWidgets project (and the Windows
and Motif ports in particular) can be found at Julian's
homepage 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
@@ -45,17 +45,17 @@ WAS REPORTED. I know this has no effect, but I tried...
The library produced by the install process will be called
libwx_gtk.a (static) and libwx_gtk-2.2.so.0.0.0 (shared) so
that once a binary incompatible version of wxWindows/Gtk comes
that once a binary incompatible version of wxWidgets/Gtk 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
bug reports or comments to the wxWidgets users list. Information
on how to subscribe is available from my homepage.
Do NOT send any comments directly to me.
wxWindows/Gtk doesn't come with any guarantee whatsoever. It
wxWidgets/Gtk doesn't come with any guarantee whatsoever. It
might crash your harddisk or destroy your monitor. It doesn't
claim to be suitable for any special or general purpose.