--===============62053053090170041==
Content-Type: multipart/signed;
  protocol="application/pgp-signature";
  micalg=pgp-sha1;
  boundary="Boundary-02=_OODG/os5lppw4Jz";
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit


--Boundary-02=_OODG/os5lppw4Jz
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Description: signed data
Content-Disposition: inline

On Freitag, 18. Juli 2003 08:29, Andr=E9 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=20
a couple of books if you want to say so). The C++ part is explained directl=
y=20
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 th=
em
> 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 h=
ow
> 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=20
reference coverage like event handling and so forth. This is actually our=20
binding to X (and other windowing systems) and it would help the people=20
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 for=
th.=20
In the end we'll have a *full* KDE libs book that explains concepts and the=
=20
way how things work technically so you don't have to read the kdelibs code =
to=20
understand things. Of course KParts, KOffice, Konqueror are also on topic. =
In=20
short: the complete KDE infrastructure in 3.2 and what KDE provides. We'll=
=20
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 g=
ood=20
project that's worth doing it. And of course, it can't be done by one perso=
n=20
alone, that's why I want it to be a community project from the beginning, n=
ot=20
from when a book is published and then say "please help keep it up to date"=
 -=20
that didn't work out with the KDE 2 Development book *at all* because the=20
whole writing was very frustrating for the authors already.  This time we=20
have a chance to make this a really long-term project that we can continue=
=20
even after KDE 4 will be out and keep it up to date because it will be a pa=
rt=20
of KDE from the beginning.

Ralf


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

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

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

--Boundary-02=_OODG/os5lppw4Jz
Content-Type: application/pgp-signature
Content-Description: signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQA/GDOOu0nKi+w1Ky8RAuwAAJwJ4TMsHDV+dDkOCqxaWWkzyM3FZACfRBRK
gg2FHj6cw4UAe+vmAPXUZ7Q=
=pjZp
-----END PGP SIGNATURE-----

--Boundary-02=_OODG/os5lppw4Jz--


--===============62053053090170041==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============62053053090170041==--