Contribute (sr)

Revision as of 13:22, 21 May 2008 by Ushtipak (Talk | contribs)

Jump to: navigation, search


Contents

Contribute

Namena ove strane je prikaz različitih aspekata razvoja KDE okruženja, naročito u vezi sa programiranjem. KDE projekat rado prihvata svakoga ko je spreman da doprinese.

noframe
 
Note
Postoji veliki broj načina na koje se možete uključiti u razvoj KDE okruženja:
Dokumentacija, Prevođenje, Razvoj, Primena, Pristupačnost, Dizajn, Promocija

Niste programer? Pogledajte KDE stranicu uključite se i Vi, da vidite na koje sve načine možete pomoći.

Takođe pogledajte: Odred za suzbijanje bagova!

Vesti i Mejl liste

Generalni pravac KDE projekta određuju ljudi koji rade na njemu - ne postoji jedinstveni plan na "višem nivou" kako će KDE izgledati u budućnosti.

Ako želite da saznate šta se trenutno događa, evo nekoliko izvora koje možete da uzmete u razmatranje:

Mejling liste
Verovatno najbolji način da saznate šta se događa u razvoju KDE okruženja. Dostupne su i arhive.
CommitFilter
SVN obaveštenja iz oblasti koje Vas zanimaju.
KDE Commit-Digest
Nedeljni SVN izveštaji.
"The Dot"
Sajt za KDE vesti.

Počnite sa programiranjem

Ovde se podrazumeva pronalaženje određenog segmenta kome je neophodna popravka - i popravljanje istog! Možda želite da pregledate modularni prikaz kako biste pronašli ono što tražite, jer kada nešto popravite, poželjno je da ga pošaljete u formi "zakrpe". Ukoliko to radite učestalo, možete se prijaviti za SVN nalog kako biste bili u prilici da popravke vršite direktno.

Trenutno postoje dva različita segmenta u KDE razvoju - možete raditi na KDE3 ili na KDE4 okruženju. KDE3 je dobar izbor za popravke bagova, dok se glavni razvojni zadaci (zajedno sa svim novim funkcijama) obavljaju u KDE-u 4. Ovaj konkretan dokument se usredsređuje na KDE4 podršku.

C++

KDE is mostly written in C++. If you are not familiar with C++, you should do at least some work on it. There are a number of good books on C++ - an excellent source is Bruce Eckel's "Thinking in C++", which is available both as a free download and as a printed document. It isn't essential to understand everything before you start in KDE, but you do need to understand basic syntax and operations.

Qt

To become proficient with KDE coding, you should understand the Qt toolkit. If you are not familiar with Qt, you should work through the tutorials included with Qt (Qt4 version, Qt3 version).

If you are more into multimedia and videos for a start you might want to spend two amazing minutes on watching Building a Simple Help Documentation Browser with Qt4 Designer. If that got your attention you might also want to watch the video introduction Hello Qt by Mark Summerfield which is part of the Trolltech Developer Days 2006 presentations.

If you need a gentler introduction to Qt, or would just like an alternative view, then you may wish to look at the The Independent Qt Tutorial (Currently offline due to book contract).

If you prefer to learn Qt by reading a traditional book, take a look at Trolltechs book page. More suggestions on becoming familiar with Qt4 are available here as well.

KDE

A range of information on KDE techniques is available in the tutorial section. Note that some of these tutorials still target KDE3, though they should be at least partly applicable.

You will also find useful information on KDE coding in the FAQs section. This information may also be somewhat dated for KDE4, however much of it is broadly applicable, even outside KDE.

You can also read KDE coding books.

Last, but by no means least, KDE comes with extensive class (Application Programmer Interface) documentation. This is available in the KDE API Reference Manuals section, which also contains a number of useful links on how to write or update the class documentation. You can also generate these on your own machine, or refer to a more up-to-date online version at The English Breakfast Network.

A more detailed description of the steps above is available in our Programming Guide.

Getting Involved in Bug Hunting and Application Quality

There is a large number of applications within KDE, and not all of them have a maintainer dedicated to managing bugs and generally helping out with all the issues associated with turning some working code into a polished application.

If you are interested in helping out with KDE, but don't know where to start, visit Contribute Website for more information. Note that you do not need any programming skills to become involved. In particular develpers regurarly publish so-called Junior Jobs to encourage new contributions.

Of course, you can become involved in bug hunting without being part of the KDE Quality Team - just create yourself an account on the KDE bug tracking system, and start searching / sorting through the bugs. Again, you don't have to have programming skills - it helps the programmers enormously just to have a procedure that allows a bug to be consistently reproduced.

The Bugsquad tries to keep track of bugs in KDE software and make sure that valid bugs are noticed by developers. You do not need any programming knowledge to be in the Bugsquad; in fact it is a great way to return something to the KDE community if you cannot program.

Historical Sources

KDE Traffic
Summary of the development mailing lists. KDE Traffic ran for 76 issues, from 10 March 2001 until 16 April 2004. The KDE Commit-Digest (described above) is its logical successor.

KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal