Update release notes etc for 3.1.3 release

Also simplify MSVC binaries use instructions by instructing people to
just use the provided properties file.

Author: vadz

docs/contributing/how-to-release.md

@@ -50,6 +50,15 @@ and then run it using the new DLLs.
    the straightforward changes like updating the date and version number
    automatically, but please also review and update the contents of the README
    and announcement text.
+
+   Note that the best order depends on the release being prepared: for a
+   development release, `docs/publicity/announce.txt` contains the list of the
+   major changes since the last stable release and should be updated first, as
+   this part of it can then be copied verbatim to the corresponding section of
+   the README file. For the stable releases, it's probably more convenient to
+   update the README with the details of the changes first.
+
+   Here is the list of the files, for reference:
     * Update `docs/readme.txt`: version needs to be changed, content updated.
     * Update `docs/release.md`: also version and reset SHA-1 sums to zeroes.
     * Put a date on the release line in `docs/changes.txt`.

docs/doxygen/mainpages/manual.h

@@ -14,7 +14,7 @@
 @author Julian Smart, Vadim Zeitlin, Robin Dunn, Stefan Csomor,
         Bryan Petty, Francesco Montorsi, Robert Roebling et al
 
-@date December 10, 2018
+@date October 28, 2019
 
 Welcome to wxWidgets, a stable and powerful open source framework for
 developing native cross-platform GUI applications in C++!

docs/msw/binaries.md

@@ -8,7 +8,7 @@ Supported Compilers
 We provide pre-built binary files for the following compilers:
 
 * Microsoft Visual C++ compiler versions 9.0, 10.0, 11.0, 12.0, 14.0, 14.1 and 14.2
-  (corresponding to marketing product names of Microsoft Visual Studio 2008, 2010, 2012, 2013, 2015, 2017 and 2019 respectively).
+  (corresponding to marketing product names of Microsoft Visual Studio 2008, 2010, 2012, 2013, 2015, 2017 and 2019 respectively). Please note that MSVC 14.x versions are ABI-compatible and the same set of binaries is used for all of them.
 * TDM-GCC version 5.1 and MinGW-w64 version 7.2 (with the default SJLJ
   exceptions propagation method, using C++11). Please note that you need to use
   the very latest MinGW-w64 7.2 compiler release with this version of the
@@ -24,7 +24,7 @@ Getting the files
 -----------------
 
 First, you need to get the correct files. You will always need the
-`wxWidgets-3.1.1-headers.7z` one but the rest depends on your compiler version
+`wxWidgets-3.1.3-headers.7z` one but the rest depends on your compiler version
 and architecture: as different versions of MSVC compiler are not binary
 compatible, you should select the files with the correct
 `vc80`, `vc90`, `vc100`, `vc110`, `vc120`, or `vc14x`
@@ -35,14 +35,14 @@ or the ones without this suffix for the still more common 32-bit builds. After
 determining the combination of suffixes you need, you should download the
 "Dev" and the "ReleaseDLL" files in addition to the "Headers" one above,
 e.g. for 32-bit MSVS 2017 development you need
-`wxMSW-3.1.1_vc14x_Dev.7z` and `wxMSW-3.1.1_vc14x_ReleaseDLL.7z`.
+`wxMSW-3.1.3_vc14x_Dev.7z` and `wxMSW-3.1.3_vc14x_ReleaseDLL.7z`.
 
 All binaries are available at:
 
-https://github.com/wxWidgets/wxWidgets/releases/v3.1.1
+https://github.com/wxWidgets/wxWidgets/releases/v3.1.3
 
 Once you have the files you need, unzip all of them into the same directory, for
-example `c:\wx\3.1.1`. You should have only include and lib subdirectories under
+example `c:\wx\3.1.3`. You should have only include and lib subdirectories under
 it, nothing else. To avoid hard-coding this path into your projects, define
 `wxwin` environment variable containing it: although it's a little known fact,
 all versions of MSVC support environment variable expansion in the C++ projects
@@ -51,42 +51,16 @@ all versions of MSVC support environment variable expansion in the C++ projects
 Using Binaries with Visual Studio
 ---------------------------------
 
-Next step is to set up your project to use these files. You need to do the
-following:
+Next step is to set up your project to use these files: for this, simply add
+the provided `wxwidgets.props` file as a property sheet to your project.
+This can be done using `View|Property Manager` menu item in the IDE and
+selecting "Add Existing Property Sheet..." from the project popup menu.
 
-*   In the compiler options, i.e. "C/C++" properties:
-    *   Add `$``(wxwin)/include/msvc;$``(wxwin)/include` to the "Additional Include
-        Directories". Notice that the order is important here, putting the
-        MSVC-specific directory first ensures that you use `wx/setup.h`
-        automatically linking in wxWidgets libraries.
-    *   Add `WXUSINGDLL` and `wxMSVC_VERSION_ABI_COMPAT` to the list of defined
-        symbols in "Preprocessor Definitions". The first should be
-        self-explanatory (we only provide DLLs, not static libraries) while the
-        second one is necessary to use the libraries from e.g. `lib\vc100_dll`
-        directory and not the default `lib\vc_dll`.
-    *   Also check that `_UNICODE` and `UNICODE` symbols are defined in the same
-        "Preprocessor Definitions" section. This should already be the case for
-        the newly created projects but it might be necessary to add them if
-        you're upgrading an existing one.
-    *   Check that you use "Multi-threaded \[Debug\] DLL" in the "Run-time
-        library" option under "Code Generation" to ensure that your build uses
-        the same CRT version as our binaries.
-* In the linker options you only need to add `$``(wxwin)\lib\vc$``(PlatformToolsetVersion)_dll`
-  (the standard `PlatformToolsetVersion` macro expands into something like
-  `141`, depending on the toolset version being used, and you could also use
-  the version number directly if you prefer) to "Additional Library
-  Directories" under "Linker\\General" in the options. Thanks to the use of
-  MSVC-specific `setup.h` you don't need to list wxWidgets libraries manually,
-  i.e. you do **not** need to put anything in the list of "Additional
-  Dependencies".
+Note: your project must use "Unicode Character Set" option.
 
-Now you should be able to build your project successfully, both in "Debug" and
-"Release" configurations. With MSVS 10 or newer it can also be done from the
-command line using `msbuild.exe`. Of course, to run the generated executable
-you will need to either add the directory containing wxWidgets DLLs to your PATH
-or copy the DLL files to a directory already on it. Finally, if you want to
-distribute the binaries created using these options, you will need to install
-Microsoft Visual C++ run-time DLLs. Again, MSVC 10 or newer has an advantage
-here as you can simply copy `msvcp100.dll` and `msvcr100.dll` as any other DLL,
-while you need to install specially for the previous compiler versions that
-use WinSxS ("side-by-side") for them.
+Now you should be able to build and run your project successfully, both in
+"Debug" and "Release" configurations. Please note that during run-time the
+executables will require wxWidgets DLLs in addition to MSVC run-time DLLs, so
+you should consider adding the directory containing these DLLs to your PATH and
+either distributing them with your application or instructing your users to
+download them.

docs/publicity/announce.txt

@@ -1,29 +1,31 @@
-December 10, 2018 -- The wxWidgets team is pleased to announce a new
+October 28, 2019 -- The wxWidgets team is pleased to announce a new
 release of our open source framework for the development of native
 cross-platform applications in C++.
 
-wxWidgets 3.1.2 is the latest release in the 3.1 development
+wxWidgets 3.1.3 is the latest release in the 3.1 development
 branch and is now available at
 
-    https://github.com/wxWidgets/wxWidgets/releases/tag/v3.1.2
+    https://github.com/wxWidgets/wxWidgets/releases/tag/v3.1.3
 
 Compared to the stable 3.0.x series, this version brings many
 improvements and even more bug fixes, please see the change log
 
-https://raw.githubusercontent.com/wxWidgets/wxWidgets/v3.1.2/docs/changes.txt
+https://raw.githubusercontent.com/wxWidgets/wxWidgets/v3.1.3/docs/changes.txt
 
 for the incomplete list of the most important ones. Here is the
 maximally condensed summary of the changes compared to 3.0:
 
-- Build system improvements: support for new compilers (MSVS 2017, g++ 8) and
-  OS versions (macOS 10.14 and its dark mode) as well as an entirely new CMake
-  build system.
-- New features: support for mouse gesture events (GSoC 2017 project);
-  non-integer font sizes and arbitrary font weights in wxFont; fractional pen
-  widths in wxGraphicsContext; arbitrary label windows in wxStaticBox; markup
-  in wxDataViewCtrl items text; better support for high DPI monitors; support
-  for ZIP 64 files; LZMA compression; much improved accessibility support under
-  MSW.
+- Build system improvements: support for new compilers (up to MSVS 2019, g++ 9)
+  with an even simpler way of using wxWidgets from MSVS, with wxwidgets.props
+  file, and OS versions as well as an entirely new CMake build system.
+- Support for native dark mode under macOS 10.14 Mojave and later.
+- New features: implement freezing rows/columns in wxGrid; support for mouse
+  gesture events (GSoC 2017 project); non-integer font sizes and arbitrary font
+  weights in wxFont; fractional pen widths in wxGraphicsContext; arbitrary
+  label windows in wxStaticBox; markup in wxDataViewCtrl items text; better
+  support for high DPI monitors and per-monitor DPI and dynamic DPI changes
+  support under MSW; support for ZIP 64 files; LZMA compression; much improved
+  accessibility support under MSW.
 - New classes: wxActivityIndicator, wxAddRemoveCtrl,
   wxAppProgressIndicator, wxNativeWindow, wxPowerResourceBlocker,
   wxSecretStore.
@@ -33,6 +35,8 @@ maximally condensed summary of the changes compared to 3.0:
   wxListBox::GetTopItem(), wxProcess::Activate(), wxTextEntry::ForceUpper(),
   several ones in wxRendererNative, wxStandardPaths::GetUserDir(),
   wxToolbook::EnablePage(), wxUIActionSimulator::Select() and many others.
+- New XRC handlers for wxActivityIndicator, wxAui classes, wxDataViewCtrl,
+  wxInfoBar, wxSimplebook, wxSpinCtrlDouble.
 - Significant improvements to: wxBusyInfo, wxDataViewCtrl,
   wxNotificationMessage, wxStaticBox, wxStyledTextCtrl.
 - Latest versions of all bundled 3rd party libraries, including all the

docs/readme.txt

@@ -27,11 +27,28 @@ download from:
 Changes since 3.1.2
 -------------------
 
-TODO: Fill in
+There have been almost 2000 commits from 97 unique contributors (52 with
+multiple contributions) since 3.1.2 releases, so it is impossible to summarize
+all the changes in this document without making it too long, please see the
+full changelog at
 
-Notice that this release is almost completely compatible with 3.1.2 at the API
-level, so upgrading to it if you're already using wxWidgets 3 should be
-straightforward.
+https://raw.githubusercontent.com/wxWidgets/wxWidgets/v3.1.3/docs/changes.txt
+
+for more details, but some of the most important changes are:
+
+- Support for per-monitor DPI and dynamic DPI changes under MSW.
+- More generally, many fixes for various controls appearance in high DPI.
+- Long requested support for freezing rows and/or columns in wxGrid.
+- New XRC handlers for wxDataViewCtrl, wxInfoBar.
+- It is now possible to use gradients when creating wxGraphicsPen.
+- Extended compiler (MSVS 2019) and platforms (macOS 10.14+) support.
+- Significant improvements to the (still experimental) wxQt port.
+- Important bug fixes for focus handling in wxOSX port.
+
+
+Notice that in spite of all the changes, this release remains almost completely
+compatible with 3.1.2 at the API level, so upgrading to it if you're already
+using wxWidgets 3 should be straightforward.
 
 
 Changes since 3.0
@@ -41,13 +58,16 @@ Compared to the stable 3.0.x series, this version brings too many
 improvements and even more bug fixes to list them all, but here is the
 maximally condensed summary:
 
-- Build system improvements: support for new compilers (MSVS 2017, g++ 8) and
-  OS versions as well as an entirely new CMake build system.
+- Build system improvements: support for new compilers (up to MSVS 2019, g++ 9)
+  with an even simpler way of using wxWidgets from MSVS, with wxwidgets.props
+  file, and OS versions as well as an entirely new CMake build system.
+- Support for native dark mode under macOS 10.14 Mojave and later.
 - New features: support for mouse gesture events (GSoC 2017 project);
   fractional pen widths in wxGraphicsContext; arbitrary label windows in
   wxStaticBox; markup in wxDataViewCtrl items text; better support for high DPI
   monitors; support for ZIP 64 files; much improved accessibility support under
-  MSW.
+  MSW; Support for non-integer font sizes and arbitrary font weights; LZMA
+  compression support (using liblzma)/
 - New classes: wxActivityIndicator, wxAddRemoveCtrl,
   wxAppProgressIndicator, wxNativeWindow, wxPowerResourceBlocker,
   wxSecretStore.
@@ -82,8 +102,8 @@ There is some support for the following platforms:
 * Most Unix variants with GTK+ 1.2
 * Most Unix variants with Qt 5 or newer (experimental)
 
-Most popular C++ compilers are supported; see the install.txt file for each
-platform (following the links from docs/index.htm).
+All C++ compilers in common use are supported; see the install.txt file for
+each platform (following the links from docs/index.htm).
 
 
 Files
@@ -190,4 +210,4 @@ developed by its users and your contributions to it are always welcome!
 
 Have fun!
 
-The wxWidgets Team, December 2018
+The wxWidgets Team, October 2019