{{Template:I18n/Language Navigation Bar|Development/Tutorials/Plasma}}

== Programación en Plasma con C++ ==

;[[/GettingStarted_(es)|Primeros pasos con Plasmoids]]
:''Crea tu primer plasmoid en C++ con un fondo SVG, un icono y un texto.''

;[[/DataEngines|Escribir un DataEngine]]
:''Un DataEngine proporciona una interfaz estándar para acceder a varias fuentes de datos. Aprende que es un DataEngine y como escribir uno propio.''

;[http://www.kdedevelopers.org/node/3247 Vídeo tutorial]
:''Vídeo y transparencias de una presentación de libplasma (enlace a las transparencias a continuación).''

;[http://mirror.linux.org.au/pub/linux.conf.au/2008/slides/296-coolplasma.odp Enlace a las transparencias del citado vídeo]
:''Transparencias de la presentación "Creación de interfaces de usuario con Plasma", por Aaron Seigo.''

;[[/UsingExtenders|Como usar extenders en tu Plasmoid]]
:''Un sencillo ejemplo que muestra como usar extenders en un Plasmoid.''

;[[Development/Tutorials/Plasma/AbstractRunner|Crear Runners]]
:''Los Runners son plugins que proporcionan una funcionalidad de búsqueda basada en acciónes en el dialogo "ejecutar orden" del área de trabajo de Plasma. Estos plugins pueden usarse en cualquier aplicación que enlace con libplasma.''

;[[Development/Tutorials/Plasma/ComicPlugin|Crear un plugin para Comic]]
:''Esta guia te muestra como crear un plugin para el plasmoid Comic.''

== Programación en Plasma con Python ==

;[[/Python/GettingStarted|Getting Started]]
:''Creating and running your first plasmoid in Python''

;[[/Python/Using widgets|Using widgets]]
:''Introduction to using Plasma widgets''

;[[/Python/Using DataEngines|Using DataEngines]]
:''How to use DataEngines from a plasmoid''

;[[/Python/Writing DataEngines|Writing DataEngines]]
:''How to write your own Plasma DataEngine''

;[[Development/Tutorials/Plasma/PythonPlasmoid|Writing a Plasmoid in Python]]
:''Writing a simple battery graph in python''

== Plasma Programming with Ruby ==
;[[/Ruby/GettingStarted|Getting Started]]
:''Creating and running your first plasmoid in Ruby''

;[[/Ruby/Using widgets|Using widgets]]
:''Introduction to using Plasma widgets''

;[[/Ruby/SimplePasteApplet|Writing a simple paste applet]]
:''A tutorial explaining how to write a simple paste applet using widgets''

== Theme development ==

;[[/Theme|Creating a Plasma Theme]]
:''Guide to creating your first Plasma theme''

Resources:

* http://techbase.kde.org/Projects/Plasma
* [http://api.kde.org/4.x-api/kdelibs-apidocs/plasma/html/index.html Plasma api documentation]
* The [https://mail.kde.org/mailman/listinfo/plasma-devel plasma-devel mailing list] and #plasma on IRC (irc.freenode.org).

TODO:

* '''tutorials for other languages''' (JavaScript, Ruby, etc...)

Development/Tutorials/Plasma (es)

2009-03-09T22:24:39Z

Edumardo:

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Plasma}}

== Programación en Plasma con C++ ==

;[[/GettingStarted|Primeros pasos con Plasmoids]]
:''Crea tu primer plasmoid en C++ con un fondo SVG, un icono y un texto.''

;[[/DataEngines|Escribir un DataEngine]]
:''Un DataEngine proporciona una interfaz estándar para acceder a varias fuentes de datos. Aprende que es un DataEngine y como escribir uno propio.''

;[http://www.kdedevelopers.org/node/3247 Vídeo tutorial]
:''Vídeo y transparencias de una presentación de libplasma (enlace a las transparencias a continuación).''

;[http://mirror.linux.org.au/pub/linux.conf.au/2008/slides/296-coolplasma.odp Enlace a las transparencias del citado vídeo]
:''Transparencias de la presentación "Creación de interfaces de usuario con Plasma", por Aaron Seigo.''

;[[/UsingExtenders|Como usar extenders en tu Plasmoid]]
:''Un sencillo ejemplo que muestra como usar extenders en un Plasmoid.''

;[[Development/Tutorials/Plasma/AbstractRunner|Crear Runners]]
:''Los Runners son plugins que proporcionan una funcionalidad de búsqueda basada en acciónes en el dialogo "ejecutar orden" del área de trabajo de Plasma. Estos plugins pueden usarse en cualquier aplicación que enlace con libplasma.''

;[[Development/Tutorials/Plasma/ComicPlugin|Crear un plugin para Comic]]
:''Esta guia te muestra como crear un plugin para el plasmoid Comic.''

== Programación en Plasma con Python ==

;[[/Python/GettingStarted|Getting Started]]
:''Creating and running your first plasmoid in Python''

;[[/Python/Using widgets|Using widgets]]
:''Introduction to using Plasma widgets''

;[[/Python/Using DataEngines|Using DataEngines]]
:''How to use DataEngines from a plasmoid''

;[[/Python/Writing DataEngines|Writing DataEngines]]
:''How to write your own Plasma DataEngine''

;[[Development/Tutorials/Plasma/PythonPlasmoid|Writing a Plasmoid in Python]]
:''Writing a simple battery graph in python''

== Plasma Programming with Ruby ==
;[[/Ruby/GettingStarted|Getting Started]]
:''Creating and running your first plasmoid in Ruby''

;[[/Ruby/Using widgets|Using widgets]]
:''Introduction to using Plasma widgets''

;[[/Ruby/SimplePasteApplet|Writing a simple paste applet]]
:''A tutorial explaining how to write a simple paste applet using widgets''

== Theme development ==

;[[/Theme|Creating a Plasma Theme]]
:''Guide to creating your first Plasma theme''

Resources:

* http://techbase.kde.org/Projects/Plasma
* [http://api.kde.org/4.x-api/kdelibs-apidocs/plasma/html/index.html Plasma api documentation]
* The [https://mail.kde.org/mailman/listinfo/plasma-devel plasma-devel mailing list] and #plasma on IRC (irc.freenode.org).

TODO:

* '''tutorials for other languages''' (JavaScript, Ruby, etc...)

Development/Tutorials/Saving and loading

2008-12-23T00:23:15Z

Edumardo: {{class|QTextStream}} ---> {{qt|QTextStream}}

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Saving_and_loading}}

{{TutorialBrowser|

series=Beginner Tutorial|

name=Loading and saving files|

pre=[[Development/Tutorials/Using_KActions|Tutorial 3 - KActions]]|

next=[[Development/Tutorials/KCmdLineArgs|Tutorial 5 - Using KCmdLineArgs]]|

reading=KIO::{{class|NetAccess}} {{qt|QFile}}
}}

==Abstract==

Now that we have a basic text editor interface, it's time to make it do something useful. At the most basic, a text editor needs to be able to load files from disc, save files that you've created/edited and create new files.

KDE provides a number of classes for working with files which make life a lot easier for developers. The KIO library allows you to easily access files through network-transparent protocols as well as providing standard file dialogs.

[[image:introtokdetutorial4.png|frame|center]]

== The Code ==

===main.cpp===
<code cppqt n>
#include <KApplication>
#include <KAboutData>
#include <KCmdLineArgs>

#include "mainwindow.h"

int main (int argc, char *argv[])
{
KAboutData aboutData( "tutorial4", "tutorial4",
ki18n("Tutorial 4"), "1.0",
ki18n("A simple text area which can load and save."),
KAboutData::License_GPL,
ki18n("Copyright (c) 2007 Developer") );
KCmdLineArgs::init( argc, argv, &aboutData );
KApplication app;

MainWindow* window = new MainWindow();
window->show();
return app.exec();
}
</code>
<tt>main.cpp</tt> hasn't changed from tutorial 3 except to change any reference to tutorial 3 to tutorial 4.

===mainwindow.h===
<code cppqt n>
#ifndef MAINWINDOW_H
#define MAINWINDOW_H

#include <KXmlGuiWindow>
#include <KTextEdit>

class MainWindow : public KXmlGuiWindow
{
Q_OBJECT //new from tutorial3

public:
MainWindow(QWidget *parent=0);

private:
KTextEdit* textArea;
void setupActions();
QString fileName; //new

private slots: //new
void newFile(); //new
void openFile(); //new
void saveFile(); //new
void saveFileAs(); //new
void saveFileAs(const QString &outputFileName); //new
};

#endif
</code>
Since we want to add the ability to load and save files, we must add the functions which will do the work. Since the functions will be called through Qt's [http://doc.trolltech.com/latest/signalsandslots.html signal/slot] mechanism we must specify that these functions are slots as we do on line 19. Since we are using slots in this header file, we must also add the [http://doc.trolltech.com/latest/qobject.html#Q_OBJECT <tt>Q_OBJECT</tt>] macro.

We also want to keep track of the filename of the currently opened file so we declare a <tt>{{qt|QString}} fileName</tt>.

===mainwindow.cpp===
<code cppqt n>
#include "mainwindow.h"

#include <KApplication>
#include <KAction>
#include <KLocale>
#include <KActionCollection>
#include <KStandardAction>
#include <KFileDialog> //new
#include <KMessageBox> //new
#include <KIO/NetAccess> //new
#include <KSaveFile> //new
#include <QTextStream> //new

MainWindow::MainWindow(QWidget *parent)
: KXmlGuiWindow(parent),
fileName(QString()) //new
{
textArea = new KTextEdit;
setCentralWidget(textArea);

setupActions();
}

void MainWindow::setupActions()
{
KAction* clearAction = new KAction(this);
clearAction->setText(i18n("Clear"));
clearAction->setIcon(KIcon("document-new"));
clearAction->setShortcut(Qt::CTRL + Qt::Key_W);
actionCollection()->addAction("clear", clearAction);
connect(clearAction, SIGNAL(triggered(bool)),
textArea, SLOT(clear()));

KStandardAction::quit(kapp, SLOT(quit()),
actionCollection());

KStandardAction::open(this, SLOT(openFile()),
actionCollection()); //new

KStandardAction::save(this, SLOT(saveFile()),
actionCollection()); //new

KStandardAction::saveAs(this, SLOT(saveFileAs()),
actionCollection()); //new

KStandardAction::openNew(this, SLOT(newFile()),
actionCollection()); //new

setupGUI();
}

//New from here on

void MainWindow::newFile()
{
fileName.clear();
textArea->clear();
}

void MainWindow::saveFileAs(const QString &outputFileName)
{
KSaveFile file(outputFileName);
file.open();

QByteArray outputByteArray;
outputByteArray.append(textArea->toPlainText().toUtf8());
file.write(outputByteArray);
file.finalize();
file.close();

fileName = outputFileName;
}

void MainWindow::saveFileAs()
{
saveFileAs(KFileDialog::getSaveFileName());
}

void MainWindow::saveFile()
{
if(!fileName.isEmpty())
{
saveFileAs(fileName);
}
else
{
saveFileAs();
}
}

void MainWindow::openFile()
{
QString fileNameFromDialog = KFileDialog::getOpenFileName();

QString tmpFile;
if(KIO::NetAccess::download(fileNameFromDialog, tmpFile,
this))
{
QFile file(tmpFile);
file.open(QIODevice::ReadOnly);
textArea->setPlainText(QTextStream(&file).readAll());
fileName = fileNameFromDialog;

KIO::NetAccess::removeTempFile(tmpFile);
}
else
{
KMessageBox::error(this,
KIO::NetAccess::lastErrorString());
}
}
</code>

===tutorial4ui.rc===
<code xml n>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE kpartgui SYSTEM "kpartgui.dtd">
<gui name="tutorial4" version="1">
<ToolBar name="mainToolBar" >
<text>Main Toolbar</text>
<Action name="clear" />
</ToolBar>
<MenuBar>
<Menu name="file" >
<Action name="clear" />
</Menu>
</MenuBar>
</gui>
</code>
This is identical to <tt>tutorial3ui.rc</tt> from tutorial 3 except the <tt>name</tt> has changed to 'tutorial4'. We do not need to add any information about any of the <tt>KStandardAction</tt>s since the placement of those actions is handled automatically by KDE.

==Explanation==

Okay, now to implement the code that will do the loading and saving. This will all be happening in <tt>mainwindow.cpp</tt>

The first thing we do is add
<code cppqt>
fileName(QString())
</code>
to the <tt>MainWindow</tt> constructor list on line 16. This makes sure that <tt>fileName</tt> is empty right from the beginning.

===Adding the actions===

The first thing we are going to do is provide the outward interface for the user so they can tell the application to load and save. Like with the <tt>quit</tt> action in tutorial 3, we will use <tt>KStandardActions</tt>. On lines 37 to 47 we add the actions in the same way as for the <tt>quit</tt> action. For each one, we connect it to the appropriate slot that we declared in the header file.

===Creating a new document===

The first function we create is the <tt>newFile()</tt> function.
<code cppqt>
void MainWindow::newFile()
{
fileName.clear();
textArea->clear();
}
</code>
<tt>fileName.clear()</tt> sets the <tt>fileName</tt> QString to be empty to reflect the fact that this document does not yet have a presence on disc. <tt>textArea->clear()</tt> then clears the central text area using the same function that we connected the <tt>clear</tt> <tt>KAction</tt> to in tutorial 3.

===Saving a file===

====saveFileAs(QString)====

Now we get onto our first file handling code. We're going to implement a function which will save the contents of the text area to the file name given as a parameter. KDE provides a class for safely saving a file called {{class|KSaveFile}} which is derived from Qt's {{qt|QFile}}.

The function's prototype is
<code cppqt>
void MainWindow::saveFileAs(const QString &outputFileName)
</code>

We then create our <tt>KSaveFile</tt> object and open it with
<code cppqt>
KSaveFile file(outputFileName);
file.open();
</code>

Now that we have our file to write to, we need to format the text in the text area to a format which can be written to file. For this, we create a {{qt|QByteArray}} and fill it with the plain text version of whatever is in the text area:
<code cppqt>
QByteArray outputByteArray;
outputByteArray.append(textArea->toPlainText().toUtf8());
</code>
Now that we have our <tt>QByteArray</tt>, we use it to write to the file with <tt>KSaveFile::write()</tt>. If we were using a normal <tt>QFile</tt>, this would make the changes immediately. However, if a problem occurred partway through writing, the file would become corrupted. For this reason, <tt>KSaveFile</tt> works by first writing to a temporary file and then, when you call <tt>KSaveFile::finalize()</tt> the changes are made to the actual file.
<code cppqt>
file.write(outputByteArray);
file.finalize();
file.close();
</code>
Finally, we set <tt>MainWindows</tt>'s <tt>fileName</tt> member to point to the file name we just saved to.
<code cppqt>
fileName = outputFileName;
</code>

====saveFileAs()====

This is the function that the <tt>saveAs</tt> slot is connected to. It simply calls the generic <tt>saveFileAs(QString)</tt> function and passes the file name returned by <tt>{{class|KFileDialog}}::[http://api.kde.org/4.0-api/kdelibs-apidocs/kio/html/classKFileDialog.html#8891356c249c5911e1ab15cc2739a89b getSaveFileName()]</tt>.

<code cppqt>
void MainWindow::saveFileAs()
{
saveFileAs(KFileDialog::getSaveFileName());
}
</code>

This is our first actual use of the KIO library. {{class|KFileDialog}} provides a number of static functions for displaying the common file dialog that is used by all KDE applications. Calling <tt>KFileDialog::getSaveFileName()</tt> will display a dialog where the user can select the name of the file to save to or choose a new name. The function returns the full file name, which we then pass to <tt>saveFileAs(QString)</tt>.

====saveFile()====

<code cppqt>
void MainWindow::saveFile()
{
if(!fileName.isEmpty())
{
saveFileAs(fileName);
}
else
{
saveFileAs();
}
}
</code>

There's nothing exciting or new in this function, just the logic to decide whether or not to show the save dialog. If <tt>fileName</tt> is not empty, then the file is saved to <tt>fileName</tt>. But if it is, then the dialog is shown to allow the user to select a file name.

===Loading a file===

Finally, we get round to being able to load a file from disc. The code for this is all contained in <tt>MainWindow::openFile()</tt>.

First we must ask the user for the name of the file they wish to open. We do this using another one of the <tt>KFileDialog</tt> functions, this time <tt>getOpenFileName()</tt>:
<code cppqt>
QString fileNameFromDialog = KFileDialog::getOpenFileName();
</code>

Then we use the KIO library to retrieve our file. This allows us to open the file with QFile even if it's stored in a remote location like an FTP site. We make the following call to {{class|NetAccess}}'s <tt>download()</tt> function
<code cppqt>
KIO::NetAccess::download(fileNameFromDialog, tmpFile, this)
</code>
The first argument is the name of the file you wish to download. The second is a QString which, after the download is complete, will contain the location of the temporary copy of the file. It is this <tt>tmpFile</tt> we will work with from now on.

The function returns <tt>true</tt> or <tt>false</tt> depending on whether the transfer was successful. If it failed, we display a message box giving the error:
<code cppqt>
KMessageBox::error(this, KIO::NetAccess::lastErrorString());
</code>

Otherwise, we continue with opening the file.

We create a QFile by passing the temporary file created by <tt>NetAccess::download()</tt> to its constructor and then open it in read-only mode
<code cppqt>
QFile file(tmpFile);
file.open(QIODevice::ReadOnly);
</code>

In order to display the contents of the file, we must use a {{qt|QTextStream}}. We create one by passing the contents of our file to its constructor and then call QFile's <tt>readAll()</tt> function to get the text from the file. This is then passed to the <tt>setPlainText()</tt> function of our text area.

<code cppqt>
textArea->setPlainText(QTextStream(&file).readAll());
</code>

We then store the path of the file we just opened:
<code cppqt>
fileName = fileNameFromDialog;
</code>
and finally, we remove the temporary file that was created by <tt>NetAccess::download()</tt>:
<code cppqt>
KIO::NetAccess::removeTempFile(tmpFile);
</code>

==Make, Install And Run==

===CMakeLists.txt===
<code ini n>
project(tutorial4)

find_package(KDE4 REQUIRED)
include_directories(${KDE4_INCLUDES})

set(tutorial4_SRCS
main.cpp
mainwindow.cpp
)

kde4_add_executable(tutorial4 ${tutorial4_SRCS})

target_link_libraries(tutorial4 ${KDE4_KDEUI_LIBS}
${KDE4_KIO_LIBS})

install(TARGETS tutorial4 DESTINATION ${BIN_INSTALL_DIR})
install(FILES tutorial4ui.rc
DESTINATION ${DATA_INSTALL_DIR}/tutorial4)
</code>
Since we are now using the KIO library, we must tell CMake to link against it. We do this by passing <tt>${KDE4_KIO_LIBS}</tt> to the <tt>target_link_libraries()</tt> function.

With this file, the tutorial can be built and run in the same way as tutorial 3. For more information, see tutorial 3.

mkdir build && cd build
cmake .. -DCMAKE_INSTALL_PREFIX=$HOME
make install
$HOME/bin/tutorial4

==Moving On==
Now you can move on to the [[Development/Tutorials/KCmdLineArgs|KCmdLineArgs]] tutorial.

[[Category:C++]]

2008-10-06T22:35:37Z

Edumardo: translation to spanish

{{Template:I18n/Language Navigation Bar|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
: [[Development/Tools/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)
: [http://sources.redhat.com/gdb/ GDB] te ayuda a depurar código fuente. Como GDB está en desarrollo todo el tiempo, es recomendable usar la versión 6.x. Exsiten interfaces de usuario. Mira también el tutorial de depurado [[../Tutorials/Debugging/Debugging with GDB|Debugging with GDB]].

; KDbg
: [http://www.kdbg.org/ KDbg] es una interfaz gráfica de usuario de GDB, con la cual puedes establecer breakpoints, ir paso a paso a través del código, etc.

; MS Windows tools (Process Explorer, Console, WinDbg, DebugView...)
: Mas información en la[[Projects/KDE_on_Windows/Tools|página de KDE en Windows]].

== Herramientas de desarrollo ==
; KDevelop
: [http://www.kdevelop.org 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 [http://kdevelop.org/mediawiki/index.php/Main_Page KDevelop wiki].

:Las instrucciones sobre como usar KDevelop con aplicaciones KDE4 están disponibles en [[Getting_Started/Set_up_KDE_4_for_development#KDevelop|this page]].

; Qt Designer
: Con Trolltech [http://www.trolltech.com/products/qt/features/designer Qt Designer] es fácil 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 [[Development/Tutorials/Using_Qt_Designer|Using Qt Designer]] y en la [http://doc.trolltech.com/4.2/designer-manual.html documentación de Qt].

; MS Visual Studio® Express 2005 IDE (solo Windows)
: Visual C++® 2005 Express Edition [http://www.microsoft.com/germany/msdn/vstudio/products/express/visualc/default.mspx] es la verión gratuita del compilador Microsoft Visual Studio 2005 de Microsoft, soportado oficialmente por Trolltech desde Qt 4.3.2. Es una opción para compilar Qt y aplicaciones KDE en Windows. [[Projects/KDE_on_Windows/Issues/MSVC|Mas información]].

== Herramientas de internacionalización (i18n) ==

; KBabel
: [http://kbabel.kde.org/ KBabel] es un conjunto de herramientas para editar y administrar archivos PO. Es un potente y cómodo editor de archivos PO que proporciona navegación entre archivos, edición, posibilidad de buscar traducciones en diferentes diccionarios, comprobación de vocabulario y sintaxis, mostrar diferencias y mucho mas.

: También incluye un "administrador de catálogo", una vista de administración de archivos que ayuda a mantener y observar archivos PO. Por último, pero no por ello menos importante, incluye una aplicación de diccionario independiente que ofrece la posibilidad adicional de acceder a los potentes diccionarios de KBabel. KBabel te ayudará a traducir rápido y también a conseguir traducciones coherentes.

; Dr. Klash
: Esta pequeña utilidad, una vez activada, puede presentar un informe sobre los conflictos de teclado en los menús. No solo es útil para los traductores, sino también los para desarrolladores. Una pequeña edición de {{path|`kde-config --localprefix`/share/config/kdeglobals}} activa esta funcionalidad:

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

: Al pulsar F12 se mostrará un diálogo que contendrá que atajos de teclado de la interfaz activa crean conflictos y proporcionará sugerencias para unos nuevos. Si no existen conflictos o Dr. Klash no tiene ninguna sugerencia, no se mostrará nada.

: Con <tt>AutoCheckAccelerators</tt> activado, se mostrará automáticamente el diálogo si existe un conflicto, y <tt>AlwaysShowCheckAccelerators</tt> puede forzar a que el dialogo siempre aparezca aunque no existan conflictos.

; El lenguaje x-test
: Este lenguaje de ayuda actúa como un depurador que permite a la gente encontrar cadenas no traducidas. Si inicias tu aplicación con "x-test", todas las cadenas traducidas aparecerán marcadas con xx's al principio. En primer lugar tienes que comprobar dichas "traducciones" en l10n-kde4/x-test, e instalarlas después.

: Despues de haber compilado e instalado l10n-kde4/x-test, ejecuta tu aplicación usando "x-test". Esto lo puedes hacer lanzandola desde la linea de ordenes de esta manera:

> KDE_LANG=x-test kspread

: De esta forma, arrancará KSpread usando "x-test", sin importar cual sea la configuración del idioma. Observa las cadenas que no tienen xx's. Si una cadena no tiene xx's, podría deberse a que faltan llamadas a i18n o incluso archivos .pot desaparecidos o generados incorrectamente. Consulta los tutoriales de i18n para mas información.

: Cuando compruebes cadenas sin traducir, asegurate que compruebas toda la ayuda "¿Qué es esto?" y los tooltips.

=== Examinando archivos .po ===

Puedes mirar en los archivos .po traducidos para comprobar si una cadena está presente y ha sido traducida. Por ejemplo, aquí tienes una porción de {{path|l10n/es/messages/kdebase/kdesu.po}}:

#: kdesu.cpp:100 kdesu.cpp:101
msgid "Specifies the command to run"
msgstr "Indica la orden a ejecutar"

La cadena a traducir empieza en la línea msgid. La cadena traducida está en la línea msgstr. Ten en cuenta que la cadena a traducir puede necesitarse en dos partes del código diferentes. Los archivos .po ahorran a los traductores tener que traducir la misma cadena dos veces.

Puedes usar también KBabel para examinar archivos {{path|.po}}. KBabel es parte del módulo kdesdk.
{{note|Puedes encontrar mas información sobre la escritura y traducción de documentación en el [http://l10n.kde.org/ sitio web de l10n].}}

== Herramientas de ayuda ==

; [[Development/Tools/Using kde-config|Obtener información sobre la instalación de KDE - kde-config]]
: La herramienta kde-config te ayuda a saber más acerca de una instalación de KDE

; [[Development/Tools/Using kfmclient|Manejar Konqueror mediante scripts - kfmclient]]
: kfmclient es una pequeña herramienta para comunicarse con Konqueror.

;[[Development/Tools/Using kconf_update|Actualizar archivos de configuración del usuario - kconf_update]]
: kconf_update es una herramienta diseñada para actualizar archivos de configuración del usuario.

;[[Development/Tools/apidox|Generar apidox]]
: Herramientas que ayudan a desarrollar y generar la documentación de la API de tu código.

;[[Development/Tools/Automoc4|Automoc4]]
: Es una herramienta de ayuda necesaria para construir KDE4. Genera automáticamente archivos moc.

== Asegurar la calidad ==

; Construcción continua - Dashboard
: [http://developer.kde.org/~dirk/dashboard/ Todos los módulos de kde en Dirk's dashboard]
: [http://public.kitware.com/dashboard.php?name=kde kdelibs en kitware]

; [http://englishbreakfastnetwork.org/ English Breakfast Network] - Análisis estático
: [http://www.englishbreakfastnetwork.org/krazy/ Krazy ] - Análisis de código, [[Development/Tutorials/Code_Checking|Tutorial de uso]]
: [http://www.englishbreakfastnetwork.org/apidocs/ APIDOX] - Estadísticas de la documentación de la API
: [http://www.englishbreakfastnetwork.org/sanitizer/ Sanitizer] - Verificador de DocBook
: [http://www.englishbreakfastnetwork.org/usability/ Comprobación de usabilidad]

File:Creatingyourfirstplasmoid1 (es).png

2008-09-30T21:03:06Z

Edumardo:

Development/Tutorials/Plasma/GettingStarted (es)

2008-09-23T20:14:36Z

Edumardo: translation to spanish

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Plasma/GettingStarted}}

{{TutorialBrowser|

series=Plasma Tutorial|

name=Creating your first Plasmoid|

pre=[http://mindview.net/Books/TICPP/ThinkingInCPP2e.html C++], [http://www.trolltech.com/products/qt/ Qt], [[Getting_Started/Build/KDE4|KDE4 development environment]]|

next=|

reading=[[Development/Tutorials/CMake|CMake]]
}}
==Abstract==
This tutorial needs KDE 4.1 (trunk) to build.
We are going to create a simple plasmoid in this tutorial. To keep things simple, we will only create a static plasmoid which will contain the following items:

* An SVG Image
* Icon
* Some nice text

[[image:creatingyourfirstplasmoid1.png|frame|center]]

== The Code ==
=== The .desktop file ===
Every Plasmoid needs a .desktop file to tell plasma how it should be started and what name it carries.

'''plasma-applet-tutorial1.desktop'''
<code ini>
[Desktop Entry]
Name=Tutorial 1
Comment=Plasma Tutorial 1
Type=Service

X-KDE-ServiceTypes=Plasma/Applet
X-KDE-Library=plasma_applet_tutorial1
X-KDE-PluginInfo-Author=Bas Grolleman
X-KDE-PluginInfo-Email=bgrolleman@emendo-it.nl
X-KDE-PluginInfo-Name=tutorial1
X-KDE-PluginInfo-Version=0.1
X-KDE-PluginInfo-Website=http://plasma.kde.org/
X-KDE-PluginInfo-Category=Examples
X-KDE-PluginInfo-Depends=
X-KDE-PluginInfo-License=GPL
X-KDE-PluginInfo-EnabledByDefault=true
</code>

The most important bits are the '''X-KDE-Library''' and '''X-KDE-PluginInfo-Name''', they are the "glue" between your class and plasma, without it, nothing will start. For '''X-KDE-PluginInfo-Category''', refer to the [[Projects/Plasma/PIG | PIG]].

=== The header file ===
This is the example header file. Comments have been added in the code for clarity.

'''plasma-tutorial1.h'''
<code cppqt>
// Here we avoid loading the header multiple times
#ifndef Tutorial1_HEADER
#define Tutorial1_HEADER
// We need the Plasma Applet headers
#include <KIcon>

#include <Plasma/Applet>
#include <Plasma/Svg>

class QSizeF;

// Define our plasma Applet
class PlasmaTutorial1 : public Plasma::Applet
{
Q_OBJECT
public:
// Basic Create/Destroy
PlasmaTutorial1(QObject *parent, const QVariantList &args);
~PlasmaTutorial1();

// The paintInterface procedure paints the applet to screen
void paintInterface(QPainter *painter,
const QStyleOptionGraphicsItem *option,
const QRect& contentsRect);
void init();

private:
Plasma::Svg m_svg;
KIcon m_icon;
};

// This is the command that links your applet to the .desktop file
K_EXPORT_PLASMA_APPLET(tutorial1, PlasmaTutorial1)
#endif
</code>

==== QRectF boundingRect() ====
The <tt>boundingRect()</tt> function tells plasma the actual size of the plasmoid. This is important because we need to know how much space is taken on the screen.
{{tip|
If you have issues with your plasmoid leaving pixels behind when dragging, this is usually a result of an incorrect boundingRect()
}}

==== void paintInterface(QRectF contentsRect) ====
This can be considered the main function since it paints the plasmoid on to the screen. Here, you define how you want your plasmoid to look.
You should only paint in the boundaries defined by contentsRect and avoid using geometry(). When a plasmoid does not have a standard background, e.g. when it's disabled with a setBackgroundHints() call or it's in the panel, geometry() and boundingRect() behave the same; however, when the standard background is enabled (the usual case), the appplet will have a margin where it should not be painted

==== K_EXPORT_PLASMA_APPLET ( <name>, <class> ) ====
This is a small but very important part that links your classname to the applet name in the .desktop file. If your applet doesn't seem to get loaded, there may be a difference between this declaration and your .desktop file

{{tip|
The K_EXPORT_PLASMA_APPLET adds "plasma_applet_", please pay attention to this when setting up your .desktop file to avoid a name difference
}}

=== The actual work file ===
Here is the body of the function, again with a lot of comments in between.

'''plasma-tutorial1.cpp'''
<code cppqt>
#include "plasma-tutorial1.h"
#include <QPainter>
#include <QFontMetrics>
#include <QSizeF>

#include <plasma/svg.h>
#include <plasma/theme.h>

PlasmaTutorial1::PlasmaTutorial1(QObject *parent, const QVariantList &args)
: Plasma::Applet(parent, args),
m_svg(this),
m_icon("document")
{
m_svg.setImagePath("widgets/background");
// this will get us the standard applet background, for free!
setBackgroundHints(DefaultBackground);
resize(200, 200);
}

PlasmaTutorial1::~PlasmaTutorial1()
{
if (hasFailedToLaunch()) {
// Do some cleanup here
} else {
// Save settings
}
}

void PlasmaTutorial1::init()
{

// A small demonstration of the setFailedToLaunch function
if (m_icon.isNull()) {
setFailedToLaunch(true, "No world to say hello");
}
}

void PlasmaTutorial1::paintInterface(QPainter *p,
const QStyleOptionGraphicsItem *option, const QRect &contentsRect)
{
p->setRenderHint(QPainter::SmoothPixmapTransform);
p->setRenderHint(QPainter::Antialiasing);

// Now we draw the applet, starting with our svg
m_svg.resize((int)contentsRect.width(), (int)contentsRect.height());
m_svg.paint(p, (int)contentsRect.left(), (int)contentsRect.top());

// We place the icon and text
p->drawPixmap(7, 0, m_icon.pixmap((int)contentsRect.width(),(int)contentsRect.width()-14));
p->save();
p->setPen(Qt::white);
p->drawText(contentsRect,
Qt::AlignBottom | Qt::AlignHCenter,
"Hello Plasmoid!");
p->restore();
}

#include "plasma-tutorial1.moc"
</code>

==== Plasma/Svg ====
As you can see in the example code we are using the {{class|Plasma::Svg}} object, there are some important things to note here.

First we're using a relative path '''widgets/background''' which causes {{class|Plasma::Svg}} to use {{class|Plasma::Theme}} to locate the SVG data. While {{class|Plasma::Svg}} does support loading arbitrary files when passed an absolute path, use relative paths from the theme as often as possible as it makes Plasma skinable and the individual plasmoids look like a combined whole instead of a group of separate unrelated applications. You can see a list of available image components on the [[Projects/Plasma/Theme|Plasma Theme page]].

In either mode, {{class|Plasma::Svg}} can be used to draw a subset of the SVG file by passing it an element id that appears in the SVG document. As a good example, if you open the clock.svg file that ships with the default theme, you will see that it has a background, 3 handles (hour, minute and seconds) and a foreground (the glass). Due to the ability to put all the elements in one file the SVG file shows a clock. This is much nicer for artists compared to editing 5 separate files that they have to imagine on top of each other, and much nicer for performance as only one SVG renderer and one file read from disk is necessary.

==== setBackgroundHints(DefaultBackground) ====
Since drawing a background is a common function there is fast and easier way of doing it. By adding <tt>setBackgroundHints(DefaultBackground)</tt> to the code, the default Plasma background gets drawn behind your plasmoid. This not only saves you time and code, but creates a more consistent presentation for the user.

==== The init() method ====
In the constructor you only tell plasma about the background and configuration file if any. You also set the start size in the constructor. After that, plasma will take care of any resizing and you never have to worry about size. In the <tt>init()</tt> method you initialize everything that needs to be initialize such as reading config data for example.

==== hasFailedToLaunch() ====
If for some reason, the applet fails to get up on its feet (the library couldn't be loaded, necessary hardware support wasn't found, etc..) this method returns true. Using this function gives your application a chance to cleanup before quiting.

==== setFailedToLaunch(bool, QString) ====
When your application is unable to start, this function allows you to inform Plasma and give an optional reason why. Plasma will then draw a standardized error interface to inform the user of the situation and your applet will not be called upon to do any drawing on its own from that point forward. If your plasmoid becomes more complex and depends on multiple factors this is the nicest way to cleanup.

==== dataUpdated ====
If you would connect to any of plasma's data-engines you would have to implement a function called dataUpdated in your plasmoid. The latter is called if the data-engine sends you data, i.e. your plasmoid should recalculate its contents.

==== Determine the applet size and geometry: geometry() and contentsRect() ====
If you need to know, in your applet code, what the applet size and geometry is, call contentsRect() and contentsRect().size(). Avoid calling geometry() and size() because they don't take into account the margin's size set by the applets default background.
Also avoid using absolute numbers to position items in the applet like QPoint(0, 0) to indicate the top-left point of your applet, instead use contentsRect().topLeft().

=== Building it all, the CMakeLists.txt ===
Finally, to put everything together you need to build everything. To tell cmake what needs to go where there is the CMakeLists.txt file.

For more details on CMake please read [[Development/Tutorials/CMake]]

<code bash>
# Project Needs a name ofcourse
project(plasma-tutorial1)

# Find the required Libaries
find_package(KDE4 REQUIRED)
include(KDE4Defaults)
find_package(Plasma REQUIRED)

add_definitions (${QT_DEFINITIONS} ${KDE4_DEFINITIONS})
include_directories(
${CMAKE_SOURCE_DIR}
${CMAKE_BINARY_DIR}
${KDE4_INCLUDES}
)

# We add our source code here
set(tutorial1_SRCS plasma-tutorial1.cpp)

# Now make sure all files get to the right place
kde4_add_plugin(plasma_applet_tutorial1 ${tutorial1_SRCS})
target_link_libraries(plasma_applet_tutorial1
${PLASMA_LIBS} ${KDE4_KDEUI_LIBS})

install(TARGETS plasma_applet_tutorial1
DESTINATION ${PLUGIN_INSTALL_DIR})

install(FILES plasma-applet-tutorial1.desktop
DESTINATION ${SERVICES_INSTALL_DIR})
</code>

== Testing the Applet ==
If your current Development Environment differs from the Test Installation, you have to run cmake with -DCMAKE_INSTALL_PREFIX=/usr/lib/kde4/ (replace with your $KDEDIR). Then run make. If succesfull the applet can be installed by running sudo make install
or
* cp ./lib/plasma_applet_tutorial1.so $KDEDIR/lib
* cp ./plasma-applet-tutorial1.desktop $KDEDIR/share/kde4/services/

and run kbuildsycoca4 (so that KDE apps will know about the new desktop files).
In order to test your Applet you can use the '''plasmoidviewer''' program:
<code bash>
plasmoidviewer applet_name
</code>

Where '''applet_name''' is the value specified into .desktop for the '''X-KDE-PluginInfo-Name''' key.

Otherwise you can restart plasma, so the Applet will be displayed in the Applet Browser:
<code bash>
kbuildsycoca4
kquitapp plasma
plasma
</code>

If that doesn't work you will have to restart your KDE session by logging out and back in.

Development/Tutorials (es)

2008-09-23T20:10:15Z

Edumardo: translation to spanish, update

{{Template:I18n/Language Navigation Bar|Development/Tutorials}}
{{warning_(es)| Traducción en curso: solo hasta el punto 4, también está traducido el punto 13 (Plasma)}}
Los tutoriales son la forma más rápida de encontrar lo que KDE puede hacer por usted y como hacerlo. Aquí tienes una lista de los tutoriales disponibles actualmente para KDE4. Material para KDE3 y KDE2 está disponible al final de la página.

== Introducción a la programación en KDE4 ==
Estś interesado en escribir aplicacion en KDE4? Esta serie de tutoriales están dirigidos a personas totalmente novatas en la programación en KDE4.
;[[Development/Tutorials/First program_(es)|Hola Mundo]]
:''Una introducción preliminar a los aspectos básicos de la programación en KDE4.''

;[[Development/Tutorials/Using KXmlGuiWindow_(es)|Crear la ventana principal]]
:''Este tutorial te muestra la magia de la cosa mas importante en una aplicación: la ventana principal''

;[[Development/Tutorials/Using KActions_(es)|Usar KActions]]
:''Como añadir acciones a los menús y a las toolbars.''

;[[Development/Tutorials/Saving and loading|Guardar y Abrir]]
:''Introducción a la biblioteca KIO mientras añades soporte para guardar y abrir en tu aplicación.''

;[[Development/Tutorials/KCmdLineArgs|Argumentos en la línea de órdenes]]
:''Añade la capacidad de especificar a nuestro editor que archivo abrir desde la línea de ordenes.''

== Básicos ==
;[[Development/Tutorials/KDE4 Porting Guide|Portar tu aplicación]]
:''Ayuda para portar aplicaciones de Qt3/KDE3 a Qt4/KDE4.''

;[[Development/Tutorials/CMake|Introducción a CMake]]
:''Como usar el sistema de construcción CMake usado por KDE4.''

;[[Development/Tutorials/Common Programming Mistakes|Errores comunes de programación]]
:''Varios errores comunes que se presentan en el desarrollo de aplicaciones Qt y KDE y como evitarlos.''

;[[Development/Tutorials/Using Qt Designer|Usar Qt Designer para diseñar interfaces de usuario]]
:''Como crear archivos UI con el diseñador, y como integrarlos después en un programa KDE.''

;[[Development/Tutorials/Creating Libraries|Crear bibliotecas para compartir código]]
:''Como añadir la biblioteca al "buildsystem" y como preparar el código fuente.''
:''How to add the library to the buildsystem and how to prepare the source code.''

== Comprobación y depurado ==

;[[Development/Tutorials/Debugging|Depurar tu aplicación]]
:''Consejos, herramientas y técnicas para depurar tu aplicación KDE.''

;[[Development/Tutorials/Unittests|Escribir "unittests" para Qt4 y KDE4 con QTestLib]] ([http://developer.kde.org/documentation/tutorials/writingunittests/writingunittests.html enlace original])
:''Tutorial de [mailto:bradh@frogmouth.net Brad Hards] que describe como escribir unittests mediante la framework QTestLib. El tutorial se realiza con un ejemplo, y aun está en desarrollo.''

;[[Development/Tutorials/Code_Checking|Maneras semiautomáticas de detectar errores en el código]]
:''Técnicas que puedes usar para detectar errores en el código KDE.''

== Gestión de los datos de configuración con KConfig ==

;[[Development/Tutorials/KConfig|Introducción a KConfig]]
:''Una sinopsis de las clases de KConfig y como usarlas en el código de tu aplicación.''

;[[Development/Tutorials/Using KConfig XT|Uso de KConfig XT]]
:''Tutorial sobre como usar eficientemente el framework KConfig XT''

;[[Development/Tutorials/Updating KConfig Files|Actualizando archivos con KConfig]]
:''Tutorial sobre como escribir un script de actualización para conservar los cambios de tu archivo de configuración de tu aplicación y sincornizarlo con el archivo de configuración del usuario''

== Services: Applications and Plugins ==
;[[Development/Tutorials/Services/Introduction|Introduction to the Services Framework]]
:''An overview of the services framework in KDE and what it provides the application developer. Covers the system configuration cache (SyCoCa), the source data files and what the indexed information can be used for.''

;[[Development/Tutorials/Services/Traders|Finding Services Using Trader Queries]]
:''How to find services, such as plugins or mimetypes, that are indexed in the SyCoCa using Trader Query Syntax''

;[[Development/Tutorials/Services/Plugins|Creating and Loading Plugins Using KService]]
:''Learn how to define custom plugin types, find installed plugins (including 3rd party plugins) and load them in an easy and portable fashion using KService.''

== Localization ==
See also [[Localization|Localization portal]].

;[[Development/Tutorials/Localization/Unicode|Introduction To Unicode]]
:''An introduction to what Unicode is as well as how to handle Unicode data in KDE applications.''

; [[Development/Tutorials/Localization/i18n|Writing Applications With Localization In Mind]]
:''This tutorial covers what localization is, why it's important and how to ensure your application is ready to be localized. A must read for all application developers.''

; [[Development/Tutorials/Localization/i18n Mistakes|Avoiding Common Localization Pitfalls]]
:''There are several common mistakes that prevent applications from being properly localized. Find out what they are and how to easily avoid them in this tutorial.''

; [[Development/Tutorials/Localization/Building KDE's l10n Module|Building KDE's Localization Module]]
:''Building and installing language support from KDE's localization (l10n) module is a good idea for those working on applications in the main KDE repository. Doing so will allow you to test your application in another language and spot problem areas. Learn how to do just that in this tutorial.''

; [[Development/Tutorials/Localization/i18n Build Systems|Incorporating i18n Into the Build System]]
:''Once your application is ready to be localized, the next step is to ensure that translation files are built automatically and kept up to date. This tutorial covers the necessary CMakeFiles.txt additions as well the process of distributing the resulting message catalogs with your application.''

; [[Development/Tutorials/Localization/i18n Challenges|Common i18n Challenges and Solutions]]
:''This tutorial covers challenges that you may eventually run into such as translating handbooks and other data that exists outside of the source code, merging and handling obsolete .po files, dealing with freezes, coding in languages other than English and creating independent releases of or moving applications between KDE modules.''

; [[Development/Tutorials/Localization/i18n_Semantics|Semantic Markup of Messages]]
:''To ensure consistent presentation and more meaningful representations of messages in applications, semantic markup can be applied to messages marked for translation using the KUIT system. This tutorial describes how this system works.''

; [[Development/Tutorials/Localization/i18n Krazy|Automated i18n Code Checking]]
:''The Krazy code checker scans KDE's code and reports common i18n mistakes.''

== Documentation ==

;[[Development/Tutorials/API_Documentation|API Documentation]]
:''This tutorial explains how to document your APIs properly.''

;[[Development/Tutorials/Man_Pages|Man Pages]]
:''Writing and Generating Reference Manual Pages.''

== Application Automation and Scripting ==

=== D-Bus ===
; [[Development/Tutorials/D-Bus/Introduction|Introduction to D-Bus]]
:''A straight-forward introduction to the core concepts in D-Bus from an application developer's perspective, this tutorial covers what D-Bus is and how it can be used by applications.''
; [[Development/Tutorials/D-Bus/Accessing Interfaces|Accessing D-Bus Interfaces]]
:''A step-by-step guide to calling D-Bus methods and connecting to D-Bus signals using QtDBus.''
; [[Development/Tutorials/D-Bus/Intermediate_D-Bus|Intermediate D-Bus]]
:''Tips to make use of QtDBus when faced with problematic real-world interfaces.''
; [[Development/Tutorials/D-Bus/Creating Interfaces|Creating D-Bus Interfaces]]
:''Learn how to expose functionality in your application by creating and using custom D-Bus interfaces. Covers generating the XML descriptions, instantiating interfaces at run time and setting up the build system with CMake.''
; [[Development/Tutorials/D-Bus/Autostart Services|D-Bus Autostart Services]]
:''Turn your application into a D-Bus autostart service with this tutorial. This D-Bus feature, also known as "D-Bus service activation", will ensure that even when your application isn't running that D-Bus calls made to it will work by relying on the D-Bus daemon itself to start your app if and when needed.''
; [[Development/Tutorials/Porting_to_D-Bus|Porting from DCOP to D-Bus]]
: ''Port your applications from DCOP to D-Bus with this handy guide.''

=== Konqueror ===
; [[Development/Tutorials/Creating Konqueror Service Menus|Creating Konqueror Service Menus]]
:''This tutorial shows you how to create mimetype-specific actions in Konqueror's context menu (aka "servicemenus").''

=== Kross ===
; [[Development/Tutorials/Kross/Introduction|Introduction to Kross]]
:''An introduction to the Kross Scripting Framework.''

; [[Development/Tutorials/Kross/Hello_World|Hello World]]
:''A first application with working kross code.''

; [[Development/Tutorials/Kross/Call_Functions_in_Kross|Calling Functions in Kross]]
:''Simple demonstration of calling scripting functions''

; [[Development/Tutorials/Kross/Connecting_Signals_and_slots_in_Kross|Connecting Signals and Slots in Kross]]
:''Simple demonstration of connecting object signals with script slots''

; [[Development/Tutorials/Kross/Scripts-as-Plugins|Scripts as Plugins with Kross]]
:''This tutorial provides a step-by-step introduction how to integrate scripts as plugins into a KDE application.''

; [[Development/Tutorials/Kross/Scripts-as-KPlugins|Load Kross Scripts as KPlugins]]
:''This tutorial provides a step-by-step introduction how to load scripts as KPlugins.''

; [[Development/Tutorials/Kross/Script-Actions|Placing script actions in your application menus ]]
:''Simple demonstration on how to extend you application menus to execute script files.''

=== KOffice ===
; [[Development/Tutorials/KOffice Overview|KOffice Overview]]
:''This document shows an overview of the different KOffice plugin types and tells you what each of their purpose and strengths are.'' If you are new with KOffice plugins, this is the place to start.

; [[Development/Tutorials/Write a Flake Plugin|Creating KOffice Flake Plugins]]
:''This tutorial shows you how you can build a plugin for KOffice applications to allow you embed content in ODF documents using Flake.''

; [[Development/Tutorials/KWord Scripting|KWord Scripting]]
:''This tutorial shows how to script KWord with Python, Ruby or JavaScript using Kross.''

; [[Development/Tutorials/KSpread Scripting|KSpread Scripting]]
:''This tutorial shows how to script KSpread with Python, Ruby or JavaScript using Kross.''

; [[Development/Tutorials/Krita Scripting|Krita Scripting]]
:''This tutorial shows how to script Krita with Python, Ruby or JavaScript using Kross.''

=== SuperKaramba ===
; [[Development/Tutorials/SuperKaramba|SuperKaramba Tutorial]]
:''This tutorial provides an overview of SuperKaramba, theme files and scripting with Python, Ruby and JavaScript.''

== Plugins and KParts ==

; [[Development/Tutorials/Writing kontact plugins|Writing kontact plugins]]:''Kontact plugins are KParts. This tutorial describes how you can write one.''

; [[Development/Tutorials/Using KParts|Using KParts]]:''Learn how to load a KPart into an application window.''

== Search and Metadata ==

=== Strigi ===

; [[Development/Tutorials/Writing file analyzers|Writing file analyzers]]
:''File analyzers extract data from files to display in the file dialogs and file managers. The data gathered this way is also used to search for files. KDE4 allows the use of multiple analyzers per file type. This tutorial describes how you can write new analyzers.''

=== [http://nepomuk.kde.org Nepomuk] ===

; [[Development/Tutorials/Metadata/Nepomuk/Quickstart|Nepomuk Quickstart]]
:''How to use Nepomuk resources in a quick and painless way without much fuss.''

; [[Development/Tutorials/Metadata/Nepomuk/RDFIntroduction|RDF and Ontologies in Nepomuk]]
:''An introduction to RDF and the usage of ontologies in Nepomuk.''

; [[Development/Tutorials/Metadata/Nepomuk/Resources|Handling Resources with Nepomuk]]
:''Nepomuk is the KDE library which provides easy access to metadata in the Nepomuk system. Learn how to make your application create and read metadata using the Nepomuk system.''

; [[Development/Tutorials/Metadata/Nepomuk/ResourceGenerator|Using the Nepomuk Resource Generator]]
:''Nepomuk includes a resource generator which creates convenience classes for handling metadata.''

; [[Development/Tutorials/Metadata/Nepomuk/NepomukServer|The Nepomuk Server]]
:''The Nepomuk Server hosts the main Nepomuk data repository and can be accessed directly via a Soprano API.''

; [[Development/Tutorials/Metadata/Nepomuk/NepomukServices|Nepomuk Services]]
:''The Nepomuk Server manages a set of Nepomuk services.''

; [[Development/Tutorials/Metadata/Nepomuk/AdvancedQueries|Advanced Queries]]
:''The real power of Nepomuk can only be exposed when performing fancy queries on the data repository. This tutorial provides an introduction to semantic and full text queries in Nepomuk.''

== Hardware Awareness (Solid) ==

;[[Development/Tutorials/Solid_Tutorials|Introduction to Solid]]
:''An introduction to using the Solid hardware discovery and interaction system in KDE applications.''

;[[Development/Tutorials/Solid_Network_Tutorial|Accessing Network Information]]
:''How to use the Solid system to get information about the network''

== Multimedia (Phonon) ==

;[[Development/Tutorials/Phonon/Introduction|Phonon]]
:''How to start with the multimedia API''

:''How to compile and use Phonon and its GStreamer backend on Linux using Qt 4.3.x''
::''This article gives you a quick brief of how you can use checkout, compile Phonon and its GStreamer backend on GNU/Linux with just Qt 4.3.x. Towards the end, the article also describes how a developer can make use of Phonon to create simple audio and video players. You can read the article [http://www.vcreatelogic.com/oss/docs/CompilingPhononOnLinux.pdf here]. You can download the editable OpenDocumentText file from [http://www.prashanthudupa.com/phonon/CompilingPhononOnLinux.odt here].''

== Plasma ==

;[[Development/Tutorials/Plasma/GettingStarted_(es)|Primeros pasos con los Plasmoids]]
:''Crea tu primer widget de Plasma, o Plasmoid, en C++ con un fondo SVG, un icono y algo de texto''.

;[[Development/Tutorials/Plasma/DataEngines|Escribir DataEngine]]
:''DataEngines proporcionan una [http://api.kde.org/4.0-api/kdebase-apidocs/workspace/libs/plasma/html/classPlasma_1_1DataEngine.html interfaz estandarizada] para varias fuentes de datos para usarlos en las visualizaciones. Aprende que es un DataEngine y como escribir uno''.

;[[Development/Tutorials/Plasma/UsingDataEngines|Usar DataEngines en los Plasmoids]]
:''Con un DateEngine, es posible recuperar datos para mostrarlos de una forma simple y estandar. Este tutorial abarca el tema de como usar DataEngines en los Plasmoids''.

;[[Development/Tutorials/Plasma/AbstractRunner|Crear Runners]]
:''Los "Runners" son plugins que proporcionan la funcionalidad de busqueda basada en acciones mediante el dialogo "ejecutar orden" en el area de trabajo de Plasma. Estos plugins pueden ser usados por cualquier aplicación que enlace con libplasma''.

;[[Development/Tutorials/Plasma/Theme|Creating a Plasma Theme]]
:''Guía para crear tu primer tema de Plasma.''

;[[Development/Tutorials/Plasma/UsingExtenders|Usar Extenders]]
:''Esta guía te muestra como crear un simple applet (destripando el applet kuiserver) que use extenders''.

== Communication (Decibel) ==

;[[Development/Tutorials/Decibel/GettingStarted|Getting started with Decibel]]
:''This tutorial describes how to set up Decibel.''

;[[Development/Tutorials/Decibel/Handling_TextChannels|Handling TextChannels]]
:''This tutorial introduces the basics of handling incoming TextChannels by guiding you through building a simple text chat application.''

== Personal Information Management (Akonadi) ==

;[[Development/Tutorials/Akonadi/Resources|Developing Akonadi Resources]]
:''Akonadi Resources are agent programs which transport PIM data between Akonadi and a backend (files, servers, etc)''

== Kate / Kwrite ==

;[[Development/Tutorials/Kate/KTextEditor Plugins|Getting started with KTextEditor plugins]]
:''Creating your first KTextEditor plugin''

;[[Development/Tutorials/Kate/KTextEditor_Plugins_Advanced|Developing a plugin with configuration dialog]]
:''Adding a configuration dialog to the Time & Date example''

;[[Development/Tutorials/Kate/KTextEditor_Example|A small Editor]]
:''Create a small application using KTextEditor''

==Printing==

;[[Development/Tutorials/Printing Hello World|Hello World]]
:''Introduction to the KDE printing system''

;[[Development/Tutorials/Printing Print Dialog|Print Dialog]]
:''Using the KDE print dialog''

== Get Hot New Stuff ==
; [[Development/Tutorials/K_Hot_New_Stuff2|New introduction to KGet Hot New Stuff2]]
:''A short tutorial about how to use KHotNewStuff2 in your application.''

* old links for KNS1 content:
; [[Development/Tutorials/Introduction to Get Hot New Stuff|Introduction to Get Hot New Stuff]]
:''An introduction to the developer-friendly network update system that allows KDE applications to fetch new application data at runtime in a user friendly manner.''

;[[Development/Tutorials/KNewStuffSecure|KNewStuff Secure]] ([http://developer.kde.org/documentation/tutorials/knewstuffsecure/index.html Original Link])
:''Tutorial showing how to share resources in a secured way (KDE 3.4 and later).'' By András Mantia <amantia@kde.org>.

== Goya ==
; [[Development/Tutorials/Introduction to Goya usage|Introduction to Goya usage]]
:''An introduction for the Goya subsystem usage, which allows you to easily add widgets to your itemviews and connect their signals to your code, as they were real widgets.''

; [[Development/Tutorials/Introduction to Goya usage 2|Introduction to Goya usage (part 2)]]
:''The second part of the tutorial, with a slightly more complex example than the first part.''

== Rapid Application Development ==

=== Python ===

;[[Development/Tutorials/Python introduction to signals and slots|101 Introduction to signals and slots]]
:''A simple introduction to Qt's signal and slot architecture.''

=== Ruby ===

;[http://developer.kde.org/language-bindings/ruby/kde3tutorial/index.html KDE Ruby Korundum tutorial]
:''A ruby version of Antonio Larrosa Jiménez's KDE tutorial by Richard Dale. See the [http://developer.kde.org/language-bindings/ruby/index.html Ruby Developers Corner] for Qt tutorials and other info.''

;[[Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby Tutorial]]
:''Trolltech's fabulous introductory tutorial to Qt, translated to Ruby.''

;[[Development/Tutorials/Plasma/RubyApplet|Creating a Plasma Widget in Ruby]]
:''Tutorial that shows how to create your first Plasma Applet using the Ruby language.''

=== Shell ===

;[[Development/Tutorials/Shell_Scripting_with_KDE_Dialogs|Shell Scripting with KDE dialogs]] ([http://developer.kde.org/documentation/tutorials/kdialog/t1.html Original Link])
:''Tutorial by [mailto:bradh@frogmouth.net Brad Hards] that describes how to use KDE dialogs in shell scripts with kdialog. It is presented as an example based tutorial.''

== Graphics Programming ==

;[[Development/Tutorials/Graphics/Performance|QPainter Perfomance]]
:''Hints on avoiding common mistakes leading to poor performance when using QPainter''

== Using the KDE Games Libraries ==
;[[Development/Tutorials/Games/KStandardGameAction| KStandardGameAction]]
:''Using libkdegames to make your game fit the kdegames standard''
;[[Development/Tutorials/Games/Highscores| Highscores]]
:''Implementing a simple highscore table into your game''
;[[Development/Tutorials/Games/Theme Selector| Theme Selector]]
:''Using the libkdegames theme selection dialog''
;[[Development/Tutorials/Games/Palapeli Patterns| Palapeli Patterns]]
:''Creating a pattern for Palapeli''

== Other tutorials ==

=== 2D Plotting (KPlotWidget) ===
;[[Development/Tutorials/KPlotWidget|Using the KDE data-plotting widget]]
:''This tutorial introduces KPlotWidget, which is used for 2-D data plotting. It includes information on simple usage of the widget (including adding and modifying data sets, and customizing the plot axes and labels), and advanced customization (including extending the widget through sub-classing).''

=== Spelling and Grammar Checking (Sonnet) ===
;[[Development/Tutorials/Sonnet/SonnetTutorial|Adding spell-checking or grammar-checking to KDE applications]]
:''This tutorial introduces Sonnet and how one may use it to add language correction to your KDE application. Sonnet's auxiliary features shall be described in a separate tutorial.''

=== Pixmap cache (KPixmapCache) ===
;[[Development/Tutorials/KPixmapCache|Using the KDE pixmap cache]]
:''This tutorial shows how to use KPixmapCache to cache e.g. pixmaps generated from SVGs or some data.''

=== Using MarbleWidget (Marble) ===
;[[Development/Tutorials/MarbleWidget|Using MarbleWidget]]
:''This short tutorial describes how to use the MarbleWidget in your project''

=== Using local SCM for KDE development ===
;[[Development/Tutorials/Git|Using Git to develop for KDE]]
:''This tutorial shows how to use Git to develop for KDE''

== KDE2 and KDE3 Materials ==

;[[Development/Tutorials/KDE3|KDE3 Tutorials]]
:''These tutorials cover topics related to KDE3.''

;[[Development/Tutorials/KDE2|KDE2 Tutorials]]
:''These tutorials cover topics related to KDE2.''

[[Category:KDE4]]

Development/Tutorials (es)

2008-09-23T20:09:31Z

Edumardo: translation to spanish, update

{{Template:I18n/Language Navigation Bar|Development/Tutorials}}
{{warning_(es)| Traducción en curso: solo hasta el punto 4, también está traducido el punto 13 (Plasma)}}
Los tutoriales son la forma más rápida de encontrar lo que KDE puede hacer por usted y como hacerlo. Aquí tienes una lista de los tutoriales disponibles actualmente para KDE4. Material para KDE3 y KDE2 está disponible al final de la página.

== Introducción a la programación en KDE4 ==
Estś interesado en escribir aplicacion en KDE4? Esta serie de tutoriales están dirigidos a personas totalmente novatas en la programación en KDE4.
;[[Development/Tutorials/First program_(es)|Hola Mundo]]
:''Una introducción preliminar a los aspectos básicos de la programación en KDE4.''

;[[Development/Tutorials/Using KXmlGuiWindow_(es)|Crear la ventana principal]]
:''Este tutorial te muestra la magia de la cosa mas importante en una aplicación: la ventana principal''

;[[Development/Tutorials/Using KActions_(es)|Usar KActions]]
:''Como añadir acciones a los menús y a las toolbars.''

;[[Development/Tutorials/Saving and loading|Guardar y Abrir]]
:''Introducción a la biblioteca KIO mientras añades soporte para guardar y abrir en tu aplicación.''

;[[Development/Tutorials/KCmdLineArgs|Argumentos en la línea de órdenes]]
:''Añade la capacidad de especificar a nuestro editor que archivo abrir desde la línea de ordenes.''

== Básicos ==
;[[Development/Tutorials/KDE4 Porting Guide|Portar tu aplicación]]
:''Ayuda para portar aplicaciones de Qt3/KDE3 a Qt4/KDE4.''

;[[Development/Tutorials/CMake|Introducción a CMake]]
:''Como usar el sistema de construcción CMake usado por KDE4.''

;[[Development/Tutorials/Common Programming Mistakes|Errores comunes de programación]]
:''Varios errores comunes que se presentan en el desarrollo de aplicaciones Qt y KDE y como evitarlos.''

;[[Development/Tutorials/Using Qt Designer|Usar Qt Designer para diseñar interfaces de usuario]]
:''Como crear archivos UI con el diseñador, y como integrarlos después en un programa KDE.''

;[[Development/Tutorials/Creating Libraries|Crear bibliotecas para compartir código]]
:''Como añadir la biblioteca al "buildsystem" y como preparar el código fuente.''
:''How to add the library to the buildsystem and how to prepare the source code.''

== Comprobación y depurado ==

;[[Development/Tutorials/Debugging|Depurar tu aplicación]]
:''Consejos, herramientas y técnicas para depurar tu aplicación KDE.''

;[[Development/Tutorials/Unittests|Escribir "unittests" para Qt4 y KDE4 con QTestLib]] ([http://developer.kde.org/documentation/tutorials/writingunittests/writingunittests.html enlace original])
:''Tutorial de [mailto:bradh@frogmouth.net Brad Hards] que describe como escribir unittests mediante la framework QTestLib. El tutorial se realiza con un ejemplo, y aun está en desarrollo.''

;[[Development/Tutorials/Code_Checking|Maneras semiautomáticas de detectar errores en el código]]
:''Técnicas que puedes usar para detectar errores en el código KDE.''

== Gestión de los datos de configuración con KConfig ==

;[[Development/Tutorials/KConfig|Introducción a KConfig]]
:''Una sinopsis de las clases de KConfig y como usarlas en el código de tu aplicación.''

;[[Development/Tutorials/Using KConfig XT|Uso de KConfig XT]]
:''Tutorial sobre como usar eficientemente el framework KConfig XT''

;[[Development/Tutorials/Updating KConfig Files|Actualizando archivos con KConfig]]
:''Tutorial sobre como escribir un script de actualización para conservar los cambios de tu archivo de configuración de tu aplicación y sincornizarlo con el archivo de configuración del usuario''

== Services: Applications and Plugins ==
;[[Development/Tutorials/Services/Introduction|Introduction to the Services Framework]]
:''An overview of the services framework in KDE and what it provides the application developer. Covers the system configuration cache (SyCoCa), the source data files and what the indexed information can be used for.''

;[[Development/Tutorials/Services/Traders|Finding Services Using Trader Queries]]
:''How to find services, such as plugins or mimetypes, that are indexed in the SyCoCa using Trader Query Syntax''

;[[Development/Tutorials/Services/Plugins|Creating and Loading Plugins Using KService]]
:''Learn how to define custom plugin types, find installed plugins (including 3rd party plugins) and load them in an easy and portable fashion using KService.''

== Localization ==
See also [[Localization|Localization portal]].

;[[Development/Tutorials/Localization/Unicode|Introduction To Unicode]]
:''An introduction to what Unicode is as well as how to handle Unicode data in KDE applications.''

; [[Development/Tutorials/Localization/i18n|Writing Applications With Localization In Mind]]
:''This tutorial covers what localization is, why it's important and how to ensure your application is ready to be localized. A must read for all application developers.''

; [[Development/Tutorials/Localization/i18n Mistakes|Avoiding Common Localization Pitfalls]]
:''There are several common mistakes that prevent applications from being properly localized. Find out what they are and how to easily avoid them in this tutorial.''

; [[Development/Tutorials/Localization/Building KDE's l10n Module|Building KDE's Localization Module]]
:''Building and installing language support from KDE's localization (l10n) module is a good idea for those working on applications in the main KDE repository. Doing so will allow you to test your application in another language and spot problem areas. Learn how to do just that in this tutorial.''

; [[Development/Tutorials/Localization/i18n Build Systems|Incorporating i18n Into the Build System]]
:''Once your application is ready to be localized, the next step is to ensure that translation files are built automatically and kept up to date. This tutorial covers the necessary CMakeFiles.txt additions as well the process of distributing the resulting message catalogs with your application.''

; [[Development/Tutorials/Localization/i18n Challenges|Common i18n Challenges and Solutions]]
:''This tutorial covers challenges that you may eventually run into such as translating handbooks and other data that exists outside of the source code, merging and handling obsolete .po files, dealing with freezes, coding in languages other than English and creating independent releases of or moving applications between KDE modules.''

; [[Development/Tutorials/Localization/i18n_Semantics|Semantic Markup of Messages]]
:''To ensure consistent presentation and more meaningful representations of messages in applications, semantic markup can be applied to messages marked for translation using the KUIT system. This tutorial describes how this system works.''

; [[Development/Tutorials/Localization/i18n Krazy|Automated i18n Code Checking]]
:''The Krazy code checker scans KDE's code and reports common i18n mistakes.''

== Documentation ==

;[[Development/Tutorials/API_Documentation|API Documentation]]
:''This tutorial explains how to document your APIs properly.''

;[[Development/Tutorials/Man_Pages|Man Pages]]
:''Writing and Generating Reference Manual Pages.''

== Application Automation and Scripting ==

=== D-Bus ===
; [[Development/Tutorials/D-Bus/Introduction|Introduction to D-Bus]]
:''A straight-forward introduction to the core concepts in D-Bus from an application developer's perspective, this tutorial covers what D-Bus is and how it can be used by applications.''
; [[Development/Tutorials/D-Bus/Accessing Interfaces|Accessing D-Bus Interfaces]]
:''A step-by-step guide to calling D-Bus methods and connecting to D-Bus signals using QtDBus.''
; [[Development/Tutorials/D-Bus/Intermediate_D-Bus|Intermediate D-Bus]]
:''Tips to make use of QtDBus when faced with problematic real-world interfaces.''
; [[Development/Tutorials/D-Bus/Creating Interfaces|Creating D-Bus Interfaces]]
:''Learn how to expose functionality in your application by creating and using custom D-Bus interfaces. Covers generating the XML descriptions, instantiating interfaces at run time and setting up the build system with CMake.''
; [[Development/Tutorials/D-Bus/Autostart Services|D-Bus Autostart Services]]
:''Turn your application into a D-Bus autostart service with this tutorial. This D-Bus feature, also known as "D-Bus service activation", will ensure that even when your application isn't running that D-Bus calls made to it will work by relying on the D-Bus daemon itself to start your app if and when needed.''
; [[Development/Tutorials/Porting_to_D-Bus|Porting from DCOP to D-Bus]]
: ''Port your applications from DCOP to D-Bus with this handy guide.''

=== Konqueror ===
; [[Development/Tutorials/Creating Konqueror Service Menus|Creating Konqueror Service Menus]]
:''This tutorial shows you how to create mimetype-specific actions in Konqueror's context menu (aka "servicemenus").''

=== Kross ===
; [[Development/Tutorials/Kross/Introduction|Introduction to Kross]]
:''An introduction to the Kross Scripting Framework.''

; [[Development/Tutorials/Kross/Hello_World|Hello World]]
:''A first application with working kross code.''

; [[Development/Tutorials/Kross/Call_Functions_in_Kross|Calling Functions in Kross]]
:''Simple demonstration of calling scripting functions''

; [[Development/Tutorials/Kross/Connecting_Signals_and_slots_in_Kross|Connecting Signals and Slots in Kross]]
:''Simple demonstration of connecting object signals with script slots''

; [[Development/Tutorials/Kross/Scripts-as-Plugins|Scripts as Plugins with Kross]]
:''This tutorial provides a step-by-step introduction how to integrate scripts as plugins into a KDE application.''

; [[Development/Tutorials/Kross/Scripts-as-KPlugins|Load Kross Scripts as KPlugins]]
:''This tutorial provides a step-by-step introduction how to load scripts as KPlugins.''

; [[Development/Tutorials/Kross/Script-Actions|Placing script actions in your application menus ]]
:''Simple demonstration on how to extend you application menus to execute script files.''

=== KOffice ===
; [[Development/Tutorials/KOffice Overview|KOffice Overview]]
:''This document shows an overview of the different KOffice plugin types and tells you what each of their purpose and strengths are.'' If you are new with KOffice plugins, this is the place to start.

; [[Development/Tutorials/Write a Flake Plugin|Creating KOffice Flake Plugins]]
:''This tutorial shows you how you can build a plugin for KOffice applications to allow you embed content in ODF documents using Flake.''

; [[Development/Tutorials/KWord Scripting|KWord Scripting]]
:''This tutorial shows how to script KWord with Python, Ruby or JavaScript using Kross.''

; [[Development/Tutorials/KSpread Scripting|KSpread Scripting]]
:''This tutorial shows how to script KSpread with Python, Ruby or JavaScript using Kross.''

; [[Development/Tutorials/Krita Scripting|Krita Scripting]]
:''This tutorial shows how to script Krita with Python, Ruby or JavaScript using Kross.''

=== SuperKaramba ===
; [[Development/Tutorials/SuperKaramba|SuperKaramba Tutorial]]
:''This tutorial provides an overview of SuperKaramba, theme files and scripting with Python, Ruby and JavaScript.''

== Plugins and KParts ==

; [[Development/Tutorials/Writing kontact plugins|Writing kontact plugins]]:''Kontact plugins are KParts. This tutorial describes how you can write one.''

; [[Development/Tutorials/Using KParts|Using KParts]]:''Learn how to load a KPart into an application window.''

== Search and Metadata ==

=== Strigi ===

; [[Development/Tutorials/Writing file analyzers|Writing file analyzers]]
:''File analyzers extract data from files to display in the file dialogs and file managers. The data gathered this way is also used to search for files. KDE4 allows the use of multiple analyzers per file type. This tutorial describes how you can write new analyzers.''

=== [http://nepomuk.kde.org Nepomuk] ===

; [[Development/Tutorials/Metadata/Nepomuk/Quickstart|Nepomuk Quickstart]]
:''How to use Nepomuk resources in a quick and painless way without much fuss.''

; [[Development/Tutorials/Metadata/Nepomuk/RDFIntroduction|RDF and Ontologies in Nepomuk]]
:''An introduction to RDF and the usage of ontologies in Nepomuk.''

; [[Development/Tutorials/Metadata/Nepomuk/Resources|Handling Resources with Nepomuk]]
:''Nepomuk is the KDE library which provides easy access to metadata in the Nepomuk system. Learn how to make your application create and read metadata using the Nepomuk system.''

; [[Development/Tutorials/Metadata/Nepomuk/ResourceGenerator|Using the Nepomuk Resource Generator]]
:''Nepomuk includes a resource generator which creates convenience classes for handling metadata.''

; [[Development/Tutorials/Metadata/Nepomuk/NepomukServer|The Nepomuk Server]]
:''The Nepomuk Server hosts the main Nepomuk data repository and can be accessed directly via a Soprano API.''

; [[Development/Tutorials/Metadata/Nepomuk/NepomukServices|Nepomuk Services]]
:''The Nepomuk Server manages a set of Nepomuk services.''

; [[Development/Tutorials/Metadata/Nepomuk/AdvancedQueries|Advanced Queries]]
:''The real power of Nepomuk can only be exposed when performing fancy queries on the data repository. This tutorial provides an introduction to semantic and full text queries in Nepomuk.''

== Hardware Awareness (Solid) ==

;[[Development/Tutorials/Solid_Tutorials|Introduction to Solid]]
:''An introduction to using the Solid hardware discovery and interaction system in KDE applications.''

;[[Development/Tutorials/Solid_Network_Tutorial|Accessing Network Information]]
:''How to use the Solid system to get information about the network''

== Multimedia (Phonon) ==

;[[Development/Tutorials/Phonon/Introduction|Phonon]]
:''How to start with the multimedia API''

:''How to compile and use Phonon and its GStreamer backend on Linux using Qt 4.3.x''
::''This article gives you a quick brief of how you can use checkout, compile Phonon and its GStreamer backend on GNU/Linux with just Qt 4.3.x. Towards the end, the article also describes how a developer can make use of Phonon to create simple audio and video players. You can read the article [http://www.vcreatelogic.com/oss/docs/CompilingPhononOnLinux.pdf here]. You can download the editable OpenDocumentText file from [http://www.prashanthudupa.com/phonon/CompilingPhononOnLinux.odt here].''

== Plasma ==

;[[Development/Tutorials/Plasma/GettingStarted|Primeros pasos con los Plasmoids]]
:''Crea tu primer widget de Plasma, o Plasmoid, en C++ con un fondo SVG, un icono y algo de texto''.

;[[Development/Tutorials/Plasma/DataEngines|Escribir DataEngine]]
:''DataEngines proporcionan una [http://api.kde.org/4.0-api/kdebase-apidocs/workspace/libs/plasma/html/classPlasma_1_1DataEngine.html interfaz estandarizada] para varias fuentes de datos para usarlos en las visualizaciones. Aprende que es un DataEngine y como escribir uno''.

;[[Development/Tutorials/Plasma/UsingDataEngines|Usar DataEngines en los Plasmoids]]
:''Con un DateEngine, es posible recuperar datos para mostrarlos de una forma simple y estandar. Este tutorial abarca el tema de como usar DataEngines en los Plasmoids''.

;[[Development/Tutorials/Plasma/AbstractRunner|Crear Runners]]
:''Los "Runners" son plugins que proporcionan la funcionalidad de busqueda basada en acciones mediante el dialogo "ejecutar orden" en el area de trabajo de Plasma. Estos plugins pueden ser usados por cualquier aplicación que enlace con libplasma''.

;[[Development/Tutorials/Plasma/Theme|Creating a Plasma Theme]]
:''Guía para crear tu primer tema de Plasma.''

;[[Development/Tutorials/Plasma/UsingExtenders|Usar Extenders]]
:''Esta guía te muestra como crear un simple applet (destripando el applet kuiserver) que use extenders''.

== Communication (Decibel) ==

;[[Development/Tutorials/Decibel/GettingStarted|Getting started with Decibel]]
:''This tutorial describes how to set up Decibel.''

;[[Development/Tutorials/Decibel/Handling_TextChannels|Handling TextChannels]]
:''This tutorial introduces the basics of handling incoming TextChannels by guiding you through building a simple text chat application.''

== Personal Information Management (Akonadi) ==

;[[Development/Tutorials/Akonadi/Resources|Developing Akonadi Resources]]
:''Akonadi Resources are agent programs which transport PIM data between Akonadi and a backend (files, servers, etc)''

== Kate / Kwrite ==

;[[Development/Tutorials/Kate/KTextEditor Plugins|Getting started with KTextEditor plugins]]
:''Creating your first KTextEditor plugin''

;[[Development/Tutorials/Kate/KTextEditor_Plugins_Advanced|Developing a plugin with configuration dialog]]
:''Adding a configuration dialog to the Time & Date example''

;[[Development/Tutorials/Kate/KTextEditor_Example|A small Editor]]
:''Create a small application using KTextEditor''

==Printing==

;[[Development/Tutorials/Printing Hello World|Hello World]]
:''Introduction to the KDE printing system''

;[[Development/Tutorials/Printing Print Dialog|Print Dialog]]
:''Using the KDE print dialog''

== Get Hot New Stuff ==
; [[Development/Tutorials/K_Hot_New_Stuff2|New introduction to KGet Hot New Stuff2]]
:''A short tutorial about how to use KHotNewStuff2 in your application.''

* old links for KNS1 content:
; [[Development/Tutorials/Introduction to Get Hot New Stuff|Introduction to Get Hot New Stuff]]
:''An introduction to the developer-friendly network update system that allows KDE applications to fetch new application data at runtime in a user friendly manner.''

;[[Development/Tutorials/KNewStuffSecure|KNewStuff Secure]] ([http://developer.kde.org/documentation/tutorials/knewstuffsecure/index.html Original Link])
:''Tutorial showing how to share resources in a secured way (KDE 3.4 and later).'' By András Mantia <amantia@kde.org>.

== Goya ==
; [[Development/Tutorials/Introduction to Goya usage|Introduction to Goya usage]]
:''An introduction for the Goya subsystem usage, which allows you to easily add widgets to your itemviews and connect their signals to your code, as they were real widgets.''

; [[Development/Tutorials/Introduction to Goya usage 2|Introduction to Goya usage (part 2)]]
:''The second part of the tutorial, with a slightly more complex example than the first part.''

== Rapid Application Development ==

=== Python ===

;[[Development/Tutorials/Python introduction to signals and slots|101 Introduction to signals and slots]]
:''A simple introduction to Qt's signal and slot architecture.''

=== Ruby ===

;[http://developer.kde.org/language-bindings/ruby/kde3tutorial/index.html KDE Ruby Korundum tutorial]
:''A ruby version of Antonio Larrosa Jiménez's KDE tutorial by Richard Dale. See the [http://developer.kde.org/language-bindings/ruby/index.html Ruby Developers Corner] for Qt tutorials and other info.''

;[[Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby Tutorial]]
:''Trolltech's fabulous introductory tutorial to Qt, translated to Ruby.''

;[[Development/Tutorials/Plasma/RubyApplet|Creating a Plasma Widget in Ruby]]
:''Tutorial that shows how to create your first Plasma Applet using the Ruby language.''

=== Shell ===

;[[Development/Tutorials/Shell_Scripting_with_KDE_Dialogs|Shell Scripting with KDE dialogs]] ([http://developer.kde.org/documentation/tutorials/kdialog/t1.html Original Link])
:''Tutorial by [mailto:bradh@frogmouth.net Brad Hards] that describes how to use KDE dialogs in shell scripts with kdialog. It is presented as an example based tutorial.''

== Graphics Programming ==

;[[Development/Tutorials/Graphics/Performance|QPainter Perfomance]]
:''Hints on avoiding common mistakes leading to poor performance when using QPainter''

== Using the KDE Games Libraries ==
;[[Development/Tutorials/Games/KStandardGameAction| KStandardGameAction]]
:''Using libkdegames to make your game fit the kdegames standard''
;[[Development/Tutorials/Games/Highscores| Highscores]]
:''Implementing a simple highscore table into your game''
;[[Development/Tutorials/Games/Theme Selector| Theme Selector]]
:''Using the libkdegames theme selection dialog''
;[[Development/Tutorials/Games/Palapeli Patterns| Palapeli Patterns]]
:''Creating a pattern for Palapeli''

== Other tutorials ==

=== 2D Plotting (KPlotWidget) ===
;[[Development/Tutorials/KPlotWidget|Using the KDE data-plotting widget]]
:''This tutorial introduces KPlotWidget, which is used for 2-D data plotting. It includes information on simple usage of the widget (including adding and modifying data sets, and customizing the plot axes and labels), and advanced customization (including extending the widget through sub-classing).''

=== Spelling and Grammar Checking (Sonnet) ===
;[[Development/Tutorials/Sonnet/SonnetTutorial|Adding spell-checking or grammar-checking to KDE applications]]
:''This tutorial introduces Sonnet and how one may use it to add language correction to your KDE application. Sonnet's auxiliary features shall be described in a separate tutorial.''

=== Pixmap cache (KPixmapCache) ===
;[[Development/Tutorials/KPixmapCache|Using the KDE pixmap cache]]
:''This tutorial shows how to use KPixmapCache to cache e.g. pixmaps generated from SVGs or some data.''

=== Using MarbleWidget (Marble) ===
;[[Development/Tutorials/MarbleWidget|Using MarbleWidget]]
:''This short tutorial describes how to use the MarbleWidget in your project''

=== Using local SCM for KDE development ===
;[[Development/Tutorials/Git|Using Git to develop for KDE]]
:''This tutorial shows how to use Git to develop for KDE''

== KDE2 and KDE3 Materials ==

;[[Development/Tutorials/KDE3|KDE3 Tutorials]]
:''These tutorials cover topics related to KDE3.''

;[[Development/Tutorials/KDE2|KDE2 Tutorials]]
:''These tutorials cover topics related to KDE2.''

[[Category:KDE4]]

User:Edumardo

2008-09-21T21:40:06Z

Edumardo:

Hello, soy miembro del [[KDE_TechBase:Contributors#Spanish_Team|Spanish translation team]]. Estaba interesado en desarrollar algo sobre KDE4, y como la información que encontré era casi toda en ingles, me dije que podría traducirla yo mismo.

=== Traduciendo o Actualizando ===
*http://techbase.kde.org/Development/Tutorials_(es)

=== Traducido o actualizado ===
Aqui tienes una lista de las páginas que he traducido o actualizado con la versión inglesa. Destacar que algunas ya estaban traducidas por lo que no todo el mérito es mio:

*http://techbase.kde.org/Development_(es)
;
*http://techbase.kde.org/Development/Architecture/KDE4_(es)
**http://techbase.kde.org/Development/Architecture/KDE4/Plasma_(es)
**http://techbase.kde.org/Development/Architecture/KDE4/KParts_(es)
**http://techbase.kde.org/Development/Architecture/KDE4/Solid_(es)
**http://techbase.kde.org/Development/Architecture/KDE4/Phonon_(es)
**http://techbase.kde.org/Development/Architecture/KDE4/Providing_Online_Help_(es)
**http://techbase.kde.org/Development/Architecture/KDE4/KGGZ_(es)
;
*http://techbase.kde.org/Development/Tutorials/First_program_(es)
*http://techbase.kde.org/Development/Tutorials/Using_KXmlGuiWindow_(es)
*http://techbase.kde.org/Development/Tutorials/Using_KActions_(es)
;
*http://techbase.kde.org/Development/Tools_(es)
;
*http://techbase.kde.org/Development/FAQs_(es)
;
*http://techbase.kde.org/Development/Languages_(es)
;
*http://techbase.kde.org/Development/CMake_(es)
;
*http://techbase.kde.org/Projects/KNS2_(es)
;
*http://techbase.kde.org/Template:TutorialBrowser_(es)
*http://techbase.kde.org/Template:Tip_(es)

Development/Tutorials/Using KActions (es)

2008-09-21T21:39:40Z

Edumardo: translation to spanish

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Using_KActions}}

{{TutorialBrowser_(es)|

series=Tutorial para principiantes|

name=Como usar KActions y XMLGUI|

pre=[[Development/Tutorials/Using_KXmlGuiWindow_(es)|Tutorial 2 - KXmlGuiWindow]], Conocimiento básico de XML|

next=[[Development/Tutorials/Saving_and_loading|Tutorial 4 - Guardar y Abrir]]|

reading=Nada
}}

==Resumen==
Este tutorial introduce el concepto de las acciones. Las acciones son una forma unificada de proporcionar al usuario la forma de interactuar con tu programa.

Por ejemplo, si queremos permitir que el usuario del [[Development/Tutorials/Using_KXmlGuiWindow_(es)|Tutorial 2]] pueda borrar la caja de texto pulsando un botón de la barra de herramientas, desde una entrada del menú File o a través de un atajo de teclado, podremos realizarlo mediante un {{class|KAction}}.

[[image:introtokdetutorial3_(es).png|frame|center]]

==KAction==
Un {{class|KAction}} es un objeto que contiene toda la información sobre el icono y el atajo de teclado asociado a una determinada acción. La acción se conecta a un [http://doc.trolltech.com/latest/signalsandslots.html slot], que lleva a cabo el trabajo de la acción.

== El código ==

===main.cpp===
<code cppqt n>
#include <KApplication>
#include <KAboutData>
#include <KCmdLineArgs>

#include "mainwindow.h"

int main (int argc, char *argv[])
{
KAboutData aboutData( "tutorial3", "tutorial3",
ki18n("Tutorial 3"), "1.0",
ki18n("Area de texto usando KAction."),
KAboutData::License_GPL,
ki18n("Copyright (c) 2008 Developer") );
KCmdLineArgs::init( argc, argv, &aboutData );
KApplication app;

MainWindow* window = new MainWindow();
window->show();
return app.exec();
}
</code>
Pocas cosas han cambiado en <tt>main.cpp</tt>, solo se ha actualizado la declaración de KAboutData para indicar que ahora estamos en el tutorial 3.

===mainwindow.h===
<code cppqt n>
#ifndef MAINWINDOW_H
#define MAINWINDOW_H

#include <KXmlGuiWindow>
#include <KTextEdit>

class MainWindow : public KXmlGuiWindow
{
public:
MainWindow(QWidget *parent=0);

private:
KTextEdit* textArea;
void setupActions();
};

#endif
</code>
Sólo se ha añadido la función <tt>void setupActions()</tt>, que realizará el trabajo de configurar los KActions.

===mainwindow.cpp===
<code cppqt n>
#include "mainwindow.h"

#include <KApplication>
#include <KAction>
#include <KLocale>
#include <KActionCollection>
#include <KStandardAction>

MainWindow::MainWindow(QWidget *parent)
: KXmlGuiWindow(parent)
{
textArea = new KTextEdit;
setCentralWidget(textArea);

setupActions();
}

void MainWindow::setupActions()
{
KAction* clearAction = new KAction(this);
clearAction->setText(i18n("Limpiar"));
clearAction->setIcon(KIcon("document-new"));
clearAction->setShortcut(Qt::CTRL + Qt::Key_W);
actionCollection()->addAction("limpiar", clearAction);
connect(clearAction, SIGNAL(triggered(bool)),
textArea, SLOT(clear()));

KStandardAction::quit(kapp, SLOT(quit()),
actionCollection());

setupGUI();
}

</code>

==Explicación==
El archivo está basado en el código de KXmlGuiWindow del [[Development/Tutorials/Using_KXmlGuiWindow_(es)|Tutorial 2]]. La mayoría de los cambios están en <tt>mainwindow.cpp</tt>, un cambio estructural importante es que el constructor de MainWindow ahora llama a <tt>setupActions()</tt> en vez de a <tt>setupGUI()</tt>. En <tt>setupActions()</tt> va el nuevo código de KAction antes de llamar a <tt>setupGUI()</tt>.

===Creando el objeto KAction===
KAction se construye en varios pasos. El primero es incluir la biblioteca <tt>KAction</tt> y crear el KAction:
<code cppqt>
#include <KAction>
...
KAction* clearAction = new KAction(this);
</code>
Crear un KAction nuevo llamado <tt>clearAction</tt>.

===Estableciendo las propiedades de KAction===
====Texto====
Ahora que tenemos nuestro objeto KAction, podemos empezar a establecer sus propiedades. El siguiente código establece el texto que se mostrará en el menú y el de debajo del icono del <tt>KAction</tt> en la barra de herramientas:
<code cppqt>clearAction->setText(i18n("Limpiar"));</code>
Ten en cuenta que el texto se pasa a través de la función i18n(), esto es necesario para para que la UI pueda ser traducida (puedes encontrar mas información en el [[Development/Tutorials/Localization/i18n|tutorial de i18n]]).

====Icono====
Si la acción va a mostrarse en el la barra de herramientas, estaría bien que tuviera un icono que la representara. El siguiente código establece como icono el icono estándar de KDE <tt>document-new</tt> mediante el uso de la función <tt>setIcon()</tt>:
<code cppqt>clearAction->setIcon(KIcon("document-new"));</code>

====Atajo de teclado====
Establecer un atajo de teclado para lanzar nuestra acción es igual de simple:
<code cppqt>clearAction->setShortcut(Qt::CTRL + Qt::Key_W);</code>
Asocia Ctrl+W a la acción.

===Añadir a la colección===
Para que la acción sea accesible por el framework XMLGUI (explicado en profundidad mas adelante) debe añadirse a la ''colección de acciones'' de la aplicación. La colección de acciones es accesible mediante la función <tt>actionCollection()</tt>:
<code cppqt>
actionCollection()->addAction("limpiar", clearAction);
</code>
Con esta llamada, la KAction <tt>clearAction</tt> se añade a la colección y toma el nombre de ''limpiar''. Este nombre (''limpiar'') lo usa el framework XMLGUI para referirse a la acción.

====Conectando la acción====
Ahora que hemos establecido la acción, es necesario conectarla a algo útil. En este caso (porque queremos limpiar el área de texto), conectamos nuestra acción con la acción <tt>clear()</tt> perteneciente a KTextEdit (que como era de esperar, limpia KTextEdit):
<code cppqt>
connect( clearAction, SIGNAL( triggered(bool) ),
textArea, SLOT( clear() ) );
</code>
Es lo mismo que se llevaría a cabo en Qt con una {{qt|QAction}}.

===KStandardAction===
Para las acciones que normalmente aparecen en casi todas las aplicaciones KDE, como 'quit', 'save', y 'load', existen unas acciones ya creadas, accesibles a través de [http://api.kde.org/4.0-api/kdelibs-apidocs/kdeui/html/namespaceKStandardAction.html KStandardAction].

Son muy sencillas de usar. Una vez que has incluido las bibliotecas (<tt>#include <KStandardAction></tt>), simplemente añadelas con la función que quieras que realicen. Por ejemplo:
<code cppqt>KStandardAction::quit(kapp, SLOT(quit()), actionCollection());</code>
Crea una KAction con el icono correcto, el texto y el atajo de teclado, e incluso la añade al menú File.

==Añadir la acción a los menús y a las barras de herramientas==
Por el momento, hemos creado la nueva acción "Limpiar" pero no se ha asociado a ningún menú o barra de herramientas. Esto lo podemos hacer con una tecnología de KDE llamada XMLGUI, que hace cosas majas como barras de herramientas móviles.

{{note|En una versión posterior de KDE4, XMLGUI puede ser reemplazada por un nuevo framework llamado liveui. Por ahora, XMLGUI es la única manera correcta de configurar la UI.}}

==XMLGUI==
La función <tt>setupGUI()</tt> de la clase {{class|KXmlGuiWindow}} depende del sistema XMLGUI para construir la GUI, el cual la realiza analizando el archivo de descripción XML de la interfaz.

La regla para establecer el nombre del archivo XML es <tt>appnameui.rc</tt>, donde <tt>appname</tt> es el nombre que estableces en {{class|KAboutData}} (en este caso, ''tutorial 3''). Por lo que en nuestro ejemplo, llamamos al archivo <tt>tutorial3ui.rc</tt>, y está localizado en el directorio del código. Cmake maneja donde será puesto el archivo en última instancia.

==Archivo ''appname''ui.rc==
Como la descripción de la UI está definida en el archivo XML, el layout debe seguir unas reglas estrictas. Este tutorial no profundizará en exceso en este aspecto, pero para mas información puedes echar un vistazo a la [[Development/Architecture/KDE4/XMLGUI_Technology|página de XMLGUI]] (aquí tienes un tutorial antiguo: [http://developer.kde.org/documentation/tutorials/xmlui/preface.html])

===tutorial3ui.rc===
<code xml n>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE kpartgui SYSTEM "kpartgui.dtd">
<gui name="tutorial3" version="1">
<ToolBar name="mainToolBar" >
<text>Main Toolbar</text>
<Action name="limpiar" />
</ToolBar>
<MenuBar>
<Menu name="file" >
<Action name="limpiar" />
</Menu>
</MenuBar>
</gui>
</code>

La etiqueta <tt><Toolbar></tt> permite describir la barra de herramientas, que normalmente es la barra con los iconos de la parte superior de la ventana. Se le da el nombre único de ''mainToolBar'', y usando la etiqueta <tt><text></tt>, es visible a los usuarios con el nombre ''Main Toolbar''. La acción limpiae se añade a la barra de herramientas usando la etiqueta <tt><Action></tt>, el nombre del parámetro en esta etiqueta es la cadena que pasamos a KActionCollection con <tt>addAction()</tt> en <tt>mainwindow.cpp</tt>.

Además de tener la acción en la barra de herramientas, también se puede añadir a la barra de menú. Aquí la acción se ha añadido al menú ''File'' de <tt>MenuBar</tt> de la misma manera que la añadimos a la barra de herramientas.

Cambia el atributo 'version' de la etiqueta <tt><nowiki><gui></nowiki></tt> si cambiaste el archivo .rc desde la última instalación, para forzar una actualización de la cache del sistema.

Algunas notas sobre la interacción entre el código y el archivo .rc: Los menús aparecen automáticamente y deberían tener una etiqueta hija <tt><nowiki><text/></nowiki></tt> a menos que se refieran a los menús estándar. Las acciones deberán crearse manualmente y se insertarán mediante actionCollection() usando el nombre del archivo .rc. Las acciones pueden ocultarse o desactivarse, mientras que los menús no.

==CMake==
Por último, el <tt>tutorial3ui.rc</tt> hay que ubicarlo en algún lugar donde KDE pueda encontrarlo (no lo puedes dejar en el directorio de las fuentes!). '''Esto significa que el proyecto tiene que ser instalado en algún sitio'''.
===CMakeLists.txt===
<code ini n>
project(tutorial3)

find_package(KDE4 REQUIRED)
include_directories(${KDE4_INCLUDES})

set(tutorial3_SRCS
main.cpp
mainwindow.cpp
)

kde4_add_executable(tutorial3 ${tutorial3_SRCS})

target_link_libraries(tutorial3 ${KDE4_KDEUI_LIBS})

install(TARGETS tutorial3 DESTINATION ${BIN_INSTALL_DIR})
install(FILES tutorial3ui.rc
DESTINATION ${DATA_INSTALL_DIR}/tutorial3)
</code>

Este archivo es casi idéntico al del tutorial2, peor con dos lineas extra al final que describen donde se instalará los archivos. En primer lugar, el objetivo <tt>tutorial3</tt> se instala en <tt>BIN_INSTALL_DIR</tt>, entonces el archivo <tt>tutorial3ui.rc</tt> que describe el layout de la interfaz de usuario se instala en el directorio de datos de las aplicaciones.

===Make, instalar y ejecutar===
Si no tienes acceso de escritura a tu directorio de instalación de KDE4, puedes instalarlo en una carpeta de tu directorio personal.

Para decirle a CMake donde instalar el programa, establece la variable <tt>DCMAKE_INSTALL_PREFIX</tt>. Probablemente quieras instalarlo en algún sitio local para testearlo (probablemente sea un poco tonto hacer el esfuerzo de instalar estos tutoriales en el directorio de KDE), por lo que podría ser el siguiente caso:
mkdir build && cd build
cmake .. -DCMAKE_INSTALL_PREFIX=$HOME
make install
$HOME/bin/tutorial3
Creará una estructura de directorios como la de KDE en tu directorio de usuario e instalara el ejecutable en {{path|$HOME/bin/tutorial3}}.

==Avanzando==
Ahora puedes continuar con el [[Development/Tutorials/Saving_and_loading|Tutorial 4 - Guardar y Abrir]].

[[Category:C++]]

File:Introtokdetutorial3 (es).png

2008-09-21T21:27:05Z

Development/Tutorials (es)

2008-09-19T15:34:11Z

Edumardo: translation to spanish

{{Template:I18n/Language Navigation Bar|Development/Tutorials}}
{{warning_(es)| Traducción en curso: solo hasta el punto 4}}
Los tutoriales son la forma más rápida de encontrar lo que KDE puede hacer por usted y como hacerlo. Aquí tienes una lista de los tutoriales disponibles actualmente para KDE4. Material para KDE3 y KDE2 está disponible al final de la página.

== Introducción a la programación en KDE4 ==
Estś interesado en escribir aplicacion en KDE4? Esta serie de tutoriales están dirigidos a personas totalmente novatas en la programación en KDE4.
;[[Development/Tutorials/First program_(es)|Hola Mundo]]
:''Una introducción preliminar a los aspectos básicos de la programación en KDE4.''

;[[Development/Tutorials/Using KXmlGuiWindow_(es)|Crear la ventana principal]]
:''Este tutorial te muestra la magia de la cosa mas importante en una aplicación: la ventana principal''

;[[Development/Tutorials/Using KActions|Usar KActions]]
:''Como añadir acciones a los menús y a las toolbars.''

;[[Development/Tutorials/Saving and loading|Guardar y Abrir]]
:''Introducción a la biblioteca KIO mientras añades soporte para guardar y abrir en tu aplicación.''

;[[Development/Tutorials/KCmdLineArgs|Argumentos en la línea de órdenes]]
:''Añade la capacidad de especificar a nuestro editor que archivo abrir desde la línea de ordenes.''

== Básicos ==
;[[Development/Tutorials/KDE4 Porting Guide|Portar tu aplicación]]
:''Ayuda para portar aplicaciones de Qt3/KDE3 a Qt4/KDE4.''

;[[Development/Tutorials/CMake|Introducción a CMake]]
:''Como usar el sistema de construcción CMake usado por KDE4.''

;[[Development/Tutorials/Common Programming Mistakes|Errores comunes de programación]]
:''Varios errores comunes que se presentan en el desarrollo de aplicaciones Qt y KDE y como evitarlos.''

;[[Development/Tutorials/Using Qt Designer|Usar Qt Designer para diseñar interfaces de usuario]]
:''Como crear archivos UI con el diseñador, y como integrarlos después en un programa KDE.''

;[[Development/Tutorials/Creating Libraries|Crear bibliotecas para compartir código]]
:''Como añadir la biblioteca al "buildsystem" y como preparar el código fuente.''
:''How to add the library to the buildsystem and how to prepare the source code.''

== Comprobación y depurado ==

;[[Development/Tutorials/Debugging|Depurar tu aplicación]]
:''Consejos, herramientas y técnicas para depurar tu aplicación KDE.''

;[[Development/Tutorials/Unittests|Escribir "unittests" para Qt4 y KDE4 con QTestLib]] ([http://developer.kde.org/documentation/tutorials/writingunittests/writingunittests.html enlace original])
:''Tutorial de [mailto:bradh@frogmouth.net Brad Hards] que describe como escribir unittests mediante la framework QTestLib. El tutorial se realiza con un ejemplo, y aun está en desarrollo.''

;[[Development/Tutorials/Code_Checking|Maneras semiautomáticas de detectar errores en el código]]
:''Técnicas que puedes usar para detectar errores en el código KDE.''

== Gestión de los datos de configuración con KConfig ==

;[[Development/Tutorials/KConfig|Introducción a KConfig]]
:''Una sinopsis de las clases de KConfig y como usarlas en el código de tu aplicación.''

;[[Development/Tutorials/Using KConfig XT|Uso de KConfig XT]]
:''Tutorial sobre como usar eficientemente el framework KConfig XT''

;[[Development/Tutorials/Updating KConfig Files|Actualizando archivos con KConfig]]
:''Tutorial sobre como escribir un script de actualización para conservar los cambios de tu archivo de configuración de tu aplicación y sincornizarlo con el archivo de configuración del usuario''

== Services: Applications and Plugins ==
;[[Development/Tutorials/Services/Introduction|Introduction to the Services Framework]]
:''An overview of the services framework in KDE and what it provides the application developer. Covers the system configuration cache (SyCoCa), the source data files and what the indexed information can be used for.''

;[[Development/Tutorials/Services/Traders|Finding Services Using Trader Queries]]
:''How to find services, such as plugins or mimetypes, that are indexed in the SyCoCa using Trader Query Syntax''

;[[Development/Tutorials/Services/Plugins|Creating and Loading Plugins Using KService]]
:''Learn how to define custom plugin types, find installed plugins (including 3rd party plugins) and load them in an easy and portable fashion using KService.''

== Localization ==
See also [[Localization|Localization portal]].

;[[Development/Tutorials/Localization/Unicode|Introduction To Unicode]]
:''An introduction to what Unicode is as well as how to handle Unicode data in KDE applications.''

; [[Development/Tutorials/Localization/i18n|Writing Applications With Localization In Mind]]
:''This tutorial covers what localization is, why it's important and how to ensure your application is ready to be localized. A must read for all application developers.''

; [[Development/Tutorials/Localization/i18n Mistakes|Avoiding Common Localization Pitfalls]]
:''There are several common mistakes that prevent applications from being properly localized. Find out what they are and how to easily avoid them in this tutorial.''

; [[Development/Tutorials/Localization/Building KDE's l10n Module|Building KDE's Localization Module]]
:''Building and installing language support from KDE's localization (l10n) module is a good idea for those working on applications in the main KDE repository. Doing so will allow you to test your application in another language and spot problem areas. Learn how to do just that in this tutorial.''

; [[Development/Tutorials/Localization/i18n Build Systems|Incorporating i18n Into the Build System]]
:''Once your application is ready to be localized, the next step is to ensure that translation files are built automatically and kept up to date. This tutorial covers the necessary CMakeFiles.txt additions as well the process of distributing the resulting message catalogs with your application.''

; [[Development/Tutorials/Localization/i18n Challenges|Common i18n Challenges and Solutions]]
:''This tutorial covers challenges that you may eventually run into such as translating handbooks and other data that exists outside of the source code, merging and handling obsolete .po files, dealing with freezes, coding in languages other than English and creating independent releases of or moving applications between KDE modules.''

; [[Development/Tutorials/Localization/i18n_Semantics|Semantic Markup of Messages]]
:''To ensure consistent presentation and more meaningful representations of messages in applications, semantic markup can be applied to messages marked for translation using the KUIT system. This tutorial describes how this system works.''

; [[Development/Tutorials/Localization/i18n Krazy|Automated i18n Code Checking]]
:''The Krazy code checker scans KDE's code and reports common i18n mistakes.''

== Documentation ==

;[[Development/Tutorials/API_Documentation|API Documentation]]
:''This tutorial explains how to document your APIs properly.''

;[[Development/Tutorials/Man_Pages|Man Pages]]
:''Writing and Generating Reference Manual Pages.''

== Application Automation and Scripting ==

=== D-Bus ===
; [[Development/Tutorials/D-Bus/Introduction|Introduction to D-Bus]]
:''A straight-forward introduction to the core concepts in D-Bus from an application developer's perspective, this tutorial covers what D-Bus is and how it can be used by applications.''
; [[Development/Tutorials/D-Bus/Accessing Interfaces|Accessing D-Bus Interfaces]]
:''A step-by-step guide to calling D-Bus methods and connecting to D-Bus signals using QtDBus.''
; [[Development/Tutorials/D-Bus/Intermediate_D-Bus|Intermediate D-Bus]]
:''Tips to make use of QtDBus when faced with problematic real-world interfaces.''
; [[Development/Tutorials/D-Bus/Creating Interfaces|Creating D-Bus Interfaces]]
:''Learn how to expose functionality in your application by creating and using custom D-Bus interfaces. Covers generating the XML descriptions, instantiating interfaces at run time and setting up the build system with CMake.''
; [[Development/Tutorials/D-Bus/Autostart Services|D-Bus Autostart Services]]
:''Turn your application into a D-Bus autostart service with this tutorial. This D-Bus feature, also known as "D-Bus service activation", will ensure that even when your application isn't running that D-Bus calls made to it will work by relying on the D-Bus daemon itself to start your app if and when needed.''
; [[Development/Tutorials/Porting_to_D-Bus|Porting from DCOP to D-Bus]]
: ''Port your applications from DCOP to D-Bus with this handy guide.''

=== Konqueror ===
; [[Development/Tutorials/Creating Konqueror Service Menus|Creating Konqueror Service Menus]]
:''This tutorial shows you how to create mimetype-specific actions in Konqueror's context menu (aka "servicemenus").''

=== Kross ===
; [[Development/Tutorials/Kross/Introduction|Introduction to Kross]]
:''An introduction to the Kross Scripting Framework.''

; [[Development/Tutorials/Kross/Hello_World|Hello World]]
:''A first application with working kross code.''

; [[Development/Tutorials/Kross/Call_Functions_in_Kross|Calling Functions in Kross]]
:''Simple demonstration of calling scripting functions''

; [[Development/Tutorials/Kross/Connecting_Signals_and_slots_in_Kross|Connecting Signals and Slots in Kross]]
:''Simple demonstration of connecting object signals with script slots''

; [[Development/Tutorials/Kross/Scripts-as-Plugins|Scripts as Plugins with Kross]]
:''This tutorial provides a step-by-step introduction how to integrate scripts as plugins into a KDE application.''

; [[Development/Tutorials/Kross/Scripts-as-KPlugins|Load Kross Scripts as KPlugins]]
:''This tutorial provides a step-by-step introduction how to load scripts as KPlugins.''

; [[Development/Tutorials/Kross/Script-Actions|Placing script actions in your application menus ]]
:''Simple demonstration on how to extend you application menus to execute script files.''

=== KOffice ===
; [[Development/Tutorials/KOffice Overview|KOffice Overview]]
:''This document shows an overview of the different KOffice plugin types and tells you what each of their purpose and strengths are.'' If you are new with KOffice plugins, this is the place to start.

; [[Development/Tutorials/Write a Flake Plugin|Creating KOffice Flake Plugins]]
:''This tutorial shows you how you can build a plugin for KOffice applications to allow you embed content in ODF documents using Flake.''

; [[Development/Tutorials/KWord Scripting|KWord Scripting]]
:''This tutorial shows how to script KWord with Python, Ruby or JavaScript using Kross.''

; [[Development/Tutorials/KSpread Scripting|KSpread Scripting]]
:''This tutorial shows how to script KSpread with Python, Ruby or JavaScript using Kross.''

; [[Development/Tutorials/Krita Scripting|Krita Scripting]]
:''This tutorial shows how to script Krita with Python, Ruby or JavaScript using Kross.''

=== SuperKaramba ===
; [[Development/Tutorials/SuperKaramba|SuperKaramba Tutorial]]
:''This tutorial provides an overview of SuperKaramba, theme files and scripting with Python, Ruby and JavaScript.''

== Plugins and KParts ==

; [[Development/Tutorials/Writing kontact plugins|Writing kontact plugins]]:''Kontact plugins are KParts. This tutorial describes how you can write one.''

; [[Development/Tutorials/Using KParts|Using KParts]]:''Learn how to load a KPart into an application window.''

== Search and Metadata ==

=== Strigi ===

; [[Development/Tutorials/Writing file analyzers|Writing file analyzers]]
:''File analyzers extract data from files to display in the file dialogs and file managers. The data gathered this way is also used to search for files. KDE4 allows the use of multiple analyzers per file type. This tutorial describes how you can write new analyzers.''

=== [http://nepomuk.kde.org Nepomuk] ===

; [[Development/Tutorials/Metadata/Nepomuk/Quickstart|Nepomuk Quickstart]]
:''How to use Nepomuk resources in a quick and painless way without much fuss.''

; [[Development/Tutorials/Metadata/Nepomuk/RDFIntroduction|RDF and Ontologies in Nepomuk]]
:''An introduction to RDF and the usage of ontologies in Nepomuk.''

; [[Development/Tutorials/Metadata/Nepomuk/Resources|Handling Resources with Nepomuk]]
:''Nepomuk is the KDE library which provides easy access to metadata in the Nepomuk system. Learn how to make your application create and read metadata using the Nepomuk system.''

; [[Development/Tutorials/Metadata/Nepomuk/ResourceGenerator|Using the Nepomuk Resource Generator]]
:''Nepomuk includes a resource generator which creates convenience classes for handling metadata.''

; [[Development/Tutorials/Metadata/Nepomuk/NepomukServer|The Nepomuk Server]]
:''The Nepomuk Server hosts the main Nepomuk data repository and can be accessed directly via a Soprano API.''

; [[Development/Tutorials/Metadata/Nepomuk/NepomukServices|Nepomuk Services]]
:''The Nepomuk Server manages a set of Nepomuk services.''

; [[Development/Tutorials/Metadata/Nepomuk/AdvancedQueries|Advanced Queries]]
:''The real power of Nepomuk can only be exposed when performing fancy queries on the data repository. This tutorial provides an introduction to semantic and full text queries in Nepomuk.''

== Hardware Awareness (Solid) ==

;[[Development/Tutorials/Solid_Tutorials|Introduction to Solid]]
:''An introduction to using the Solid hardware discovery and interaction system in KDE applications.''

;[[Development/Tutorials/Solid_Network_Tutorial|Accessing Network Information]]
:''How to use the Solid system to get information about the network''

== Multimedia (Phonon) ==

;[[Development/Tutorials/Phonon/Introduction|Phonon]]
:''How to start with the multimedia API''

:''How to compile and use Phonon and its GStreamer backend on Linux using Qt 4.3.x''
::''This article gives you a quick brief of how you can use checkout, compile Phonon and its GStreamer backend on GNU/Linux with just Qt 4.3.x. Towards the end, the article also describes how a developer can make use of Phonon to create simple audio and video players. You can read the article [http://www.vcreatelogic.com/oss/docs/CompilingPhononOnLinux.pdf here]. You can download the editable OpenDocumentText file from [http://www.prashanthudupa.com/phonon/CompilingPhononOnLinux.odt here].''

== Plasma ==

;[[Development/Tutorials/Plasma/GettingStarted|Getting Started With Plasmoids]]
:''Creating your first Plasma widget, or Plasmoid, in C++ with an SVG background, an icon and some text''

;[[Development/Tutorials/Plasma/DataEngines|Writing A DataEngine]]
:''DataEngines provide a [http://api.kde.org/4.0-api/kdebase-apidocs/workspace/libs/plasma/html/classPlasma_1_1DataEngine.html standardized interface] to various data sources for visualizations to use. Learn what a DataEngine is and how to write one of your own.''

;[[Development/Tutorials/Plasma/UsingDataEngines|Using DataEngines in Plasmoids]]
:''With a DataEngine, it is possible to retrieve data for display in a simple and standard way. This tutorial covers the topic of how to use DataEngines for this purpose in Plasmoids.''

;[[Development/Tutorials/Plasma/AbstractRunner|Creating Runners]]
:''Runners are plugins that provide action-based search functionality in the Plasma workspace "run command" dialog. These plugins can be used by any application that links again libplasma.''

;[[Development/Tutorials/Plasma/Theme|Creating a Plasma Theme]]
:''Guide to creating your first Plasma theme.''

;[[Development/Tutorials/Plasma/UsingExtenders|Using Extenders]]
:''This guide shows you how to create a simple applet (a stripped down kuiserver applet) that uses extenders.''

== Communication (Decibel) ==

;[[Development/Tutorials/Decibel/GettingStarted|Getting started with Decibel]]
:''This tutorial describes how to set up Decibel.''

;[[Development/Tutorials/Decibel/Handling_TextChannels|Handling TextChannels]]
:''This tutorial introduces the basics of handling incoming TextChannels by guiding you through building a simple text chat application.''

== Personal Information Management (Akonadi) ==

;[[Development/Tutorials/Akonadi/Resources|Developing Akonadi Resources]]
:''Akonadi Resources are agent programs which transport PIM data between Akonadi and a backend (files, servers, etc)''

== Kate / Kwrite ==

;[[Development/Tutorials/Kate/KTextEditor Plugins|Getting started with KTextEditor plugins]]
:''Creating your first KTextEditor plugin''

;[[Development/Tutorials/Kate/KTextEditor_Plugins_Advanced|Developing a plugin with configuration dialog]]
:''Adding a configuration dialog to the Time & Date example''

;[[Development/Tutorials/Kate/KTextEditor_Example|A small Editor]]
:''Create a small application using KTextEditor''

==Printing==

;[[Development/Tutorials/Printing Hello World|Hello World]]
:''Introduction to the KDE printing system''

;[[Development/Tutorials/Printing Print Dialog|Print Dialog]]
:''Using the KDE print dialog''

== Get Hot New Stuff ==
; [[Development/Tutorials/K_Hot_New_Stuff2|New introduction to KGet Hot New Stuff2]]
:''A short tutorial about how to use KHotNewStuff2 in your application.''

* old links for KNS1 content:
; [[Development/Tutorials/Introduction to Get Hot New Stuff|Introduction to Get Hot New Stuff]]
:''An introduction to the developer-friendly network update system that allows KDE applications to fetch new application data at runtime in a user friendly manner.''

;[[Development/Tutorials/KNewStuffSecure|KNewStuff Secure]] ([http://developer.kde.org/documentation/tutorials/knewstuffsecure/index.html Original Link])
:''Tutorial showing how to share resources in a secured way (KDE 3.4 and later).'' By András Mantia <amantia@kde.org>.

== Goya ==
; [[Development/Tutorials/Introduction to Goya usage|Introduction to Goya usage]]
:''An introduction for the Goya subsystem usage, which allows you to easily add widgets to your itemviews and connect their signals to your code, as they were real widgets.''

; [[Development/Tutorials/Introduction to Goya usage 2|Introduction to Goya usage (part 2)]]
:''The second part of the tutorial, with a slightly more complex example than the first part.''

== Rapid Application Development ==

=== Python ===

;[[Development/Tutorials/Python introduction to signals and slots|101 Introduction to signals and slots]]
:''A simple introduction to Qt's signal and slot architecture.''

=== Ruby ===

;[http://developer.kde.org/language-bindings/ruby/kde3tutorial/index.html KDE Ruby Korundum tutorial]
:''A ruby version of Antonio Larrosa Jiménez's KDE tutorial by Richard Dale. See the [http://developer.kde.org/language-bindings/ruby/index.html Ruby Developers Corner] for Qt tutorials and other info.''

;[[Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby Tutorial]]
:''Trolltech's fabulous introductory tutorial to Qt, translated to Ruby.''

;[[Development/Tutorials/Plasma/RubyApplet|Creating a Plasma Widget in Ruby]]
:''Tutorial that shows how to create your first Plasma Applet using the Ruby language.''

=== Shell ===

;[[Development/Tutorials/Shell_Scripting_with_KDE_Dialogs|Shell Scripting with KDE dialogs]] ([http://developer.kde.org/documentation/tutorials/kdialog/t1.html Original Link])
:''Tutorial by [mailto:bradh@frogmouth.net Brad Hards] that describes how to use KDE dialogs in shell scripts with kdialog. It is presented as an example based tutorial.''

== Graphics Programming ==

;[[Development/Tutorials/Graphics/Performance|QPainter Perfomance]]
:''Hints on avoiding common mistakes leading to poor performance when using QPainter''

== Using the KDE Games Libraries ==
;[[Development/Tutorials/Games/KStandardGameAction| KStandardGameAction]]
:''Using libkdegames to make your game fit the kdegames standard''
;[[Development/Tutorials/Games/Highscores| Highscores]]
:''Implementing a simple highscore table into your game''
;[[Development/Tutorials/Games/Theme Selector| Theme Selector]]
:''Using the libkdegames theme selection dialog''
;[[Development/Tutorials/Games/Palapeli Patterns| Palapeli Patterns]]
:''Creating a pattern for Palapeli''

== Other tutorials ==

=== 2D Plotting (KPlotWidget) ===
;[[Development/Tutorials/KPlotWidget|Using the KDE data-plotting widget]]
:''This tutorial introduces KPlotWidget, which is used for 2-D data plotting. It includes information on simple usage of the widget (including adding and modifying data sets, and customizing the plot axes and labels), and advanced customization (including extending the widget through sub-classing).''

=== Spelling and Grammar Checking (Sonnet) ===
;[[Development/Tutorials/Sonnet/SonnetTutorial|Adding spell-checking or grammar-checking to KDE applications]]
:''This tutorial introduces Sonnet and how one may use it to add language correction to your KDE application. Sonnet's auxiliary features shall be described in a separate tutorial.''

=== Pixmap cache (KPixmapCache) ===
;[[Development/Tutorials/KPixmapCache|Using the KDE pixmap cache]]
:''This tutorial shows how to use KPixmapCache to cache e.g. pixmaps generated from SVGs or some data.''

=== Using MarbleWidget (Marble) ===
;[[Development/Tutorials/MarbleWidget|Using MarbleWidget]]
:''This short tutorial describes how to use the MarbleWidget in your project''

=== Using local SCM for KDE development ===
;[[Development/Tutorials/Git|Using Git to develop for KDE]]
:''This tutorial shows how to use Git to develop for KDE''

== KDE2 and KDE3 Materials ==

;[[Development/Tutorials/KDE3|KDE3 Tutorials]]
:''These tutorials cover topics related to KDE3.''

;[[Development/Tutorials/KDE2|KDE2 Tutorials]]
:''These tutorials cover topics related to KDE2.''

[[Category:KDE4]]

Development/Tutorials/Using KXmlGuiWindow (es)

2008-09-19T15:20:28Z

Edumardo: translation to spanish

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Using_KXmlGuiWindow}}
{{TutorialBrowser_(es)|

series=Tutorial para principiantes|

name=Como usar usar KXmlGuiWindow|

pre=[[Development/Tutorials/First_program_(es)|Tutorial 1 - Hola Mundo]]|

next=[[Development/Tutorials/Using_KActions|Tutorial 3 - KActions y XMLGUI]]|

reading={{class|KXmlGuiWindow}}
}}

==Resumen==
Este tutorial continua el camino iniciado por el tutorial [[Development/Tutorials/First_program_(es)|Hola Mundo]], haciendo una introducción a la clase {{class|KXmlGuiWindow}}.

En el tutorial anterior, el programa mostró una "caja de diálogo" (dialog box), ahora vamos a añadir mas funcionalidad al programa.

[[image:introtokdetutorial2.png|frame|center]]

==KXmlGuiWindow==

La clase {{class|KXmlGuiWindow}} proporciona una vista de la venta principal con una barra de menú, una barra de herramientas, una barra de estado y un área principial en el centro del widget. La mayoria de las aplicaciones de KDE derivarán de esta clase, que proporciona una manera facil de definir el layout del menú y la barra de herramientas mediante archivos XML (esta tecnología se llama XMLGUI). Si bien no usaremos XMLGUI en ''este'' tutorial, lo haremos en el siguiente.

Con el fin de tener un KXmlGuiWindow que pueda usarse, debemos heredar de él. Por lo que creamos dos archivos, <tt>mainwindow.cpp</tt> y <tt>mainwindow.h</tt> que contendrán nuestro código.

===mainwindow.h===
<code cppqt n>
#ifndef MAINWINDOW_H
#define MAINWINDOW_H

#include <KXmlGuiWindow>
#include <KTextEdit>

class MainWindow : public KXmlGuiWindow
{
public:
MainWindow(QWidget *parent=0);

private:
KTextEdit* textArea;
};

#endif
</code>
En primer lugar, en la línea 7, hacemos que MainWindow herede de KXmlGuiWindow con <tt>class MainWindow : public KXmlGuiWindow</tt>.

Luego declaramos el constructor con <tt>MainWindow(QWidget *parent=0);</tt>.

Y por último declaramos un puntero al objeto que compondrá la mayor parte de nuestro programa: <tt>textArea</tt>. {{class|KTextEdit}} es un editor genérico de texto enriquecido con algunas sutilezas de KDE, como ocultación automática del cursor.

===mainwindow.cpp===
<code cppqt n>
#include "mainwindow.h"

MainWindow::MainWindow(QWidget *parent) : KXmlGuiWindow(parent)
{
textArea = new KTextEdit();
setCentralWidget(textArea);
setupGUI();
}
</code>
Lo primero que tenemos que hacer es incluir el archivo de cabecera que contiene la declaración de la clase (en la línea 1).

En la línea 5, inicializamos nuestro editor de texto con un objeto. En la línea 6 usamos la función setCentralWidget() de KXmlGuiWindow para decirle a KXmlGuiWindow que debe aparecer en la sección central de la ventana.

Por último, KXmlGuiWindow::setupGUI()
is called which does a lot of behind-the-scenes stuff and creates the default menu bars (Settings, Help).

==Actualizando main.cpp==
Con el fin de ejecutar esta ventana, necesitamos añadir unas pocas lineas a main.cpp:
===main.cpp===
<code cppqt n>
#include <KApplication>
#include <KAboutData>
#include <KCmdLineArgs>

#include "mainwindow.h"

int main (int argc, char *argv[])
{
KAboutData aboutData( "tutorial2", 0,
ki18n("Tutorial 2"), "1.0",
ki18n("A simple text area"),
KAboutData::License_GPL,
ki18n("Copyright (c) 2007 Developer") );
KCmdLineArgs::init( argc, argv, &aboutData );

KApplication app;

MainWindow* window = new MainWindow();
window->show();

return app.exec();
}
</code>
The only new lines here (compared to Tutorial 1) are 5, 18 and 19. On line 18, we create our MainWindow object and then on line 19, we display it.

==CMake==
La mejor manera de compilar el programa es usar CMake. Lo único que ha cambiado desde el tutorial 1 es que hemos añadido <tt>mainwindow.cpp</tt> a la lista de fuentes y hemos cambiado <tt>tutorial1</tt> por <tt>tutorial2</tt>.

===CMakeLists.txt===
<code ini n>
project (tutorial2)

find_package(KDE4 REQUIRED)
include_directories(${KDE4_INCLUDES})

set(tutorial2_SRCS
main.cpp
mainwindow.cpp
)

kde4_add_executable(tutorial2 ${tutorial2_SRCS})
target_link_libraries(tutorial2 ${KDE4_KDEUI_LIBS})
</code>

===Compilando===
Para compilarlo, enlazarlo y ejecutarlo, usa:
mkdir build && cd build
cmake ..
make
./tutorial2

==Avanzando==
Ahora puedes continuar con el [[Development/Tutorials/Using_KActions|Tutorial 3 - Usar KActions]].

[[Category:C++]]

Development/Tutorials/Using KXmlGuiWindow (es)

2008-09-19T14:45:45Z

Edumardo: translation to spanish

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Using_KXmlGuiWindow}}
{{TutorialBrowser_(es)|

series=Tutorial para principiantes|

name=Como usar usar KXmlGuiWindow|

pre=[[Development/Tutorials/First_program_(es)|Tutorial 1 - Hola Mundo]]|

next=[[Development/Tutorials/Using_KActions|Tutorial 3 - KActions y XMLGUI]]|

reading={{class|KXmlGuiWindow}}
}}

==Resumen==
Este tutorial continua el camino iniciado por el tutorial [[Development/Tutorials/First_program_(es)|Hola Mundo]], haciendo una introducción a la clase {{class|KXmlGuiWindow}}.

En el tutorial anterior, el programa mostró una "caja de diálogo" (dialog box), ahora vamos a añadir mas funcionalidad al programa.

[[image:introtokdetutorial2.png|frame|center]]

==KXmlGuiWindow==

La clase {{class|KXmlGuiWindow}} proporciona una vista de la venta principal con una barra de menú, una barra de herramientas, una barra de estado y un área principial en el centro del widget. La mayoria de las aplicaciones de KDE derivarán de esta clase, que proporciona una manera facil de definir el layout del menú y la barra de herramientas mediante archivos XML (esta tecnología se llama XMLGUI). Si bien no usaremos XMLGUI en ''este'' tutorial, lo haremos en el siguiente.

Con el fin de tener un KXmlGuiWindow que pueda usarse, debemos heredar de él. Por lo que creamos dos archivos, <tt>mainwindow.cpp</tt> y <tt>mainwindow.h</tt> que contendrán nuestro código.

===mainwindow.h===
<code cppqt n>
#ifndef MAINWINDOW_H
#define MAINWINDOW_H

#include <KXmlGuiWindow>
#include <KTextEdit>

class MainWindow : public KXmlGuiWindow
{
public:
MainWindow(QWidget *parent=0);

private:
KTextEdit* textArea;
};

#endif
</code>
First we Subclass KXmlGuiWindow on line 7 with <tt>class MainWindow : public KXmlGuiWindow</tt>.

Then we declare the constructor with <tt>MainWindow(QWidget *parent=0);</tt>.

And finally we declare a pointer to the object that will make up the bulk of our program. {{class|KTextEdit}} is a generic richtext editor with some KDE niceties like cursor auto-hiding.

===mainwindow.cpp===
<code cppqt n>
#include "mainwindow.h"

MainWindow::MainWindow(QWidget *parent) : KXmlGuiWindow(parent)
{
textArea = new KTextEdit();
setCentralWidget(textArea);
setupGUI();
}
</code>
First, of course, on line 1 we have to include the header file containing the class declaration.

On line 5, we initialise our text editor with an object. Then on line 6 we use KXmlGuiWindow's built-in setCentralWidget() function which tells the KXmlGuiWindow what should appear in the central section of the window.

Finally, KXmlGuiWindow::setupGUI() is called which does a lot of behind-the-scenes stuff and creates the default menu bars (Settings, Help).

==Actualizando main.cpp==
Con el fin de ejecutar esta ventana, necesitamos añadir unas pocas lineas a main.cpp:
===main.cpp===
<code cppqt n>
#include <KApplication>
#include <KAboutData>
#include <KCmdLineArgs>

#include "mainwindow.h"

int main (int argc, char *argv[])
{
KAboutData aboutData( "tutorial2", 0,
ki18n("Tutorial 2"), "1.0",
ki18n("A simple text area"),
KAboutData::License_GPL,
ki18n("Copyright (c) 2007 Developer") );
KCmdLineArgs::init( argc, argv, &aboutData );

KApplication app;

MainWindow* window = new MainWindow();
window->show();

return app.exec();
}
</code>
The only new lines here (compared to Tutorial 1) are 5, 18 and 19. On line 18, we create our MainWindow object and then on line 19, we display it.

==CMake==
La mejor manera de compilar el programa es usar CMake. Lo único que ha cambiado desde el tutorial 1 es que hemos añadido <tt>mainwindow.cpp</tt> a la lista de fuentes y hemos cambiado <tt>tutorial1</tt> por <tt>tutorial2</tt>.

===CMakeLists.txt===
<code ini n>
project (tutorial2)

find_package(KDE4 REQUIRED)
include_directories(${KDE4_INCLUDES})

set(tutorial2_SRCS
main.cpp
mainwindow.cpp
)

kde4_add_executable(tutorial2 ${tutorial2_SRCS})
target_link_libraries(tutorial2 ${KDE4_KDEUI_LIBS})
</code>

===Compilando===
Para compilarlo, enlazarlo y ejecutarlo, usa:
mkdir build && cd build
cmake ..
make
./tutorial2

==Avanzando==
Ahora puedes continuar con el [[Development/Tutorials/Using_KActions|Tutorial 3 - Usar KActions]].

[[Category:C++]]