diff options
Diffstat (limited to 'files/es/archive/b2g_os/developing_gaia')
3 files changed, 0 insertions, 212 deletions
diff --git a/files/es/archive/b2g_os/developing_gaia/entendiendo_el_codigo_base_de_gaia/index.html b/files/es/archive/b2g_os/developing_gaia/entendiendo_el_codigo_base_de_gaia/index.html deleted file mode 100644 index 6c1ea3499d..0000000000 --- a/files/es/archive/b2g_os/developing_gaia/entendiendo_el_codigo_base_de_gaia/index.html +++ /dev/null @@ -1,104 +0,0 @@ ---- -title: Entendiendo el código base de Gaia -slug: Archive/B2G_OS/Developing_Gaia/Entendiendo_el_codigo_base_de_Gaia -translation_of: Archive/B2G_OS/Developing_Gaia/Understanding_the_Gaia_codebase ---- -<div class="summary"> - <p><span class="seoSummary">Before you start to make your own changes to the <a href="https://github.com/mozilla-b2g/gaia/">Gaia codebase</a>, you should understand the basics of how it is all structured, and what coding conventions are used. This article covers both of these points.</span></p> -</div> -<h2 id="Gaia_branches">Gaia branches</h2> -<p>There are many different branches in the Gaia codebase, and depending on what work you are doing (or what device you have) you might not just want to download, hack and make the master branch. Here is a brief guide to the most common repos you'll likely be interested in:</p> -<ul> - <li><strong>master</strong> — the latest development branch. You'll want to use this branch if you are developing (or fixing bugs on) new features, or you want to run the latest Gaia on your phone or emulator</li> - <li><strong>v2.1</strong>, <strong>v2.0</strong>, <strong>v1.4</strong>, etc. — feature freeze versions of Gaia 2.1, 2.0, 1.4, etc. You'll want to use these branches if you are fixing a bug in a specific Gaia version, or want to develop an app and make sure it supports a specific Gaia version (for example, you might be using the Firefox OS Building Blocks with modifications, and want to make sure your layout still works across different Gaia versions.)</li> - <li><strong>v1.3t</strong> — the low-memory version of Gaia, developed for running on low-memory devices such as the Tarako or Spice Fire One. If you want to develop an app for such devices, this is the branch you should work with.</li> -</ul> -<h2 id="Gaia_codebase_structure">Gaia codebase structure</h2> -<p>The following section outlines all the most important parts of the Gaia codebase.</p> -<h3 id="apps">apps/</h3> -<p>This directory contains all of the main Gaia apps, both apps shown in the homescreen — such as calendar and camera — and underlying apps — such as system, homescreen, and keyboard.<br> - <br> - The apps work in slightly different ways, but all have a number of common features, including:</p> -<ul> - <li><code>index.html</code>: the central file for each app</li> - <li><code>manifest.webapp</code>: the manifest file defines the app</li> - <li><code>locales</code>: localisation strings for that app</li> - <li><code>test</code>: unit and integration tests particular to that app</li> - <li><code>js</code>, <code>style</code>: scripts and styles for that app</li> - <li><code>resources</code>: images, sounds and other assets</li> -</ul> -<div class="note"> - <p><strong>Note</strong>: You can find more information about the apps actually work on our <a href="/en-US/Firefox_OS/Platform/Gaia/Gaia_apps">Gaia apps guide</a>.</p> -</div> -<h3 id="build">build/</h3> -<p>This directory contains build scripts.</p> -<h3 id="dev_apps">dev_apps/</h3> -<p>This directory contains other apps that are included by customization. For example you could include custom apps that you want to include in custom builds in here.</p> -<div class="note"> - <p><strong>Note</strong>: For more information about Gaia customization, read our <a href="/en-US/Firefox_OS/Developing_Firefox_OS/Market_customizations_guide">Market customizations guide</a>.</p> -</div> -<h3 id="keyboard">keyboard/</h3> -<p>The keyboard directory contains keyboard dictionaries and layouts for different languages.</p> -<h3 id="locales">locales/</h3> -<p>This directory contains a JSON file, <code>languages_all.json</code>, which defines what languages are supported on Gaia. For more insight into how apps are localized, read <a href="/en-US/Apps/Build/Localization/Getting_started_with_app_localization">Getting started with app localization</a>.</p> -<h3 id="shared">shared/</h3> -<p>This directory contains a number of resources that multiple apps make use of; the most notable parts of these are:</p> -<ul> - <li><code>gaia/shared/js</code>: JavaScript libraries that perform common functions</li> - <li><code>l10n.js</code>: A localisation library that detects your device's locale, and replaces localisable strings in your apps with the strings found in the apps locales folders. Localisable strings to be replaced are contained in elements with <code>data-l10n-id</code> attributes.</li> - <li><code>gaia/shared/locales</code>: Localised resources for different locales.</li> - <li><code>gaia/shared/resources</code>: Common assets such as icons, ringtones and alarm sound tracks.</li> - <li><code>gaia/shared/style</code>: stylesheets and other styling resources for common building blocks such as buttons, progress bars, toolbars, tabs, etc. For more information on these, see <a href="/en-US/Apps/Design/Firefox_OS_building_blocks">Firefox OS Building Blocks</a>.</li> - <li><code>gaia/shared/style_unstable</code>: unstable or experimental styling resources.</li> - <li><code>gaia/shared/test</code>: JavaScript to define integration and unit tests.</li> -</ul> -<h3 id="tools">tools/</h3> -<p>The tools directory contains tools for build scripts and tests.</p> -<h2 id="Gaia_coding_style">Gaia coding style</h2> -<p>Gaia follows the <a href="http://google-styleguide.googlecode.com/svn/trunk/javascriptguide.xml">Google JavaScript coding style</a>.</p> -<p>Background information:</p> -<ul> - <li>Coding Style: <a href="/en-US/docs/Mozilla/Developer_guide/Coding_Style#General_practices">General practices</a></li> - <li>Coding Style: <a href="/en-US/docs/Mozilla/Developer_guide/Coding_Style#JavaScript_practices">JavaScript practices</a></li> - <li>Coding Style: <a href="/en-US/docs/Mozilla/Developer_guide/Coding_Style#Naming_and_Formatting_code">Naming and formatting code</a></li> -</ul> -<h3 id="Specific_rules">Specific rules</h3> -<ol> - <li>Make sure HTML files are declared with <code><!DOCTYPE html></code> (that is, as HTML5 documents). If you don't, Internet Explorer 9 and later will load them in compatibility mode.</li> - <li>Include the <code>"use strict";</code> statement (just like that, including the quotes) to the top of your JavaScript files to put them into strict mode.</li> - <li>Always use two spaces for indentation, rather than tabs.</li> - <li>Please use line breaks to separate logical bits of code!</li> - <li>Multi-word file names should use the "underscore" character to separate words, <code>like_this.js</code>.</li> - <li>Use single quotes instead of double quotes for strings.</li> - <li>Use expanded conditional structures: - <pre class="brush: js">Bad -if (expression) doSomething(); - -Correct -if (expression) { - doSomething(); -}</pre> - </li> - <li>If you're working on the <a href="/en-US/Firefox_OS/Platform/Gaia/Gaia_apps/System">System app</a>, check out the <a href="https://groups.google.com/forum/#!msg/mozilla.dev.gaia/rEhSrw6XmT4/UNvE7qW9pgYJ">guidance listed here</a>.</li> -</ol> -<h3 id="Per_commit_coding_style_check">Per commit coding style check</h3> -<p>Gaia uses <a href="http://www.jshint.com/">jshint</a> to automatically check JS coding styles before each commit (via a git pre-commit hook). Once you submit a Pull Request to the Gaia repository, the Travis (Github Continuous Integration) server will run this linter to double check all styles are right.</p> -<p>The precommit hook script is in <a href="https://github.com/mozilla-b2g/gaia/blob/master/tools/pre-commit">gaia/tools/pre-commit</a> and will be copied to project's <code>.git/hooks</code> folder once a <code>make</code> command is executed.</p> -<div class="note"> - <p><strong>Note</strong>: We used to use <a href="https://developers.google.com/closure/utilities/docs/linter_howto">gjslint</a> to check coding styles, but we have since deprecated its use as jshint is stricter and produces better results. We’ve been using JSHint since Firefox OS 1.4, and gjslint is now only recommended for legacy files that have not yet been moved to JSHint.</p> -</div> -<h3 id="Running_linting_checks_manually_via_Gaia">Running linting checks manually via Gaia</h3> -<p>Before submitting a patch we recommend you run JSHint on it manually to check for any style errors.<br> - <br> - You should look in the <a href="https://github.com/mozilla-b2g/gaia/tree/master/build/jshint">gaia/build/jshint</a> directory for more details about jshint in Gaia; Gaia provides the build script for you. You can run:</p> -<pre class="brush: bash">$ make lint</pre> -<p>to automatically run both the gjslint and jshint style checks. Or you can run</p> -<pre class="brush: bash">$ make hint</pre> -<p>to just run the jshint style check.</p> -<div class="note"> - <p><strong>Note</strong>: If you want to install jshint yourself, without using Gaia, you can use the following:</p> - <pre class="brush: bash">npm install jshint -g -jshint myfile.js -</pre> -</div> -<p> </p> diff --git a/files/es/archive/b2g_os/developing_gaia/index.html b/files/es/archive/b2g_os/developing_gaia/index.html deleted file mode 100644 index 93fce20871..0000000000 --- a/files/es/archive/b2g_os/developing_gaia/index.html +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: Desarrollando Gaia -slug: Archive/B2G_OS/Developing_Gaia -tags: - - Construir - - Firefox OS - - Gaia - - Mozilla -translation_of: Archive/B2G_OS/Developing_Gaia ---- -<div class="summary"> - <p><span class="seoSummary">Gaia es la interfaz de usuario de Firefox OS y el conjunto de aplicaciones por defecto: Incluye la pantalla de bloqueo, la pantalla de inicio, marcadores, y otras aplicaciones. Esencialmente, Gaia es un conjunto de aplicaciones web complejas que se ejecutan en la capa superior de la plataforma Firefox OS. Este conjunto de articulos cubre todo lo que necesita saber para contribuir con el proyecto Gaia.</span></p> -</div> -<p>En esta guía te llevaremos a un proceso de trabajo eficaz para contribuir con <em>Gaia</em> — y por eso queremos decir la adición de características al codigo base de <em>Gaia</em> y trabajando en errores presentes en el proyecto <em>Gaia</em>. El primer grupo de articulos se puden trabajar en orden, o se puede saltar a la sección que necesita para recordar un aspecto específico de el proceso.</p> -<p>Después de eso, se proporcionan materiales de referencia e información de temas adicionales.</p> -<p><img alt="" src="https://mdn.mozillademos.org/files/7951/gaia-2.0-screen.png" style="padding: 0px 0px 30px 30px; width: 320px; height: 533px; float: right;"></p> -<h2 id="Lo_básico">Lo básico</h2> -<ol> - <li><a href="/es/Firefox_OS/Developing_Gaia/Running_the_Gaia_codebase">Ejecutar el codigo base de Gaia</a></li> - <li><a href="/en-US/Firefox_OS/Developing_Gaia/Understanding_the_Gaia_codebase"><span class="short_text" id="result_box" lang="es"><span class="hps alt-edited">Entender</span> <span class="hps alt-edited">el</span> <span class="hps alt-edited">código base</span> <span class="hps alt-edited">de Gaia</span></span></a></li> - <li><a href="/en-US/Firefox_OS/Developing_Gaia/Making_Gaia_code_changes">Hacer cambios en el código de Gaia</a></li> - <li><a href="/en-US/Firefox_OS/Developing_Gaia/Test_Gaia_code_changes">Probando los cambios en el código de Gaia</a></li> - <li><a href="/en-US/Firefox_OS/Developing_Gaia/Submitting_a_Gaia_patch">Enviar los cambios de Gaia</a></li> -</ol> -<h2 id="Referencia_contrucción_de_Gaia">Referencia contrucción de Gaia</h2> -<ul> - <li><a href="/en-US/Firefox_OS/Developing_Gaia/Build_System_Primer">Introducción al sistema de contrucción de Gaia</a></li> - <li><a href="/en-US/Firefox_OS/Developing_Gaia/Customizing_build-time_apps">Personalizar aplicaciones en tiempo de compilación</a></li> - <li><a href="/en-US/Firefox_OS/Developing_Gaia/make_options_reference">Referencia de las opciones del comando Make</a></li> - <li><a href="/en-US/Firefox_OS/Developing_Gaia/Gaia_tools_reference">Referencia a las herramientas de Gaia</a></li> -</ul> -<h2 id="Ver_también">Ver también</h2> -<ul> - <li><a href="/en-US/Firefox_OS/Developing_Firefox_OS/Filing_bugs_against_Firefox_OS">Informar sobre errores de Firefox OS</a></li> - <li><a href="/en-US/Firefox_OS/Platform/Gaia/Gaia_apps">Guía de las aplicaciones de Gaia</a></li> - <li><a href="/it/Firefox_OS/Guida_rapida_allo_sviluppo_di_Gaia/Diversi_modi_per_eseguire_Gaia">Diversidad de maneras para visualizar Gaia</a></li> - <li><a href="/en-US/Firefox_OS/Developing_Gaia/Market_customizations_guide">Guía de personalización de comercialización</a></li> - <li><a href="/en-US/Firefox_OS/Developing_Gaia/Customizing_the_keyboard">Personalización del teclado para las aplicaciones en Firefox OS</a></li> - <li><a href="/en-US/Firefox_OS/Developing_Gaia/Localizing_Firefox_OS">Localización en Firefox OS (Guía de localización)</a></li> - <li><a href="/en-US/Firefox_OS/Developing_Gaia/L10n_Best_Practices">L10n Buenas Practicas (Para desarrolladores )</a></li> -</ul> -<p> </p> -<p></p><div class="overheadIndicator communitybox" dir="ltr"> - - <div class="column-container"> - <h2 id="Join_the_Gaia_community">Join the Gaia community</h2> - <div class="column-half"> - <div class="communitysubhead">Choose your preferred method for joining the discussion:</div> - <ul class="communitymailinglist"> - <li><a href="https://lists.mozilla.org/listinfo/dev-gaia"> como lista de correo</a></li> - - - <li><a href="http://groups.google.com/group/mozilla.dev.gaia"> como grupo de noticias</a></li> - <li><a href="http://groups.google.com/group/mozilla.dev.gaia/feeds"> como RSS</a></li> -</ul> - </div> - <div class="column-half"> - <ul class="communitycontact"><li><strong>IRC: </strong><a href="irc://irc.mozilla.org/gaia">#gaia</a> <span class="smaller">(<a href="https://wiki.mozilla.org/IRC">learn more</a>)</span></li><li><strong>Other IRC channels: </strong><a href="irc://irc.mozilla.org/b2g" title="Discuss B2G, the overall Firefox OS platform">#b2g</a>, <a href="irc://irc.mozilla.org/openwebapps" title="Talk with Web app developers">#openwebapps</a>, <a href="irc://irc.mozilla.org/webapi" title="Discuss Web APIs used to create powerful Web apps">#webapi</a></li></ul> - </div> - </div> -</div><p></p> diff --git a/files/es/archive/b2g_os/developing_gaia/running_the_gaia_codebase/index.html b/files/es/archive/b2g_os/developing_gaia/running_the_gaia_codebase/index.html deleted file mode 100644 index 334a44b435..0000000000 --- a/files/es/archive/b2g_os/developing_gaia/running_the_gaia_codebase/index.html +++ /dev/null @@ -1,47 +0,0 @@ ---- -title: Ejecutar el codigo base de Gaia -slug: Archive/B2G_OS/Developing_Gaia/Running_the_Gaia_codebase -tags: - - Gaia -translation_of: Archive/B2G_OS/Developing_Gaia/Running_the_Gaia_codebase ---- -<div class="summary"> - <p><span class="seoSummary">Este artículo se muestra en detalle cómo ejecutar el código base de Gaia, y qué herramienta están disponibles en esta configuración.</span></p> -</div> -<p>Para empezar, debemos señalar que NO tiene que compilar Gecko, o B2G, para contribuir con Gaia. Sólo tienes que descargar el código fuente de Gaia y tendrás la capacidad de ejecutarlo y editarlo.<br> - <br> - Hay diferentes formas de ejecutar Gaia:</p> -<ul> - <li>Flashear tu teléfono con tu actualización Gaia.</li> - <li>Iniciar tu Gaia dentro de B2G Desktop.</li> - <li>Correr tu Gaia dentro del WebIDE.</li> - <li>Iniciar Gaia dentro de nuestra herramienta de Firefox Mulet tool para correr Gaia en el Escritorio.</li> -</ul> -<p>Puedes encontrar información concisa de como <a href="/en-US/Firefox_OS/Developing_Gaia/Different_ways_to_run_Gaia">ejecutar Gaia de estas diferentes maneras </a>desde esta página, junto con enlaces e información detallada. En general, estos se ordenan de lo más complejo (experiencia más realista), a lo más fácil (experiencia menos realista).</p> -<p>En este artículo vamos a concentrarnos en el funcionamiento de Gaia dentro de Firefox Mulet o en el WebIDE — para la mayoría de los cambios que hagas en el código base de Gaia, este mecanismo ofrece la forma más rapida de probar los cambios, pero obviamente hay algunas características (tales como probar las API del dispositivo o la interaccíon con el hardware del teléfono) no estarán disponibles, ya que necesitara un dispositivo real.</p> -<div class="note"> - <p><strong>Nota</strong>: Para obtener más ayuda con Gaia, los mejores lugares son el canal #gaia (ver <a href="https://wiki.mozilla.org/IRC">Mozilla IRC</a> para más información) y la <a href="https://lists.mozilla.org/listinfo/dev-gaia">lista de correo dev-gaia</a>.</p> -</div> -<h2 id="Ejecutar_tu_construcción_de_Gaia">Ejecutar tu construcción de Gaia</h2> -<ol> - <li>Primero, hacer una bifurcación (fork) de el <a href="https://github.com/mozilla-b2g/gaia">Repositorio de Gaia en Github</a>.</li> - <li>Después, clona tu bifurcación localmente: - <pre class="brush: bash">git clone https://github.com/your-username/gaia.git</pre> - </li> - <li>Agrega tu producción (upstream) como esto: - <pre class="brush: bash">cd gaia -git remote add upstream https://github.com/mozilla-b2g/gaia</pre> - </li> - <li>Now you need to create a Gaia profile. Running <code>make</code> inside your repo folder creates a profile in the <code>profile</code> directory, which is setup for optimal debugging. It creates unpackaged (hosted versions) of the Gaia apps that can be served directly via the local HTTPD server bundled along with Firefox desktop as an extension. When you make a change you just need to refresh your browser window to see the result (as you'll see later), rather than having to rebuild the profile, repush it to the device, etc. This is really good for rapid CSS/JS/HTML hacking.</li> - <li>With your debug profile built, run it in <a href="/en-US/Firefox_OS/Developing_Gaia/Different_ways_to_run_Gaia#Using_Gaia_in_Firefox_Mulet">Mulet</a> or <a href="/en-US/Firefox_OS/Developing_Gaia/Different_ways_to_run_Gaia#Using_Gaia_inside_WebIDE_with_a_Firefox_OS_Simulator">WebIDE</a>, using the linked instructions.</li> -</ol> -<h2 id="Troobleshooting_and_known_issues">Troobleshooting and known issues</h2> -<h3 id="Error_Python_executable_python3_is_v3.x_which_is_not_supported_by_gyp.">Error: Python executable "python3" is v3.x, which is not supported by gyp.</h3> -<p>On some Linux distributions (eg: Archlinux), the default <code>python</code> is <code>python3</code>. This makes <code>npm</code> fail when running some commands (eg. when running tests). To fix it once and for all, you can run the following command:</p> -<pre>npm config set python python2</pre> -<p>You can look at this <a href="http://stackoverflow.com/questions/20454199/how-to-use-a-different-version-of-python-duing-npm-install">Stack Overflow page</a> for other solutions.</p> -<p>Then you should delete your <code>node_modules</code> directory and run the failed command again.</p> -<h3 id="Please_Install_NodeJS_--_(use_aptitude_on_linux_or_homebrew_on_osx)">Please Install NodeJS -- (use aptitude on linux or homebrew on osx)</h3> -<p>So, you get this error although you think you installed it. Chances are you're running Debian or another Debian-based distribution like Ubuntu. On these distributions, NodeJS is contained in the <code>nodejs</code> package, and you can install the <code>nodejs-legacy</code> package to set up everything correctly:</p> -<pre>sudo aptitude install nodejs-legacy</pre> -<p>If you have issues installing this package, maybe you're using <a href="http://www.ubuntuupdates.org/ppa/chris_lea_nodejs">Chris Lea's PPA for Node</a>; please remove it before moving forward.</p> |