Updated FAQ from web files
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@35608 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
@@ -1,7 +1,8 @@
|
||||
|
||||
<HTML>
|
||||
|
||||
<HEAD>
|
||||
<TITLE>wxWidgets 2 FAQ: General</TITLE>
|
||||
<TITLE>wxWidgets FAQ: General</TITLE>
|
||||
</HEAD>
|
||||
|
||||
<BODY BGCOLOR=#FFFFFF TEXT=#000000 VLINK="#00376A" LINK="#00529C" ALINK="#313063">
|
||||
@@ -12,7 +13,7 @@
|
||||
<tr>
|
||||
<td bgcolor="#004080" align=left height=24 background="images/bluetitlegradient.gif">
|
||||
<font size=+1 face="Arial, Lucida Sans, Helvetica" color="#FFFFFF">
|
||||
<b>wxWidgets 2 FAQ: General</b>
|
||||
<b>wxWidgets FAQ: General</b>
|
||||
</font>
|
||||
</td>
|
||||
</tr>
|
||||
@@ -25,7 +26,7 @@ See also <a href="faq.htm">top-level FAQ page</a>.
|
||||
<h3>List of questions in this category</h3>
|
||||
<ul>
|
||||
<li><a href="#whatis">What is wxWidgets?</a></li>
|
||||
<li><a href="#licence">Can I use wxWidgets 2 for both proprietary projects, and GPL'ed projects?</a></li>
|
||||
<li><a href="#licence">Can I use wxWidgets for both proprietary projects, and GPL'ed projects?</a></li>
|
||||
<li><a href="#support">Is there support?</a></li>
|
||||
<li><a href="#users">Who uses wxWidgets?</a></li>
|
||||
<li><a href="#platforms">What platforms are supported by wxWidgets?</a></li>
|
||||
@@ -35,7 +36,9 @@ See also <a href="faq.htm">top-level FAQ page</a>.
|
||||
<li><a href="#exceptions">How to use C++ exceptions with wxWidgets?</a></ li>
|
||||
<li><a href="#dev">How is wxWidgets being developed?</a></li>
|
||||
<li><a href="#distrib">How is wxWidgets distributed?</a></li>
|
||||
<!--
|
||||
<li><a href="#future">What are the plans for the future?</a></li>
|
||||
-->
|
||||
<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>
|
||||
@@ -56,17 +59,17 @@ build attractive dialogs and panels. Robert Roebling's <a href="http://www.r
|
||||
and Anthemion Software's <a href="http://www.anthemion.co.uk/dialogblocks/" target=_new>DialogBlocks</a>
|
||||
are two commercial examples, but there are others: see the <a href="lnk_tool.htm">Useful Tools</a> page.<P>
|
||||
|
||||
You don't have to use C++ to use wxWidgets: there is a <a href="http://wxpython.org">Python interface</a> for wxWidgets 2,
|
||||
You don't have to use C++ to use wxWidgets: there is a <a href="http://wxpython.org">Python interface</a> for wxWidgets,
|
||||
and also a <a href="http://wxperl.sourceforge.net" target=_top>Perl interface</a>.
|
||||
<P>
|
||||
|
||||
<h3><a name="licence">Can I use wxWidgets 2 for both proprietary (commercial) projects, and GPL'ed projects?</a></h3>
|
||||
<h3><a name="licence">Can I use wxWidgets for both proprietary (commercial) projects, and GPL'ed projects?</a></h3>
|
||||
|
||||
Yes. Please see the <a href="newlicen.htm">licence</a> for details, but basically
|
||||
you can distribute proprietary binaries without distributing any source code, and neither will wxWidgets
|
||||
conflict with GPL code you may be using or developing with it.
|
||||
<P>
|
||||
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.
|
||||
<P>
|
||||
|
||||
@@ -91,7 +94,7 @@ Our highest-profile user yet is industry veteran and Lotus Corp. founder Mitch K
|
||||
and his <a href="http://www.osafoundation.org" target=_new>Open Source Applications Foundation</a>.
|
||||
<P>
|
||||
|
||||
<H3><a name="platforms">What platforms are supported by wxWidgets 2?</a></H3>
|
||||
<H3><a name="platforms">What platforms are supported by wxWidgets?</a></H3>
|
||||
|
||||
<ul>
|
||||
<li>Windows 3.1, Windows 95/98, Windows NT, Windows 2000, Windows ME.
|
||||
@@ -104,7 +107,7 @@ on OS/2.
|
||||
</ul>
|
||||
<P>
|
||||
|
||||
<H3><a name="specific">How does wxWidgets 2 support platform-specific
|
||||
<H3><a name="specific">How does wxWidgets support platform-specific
|
||||
features?</a></H3>
|
||||
|
||||
This is a hotly-debated topic amongst the developers. My own philosophy
|
||||
@@ -130,7 +133,7 @@ of today's sophisticated applications.<P>
|
||||
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.<P>
|
||||
|
||||
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.<P>
|
||||
|
||||
@@ -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.<P>
|
||||
wxWidgets is strenuously trying to avoid.<P>
|
||||
|
||||
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:<P>
|
||||
<P>
|
||||
|
||||
|
||||
<H3><a name="richedit">Is there a rich edit/markup widget for wxWidgets 2?</a></H3>
|
||||
<H3><a name="richedit">Is there a rich edit/markup widget for wxWidgets?</a></H3>
|
||||
|
||||
These are the possibilities so far:<P>
|
||||
|
||||
@@ -225,22 +228,14 @@ If you are feeling adventurous, you may also check out the sources directly
|
||||
from <a href="cvs.htm">cvs</a>.
|
||||
<p>
|
||||
|
||||
<!--
|
||||
<H3><a name="future">What are the plans for the future?</a></H3>
|
||||
|
||||
Currently we're working too hard on getting wxWidgets finished (are GUI toolkits ever
|
||||
finished?) to think very far ahead. However, we know we want to make wxWidgets 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 PNG and XPM for all platforms.<P>
|
||||
TODO
|
||||
|
||||
Other possibilities include: DCOM/CORBA compatibility; a wxWidgets book;
|
||||
<a href="http://wxworkshop.sourceforge.net/">wxWorkshop</a>, an IDE;
|
||||
other platforms, especially embedded systems; other interface abilities such as speech output.<P>
|
||||
<p>
|
||||
|
||||
We will investigate the possibility of compiler or operating system vendors bundling wxWidgets with
|
||||
their product.<P>
|
||||
|
||||
The high-level goal of wxWidgets is to be thought of as the number one C++ framework,
|
||||
for virtually any platform. Move over, MFC!<P>
|
||||
-->
|
||||
|
||||
<h3><a name="base">What is wxBase?</a></h3>
|
||||
|
||||
|
Reference in New Issue
Block a user