From kde-devel  Mon Jul 21 10:29:00 2003
From: Ralf Nolden <nolden () kde ! org>
Date: Mon, 21 Jul 2003 10:29:00 +0000
To: kde-devel
Subject: Re: new KDE Development book
X-MARC-Message: https://marc.info/?l=kde-devel&m=105878419107951
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============027838006779487001=="


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


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

On Montag, 21. Juli 2003 10:17, Brad Hards wrote:
> On Mon, 21 Jul 2003 16:14 pm, Ralf Nolden wrote:
> > Now, enough talk. Should we get going with a separate CVS module or
> > should we start in kdenonbeta first ?  (where I don't have a good feeli=
ng
> > that too many people would put their stuff there :) so a kde-books
> > (because the contents will span more than one book I guess :-) module is
> > probably the best way to go. Any volunteers for generating the automake
> > framework and putting it in CVS ? BTW this would also have the advantage
> > that we could make exercise programs *inside* this module and one can
> > compile the book together with the exercises :))
>
> Before we code our book, perhaps a bit of design and coding standards wor=
k.
>
> Assuming DocBook, I imagine that we are talking about
> Book
> Part
> Chapter
> Section1
> Section2
>
> What stuff belongs at what level? For example, there was discussion of a
> C++ intro - where does that go?

I've been talking with clee on IRC this morning and I think actually we'll=
=20
have more than one "book". We need one for C++, one for Qt and one for each=
=20
library, starting with turning a Qt example program from the Qt book into a=
=20
KDE program with QApplication -> KApplication and QSettings -> KConfig, tr(=
)=20
=2D> i18n(), all in the KDE Core book. Then comes DCOP, KDE UI, etc.

The reason for this is also that this needs to be maintainable alongside an=
y=20
API changes and conceptual changes so a book per library seems to be the be=
st=20
solution.

Ralf

 What about the PyKDE description? How do we
> fit in stuff like:
> http://developer.kde.org/documentation/tutorials/dot/panel-applets.html or
> http://developer.kde.org/documentation/tutorials/dot/dcopiface/dcop-inter=
fa
>ce.html (assuming that the authors agree to licensing and re-use).
>
> Which DocBook? XML or SGML?
>
> How do authors get recognised? What about editors, reviewers and
> contributors?
>
> Do we include compilable examples (as opposed to fragments) as inline, or
> do we use hacks like:
> <example><title>Basic example</title>
> <programlisting>
> <inlinegraphic fileref=3D"examples/example.c" format=3D"linespecific">
> </programlisting>
> </example>
>
> What license do the examples fall under? Can readers use bits of them in
> proprietary or BSD licensed code?
>
> [Yep, I'm excited by the concept too!]
>
> Brad

=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=_0B8G/EIjt1okxqg
Content-Type: application/pgp-signature
Content-Description: signature

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

iD8DBQA/G8B0u0nKi+w1Ky8RAvvSAJ4pkBBPlddU/PDhzShaL3U8skUlDgCfaRSm
d6reKUfpjH5CDojZp4s6RqU=
=eaIV
-----END PGP SIGNATURE-----

--Boundary-02=_0B8G/EIjt1okxqg--


--===============027838006779487001==
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 <<

--===============027838006779487001==--