Development/Tools: Difference between revisions

Revision as of 18:12, 29 December 2006

This section contains information about tools for KDE development.

Analysis

A list of tools which are used to analyze a program. This includes debuggers and profilers, for instance.

Valgrind

Valgrind helps to find memory leaks and uninitialized memory blocks. Additional features are a profiler and more. Valgrind is one of the most important development tools!

The GNU Project Debugger (GDB)

GDB helps in debugging source code. As GDB evolved over time it is recommended to use version 6.x. Graphical frontends are available (see below). See also the debugging tutorial Debugging with GDB.

KDbg

KDbg is a graphical user interface to GDB, which is able to set breakpoints, step through the code etc.

KDevelop

KDevelop is an excellent IDE for developing KDE and Qt C++ applications. It includes a an integrated debugger, a powerful editor with syntax highlighting, a Project wizard to create applications from templates, the automake/autoconf gunk, and even the class documentation. Further details can also be found in the KDevelop wiki.

Qt Designer

With Trolltechs Qt Designer it is easy to layout user interfaces like buttons and checkboxes. Additional features are undo/redo, checking accelerator conflicts etc. Qt Designer allows even non-programmers to help design KDE dialogs.

Internationalisation (i18n) Tools

You can find information on writing and translating documentation on this dedicated site.

@@ Line 5: / Line 5: @@
 === Valgrind ===
-[[/Valgrind|Valgrind]] helps to find memory leaks and uninitialized memory blocks. Additional features are a profiler and more. Valgrind is one of the most important development tools!d
+[[/Valgrind|Valgrind]] helps to find memory leaks and uninitialized memory blocks. Additional features are a profiler and more. Valgrind is one of the most important development tools!
 === The GNU Project Debugger (GDB) ===