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

List:       kde-devel
Subject:    Re: new KDE Development book
From:       Ralf Nolden <nolden () kde ! org>
Date:       2003-07-18 17:51:10
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Freitag, 18. Juli 2003 08:29, André Somers wrote:
> Hi,
>
> >So, target is: FDL-licensed book that can be published on
> > developer.kde.org, covering:
> >
> >- C++
>
> Why do you want to cover C++? There are lots of books about that allready.
> I think it makes your otherwise very usefull project a bit too ambitous. I
> fear it would end up covering too much in too little detail to be usefull.

My experience is different. What I would like is a "one book for everyone" (or 
a couple of books if you want to say so). The C++ part is explained directly 
with Qt/KDE, pointing out directly where Qt/KDE extends the C++ standard.

>
> >- Qt 3.2
>
> Sure, an introductio to Qt would be nice. Explain the basics, stuff like
> using inheritance and the signal/slot stuff. And, very important: tell them
> how to use the Qt documentation. I have found that the documentation of
> most of the Qt classes is very good, and if you get the basics and know how
> to find your way, it's enough to get you going.
Yes and no. You have a point but I'm thinking of an in-depth technical 
reference coverage like event handling and so forth. This is actually our 
binding to X (and other windowing systems) and it would help the people 
answer their basic question: when do I have to use Qt and when KDE classes ?

>
> >- KDE 3.2
>
> Could you give some examples on stuff you want to focus on here?

Also starting from KApplication, KConfig over to KAction, KParts and so forth. 
In the end we'll have a *full* KDE libs book that explains concepts and the 
way how things work technically so you don't have to read the kdelibs code to 
understand things. Of course KParts, KOffice, Konqueror are also on topic. In 
short: the complete KDE infrastructure in 3.2 and what KDE provides. We'll 
end up with something like "The Komplete KDE Desktop Reference".

BTW I already *know* that this is a tremendous amount of work but it is a good 
project that's worth doing it. And of course, it can't be done by one person 
alone, that's why I want it to be a community project from the beginning, not 
from when a book is published and then say "please help keep it up to date" - 
that didn't work out with the KDE 2 Development book *at all* because the 
whole writing was very frustrating for the authors already.  This time we 
have a chance to make this a really long-term project that we can continue 
even after KDE 4 will be out and keep it up to date because it will be a part 
of KDE from the beginning.

Ralf


>
> >If you have any ideas, let me know.
>
> André
>
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
> >> unsubscribe <<

-- 
We're not a company, we just produce better code at less costs.
--------------------------------------------------------------------
Ralf Nolden
nolden@kde.org

The K Desktop Environment       The KDevelop Project
http://www.kde.org              http://www.kdevelop.org

[Attachment #5 (application/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]