Development/Tools (es)

Development/Tools

Esta sección contiene informacion sobre las herramientas para el desarrollo de KDE.

Depurado y análisis

Lista de herramientas usadas para analizar un programa. Incluye depuradores y perfiles (profilers), por ejemplo:

Valgrind: Valgrind te ayuda a encontrar fugas de memoria y bloques de memoria sin inicializar. Como funcionalidades avanzadas tenemos un profiler y más. Valgrind es una de las herramientas de desarrollo mas importante!.

The GNU Project Debugger (GDB): GDB te ayuda a depurar código fuente. Como GDB está siendo desarrollado todo el tiempo, es recomendable usar la versión 6.x. Exiten interfaces de usuario. Mira también el tutorial de depurado Debugging with GDB.

KDbg: KDbg es una interfaz gráfica de usuario de GDB, con la cual puedes establecer breakpoints, ir paso a paso a traves del código etc.

MS Windows tools (Process Explorer, Console, WinDbg, DebugView...): Mas información en KDE on Windows page.

Herramientas de desarrollo

KDevelop: KDevelop es un excelente IDE para el desarrollo de aplicaciones KDE y Qt en C++. Incluye un depurador integrado, un potente editor con realce de sintaxis, un Project Wizard para crear aplicaciones desde plantillas, automake/autoconf, e incluso la documentación de clases. Puedes encontrar mas detalles en KDevelop wiki.

Las instrucciones sobre como usar KDevelop con aplicaciones KDE4 están disponibles en this page.

Qt Designer

Con Trolltech Qt Designer es facil diseñar interfaces con botones y "checkboxes". Tiene características adicionales como deshacer/rehacer,comprobación de conflictos etc. Puedes encontrar mas detalles en el tutorial Using Qt Designer y en documentación de Qt.

MS Visual Studio® Express 2005 IDE (solo Windows): Visual C++® 2005 Express Edition [1] is the free version of the Microsoft Visual Studio 2005 compiler from Microsoft, which is officially supported by Trolltech since Qt 4.3.2. It is a choice for compiling Qt and KDE applications on Windows. more info...

Internationalization (i18n) Tools

KBabel: KBabel is a set of tools for editing and managing gettext PO files. Its main part is a powerful and comfortable PO file editor which features full navigation capabilities, full editing functionality, possibility to search for translations in different dictionaries, spell and syntax checking, showing diffs and many more.

Also included is a "Catalog Manager", a file manager view which helps in keeping an overview of PO files. Last but not least it includes a standalone dictionary application as an additional possibility to access KBabel's powerful dictionaries. KBabel will help you to translate fast and also keep consistent translations.

Dr. Klash: This little utility, once activated, can present a report about conflicting shortcuts in menus. Not only is this helpful for translators but also for developers. A little hand editing of `kde-config --localprefix`/share/config/kdeglobals activates this feature:

[Development] CheckAccelerators=F12 AutoCheckAccelerators=false AlwaysShowCheckAccelerators=false

Pressing F12 will show a dialog containing which accelerators in the currently focussed interface conflict and provide suggestions for new accelerators. If no accelerators conflict or Dr. Klash has nothing to suggest, no popup dialog will be displayed.

With AutoCheckAccelerators enabled the dialog will popup automatically if a conflict exists and AlwaysShowCheckAccelerators can force the dialog to always popup even if there are no conflicts to report.

The x-test language: This helper language serves as a debugging aid for people finding untranslated strings in applications. If you start your application with the "x-test" locale, all translated strings will appear with trailing and leading xx's. First you have to check out these "translations" from l10n-kde4/x-test and install them.

After you've built l10n-kde4/x-test and installed it, run your application using the "x-test" locale. This can be done by launching it from the command line like this:

> KDE_LANG=x-test kspread

This will start KSpread using the "x-test" locale no matter what your current language setting is. Look for strings that do not have the xx's. If xx's are missing from a string, it could be due to missing i18n calls or even missing or incorrectly generated .pot files. Consult the i18n tutorials for further information.

When checking for untranslated strings, be sure to check all the WhatsThis help and tooltips.

Examining .po files

You can look at the translated .po files to see if a string is present and has been translated. For example, here's a portion of l10n/de/messages/kdebase/konqueror.po:

#: konq_mainwindow.cc:3707 konq_tabs.cc:84
msgid "&New Tab"
msgstr "Neues &Unterfenster"

The string to be translated is given on the msgid line. The translated string is on the msgstr line. Notice that the exact same string to translate came from konq_mainwindow.cc and also from konq_tabs.cc. This saves the translators from having to translate the same identical string twice.

You can also use KBabel to examine .po files. KBabel is part of the kdesdk module.

Note

More information on writing and translating documentation can be found on the l10n project site.

Helper Tools

Get information about KDE's installation - kde-config: The tool kde-config helps to find out more about a KDE installation.

Driving Konqueror From Scripts - kfmclient: kfmclient is a small tool to communicate with Konqueror.

Updating User Configuration Files - kconf_update: kconf_update is a tool designed to update config files.

Generating apidox: tools that help develop and generate API documentation for your code.

Automoc4: This is a helper tool needed to build KDE4. It automatically generates moc-files.

Quality Assurance

Continuous Building - Dashboard: all kde modules on Dirk's dashboard; kdelibs on kitware

English Breakfast Network - Static Analysis: Krazy - Code Analysis, Usage Tutorial; APIDOX - API Documentation Statistics; Sanitizer - DocBook Checker; Usability Checks