Contribute/es - Revision history

FuzzyBot: Updating to match new version of source page

2012-12-20T18:56:50Z

Updating to match new version of source page

FuzzyBot: Updating to match new version of source page

2012-12-08T16:54:51Z

Updating to match new version of source page

FuzzyBot: Updating to match new version of source page

2012-11-04T10:00:05Z

Updating to match new version of source page

AnneW at 18:07, 19 July 2012

2012-07-19T18:07:03Z

AnneW: Created page with "==Cómo obtener respuestas a sus preguntas=="

2012-07-19T18:05:25Z

Created page with "==Cómo obtener respuestas a sus preguntas=="

FuzzyBot: Updating to match new version of source page

2012-05-31T19:51:43Z

Updating to match new version of source page

Alejandronova: Created page with "La gran mayoría de KDE está escrita en C++. Si usted no está familiarizado con C++, es necesario que aprenda, a lo menos, sus fundamentos. Hay una serie de buenos libros acerc..."

2011-11-30T18:38:13Z

Created page with "La gran mayoría de KDE está escrita en C++. Si usted no está familiarizado con C++, es necesario que aprenda, a lo menos, sus fundamentos. Hay una serie de buenos libros acerc..."

Alejandronova: Created page with "Empezar a programar en KDE es un asunto de encontrar algo para arreglar, y arreglarlo. Puede ser que quiera consultar la vista de módulos para que le ayude a encontrar lo que es..."

2011-11-30T18:35:49Z

Created page with "Empezar a programar en KDE es un asunto de encontrar algo para arreglar, y arreglarlo. Puede ser que quiera consultar la vista de módulos para que le ayude a encontrar lo que es..."

Alejandronova: Created page with "== Empezando a programar =="

2011-11-30T18:10:54Z

Created page with "== Empezando a programar =="

Alejandronova: Created page with "Si sus programas se caen, no olvide enviar informes utilizando las herramientas automatizadas de reporte. Si sabe inglés, no olvide leer los consejos sobre [[Development/Tutoria..."

2011-11-30T18:10:41Z

Created page with "Si sus programas se caen, no olvide enviar informes utilizando las herramientas automatizadas de reporte. Si sabe inglés, no olvide leer los consejos sobre [[Development/Tutoria..."

@@ Line 39: / Line 39: @@
 === Qt ===
-To become proficient with KDE coding, you should understand the Qt toolkit. If you are not familiar with Qt, you should work through the tutorials included with [http://doc.qt.nokia.com/latest Qt Reference Documentation].
+To become proficient with KDE coding, you should understand the Qt toolkit. If you are not familiar with Qt, you should work through the tutorials included with [http://qt-project.org/doc/latest Qt Reference Documentation].
 If you need a gentler introduction to Qt, or would just like an alternative view, then you may wish to look at the [http://www.apress.com/9781590598313 Foundations of Qt Development].
-If you prefer to learn Qt by reading a traditional book, take a look at the  [http://qt.nokia.com/developer/books/ Books about Qt page]. More suggestions on becoming familiar with Qt4 are available [http://doc.qt.nokia.com/latest/how-to-learn-qt.html How to Learn Qt page].
+If you prefer to learn Qt by reading a traditional book, take a look at the  [http://qt-project.org/books Books about Qt page]. More suggestions on becoming familiar with Qt4 are available [http://qt-project.org/doc/qt-4.8/how-to-learn-qt.html How to Learn Qt page].
 === KDE ===

@@ Line 94: / Line 94: @@
 :* '''Read the Developer FAQ'''. Many common developer questions have been answered in the [[Development/FAQs|KDE Developer FAQ]]
 :* '''Search/browse KDE websites'''. A lot of questions can also be answered from the KDE websites, and the documentation included on it. You can search all the KDE websites on the homepage. In addition, you can browse the [http://techbase.kde.org KDE TechBase website]. And if possible, help edit it for clarity, and use the talk page if something is unclear.
-:* '''Search mailing lists'''. A lot of questions have already been answered on the KDE mailing lists, particular the lists kde-devel, kde2-porting, kde-core-devel, kde-games-devel, kfm-devel and koffice-devel. You can search these lists either at [http://lists.kde.org/ lists.kde.org]. You should always search for your answer before asking questions on the mailing lists. When you ask a question on a mailing list you are emailing thousands of people -- please do this only if the answer is not available through a simple search.
+:* '''Search mailing lists'''. A lot of questions have already been answered on the KDE mailing lists, particular the lists kde-devel, kde2-porting, kde-core-devel, kde-games-devel, kfm-devel and koffice-devel. You can search these lists at [http://lists.kde.org/ lists.kde.org]. You should always search for your answer before asking questions on the mailing lists. When you ask a question on a mailing list you are emailing thousands of people -- please do this only if the answer is not available through a simple search.
 :* '''Search engines'''. Do not forget about your favorite search engine. One of the best search engines is Google. With Google you can also [http://groups.google.com/ search] the great bulk of Usenet news sites, which is also particularly helpful, especially for general programming and gcc-related questions.

@@ Line 41: / Line 41: @@
 To become proficient with KDE coding, you should understand the Qt toolkit. If you are not familiar with Qt, you should work through the tutorials included with [http://doc.qt.nokia.com/latest Qt Reference Documentation].
-If you need a gentler introduction to Qt, or would just like an alternative view, then you may wish to look at the [http://qt4.digitalfanatics.org/tiqt/ The Independent Qt Tutorial] (Currently offline due to book contract).
+If you need a gentler introduction to Qt, or would just like an alternative view, then you may wish to look at the [http://www.apress.com/9781590598313 Foundations of Qt Development].
 If you prefer to learn Qt by reading a traditional book, take a look at the  [http://qt.nokia.com/developer/books/ Books about Qt page]. More suggestions on becoming familiar with Qt4 are available [http://doc.qt.nokia.com/latest/how-to-learn-qt.html How to Learn Qt page].
 === KDE ===

@@ Line 1: / Line 1: @@
 <languages />
-<span class="mw-translate-fuzzy">
+Esta página pretende dar un resumen de los diferentes aspectos del desarrollo de KDE, enfocándose en particular a asuntos relacionados con programación. ''El proyecto KDE da la bienvenida a todos quienes deseen ayudar''.
-{{Template:I18n/Language Navigation Bar|Contribuir}}Esta página pretende dar un resumen de los diferentes aspectos del desarrollo de KDE, enfocándose en particular a asuntos relacionados con programación. ''El proyecto KDE da la bienvenida a todos quienes deseen ayudar''.
-</span>
 {{Note|Hay varias formas de involucrarse en el desarrollo de KDE, las que pueden clasificarse de la siguiente forma: ''Documentación, Traducción, Desarrollo, Ergonomía, Accesibilidad, Arte, Promoción'' ¿No es usted un programador? Vea las páginas de KDE acerca de [http://kde.org/community/getinvolved/ cómo nos puede ayudar] para otras formas en las que puede colaborar. También vea: [[Contribute/Bugsquad|Escuadrón de errores]]!''}}

@@ Line 1: / Line 1: @@
 <languages />
 {{Template:I18n/Language Navigation Bar|Contribuir}}Esta página pretende dar un resumen de los diferentes aspectos del desarrollo de KDE, enfocándose en particular a asuntos relacionados con programación. ''El proyecto KDE da la bienvenida a todos quienes deseen ayudar''.
 {{Note|Hay varias formas de involucrarse en el desarrollo de KDE, las que pueden clasificarse de la siguiente forma: ''Documentación, Traducción, Desarrollo, Ergonomía, Accesibilidad, Arte, Promoción'' ¿No es usted un programador? Vea las páginas de KDE acerca de [http://kde.org/community/getinvolved/ cómo nos puede ayudar] para otras formas en las que puede colaborar. También vea: [[Contribute/Bugsquad|Escuadrón de errores]]!''}}
@@ Line 88: / Line 90: @@
 Some projects for analysis of user interfaces may include: checking that shortcut keys are coherent across KDE applications, making sure that dialogs are directly relevant to the interaction that the user would expect, and finding users of KDE software to see how they perform common workflows.
-==Getting Answers to Your Questions==
+==Cómo obtener respuestas a sus preguntas==
 If your question concerns KDE development, your options are pretty much the same general user ones, with some modifications:

@@ Line 57: / Line 57: @@
 A more detailed description of the steps above is available in our [http://quality.kde.org/develop/howto/howtohack.php Programming Guide].
 == Getting Involved in Bug Hunting and Application Quality ==
@@ Line 62: / Line 70: @@
 There is a large number of applications within KDE, and not all of them have a maintainer dedicated to managing bugs and generally helping out with all the issues associated with turning some working code into a polished application.
-If you are interested in helping out with KDE, but don't know where to start, becoming a member of the KDE Quality Team might appeal to you - see the [http://quality.kde.org Quality Team website] for more information. Note that you do not need any programming skills to become involved. In particular developers regularly publish so-called [http://community.kde.org/KDE/Junior_Jobs Junior Jobs] to encourage new contributions.
+If you are interested in helping out with KDE, but don't know where to start, becoming a member of the KDE Quality Team might appeal to you - see the [http://techbase.kde.org/Contribute/Quality_Team Quality Team website] for more information. Note that you do not need any programming skills to become involved. In particular developers regularly publish so-called [http://community.kde.org/KDE/Junior_Jobs Junior Jobs] to encourage new contributions.
 Of course, you can become involved in bug hunting without being part of the KDE Quality Team - just create yourself an account on the KDE [http://bugs.kde.org bug tracking system], and start searching / sorting through the bugs. Again, you don't have to have programming skills - it helps the programmers enormously just to have a procedure that allows a bug to be consistently reproduced.
 The [[Contribute/Bugsquad|Bugsquad]] tries to keep track of bugs in KDE software and make sure that valid bugs are noticed by developers. You do not need any programming knowledge to be in the Bugsquad; in fact it is a great way to return something to the KDE community if you cannot program.
 ==Getting Answers to Your Questions==

@@ Line 35: / Line 35: @@
 === C++ ===
-KDE is mostly written in C++. If you are not familiar with C++, you should do at least some work on it. There are a number of good books on C++ - an excellent source is [http://mindview.net/Books/TICPP/ThinkingInCPP2e.html Bruce Eckel's "Thinking in C++"], which is available both as a free download and as a printed document. It isn't essential to understand everything before you start in KDE, but you do need to understand basic syntax and operations.
+La gran mayoría de KDE está escrita en C++. Si usted no está familiarizado con C++, es necesario que aprenda, a lo menos, sus fundamentos. Hay una serie de buenos libros acerca de C++ ─una buena fuente es [http://mindview.net/Books/TICPP/ThinkingInCPP2e.html "Thinking in C++" de Bruce Eckel] (en inglés), que está disponible tanto en un archivo electrónico gratuito, como en un libro impreso. No es necesario que usted entienda todo antes de que se inicie en KDE, pero es necesario que entienda, al menos, la sintaxis básica y las operaciones.
 === Qt ===

@@ Line 26: / Line 26: @@
 == Empezando a programar ==
-Getting started at coding for KDE is a matter of finding something to fix, and fixing it. You may want to consult the module overview to help find what you are looking for; once you have fixed something, you will want to send in a patch. If you do that a few times, you may want to apply for a KDE Contributor account so you can improve things directly.
+Empezar a programar en KDE es un asunto de encontrar algo para arreglar, y arreglarlo. Puede ser que quiera consultar la vista de módulos para que le ayude a encontrar lo que está buscando; una vez haya arreglado algo, querrá mandar un parche. Si hace eso unas cuantas veces, puede postular a una cuenta de Asistente KDE, para tener acceso directo al código.
 * [[Contribute/List of KDE Modules|Module overview]]

@@ Line 24: / Line 24: @@
 Si sus programas se caen, no olvide enviar informes utilizando las herramientas automatizadas de reporte. Si sabe inglés, no olvide leer los consejos sobre [[Development/Tutorials/Debugging/How_to_create_useful_crash_reports|cómo crear reportes útiles de caída]].
-== Getting Started with Coding ==
+== Empezando a programar ==
 Getting started at coding for KDE is a matter of finding something to fix, and fixing it. You may want to consult the module overview to help find what you are looking for; once you have fixed something, you will want to send in a patch. If you do that a few times, you may want to apply for a KDE Contributor account so you can improve things directly.

@@ Line 22: / Line 22: @@
 Si usted sabe inglés, la forma más rápida de contribuir a KDE es [http://userbase.kde.org/Asking_Questions#Reporting_KDE_Bugs reportar los errores] que encuentre en KDE, usando el [https://bugs.kde.org/ Sistema de Procesamiento de Errores de KDE]. Recuerde hacer esto en inglés.
-If the application you are using crashes then the '''Dr Konqi''' utility will appear and guide you through the process of reporting the crash.  Learn more by reading  [[Development/Tutorials/Debugging/How_to_create_useful_crash_reports|how to create useful crash reports]].
+Si sus programas se caen, no olvide enviar informes utilizando las herramientas automatizadas de reporte. Si sabe inglés, no olvide leer los consejos sobre [[Development/Tutorials/Debugging/How_to_create_useful_crash_reports|cómo crear reportes útiles de caída]].
 == Getting Started with Coding ==