set WXWIN_COMPATIBILITY_2_2 to 1 by default

[wxWidgets.git] / docs / wxQt.html

diff --git a/docs/wxQt.html b/docs/wxQt.html
index b271a816a132735850bc9937e0e869bca3a9d4a4..87f70136945ac523539faa024d8feb93a8b1fd34 100644 (file)
--- a/docs/wxQt.html
+++ b/docs/wxQt.html
@@ -1,9 +1,9 @@
       $Id$
     <br>
       $Id$
     <br>

-    <H1>Proposal for a wxQt project</H1>
+    <H1>Proposal for a port of wxWindows to Qt - wxQt</H1>

     <p>
       Following the recent discussions
     <p>
       Following the recent discussions

-      and flamewars about KDE vs Gnome, I got worried that we see a
+      and flamewars about KDE vs Gnome, we got worried that we'll see a

       repetition of the same damaging infighting from which Unix has
       suffered before. Competition is a good thing, but the current
       situation leaves application developers with a difficult decision to
       repetition of the same damaging infighting from which Unix has
       suffered before. Competition is a good thing, but the current
       situation leaves application developers with a difficult decision to


@@ -16,10 +16,10 @@
       
       The people on the wxWindows developers team thought that we might have
       a solution for this problem, if we can get some outside help to get it
       
       The people on the wxWindows developers team thought that we might have
       a solution for this problem, if we can get some outside help to get it

-      done. Let me explain: wxWindows is a cross-platform development
+      done. Let us explain: wxWindows is a cross-platform development

       toolkit, a library of C++ classes which provide GUI concepts as well
       as other cross-platform issues such as container classes, debug
       toolkit, a library of C++ classes which provide GUI concepts as well
       as other cross-platform issues such as container classes, debug

-      features or configuration management. It has been around since 1992G
+      features or configuration management. It has been around since 1992

       and started by supporting Motif, XView and MS-Windows, with a direct
       X11/Xt port added later. Last year, a major rewrite was started and we
       now have a much advanced library, available for MS Windows, with a
       and started by supporting Motif, XView and MS-Windows, with a direct
       X11/Xt port added later. Last year, a major rewrite was started and we
       now have a much advanced library, available for MS Windows, with a


@@ -37,10 +37,10 @@
       operating systems (a MacOS port is under construction, too), it could
       easily bridge the gap between KDE and Gnome. The quick evolution of
       wxGTK has shown that a new port based on an existing widget set or
       operating systems (a MacOS port is under construction, too), it could
       easily bridge the gap between KDE and Gnome. The quick evolution of
       wxGTK has shown that a new port based on an existing widget set or

-      toolkit can easily be created by a small team within few
+      toolkit can easily be created by a small team within a few

       months. Therefore, we would like to start a project for a Qt/Harmony
       based wxWindow library, wxQt. It would then be possible for
       months. Therefore, we would like to start a project for a Qt/Harmony
       based wxWindow library, wxQt. It would then be possible for

-      application developers to write the same source and copile it either
+      application developers to write the same source and compile it either

       for KDE, Gnome or even any of the other supported systems.
     <p>
       
       for KDE, Gnome or even any of the other supported systems.
     <p>
       


@@ -50,14 +50,17 @@
       code from the other ports.
 
       Please, join us in this effort and, if you feel that you could
       code from the other ports.
 
       Please, join us in this effort and, if you feel that you could

-      contribute, join the wxWindows developers mainling list for further
+      contribute, join the wxWindows developers mailing list for further

       discussions. Just send a mail containing "<tt>subscribe</tt>" to
       discussions. Just send a mail containing "<tt>subscribe</tt>" to

-    <tt>wxwin-developers-request@x.dent.med.uni-muenchen.de</tt>
+    <tt>wxwin-developers-request@wx.dent.med.uni-muenchen.de</tt>

     <p>
       You can find some more information about wxWindows at the following places:
 <ul>
 <li>The <a href="http://web.ukonline.co.uk/julian.smart/wxwin/">wxWindows homepage</a>.
 <li>The <a href="http://www.freiburg.linux.de/~wxxt/">wxGTK homepage</a>
     <p>
       You can find some more information about wxWindows at the following places:
 <ul>
 <li>The <a href="http://web.ukonline.co.uk/julian.smart/wxwin/">wxWindows homepage</a>.
 <li>The <a href="http://www.freiburg.linux.de/~wxxt/">wxGTK homepage</a>

+<li>The <a
+         href="http://Ballueder.home.ml.org/wxWindows/wxQt.html">wxQt
+         proposal</a>(this text)

 <li>The <a href="http://Ballueder.home.ml.org/M/">home of <em>M</em></a>, an email client developed using wxGTK, showing several <a href="http://Ballueder.home.ml.org/M/screenshots/">screenshots</a> of how it actually looks like.
 </ul>
 <p>
 <li>The <a href="http://Ballueder.home.ml.org/M/">home of <em>M</em></a>, an email client developed using wxGTK, showing several <a href="http://Ballueder.home.ml.org/M/screenshots/">screenshots</a> of how it actually looks like.
 </ul>
 <p>