]> git.saurik.com Git - wxWidgets.git/blame_incremental - docs/html/wxbook.htm
projects / wxWidgets.git / blame_incremental
? search:
summary | shortlog | log | commit | commitdiff | tree
blob | blame (non-incremental) | history | HEAD
wxMenu implementations
[wxWidgets.git] / docs / html / wxbook.htm
... / ...
CommitLineData
1<HTML>
2
3<HEAD>
4<TITLE>wxWindows Book</TITLE>
5</HEAD>
6
7<BODY BGCOLOR=#FFFFFF TEXT=#000000 LINK=#FF0000 VLINK=#000000>
8
9<font face="Arial, Lucida Sans, Helvetica">
10
11<table width=100% border=4 cellpadding=5 cellspacing=0>
12<tr>
13<td bgcolor="#660000">
14<font size=+1 face="Arial, Lucida Sans, Helvetica" color="#FFFFFF">
15wxWindows Book
16</font>
17</td>
18</tr>
19</table>
20
21<P>
22
23<center>
24<a href="#about">About</a> |
25<a href="#participants">Participants</a> |
26<a href="#publication">Publication</a> |
27<a href="#suggestions">Suggestions</a> |
28<a href="#format">Format</a> |
29<a href="#contents">Contents</a>
30</center>
31
32<hr>
33
34<H3><a name="about">About the wxWindows book</a></H3>
35
36Discussions have been taking place on the wxwin-developers list about
37collaboratively writing a wxWindows book. The concensus is to write a tutorial
38book for people with reasonable C++ experience, with the possibility of including the API reference either in a very compact
39form at the back of the book, or as a separate volume. The book would almost certainly
40contain a CD-ROM with wxWindows and its documentation. It would probably be available
41for free on-line, publisher permitting.<P>
42
43Goals for the book:<P>
44
45<ol>
46<li> to allow users to become accomplished wxWindows developers rapidly;
47<li> to be useful over a longer period than just the first few weeks, since
48there are a lot of complex areas to address and not all features will be
49used up-front in a project;
50<li> to promote wxWindows to a wider audience;
51<li> to make at least some money for the authors.
52</ol>
53
54<P>
55
56Audience: beginners + experienced wxWindows users, but with reasonable C++
57knowledge.<P>
58
59It is suggested that any financial return from the book be allocated on a points system,
60with a predefined number of points for chapters, indexing, editing, proof-reading etc.<P>
61
62<hr>
63
64<H3><a name="participants">Participants</a></H3>
65
66So far, the following people are interested in taking part in this project:<P>
67
68<ul>
69<li><a href="mailto:tomr@scitechsoft.com">Tom Ryan</a>, SciTech Software.
70<li><a href="mailto:robin@alldunn.com">Robin Dunn</a>. <i>Chapter on wxPython.</i>
71<li><a href="mailto:mheck@www.surveyorcorp.com">Matt Heck</a>, SurveyorCorp Inc.
72<i>
73<ol>
74 <li>a case study of how and why we've used wxWindows at Surveyor Corp., and
75 how it's worked out so far;
76 <li>an appendix something similar about how to use wxLIVID for video capture and display;
77 <li>proofreading
78</ol>
79</i>
80<li><a href="mailto:julian.smart@ukonline.co.uk">Julian Smart</a>.
81<li><a href="mailto:zeitlin@dptmaths.ens-cachan.fr">Vadim Zeitlin</a>.
82<li><a href="mailto:slavik2@czn.cz">Vaclav Slavik</a>. <i>wxHTML section</i>
83<li><a href="mailto:csomor@advancedconcepts.ch">Stefan Csomor</a>. <i>the sequence of events i.e. which action provokes which event sequence,
84this is implicit for the use on MSW, but very important for other systems; and porting to new platforms</i>
85<li><a href="mailto:karsten@phy.hw.ac.uk">Karsten Ballueder</a>. <i>short tutorials on some useful
86GNU tools, like autoconf/configure/make, programming
87strategies, etc.</i>
88</ul>
89
90<hr>
91
92<H3><a name="publication">Publication</a></H3>
93
94Tom Ryan originally wrote:<P>
95
96<PRE>
97Hi Guys,
98
99I just wanted to let you know that I have spoken with officials here
100at California State University, Chico and they are potentially
101interested in publishing a book on wxWindows! A wxWindows
102book would give wxWindows a great deal of exposure.
103
104These discussions came out of the fact that CSUC wanted to
105switch from MFC to wxWindows in their GUI programming classes,
106but there was not a book available for students to work with.
107
108I was thinking that the first edition could be primarily the reference
109documentation combined with a basic wxTutorial and examples. In
110this case, it would be fairly straightforward to get something out
111initially and then we could take it from there.
112</PRE>
113
114<p>
115
116<a href="mailto:benles@powernet.net">Ben Allfree</a> has also expressed an interest
117in publishing a wxWindows book, and distributing it via Amazon. Ben was thinking
118in terms of a quickie job using the existing reference manual.<P>
119
120Another publishing name to think of is O'Reilly. They would probably give us a lot
121of guidance for style, formatting, etc.<P>
122
123<a href="mailto:Roald.Ribe@winlink.no">Roald Ribe</a> writes:
124"<a href="http://www.bruceeckel.com/javabook.html" target=_new>Thinking in Java</a>
125is published both as a PDF for internet (by the author) and in print by Prentice Hall."<P>
126
127<hr>
128
129<H3><a name="suggestions">Suggestions and comments</a></H3>
130
131<ul>
132<li>Chapter on converting from MFC. (Julian Smart)
133<li>A chapter on why some inconsistencies are almost always going to show up in a
134multiplatform toolkit, how to avoid them, how to deal with when you have
135no choice, and (if wxBook explains the internals or philosophy of
136wxWindows at all) how wxWindows attempts to minimize the number we
137encounter. (Matt Heck)
138<li>Creating the shortest possible path to writing "Hello World" from scratch in wxWindows. (Matt Heck)
139<li>How will royalties for subsequent editions be shared out? (Tom Ryan)
140<li>"My personal feeling is that this project will wind up being developed
141by a small team, led by an editor that will wind up doing about half
142of the total amount of work." (Tom Ryan)
143</ul>
144
145<hr>
146
147<H3><a name="format">Text format</a></H3>
148
149This depends partly on the publisher, but one possibility is to target Word but have
150submissions in a number of formats including Latex. We should eventually write a style
151and formatting guide.<P>
152
153<hr>
154
155<H3><a name="contents">Contents</a></H3>
156
157This is open to suggestion.<P>
158
159Last year, <a href="mailto:mlorenz@visionx.com">Mike Lorenz</a> of <a href="http://www.visionx.com">VisionX</a>
160suggested this
161<a href="http://www.visionx.com/wx/tutorial_outline.htm">tutorial outline</a>, which could
162be a good starting point.<P>
163
164</font>
165
166</BODY>
167
168</HTML>
wxWidgets (Impactor)