--- /dev/null
+<HTML>
+
+<HEAD>
+<TITLE>wxWindows Book</TITLE>
+</HEAD>
+
+<BODY BGCOLOR=#FFFFFF TEXT=#000000 LINK=#FF0000 VLINK=#000000>
+
+<font face="Arial, Lucida Sans, Helvetica">
+
+<table width=100% border=4 cellpadding=5 cellspacing=0>
+<tr>
+<td bgcolor="#660000">
+<font size=+1 face="Arial, Lucida Sans, Helvetica" color="#FFFFFF">
+wxWindows Book
+</font>
+</td>
+</tr>
+</table>
+
+<P>
+
+<center>
+<a href="#about">About</a> |
+<a href="#participants">Participants</a> |
+<a href="#publication">Publication</a> |
+<a href="#suggestions">Suggestions</a> |
+<a href="#format">Format</a> |
+<a href="#contents">Contents</a>
+</center>
+
+<hr>
+
+<H3><a name="about">About the wxWindows book</a></H3>
+
+Discussions have been taking place on the wxwin-developers list about
+collaboratively writing a wxWindows book. The concensus is to write a tutorial
+book for people with reasonable C++ experience, with the possibility of including the API reference either in a very compact
+form at the back of the book, or as a separate volume. The book would almost certainly
+contain a CD-ROM with wxWindows and its documentation. It would probably be available
+for free on-line, publisher permitting.<P>
+
+Goals for the book:<P>
+
+<ol>
+<li> to allow users to become accomplished wxWindows developers rapidly;
+<li> to be useful over a longer period than just the first few weeks, since
+there are a lot of complex areas to address and not all features will be
+used up-front in a project;
+<li> to promote wxWindows to a wider audience;
+<li> to make at least some money for the authors.
+</ol>
+
+<P>
+
+Audience: beginners + experienced wxWindows users, but with reasonable C++
+knowledge.<P>
+
+It is suggested that any financial return from the book be allocated on a points system,
+with a predefined number of points for chapters, indexing, editing, proof-reading etc.<P>
+
+<hr>
+
+<H3><a name="participants">Participants</a></H3>
+
+So far, the following people are interested in taking part in this project:<P>
+
+<ul>
+<li><a href="mailto:tomr@scitechsoft.com">Tom Ryan</a>, SciTech Software.
+<li><a href="mailto:robin@alldunn.com">Robin Dunn</a>. <i>Chapter on wxPython.</i>
+<li><a href="mailto:mheck@www.surveyorcorp.com">Matt Heck</a>, SurveyorCorp Inc.
+<i>
+<ol>
+ <li>a case study of how and why we've used wxWindows at Surveyor Corp., and
+ how it's worked out so far;
+ <li>an appendix something similar about how to use wxLIVID for video capture and display;
+ <li>proofreading
+</ol>
+</i>
+<li><a href="mailto:julian.smart@ukonline.co.uk">Julian Smart</a>.
+<li><a href="mailto:zeitlin@dptmaths.ens-cachan.fr">Vadim Zeitlin</a>.
+</ul>
+
+<hr>
+
+<H3><a name="publication">Publication</a></H3>
+
+Tom Ryan originally wrote:<P>
+
+<PRE>
+Hi Guys,
+
+I just wanted to let you know that I have spoken with officials here
+at California State University, Chico and they are potentially
+interested in publishing a book on wxWindows! A wxWindows
+book would give wxWindows a great deal of exposure.
+
+These discussions came out of the fact that CSUC wanted to
+switch from MFC to wxWindows in their GUI programming classes,
+but there was not a book available for students to work with.
+
+I was thinking that the first edition could be primarily the reference
+documentation combined with a basic wxTutorial and examples. In
+this case, it would be fairly straightforward to get something out
+initially and then we could take it from there.
+</PRE>
+
+<p>
+
+<a href="mailto:benles@powernet.net">Ben Allfree</a> has also expressed an interest
+in publishing a wxWindows book, and distributing it via Amazon. Ben was thinking
+in terms of a quickie job using the existing reference manual.<P>
+
+Another publishing name to think of is O'Reilly. They would probably give us a lot
+of guidance for style, formatting, etc.<P>
+
+
+<hr>
+
+<H3><a name="suggestions">Suggestions and comments</a></H3>
+
+<ul>
+<li>Chapter on converting from MFC. (Julian Smart)
+<li>A chapter on why some inconsistencies are almost always going to show up in a
+multiplatform toolkit, how to avoid them, how to deal with when you have
+no choice, and (if wxBook explains the internals or philosophy of
+wxWindows at all) how wxWindows attempts to minimize the number we
+encounter. (Matt Heck)
+<li>Creating the shortest possible path to writing "Hello World" from scratch in wxWindows. (Matt Heck)
+<li>How will royalties for subsequent editions be shared out? (Tom Ryan)
+<li>"My personal feeling is that this project will wind up being developed
+by a small team, led by an editor that will wind up doing about half
+of the total amount of work." (Tom Ryan)
+</ul>
+
+<hr>
+
+<H3><a name="format">Text format</a></H3>
+
+This depends partly on the publisher, but one possibility is to target Word but have
+submissions in a number of formats including Latex. We should eventually write a style
+and formatting guide.<P>
+
+<hr>
+
+<H3><a name="contents">Contents</a></H3>
+
+This is open to suggestion.<P>
+
+Last year, <a href="mailto:mlorenz@visionx.com">Mike Lorenz</a> of <a href="http://www.visionx.com">VisionX</a>
+suggested this
+<a href="http://www.visionx.com/wx/tutorial_outline.htm">tutorial outline</a>, which could
+be a good starting point.<P>
+
+</font>
+
+</BODY>
+
+</HTML>
projects / wxWidgets.git / commitdiff
