View source for Development/Tools (pt BR)

{{Template:I18n/Language Navigation Bar|Development/Tools}}
Esta sessão contém informação sobre ferramentas para desenvolvimento do KDE.

== Depuração e Análise ==
Uma lista de ferramentas as quais são usadas para analisar o programa. Nesta categoria estão depuradores e ferramentas de acompanhamento de performance, por exemplo.

; Valgrind
: [[Development/Tools/Valgrind (pt_BR)|Valgrind]] ajuda a encontrar vazamentos de memória e blocos de memória não iniciados. Características adicionais são um medidor de performance entre outras. Valgrind é umas das ferramentas de desenvolvimento mais importantes!

; O GNU Project Debugger (GDB)
: [http://sources.redhat.com/gdb/ GDB] ajuda a depurar o código fonte. Como o GDB evoluiu ao longo do tempo é recomendado usar a versão 6.x. Interfaces gráficas estão disponíveis (veja abaixo). Veja também o tutorial de depuração [[../Tutorials/Debugging/Debugging with GDB (pt_BR)|Depurando com GDB]].

; KDbg
: [http://www.kdbg.org/ KDbg] é uma interface gráfica para o GDB, a qual permite definir pontos de parada no código (breakpoints), passar entre o código, etc.

; MS Windows tools (Process Explorer, Console, WinDbg, DebugView...)
: More info on the [[Projects/KDE_on_Windows/Tools (pt_BR)|KDE on Windows page]].

== Ferramentas de desenvolvimento ==
; KDevelop
: [http://www.kdevelop.org KDevelop] é uma excelente IDE para desenvolver o KDE e aplicações Qt C++. Ele incluir um depurador integrado, um poderoso editor com realce da sintaxe, um ''Assistente de projeto'' para criar aplicações a partir de modelos prontos, o automake/autoconf, e até mesmo a documentação da classe. Detalhes adicionais podem também serem encontrados no [http://kdevelop.org/mediawiki/index.php/Main_Page KDevelop wiki].

:Instruções de como usar o KDevelop com aplicações KDE 4 estão disponíveis [[Getting_Started/Set_up_KDE_4_for_development (pt_BR)#KDevelop|nesta página]]

; 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. 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].

; MS Visual Studio® Express 2005 IDE (Windows only)
: Visual C++® 2005 Express Edition [http://www.microsoft.com/germany/msdn/vstudio/products/express/visualc/default.mspx]  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. [[Projects/KDE_on_Windows/Issues/MSVC|more info...]]

== Ferramentas de Internacionalização (i18n) ==

; KBabel
: [http://kbabel.kde.org/ 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 {{path|`kde-config --localprefix`/share/config/kdeglobals}} activates this feature:

<code ini>
[Development]
CheckAccelerators=F12
AutoCheckAccelerators=false
AlwaysShowCheckAccelerators=false
</code>

: 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 <tt>AutoCheckAccelerators</tt> enabled the dialog will popup automatically if a conflict exists and <tt>AlwaysShowCheckAccelerators</tt> 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.

=== Examinando arquivos .po ===

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 {{path|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 {{path|konq_mainwindow.cc}} and also from {{path|konq_tabs.cc}}. This saves the translators from having to translate the same identical string twice. 

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

{{note|More information on writing and translating documentation can be found on [http://l10n.kde.org/ the l10n project site].}}

== Ferramentas de ajuda ==

; [[Development/Tools/Using kde-config (pt_BR)|Get information about KDE's installation - kde-config]] 
: The tool kde-config helps to find out more about a KDE installation.

; [[Development/Tools/Using kfmclient (pt_BR)|Driving Konqueror From Scripts - kfmclient]] 
: kfmclient is a small tool to communicate with Konqueror.

;[[Development/Tools/Using kconf_update (pt_BR)|Updating User Configuration Files - kconf_update]]
: kconf_update is a tool designed to update config files.

;[[Development/Tools/apidox (pt_BR)|Generating apidox]]
: tools that help develop and generate API documentation for your code.

;[[Development/Tools/Automoc4 (pt_BR)|Automoc4]]
: This is a helper tool needed to build KDE4. It automatically generates moc-files.

== Garantia de Qualidade ==

; Continuous Building - Dashboard 
: [http://developer.kde.org/~dirk/dashboard/ all kde modules on Dirk's dashboard]
: [http://public.kitware.com/dashboard.php?name=kde kdelibs on kitware]

; [http://englishbreakfastnetwork.org/ English Breakfast Network] - Static Analysis
: [http://www.englishbreakfastnetwork.org/krazy/ Krazy ] - Code Analysis, [[Development/Tutorials/Code_Checking|Usage Tutorial]]
: [http://www.englishbreakfastnetwork.org/apidocs/ APIDOX] - API Documentation Statistics
: [http://www.englishbreakfastnetwork.org/sanitizer/ Sanitizer] - DocBook Checker
: [http://www.englishbreakfastnetwork.org/usability/ Usability Checks]