Difference between revisions of "Contribute/es"

Jump to: navigation, search
(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...")
(Updating to match new version of source page)
(4 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
<languages />
 
<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''.
+
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]]!''}}
 
{{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 35: Line 35:
 
=== C++ ===
 
=== 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 ===
 
=== Qt ===
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].
 
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].  
+
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 ===
 
=== KDE ===
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].
 
A more detailed description of the steps above is available in our [http://quality.kde.org/develop/howto/howtohack.php Programming Guide].
 +
 +
==== Context Help: Whatsthis ====
 +
 +
Context help is inseparable from the dialogs and widgets, as they are the target of the context help. In fact, in order to write context help, you have to touch programming or programming tools. Indeed, the context help is a property of widgets. In object oriented programming, a property can have different values, and behave differently depending on the value. In Qt/KDE programming, the name of the property is "whatsthis", and its value is the text the context help is going to display.
 +
 +
Fortunately, this task is usually not very difficult, as there are good tools to deal with user interface design, and better, you will use the knowledge acquired here later when dealing with user interface in general. Using the Qt framework (Qt is the base of KDE technology), it is possible to separate code and user interface. You have two basic cases here: the user interface is written with the general code of application (usually .cpp files) or in Qt Designer files (.ui files: it is a XML document). The second case is the best to start with, as it is simpler to work with. If you don't have Qt Designer installed, you can do so by installing the devel package of Qt from your distribution or the Qt Designer package (if your distribution has more fine grained packages).
 +
 +
Here you can find a detailed guide for writing whatsthis using Qt Designer and working directly with the source code: [http://bddf.ca/~aseigo/whatsthis_tutorial/ WhatsThis Tutorial], by Aaron J. Seigo.
  
 
== Getting Involved in Bug Hunting and Application Quality ==
 
== 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.
 
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.
 
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.
Line 68: Line 76:
 
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.
 
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==
+
== User Interface ==
 +
 
 +
User interface is a very wide subject, and very subjective too, as something obvious to someone is absurd to others and vice versa. Therefore, don't assume, argue clearly, stating your logical steps. Your main tool discussing it are objective reasoning and good sense.
 +
 
 +
It is easy to perform a quick user interface analysis, but it is hard to convince people to change the interface. A good, convincing analysis can gain much if it incorporates information from the KDE guidelines, competing program and operational system analysis, general design principles found in many books, user testing or individual (anecdotal) feedback. It is a volunteer project, and even if everybody agree with you, someone has to implement it.
 +
 
 +
The [http://mail.kde.org/mailman/listinfo/kde-usability KDE Usability Mailing List] is very active and a good place for discussing your ideas, and their homepage is at http://techbase.kde.org/Projects/Usability. If you are already an usability expert, please check [http://www.openusability.org/ OpenUsability.org], a project that brings open source developers and usability experts together, and is collaborating closely with KDE.
 +
 
 +
Some documents guiding documents include the [http://developer.kde.org/documentation/standards/kde/style/basics/index.html  KDE User Interface Guidelines (design standards)] and [http://developer.kde.org/documentation/design/ui/index.html KDE User Interface Guidelines (design principles)].
 +
 
 +
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.
 +
 
 +
==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:
 
If your question concerns KDE development, your options are pretty much the same general user ones, with some modifications:

Revision as of 11:00, 4 November 2012

Other languages:Greek 34% • ‎English 100% • ‎Spanish 40% • ‎Finnish 72% • ‎French 79% • ‎Galician 100% • ‎Japanese 56% • ‎Korean 51% • ‎Dutch 98% • ‎Polish 95% • ‎Brazilian Portuguese 95% • ‎Slovak 13% • ‎Chinese (China) 96%

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.

noframe
 
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 cómo nos puede ayudar para otras formas en las que puede colaborar. También vea: Escuadrón de errores!

Contents

Noticias y fuentes de correo

La dirección general del proyecto KDE está fijada por quienes hacen el trabajo ─no hay un plan maestro sobre cómo lucirá KDE en el futuro.

Si desea saber qué es lo que está pasando con KDE, hay un buen número de fuentes que podría considerar: ; Listas de correo: Probablemente la mejor manera de saber qué ocurre con el desarrollo de KDE. Los archivos están disponibles aquí

CommitFilter
Reciba notificaciones de los cambios en los depósitos de código fuente de KDE, en las áreas de su interés.
KDE Commit-Digest
Revise un resumen semanal, en inglés, de los cambios en el código fuente de KDE.
KDE.news
El sitio de noticias de KDE.
[1]
KDE Blog, un sitio en castellano con las últimas novedades de KDE.
[2]
Planeta KDE en castellano, para saber qué piensan y qué hacen los desarrolladores de KDE de Hispanoamérica.

Reporte de errores

Si usted sabe inglés, la forma más rápida de contribuir a KDE es reportar los errores que encuentre en KDE, usando el Sistema de Procesamiento de Errores de KDE. Recuerde hacer esto en inglés.

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 cómo crear reportes útiles de caída.

Empezando a programar

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.

C++

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 "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

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 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 Foundations of Qt Development.

If you prefer to learn Qt by reading a traditional book, take a look at the Books about Qt page. More suggestions on becoming familiar with Qt4 are available How to Learn Qt page.

KDE

A range of information on KDE techniques is available in the tutorial section. Note that some of these tutorials still target KDE3, though they should be at least partly applicable.

You will also find useful information on KDE coding in the FAQs section. This information may also be somewhat dated for KDE4, however much of it is broadly applicable, even outside KDE.

You can also read KDE coding books.

Last, but by no means least, KDE comes with extensive class (Application Programmer Interface) documentation. This is available in the KDE API Reference Manuals section, which also contains a number of useful links on how to write or update the class documentation. You can also generate these on your own machine, or refer to a more up-to-date online version at API Reference.

A more detailed description of the steps above is available in our Programming Guide.

Context Help: Whatsthis

Context help is inseparable from the dialogs and widgets, as they are the target of the context help. In fact, in order to write context help, you have to touch programming or programming tools. Indeed, the context help is a property of widgets. In object oriented programming, a property can have different values, and behave differently depending on the value. In Qt/KDE programming, the name of the property is "whatsthis", and its value is the text the context help is going to display.

Fortunately, this task is usually not very difficult, as there are good tools to deal with user interface design, and better, you will use the knowledge acquired here later when dealing with user interface in general. Using the Qt framework (Qt is the base of KDE technology), it is possible to separate code and user interface. You have two basic cases here: the user interface is written with the general code of application (usually .cpp files) or in Qt Designer files (.ui files: it is a XML document). The second case is the best to start with, as it is simpler to work with. If you don't have Qt Designer installed, you can do so by installing the devel package of Qt from your distribution or the Qt Designer package (if your distribution has more fine grained packages).

Here you can find a detailed guide for writing whatsthis using Qt Designer and working directly with the source code: WhatsThis Tutorial, by Aaron J. Seigo.

Getting Involved in Bug Hunting and Application Quality

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

User Interface

User interface is a very wide subject, and very subjective too, as something obvious to someone is absurd to others and vice versa. Therefore, don't assume, argue clearly, stating your logical steps. Your main tool discussing it are objective reasoning and good sense.

It is easy to perform a quick user interface analysis, but it is hard to convince people to change the interface. A good, convincing analysis can gain much if it incorporates information from the KDE guidelines, competing program and operational system analysis, general design principles found in many books, user testing or individual (anecdotal) feedback. It is a volunteer project, and even if everybody agree with you, someone has to implement it.

The KDE Usability Mailing List is very active and a good place for discussing your ideas, and their homepage is at http://techbase.kde.org/Projects/Usability. If you are already an usability expert, please check OpenUsability.org, a project that brings open source developers and usability experts together, and is collaborating closely with KDE.

Some documents guiding documents include the KDE User Interface Guidelines (design standards) and KDE User Interface Guidelines (design principles).

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.

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:

  • Read the Developer FAQ. Many common developer questions have been answered in the 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 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 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 search the great bulk of Usenet news sites, which is also particularly helpful, especially for general programming and gcc-related questions.

A full list of KDE mailing lists is available here and here.


KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal