-You don't have to use C++ to use wxWidgets: there is a Python interface for wxWidgets 2, +You don't have to use C++ to use wxWidgets: there is a Python interface for wxWidgets, and also a Perl interface.
-
-The conditions for using wxWidgets 2 are the same whether you are a personal, academic +The conditions for using wxWidgets are the same whether you are a personal, academic or commercial developer.
@@ -91,7 +94,7 @@ Our highest-profile user yet is industry veteran and Lotus Corp. founder Mitch K and his Open Source Applications Foundation.
-
-
Currently resources such as bitmaps and icons are handled in a platform-specific way, but it is hoped to reduce this dependence in due course.
-Another reason why wxWidgets 2 is not a 'lowest common denominator' toolkit is that +Another reason why wxWidgets is not a 'lowest common denominator' toolkit is that some functionality missing on some platform has been provided using generic, platform-independent code, such as the wxTreeCtrl and wxListCtrl classes.
@@ -142,7 +145,7 @@ templates adequately so it would dramatically reduce the number of compilers and platforms that could be supported. It would also be undesirable to make wxWidgets dependent on another large library that may have to be downloaded and installed. In addition, use of templates can lead to executable bloat, which is something -wxWidgets 2 is strenuously trying to avoid.
+wxWidgets is strenuously trying to avoid.
The standard C++ string class is not used, again because it is not available to all compilers, and it is not necessarily a very efficient implementation. Also, we retain more flexibility @@ -163,7 +166,7 @@ or by adding this to a header before you include any STL files:
-
@@ -225,22 +228,14 @@ If you are feeling adventurous, you may also check out the sources directly from cvs.
+
-See also top-level FAQ page +See also top-level FAQ page and Unix FAQ page.
diff --git a/docs/html/faqmac.htm b/docs/html/faqmac.htm index 6c053adb95..eb10289a07 100644 --- a/docs/html/faqmac.htm +++ b/docs/html/faqmac.htm @@ -2,7 +2,7 @@
-The author of this port is Stefan Csomor.
-A Mac OS X port is in progress in order to be able to build wxWidgets applications using the Apple Developer Tools that are delivered with every copy of Mac OS X. -The Mac OS X port is based on and, for the most part, merged with the Carbon code for Classic Mac OS. -
- -
-This hybrid approach was suggested by Apple to the Fizzilla team working on Mozilla for Mac OS X. -
- -
-The following points should be considered when improving wxMac: -
Under Mac OS X, the Developer Tools are sufficient to build wxMac. CodeWarrior Pro 6 can also be used to build the Carbon targets.
+
+ +
+I got it to work. I removed the original wxMac build-release folder +and recompiled wxMac following instructions in your book. I then ran +"sudo make install" which I didn't do the first time. I figured I +could now run wx-config --cxxflags from my home directory because +/usr/local/bin/wx-config was in my $PATH. However, OSX 10.4 installed +a version of wxWidgets. When I ran wx-config I was getting wx 2.5 +libs instead of the 2.6.1 libs I just compiled. When I ran +"/usr/local/bin/wx-config --cxxflags" and "/usr/local/bin/wx-config --libs" +and pasted that output into XCode preferences, everything worked fine. ++
+
xpm and xbm images correctly:
@@ -106,6 +104,7 @@ All files checked out under Mac OS X will be untyped and CodeWarrior will not re
+
+wxWidgets can be used to develop and deliver applications on Windows 95, Windows 98, Windows NT, +Windows 2000, Windows XP, and Windows Vista. A Windows CE +port is also available (see below).
-wxWidgets 2 is designed to make use of WIN32 features and controls. However, unlike Microsoft, -we have not forgotten users of 16-bit Windows. Most features -work under Windows 3.1, including wxTreeCtrl and wxListCtrl using the generic implementation. -However, don't expect very Windows-95-specific classes to work, such as wxTaskBarIcon. The wxRegConfig -class doesn't work either because the Windows 3.1 registry is very simplistic. Check out the 16-bit -makefiles to see what other files have been left out. -
-16-bit compilation is supported under Visual C++ 1.5, and Borland BC++ 4 to 5. +16-bit compilation is only supported for wxWidgets 2.4 and previous versions, +using Visual C++ 1.5 and Borland BC++ 4 to 5.
-wxWidgets 2 for Windows will also compile on Unix with gcc using Wine from WineHQ. +wxWidgets for Windows will also compile on Unix with gcc using Wine from WineHQ. The resulting executables are Unix binaries that work with the Wine Windows API emulator.
-You can also compile wxWidgets 2 for Windows on Unix with Cygwin or Mingw32, resulting +You can also compile wxWidgets for Windows on Unix with Cygwin or Mingw32, resulting in executables that will run on Windows. So in theory you could write your applications using wxGTK or wxMotif, then check/debug your wxWidgets for Windows programs with Wine, and finally produce an ix86 Windows executable using Cygwin/Mingw32, @@ -78,10 +73,19 @@ without ever needing a copy of Microsoft Windows. See the Technical Note on the
+This port supports Pocket PC 2002/2003 and MS Smartphone 2002/2003, using +Embedded Visual C++ 3 or 4. For further information, see the wxMSW section in +the wxWidgets Reference Manual, and also the wxEmbedded page.
+ +For versions of wxWidgets below 2.5, you need to provide the manifest +explicitly, as follows.
+ In the same directory as you have your executable (e.g. foo.exe) you put a file called foo.exe.manifest in which you have something like the following: @@ -119,10 +123,6 @@ line:
1 24 "winxp.manifest" -In wxWidgets 2.5, this will be in the wx/msw/wx.rc and -so will happen automatically so long as you include wx.rc -in your own .rc file.
- For an explanation of this syntax, please see this article. @@ -130,7 +130,7 @@ article
-
@@ -170,7 +170,8 @@ Watcom C++ is a little slow and the debugger is not really up to today's sta Among the free compilers the best choice seem to be Borland C++ command line tools and mingw32 (port of gcc to Win32). Both of them are supported by -wxWidgets. +wxWidgets. However BC++ has trouble compiling large executables statically, +so you need to dynamically link the wxWidgets libraries.
-
-lib/mswd
+lib/vc_lib/mswd
-or if building the static Release library, lib/msw.
+or if building the static Release library, lib/vc_lib/msw.
See also the wxWiki Contents for more information.
@@ -323,13 +324,12 @@ Code' (and no others). This will then work.
+is described in technical note 16 under docs/tech in your distribution.
-As of wxWidgets 2.1, there is a new system written by Vadim Zeitlin, that +For 2.4.x, there is a system written by Vadim Zeitlin that generates the makefiles from templates using tmake.
-Here are Vadim's notes:
+Here are Vadim's notes on tmake:
To use these new makefiles, you don't need anything (but see below). @@ -341,7 +341,7 @@ example) and regenerate the makefile using tmake.diff --git a/docs/html/faqx11.htm b/docs/html/faqx11.htm index 7ebaf3f5a0..5a7b005a54 100644 --- a/docs/html/faqx11.htm +++ b/docs/html/faqx11.htm @@ -2,7 +2,7 @@ -tmake can be found at www.troll.no/freebies/tmake.html. -It's a Perl5 program and so it needs Perl (doh). There is a binary for +It's a Perl5 program and so it needs Perl (doh). There is a binary for Windows (available from the same page), but I haven't used it, so I don't know if it works as flawlessly as "perl tmake" does (note for people knowing Perl: don't try to run tmake with -w, it won't @@ -350,7 +350,7 @@ just go to distrib/msw/tmake and type
tmake -t b32 wxwin.pro -o ../../src/msw/makefile.b32-The makefiles are untested - I don't have any of Borland, Watcom or +The makefiles are untested - I don't have any of Borland, Watcom or Symantec and I don't have enough diskspace to recompile even with VC6 using makefiles. The new makefiles are as close as possible to the old ones, but not closer: in fact, there has been many strange things @@ -457,7 +457,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\\"); @@ -542,7 +542,7 @@ slightly smaller and faster. But the most important thing is to use the same CRT setting for all components of your project. -
Why do I get compilation erros when using wxWidgets with DirectShow?
+Why do I get compilation errors when using wxWidgets with DirectShow?
If you get errors when including Microsoft DirectShow or DirectDraw headers, the following message from Peter Whaite could help: @@ -554,9 +554,9 @@ the following message from Peter Whaite could help: The reason for this is that __WXDEBUG__ is also used by the DXSDK (9.0 in my case) to '#pragma once' the contents of -DXSDK/Samples/C++/DirectShow/BaseClasses/wxdebug.h. So if __WXDEBUG__ +DXSDK/Samples/C++/DirectShow/BaseClasses/wxdebug.h. So if __WXDEBUG__ is defined, then wxdebug.h doesn't get included, and the assert macros -don't get defined. You have to #undef __WXDEBUG__ before including the +don't get defined. You have to #undef __WXDEBUG__ before including the directshow baseclass's <streams.h>.