X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/ad90972f272019228f98bc37d90bbff54b298fe3..94e2ed3b8db0220160c0b939782cd46914ec073a:/docs/html/wxbook.htm?ds=sidebyside diff --git a/docs/html/wxbook.htm b/docs/html/wxbook.htm index a2cae70661..01c3c737bf 100644 --- a/docs/html/wxbook.htm +++ b/docs/html/wxbook.htm @@ -24,20 +24,30 @@ wxWindows Book About | Participants | Publication | -Suggestions | + Format | +Style guide | +Titles | Contents +


+

About the wxWindows book

-Discussions have been taking place on the wxwin-developers list -about collaboratively writing a wxWindows book. The book will +August 2000: the 'wxBook' project is getting going again, +with a good response from potential contributors.

+ +Robin Dunn has set up a wxBook mailing list.

+ +The book will comprise 30 or so chapters dealing with progressively +more advanced areas of wxWindows; each chapter will be as stand-alone as +possible. The book will not include the API reference, though this could be a separate project. The book will be accompanied by a CD-ROM with -wxWindows and its documentation. The book will initially be +wxWindows and its documentation. It will initially be available on-line, and when enough is done we will look for a publisher.

@@ -66,7 +76,9 @@ knowledge.

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.

+


+

Participants

@@ -80,7 +92,8 @@ chapters. communication classes (wxSocket, wxXXXServer, some protocol stuff); timing and timers.
  • Robin Dunn - wxPython chapter. -
  • Vadim Zeitlin - drag and drop chapter? +
  • Vadim Zeitlin - drag and drop, several other chapters. +
  • Robert Roebling - not known.
  • Vaclav Slavik - wxHTML section.
  • George Tasker - database chapter.
  • Carlos Moreno - wxImage, wxBitmap. @@ -112,12 +125,19 @@ strategies, etc. --> +

    +Others welcome! Please contact Julian Smart +if you would like to contribute. + +


    +

    Publication

    -We should have a substantial chunk of wxBook done before we approach a publisher, -because with the risks of multiple author +We wll investigate publishers, especially O'Reilly. We will have to get together +several sample chapters to convince a publisher that the many-author approach will +work.

    + +


    +

    + + + +

    File format

    + +Possible formats: + + + +


    +

    -

    Text format

    +

    Style guide

    -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.

    +We should write a style and formatting guide.

    +


    +

    + +

    Book Titles

    + +It would be good to include certain buzzwords such as Linux and open source, to get +a publisher's (and the potential reader's) attention. The trick is to do that and +not narrow the scope unduly.

    + +Suggestions for the main book:

    + +

    + +

    +Other book titles that a publisher might be interested (but would be distinct projects):

    + +

    + +

    +


    +

    Contents

    -This is open to suggestion.

    +The following is open to discussion.

    -Last year, Mike Lorenz of VisionX -suggested this -tutorial outline, which could -be a good starting point.

    +