From 5147354ced015fb79d5dfd54546396bf670b4dd0 Mon Sep 17 00:00:00 2001 From: Julian Smart Date: Sun, 17 Apr 2005 10:34:19 +0000 Subject: [PATCH] Doc updates git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@33695 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775 --- docs/html/faqgen.htm | 23 ++++++----- docs/html/faqgtk.htm | 7 ++-- docs/html/faqmsw.htm | 23 ++++++----- docs/html/index.htm | 89 ++++++++++++++++++++++++++++++------------ docs/html/platform.htm | 15 +++++-- docs/msw/install.txt | 48 ++++++++++++----------- docs/readme.txt | 68 ++++++++++++++++++-------------- docs/todo.txt | 7 +--- 8 files changed, 167 insertions(+), 113 deletions(-) diff --git a/docs/html/faqgen.htm b/docs/html/faqgen.htm index 25fc5d82b4..90f2c41d1a 100644 --- a/docs/html/faqgen.htm +++ b/docs/html/faqgen.htm @@ -1,4 +1,3 @@ - @@ -54,7 +53,7 @@ so your program will take on the native 'look and feel' that users are f Although GUI applications are mostly built programmatically, there are several dialog editors to help build attractive dialogs and panels. Robert Roebling's wxDesigner -and Anthemion Software's DialogBlocks +and Anthemion Software's DialogBlocks are two commercial examples, but there are others: see the Useful Tools page.

You don't have to use C++ to use wxWidgets: there is a Python interface for wxWidgets 2, @@ -277,29 +276,29 @@ from Java, and the level of interest in wxWidgets is as high as ever.

Microsoft is spending a lot on promoting the .NET initiative, which is a set of languages, APIs and web service components for Windows. Ximian has started an open source version of .NET, mostly for Linux. -C# is Microsoft's alternative to Java, supporting 'managed code', +C# is Microsoft's alternative to Java, supporting 'managed code', garbage collection and various other Java-like language features.

Although this may be attractive to some developers, there is a variety of reasons why the .NET/Mono combination is unlikely to make wxWidgets redundant. Please note that the following comments -are Julian Smart's opinions.

+are Julian Smart's opinions.

  1. Not everyone wants or needs net services.
  2. C++ will be used for a long time to come; compared with C++, C# is a recent development and its future is not certain.
  3. Mono Forms may only target Winelib (at least to begin with), so the end result is not as native as -wxWidgets (I'm aware there is GTK# for use with the C# language). +wxWidgets (I'm aware there is GTK# for use with the C# language).
  4. C# is usually byte-compiled and therefore slower. Plus, .NET adds a layer of overhead to the client computer that wxWidgets does not require. -
  5. Mono hasn't proven its long-term viability yet (it's a complex system of components); wxWidgets is ready now. +
  6. Mono hasn't proven its long-term viability yet (it's a complex system of components); wxWidgets is ready now.
  7. You may not wish to buy into Microsoft marketing spin and APIs.
  8. Microsoft may at some point sue developers of non-Microsoft .NET implementations. After all, -platform-independence is not in Microsoft's interest. +platform-independence is not in Microsoft's interest.
  9. .NET might never be implemented on some platforms, especially Mac and embedded variants of Linux.
  10. wxPython and other language variants provide further reasons for wxWidgets to continue. -
  11. The same issue exists for Qt: if Qt sales remain strong, it's a good indication that -the market for a C++-based approach is still there. (Either that, or everyone's turning to wxWidgets!) +
  12. The same issue exists for Qt: if Qt sales remain strong, it's a good indication that +the market for a C++-based approach is still there. (Either that, or everyone's turning to wxWidgets!)
There is nothing to stop folk from developing a C# version of the wxWidgets API; @@ -322,7 +321,7 @@ has specific suggestions. Also please read the coding sta

Each port consists of a platform-specific part (e.g. src/msw, include/wx/msw), -a generic set of widgets and dialogs for when the port doesn't support +a generic set of widgets and dialogs for when the port doesn't support them natively (src/generic, include/wx/generic) and the common code that all ports use (src/common, include/wx). By browsing the source you should get a good idea of the general pattern.

@@ -335,7 +334,7 @@ Perhaps it will still save you time to clean up wxStubs, and others may benefit from this too.

You will need to define a symbol for the new port, e.g. __WXXBOX__. -Look at files such as wx/defs.h, wx/wxchar.h for areas where you'll +Look at files such as wx/defs.h, wx/wxchar.h for areas where you'll need to add to existing conditionals to set up wide character support and other issues. If the GUI runs on a Unix variant, define the __UNIX__ variable in your makefile.

@@ -357,7 +356,7 @@ wxMGL, and wxMSW/Univ for sample wxUniversal ports.

To begin with, you can use whatever makefiles or project files work for you. Look at existing makefiles to see what -generic/common/Unix files need to be included. Later, you'll want to integrate support +generic/common/Unix files need to be included. Later, you'll want to integrate support for your port into configure (Unix-like systems and gcc under Windows), and bakefile (for other makefiles on Windows).

diff --git a/docs/html/faqgtk.htm b/docs/html/faqgtk.htm index 6da8b25c07..6db64c46cb 100644 --- a/docs/html/faqgtk.htm +++ b/docs/html/faqgtk.htm @@ -1,4 +1,3 @@ - @@ -21,7 +20,7 @@

-See also top-level FAQ page +See also top-level FAQ page and Unix FAQ page.

List of questions in this category

@@ -86,13 +85,13 @@ This problem can be solved by updating GTK with an official distribution of the Robert Roebling replies:

-"The important thing is the libc version that your app +"The important thing is the libc version that your app is linked against. The most recent version is 2.2.5 and programs linked against it will not run with version 2.1.X so that you will fare best if you compile your app on a 2.1.X system. It will then run on practically all Linux distros (if you link you app statically against -the image libraries and std C++ lib)." +the image libraries and std C++ lib)."

Can I statically link the GTK+ library?

diff --git a/docs/html/faqmsw.htm b/docs/html/faqmsw.htm index 6d7a5452bf..b3c333d71f 100644 --- a/docs/html/faqmsw.htm +++ b/docs/html/faqmsw.htm @@ -1,4 +1,3 @@ - @@ -45,9 +44,9 @@ See also top-level FAQ page.
  • Why are menu hotkeys or shortcuts not working in my application?
  • Why can I not write to the HKLM part of the registry with wxRegConfig?
  • Is MS Active Accessibility supported?
    • -
  • Why does Visual C++ complain about corrupted project files{/a>
    • +
  • Why does Visual C++ complain about corrupted project files?
  • Visual C++ gives errors about multiply defined symbols, what can I do?
    • -
  • Why do I get compilation erros when using wxWidgets with DirectShow?
    • +
  • Why do I get compilation errors when using wxWidgets with DirectShow?
  • How do I handle Windows messages in my wxWidgets program?
    • @@ -342,7 +341,7 @@ example) and regenerate the makefile using tmake.

    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 @@ -351,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 @@ -458,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\\"); @@ -504,7 +503,7 @@ for the current status.

    -

    Why does Visual C++ complain about corrupted project files{/a>

    +

    Why does Visual C++ complain about corrupted project files?

    If you have downloaded the wxWidgets sources from the cvs using a Unix cvs client or downloaded a daily snapshot in .tar.gz format, it is likely @@ -543,11 +542,11 @@ 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 errors when using wxWidgets with DirectShow?

    +

    Why do I get compilation erros when using wxWidgets with DirectShow?

    If you get errors when including Microsoft DirectShow or DirectDraw headers, the following message from Peter Whaite could help: -
    +
    
 > This causes compilation errors within DirectShow:
 >
 > wxutil.h(125) : error C2065: 'EXECUTE_ASSERT' : undeclared identifier
@@ -555,11 +554,11 @@ 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>.
-
    +

    How do I handle Windows messages in my wxWidgets program?

    diff --git a/docs/html/index.htm b/docs/html/index.htm index b300673400..6a2e91d712 100644 --- a/docs/html/index.htm +++ b/docs/html/index.htm @@ -13,11 +13,11 @@ -Welcome to wxWidgets 2, the première cross-platform GUI C++ framework.

    +Welcome to wxWidgets, the première cross-platform GUI C++ framework.

    This is an index of the plain text, HTML, Windows Help and Acrobat documentation: availability depends on what you've -downloaded from the wxWidgets Web site.

    +downloaded from the wxWidgets Web site.

    @@ -25,6 +25,7 @@ downloaded from the wxWidgets Web site.Manuals] [Technical Notes] [3rd party tools] +[Optional Libraries] [Samples] [Demos] @@ -53,22 +54,24 @@ for how to do this. Further platform-specific notes: @@ -115,11 +118,6 @@ To use manuals in wxHTML Help form (extension htb), you can use the HelpView< application, either compiling it from utils/helpview in the distribution, or downloading a binary, for example from here.

    -See also the wxWidgets Tutorial -by Franky Braem, in PDF format.

    - -

    - @@ -273,6 +271,37 @@ by Franky Braem, in PDF format.

    +

    + + + +
    + +Optional Libraries + +
    + +

    + +These are the optional libraries in the contrib hierarchy.

    + +

      +
    • animate: a flip-book animation class, with animated GIF player. +
    • deprecated: deprecated classes including the old WXR resource system and property sheet classes. +
    • fl: a frame layout/docking library. +
    • foldbar: wxFoldPanel class for economical layout of controls. +
    • gizmos: a variety of GUI classes including wxDynamicSashWindow, wxLEDNumberCtrl, wxEditableListBox, wxStaticPicture +and a split tree/content view. +
    • mmedia: deprecated library for playing audio and video. +
    • net: wxEmail class. +
    • ogl: Object Graphics Library (for drawing connected shapes). +
    • plot: simple plotting class. +
    • stc: wxStyledTextControl, a wrapper for the Scintilla code editor control. +
    • svg: wxSVGFileDC class for drawing vector graphics into a SVG file. +
    + +

    + - - + + + - + + + + diff --git a/docs/msw/install.txt b/docs/msw/install.txt index 96826c12ea..6e942f8ffb 100644 --- a/docs/msw/install.txt +++ b/docs/msw/install.txt @@ -1,8 +1,11 @@ Installing wxWidgets 2.6.0 --------------------------- +----------------------------------------------------------- -This is wxWidgets 2.6.0 for Microsoft Windows 9x/ME, Windows NT, Windows 2000 -and Windows XP. +This is wxWidgets 2.6.0 for Microsoft Windows 9x/ME, Windows NT, +Windows 2000, Windows XP and Windows CE. + +These installation notes can be found in docs/msw/install.txt +in your wxWidgets distribution. IMPORTANT NOTE: If you experience problems installing, please re-read this instructions and other related files (changes.txt, @@ -17,7 +20,7 @@ Please report bugs using the SourceForge bug tracker: http://sourceforge.net/bugs/?group_id=9863 Unarchiving -=========== +============================================================ A setup program is provided (setup.exe) to automatically copy files to a directory on your hard disk. Do not install into a @@ -105,7 +108,7 @@ Below are compiler specific notes followed by customizing instructions that apply to all compilers (search for "Configuring the build"). Microsoft Visual C++ compilation --------------------------------- +---------------------------------------------------------------- You may wish to visit http://wiki.wxwindows.org/wiki.pl?MSVC for a more informal and more detailed description of the process summarized below. @@ -184,7 +187,7 @@ files from an existing wxWidgets sample and adapt them, or visit http://wiki.wxwindows.org/wiki.pl?MSVC. Borland C++ 5.0/5.5 compilation -------------------------------- +---------------------------------------------------------------- Compiling using the makefiles (updated 24 Sept 02): @@ -228,13 +231,13 @@ the following preprocessor directive: more details) Borland 16 Bit compilation for Windows 3.1 ------------------------------------------- +---------------------------------------------------------------- The last version of wxWidgets to support 16-bit compilation with Borland was 2.2.7 - Please download and read the instructions in that release Watcom C++ 10.6/11 and OpenWatcom compilation ---------------------------------------------- +---------------------------------------------------------------- 1. Change directory to build\msw. Type 'wmake -f makefile.wat' to make the wxWidgets core library. @@ -258,9 +261,9 @@ Note (4): if Watcom can't read the precompiled header when building a sample, the sample again. Metrowerks CodeWarrior compilation ----------------------------------- +---------------------------------------------------------------- -1. CodeWarrior Pro7 project files in XML format are already +1. CodeWarrior Pro 7 project files in XML format are already included in wxMSW-2.6.0.zip and the setup version. 2. Review the file include\wx\msw\setup.h (or include\wx\msw\setup0.h if @@ -322,7 +325,7 @@ Metrowerks CodeWarrior compilation Cygwin/MinGW compilation ------------------------- +---------------------------------------------------------------- wxWidgets supports Cygwin (formerly GnuWin32) betas and releases, and MinGW. Cygwin can be downloaded from: @@ -351,7 +354,7 @@ If using MinGW, you can download the add-on MSYS package to provide Unix-like tools that you'll need to build wxWidgets using configure. Using makefiles directly ------------------------- +---------------------------------------------------------------- NOTE: The makefile.gcc makefiles are for compilation under MinGW using native make and Windows command interpreter (command.com/cmd.exe), they @@ -383,7 +386,7 @@ All targets have 'clean' targets to allow removal of object files and other intermediate compiler files. Using configure ---------------- +---------------------------------------------------------------- Instead of using the makefiles, you can use the configure system to generate appropriate makefiles, as used on Unix @@ -477,7 +480,8 @@ OLD VERSIONS: Symantec & DigitalMars C++ compilation --------------------------------------- +---------------------------------------------------------------- + The DigitalMars compiler is a free succssor to the Symantec compiler and can be downloaded from http://www.digitalmars.com/ @@ -505,7 +509,7 @@ using bakefile tool according to the instructions in build\bakefiles\README: 16-bit compilation is no longer supported. Configuring the build -===================== +================================================================ So far the instructions only explained how to build release DLLs of wxWidgets and did not cover any configuration. It is possible to change many aspects of @@ -515,7 +519,7 @@ and the only difference between them is in object files and library directory names and in make invocation command. Changing the settings ---------------------- +---------------------------------------------------------------- There are two ways to modify the settings: either by passing the values as arguments when invoking make or by editing build\msw\config.$(compiler) file @@ -553,7 +557,7 @@ Brief explanation of options and possible values is in every build\msw\config.* file; more detailed description follows. Basic options -------------- +---------------------------------------------------------------- BUILD=release Builds release version of the library. It differs from default 'debug' @@ -578,7 +582,7 @@ WXUNIV=1 http://www.wxwidgets.org/wxuniv.htm for more information). Advanced options ----------------- +---------------------------------------------------------------- MONOLITHIC=1 Starting with version 2.5.1, wxWidgets has the ability to be built as @@ -656,7 +660,7 @@ CFG= directories" below for more information. Compiler specific options -------------------------- +---------------------------------------------------------------- * MinGW @@ -678,7 +682,7 @@ DEBUG_RUNTIME_LIBS=1 setting makes it possible. Fine-tuning the compiler ------------------------- +---------------------------------------------------------------- All makefiles have variables that you can use to specify additional options passed to the compiler or linker. You won't need this in most cases, but if you @@ -686,7 +690,7 @@ do, simply add desired flags to CFLAGS (for C compiler), CXXFLAGS (for C++ compiler), CPPFLAGS (for both C and C++ compiler) and LDFLAGS (the linker). Object and library directories ------------------------------- +---------------------------------------------------------------- All object files produced during library build are stored in a directory under build\msw. It's name is derived from build settings and CFG variable and from @@ -736,7 +740,7 @@ enabled (without CFG, both of them would be put into same directory and there would be conflicts between the files). General Notes -============= +================================================================= - Debugging: under Windows 95, debugging output isn't output in the same way that it is under NT or Windows 3.1. diff --git a/docs/readme.txt b/docs/readme.txt index 775cf20b5e..5a90436f7e 100644 --- a/docs/readme.txt +++ b/docs/readme.txt @@ -1,9 +1,9 @@ wxWidgets 2.6.0 ---------------- +--------------------------------------------------------- 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, @@ -22,20 +22,23 @@ for a list of important documents and samples. 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: -- 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) +- PalmOS (alpha) Most popular C++ compilers are supported; see the install.txt file for each platform (available via docs/html/index.htm) for details. @@ -62,6 +65,7 @@ see the install.txt file in the individual directories: docs/x11 docs/mgl docs/os2 + docs/palmos Licence information ------------------- @@ -75,35 +79,37 @@ For licensing information, please see the files: 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 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. @@ -120,8 +126,10 @@ The wxWidgets bug database can be browsed at: 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 HTB (wxWidgets HTML Help) files are located in docs/htb. Further information ------------------- diff --git a/docs/todo.txt b/docs/todo.txt index 125f33989c..68068e1fe3 100644 --- a/docs/todo.txt +++ b/docs/todo.txt @@ -7,14 +7,9 @@ Please see also: docs/motif/todo.txt docs/msw/todo.txt -- Fix wxStream mess: problems with Eol(), LastCount(), buffering +- Fix wxStream: problems with Eol(), LastCount(), buffering - Fix wxHTTP/wxFTP which are currently broken, fix/rewrite wxURL -- Add 3-state wxCheckBox - -- In doc/view file selector, document type is selected by - extension, not the type selected in the (Windows) file selector. - - Add wxUSE_HOTKEY and any other missing options to configure. -- 2.45.2
    @@ -288,6 +317,7 @@ by Franky Braem, in PDF format.

    Each of the following samples demonstrates one or more aspect of wxWidgets.

      +
    • access: Active Accessiblity sample (Windows only).
    • artprov: shows how you can customize the look of standard wxWidgets dialogs by replacing default bitmaps/icons with your own versions.
    • calendar: a sample to test the wxCalendarCtrl class. @@ -300,11 +330,13 @@ defaults to wxRegConfig on WIN32 (optionally wxIniConfig), and wxFileConfig on o console-mode (no-GUI) compilation of wxWidgets.
    • controls: sample showing a variety of controls, including wxNotebook. -
    • db: wxDB ODBC sample. +
    • db: wxODBC sample. +
    • debugrpt: wxDebugReport sample.
    • dialogs: shows some of the common dialogs available -- wxFontDialog, wxColourDialog, wxFileDialog, wxDirDialog, wxMessageBox, wxTextEntryDialog, wxSingleChoiceDialog. For printing-related dialogs, see the printing sample.
    • dialup: wxDialUpManager demo. +
    • display: wxDisplay demo.
    • dnd: demonstrates drag and drop on supported platforms.
    • docview: demonstrates use of the document view classes, using wxFrame. @@ -314,7 +346,9 @@ using wxMDIParentFrame, wxMDIChildFrame.
    • drawing: tests device context drawing.
    • dynamic: shows how to connect events to member functions dynamically. +
    • erase: Window erasing sample.
    • event: demonstrates event handling. +
    • exept: demonstrates exception handling.
    • exec: demonstrates wxExecute.
    • font: tests fonts, font enumerator, font encodings.
    • grid: demonstrates the wxGrid class. @@ -331,6 +365,7 @@ applications and also as a help facility.
    • widget: demonstrates the use of controls in HTML pages.
    • zip: shows how help files can be packaged in zip archives.
    +
  • htlbox: demonstrates wxHtmlListBox.
  • image: shows off the cross-platform wxImage class.
  • ipc: shows the DDE-like protocol in action, both using real DDE on Windows, and TCP/IP on all platforms. Edit ddesetup.h @@ -342,6 +377,7 @@ to switch between compilation modes.
  • listctrl: demonstrates the wxListCtrl (implemented natively on WIN32, and using a generic version on other platforms).
  • menu: tests menus. +
  • mediaplayer: demonstrates wxMediaCtrl, for playing movies and audio files in a window.
  • mdi: shows off the MDI (Multiple Document Interface) classes. On Windows, the regular MDI scheme is used whereby child windows have full sizing and moving rights within the main window. On other platforms, tabbed windows are used, where the children are always maximized. @@ -353,6 +389,7 @@ platforms that don't support it, a normal-sized title bar is displayed.
  • minimal: just shows a frame, a menubar, and a statusbar. About as small a wxWidgets application as you can get.
  • mobile: mini applications for embedded platforms. +
  • multimon: demo showing how to use multiple monitors.
  • nativdlg: shows how wxWidgets can load a standard Windows dialog resource, translating the controls into wxWidgets controls (Windows only).
  • notebook: shows the wxNotebook (tabbed window) control. @@ -363,9 +400,10 @@ Excel to be present).
  • printing: shows printing and previewing.
  • propsize: demonstrates proportional sizer classes.
  • regtest: tests the low-level Windows registry functions (Windows only). -
  • rotate: demonstrates interpolated and non-interpolated rotation of a wxImage.
  • sashtest: demonstrates use of the wxSashWindow class to allow @@ -373,7 +411,9 @@ the user to resize subwindows.
  • scroll: demonstrates wxScrolledWindow.
  • scrollsub: demonstrates the use of wxScrolledWindow to scroll an embedded window. +
  • shaped: demonstrates non-rectangular windows using wxFrame::SetShape.
  • sockets: demonstrates the TCP/IP family of classes. +
  • sound: demonstrates use of wxSound.
  • splash: demonstrates use of the wxSplashScreen class.
  • splitter: demonstrates the wxSplitterWindow class.
  • statbar: demonstrates the wxStatusBar class. @@ -389,6 +429,7 @@ programming.
  • typetest: tests various data type classes, including wxTime, wxDate and wxVariant.
  • validate: shows simple use of validation. +
  • vscroll: shows use of wxVScrolledWindow.
  • wizard: demonstrates the wxWizard class.
  • xrc: demonstrates the XRC resource system. diff --git a/docs/html/platform.htm b/docs/html/platform.htm index 8e6f89a7dc..4f64c8fac2 100644 --- a/docs/html/platform.htm +++ b/docs/html/platform.htm @@ -1,3 +1,4 @@ + Platforms supported by wxWindows 2.4 @@ -133,10 +134,18 @@ often don't work.
    • HP-UX 10.20wxGTK with HP CC A.10.22
    or HP aCC B3910B A.01.18    		OkStaf VerhaegenHP-UX
    HP-UX 10.20 wxGTK with HP CC A.10.22
    or HP aCC B3910B A.01.18    		OkStaf Verhaegen you need to add -Aa -D_HPUX_SOURCE to CFLAGS
    wxGTK with gccOkJulian Albo Garcia
    HP-UX 10.20 wxGTK with gccOkJulian Albo Garcia
    HP-UX 11i v1 PA-RISC, wxMotif 2.5.4, tried aCC A.03.57 and g++ 3.4.2OkIan, MikeFor a 32-bit PA-RISC build, if you want to use SHLIB_PATH to make it easier to use + wxWidgets without installing it, then add LDFLAGS=-Wl,+s
    + If you want to compile the test suite then aCC A.03.57 requires CXX='aCC -AA'
    + aCC can also be used as the C compiler instead of cc by adding CC='aCC -Ae' +
    HP-UX 11i v2 IA64, wxMotif 2.5.4, aCC A.06.00OkMike