[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: new KDE Development book
From:       Karl-Heinz Zimmer <khz () kde ! org>
Date:       2003-07-21 6:35:09
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 21 July 2003 08:14, Ralf Nolden wrote:
> On Sonntag, 20. Juli 2003 14:56, Reinhold Kainhofer wrote:
> > Holger Schroeder wrote:
> > > it would be cool, if this book would evolve to something like _the
> > > book_ for everything kde.
>
> That's the idea :) History, implementation, concepts, detailed
> description, reference guide. Something like MSDN for KDE :)

Smileys seen but still wondering: Did you mean this seriously?

If yes please note that the MSDN is far more than a book but a structured
collection of different kinds of information, including API 
documentations, manuals, tutorials, FAQs, HOWTO-like articles, in-deepth
technical articles, small and middle sized online books, and more... all
searchable in different ways.

While I am /not/ a happy Microsoft programmer I still think the MSDN 
designers could have been made a far worse job: IMO this is one of the
not so bad things produced by Microsoft.

However making something similar for KDE would be kind of a meta project: 
the question would rather be "How to design and set up a framework 
bundling the different pieces of information that are there already?".

Of course this does not mean your idea of writing a KDE C++ learners book
is not fine (I appreciate this idea very much) but this is a different
idea than creating an MSDN-like think for KDE developers.

So what to do first?   Write the book or make the framework?

Since the book would be one part of the framework it could be even done
in parallel but of course that would require more work at the same time.

The book would still be very useful if concentrating on its prio #1 goal:
a C++ learners book based on the KDE C++ API.

So one option /might/ be to just start writing the content book - 
ignoring the technical issues for now and building the framework later, 
once the content is there.
Otherwise it might happen that you run into trouble because 100s of 
different side-effect issues showing up that have to do with the 
organisation of the stuff _around_ the book rather than finding good 
content for _inside_ the book... give your surely limited ressources 
this might lead to the project being paralized.

Please think about this and (in case you agree to me) let us perhaps 
start with thinking about the structure of the book, deciding the 
content of some of the chapters and asking who could write which of 
these chapters.

Just my 2 pence.

Karl-Heinz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/G4mdCcaVnbvggDcRAusLAJ4+yKL4waaYn+127Jcyu++GHkt5lACgySxe
nmYLCh3BC8rLZyoOpurI+r0=
=K5Wl
-----END PGP SIGNATURE-----

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]