Development/Tools: Difference between revisions
m (s/''//g) |
(new structure, much better; some port-todos) |
||
| Line 1: | Line 1: | ||
This section contains information about tools for KDE development. | This section contains information about tools for KDE development. | ||
== Analysis == | == Debugging and Analysis == | ||
A list of tools which are used to analyze a program. This includes debuggers and profilers, for instance. | A list of tools which are used to analyze a program. This includes debuggers and profilers, for instance. | ||
; 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! | : [[/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) | |||
[http://sources.redhat.com/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 [[../Tutorials/Debugging/Debugging with GDB|Debugging with GDB]]. | : [http://sources.redhat.com/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 [[../Tutorials/Debugging/Debugging with GDB|Debugging with GDB]]. | ||
; KDbg | |||
[http://www.kdbg.org/ KDbg] is a graphical user interface to GDB, which is able to set breakpoints, step through the code etc. | : [http://www.kdbg.org/ KDbg] is a graphical user interface to GDB, which is able to set breakpoints, step through the code etc. | ||
== | == Development Tools == | ||
[http://www.kdevelop.org 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 [http://kdevelop.org/mediawiki/index.php/Main_Page KDevelop wiki]. | ; KDevelop | ||
: [http://www.kdevelop.org 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 [http://kdevelop.org/mediawiki/index.php/Main_Page KDevelop wiki]. | |||
; Qt Designer | |||
With Trolltechs [http://www.trolltech.com/products/qt/features/designer 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. | : With Trolltechs [http://www.trolltech.com/products/qt/features/designer 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. Further details can be found in the tutorial [[Development/Tutorials/Using_Qt_Designer|Using Qt Designer]] and in the [http://doc.trolltech.com/4.2/designer-manual.html Qt documentation]. | ||
== Internationalisation (i18n) Tools == | == Internationalisation (i18n) Tools == | ||
Information on writing and translating documentation can be found on [http://i18n.kde.org/ the i18n project site]. | |||
== Helper Tools == | |||
; [[/Using kde-config|Get information about KDE's installation - kde-config]] ([http://developer.kde.org/documentation/other/kde-config.html port me!]) | |||
: The tool kde-config helps to find out more about a KDE installation. | |||
; [[/Using kfmclient|Driving Konqueror From Scripts - kfmclient]] ([http://developer.kde.org/documentation/other/kfmclient.html port me!]) | |||
: kfmclient is a small tool to communicate with Konqueror. | |||
Revision as of 22:01, 29 December 2006
This section contains information about tools for KDE development.
Debugging and 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.
Development Tools
- 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. Further details can be found in the tutorial Using Qt Designer and in the Qt documentation.
Internationalisation (i18n) Tools
Information on writing and translating documentation can be found on the i18n project site.
Helper Tools
- Get information about KDE's installation - kde-config (port me!)
- The tool kde-config helps to find out more about a KDE installation.
- Driving Konqueror From Scripts - kfmclient (port me!)
- kfmclient is a small tool to communicate with Konqueror.