Development/Tools (ru)

Development/Tools

Эта глава содержит информацию о инструментах для разработчика KDE.

Анализ и отладка

Список инструментов, которые могут быть использованы для анализа программы. Он включает в себя отладчики, профилировщики и т.д.

Valgrind: Valgrind помогает находить утечки памяти и неинициализированные блоки памяти. В дополнении к этому он обладает функцией профилирования и многими другими. Valgrind - один из самых важных инструментов разработчика.

The GNU Project Debugger (GDB): GDB помогает отлаживать исходный код. 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 это графический интерфейс к GDB, который также умеет устанавливать точки останова, отлаживать код по шагам и т.п.

Инструменты разработчика

KDevelop: KDevelop - это превосходная интегрированная среда для разработки KDE и Qt приложений с использованием языка C++. Она включает в себя отладчик, мощный редактор с подстветкой синтаксиса, Project wizard для создания приложений из шаблонов, automake/autoconf gunk и даже class documentation. Более подробную информацию вы можете найти на KDevelop wiki.

Инструкции к использованию KDevelop с приложениями KDE 4 доступны на этой странице

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.

MS Visual Studio® Express 2005 IDE (только для Windows): Visual C++® 2005 Express Edition [1] - это бесплатная версия Microsoft Visual Studio 2000 compiler от Microsoft, которая официально поддерживается компанией Trolltech с момента выхода QT 4.3.2 как инструмент для компиляции qt и kde приложений для windows.

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: Эта маленькая утилита, once activated, can present a report about conflicting shortcuts in menus. Это полезно не только для переводчиков, но и для разработчиков. 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.

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