+
<html>
<head>
For further information, please see the
<a href="http://www.wxwindows.org" target=_top>wxWindows Web site</a>,
-<a href="http://mintzer.pqdot.net/cgi-bin/wiki/wiki.pl" target=_top>wxWiki</a>
+<a href="http://wiki.wxwindows.org" target=_top>wxWiki</a>
and install.txt (per port), todo.txt (per port), and bugs.txt (all ports) files
in your wxWindows installation.
<p>
<li><a href="#base">What is wxBase?</a></li>
<li><a href="#univ">What is wxUniversal?</a></li>
<li><a href="#jave">What about Java?</a></li>
+<li><a href="#dotnet">What about .NET/Mono?</a></li>
<li><a href="#help">How can I help the project?</a></li>
</ul>
<hr>
meet all their cross-platform development needs. We don't anticipate a major threat
from Java, and the level of interest in wxWindows is as high as ever.<P>
+<H3><a name="dotnet">What about .NET/Mono?</a></H3>
+
+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',
+garbage collection and various other Java-like language features.<P>
+
+Although this may be attractive to some developers, there
+is a variety of reasons why the .NET/Mono combination is unlikely
+to make wxWindows redundant. Please note that the following comments
+are Julian Smart's opinions.<P>
+
+<ol>
+<li>Not everyone wants or needs net services.
+<li>C++ will be used for a long time to come; compared with C++, C# is a recent development and its future is not certain.
+<li>Mono Forms may only target Winelib (at least to begin with), so the end result is not as native as
+wxWindows (I'm aware there is GTK# for use with the C# language).
+<li>C# is usually byte-compiled and therefore slower. Plus, .NET adds a layer of overhead to the client computer
+that wxWindows does not require.
+<li>Mono hasn't proven its long-term viability yet (it's a complex system of components); wxWindows is ready now.
+<li>You may not wish to buy into Microsoft marketing spin and APIs.
+<li>.NET might never be implemented on some platforms, especially Mac and embedded variants of Linux.
+<li>wxPython and other language variants provide further reasons for wxWindows to continue.
+<li>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 wxWindows!)
+</ol>
+
+There is nothing to stop folk from developing a C# version of the wxWindows API;
+we already have bindings to Python, Perl, JavaScript, Lua, Basic, and Eiffel.
+Update: a <a href="http://wxnet.sourceforge.net/" target=_new>wx.NET</a> project is now in progress.
+
+<P>
+
<H3><a name="help">How can I help the project?</a></H3>
Please check out the <a href="http://www.wxwindows.org/develop2.htm">Community</a> pages,
<li><a href="#settings">What important settings are required in the CodeWarrior Project Preferences?</a></li>
<li><a href="#smarterrors">What are the smart preprocessing errors with the Apple Developer Tools?</a></li>
<li><a href="#aboutmenu">How does wxMac support the standard Apple About menu item and Help menu?</a></li>
+<li><a href="#findericon">How do I add an icon to my application?</a></li>
+<li><a href="#switching">How can I easily switch between different versions of wxWindows in CodeWarrior?</a></li>
</ul>
<hr>
</ul>
<P>
+<h3><a name="findericon">How do I add an icon to my application?</a></h3>
+
+If you have Mac OS X, you have the icns editor somewhere in the
+Utilities folder. Create an icon using this tool and DeRez it, so that you have a .r
+file with a 'icns' resource with id (-16455). Include this .r file in
+your project and in the CodeWarrior Settings add a check mark under Linker:Output
+Flags/Finder Flags/Has Custom Icon.
+<P>
+
+<h3><a name="switching">How can I easily switch between different versions of wxWindows in CodeWarrior?</a></h3>
+
+Sometimes you want to test your application against different versions
+of wxWindows, for example a stable version of wxWindows versus a development version.
+The easiest way to do this is to create a symbolic path.<P>
+
+Under Edit-Preferences in General:Source Trees, type a name (for example WXWIN)
+and choose a path for it. Now reselect your include and lib paths for a last
+time, in the settings for each configuration, but make them relative to the symbolic name.
+<P>
+
+From now on you can just change the path associated with the symbolic name.
+
+<P>
+
+
</font>
</BODY>
<li><a href="#vcdebug">How do you use VC++'s memory leak checking instead of that in wxWindows?</a></li>
<li><a href="#shortcutproblem">Why are menu hotkeys or shortcuts not working in my application?</a></li>
<li><a href="#regconfig">Why can I not write to the HKLM part of the registry with wxRegConfig?</a></li>
+<li><a href="#access">Is MS Active Accessibility supported?</a></li>
</ul>
<hr>
</assembly>
</pre>
+If you want to add it to your application permanently,
+you can also include it in your .rc file using this
+line:<P>
+
+<PRE>
+ 1 24 "winxp.manifest"
+</PRE>
+
+In wxWindows 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.<P>
+
+For an explanation of this syntax, please see
+<a href="http://delphi.about.com/library/bluc/text/uc111601a.htm" target=_new>this
+article</a>.
+<P>
+
<h3><a name="compilers">What compilers are supported?</a></h3>
Please see the wxWindows 2 for Windows install.txt file for up-to-date information, but
compile your programs for release using non-debugging and space-optimisation options, but
take with VC++ 5/6 space optimisation: it can sometimes cause problems.<P>
-Statically-linked wxWindows 2 programs are smaller than wxWindows 1.xx programs, because of the way
-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 500KB using VC++ 6
-(note that this figure may be greater for the latest version of wxWindows).<P>
-
If you want to distribute really small executables, you can
use <a href="http://www.un4seen.com/petite/" target=_top>Petite</a>
by Ian Luck. This nifty utility compresses Windows executables by around 50%, so your 500KB executable
will shrink to a mere 250KB. With this sort of size, there is reduced incentive to
-use DLLs. Another good compression tool is <a href="http://upx.sourceforge.net/" target=_top>UPX</a>.
+use DLLs. Another good compression tool
(probably better than Petite) is <a href="http://upx.sourceforge.net/" target=_top>UPX</a>.
<P>
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.
+complex, the overhead becomes proportionally less significant. And thirdly, trading executable compactness
+for the enormous increase in productivity you get with wxWindows is almost always well worth it.<P>
+
+If you have a really large executable compiled with MinGW (for example 20MB) then
+you need to configure wxWindows to compile without debugging information: see
+docs/msw/install.txt for details. You may find that using configure instead
+of makefile.g95 is easier, particularly since you can maintain debug and
+release versions of the library simultaneously, in different directories.
+Also, run 'strip' after linking to remove all traces of debug info.
+<P>
<H3><a name="mfc">Is wxWindows compatible with MFC?</a></H3>
}
</pre>
+<H3><a name="#access">Is MS Active Accessibility supported?</a></H3>
+
+This is being worked on. Please see <a href="http://www.wxwindows.org/access.htm">this page</a>
+for the current status.
+
+<P>
+
</font>
</BODY>
is -- it is quite helpful to have several translators for one language at
least for proof reading).
-<hr>
+<hr>
<center>
<font size=+2><i><b><a name="available">Available translations</a></b></i></font>
</center>
</tr>
<tr>
- <td valign=center>Chinese</td>
+ <td valign=center>Catalan</td>
+ <td align=center valign=center><IMG SRC="images/yes.gif" ALT="Done"></td>
+ <td align=center valign=center><A HREF="mailto:paubcrespo@hotmail.com">Pau Bosch i Crespo</A>
+ </td>
+</tr>
+
+<tr>
+ <td valign=center>Chinese (simplified)</td>
<td align=center valign=center><IMG SRC="images/yes.gif" ALT="Done"></td>
<td align=center valign=center><A HREF="mailto:mrfx@fm365.com">mrfx</A>
</td>
</tr>
+<tr>
+ <td valign=center>Chinese (traditional)</td>
+ <td align=center valign=center><IMG SRC="images/yes.gif" ALT="Done"></td>
+ <td align=center valign=center><A HREF="mailto:pal.tw@yahoo.com.tw">pal.tw</A>
+ </td>
+</tr>
+
<tr>
<td valign=center>Czech</td>
<td align=center valign=center><IMG SRC="images/yes.gif" ALT="Done"></td>
<tr>
<td valign=center>Polish</td>
- <td align=center valign=center><IMG SRC="images/no.gif" ALT="Not yet"></td>
- <td align=center valign=center><A HREF="mailto:matiso@hoga.pl">Piotr Mackowiak</A></td>
+ <td align=center valign=center><IMG SRC="images/yes.gif" ALT="Done"></td>
+ <td align=center valign=center><A HREF="mailto:matiso@hoga.pl">Piotr Mackowiak</A>,
+ <a href="mailto:jpiw@go2.pl">Janusz Piwowarski</a></td>
</tr>
<tr>
<td align=center valign=center><A HREF="mailto:dogusanh@dynaset.org">Hakki Dogusan</A></td>
</tr>
+<tr>
+ <td valign=center>Ukrainian</td>
+ <td align=center valign=center><IMG SRC="images/yes.gif" ALT="Ok"></td>
+ <td align=center valign=center><A HREF="mailto:manko@salingshot.co.nz">Eugene Manko></td>
+</tr>
+
+
</table>
<br>
-<hr>
+<hr>
<center>
<font size=+2><i><b><a name="howtohelp">How to help</a></b></i></font>
</center>
</body>
</html>
-
-
+
<html>
<head>
<title>Platforms supported by wxWindows 2.4</title>
<tr> <td bgcolor="#fafafa"><br></td><td bgcolor="#fafafa" colspan=5> All BSD systems tests are for wxGTK using gcc. </td>
<tr>
<td bgcolor="#F0F0F0" align=center valign=center rowspan=1>FreeBSD</td>
- <td>
version from 3.2 to 4.6, x86</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td>VZ</td><td><br></td>
+ <td>
all version between 3.2 and 5.0 x86</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td>VZ</td><td><br></td>
</tr>
<tr>
<td bgcolor="#FFFFFF" align=center valign=center rowspan=5>Solaris</td>
<td>wxMotif with Sun CC 4.2</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td>VZ</td><td>Thread support must be disabled on system with not MT-safe X11</td>
<tr> <td>wxMotif with gcc</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td><br></td><td><br></td>
-<tr> <td>wxGTK with Sun CC 4.2</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td>Shiv Shankar Ramakrishnan</td><td><br></td>
+<tr> <td>wxGTK with Sun CC 4.2</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td> </td><td><br></td>
<tr> <td>wxGTK with gcc</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td><br></td><td><br></td>
<tr> <td>wxGTK with Sun CC 5.0 and 6.1 (Solaris 7 and 8)</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td>Jiri Mracek</td><td>You have to edit line 2079 in glib.h to fix GTK+ error</td>
</tr>
/pack/cvsroots/wxwindows/wxWindows/include/wx/textbuf.h,v <-- textbuf.h
new revision: 1.8; previous revision: 1.7
+18. Better notebook page sizing
+
+nbbase.cpp, CalcSizeFromPage, plus #includes at top of file.
+This gets the tab size and adds a bit for borders.
+We should do the same for other platforms, only rationalise
+it so that wxNotebook returns the tab rect info.
+
these classes, as per the patch on SF.
- Rewrite wxFileHistory using wxString and wxArrayString, and
put in separate file.
-
+- Add wxArrayString methods to wxTextValidator and any other
+ class that needs them.
+- Add wxNotebook::GetTabRect or similar so we can estimate
+ page size better in wxNotebookBase::CalcSizeFromPage.
+- Add function to clear all wxNotebook tabs without
+ destroying the pages.
+- Add individual setters to wxScrollBar and other classes
+ that use a combined setter.
+- Remove traces of old resource system from wxWizard.
Version: $Id$
projects / wxWidgets.git / commitdiff
