Amebis/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Mods to the intro.

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@8106 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Julian Smart
2000-08-15 10:19:45 +00:00
parent 14329e037b
commit 45961fa0a5
1 changed files with 47 additions and 35 deletions
Download Patch File Download Diff File Expand all files Collapse all files

82
docs/latex/book/chap_intro.tex
View File

@@ -9,8 +9,8 @@ Not so long ago, it seemed as though Microsoft was on course to
take over the desktop for good with the Windows range of take over the desktop for good with the Windows range of
operating systems. Unix was retreating to server territory and operating systems. Unix was retreating to server territory and
had all but given up the fight against NT. Apple was sickening had all but given up the fight against NT. Apple was sickening
and it seemed almost common sense that the quirky Mac had had (in the non-derogatory sense of the word!) and it seemed almost
its day. common sense that the quirky Mac had had its day.
At the start of the new century, the picture has changed quite At the start of the new century, the picture has changed quite
dramatically. Linux is advancing from its position of strength dramatically. Linux is advancing from its position of strength
@@ -85,24 +85,23 @@ Hardy which needed to run on Windows as well as X-based Unix
workstations. The existing commercial cross-platform tools were workstations. The existing commercial cross-platform tools were
deemed too expensive for an in-house experimental project, so deemed too expensive for an in-house experimental project, so
the only alternative was to build one. wxWindows (w for Microsoft the only alternative was to build one. wxWindows (w for Microsoft
Windows, x for the X Windowing System) started off with support for XView and MFC 1.0, and Windows, x for the X Windowing System) started off with support for Sun's XView
and Microsoft's MFC 1.0, and
AIAI allowed it to be released to the Internet. As it became AIAI allowed it to be released to the Internet. As it became
clear that XView was doomed, a Motif port was written. Borland clear that XView was doomed, a Motif port was written. Borland
C++ users began to request a version that was not dependent on C++ users began to request a version that was not dependent on
MFC, so the Windows port was rewritten to use the native Windows MFC, so the Windows port was rewritten to use the native Windows
API. Over time, a small but enthusiastic community of wxWindows API. Over time, a small but enthusiastic community of wxWindows
users was established and a mailing list set up. Contributions users was established and a mailing list set up. Many contributions
and fixes were sent in, the largest contributions being the Mac and fixes were sent in. wxWindows gradually picked up more and more users
and Xt ports. wxWindows gradually picked up more and more users from all over the world: academic, government, and corporate users
from all over the world: commercial, government, and - most who found that wxWindows offered a better product, and better support, than the
gratifying of all - company users who found that wxWindows
offered a better product, and better support, than the
commercial products they had looked at or used. commercial products they had looked at or used.
During 1995, Markus Holzem released his port of wxWindows to Xt, During 1995, Markus Holzem released his port of wxWindows to Xt,
the X toolkit. This meant that software could be written that the X toolkit. This meant that software could be written that
would work on X systems without the need for installing Motif, would work on X-based systems without the need for installing Motif,
which is a commercial product. then still a commercial product.
In 1996, Julian left AIAI to pursue freelance consultancy, and In 1996, Julian left AIAI to pursue freelance consultancy, and
there were few new releases. The seemingly unstoppable advance there were few new releases. The seemingly unstoppable advance
@@ -112,52 +111,58 @@ tired and in need of a serious rethink. At the start of 1997 it
was make or break time - call it a day and move onto other was make or break time - call it a day and move onto other
things, or commit to re-engineering wxWindows with an API that things, or commit to re-engineering wxWindows with an API that
was flexible enough for current and future user interface was flexible enough for current and future user interface
trends, with more 'widgets', and better use of C++. After an trends, with more sophisticated widgets, and making better use of C++.
exchange between Julian Smart and Markus Holzem (the author of After a short debate, the effort was relaunched
the Xt port), it was decided that it was worthwhile. Julian with Julian concentrating on the Windows port, and Markus on the combined Motif/Xt port,
would do the Windows port, Markus the combined Motif/Xt port, with both contributing to the common and generic parts. wxWindows 2 API
with both contributing to the generic parts. wxWindows 2 API
ideas and code started to take shape. ideas and code started to take shape.
During 1997 an effort to produce a standard Linux desktop During 1997 an effort to produce a standard Linux desktop
environment was underway - GNOME. Its widget set was GTK+, built environment was underway - GNOME. Its widget set was GTK+, built
on top of X11 and it looked as though GTK+-based apps were to on top of X11 and it looked as though GTK+-based apps were to
become the standard in the Linux universe. Its one major problem become the standard in the Linux universe. Its one major problem:
- GTK+ was C-based, and only a thin (and unportable) C++ wrapper GTK+ was C-based, and only a thin (and unportable) C++ wrapper
existed for it. In August 1997, Wolfram Gloger made a suggestion existed for it. In August 1997, Wolfram Gloger made a suggestion
that wxWindows 2 should be ported to GTK+ - Robert Roebling had that wxWindows 2 should be ported to GTK+ - Robert Roebling had
initial reservations, but in general supported the idea. He initial reservations, but in general supported the idea. He
became the prime mover for wxGTK and alphas were made available became the prime mover for wxGTK and alphas were made available
at the beginning of 1998. In May 1998 the Windows and GTK+ ports at the beginning of 1998. In May 1998 the Windows and GTK+ ports
were merged and put into a CVS repository made available to all were merged and put into a CVS repository made available to all
contributors to wxWindows. contributors to wxWindows: a decision that has accelerated the development
effort tremendously. At this point Vadim Zeitlin became a prime
mover on the Windows port and revamped much of the container
and collection support.
Markus Holzem had to drop out of the wxWindows 2 effort in early Markus Holzem had to drop out of the wxWindows 2 effort in early
1998, but Julian Smart started a new wxMotif port. The idea of 1998, but Julian Smart started a new wxMotif port. The idea of
an Xt port was dropped, since there remain two possibilities for an Xt port was dropped, since there remain two possibilities for
free Unix programming with wxWindows: wxGTK, and wxMotif with free Unix programming with wxWindows: wxGTK, and wxMotif using
the Motif clone Lesstif. the Motif clone Lesstif.
In September 1998, Stefan Csomor started a new version of the In September 1998, Stefan Csomor started a new version of the
wxMac 2 port based in part on Greg Whitehead's initial work. wxMac 2 port based in part on Greg Whitehead's initial work.
Several releases have been made and the code will be integrated In 1999 wxMac became ready for prime-time and Stefan has
into the main CVS stream in Summer 2000. made it ready for MacOS X.
David Webster and Stefan Neis are working on an OS/2 port, and Also in 1998, Vaclav Slavik burst onto the wxWindows scene with his
interest has been expressed in ports to other systems, such as exciting wxHTML module that can now provide applications with (to name but a few) HTML help, superb
BeOS. About boxes, and report viewing and printing facilities. Vaclav has
also written an enhanced resource system for wxWindows based on XML,
that supports many more wxWindows features than the old WXR-based system.
wxWindows 2.1.11 saw the bundling of Vaclav Slavik's impressive Since 1998 Robin Dunn has been completely rewriting the old Python/wxWindows
wxHTML classes, with subsequent enhancements including marriage and now wxPython is another force to be reckoned with in the
print/preview ability, and a helpview application and help development community.
controller class for cross-platform HTML help. wxHTML gives
applications easy access to enviable formatted text viewing and
reporting capabilities.
During 2000 wxWindows will adopt Vaclav's XML resource system %David Webster and Stefan Neis have been working on an OS/2 port, and
as a replacement for the WXR system; this will allow much %interest has been expressed in ports to other systems, such as
greater flexibility and portability with support for %BeOS.
sizers and many more controls than WXR. %
Development on wxWindows is concentrating on achieving more modularity,
additional sophisticated GUI components, and compatibility with
a wider range platforms. The wxStudio IDE project promises to
make wxWindows development much easier and introduce wxWindows to people
used to rapid application development environments under Microsoft Windows.
\section{How to use this book} \section{How to use this book}
@@ -166,3 +171,10 @@ as usual, the ordering reflects a progression from basic concepts
to more advanced ones, so the first few chapters at least to more advanced ones, so the first few chapters at least
should be read consecutively for best effect. should be read consecutively for best effect.
Complete programs illustrating concepts in many of the chapters can be
found in the accompanying CD-ROM, along with wxWindows itself and lots
of extra, cool stuff.
We all hope that you enjoy reading this book and, most importantly,
have fun using wxWindows to build great-looking, multiplatform applications!