Merge the changes from 3.0 branch.

git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@75178 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Vadim Zeitlin
2013-11-12 18:06:37 +00:00
parent e4d0bc4bb1
commit 9b31387508
100 changed files with 7289 additions and 1390 deletions

View File

@@ -41,7 +41,7 @@ mention that wxWidgets is a C++ framework for building rich GUI
applications from a single source which can then be compiled on
different operating systems, resulting in a native application on
each system. wxWidgets uses native controls (or widgets) and other
native functions whereever possible so that the resulting
native functions wherever possible so that the resulting
applications will look and feel as native as possible, and they are
usually not distinguishable from applications written using single
platform toolkits such as MFC for Windows, GTK+ for Linux or Cocoa
@@ -51,9 +51,9 @@ achieve perfect integration with that platform.</P>
<P ALIGN=JUSTIFY>The major operating system for which wxWidgets
supports are Windows (Windows 95, NT, 2000, XP, Vista) including its
mobile variants (Windows CE, PocketPC, Windows Mobile), Linux and
Unix using the GTK+ 2 toolkit (minimum version is GTK+ 2.4, more
Unix using the GTK+ 2 toolkit (minimum version is GTK+ 2.6, more
recent features are used when available) and Mac OS X (minimum
version 10.4 Tiger, both Intel, PPC and the Universal Binaries for
version 10.5 Tiger, both Intel, PPC and the Universal Binaries for
both are supported). wxWidgets includes many code pieces for
optimising dialog and general layout for small screens such as those
of the recent netbooks and mobile phones and tablets.</P>
@@ -103,8 +103,8 @@ tries to both make use of new features of the different operating
systems and support older systems for as long as possible and as long
as supporting them does not hinder development for up-to-date
systems. This is especially true for OS X and GTK+ 2 and it was
therefore decided that OS X versions older than 10.4 Tiger and GTK+ 2
version older than 2.4 are no longer supported. The wxWidgets team
therefore decided that OS X versions older than 10.5 Leopard and GTK+ 2
version older than 2.6 are no longer supported. The wxWidgets team
also realized that it could not do everything and that support for a
cross-platform database API was beyond the scope and focus of the
project so that its old wxODBC database connectivity classes were
@@ -209,7 +209,7 @@ and may thus be the most important changes from a user's perspective
control used to display lists and hierarchies of name-value pairs.
Like wxDataViewCtrl, it offers a number of ready-to-use editors for
editing text, numbers, lists, fonts, file names etc. using in-place
editing or using pop-up dialog and combo boxes. Developement of
editing or using pop-up dialog and combo boxes. Development of
wxPropertyGrid has so far taken place outside of wxWidgets as a
separate project, but it has not been included in wxWidgets per se.
See also <A HREF="http://docs.wxwidgets.org/trunk/classwx_property_grid.html">wxPropertyGrid</A>.</P>
@@ -271,28 +271,24 @@ iPhone and iPod, and these are devices are clearly not Macs. Apart
from the name change wxMac has undergone the most fundamental
changes of the three main ports, even if some of the changes were
mostly reorganizing code instead of writing new code. The code has
been reorganized into common code (common to Carbon, Cocoa and Cocoa
been reorganized into common code (common to Carbon, Cocoa, and Cocoa
Touch) including both general wrapping or front-end classes for much
of the GUI code as well as a wrapper for the so called CoreFoundation
classes of OS X, which are responsible on all OS X variants for
string manipulation, font support, graphics and other basic
functionality (CoreImage and CoreVideo have recently been added by
Apple) and toolkit dependent code for the Carbon, Cocoa and Cocoa
Touch API. The Carbon variant is the core of what used to be wxMac
and is the most stable and mature version. The reason behind adding
optional support for Cocoa and Cocoa Touch is that Carbon is not
available on iPhones at all and that it has been deprecated for all
64-bit versions of OS X, which is likely to be the default a few
years from now. So while present applications using wxOSX are advised
to use the Carbon backend due its maturity, future developement will
have to focus on the Cocoa backend.</P>
functionality and toolkit dependent code for the Carbon, Cocoa, and
Cocoa Touch API. wxOSX/Carbon is the core of what used to be wxMac
and is now deprecated in favour of wxOSX/Cocoa. Existing applications
are encouraged to switch to wxOSX/Cocoa as Carbon is a deprecated OS X
feature, not available for 64-bit GUI applications, and not available for
iOS devices at all.</P>
<P ALIGN=JUSTIFY>As part of the restructuring, all remaining drawing
code using the old QuickDraw API has been removed (it was only an
option before) and drawing now always takes place using CoreGraphics.
Likewise, all code using Carbon functions no longer present in OS X
10.4 has been removed to clean-up the code greatly. This is turn
10.4 and 10.5 has been removed to clean-up the code greatly. This is turn
means, as mentioned above, that applications will require a minimum
of OS X 10.4 in order to run, better yet OS X 10.5.</P>
of OS X 10.5 in order to run.</P>
<P ALIGN=JUSTIFY>Apart from these large changes, these additional
features can be noted:</P>
<UL>
@@ -311,7 +307,7 @@ compatible way. The main problem of this approach is that
applications written using wxGTK should work with relatively old
versions of GTK+ but should also make use of recent features. In some
cases, supporting an old version of GTK+ hinders development so we
decided to declare GTK+ 2.4 the minimum toolkit version that is
decided to declare GTK+ 2.6 the minimum toolkit version that is
supported. As an example, this made it possible to always use the
GTK+ file dialog instead of the old generic file dialog which had to
be used when GTK+ didn't have a usable file dialog.

View File

@@ -1,13 +1,15 @@
October 7, 2013 -- The wxWidgets team is pleased to announce the
first release candidate release of wxWidgets 3.0.
November 11, 2013 -- The wxWidgets team is pleased to announce a
major new release of our open source framework for the development
of native cross-platform applications in C++.
wxWidgets 3.0-RC1 is available at
wxWidgets 3.0.0 is the first release in the new major stable 3.0
branch and is available at
https://sourceforge.net/downloads/wxwindows/3.0.0-rc1/
https://sourceforge.net/downloads/wxwindows/3.0.0/
and at our FTP mirror at
ftp://ftp.wxwidgets.org/pub/3.0.0-rc1/
ftp://ftp.wxwidgets.org/pub/3.0.0/
Please choose the archive format suitable for your platform, i.e. 7z
or ZIP for Windows platforms and tar.bz2 for the Unix systems
@@ -22,9 +24,6 @@ selected compilers at
https://sourceforge.net/downloads/wxwindows/3.0.0/binaries/
Notice that 3.0-RC1 does NOT include the binaries, they will be only
available for the final 3.0 release.
Please see the README file there for the descriptions of the
individual files.
@@ -44,20 +43,20 @@ here, but the most important ones are:
Please see the changes.txt file in the "docs" subdirectory of
wxWidgets distribution or also available online at
https://sourceforge.net/projects/wxwindows/files/3.0.0-rc1/changes.txt
https://sourceforge.net/projects/wxwindows/files/3.0.0/changes.txt
for more details and please read the "INCOMPATIBLE CHANGES" section
in its beginning for a brief description of changes if you are
upgrading from wxWidgets 2.8. For more details, please see
http://docs.wxwidgets.org/3.0.0/overview_changes_since28.html
Please test this release candidate version to help us with making the
final 3.0 release as problem-free as possible. We are especially
looking forward to your feedback about the changes in this release
compared to 2.8 version if you're upgrading. Please let us know about
any regressions (http://trac.wxwidgets.org/newticket) so that we could
fix them in the upcoming 3.0.
We recommend that you use wxWidgets 3.0 for any new programs and
also update any existing code using the older versions to the new
one (which should be easier than the jump in the version number
indicates) as all the future development will only happen in 3.x
series.
Thanks in advance!
We hope that you will enjoy using the new release!
Vadim Zeitlin, on behalf of wxWidgets development team.