Fixes to allow compilation with no wchar_t (djgpp probably has a real wchar_t

[wxWidgets.git] / docs / readme.txt

diff --git a/docs/readme.txt b/docs/readme.txt
index 8fc4fa3dcb88622c2a8a62e1c4f16325d871e0ac..1940621586c142c1c85db67592d8a124aa539239 100644 (file)
--- a/docs/readme.txt
+++ b/docs/readme.txt
@@ -1,17 +1,9 @@
-wxWidgets 2.5.5
----------------
-
-*** Please note that this is an UNSTABLE DEVELOPMENT SNAPSHOT.
-*** Unless you need the new features and bug fixes, you may wish to
-*** use the official 2.4.x stable series. You are still encouraged
-*** to try the releases from 2.5.x branch, of course, and unstable
-*** doesn't mean that they crash all the time -- just that the API
-*** may change in a backwards incompatible way. If this doesn't frighten
-*** you, do try this release and please let us know what you think!
+wxWidgets 2.6.0
+---------------------------------------------------------

 
 Welcome to wxWidgets, a sophisticated cross-platform C++
 
 Welcome to wxWidgets, a sophisticated cross-platform C++

-framework for writing advanced GUI applications using (where
-possible) the native controls.
+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,
 
 In addition to common and advanced GUI facilities such as
 frames, scrolling windows, toolbars, tree controls, icons,


@@ -21,7 +13,7 @@ TCP/IP applications, thread handling, and more. Where certain
 features are not available on a platform, such as MDI and tree
 controls on Unix, they are emulated.
 
 features are not available on a platform, such as MDI and tree
 controls on Unix, they are emulated.
 

-A detailed 1800-page reference manual is supplied in HTML, PDF
+A detailed 2000-page reference manual is supplied in HTML, PDF

 and Windows Help form: see the docs hierarchy.
 
 For a quick start, point your Web browser at docs/html/index.htm
 and Windows Help form: see the docs hierarchy.
 
 For a quick start, point your Web browser at docs/html/index.htm


@@ -30,25 +22,32 @@ for a list of important documents and samples.
 Changes in this release
 -----------------------
 
 Changes in this release
 -----------------------
 

-Please see changes.txt for details.
+Please see changes.txt and "Changes since 2.4" in the manual
+for details.

 
 Platforms supported
 -------------------
 
 wxWidgets currently supports the following platforms:
 
 
 Platforms supported
 -------------------
 
 wxWidgets currently supports the following platforms:
 

-- Windows 95/98/ME, Windows NT, Windows 2000, Windows XP, Pocket PC
+- Windows 95/98/ME, Windows NT, Windows 2000, Windows XP,
+  Pocket PC, Smartphone

 - Most Unix variants with GTK+ 1 and GTK+ 2
 - Most Unix variants with X11 (beta)
 - Most Unix variants with Motif/Lesstif
 - MacOS 9.x and 10.x using Carbon (10.3 and above preferred)
 - MacOS 10.x using Cocoa (beta)
 - OS/2 (beta)
 - Most Unix variants with GTK+ 1 and GTK+ 2
 - Most Unix variants with X11 (beta)
 - Most Unix variants with Motif/Lesstif
 - MacOS 9.x and 10.x using Carbon (10.3 and above preferred)
 - MacOS 10.x using Cocoa (beta)
 - OS/2 (beta)

+- PalmOS (alpha)

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

+The 2.6 series is the last to fully support GTK+ 1.2, and Mac OS
+9/Mac OS 10.2 and below. wxWidgets 2.7 and above will focus on
+GTK+ 2, and Mac OS 10.3 and above.
+

 Files
 -----
 
 Files
 -----
 


@@ -70,6 +69,7 @@ see the install.txt file in the individual directories:
   docs/x11
   docs/mgl
   docs/os2
   docs/x11
   docs/mgl
   docs/os2

+  docs/palmos

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


@@ -83,35 +83,37 @@ For licensing information, please see the files:
   docs/lgpl.txt
 
 Although this may seem complex, it is there to allow authors of
   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 compiled with --enable-odbc (Unix only), wxWidgets library will 
-contain iODBC library which is covered by LGPL.
+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 compiled with --enable-odbc (Unix
+only), wxWidgets library will contain iODBC library which is
+covered by LGPL.

 
 If you use TIFF image handler, please see src/tiff/COPYRIGHT
 for libtiff licence details.
 
 
 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 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 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.
 
 
 If you use wxXML classes or XRC, see src/expat/COPYING for licence details.
 


@@ -128,8 +130,10 @@ The wxWidgets bug database can be browsed at:
 
   http://sourceforge.net/bugs/?group_id=9863
 
 
   http://sourceforge.net/bugs/?group_id=9863
 

-The Windows help files are located in docs/winhelp.
+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 PDF help files are located in docs/pdf.

+The HTB (wxWidgets HTML Help) files are located in docs/htb.

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