Go to file
Vadim Zeitlin 50805a002a Work around wrong vsscanf() declaration under HP-UX.
Under this system vsscanf() is declared as taking a non-const char* as first
argument which prevented our code using it from compiling. Wrap it in
wxCRT_VsscanfA() adding the necessary const_cast<> to fix this.

Closes #15638.

git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@75340 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
2013-12-03 13:38:35 +00:00
art
build Add XRC handler for wxAuiToolBar. 2013-11-23 00:34:55 +00:00
demos More version change related changes to the generated files. 2013-11-23 00:34:42 +00:00
distrib Remove all lines containing cvs/svn "$Id$" keyword. 2013-07-26 16:02:46 +00:00
docs Document the order in which event tables are examined. 2013-11-25 12:12:24 +00:00
include Work around wrong vsscanf() declaration under HP-UX. 2013-12-03 13:38:35 +00:00
interface Minor clarifications to wxTextEntry::SetHint() docs. 2013-12-02 17:46:30 +00:00
lib remove executable property from non-executable files, closes #15504 2013-09-16 15:47:27 +00:00
locale Add a missing string in Slovakian translations. 2013-12-02 12:58:11 +00:00
misc Add XRC handler for wxAuiToolBar. 2013-11-23 00:34:55 +00:00
samples always initialize m_statText 2013-11-25 16:50:06 +00:00
src Implement wxTextEntry::SetHint() natively for GTK+3. 2013-12-02 17:46:27 +00:00
tests Try to use /proc/self instead of /dev/core in the unit test. 2013-12-02 16:50:22 +00:00
utils More version change related changes to the generated files. 2013-11-23 00:34:42 +00:00
.travis.yml Update Travis configuration to run tests and build more configurations. 2013-08-07 11:08:21 +00:00
acinclude.m4 Remove all lines containing cvs/svn "$Id$" keyword. 2013-07-26 16:02:46 +00:00
aclocal.m4 support for GTK3 2012-06-30 20:39:06 +00:00
autoconf_inc.m4 Better fix for wxX11 linking problems than r74499. 2013-07-13 23:35:55 +00:00
autogen.sh
BuildSVN.txt Merge the changes from 3.0 branch. 2013-11-12 18:06:37 +00:00
config.guess
config.sub
configure Work around wrong vsscanf() declaration under HP-UX. 2013-12-03 13:38:35 +00:00
configure.in Work around wrong vsscanf() declaration under HP-UX. 2013-12-03 13:38:35 +00:00
descrip.mms Update OpenVMS compile support 2013-08-27 12:02:20 +00:00
install-sh
Makefile.in Add XRC handler for wxAuiToolBar. 2013-11-23 00:34:55 +00:00
mkinstalldirs Remove all lines containing cvs/svn "$Id$" keyword. 2013-07-26 16:02:46 +00:00
regen Remove all lines containing cvs/svn "$Id$" keyword. 2013-07-26 16:02:46 +00:00
setup.h_vms Work around wrong vsscanf() declaration under HP-UX. 2013-12-03 13:38:35 +00:00
setup.h.in Work around wrong vsscanf() declaration under HP-UX. 2013-12-03 13:38:35 +00:00
version-script.in Remove all lines containing cvs/svn "$Id$" keyword. 2013-07-26 16:02:46 +00:00
wx-config-inplace.in Remove all lines containing cvs/svn "$Id$" keyword. 2013-07-26 16:02:46 +00:00
wx-config.in slight simplification: use another sed expression instead of running tr 2013-10-16 17:09:07 +00:00
wxwin.m4 Remove all lines containing cvs/svn "$Id$" keyword. 2013-07-26 16:02:46 +00:00

                wxWidgets 3.1.0 Release Notes
                =============================

Welcome to the latest development release of wxWidgets, a free and
open source cross-platform C++ framework for writing advanced GUI
applications using native controls.


wxWidgets allows you to write native-looking GUI applications for
all the major desktop platforms and also helps with abstracting
the differences in the non-GUI aspects between them. It is free
for the use in both open source and commercial applications, comes
with the full, easy to read and modify, source and extensive
documentation and a collection of more than a hundred examples.
You can learn more about wxWidgets at

        http://www.wxwidgets.org/

and read its documentation online at

        http://docs.wxwidgets.org/3.1.0/


wxWidgets sources and binaries for the selected platforms are
available for download from

        https://sourceforge.net/projects/wxwindows/files/3.1.0/

or

        ftp://ftp.wxwidgets.org/pub/3.1.0/

Please see the "Files" section below for the description of various
files available at these locations.



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



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

wxWidgets currently supports the following primary platforms:

- Windows 95/98/ME, NT, 2000, XP, Vista, 7 (32/64 bits).
- Most Unix variants using the GTK+ toolkit (version 2.6 or newer)
- Mac OS X (10.5 or newer) using Cocoa (32/64 bits) or Carbon (32 only)

There is some support for the following platforms:

- Most Unix variants with X11
- Most Unix variants with Motif/Lesstif
- Most Unix variants with GTK+ 1.2
- OS/2
- Windows CE (Pocket PC)

Most popular C++ compilers are supported; see the install.txt
file for each platform (available via docs/html/index.htm) and
http://wiki.wxwidgets.org/Supported_Platforms for the most up to
date status.


Files
-----

wxWidgets is distributed in source form in several archive formats.
ZIP and 7z archives are for Microsoft Windows users and contain the
files with DOS/Windows line endings while the compressed tar archives
for Unix systems users (including OS X) and contain the files with
Unix line endings. Please notice that some Windows tools still don't
accept files with Unix line endings and that compiling sources with
DOS line endings under Unix will fail, so please choose the correct
file for your system.

In addition to the sources, documentation in HTML, CHM and HTB
(wxWidgets help viewer) formats is provided as well as an installer
for Microsoft Windows. Notice that you will still need to compile
wxWidgets even when using the installer.

We also supply binaries of wxMSW libraries built with several
versions of Microsoft Visual C++ and GNU g++ compiler for this
release. They are available in the "binaries" subdirectory, see
the description of the files in the README file there.


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

Unless you have downloaded the binaries for your compiler, you
will need to build wxWidgets before you can test out the samples
or write your own applications. For installation information,
please see the install.txt file in the docs subdirectory
appropriate for the platform you use.


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

For licensing information, please see the files:

  docs/preamble.txt
  docs/licence.txt
  docs/licendoc.txt
  docs/gpl.txt
  docs/lgpl.txt
  docs/xserver.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 and so is bound by its requirements.

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

wxWidgets documentation is available online at
http://docs.wxwidgets.org/3.1.0/ and can also be downloaded in
HTML format. To generate documentation in other formats (PDF, CHM,
...) please use the scripts in docs/doxygen directory.


Bug reporting
-------------

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.


Further information
-------------------

If you are looking for support, you can get it from

- wxForum at http://forums.wxwidgets.org/
- wx-users mailing list (http://www.wxwidgets.org/support/maillst2.htm)
- #wxwidgets IRC channel
- http://stackoverflow.com/ if you tag your question with "wxwidgets"


Have fun!

The wxWidgets Team, November 2013