Difference between revisions of "Contribute/nl"

Jump to: navigation, search
(Updating to match new version of source page)
(Created page with "Als de KDE-applicatie crasht tijdens het gebruik, dan verschijnt een '''Dr Konqi'''-venster, dat u door het proces zal loodsen om de crash te rapporteren. Lees hier meer over ...")
Line 29: Line 29:
De gemakkelijkste manier om aan KDE bij te dragen is om [http://userbase.kde.org/Asking_Questions#Reporting_KDE_Bugs fouten te rapporteren] die u vindt in KDE met behulp van het [https://bugs.kde.org/ KDE-foutensysteem] (ook bekend onder de naam '''Bugzilla''').
De gemakkelijkste manier om aan KDE bij te dragen is om [http://userbase.kde.org/Asking_Questions#Reporting_KDE_Bugs fouten te rapporteren] die u vindt in KDE met behulp van het [https://bugs.kde.org/ KDE-foutensysteem] (ook bekend onder de naam '''Bugzilla''').
If the application you are using crashes then the '''Dr Konqi''' utility will appear and guide you through the process of reporting the crash. Learn more by reading  [[Development/Tutorials/Debugging/How_to_create_useful_crash_reports|how to create useful crash reports]].
Als de KDE-applicatie crasht tijdens het gebruik, dan verschijnt een '''Dr Konqi'''-venster, dat u door het proces zal loodsen om de crash te rapporteren. Lees hier meer over op de pagina [[Development/Tutorials/Debugging/How_to_create_useful_crash_reports|hoe een nuttig crash-rapport te maken]].
== Getting Started with Coding ==
== Getting Started with Coding ==

Revision as of 20:12, 16 November 2012

Other languages:
Ελληνικά • ‎English • ‎español • ‎suomi • ‎français • ‎galego • ‎日本語 • ‎한국어 • ‎Nederlands • ‎polski • ‎português do Brasil • ‎slovenčina • ‎中文(中国大陆)‎

Deze pagina geeft een overzicht van de verschillende aspecten van het bijdragen aan KDE, met name voor de programmeertaken. Het KDE-project is blij met iedereen die meehelpt.

Er zijn vele manieren om mee te doen aan de ontwikkeling van KDE, die kunnen worden onderverdeeld in de volgende categorieën:
documentatie, vertaling, ontwikkeling, gebruiksvriendelijkheid, toegankelijkheid, uiterlijk, promotie
Kunt u niet programmeren? Zie KDE's pagina's over hoe u kunt meedoen om andere manieren te ontdekken om mee te helpen. Zie ook: Bugsquad!

Nieuws en mailbronnen

De richting waar het KDE-project heengaat, wordt bepaald door degenen die het werk doen - er is geen eenduidig plan over hoe KDE er in de toekomst uit zal zien.

Als u wilt ontdekken wat er momenteel wordt gedaan, dan is er een aantal bronnen die u kunt gebruiken:

Waarschijnlijk de beste manier om uit te vinden wat er momenteel gebeurt rondom de KDE-ontwikkeling. Er zijn hier archieven beschikbaar.
Ontvang berichten over wijzigingen aan de broncode van KDE in gebieden die u interessant vindt.
KDE Commit-Digest
Een wekelijkse samenvatting van broncodewijzigingen aan KDE.
The Dot
De nieuwssite over KDE.

Fouten rapporteren

De gemakkelijkste manier om aan KDE bij te dragen is om fouten te rapporteren die u vindt in KDE met behulp van het KDE-foutensysteem (ook bekend onder de naam Bugzilla).

Als de KDE-applicatie crasht tijdens het gebruik, dan verschijnt een Dr Konqi-venster, dat u door het proces zal loodsen om de crash te rapporteren. Lees hier meer over op de pagina hoe een nuttig crash-rapport te maken.

Getting Started with Coding

Getting started at coding for KDE is a matter of finding something to fix, and fixing it. You may want to consult the module overview to help find what you are looking for; once you have fixed something, you will want to send in a patch. If you do that a few times, you may want to apply for a KDE Contributor account so you can improve things directly.


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.


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 Reference Documentation.

If you need a gentler introduction to Qt, or would just like an alternative view, then you may wish to look at the Foundations of Qt Development.

If you prefer to learn Qt by reading a traditional book, take a look at the Books about Qt page. More suggestions on becoming familiar with Qt4 are available How to Learn Qt page.


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 API Reference.

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

Context Help: Whatsthis

Context help is inseparable from the dialogs and widgets, as they are the target of the context help. In fact, in order to write context help, you have to touch programming or programming tools. Indeed, the context help is a property of widgets. In object oriented programming, a property can have different values, and behave differently depending on the value. In Qt/KDE programming, the name of the property is "whatsthis", and its value is the text the context help is going to display.

Fortunately, this task is usually not very difficult, as there are good tools to deal with user interface design, and better, you will use the knowledge acquired here later when dealing with user interface in general. Using the Qt framework (Qt is the base of KDE technology), it is possible to separate code and user interface. You have two basic cases here: the user interface is written with the general code of application (usually .cpp files) or in Qt Designer files (.ui files: it is a XML document). The second case is the best to start with, as it is simpler to work with. If you don't have Qt Designer installed, you can do so by installing the devel package of Qt from your distribution or the Qt Designer package (if your distribution has more fine grained packages).

Here you can find a detailed guide for writing whatsthis using Qt Designer and working directly with the source code: WhatsThis Tutorial, by Aaron J. Seigo.

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, becoming a member of the KDE Quality Team might appeal to you - see the Quality Team website for more information. Note that you do not need any programming skills to become involved. In particular developers regularly 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.

User Interface

User interface is a very wide subject, and very subjective too, as something obvious to someone is absurd to others and vice versa. Therefore, don't assume, argue clearly, stating your logical steps. Your main tool discussing it are objective reasoning and good sense.

It is easy to perform a quick user interface analysis, but it is hard to convince people to change the interface. A good, convincing analysis can gain much if it incorporates information from the KDE guidelines, competing program and operational system analysis, general design principles found in many books, user testing or individual (anecdotal) feedback. It is a volunteer project, and even if everybody agree with you, someone has to implement it.

The KDE Usability Mailing List is very active and a good place for discussing your ideas, and their homepage is at http://techbase.kde.org/Projects/Usability. If you are already an usability expert, please check OpenUsability.org, a project that brings open source developers and usability experts together, and is collaborating closely with KDE.

Some documents guiding documents include the KDE User Interface Guidelines (design standards) and KDE User Interface Guidelines (design principles).

Some projects for analysis of user interfaces may include: checking that shortcut keys are coherent across KDE applications, making sure that dialogs are directly relevant to the interaction that the user would expect, and finding users of KDE software to see how they perform common workflows.

Getting Answers to Your Questions

If your question concerns KDE development, your options are pretty much the same general user ones, with some modifications:

  • Read the Developer FAQ. Many common developer questions have been answered in the KDE Developer FAQ
  • Search/browse KDE websites. A lot of questions can also be answered from the KDE websites, and the documentation included on it. You can search all the KDE websites on the homepage. In addition, you can browse the KDE TechBase website. And if possible, help edit it for clarity, and use the talk page if something is unclear.
  • Search mailing lists. A lot of questions have already been answered on the KDE mailing lists, particular the lists kde-devel, kde2-porting, kde-core-devel, kde-games-devel, kfm-devel and koffice-devel. You can search these lists either at lists.kde.org. You should always search for your answer before asking questions on the mailing lists. When you ask a question on a mailing list you are emailing thousands of people -- please do this only if the answer is not available through a simple search.
  • Search engines. Do not forget about your favorite search engine. One of the best search engines is Google. With Google you can also search the great bulk of Usenet news sites, which is also particularly helpful, especially for general programming and gcc-related questions.

A full list of KDE mailing lists is available here and here.