Go to file
Kevin Ollivier da8b1d4b3b Rebake from clean wx tree.
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@63052 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
2010-01-04 00:45:45 +00:00
art Implement DrawTitleBarBitmap() for OS X using hard coded PNG images. 2009-10-05 22:57:32 +00:00
build Rebake from clean wx tree. 2010-01-04 00:45:45 +00:00
debian For the wxPython headers, we need to copy SWIG files like the other platforms do so that wxPython extensions can be built. 2009-04-14 17:11:30 +00:00
demos Rebake from clean wx tree. 2010-01-04 00:45:45 +00:00
distrib Make sure all Bakefile formats that use CRLF line feeds are set to use CRLF in SVN. 2009-10-08 04:07:02 +00:00
docs wxOwnerDrawComboCtrl -> wxComboCtrl 2009-12-30 17:07:16 +00:00
include Don't use a destroy event handler to disconnect the native control's delegate as the destroy event propagates and can cause the TLW to remove its delegate at unexpected times, such as when a child control is destroyed but the TLW remains active. Instead, do it in response to the Destroy() call. 2010-01-03 23:59:32 +00:00
interface Document wxPerl interface differences for wxRichTextCtrl. 2010-01-02 11:29:00 +00:00
lib add the abicheck.sh script for checking possible ABI violations 2009-02-01 17:17:58 +00:00
locale Romanian translation update from Catalin. 2010-01-03 17:37:24 +00:00
misc Don't use "-I @" in ctags command line as cmd.exe handles '@' specially. 2009-12-18 14:46:58 +00:00
samples Rebake from clean wx tree. 2010-01-04 00:45:45 +00:00
src Don't use a destroy event handler to disconnect the native control's delegate as the destroy event propagates and can cause the TLW to remove its delegate at unexpected times, such as when a child control is destroyed but the TLW remains active. Instead, do it in response to the Destroy() call. 2010-01-03 23:59:32 +00:00
tests Rebake from clean wx tree. 2010-01-04 00:45:45 +00:00
utils Rebake from clean wx tree. 2010-01-04 00:45:45 +00:00
acinclude.m4 fix output of WX_ARG_DISABLE() for options which can have values other than yes/no (e.g. auto, as for wxUSE_COMPILER_TLS) 2009-06-18 23:51:57 +00:00
aclocal.m4 don't use __thread keyword with g++ < 4 as it results in mysterious problems at link time related to thread-local static wxString::ms_cache 2008-11-23 01:53:24 +00:00
autoconf_inc.m4 Added samples/dll for showing how to use wxWidgets to implement 2009-12-05 18:54:40 +00:00
autogen.sh Use build/autoconf_prepend-include when running autoconf 2008-02-22 22:31:20 +00:00
BuildSVN.txt Removing Classic MacOS / CodeWarrior instructions as neither are supported any longer. 2009-03-12 19:14:14 +00:00
config.guess
config.sub
configure Correct wxUSE_MACOSX_VERSION_MIN setting when running under OS X 10.4. 2009-12-27 19:40:15 +00:00
configure.in Correct wxUSE_MACOSX_VERSION_MIN setting when running under OS X 10.4. 2009-12-27 19:40:15 +00:00
descrip.mms add more samples to the compile cascade for OpenVMS 2009-10-12 06:50:59 +00:00
install-sh
Makefile.in Rename gtk{,1}/tbargtk.{h,cpp} to toolbar.{h,cpp}. 2009-12-10 03:04:07 +00:00
mkinstalldirs
regen give an error message when ran from a wrong location instead of just saying that config.status is not found 2008-03-31 15:00:42 +00:00
setup.h_vms Updating configuration for OpenVMS 2009-10-23 10:52:41 +00:00
setup.h.in Enable wxGraphicsContext and related classes by default if supported. 2009-11-24 00:01:15 +00:00
version-script.in Fix accidental commit of 2.8 ABI compat. code. 2009-11-18 21:01:52 +00:00
wx-config-inplace.in and restored error checking too: this completes sequence of 3 check ins making wx-config work on systems with Bourne shell 2005-09-20 23:09:36 +00:00
wx-config.in Don't include LDFLAGS in wx-config --libs output. 2009-10-19 13:57:41 +00:00
wxBase.spec updated the version to 2.9.1 2009-07-05 11:51:53 +00:00
wxGTK.spec Added typeinfo.h which implements wxTypeId, using C++ RTTI if available. wxAny and Unbind<>() code are updated to use it. Added and updated related unit tests. 2009-11-19 19:27:24 +00:00
wxMGL.spec updated the version to 2.9.1 2009-07-05 11:51:53 +00:00
wxMotif.spec Added typeinfo.h which implements wxTypeId, using C++ RTTI if available. wxAny and Unbind<>() code are updated to use it. Added and updated related unit tests. 2009-11-19 19:27:24 +00:00
wxwin.m4 update wxpresets for new osx_carbon and osx_cocoa names provided by the wx-config --selected_config command 2009-10-22 15:44:30 +00:00
wxX11.spec Added typeinfo.h which implements wxTypeId, using C++ RTTI if available. wxAny and Unbind<>() code are updated to use it. Added and updated related unit tests. 2009-11-19 19:27:24 +00:00

wxWidgets 2.9.x
---------------------------------------------------------

Welcome to wxWidgets, a cross-platform C++ 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,
device contexts, printing, splitter windows and so on, there
are wrappers for common file operations, and facilities for
writing TCP/IP applications, thread handling, and more.

Where certain features are not available on a platform, such
as MDI under Unix and OS X, they are emulated.

A detailed reference manual including in-depth overviews for
various topics is supplied in various formats and can be
accessed online.

Changes in this release
-----------------------

Please see changes.txt and "Changes since 2.8" in the manual
for details.

Platforms supported
-------------------

wxWidgets currently supports the following platforms:

- Windows 95/98/ME, NT, 2000, XP, Vista, Pocket PC/Mobile, Smartphone
- Most Unix variants using the  GTK+ 2 toolkit (version 2.4 or newer)
- MacOS OS X (10.4 or newer) using Carbon and some Cocao mix-in

There is some support for the followig platforms:

- Most Unix variants with X11
- Most Unix variants with Motif/Lesstif
- Most Unix variants with GTK+ 1.2
- MacOS 10.x using the Cocoa API
- OS/2
- PalmOS

Most popular C++ compilers are supported; see the install.txt
file for each platform (available via docs/html/index.htm) for details.
See also http://www.wxwidgets.org/platform.htm.

Files
-----

The distribution is available in archive formats appropriate to the
target system. See the download pages for details.

Installation
------------

wxWidgets needs to be compiled before you can test out the samples
or write your own applications. For installation information, please
see the install.txt file in the individual directories:

  docs/msw
  docs/gtk
  docs/motif
  docs/osx
  docs/cocoa
  docs/x11
  docs/mgl
  docs/os2
  docs/palmos

Licence information
-------------------

For licensing information, please see the files:

  docs/preamble.txt
  docs/licence.txt
  docs/licendoc.txt
  docs/gpl.txt
  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. 

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 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 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.

Documentation
-------------

See docs/html/index.htm for an HTML index of the major documents.

See docs/changes.txt for a summary of changes to wxWidgets.

See docs/tech for an archive of technical notes.

The wxWidgets bug tracker can be browsed at:

    http://trac.wxwidgets.org/report

Please use the search function of our Trac installation to find
any possibly relevant bugs before reporting new ones. Also please
notice that often trying to correct the bug yourself is the
quickest way to fix it. Even if you fail to do it, you may
discover valuable information allowing us to fix it while doing
it. We also give much higher priority to bug reports with patches
fixing the problems so this ensures that your report will be
addressed sooner.

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
-------------------

The wxWidgets Web site is located at:

  http://www.wxwidgets.org

The main wxWidgets ftp site is at:

  ftp://biolpc22.york.ac.uk/pub

A wxWidgets CD-ROM with the latest distribution plus an HTML
front-end and hundreds of MB of compilers, utilities and other
material may be ordered from the CD-ROM page: see the wxWidgets
web site.

Have fun!

The wxWidgets Team, January 2007