Sugar Labs - User contributions [en]

Activities/Conozco Paraguay

2015-07-24T15:47:48Z

Km0r3: /* Conozco Paraguay */

= Conozco Paraguay =

Sugar activity for learning the Paraguayan geography. This activity is a fork of the Conozco Uruguay app.

Current maintainer: Richar José Ferreira <rnezferreira9@gmail.com>

Previous maintainer: Kenny Meyer < kenny@protonmail.ch >

== Screenshot ==

[[File:Conozco-paraguay.png]]

== Versions ==

=== 1 ===

Details:

* Full features Paraguay map
* Bicentario-powered
* Paraguayan colors

== TODO list ==

* Maps
** Paraguay
*** Cuchillas
** Central
*** Cursos de agua
*** Rutas
** Y los otros departamentos

== Contributors ==

Contributors are needed! The project needs designers who can help designing the departamentos.

Contributions are only limited by your imagination, and every contribution is welcome.

== Development ==

Development is located at git.sugarlabs.org[http://git.sugarlabs.org/conozco-paraguay/mainline].

=== Getting the code ===

$ git clone git://git.sugarlabs.org/conozco-paraguay/mainline.git

Activities/Conozco Paraguay

2015-07-24T15:47:37Z

Km0r3: /* Conozco Paraguay */

= Conozco Paraguay =

Sugar activity for learning the Paraguayan geography. This activity iss a fork of the Conozco Uruguay app.

Current maintainer: Richar José Ferreira <rnezferreira9@gmail.com>

Previous maintainer: Kenny Meyer < kenny@protonmail.ch >

== Screenshot ==

[[File:Conozco-paraguay.png]]

== Versions ==

=== 1 ===

Details:

* Full features Paraguay map
* Bicentario-powered
* Paraguayan colors

== TODO list ==

* Maps
** Paraguay
*** Cuchillas
** Central
*** Cursos de agua
*** Rutas
** Y los otros departamentos

== Contributors ==

Contributors are needed! The project needs designers who can help designing the departamentos.

Contributions are only limited by your imagination, and every contribution is welcome.

== Development ==

Development is located at git.sugarlabs.org[http://git.sugarlabs.org/conozco-paraguay/mainline].

=== Getting the code ===

$ git clone git://git.sugarlabs.org/conozco-paraguay/mainline.git

Activities/Conozco Paraguay

2015-07-24T15:46:52Z

Km0r3: Changed current maintainer

= Conozco Paraguay =

Sugar activity for learning the Paraguayan geography. This ictivity iss a fork of the Conozco Uruguay app.

Current maintainer: Richar José Ferreira <rnezferreira9@gmail.com>

Previous maintainer: Kenny Meyer < kenny@protonmail.ch >

== Screenshot ==

[[File:Conozco-paraguay.png]]

== Versions ==

=== 1 ===

Details:

* Full features Paraguay map
* Bicentario-powered
* Paraguayan colors

== TODO list ==

* Maps
** Paraguay
*** Cuchillas
** Central
*** Cursos de agua
*** Rutas
** Y los otros departamentos

== Contributors ==

Contributors are needed! The project needs designers who can help designing the departamentos.

Contributions are only limited by your imagination, and every contribution is welcome.

== Development ==

Development is located at git.sugarlabs.org[http://git.sugarlabs.org/conozco-paraguay/mainline].

=== Getting the code ===

$ git clone git://git.sugarlabs.org/conozco-paraguay/mainline.git

Activities/Conozco Paraguay

2011-06-03T23:19:46Z

Km0r3: /* Contributors */

= Conozco Paraguay =

Modification of Conozco Uruguay for learning Paraguayan geography (and possibly more, in the future).

Current maintainer and contact person: Kenny Meyer <knny.myer@gmail.com>

== Screenshot ==

[[File:Conozco-paraguay.png]]

== Versions ==

=== 1 ===

Details:

* Full features Paraguay map
* Bicentario-powered
* Paraguayan colors

== TODO list ==

* Maps
** Paraguay
*** Cuchillas
** Central
*** Cursos de agua
*** Rutas
** Y los otros departamentos

== Contributors ==

Contributors are needed! The project needs designers who can help designing the departamentos. Please, contact me directly at knny.myer@gmail.com to discuss the details.

Contributions are only limited by your imagination, and every contribution is welcome.

== Development ==

Development is located at git.sugarlabs.org[http://git.sugarlabs.org/conozco-paraguay/mainline].

=== Getting the code ===

$ git clone git://git.sugarlabs.org/conozco-paraguay/mainline.git

Activities/Conozco Paraguay

2011-06-03T23:18:12Z

Km0r3:

= Conozco Paraguay =

Modification of Conozco Uruguay for learning Paraguayan geography (and possibly more, in the future).

Current maintainer and contact person: Kenny Meyer <knny.myer@gmail.com>

== Screenshot ==

[[File:Conozco-paraguay.png]]

== Versions ==

=== 1 ===

Details:

* Full features Paraguay map
* Bicentario-powered
* Paraguayan colors

== TODO list ==

* Maps
** Paraguay
*** Cuchillas
** Central
*** Cursos de agua
*** Rutas
** Y los otros departamentos

== Contributors ==

Contributors are needed! The project needs designers who can help designing the departamentos. Please, contact me directly at knny.myer@gmail.com to discuss the details.

Contributions are only limited by your imagination, so every contribution is welcome.

== Development ==

Development is located at git.sugarlabs.org[http://git.sugarlabs.org/conozco-paraguay/mainline].

=== Getting the code ===

$ git clone git://git.sugarlabs.org/conozco-paraguay/mainline.git

Activities/Conozco Paraguay

2011-06-03T23:09:58Z

Km0r3:

= Conozco Paraguay =

Modification of Conozco Uruguay for learning Paraguayan geography (and possibly more, in the future).

== Screenshot ==

[[File:Conozco-paraguay.png]]

== Versions ==

=== 1 ===

Details:

* Full features Paraguay map
* Bicentario-powered
* Paraguayan colors

== TODO list ==

* Maps
** Paraguay
*** Cuchillas
** Central
*** Cursos de agua
*** Rutas
** Y los otros departamentos

File:Conozco-paraguay.png

2011-06-03T23:04:29Z

Km0r3:

Activities/Conozco Paraguay

2011-05-23T01:03:38Z

Km0r3: Created page with "Modification of Conozco Uruguay for learning Paraguayan geography (and possibly more, in the future)."

Modification of Conozco Uruguay for learning Paraguayan geography (and possibly more, in the future).

Karma/i18n

2010-06-14T00:24:17Z

Km0r3: /* JavaScript Strings */

Rough plan for implementing i18n for Karma

=== Requirements ===
* Integrate with pootle
* Handle strings inside code and html markup
Examples
$("#someDiv").text(gettext("Hello World"));
<nowiki>
<div>Hello <strong>W</strong>orld</div>
</nowiki>

* All strings stored in one file per locale, messages.json
* All message identifiers must be unique within an a lesson
* Accommodating numeric, currency, and date formatting is not an immediate requirement

=== General Strategy ===
====JavaScript Strings====
We try to follow a subset of the [http://www.gnu.org/software/gettext/manual/gettext.html#gettext gettext api] quite closely. After including jquery.i18n.js you can use the following gettext functions in your javascript scripts:
* $.i18n.gettext('text to be translated') or $. _('text to be translated'): to translate a simple string
* $.i18n.ngettext('a car', 'multiple cars', n): to choose a pluralized form depending on n
* $.i18n.pgettext('context', 'text to be translated'): this is useful if you are writing plugins. E.g. in ui.kFooter.js the context is '$.ui.kFooter'.

Remarks:
* you can add the statement var _ = $._; at the beginning of your $(document).ready function and then use _('message') without needing to add the $. However the name of the function you are calling should be _, gettext, ngettext or pgettext. Otherwise the strings can not be automatically be extracted with xgettext.
* the arguments to the different calls should be string literals. Otherwise xgettext will not be able to extract the messages to be translated.

More resources:
http://forum.jquery.com/topic/locale-information-should-be-separated-from-plugins
http://wiki.jqueryui.com/i18n

====HTML Strings====

The Python library [http://www.hforge.org/itools itools] automates the job of parsing the HTML and creating the PO files. There are already concrete experiments, which you can find [http://git.olenepal.org/~km0r3/karma/km0r3-karma/commits/experimental here].

Things which still need to be done:
* Dynamically change out strings per locale on page load (HIGH PRIORITY)
* A well-defined workflow
** integrate the JavaScript i18n within the workflow.
* Documentation.

I'm still actively working on it. Questions, comments, suggestions > km0r3 AT sugarlabs DOT org .

Karma/i18n

2010-06-14T00:13:14Z

Km0r3: /* JavaScript Strings */

Rough plan for implementing i18n for Karma

=== Requirements ===
* Integrate with pootle
* Handle strings inside code and html markup
Examples
$("#someDiv").text(gettext("Hello World"));
<nowiki>
<div>Hello <strong>W</strong>orld</div>
</nowiki>

* All strings stored in one file per locale, messages.json
* All message identifiers must be unique within an a lesson
* Accommodating numeric, currency, and date formatting is not an immediate requirement

=== General Strategy ===
====JavaScript Strings====
We try to follow a subset of the [http://www.gnu.org/software/gettext/manual/gettext.html#gettext gettext api] quite closely. After including jquery.i18n.js you can use the following gettext functions in your javascript scripts:
* $.i18n.gettext('text to be translated') or $. _('text to be translated'): to translate a simple string
* $.i18n.ngettext('a car', 'multiple cars', n): to choose a pluralized form depending on n
* $.i18n.pgettext('context', 'text to be translated'): this is useful if you are writing plugins. E.g. in ui.kFooter.js the context is '$.ui.kFooter'.

Remarks:
* you can add the statement var _ = $._; at the beginning of your $(document).ready function and then use _('message') without needing to add the $. However the name of the function you are calling should be _, gettext, ngettext or pgettext. Otherwise the strings can not be automatically be extracted with xgettext.
* the arguments to the different calls should be string literals. Otherwise xgettext will not be able to extract the messages to be translated.

More information: http://forum.jquery.com/topic/locale-information-should-be-separated-from-plugins

====HTML Strings====

The Python library [http://www.hforge.org/itools itools] automates the job of parsing the HTML and creating the PO files. There are already concrete experiments, which you can find [http://git.olenepal.org/~km0r3/karma/km0r3-karma/commits/experimental here].

Things which still need to be done:
* Dynamically change out strings per locale on page load (HIGH PRIORITY)
* A well-defined workflow
** integrate the JavaScript i18n within the workflow.
* Documentation.

I'm still actively working on it. Questions, comments, suggestions > km0r3 AT sugarlabs DOT org .

Karma/i18n

2010-06-05T04:49:26Z

Km0r3: /* HTML Strings */

Rough plan for implementing i18n for Karma

=== Requirements ===
* Integrate with pootle
* Handle strings inside code and html markup
Examples
$("#someDiv").text(gettext("Hello World"));
<nowiki>
<div>Hello <strong>W</strong>orld</div>
</nowiki>

* All strings stored in one file per locale, messages.json
* All message identifiers must be unique within an a lesson
* Accommodating numeric, currency, and date formatting is not an immediate requirement

=== General Strategy ===
====JavaScript Strings====
We try to follow a subset of the [http://www.gnu.org/software/gettext/manual/gettext.html#gettext gettext api] quite closely. After including jquery.i18n.js you can use the following gettext functions in your javascript scripts:
* $.i18n.gettext('text to be translated') or $. _('text to be translated'): to translate a simple string
* $.i18n.ngettext('a car', 'multiple cars', n): to choose a pluralized form depending on n
* $.i18n.pgettext('context', 'text to be translated'): this is useful if you are writing plugins. E.g. in ui.kFooter.js the context is '$.ui.kFooter'.

Remarks:
* you can add the statement var _ = $._; at the beginning of your $(document).ready function and then use _('message') without needing to add the $. However the name of the function you are calling should be _, gettext, ngettext or pgettext. Otherwise the strings can not be automatically be extracted with xgettext.
* the arguments to the different calls should be string literals. Otherwise xgettext will not be able to extract the messages to be translated.

The lesson examples/6_Maths_matchingAnglesAndShapes/ contains an example.

====HTML Strings====

The Python library [http://www.hforge.org/itools itools] automates the job of parsing the HTML and creating the PO files. There are already concrete experiments, which you can find [http://git.olenepal.org/~km0r3/karma/km0r3-karma/commits/experimental here].

Things which still need to be done:
* Dynamically change out strings per locale on page load (HIGH PRIORITY)
* A well-defined workflow
** integrate the JavaScript i18n within the workflow.
* Documentation.

I'm still actively working on it. Questions, comments, suggestions > km0r3 AT sugarlabs DOT org .

Karma/i18n

2010-06-05T04:48:42Z

Km0r3: /* HTML Strings */

Rough plan for implementing i18n for Karma

=== Requirements ===
* Integrate with pootle
* Handle strings inside code and html markup
Examples
$("#someDiv").text(gettext("Hello World"));
<nowiki>
<div>Hello <strong>W</strong>orld</div>
</nowiki>

* All strings stored in one file per locale, messages.json
* All message identifiers must be unique within an a lesson
* Accommodating numeric, currency, and date formatting is not an immediate requirement

=== General Strategy ===
====JavaScript Strings====
We try to follow a subset of the [http://www.gnu.org/software/gettext/manual/gettext.html#gettext gettext api] quite closely. After including jquery.i18n.js you can use the following gettext functions in your javascript scripts:
* $.i18n.gettext('text to be translated') or $. _('text to be translated'): to translate a simple string
* $.i18n.ngettext('a car', 'multiple cars', n): to choose a pluralized form depending on n
* $.i18n.pgettext('context', 'text to be translated'): this is useful if you are writing plugins. E.g. in ui.kFooter.js the context is '$.ui.kFooter'.

Remarks:
* you can add the statement var _ = $._; at the beginning of your $(document).ready function and then use _('message') without needing to add the $. However the name of the function you are calling should be _, gettext, ngettext or pgettext. Otherwise the strings can not be automatically be extracted with xgettext.
* the arguments to the different calls should be string literals. Otherwise xgettext will not be able to extract the messages to be translated.

The lesson examples/6_Maths_matchingAnglesAndShapes/ contains an example.

====HTML Strings====

The Python library [http://www.hforge.org/itools itools] automates the job of parsing the HTML and creating the PO files. There are already concrete experiments, which you can find [http://git.olenepal.org/~km0r3/karma/km0r3-karma/commits/experimental here].

Things which still need to be done:
* Dynamically change out strings per locale on page load (HIGH PRIORITY)
* A well-defined workflow
* integrate the JavaScript i18n within the workflow.
* Documentation.

I'm still actively working on it. Questions, comments, suggestions > km0r3 AT sugarlabs DOT org .

User:Km0r3

2010-04-08T00:02:31Z

Km0r3: /* In Process */

== Contact details ==

Email: knny dot myer at gmail dot com

Blog: http://kenny.alwaysdata.net

[http://www.irchelp.org/irchelp/irctutorial.html irc]: km0r3 at [http://freenode.net FreeNode] (#sugar, #olpc-paraguay)

== Brief Bio ==

Kenny Meyer is currently volunteering to the OLPC Project.

He's a student from Paraguay where he's studying Computer Science.

He started programming with Python in 2008 and gained experience with the language writing Web Applications with Django [http://www.djangoproject.com] and Linux System Scripting.

If he's not busy programming he plays the guitar or helps Newbies in Linux forums or hangs out in IRC rooms. He also loves books and reads when not in reach of a computer.

== Notes ==

=== Sugar-specific ===

==== Reset XO Registration ====

rm -rf ~/.gconf/desktop/sugar

Source: http://wiki.laptop.org/go/Schoolserver_Testing

==== Application environment diagram ====
<pre>
----------------------------------------------------------------
| | | | |
| | Non-python | Sugar shell | Python |
| | Sugar | (Desktop window, | Sugar |
| | Activities | panel, | Activities |
| Regular | (Etoys, | journal) | |
| X | Simcity, | | |
| Apps | Mono |--------------------------------------|
| | activities, | Sugar toolkit (python-only) |
| | etc.) | |
| |----------------------------------------------------|
| | DataStore | Presence |
| | service | service |
----------------------------------------------------------------
| Matchbox window manager |
| (considering switching to Metacity for improved compatibility) |
----------------------------------------------------------------
| |
| GNOME-ish Linux desktop |
| X11, HAL, D-Bus, NetworkManager, GConf, Telepathy, etc |
| |
----------------------------------------------------------------
</pre>
Source: http://wiki.laptop.org/go/Software_components

== Bugs ==

=== Fixed ===

=== Closed ===

=== In Process ===

Show file size in Journal: http://bugs.sugarlabs.org/ticket/1915

User:Km0r3

2010-03-29T00:43:39Z

Km0r3:

Development Team/Jhbuild/lang-es

2010-03-28T05:19:56Z

Km0r3: Sección "Construir una versión específica de Sugar" añadida

{{Translation
| lang = es
| source = Development Team/Jhbuild
| version = 27498}}

{{ Translated text | Sugar-jhbuild will automatically download the latest of Sugar's dependencies as well as Sugar itself directly from their source repositories, rather than relying on source packages that may have become stale. Below are generic instructions on how to use jhbuild to get up and running with Sugar. | display = None }}

Sugar-jhbuild descargará automáticamente las últimas versiones de las dependencias de Sugar, como también a Sugar mismo directamente de los repositorios fuente, en vez de confiar en paquetes de código que pueden haber haber quedado estancados. Debajo se encuentran instrucciones genéricas de como usar jhbuild y hacerlo funcionar con Sugar.

{{anchor|Compatible platforms}}
== Plataformas compatibles ==

{{ Translated text | Jhbuild is quite demanding with regard to the packages and setup for the host Linux distribution. As a result there are only a few Linux distributions which are known to work with it.

See the distribution specific instructions for information about whether your distribution is currently supported. Other distros which have a recent-enough release (e.g. including the latest stable GNOME release) can be supported if someone is willing to maintain the dependencies for that distro release (in config/sysdeps). | display = None }}

Jhbuild demanda bastante en cuanto a los paquetes y la configuración de la distribución de Linux anfitrión. Como resultado solo hay unas pocas distribuciones de Linux que se conoce que funcionan con él.

Vea las instrucciones específicas a su distribución para saber si actualmente está soportada. Otras distros que tienen una emisión suficientemente reciente (por ej. que incluyan la última versión estable de GNOME) pueden ser soportadas si alguien está dispuesto a mantener las dependencias para esa emisión de la distro (en config/sysdeps).

{{anchor|Check distro-specific instructions}}
== Consulte las instrucciones específicas a una distro ==

{{ Translated text | Many distributions have some quirks that need to be catered for and there are different package managing tools in use, so please check the page for your distribution before proceeding: | display = None}}

Muchas distribuciones tienen algunas mañas que necesitan atención, y hay distintas herramientas de manejo de paquetes en uso, así que por favor consulte la página para su distribución antes de proceder:

* [[../Debian|Debian]]
* [[../Fedora|Fedora]]
* [[../Ubuntu|Ubuntu]]
* [[../Mandriva|Mandriva]]

{{anchor|Check out sugar-jhbuild}}
== Checkout de sugar-jhbuild ==

{{ Translated text|
In a suitable directory, execute

git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild | display = None }}

En un directorio adecuado ejecute:

git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild

{{anchor|Build sugar base system and its dependencies}}
== Construír Sugar y sus dependencias ==

{{ Translated text | Change directory and start the build.

cd sugar-jhbuild
./sugar-jhbuild update
./sugar-jhbuild depscheck
./sugar-jhbuild build | display = None }}

Cambie de directorio y comience la construcción:

cd sugar-jhbuild
./sugar-jhbuild update
./sugar-jhbuild depscheck
./sugar-jhbuild build

{{anchor|Dealing with dependencies}}
=== Ocupándose de las dependencias ===

{{ Translated text | sugar-jhbuild depscheck will print a list of required packages. They are part of the distribution you're using and should be installed using your favourite package manager (e.g. aptitude/synaptic for Debian, yum for Fedora). If you notice that there's a package missing from the depscheck output (i.e. it's required for Sugar to work properly and not installed, but depscheck does not mention it), please file a bug report (login required first, but currently no automatic redirection to login page) against the sugar-jhbuild Component in the Sugar Labs bug tracker. | display = None }}

sugar-jhbuild depscheck imprimirá una lista de paquetes requeridos. Son parte de la distribución que está usando y deben ser instalados usando su manejador de paquetes favorito (por ej. aptitude/synaptic para Debian, yum para Fedora). Si nota que hay un paquete faltante en la salida de depscheck (es decir, un paquete requerido para el correcto funcionamiento de Sugar, que no está instalado, pero depscheck no lo menciona), por favor [http://dev.sugarlabs.org/newticket?component=sugar-jhbuild&version=Git%20as%20of%20bugdate&type=defect&summary=Need%20package%20%3cinsert%20name%20of%20package%3e%20on%20%3cinsert%20name%20of%20distribution%3e&description=%3cplease%20explain%20why%20you%20think%20the%20package%20is%20required%20%28e.g.%20error%20message%29%3e entre un reporte de bug] (se requiere que se identifique primero, pero actualmente no se redirige después de entrar al sistema) contra el componente sugar-jhbuild en el [http://dev.sugarlabs.org/ Sistema de seguimiento de bug de Sugar Labs]

{{ Translated text | Some tips:
* hulahop stopped building because I had installed a more recent version of xulrunner on my machine. The workaround was to <code>rm -rf ~/sugar-jhbuild/source/hulahop</code> and then run update and build again. | display = None }}

Algunos consejos:
* hulahop había dejado de construirse porque había instalado una versión más reciente de xulrunner en mi máquina. La solución fue <code>rm -rf ~/sugar-jhbuild/source/hulahop</code> y luego correr update y build nuevemante.

{{anchor|Run Sugar}}
== Correr Sugar ==

{{ Translated text | This command launches the Sugar emulator:

./sugar-jhbuild run

To exit the emulator, press Alt-Q. | display = None }}

Este comando lanza el emulador de Sugar

./sugar-jhbuild run

Para salir del emulador, presione Alt-Q.

{{anchor|Running multiple instances}}
== Corriendo múltiples instancias ==

{{Translated text | To run multiple instances of sugar you can start it in the following way:

SUGAR_PROFILE=2 ./sugar-jhbuild run

This will create a new profile in ~/.sugar/, i.e. ~/.sugar/2/. You will find logs and configuration for this instance here. The default profile is ~/.sugar/default/ | display = None }}

Para correr múltiples instancias de Sugar, puede lanzarlo de la manera siguiente:

SUGAR_PROFILE=2 ./sugar-jhbuild run

Esto creará un nuevo perfil en ~/.sugar/, o sea ~/.sugar/2/. Encontrará registros y configuración para esta instancia aquí. El perfil por omisión es ~/.sugar/default/

{{anchor|Run an individual activity}}
== Correr una actividad individual ==

{{Translated text |
Within sugar, e.g. in Terminal, this command launches an individual activity for testing:

sugar-launch [bundle name]

You will see debug output appearing in Terminal. | display = None }}

Dentro de Sugar, por ej, en Terminal, este comando lanza una actividad individual para probarla:

sugar-launch [nombre del bundle]

Verá salida de depuración apareciendo en Terminal.

{{ Anchor | Building specific version of Sugar }}

{{ Translated text |
To build a specific version of Sugar do the following:

* Open ''sugar.jhbuildrc'' and find line:
<pre>modulesets = 'sugar'</pre>
* Set this to:
<pre>modulesets = 'sugar-0.86'</pre>
customizing the latter to your specific needs.
* <code>./sugar-jhbuild</code>

=== Suggestions ===

* Copy all your sugar-jhbuild to sugar-jhbuild-0.84 (for example) or check the repositories out again.
* <pre>rm -r install/</pre>
* Don't forget to delete or modify ''.jhbuildrc'' after building the specific version of Sugar if you still want to receive the latest updates from the repositories, '''OR'''
* Create another user. }}

Para construir una versión específica de Sugar haz lo siguiente:

== Construir una versión específica de Sugar ==

* Abrí ''sugar.jhbuildrc'' y busca la línea empezando con:
<pre>modulesets = 'sugar'</pre>
* Cambiar esto a:
<pre>modulesets = 'sugar-0.86'</pre>
personalizando la versión de Sugar.
* Construir Sugar y sus dependencias: <code>./sugar-jhbuild</code>

=== Sugerencias ===

* Hacer una copia de ''sugar-jhbuild/'', llamando el la nueva carpeta ''sugar-jhbuild-0.84'', por ejemplo o obtener todos las dependencias otra vez.
* <pre>rm -r sugar-jhbuild/install/</pre>
* No olvidarse de borrar o modificar ''.jhbuildrc'' despues de construir la versión específica de Sugar para obtener todavía las actualizaciones más recientes de sugar-jhbuild O
* Crear otro usuario.

== Configurar el modo y la resolución de Sugar ==

{{Translated text | You can make Sugar run in a window as well as specify a resolution. Within the sugar-jhbuild/install/share/sugar/shell directory, backup, then edit the python program file '''emulator.py''':

cd sugar-jhbuild
cp install/bin/sugar-emulator install/bin/sugar-emulator.backup
nano install/bin/sugar-emulator

Find this piece of code: | display = None }}

Puede hacer que Sugar corra en una ventana como también especificar una resolución. Dentro del directorio sugar-jhbuild/install/share/sugar/shell, respalde y luego edite el programa python '''emulator.py''':

cd sugar-jhbuild
cp install/bin/sugar-emulator install/bin/sugar-emulator.backup
nano install/bin/sugar-emulato

Busque este pedazo de código:

<PRE>
cmd = [ 'Xephyr' ]
cmd.append(':%d' % display)
cmd.append('-ac')

if gtk.gdk.screen_width() < 1200 or gtk.gdk.screen_height() < 900:
cmd.append('-fullscreen')
else:
cmd.append('-screen')
cmd.append('%dx%d' % (1200, 900))
</PRE>

{{Translated text |
Comment out the '''if''' and '''else''' instructions, and specify the screen resolution and mode you want (it's important to delete 4 spaces before the "cmd.append" lines): | display = None}}

Comente las instrucciones '''if''' y '''else''', y especifique la resolución de la pantalla y el modo que desee (es ipmortante borrar 4 espacios delante de las líneas "cmd.append"):

<PRE>
cmd = [ 'Xephyr' ]
cmd.append(':%d' % display)
cmd.append('-ac')

# if gtk.gdk.screen_width() < 1200 or gtk.gdk.screen_height() < 900:
# cmd.append('-fullscreen')
# else:
cmd.append('-screen')
cmd.append('%dx%d' % (800, 600))
</PRE>

{{Translated text | Sugar will now run on a 800x600 window. This file may be replaced next time you update sugar-jhbuild, and you'll have to do this again. Also note that 800x600 is not an optimal resolution for the window, because the activity circle will be vertically off center. 1024x768 is a more useable resolution.
| display = None }}

Sugar ahora correrá en una ventana de 800x600. Este archivo puede ser reemplazado la próxima vez que actualize sugar-jhbuild, y deberá hacer esto nuevamente. También note que 800x600 no es una resolución óptima para la ventana, porque el círculo de actividades quedará descentrado verticalmente. 1024x768 es una resolución más usable.

{{anchor|Other commands}}
== Otras órdenes ==

{{Translated text |
JHBuild has several other commands that can be useful for development. You can get an overview with:

./sugar-jhbuild --help-commands

A useful sequence of commands for building Sugar, from the [http://mailman.laptop.org/pipermail/sugar/2007-February/001352.html Sugar mailing list]: (Note that build will update first anyway, so run update separately if you want to see what changed more easily.)

./sugar-jhbuild update
./sugar-jhbuild build
./sugar-jhbuild run | display = None}}

JHBuild tiene varias órdenes más que pueden ser útiles para el desarrollo. Puede obtener una descripción general con:

./sugar-jhbuild --help-commands

Una secuencia de comandos útil para construir Sugar, de la [http://mailman.laptop.org/pipermail/sugar/2007-February/001352.html Lista de distribución de correos de Sugar]: (Note que '''build''' corre '''update''' de todas maneras, así que corra '''update''' separadamente si quiere ver que cambió más fácilmente.)

./sugar-jhbuild update
./sugar-jhbuild build
./sugar-jhbuild run

{{anchor|If build breaks after an update}}
== Si la construcción se rompe luego de un update ==

{{Translated text |
The packages in sugar-jhbuild are the latest development versions, so you not only get the latest features, but also the latest breakages. The dependencies may change often, too, so be sure to run
./sugar-jhbuild depscheck
regularly and install the missing packages.

If your problem persists for more than a day (and even though you installed all missing packages), please [http://dev.sugarlabs.org/newticket?component=sugar-jhbuild&version=Git%20as%20of%20bugdate&type=defect&summary=%3cPlease%20enter%20short%20summary%20of%20your%20problem%20here%3e&description=%3cplease%20copy%20exact%20error%20message%20and%20additional%20information%20here%3e file a bug report]. | display = None }}

Los paquetes en sugar-jhbuild son las últimas versiones de desarrollo, así que no solamente obtiene las últimas prestaciones, si no que también los últimos errores. También, las dependencias pueden cambiar a menudo, así que asegúrese de correr
./sugar-jhbuild depscheck
regularmente y de instalar los paquetes faltantes.

{{anchor|From within Sugar}}
== Desde dentro de Sugar ==

{{Translated text | Once you have Sugar running, here are some useful commands:
*'''Alt+Shift+F''' makes the frame appear and disappear
*'''Ctrl-Q''' quits an activity
*'''Alt+Shift+Q''' quits Sugar
*'''Alt+Shift+O''' opens the search
*'''Alt+Shift+R''' rotates the screen | display = None }}

una vez que tenga Sugar corriendo, aquí hay algunas órdenes útiles:
*'''Alt+Shift+F''' hace aparecer y desaparecer al marco
*'''Ctrl-Q''' sale de una actividad
*'''Alt+Shift+Q''' sale de Sugar
*'''Alt+Shift+O''' abre la búsqueda
*'''Alt+Shift+R''' rota la pantalla

{{anchor|Customize}}
== Personalizar ==

{{Translated text |To customize the build create a configuration file, named ''.sugar.jhbuildrc'', in your home directory. | display = None }}
Para personalizar la construcción, cree un archivo de configuración, llamado ''.sugar.jhbuildrc'', en su directorio home.

{{anchor|Write access to the repositories}}
=== Acceso de escritura a los repositorios ===

{{Translated text |
If you have write access to the repositories you can add this (if your login name happens to be marco): | display = None }}

Si tiene acceso de escritura a los repositorios puede agregar esto (si su nombre de usuario fuera marco):
repos['gnome.org'] = ':ext:marco@cvs.gnome.org:/cvs/gnome'
repos['mozilla.org'] = ':ext:marco%gnome.org@cvs.mozilla.org:/cvsroot'
repos['dev.laptop.org'] = 'git+ssh://marco@dev.laptop.org/git/'
repos['dev.laptop.org/projects'] = 'git+ssh://marco@dev.laptop.org/git/projects/'

{{anchor|Useful Internal Links}}
== Enlaces internos útiles ==
{{Translated text | * [[Development Team/Understanding the Code|Understanding Sugar Code]]
* [[Taxonomy]] -- explains the components of Sugar (Glucose, Fructose, Sugar, Starches)
* [[Sugar Instructions]] -- how to actually use Sugar once you have it running | display = None }}

* [[Development Team/Understanding the Code/lang-es|Entendiendo el código de Sugar]]
* [[Taxonomy/lang-es|Taxonomía]] -- explica los componentes de Sugar (Glucosa, Fructosa, Azúcar (Sugar), Almidones)
* [[Sugar Instructions/lang-es|Instrucciones de Sugar]] -- cómo usar Sugar una vez que está corriendo

{{anchor|External links}}
== Enlaces externos ==

{{Translated text | * [http://library.gnome.org/devel/jhbuild/unstable/ JHBuild manual]
* [http://www.redhatmagazine.com/2007/02/23/building-the-xo-introducing-sugar/ Red Hat Magazine article: Introducing Sugar]
* [http://learn.laptop.org/tinderbox/ Tinderbox] (see the "Sugar JHBuild" tab). The old [http://dev.laptop.org/~cjb/sugar-tinder/ sugar-jhbuild tinderbox]. | display = None }}

* [http://library.gnome.org/devel/jhbuild/unstable/ Manual de JHBuild]
* [http://www.redhatmagazine.com/2007/02/23/building-the-xo-introducing-sugar/ Artículo de Red Hat Magazine: Presentando Sugar]
* [http://learn.laptop.org/tinderbox/ Tinderbox (Polvorín)] (ver la pestaña "Sugar JHBuild"). El viejo [http://dev.laptop.org/~cjb/sugar-tinder/ sugar-jhbuild tinderbox].

[[Category:Installing Sugar]]
[[Category:Jhbuild]]

Development Team/Jhbuild

2010-03-28T05:02:42Z

Km0r3: /* Building specific version of Sugar */

<noinclude>{{Translations}}{{TOCright}}</noinclude>

Sugar-jhbuild will automatically download the latest of Sugar's dependencies as well as Sugar itself directly from their source repositories, rather than relying on source packages that may have become stale.
It can also run a Sugar session in a window on your desktop using the [[wikipedia:Xephyr | Xephyr]] nested X window server.
Below are generic instructions on how to use jhbuild to get up and running with Sugar.

==Compatible platforms==

Jhbuild is quite demanding with regard to the packages and setup for the host Linux distribution. As a result there are only a few Linux distributions which are known to work with it.

See the distribution-specific instructions for information about whether your distribution is currently supported. Other distros which have a recent-enough release (e.g. including the latest stable GNOME release) can be supported if someone is willing to maintain the dependencies for that distro release (in config/sysdeps).

==Check distro-specific instructions==

Many distributions have some quirks that need to be catered for and there are different package managing tools in use, so please check the page for your distribution before proceeding:

* [[/Debian | Debian]]
* [[/Fedora | Fedora]] (some [http://www.youtube.com/profile?user=pleabargain&view=videos&query=jhbuild videos of the Fedora jhbuild install process]).
* [[/Ubuntu | Ubuntu]]
* [[/Mandriva | Mandriva]]

Distro packaging guidelines vary, so please don't worry if jhbuild requires twice/half the packages in one distro that it did an another.

==Some general advice==

Note: Like most other Unix applications, sugar-jhbuild should never be run as root. It may easily screw up your whole system and/or break in unexpected ways if you do. If you get any permissions error, there's something wrong with your installation that should be fixed.

If you're stuck or if you get strange errors, feel free to ask for help on the [[Sugar_Labs/Communication channels#irc.freenode.net_channels|#sugar IRC channel]] or the [[Sugar_Labs/Communication channels#Developer_Lists|sugar-devel mailing list]]. Don't waste too much time chasing strange problems: usually it's caused by some basic, easy to fix problem. You might also want to check the [https://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=sugar-jhbuild bug tracker] to see if it's a known issue.

==Prerequisites==
; python
: The sugar-jhbuild command is a Python script, so you need the Python interpreter.
; git
: To get the source code of sugar-jhbuild itself and many other Sugar packages you need the <code>git</code> command-line tool from the distributed version control system of the same name. In many distributions the minimal package you need to install is "git-core".
; svn
: A few packages (as of January 2010, only squeak and part of etoys) do not use git, and you need the <code>svn</code> command-line tool from the Subversion version control system to get their source code.

These should be enough to run sugar-jhbuild itself on a typical Linux installation. Running <code>sugar-jhbuild depscheck</code> (see below) will probably list dozens of additional required packages.

==Check out sugar-jhbuild==

In a suitable directory (i.e. usually your user's home directory i.e. /home/yourusername/~), execute
git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild

::Make sure you are in the _user's_ home directory
:: video http://www.youtube.com/watch?v=Tdr1bs4rQ_s

You'll know if it worked if you get something like this:
<pre>
localhost ~]$ git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild
Initialized empty Git repository in /home/denny/sugar-jhbuild/.git/
remote: Counting objects: 4688, done.
remote: Compressing objects: 100% (1998/1998), done.
remote: Total 4688 (delta 2759), reused 4488 (delta 2638)
Receiving objects: 100% (4688/4688), 1.86 MiB | 197 KiB/s, done.
Resolving deltas: 100% (2759/2759), done.
</pre>

==Build sugar base system and its dependencies==

Go into the directory you created and start the build. It takes about 30 minutes on a 1.6ghz machine with a wireless G connection.

cd sugar-jhbuild
./sugar-jhbuild update
./sugar-jhbuild depscheck
./sugar-jhbuild build
::[http://www.youtube.com/results?search_query=pleabargain+jhbuild&search_type=&aq=f Here are videos of the process].

And now run it.
./sugar-jhbuild run sugar-emulator

If it doesn't run or you have other problems read on.

=== Dealing with dependencies ===

''sugar-jhbuild depscheck'' will print a list of required packages. They are part of the distribution you're using and should be installed using your favourite package manager (e.g. aptitude/synaptic for Debian, yum for Fedora).

If you notice that there's a package missing from the <code>./sugar-jhbuild depscheck </code> output (i.e. it's required for Sugar to work properly and not installed, but depscheck does not mention it), please [https://bugs.sugarlabs.org/newticket?component=sugar-jhbuild&version=Git%20as%20of%20bugdate&type=defect&summary=Need%20package%20%3cinsert%20name%20of%20package%3e%20on%20%3cinsert%20name%20of%20distribution%3e&description=%3cplease%20explain%20why%20you%20think%20the%20package%20is%20required%20%28e.g.%20error%20message%29%3e file a bug report] (login required first, but currently no automatic redirection to login page) against the sugar-jhbuild Component in the [https://bugs.sugarlabs.org/ Sugar Labs bug tracker].

===Some tips===

A useful sequence of commands for building Sugar, from the [http://mailman.laptop.org/pipermail/sugar/2007-February/001352.html Sugar mailing list]: (Note that build without -n will update first anyway, so run update separately if you want to see what changed more easily.)

./sugar-jhbuild update
./sugar-jhbuild build -n -a --clean
./sugar-jhbuild run sugar-emulator

The use of -a and --clean flags are needed when a file is removed so that autogen.sh is run. '''Note:''' Some packages, e.g., squeak and etoys, don't have a ''make clean''. Just ignore the error.

=== known issue with hulahop ===

* hulahop stopped building because I had installed a more recent version of xulrunner on my machine. The workaround was to <code>rm -rf ~/sugar-jhbuild/source/hulahop</code> and then run update and build again.
*25 Aug 9: hulahop doesnt' build correctly. http://lists.sugarlabs.org/archive/sugar-devel/2009-August/018540.html The 'fix' is running autoconf.
::Question. How do you run autoconf to fix this problem?
::: when you get asked because of the error, choose the configure stage, or add "-a" to the build / buildone commands

=== If build breaks after an update ===

The packages in sugar-jhbuild are the latest development versions, so you not only get the latest features, but also the latest breakages. The dependencies may change often, too, so be sure to run
./sugar-jhbuild depscheck
regularly and install the missing packages.

If your problem persists for more than a day (and even though you installed all missing packages), please [https://bugs.sugarlabs.org/newticket?component=sugar-jhbuild&version=Git%20as%20of%20bugdate&type=defect&summary=%3cPlease%20enter%20short%20summary%20of%20your%20problem%20here%3e&description=%3cplease%20copy%20exact%20error%20message%20and%20additional%20information%20here%3e file a bug report].

== Run Sugar ==

This command launches the Sugar emulator in a nested X session:

./sugar-jhbuild run sugar-emulator

To exit the emulator, press Alt-Q.

To set debug variables, modify <code>~/.sugar/debug</code> (this file will be created on first run of Sugar).

Note that due to a [https://bugs.sugarlabs.org/ticket/342 bug in Xephyr] your keyboard might not work as expected. A partial workaround is to run <code>setxkbmap <keymap name></code> by adding this command line to <code>~/.sugar/debug</code>. Most "regular" keys should work fine after that, some "special keys" (e.g. cursor up/down) might still refuse to operate as intended.

The "keymap name" usually is a two letter country code, e.g. "de" for german or "fr" for french.

== Running multiple instances ==
To run an additional instance of sugar, you can start the second instance in the following way:

SUGAR_PROFILE=2 ./sugar-jhbuild run sugar-emulator

This will create a new profile in ~/.sugar/, i.e. ~/.sugar/2/. You will find logs and configuration for this instance here. The default profile is ~/.sugar/default/

== Run an individual activity ==

Within sugar, e.g. in Terminal, this command launches an individual activity for testing:

sugar-launch ''bundle_name''

You will see debug output appearing in Terminal.

== Configure the mode and resolution of Sugar ==

You can make Sugar run fullscreen or specify a size (in pixels):

./sugar-jhbuild run sugar-emulator --fullscreen
./sugar-jhbuild run sugar-emulator --dimensions 1200x900

The default size of 800x600 is currently the minimum that should work without issues. I.e. activities should be tested to work in this mode (and in others as well).

== Other commands ==

JHBuild has several other commands that can be useful for development. You can get an overview with:

./sugar-jhbuild --help-commands

== From within Sugar ==
Once you have Sugar running, here are some useful commands:
*'''Alt+Shift+F''' makes the frame appear and disappear
*'''Ctrl-Q''' quits an activity
*'''Alt+Shift+Q''' quits Sugar
*'''Alt+Shift+O''' opens the search
*'''Alt+Shift+R''' rotates the screen

== Customize ==

To customize the build you can modify the configuration file named <code>sugar.jhbuildrc</code> or create a copy of it and pass <code>--file /path/to/your/new/config</code> to sugar-jhbuild.

=== Write access to the repositories ===

If you have write access to the repositories you can add this (if your login name happens to be marco):
repos['gnome.org'] = ':ext:marco@cvs.gnome.org:/cvs/gnome'
repos['mozilla.org'] = ':ext:marco%gnome.org@cvs.mozilla.org:/cvsroot'
repos['dev.laptop.org'] = 'git+ssh://marco@dev.laptop.org/git/'
repos['dev.laptop.org/projects'] = 'git+ssh://marco@dev.laptop.org/git/projects/'

== Compiling using 2 or more CPU cores ==

Before running <code>./sugar-jhbuild build</code>, append this to <code>sugar.jhbuildrc</code>:

<pre>
os.environ["MAKEFLAGS"] = "-j4 -l4"
</pre>

Adjust the numbers to be twice the number of CPU cores in your machine.

== Using ccache to speed up rebuilds ==

To speed up full rebuilds of sugar-jhbuild (i.e. running <code>./sugar-jhbuild build</code> after removing the <code>source</code> directory) you can use [http://ccache.samba.org/ ccache]. Install it and append the following to <code>sugar.jhbuildrc</code>:

<pre>
os.environ["CCACHE_DIR"] = os.path.join(os.path.dirname(__file__), "ccache")
os.environ["PATH"] = "/usr/lib/ccache:"+os.environ["PATH"]
</pre>

Adjust <code>/usr/lib/ccache</code> to the path used by your distribution and create the <code>ccache</code> directory (inside your <code>sugar-jhbuild</code> checkout).

== Building specific version of Sugar ==

To build a specific version of Sugar do the following:

* Open ''sugar.jhbuildrc'' and find line:
<pre>modulesets = 'sugar'</pre>
* Set this to:
<pre>modulesets = 'sugar-0.86'</pre>
customizing the latter to your specific needs.
* Copy ''sugar.jhbuildrc'' to ''~/.jhbuildrc''
* <code>./sugar-jhbuild</code>

=== Suggestions ===

* Copy all your sugar-jhbuild to sugar-jhbuild-0.84 (for example) or check the repositories out again.
* <pre>rm -r install/</pre>
* Don't forget to delete or modify ''.jhbuildrc'' after building the specific version of Sugar if you still want to receive the latest updates from the repositories, '''OR'''
* Create another user.

==Useful Internal Links==
* [[Development Team/Understanding the Code|Understanding Sugar Code]]
* [[Taxonomy]] -- explains the components of Sugar (Glucose, Fructose, Sugar, Starches)
* [[Sugar Instructions]] -- how to actually use Sugar once you have it running[http://en.flossmanuals.net/sugar]

==External links==

* [http://library.gnome.org/devel/jhbuild/unstable/ JHBuild manual]
* [http://www.redhatmagazine.com/2007/02/23/building-the-xo-introducing-sugar/ Red Hat Magazine article: Introducing Sugar]

[[Category:Installing Sugar]]
[[Category:Jhbuild]]

User:Km0r3

2010-03-25T20:03:30Z

Km0r3: /* Application environment diagram */

User:Km0r3

2010-03-25T20:02:55Z

Km0r3: Application environment diagram to Notes section

== Contact details ==

Email: knny dot myer at gmail dot com

Blog: http://kenny.alwaysdata.net

[http://www.irchelp.org/irchelp/irctutorial.html irc]: km0r3 at [http://freenode.net FreeNode] (#sugar, #olpc-paraguay)

== Brief Bio ==

Kenny Meyer is currently volunteering to the OLPC Project.

He's a student from Paraguay where he's studying Computer Science.

He started programming with Python in 2008 and gained experience with the language writing Web Applications with Django [http://www.djangoproject.com] and Linux System Scripting.

If he's not busy programming he plays the guitar or helps Newbies in Linux forums or hangs out in IRC rooms. He also loves books and reads when not in reach of a computer.

== Notes ==

=== Sugar-specific ===

==== Reset XO Registration ====

rm -rf ~/.gconf/desktop/sugar

Source: http://wiki.laptop.org/go/Schoolserver_Testing

==== Application environment diagram ====

----------------------------------------------------------------
| | | | |
| | Non-python | Sugar shell | Python |
| | Sugar | (Desktop window, | Sugar |
| | Activities | panel, | Activities |
| Regular | (Etoys, | journal) | |
| X | Simcity, | | |
| Apps | Mono |--------------------------------------|
| | activities, | Sugar toolkit (python-only) |
| | etc.) | |
| |----------------------------------------------------|
| | DataStore | Presence |
| | service | service |
----------------------------------------------------------------
| Matchbox window manager |
| (considering switching to Metacity for improved compatibility) |
----------------------------------------------------------------
| |
| GNOME-ish Linux desktop |
| X11, HAL, D-Bus, NetworkManager, GConf, Telepathy, etc |
| |
----------------------------------------------------------------

Source: http://wiki.laptop.org/go/Software_components

User:Km0r3

2010-03-25T19:42:15Z

Km0r3: /* Contact details */

User:Km0r3

2010-03-25T19:40:13Z

Km0r3: /* Reset XO Registration */

User:Km0r3

2010-03-25T19:38:08Z

Km0r3: added Notes section

Development Team/Jhbuild

2010-03-25T00:32:24Z

Km0r3: /* Building specific version of Sugar */ added suggestions

<noinclude>{{Translations}}{{TOCright}}</noinclude>

Sugar-jhbuild will automatically download the latest of Sugar's dependencies as well as Sugar itself directly from their source repositories, rather than relying on source packages that may have become stale.
It can also run a Sugar session in a window on your desktop using the [[wikipedia:Xephyr | Xephyr]] nested X window server.
Below are generic instructions on how to use jhbuild to get up and running with Sugar.

==Compatible platforms==

Jhbuild is quite demanding with regard to the packages and setup for the host Linux distribution. As a result there are only a few Linux distributions which are known to work with it.

See the distribution-specific instructions for information about whether your distribution is currently supported. Other distros which have a recent-enough release (e.g. including the latest stable GNOME release) can be supported if someone is willing to maintain the dependencies for that distro release (in config/sysdeps).

==Check distro-specific instructions==

Many distributions have some quirks that need to be catered for and there are different package managing tools in use, so please check the page for your distribution before proceeding:

* [[/Debian | Debian]]
* [[/Fedora | Fedora]] (some [http://www.youtube.com/profile?user=pleabargain&view=videos&query=jhbuild videos of the Fedora jhbuild install process]).
* [[/Ubuntu | Ubuntu]]
* [[/Mandriva | Mandriva]]

Distro packaging guidelines vary, so please don't worry if jhbuild requires twice/half the packages in one distro that it did an another.

==Some general advice==

Note: Like most other Unix applications, sugar-jhbuild should never be run as root. It may easily screw up your whole system and/or break in unexpected ways if you do. If you get any permissions error, there's something wrong with your installation that should be fixed.

If you're stuck or if you get strange errors, feel free to ask for help on the [[Sugar_Labs/Communication channels#irc.freenode.net_channels|#sugar IRC channel]] or the [[Sugar_Labs/Communication channels#Developer_Lists|sugar-devel mailing list]]. Don't waste too much time chasing strange problems: usually it's caused by some basic, easy to fix problem. You might also want to check the [https://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=sugar-jhbuild bug tracker] to see if it's a known issue.

==Prerequisites==
; python
: The sugar-jhbuild command is a Python script, so you need the Python interpreter.
; git
: To get the source code of sugar-jhbuild itself and many other Sugar packages you need the <code>git</code> command-line tool from the distributed version control system of the same name. In many distributions the minimal package you need to install is "git-core".
; svn
: A few packages (as of January 2010, only squeak and part of etoys) do not use git, and you need the <code>svn</code> command-line tool from the Subversion version control system to get their source code.

These should be enough to run sugar-jhbuild itself on a typical Linux installation. Running <code>sugar-jhbuild depscheck</code> (see below) will probably list dozens of additional required packages.

==Check out sugar-jhbuild==

In a suitable directory (i.e. usually your user's home directory i.e. /home/yourusername/~), execute
git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild

::Make sure you are in the _user's_ home directory
:: video http://www.youtube.com/watch?v=Tdr1bs4rQ_s

You'll know if it worked if you get something like this:
<pre>
localhost ~]$ git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild
Initialized empty Git repository in /home/denny/sugar-jhbuild/.git/
remote: Counting objects: 4688, done.
remote: Compressing objects: 100% (1998/1998), done.
remote: Total 4688 (delta 2759), reused 4488 (delta 2638)
Receiving objects: 100% (4688/4688), 1.86 MiB | 197 KiB/s, done.
Resolving deltas: 100% (2759/2759), done.
</pre>

==Build sugar base system and its dependencies==

Go into the directory you created and start the build. It takes about 30 minutes on a 1.6ghz machine with a wireless G connection.

cd sugar-jhbuild
./sugar-jhbuild update
./sugar-jhbuild depscheck
./sugar-jhbuild build
::[http://www.youtube.com/results?search_query=pleabargain+jhbuild&search_type=&aq=f Here are videos of the process].

And now run it.
./sugar-jhbuild run sugar-emulator

If it doesn't run or you have other problems read on.

=== Dealing with dependencies ===

''sugar-jhbuild depscheck'' will print a list of required packages. They are part of the distribution you're using and should be installed using your favourite package manager (e.g. aptitude/synaptic for Debian, yum for Fedora).

If you notice that there's a package missing from the <code>./sugar-jhbuild depscheck </code> output (i.e. it's required for Sugar to work properly and not installed, but depscheck does not mention it), please [https://bugs.sugarlabs.org/newticket?component=sugar-jhbuild&version=Git%20as%20of%20bugdate&type=defect&summary=Need%20package%20%3cinsert%20name%20of%20package%3e%20on%20%3cinsert%20name%20of%20distribution%3e&description=%3cplease%20explain%20why%20you%20think%20the%20package%20is%20required%20%28e.g.%20error%20message%29%3e file a bug report] (login required first, but currently no automatic redirection to login page) against the sugar-jhbuild Component in the [https://bugs.sugarlabs.org/ Sugar Labs bug tracker].

===Some tips===

A useful sequence of commands for building Sugar, from the [http://mailman.laptop.org/pipermail/sugar/2007-February/001352.html Sugar mailing list]: (Note that build without -n will update first anyway, so run update separately if you want to see what changed more easily.)

./sugar-jhbuild update
./sugar-jhbuild build -n -a --clean
./sugar-jhbuild run sugar-emulator

The use of -a and --clean flags are needed when a file is removed so that autogen.sh is run. '''Note:''' Some packages, e.g., squeak and etoys, don't have a ''make clean''. Just ignore the error.

=== known issue with hulahop ===

* hulahop stopped building because I had installed a more recent version of xulrunner on my machine. The workaround was to <code>rm -rf ~/sugar-jhbuild/source/hulahop</code> and then run update and build again.
*25 Aug 9: hulahop doesnt' build correctly. http://lists.sugarlabs.org/archive/sugar-devel/2009-August/018540.html The 'fix' is running autoconf.
::Question. How do you run autoconf to fix this problem?
::: when you get asked because of the error, choose the configure stage, or add "-a" to the build / buildone commands

=== If build breaks after an update ===

The packages in sugar-jhbuild are the latest development versions, so you not only get the latest features, but also the latest breakages. The dependencies may change often, too, so be sure to run
./sugar-jhbuild depscheck
regularly and install the missing packages.

If your problem persists for more than a day (and even though you installed all missing packages), please [https://bugs.sugarlabs.org/newticket?component=sugar-jhbuild&version=Git%20as%20of%20bugdate&type=defect&summary=%3cPlease%20enter%20short%20summary%20of%20your%20problem%20here%3e&description=%3cplease%20copy%20exact%20error%20message%20and%20additional%20information%20here%3e file a bug report].

== Run Sugar ==

This command launches the Sugar emulator in a nested X session:

./sugar-jhbuild run sugar-emulator

To exit the emulator, press Alt-Q.

To set debug variables, modify <code>~/.sugar/debug</code> (this file will be created on first run of Sugar).

Note that due to a [https://bugs.sugarlabs.org/ticket/342 bug in Xephyr] your keyboard might not work as expected. A partial workaround is to run <code>setxkbmap <keymap name></code> by adding this command line to <code>~/.sugar/debug</code>. Most "regular" keys should work fine after that, some "special keys" (e.g. cursor up/down) might still refuse to operate as intended.

The "keymap name" usually is a two letter country code, e.g. "de" for german or "fr" for french.

== Running multiple instances ==
To run an additional instance of sugar, you can start the second instance in the following way:

SUGAR_PROFILE=2 ./sugar-jhbuild run sugar-emulator

This will create a new profile in ~/.sugar/, i.e. ~/.sugar/2/. You will find logs and configuration for this instance here. The default profile is ~/.sugar/default/

== Run an individual activity ==

Within sugar, e.g. in Terminal, this command launches an individual activity for testing:

sugar-launch ''bundle_name''

You will see debug output appearing in Terminal.

== Configure the mode and resolution of Sugar ==

You can make Sugar run fullscreen or specify a size (in pixels):

./sugar-jhbuild run sugar-emulator --fullscreen
./sugar-jhbuild run sugar-emulator --dimensions 1200x900

The default size of 800x600 is currently the minimum that should work without issues. I.e. activities should be tested to work in this mode (and in others as well).

== Other commands ==

JHBuild has several other commands that can be useful for development. You can get an overview with:

./sugar-jhbuild --help-commands

== From within Sugar ==
Once you have Sugar running, here are some useful commands:
*'''Alt+Shift+F''' makes the frame appear and disappear
*'''Ctrl-Q''' quits an activity
*'''Alt+Shift+Q''' quits Sugar
*'''Alt+Shift+O''' opens the search
*'''Alt+Shift+R''' rotates the screen

== Customize ==

To customize the build you can modify the configuration file named <code>sugar.jhbuildrc</code> or create a copy of it and pass <code>--file /path/to/your/new/config</code> to sugar-jhbuild.

=== Write access to the repositories ===

If you have write access to the repositories you can add this (if your login name happens to be marco):
repos['gnome.org'] = ':ext:marco@cvs.gnome.org:/cvs/gnome'
repos['mozilla.org'] = ':ext:marco%gnome.org@cvs.mozilla.org:/cvsroot'
repos['dev.laptop.org'] = 'git+ssh://marco@dev.laptop.org/git/'
repos['dev.laptop.org/projects'] = 'git+ssh://marco@dev.laptop.org/git/projects/'

== Compiling using 2 or more CPU cores ==

Before running <code>./sugar-jhbuild build</code>, append this to <code>sugar.jhbuildrc</code>:

<pre>
os.environ["MAKEFLAGS"] = "-j4 -l4"
</pre>

Adjust the numbers to be twice the number of CPU cores in your machine.

== Using ccache to speed up rebuilds ==

To speed up full rebuilds of sugar-jhbuild (i.e. running <code>./sugar-jhbuild build</code> after removing the <code>source</code> directory) you can use [http://ccache.samba.org/ ccache]. Install it and append the following to <code>sugar.jhbuildrc</code>:

<pre>
os.environ["CCACHE_DIR"] = os.path.join(os.path.dirname(__file__), "ccache")
os.environ["PATH"] = "/usr/lib/ccache:"+os.environ["PATH"]
</pre>

Adjust <code>/usr/lib/ccache</code> to the path used by your distribution and create the <code>ccache</code> directory (inside your <code>sugar-jhbuild</code> checkout).

== Building specific version of Sugar ==

To build a specific version of Sugar do the following:

* Open ''sugar.jhbuildrc'' and find line:
<pre>modulesets = 'sugar'</pre>
* Set this to:
<pre>modulesets = 'sugar-0.86'</pre>
customizing the latter to your specific needs.
* Copy ''sugar.jhbuildrc'' to ''~/.jhbuildrc''
* ./sugar-jhbuild

=== Suggestions ===

* Copy all your sugar-jhbuild to sugar-jhbuild-0.84 (for example) or check the repositories out again.
* <pre>rm -r install/</pre>
* Don't forget to delete or modify ''.jhbuildrc'' after building the specific version of Sugar if you still want to receive the latest updates from the repositories, '''OR'''
* Create another user.

==Useful Internal Links==
* [[Development Team/Understanding the Code|Understanding Sugar Code]]
* [[Taxonomy]] -- explains the components of Sugar (Glucose, Fructose, Sugar, Starches)
* [[Sugar Instructions]] -- how to actually use Sugar once you have it running[http://en.flossmanuals.net/sugar]

==External links==

* [http://library.gnome.org/devel/jhbuild/unstable/ JHBuild manual]
* [http://www.redhatmagazine.com/2007/02/23/building-the-xo-introducing-sugar/ Red Hat Magazine article: Introducing Sugar]

[[Category:Installing Sugar]]
[[Category:Jhbuild]]

Development Team/Jhbuild

2010-03-25T00:14:14Z

Km0r3:

<noinclude>{{Translations}}{{TOCright}}</noinclude>

Sugar-jhbuild will automatically download the latest of Sugar's dependencies as well as Sugar itself directly from their source repositories, rather than relying on source packages that may have become stale.
It can also run a Sugar session in a window on your desktop using the [[wikipedia:Xephyr | Xephyr]] nested X window server.
Below are generic instructions on how to use jhbuild to get up and running with Sugar.

==Compatible platforms==

Jhbuild is quite demanding with regard to the packages and setup for the host Linux distribution. As a result there are only a few Linux distributions which are known to work with it.

See the distribution-specific instructions for information about whether your distribution is currently supported. Other distros which have a recent-enough release (e.g. including the latest stable GNOME release) can be supported if someone is willing to maintain the dependencies for that distro release (in config/sysdeps).

==Check distro-specific instructions==

Many distributions have some quirks that need to be catered for and there are different package managing tools in use, so please check the page for your distribution before proceeding:

* [[/Debian | Debian]]
* [[/Fedora | Fedora]] (some [http://www.youtube.com/profile?user=pleabargain&view=videos&query=jhbuild videos of the Fedora jhbuild install process]).
* [[/Ubuntu | Ubuntu]]
* [[/Mandriva | Mandriva]]

Distro packaging guidelines vary, so please don't worry if jhbuild requires twice/half the packages in one distro that it did an another.

==Some general advice==

Note: Like most other Unix applications, sugar-jhbuild should never be run as root. It may easily screw up your whole system and/or break in unexpected ways if you do. If you get any permissions error, there's something wrong with your installation that should be fixed.

If you're stuck or if you get strange errors, feel free to ask for help on the [[Sugar_Labs/Communication channels#irc.freenode.net_channels|#sugar IRC channel]] or the [[Sugar_Labs/Communication channels#Developer_Lists|sugar-devel mailing list]]. Don't waste too much time chasing strange problems: usually it's caused by some basic, easy to fix problem. You might also want to check the [https://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=sugar-jhbuild bug tracker] to see if it's a known issue.

==Prerequisites==
; python
: The sugar-jhbuild command is a Python script, so you need the Python interpreter.
; git
: To get the source code of sugar-jhbuild itself and many other Sugar packages you need the <code>git</code> command-line tool from the distributed version control system of the same name. In many distributions the minimal package you need to install is "git-core".
; svn
: A few packages (as of January 2010, only squeak and part of etoys) do not use git, and you need the <code>svn</code> command-line tool from the Subversion version control system to get their source code.

These should be enough to run sugar-jhbuild itself on a typical Linux installation. Running <code>sugar-jhbuild depscheck</code> (see below) will probably list dozens of additional required packages.

==Check out sugar-jhbuild==

In a suitable directory (i.e. usually your user's home directory i.e. /home/yourusername/~), execute
git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild

::Make sure you are in the _user's_ home directory
:: video http://www.youtube.com/watch?v=Tdr1bs4rQ_s

You'll know if it worked if you get something like this:
<pre>
localhost ~]$ git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild
Initialized empty Git repository in /home/denny/sugar-jhbuild/.git/
remote: Counting objects: 4688, done.
remote: Compressing objects: 100% (1998/1998), done.
remote: Total 4688 (delta 2759), reused 4488 (delta 2638)
Receiving objects: 100% (4688/4688), 1.86 MiB | 197 KiB/s, done.
Resolving deltas: 100% (2759/2759), done.
</pre>

==Build sugar base system and its dependencies==

Go into the directory you created and start the build. It takes about 30 minutes on a 1.6ghz machine with a wireless G connection.

cd sugar-jhbuild
./sugar-jhbuild update
./sugar-jhbuild depscheck
./sugar-jhbuild build
::[http://www.youtube.com/results?search_query=pleabargain+jhbuild&search_type=&aq=f Here are videos of the process].

And now run it.
./sugar-jhbuild run sugar-emulator

If it doesn't run or you have other problems read on.

=== Dealing with dependencies ===

''sugar-jhbuild depscheck'' will print a list of required packages. They are part of the distribution you're using and should be installed using your favourite package manager (e.g. aptitude/synaptic for Debian, yum for Fedora).

If you notice that there's a package missing from the <code>./sugar-jhbuild depscheck </code> output (i.e. it's required for Sugar to work properly and not installed, but depscheck does not mention it), please [https://bugs.sugarlabs.org/newticket?component=sugar-jhbuild&version=Git%20as%20of%20bugdate&type=defect&summary=Need%20package%20%3cinsert%20name%20of%20package%3e%20on%20%3cinsert%20name%20of%20distribution%3e&description=%3cplease%20explain%20why%20you%20think%20the%20package%20is%20required%20%28e.g.%20error%20message%29%3e file a bug report] (login required first, but currently no automatic redirection to login page) against the sugar-jhbuild Component in the [https://bugs.sugarlabs.org/ Sugar Labs bug tracker].

===Some tips===

A useful sequence of commands for building Sugar, from the [http://mailman.laptop.org/pipermail/sugar/2007-February/001352.html Sugar mailing list]: (Note that build without -n will update first anyway, so run update separately if you want to see what changed more easily.)

./sugar-jhbuild update
./sugar-jhbuild build -n -a --clean
./sugar-jhbuild run sugar-emulator

The use of -a and --clean flags are needed when a file is removed so that autogen.sh is run. '''Note:''' Some packages, e.g., squeak and etoys, don't have a ''make clean''. Just ignore the error.

=== known issue with hulahop ===

* hulahop stopped building because I had installed a more recent version of xulrunner on my machine. The workaround was to <code>rm -rf ~/sugar-jhbuild/source/hulahop</code> and then run update and build again.
*25 Aug 9: hulahop doesnt' build correctly. http://lists.sugarlabs.org/archive/sugar-devel/2009-August/018540.html The 'fix' is running autoconf.
::Question. How do you run autoconf to fix this problem?
::: when you get asked because of the error, choose the configure stage, or add "-a" to the build / buildone commands

=== If build breaks after an update ===

The packages in sugar-jhbuild are the latest development versions, so you not only get the latest features, but also the latest breakages. The dependencies may change often, too, so be sure to run
./sugar-jhbuild depscheck
regularly and install the missing packages.

If your problem persists for more than a day (and even though you installed all missing packages), please [https://bugs.sugarlabs.org/newticket?component=sugar-jhbuild&version=Git%20as%20of%20bugdate&type=defect&summary=%3cPlease%20enter%20short%20summary%20of%20your%20problem%20here%3e&description=%3cplease%20copy%20exact%20error%20message%20and%20additional%20information%20here%3e file a bug report].

== Run Sugar ==

This command launches the Sugar emulator in a nested X session:

./sugar-jhbuild run sugar-emulator

To exit the emulator, press Alt-Q.

To set debug variables, modify <code>~/.sugar/debug</code> (this file will be created on first run of Sugar).

Note that due to a [https://bugs.sugarlabs.org/ticket/342 bug in Xephyr] your keyboard might not work as expected. A partial workaround is to run <code>setxkbmap <keymap name></code> by adding this command line to <code>~/.sugar/debug</code>. Most "regular" keys should work fine after that, some "special keys" (e.g. cursor up/down) might still refuse to operate as intended.

The "keymap name" usually is a two letter country code, e.g. "de" for german or "fr" for french.

== Running multiple instances ==
To run an additional instance of sugar, you can start the second instance in the following way:

SUGAR_PROFILE=2 ./sugar-jhbuild run sugar-emulator

This will create a new profile in ~/.sugar/, i.e. ~/.sugar/2/. You will find logs and configuration for this instance here. The default profile is ~/.sugar/default/

== Run an individual activity ==

Within sugar, e.g. in Terminal, this command launches an individual activity for testing:

sugar-launch ''bundle_name''

You will see debug output appearing in Terminal.

== Configure the mode and resolution of Sugar ==

You can make Sugar run fullscreen or specify a size (in pixels):

./sugar-jhbuild run sugar-emulator --fullscreen
./sugar-jhbuild run sugar-emulator --dimensions 1200x900

The default size of 800x600 is currently the minimum that should work without issues. I.e. activities should be tested to work in this mode (and in others as well).

== Other commands ==

JHBuild has several other commands that can be useful for development. You can get an overview with:

./sugar-jhbuild --help-commands

== From within Sugar ==
Once you have Sugar running, here are some useful commands:
*'''Alt+Shift+F''' makes the frame appear and disappear
*'''Ctrl-Q''' quits an activity
*'''Alt+Shift+Q''' quits Sugar
*'''Alt+Shift+O''' opens the search
*'''Alt+Shift+R''' rotates the screen

== Customize ==

To customize the build you can modify the configuration file named <code>sugar.jhbuildrc</code> or create a copy of it and pass <code>--file /path/to/your/new/config</code> to sugar-jhbuild.

=== Write access to the repositories ===

If you have write access to the repositories you can add this (if your login name happens to be marco):
repos['gnome.org'] = ':ext:marco@cvs.gnome.org:/cvs/gnome'
repos['mozilla.org'] = ':ext:marco%gnome.org@cvs.mozilla.org:/cvsroot'
repos['dev.laptop.org'] = 'git+ssh://marco@dev.laptop.org/git/'
repos['dev.laptop.org/projects'] = 'git+ssh://marco@dev.laptop.org/git/projects/'

== Compiling using 2 or more CPU cores ==

Before running <code>./sugar-jhbuild build</code>, append this to <code>sugar.jhbuildrc</code>:

<pre>
os.environ["MAKEFLAGS"] = "-j4 -l4"
</pre>

Adjust the numbers to be twice the number of CPU cores in your machine.

== Using ccache to speed up rebuilds ==

To speed up full rebuilds of sugar-jhbuild (i.e. running <code>./sugar-jhbuild build</code> after removing the <code>source</code> directory) you can use [http://ccache.samba.org/ ccache]. Install it and append the following to <code>sugar.jhbuildrc</code>:

<pre>
os.environ["CCACHE_DIR"] = os.path.join(os.path.dirname(__file__), "ccache")
os.environ["PATH"] = "/usr/lib/ccache:"+os.environ["PATH"]
</pre>

Adjust <code>/usr/lib/ccache</code> to the path used by your distribution and create the <code>ccache</code> directory (inside your <code>sugar-jhbuild</code> checkout).

== Building specific version of Sugar ==

To build a specific version of Sugar do the following:

* Open ''sugar.jhbuildrc'' and find line:
<pre>modulesets = 'sugar'</pre>
* Set this to:
<pre>modulesets = 'sugar-0.86'</pre>
customizing the latter to your specific needs.
* Copy ''sugar.jhbuildrc'' to ''~/.jhbuildrc''
* ./sugar-jhbuild

==Useful Internal Links==
* [[Development Team/Understanding the Code|Understanding Sugar Code]]
* [[Taxonomy]] -- explains the components of Sugar (Glucose, Fructose, Sugar, Starches)
* [[Sugar Instructions]] -- how to actually use Sugar once you have it running[http://en.flossmanuals.net/sugar]

==External links==

* [http://library.gnome.org/devel/jhbuild/unstable/ JHBuild manual]
* [http://www.redhatmagazine.com/2007/02/23/building-the-xo-introducing-sugar/ Red Hat Magazine article: Introducing Sugar]

[[Category:Installing Sugar]]
[[Category:Jhbuild]]

User:Km0r3

2010-03-16T23:49:54Z

Km0r3:

User:Km0r3

2010-03-16T23:47:31Z

Km0r3:

== km0r3 ==

Email: knny dot myer at gmail dot com

Blog: http://kenny.alwaysdata.net

[http://www.irchelp.org/irchelp/irctutorial.html irc]: km0r3 at [http://freenode.net FreeNode] (#sugar)

=== Brief bio ===

Kenny Meyer is currently volunteering to the OLPC Project.

He's a student from Paraguay where he's studying Computer Science.

He started programming with Python in 2008 and gained experience with the language writing Web Applications with Django [http://www.djangoproject.com] and Linux System Scripting.

If he's not busy programming he plays the guitar or helps Newbies in Linux forums or hangs out in IRC rooms. He also loves books and reads when not in reach of a computer.

User:Km0r3

2010-03-16T14:11:44Z

Km0r3:

email: knny dot myer at gmail dot com
Blog: http://kenny.alwaysdata.net

[http://www.irchelp.org/irchelp/irctutorial.html irc]: km0r3 at [http://freenode.net FreeNode] (#sugar)

=== Brief bio ===

Kenny Meyer is currently volunteering to the OLPC Project.

He's a student from Paraguay where he's studying Computer Science.

He started programming with Python in 2008 and gained experience with the language writing Web Applications with Django [http://www.djangoproject.com] and Linux System Scripting.

If he's not busy programming he plays the guitar or helps Newbies in Linux forums or hangs out in IRC rooms. He also loves books and reads when not in reach of a computer.

User:Km0r3

2010-03-16T14:11:25Z

Km0r3: Created page with 'email: knny dot myer at gmail dot com Blog: http://kenny.alwaysdata.net [http://www.irchelp.org/irchelp/irctutorial.html irc]: km0r3 at [http://freenode.net FreeNode] (#sugar) …'

email: knny dot myer at gmail dot com
Blog: http://kenny.alwaysdata.net

[http://www.irchelp.org/irchelp/irctutorial.html irc]: km0r3 at [http://freenode.net FreeNode] (#sugar)

=== Brief bio ===

Kenny Meyer is currently volunteering to the OLPC Project. He's a student from Paraguay where he's studying Computer Science.

He started programming with Python in 2008 and gained experience with the language writing Web Applications with Django [http://www.djangoproject.com] and Linux System Scripting.

If he's not busy programming he plays the guitar or helps Newbies in Linux forums or hangs out in IRC rooms. He also loves books and reads when not in reach of a computer.