From kde-devel  Sun Apr 30 16:45:23 2006
From: Kevin Krammer <kevin.krammer () gmx ! at>
Date: Sun, 30 Apr 2006 16:45:23 +0000
To: kde-devel
Subject: Re: Developing at ten?
Message-Id: <200604301845.23684.kevin.krammer () gmx ! at>
X-MARC-Message: https://marc.info/?l=kde-devel&m=114641557013598
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============1006109165=="

--===============1006109165==
Content-Type: multipart/signed;
  boundary="nextPart3946325.lBgmPyPWsc";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart3946325.lBgmPyPWsc
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Sunday 30 April 2006 18:20, Allan Sadun wrote:
> I would like to start developing for KDE, and I can't figure out if I can,
> and if so, how I can. I've read the "How to Help" page, and it hasn't
> really helped me. This dilemna has lead to a lot of questions; can anyone
> answer them?
>
> 0. Is this the right place to ask these questions?

Yes, definitely

> 1. What do I need to know?

Depends on what you want to do.
=46or example applications can be created in a couple of programming langua=
ges=20
through our language bindings so it is not necessary to know a specific=20
programming language.
Developing KDE libraries not only requires to know C++ but also to know qui=
te=20
a lot about software engineering theory.

> 2. What applications/languages should I use?

Beginners usually find it easier to use an IDE, for example KDevelop or=20
Eclipse, sometimes working with an advanced text editor like Kate, Emacs or=
=20
VIM is personally preferred by some developers.

The choice of language depends on what you like best and what you like to w=
ork=20
on (see above), for example writing SuperKaramba themes requires Python.

> 3. What part of KDE should I work on?

=46rom my exerience I'd start with a simple application, toying around with=
 KDE=20
features. Unless you are very new to a programming language then my advise=
=20
would be to start language tutorials and later come back to KDE.

> 4. Am I too young to start developing? (I'm only 10)

I guess it is a matter of being able to understand concepts, usually but no=
t=20
necessarily tied to age.
As long as you have fun doing it, you should be doing it.

> 5. How much experience do I need?

See answer to (1)

> 6. Do I write .diff files, .cpp files, both, or others?

=2Ediff files are always generated, you'll write source files

> 7. When I'm done, how do I get it into KDE?

Depends what you mean with "get into"

Cheers,
Kevin
=2D-=20
Kevin Krammer <kevin.krammer@gmx.at>
Qt/KDE Developer, Debian User
Moderator: www.mrunix.de (German), www.qtcentre.org

--nextPart3946325.lBgmPyPWsc
Content-Type: application/pgp-signature

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

iD8DBQBEVOmjnKMhG6pzZJIRAn5pAJ0Y0WgtxsW7FcoUzGs+Drr7OVqCLwCfWyvO
JEZtOfcnV6ZAVRnPKWxvBGA=
=GggT
-----END PGP SIGNATURE-----

--nextPart3946325.lBgmPyPWsc--

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

--===============1006109165==--