diff --git a/docs/html/faq.htm b/docs/html/faq.htm
index dc7bbb8f35..7c9721c4c9 100644
--- a/docs/html/faq.htm
+++ b/docs/html/faq.htm
@@ -1,45 +1,48 @@
+
-
+
+wxWindows 2 FAQ
+
-
-wxWindows 2 FAQ
-
+
-
-
-
+
-
+
-Welcome to the wxWindows FAQ. Please select a category:
+Welcome to the wxWindows FAQ. Please select a category:
-
+
-For further information, please see the wxWindows Web site,
-plus install.txt (per port), todo.txt (per port), and bugs.txt (all ports).
-
+For further information, please see the
+wxWindows Web site,
+wxWiki
+and install.txt (per port), todo.txt (per port), and bugs.txt (all ports) files
+in your wxWindows installation.
+
-
+
-
+
diff --git a/docs/html/faqgen.htm b/docs/html/faqgen.htm
index 43776e0578..f75ce4688e 100644
--- a/docs/html/faqgen.htm
+++ b/docs/html/faqgen.htm
@@ -1,3 +1,4 @@
+
@@ -25,15 +26,18 @@ See also top-level FAQ page.
List of questions in this category
- What is wxWindows?
+- Can I use wxWindows 2 for both proprietary projects, and GPL'ed projects?
+- Is there support?
- Who uses wxWindows?
-- What platforms are supported by wxWindows 2?
-- How does wxWindows 2 support platform-specific features?
+- What platforms are supported by wxWindows?
+- How does wxWindows support platform-specific features?
- Does wxWindows use STL? or the standard string class?
-- Is there a rich edit/markup widget for wxWindows 2? li>
+
- Is there a rich edit/markup widget for wxWindows? li>
- How to use C++ exceptions with wxWindows? li>
-
- How is wxWindows 2 being developed?
-- How is wxWindows 2 distributed?
+- How is wxWindows being developed?
+- How is wxWindows distributed?
- What are the plans for the future?
+- What is wxBase?
- What is wxUniversal?
- What about Java?
- How can I help the project?
@@ -54,7 +58,7 @@ You don't have to use C++ to use wxWindows: there is a Perl interface.
-
Can I use wxWindows 2 for both proprietary (commercial) projects, and GPL'ed projects?
+
Yes. Please see the licence for details, but basically
you can distribute proprietary binaries without distributing any source code, and neither will wxWindows
@@ -64,7 +68,7 @@ The conditions for using wxWindows 2 are the same whether you are a personal, ac
or commercial developer.
-
Is there support?
+
No official support, but the mailing list is very helpful and some people say that
wxWindows support is better than for much commercial software. The developers are
@@ -81,6 +85,9 @@ quite large for a list of this type.
See Users for a list of some users and their applications, and
also Feedback for comments.
+Our highest-profile user yet is industry veteran and Lotus Corp. founder Mitch Kapor
+and his Open Source Applications Foundation.
+
@@ -159,10 +166,9 @@ or by adding this to a header before you include any STL files:
These are the possibilities so far:
-- The richedit sample has a text editor that does markup.
- See www.scintilla.org for
-a very nice syntax-highlighting editor widget. Robin Dunn is writing a wxWindows wrapper
-for this widget.
+a very nice syntax-highlighting editor widget. Robin Dunn has written a wxWindows wrapper
+for this widget, available in the wxWindows distribution under contrib/src/stc.
- If you only need to display marked-up information, rather than edit it,
then wxHTML will suit your needs. wxHTML is built into wxWindows - please see the reference
manual for details, and samples/html.
@@ -200,29 +206,29 @@ There are a few issues to keep in mind, though:
-
+
We are using the CVS system to develop and maintain wxWindows. This allows
-us to make alterations and upload them instantly to the SourceForge server, from
+us to make alterations and upload them instantly to the server, from
which others can update their source.
To build source from CVS, see the file BuildCVS.txt in the top-level wxWindows distribution
directory.
-
+
By ftp, and via the wxWindows CD-ROM.
If you are feeling adventurous, you may also check out the sources directly
-from the cvs
+from cvs.
-Currently we're working too hard on getting wxWindows 2 finished (are GUI toolkits ever
+Currently we're working too hard on getting wxWindows finished (are GUI toolkits ever
finished?) to think very far ahead. However, we know we want to make wxWindows as robust
and well-publicised as possible. We also want to aim for better platform-independence of
-resources such as icons and bitmaps, standardising on the PNG for all platforms.
+resources such as icons and bitmaps, standardising on PNG and XPM for all platforms.
Other possibilities include: DCOM/CORBA compatibility; a wxWindows book;
wxWorkshop, an IDE;
@@ -234,12 +240,24 @@ their product.
The high-level goal of wxWindows is to be thought of as the number one C++ framework,
for virtually any platform. Move over, MFC!
+
+
+wxBase is a subset of wxWindows comprised by the non-GUI classes. It includes
+wxWindows container and primitive data type classes (including wxString,
+wxDateTime and so on) and also useful wrappers for the operating system objects
+such as files, processes, threads, sockets and so on. With very minor
+exceptions wxBase may be used in exactly the same way as wxWindows but it
+doesn't require a GUI to run and so is ideal for creating console mode
+utilities or server programs. It is also possible to create a program which can
+be compiled either as a console application (using wxBase) or a GUI one (using
+a full featured wxWindows port).
+
-wxUniversal is a new port of wxWindows being currently actively developed. The
-main difference is that wxUniversal implements all controls (or widgets) in
-wxWindows itself thus allowing to have much more flexibility (i.e. support for
-themes even under MS Windows!). It also means that it is now much easier to
+The main difference between wxUniversal-based ports (such as wxX11, wxMGL) and other ports (such as wxMSW, wxGTK+, wxMac)
+is that wxUniversal implements all controls (or widgets) in
+wxWindows itself thus allowing to have much more flexibility (for example, support for
+themes even under MS Windows). It also means that it is now much easier to
port wxWindows to a new platform as only the low-level classes must be ported
which make for a small part of the library.
@@ -255,7 +273,7 @@ from Java, and the level of interest in wxWindows is as high as ever.
Please check out the Community pages,
in particular the suggested projects, and
-mail Julian Smart or the developers' mailing list with your own suggestions.
+mail the developers' mailing list with your own suggestions.
diff --git a/docs/html/faqmsw.htm b/docs/html/faqmsw.htm
index 2c56fedb31..346e9de28d 100644
--- a/docs/html/faqmsw.htm
+++ b/docs/html/faqmsw.htm
@@ -1,3 +1,4 @@
+
@@ -201,7 +202,8 @@ Statically-linked wxWindows 2 programs are smaller than wxWindows 1.xx programs,
wxWindows 2 has been designed to reduce dependencies between classes, and other
techniques. The linker will not include code from the library that is not (directly or
indirectly) referenced
-by your application. So for example, the 'minimal' sample is less than 300KB using VC++ 6.
+by your application. So for example, the 'minimal' sample is less than 500KB using VC++ 6
+(note that this figure may be greater for the latest version of wxWindows).
If you want to distribute really small executables, you can
use Petite
@@ -210,6 +212,12 @@ will shrink to a mere 250KB. With this sort of size, there is reduced incentive
use DLLs. Another good compression tool is UPX.
+Please do not be surprised if MinGW produces a statically-linked minimal executable of 1 MB. Firstly, gcc
+produces larger executables than some compilers. Secondly, this figure will
+include most of the overhead of wxWindows, so as your application becomes more
+complex, the overhead becomes proportionaly less significant. And thirdly, trading executable compactness
+for the enormous increase in productivity you get with wxWindows is almost always well worth it.
+
There is a sample which demonstrates MFC and wxWindows code co-existing in the same
@@ -392,7 +400,11 @@ VZ
This can happen if you have a child window intercepting EVT_CHAR events and swallowing
all keyboard input. You should ensure that event.Skip() is called for all input that
-isn'used by the event handler.
+isn'used by the event handler.
+
+It can also happen if you append the submenu to the parent
+menu {\it before} you have added your menu items. Do the append {\it after} adding
+your items, or accelerators may not be registered properly.
@@ -414,7 +426,7 @@ First, you can use wxRegKey directly, for example:
regKey.SetName(idName);
{
- wxLogNull dummy;
+ wxLogNull dummy;
if (!regKey.Create())
{
idName = wxT("HKEY_CURRENT_USER\\SOFTWARE\\My Company\\My Product\\Stuff\\");
diff --git a/docs/html/i18n.htm b/docs/html/i18n.htm
index b5fa8b7dd9..a82dd9277c 100644
--- a/docs/html/i18n.htm
+++ b/docs/html/i18n.htm
@@ -124,6 +124,13 @@ translations as of wxWindows 2.3.
+
+ Greek |
+  |
+ Tsolakos Stavros
+ |
+
+
Hungarian |
 |
@@ -131,6 +138,14 @@ translations as of wxWindows 2.3.
+
+ Indonesian |
+  |
+
+ Bambang Purnomosidi D. P.
+ |
+
+
Italian |
 |
@@ -157,6 +172,7 @@ translations as of wxWindows 2.3.
 |
Roman Rolinsky,
Vadim Zeitlin
+ Andrew V. Samoilov
|
@@ -179,6 +195,13 @@ translations as of wxWindows 2.3.
Kaj G Backas
+
+ Turkish |
+  |
+ Hakki Dogusan |
+
+
+
@@ -196,15 +219,14 @@ translations. Here are the the steps you should follow:
- Get the latest version of the file locale/wxstd.po from the
wxWindows source tree: if you're using cvs
- or the daily
- snapshots, you should already have it. Otherwise you can always
+ or the daily snapshots,
+ you should already have it. Otherwise you can always
retrieve it directly from the cvs repository via the Web interface
-
- here.
+ here.
- Rename it to XY.po where "XY" is the 2 letter
-
- ISO country code for your language.
+ ISO 639-1 language code
+ for your language.
- Translate the strings in this file using either your favourite text
editor or a specialized tool such as Vaclav Slavik's excellent
diff --git a/docs/html/platform.htm b/docs/html/platform.htm
index cb2e2d6feb..46ef6cbc89 100644
--- a/docs/html/platform.htm
+++ b/docs/html/platform.htm
@@ -1,6 +1,6 @@
- Platforms supported by wxWindows 2.x
+ Platforms supported by wxWindows 2.4
@@ -20,10 +20,11 @@
-You will find below the list of all supported platforms for different ports of wxWindows 2.x (wxMSW/wxGTK/wxMotif ports
-only). The cross icon in the third column doesn't mean that the platform is not supported, but just that wxWindows hasn't
-been tested on it recently (the table is being updated for wxWindows 2.3.3
-currently).
+You will find below the list of all supported platforms for different ports of
+wxWindows 2.x (wxMSW/wxGTK/wxMotif ports only). The cross icon in the third
+column doesn't mean that the platform is not supported, but just that
+wxWindows hasn't been tested on it recently (the table is being updated for
+wxWindows 2.4.0 currently).
See also:
@@ -86,9 +87,20 @@ often don't work.
wxMotif with gcc 2.95 |  |
| with OpenMotif |
+
| All BSD systems tests are for wxGTK using gcc. |
FreeBSD |
- wxGTK with gcc |  | VZ | Limited thread support on older systems |
+ version from 3.2 to 4.6, x86 |  | VZ |
|
+
+
+
+NetBSD |
+ 1.6, Alpha |  | VZ |
|
+
+
+
+OpenBSD |
+ 3.1, Alpha |  | VZ | Some problems with shared libraries, ok with static ones |
diff --git a/wxwin.m4 b/wxwin.m4
index b5959a3383..e567af0914 100644
--- a/wxwin.m4
+++ b/wxwin.m4
@@ -7,7 +7,7 @@ dnl ...
dnl AM_OPTIONS_WXCONFIG
dnl ...
dnl ...
-dnl AM_PATH_WXCONFIG(2.3.3, wxWin=1)
+dnl AM_PATH_WXCONFIG(2.3.4, wxWin=1)
dnl if test "$wxWin" != 1; then
dnl AC_MSG_ERROR([
dnl wxWindows must be installed on your system
@@ -16,7 +16,7 @@ dnl
dnl Please check that wx-config is in path, the directory
dnl where wxWindows libraries are installed (returned by
dnl 'wx-config --libs' command) is in LD_LIBRARY_PATH or
-dnl equivalent variable and wxWindows version is 2.3.3 or above.
+dnl equivalent variable and wxWindows version is 2.3.4 or above.
dnl ])
dnl fi
dnl CPPFLAGS="$CPPFLAGS $WX_CPPFLAGS"