https://wiki.sugarlabs.org/api.php?action=feedcontributions&user=Aa&feedformat=atomSugar Labs - User contributions [en]2024-03-29T11:57:01ZUser contributionsMediaWiki 1.35.2https://wiki.sugarlabs.org/index.php?title=EduJAM/2011/Code_Sprint&diff=64151EduJAM/2011/Code Sprint2011-03-30T16:09:57Z<p>Aa: </p>
<hr />
<div>== Sugar Code Sprint after eduJAM! 2011 ==<br />
In Montevideo, right after the [[http://ceibaljam.org/?q=edujam2011_en|eduJAM! 2011]] we'll have a Sugar Code Sprint, to work on deployment needs detected during the summit.<br />
<br />
This is part of [[Sugar Camp Q2 2011]].<br />
<br />
Confirmed participants:<br />
* Martín Abente, Paraguay<br />
* Chris Ball, Boston<br />
* Walter Bender, USA<br />
* David Farning, USA<br />
* Pablo Flores, Uruguay<br />
* Aleksey Lim, Russia<br />
* Anish Mangal, India/Paraguay<br />
* Andrés Ambrois, Uruguay<br />
<br />
<br />
Unconfirmed participants:<br />
* CScott Ananian, Boston<br />
* Tony Anderson, Texas/Rwanda<br />
* Esteban Arias, Uruguay<br />
* Esteban Bordón, Uruguay<br />
* Daniel Castelo, Uruguay<br />
* Nick Doiron, New Hampshire<br />
* Gabriel Eirea, Uruguay<br />
* Bernie Innocenti, Italy/USA<br />
* Martin Langhoff, Miami<br />
* Gonzalo Odiard, Argentina<br />
* Rafael Ortiz, Colombia<br />
* Fernando Sansberro, Uruguay<br />
* Sebastián Silva, Colombia/ Perú<br />
* Simon Schampijer, Germany<br />
* Tomeu Vizoso, Spain<br />
<br />
<br />
Who knows...<br />
* Daniel Drake, UK<br />
* Rabi Karmacharya, Nepal</div>Aahttps://wiki.sugarlabs.org/index.php?title=EduJAM/2011&diff=62953EduJAM/20112011-03-04T19:57:01Z<p>Aa: /* Assistants */</p>
<hr />
<div>This page is for planning the summit to be taken in Uruguay on May 5th to 7th 2011.<br />
'''All subject to modifications'''.<br />
<br />
== Main goals ==<br />
* '''Focus on developers'''. It does not mean at all we're not concerned about educational aspects, but as a developers community we have huge challenges and the summit will be more of a working instance than a "reflection" instance.<br />
* '''Exceed OLPC and Sugar'''. The developers community goes beyond OLPC and Sugar, and this could be a good instance for bringing "non-olpc organizations" to the conversation. <br />
* '''Focus on South America'''. Bring as many south american developers as possible to Uruguay.<br />
<br />
== Assistants ==<br />
* Martín Abente<br />
* Walter Bender<br />
* Gabriel Eirea<br />
* David Farning<br />
* Pablo Flores<br />
* Adam Holt<br />
* Bernie Innocenti<br />
* Anish Mangal<br />
* Gonzalo Odiard<br />
* [[User:aa|Andrés Ambrois]]<br />
<br />
== Other activities ==<br />
We're organizing a set of activities for those who want to know more about Uruguayan experience, visiting different points of the country, meeting with families, teachers, etc. <br />
It will be in the week prior to the summit: April 3th to May 5th.<br />
More information soon. <br />
<br />
== Acoomodation ==<br />
We'll put here some information about possible places for staying. At the same time we'll make a volunteers hosting program, so Uruguayan volunteers can host some of the attendees. More information soon. <br />
<br />
== Uruguay ==<br />
Touristic information: http://www.turismo.gub.uy/<br />
Direct flights to Montevideo (Carrasco Airport) from: <br />
* US: Miami<br />
* Europe: Madrid<br />
* Most of South America<br />
* Nearby hubs: Buenos Aires, Sao Paulo, Santiago<br />
There are also nice ferries from Buenos Aires: http://buquebus.com</div>Aahttps://wiki.sugarlabs.org/index.php?title=Features/Journal_Sort&diff=56448Features/Journal Sort2010-09-04T00:17:53Z<p>Aa: /* Release Notes */</p>
<hr />
<div><noinclude>{{TOCright}}<br />
[[Category:Feature Accepted 0.90]]<br />
[[Category:Feature|Journal Sorting]]<br />
</noinclude><br />
<br />
== Summary ==<br />
Implements sorting in the Journal UI as described in [[Design_Team/Proposals/Journal#Extended_list_view_palette|this Design Proposal]]. Also adds support for the two new properties (filesize and ctime) to the datastore.<br />
<br />
== Owner ==<br />
* Name: [[User:aa| Andrés Ambrois]]<br />
<br />
* Email: <andresambrois@gmail.com><br />
<br />
== Current status ==<br />
* Targeted release: 0.90<br />
* Last updated: 06/06/10<br />
* Percentage of completion: 100%<br />
<br />
== Detailed Description ==<br />
This feature adds a ToolButton to the Journal toolbar. In its palette, the user can select the following sorting criteria: "Sort by file size", "Sort by last edit", "Sort by creation date".<br />
<br />
== Benefit to Sugar ==<br />
Sorting by filesize is vital in the field where users need to free up disk space. Currently, the only way to find candidates for deletion is to access the expanded view of each entry, one by one. This can be a very time consuming process and often leads to indiscriminate deletion and thus potential loss of valuable data. This is bad.<br />
<br />
Sorting by creation time (ctime) is also implemented as described in the Design<br />
Proposal.<br />
<br />
This feature was requested in [http://bugs.sugarlabs.org/ticket/1915 SL1915] and sponsored by [http://activitycentral.org Activity Central].<br />
<br />
== Scope ==<br />
* Add support for ctime and filesize to the datastore (DONE)<br />
* Implement sorting in the Journal (DONE)<br />
* Add new icons to sugar-artwork (DONE)<br />
<br />
==UI Design==<br />
Please see [[Design_Team/Proposals/Journal#Extended_list_view_palette|the Design Proposal]].<br />
<br />
<gallery><br />
Image:Journal-sort1.png|Sort palette<br />
Image:Journal-sort2.png|Sorting by file size<br />
</gallery><br />
<br />
== How To Test ==<br />
{{:{{PAGENAME}}/Testing}}<br />
== User Experience ==<br />
''If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.''<br />
<br />
== Dependencies ==<br />
None<br />
<br />
== Contingency Plan ==<br />
None necessary, revert to previous release behaviour.<br />
<br />
== Implementation ==<br />
<br />
sugar commits:<br />
<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/780eed1a3871f0cd47cdc06a655782a90eee28ea<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/4c2d26ccaeb502037484ced70b5944e3e20aa3f6<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/a4efed250c56dc6dd656bafb572a1a56e034d254<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/2c90107e36448d00dbe5a64f70024d003e7e531b<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/532594bb856c96e13462e7825187551c940d41f2<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/bc1edfa2193ca554d385c68e43c2cef0b9795a54<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/dbcd0223a87815d3b0d8c79061046d52c4418922<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/addd33e5963f27996fed46f0a34ccc4f4a0c796c<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/0a69741474c775c2dba92e527a94db9b86c27722<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/b1a05110a85ea6d1ba55cd75ccdfcb509c12276c<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/6099b087c80d7fb80856d4e157f8743ce74ec922<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/48c2eeaf5d3007f0970a0f31745efe22063c4465<br />
<br />
sugar-datastore commits:<br />
<br />
http://git.sugarlabs.org/projects/sugar-datastore/repos/mainline/commits/089ba387eafec10734ce3023665a163c531b82b4<br />
http://git.sugarlabs.org/projects/sugar-datastore/repos/mainline/commits/f3f71c3dad6fdf3b69b3624a6a584002c4c4fb28<br />
http://git.sugarlabs.org/projects/sugar-datastore/repos/mainline/commits/faa9974381f5ad70307e6c394d096b56134391e7<br />
http://git.sugarlabs.org/projects/sugar-datastore/repos/mainline/commits/7475a1fe38fca3ee4491bc272a59693805136f1e<br />
http://git.sugarlabs.org/projects/sugar-datastore/repos/mainline/commits/19845394f5f74f67e32192e3a09ce396522329bd<br />
<br />
sugar-artwork commits:<br />
<br />
http://git.sugarlabs.org/projects/sugar-artwork/repos/mainline/commits/55a2fe370eb22ac042ac1c4670f8fa3a111c8f38<br />
<br />
== Documentation ==<br />
[http://lists.sugarlabs.org/archive/sugar-devel/2010-May/023664.html Initial submission to sugar-devel (Sugar patches)]<br />
<br />
[http://lists.sugarlabs.org/archive/sugar-devel/2010-May/023658.html Initial submission to sugar-devel (DS patches)]<br />
<br />
<br />
[http://lists.sugarlabs.org/archive/sugar-devel/2010-May/024089.html Second submission to sugar-devel (Sugar patches)]<br />
<br />
[http://lists.sugarlabs.org/archive/sugar-devel/2010-May/024083.html Second submission to sugar-devel (DS patches)]<br />
<br />
[http://lists.sugarlabs.org/archive/sugar-devel/2010-May/024199.html Icons]<br />
<br />
== Release Notes ==<br />
A new menu has been added to the Journal to choose from various sorting options.<br />
<br />
[[File:Journal_sorting_options2.png]]<br />
<br />
Users can now select one of "Date modified", "Date created" and "Size" to sort their journal entries. In each case, the last column will change to display the selected property.<br />
<br />
== Comments and Discussion ==<br />
* See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page. --></div>Aahttps://wiki.sugarlabs.org/index.php?title=Features/Journal_Sort&diff=56447Features/Journal Sort2010-09-04T00:04:57Z<p>Aa: /* Release Notes */</p>
<hr />
<div><noinclude>{{TOCright}}<br />
[[Category:Feature Accepted 0.90]]<br />
[[Category:Feature|Journal Sorting]]<br />
</noinclude><br />
<br />
== Summary ==<br />
Implements sorting in the Journal UI as described in [[Design_Team/Proposals/Journal#Extended_list_view_palette|this Design Proposal]]. Also adds support for the two new properties (filesize and ctime) to the datastore.<br />
<br />
== Owner ==<br />
* Name: [[User:aa| Andrés Ambrois]]<br />
<br />
* Email: <andresambrois@gmail.com><br />
<br />
== Current status ==<br />
* Targeted release: 0.90<br />
* Last updated: 06/06/10<br />
* Percentage of completion: 100%<br />
<br />
== Detailed Description ==<br />
This feature adds a ToolButton to the Journal toolbar. In its palette, the user can select the following sorting criteria: "Sort by file size", "Sort by last edit", "Sort by creation date".<br />
<br />
== Benefit to Sugar ==<br />
Sorting by filesize is vital in the field where users need to free up disk space. Currently, the only way to find candidates for deletion is to access the expanded view of each entry, one by one. This can be a very time consuming process and often leads to indiscriminate deletion and thus potential loss of valuable data. This is bad.<br />
<br />
Sorting by creation time (ctime) is also implemented as described in the Design<br />
Proposal.<br />
<br />
This feature was requested in [http://bugs.sugarlabs.org/ticket/1915 SL1915] and sponsored by [http://activitycentral.org Activity Central].<br />
<br />
== Scope ==<br />
* Add support for ctime and filesize to the datastore (DONE)<br />
* Implement sorting in the Journal (DONE)<br />
* Add new icons to sugar-artwork (DONE)<br />
<br />
==UI Design==<br />
Please see [[Design_Team/Proposals/Journal#Extended_list_view_palette|the Design Proposal]].<br />
<br />
<gallery><br />
Image:Journal-sort1.png|Sort palette<br />
Image:Journal-sort2.png|Sorting by file size<br />
</gallery><br />
<br />
== How To Test ==<br />
{{:{{PAGENAME}}/Testing}}<br />
== User Experience ==<br />
''If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.''<br />
<br />
== Dependencies ==<br />
None<br />
<br />
== Contingency Plan ==<br />
None necessary, revert to previous release behaviour.<br />
<br />
== Implementation ==<br />
<br />
sugar commits:<br />
<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/780eed1a3871f0cd47cdc06a655782a90eee28ea<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/4c2d26ccaeb502037484ced70b5944e3e20aa3f6<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/a4efed250c56dc6dd656bafb572a1a56e034d254<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/2c90107e36448d00dbe5a64f70024d003e7e531b<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/532594bb856c96e13462e7825187551c940d41f2<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/bc1edfa2193ca554d385c68e43c2cef0b9795a54<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/dbcd0223a87815d3b0d8c79061046d52c4418922<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/addd33e5963f27996fed46f0a34ccc4f4a0c796c<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/0a69741474c775c2dba92e527a94db9b86c27722<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/b1a05110a85ea6d1ba55cd75ccdfcb509c12276c<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/6099b087c80d7fb80856d4e157f8743ce74ec922<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/48c2eeaf5d3007f0970a0f31745efe22063c4465<br />
<br />
sugar-datastore commits:<br />
<br />
http://git.sugarlabs.org/projects/sugar-datastore/repos/mainline/commits/089ba387eafec10734ce3023665a163c531b82b4<br />
http://git.sugarlabs.org/projects/sugar-datastore/repos/mainline/commits/f3f71c3dad6fdf3b69b3624a6a584002c4c4fb28<br />
http://git.sugarlabs.org/projects/sugar-datastore/repos/mainline/commits/faa9974381f5ad70307e6c394d096b56134391e7<br />
http://git.sugarlabs.org/projects/sugar-datastore/repos/mainline/commits/7475a1fe38fca3ee4491bc272a59693805136f1e<br />
http://git.sugarlabs.org/projects/sugar-datastore/repos/mainline/commits/19845394f5f74f67e32192e3a09ce396522329bd<br />
<br />
sugar-artwork commits:<br />
<br />
http://git.sugarlabs.org/projects/sugar-artwork/repos/mainline/commits/55a2fe370eb22ac042ac1c4670f8fa3a111c8f38<br />
<br />
== Documentation ==<br />
[http://lists.sugarlabs.org/archive/sugar-devel/2010-May/023664.html Initial submission to sugar-devel (Sugar patches)]<br />
<br />
[http://lists.sugarlabs.org/archive/sugar-devel/2010-May/023658.html Initial submission to sugar-devel (DS patches)]<br />
<br />
<br />
[http://lists.sugarlabs.org/archive/sugar-devel/2010-May/024089.html Second submission to sugar-devel (Sugar patches)]<br />
<br />
[http://lists.sugarlabs.org/archive/sugar-devel/2010-May/024083.html Second submission to sugar-devel (DS patches)]<br />
<br />
[http://lists.sugarlabs.org/archive/sugar-devel/2010-May/024199.html Icons]<br />
<br />
== Release Notes ==<br />
A new menu has been added to the Journal to choose from various sorting options.<br />
<br />
[[File:Journal_sorting_options2.png]]<br />
<br />
Users can now select one of "Date modified", "Date created" and "Size" to sort their journal entries.<br />
<br />
== Comments and Discussion ==<br />
* See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page. --></div>Aahttps://wiki.sugarlabs.org/index.php?title=File:Journal_sorting_options2.png&diff=56446File:Journal sorting options2.png2010-09-04T00:04:47Z<p>Aa: Journal sorting options</p>
<hr />
<div>Journal sorting options</div>Aahttps://wiki.sugarlabs.org/index.php?title=File:Journal_sorting_options.png&diff=56445File:Journal sorting options.png2010-09-03T23:58:39Z<p>Aa: Journal sorting options</p>
<hr />
<div>Journal sorting options</div>Aahttps://wiki.sugarlabs.org/index.php?title=Features/Journal_Sort&diff=56439Features/Journal Sort2010-09-03T22:42:29Z<p>Aa: /* Detailed Description */</p>
<hr />
<div><noinclude>{{TOCright}}<br />
[[Category:Feature Accepted 0.90]]<br />
[[Category:Feature|Journal Sorting]]<br />
</noinclude><br />
<br />
== Summary ==<br />
Implements sorting in the Journal UI as described in [[Design_Team/Proposals/Journal#Extended_list_view_palette|this Design Proposal]]. Also adds support for the two new properties (filesize and ctime) to the datastore.<br />
<br />
== Owner ==<br />
* Name: [[User:aa| Andrés Ambrois]]<br />
<br />
* Email: <andresambrois@gmail.com><br />
<br />
== Current status ==<br />
* Targeted release: 0.90<br />
* Last updated: 06/06/10<br />
* Percentage of completion: 100%<br />
<br />
== Detailed Description ==<br />
This feature adds a ToolButton to the Journal toolbar. In its palette, the user can select the following sorting criteria: "Sort by file size", "Sort by last edit", "Sort by creation date".<br />
<br />
== Benefit to Sugar ==<br />
Sorting by filesize is vital in the field where users need to free up disk space. Currently, the only way to find candidates for deletion is to access the expanded view of each entry, one by one. This can be a very time consuming process and often leads to indiscriminate deletion and thus potential loss of valuable data. This is bad.<br />
<br />
Sorting by creation time (ctime) is also implemented as described in the Design<br />
Proposal.<br />
<br />
This feature was requested in [http://bugs.sugarlabs.org/ticket/1915 SL1915] and sponsored by [http://activitycentral.org Activity Central].<br />
<br />
== Scope ==<br />
* Add support for ctime and filesize to the datastore (DONE)<br />
* Implement sorting in the Journal (DONE)<br />
* Add new icons to sugar-artwork (DONE)<br />
<br />
==UI Design==<br />
Please see [[Design_Team/Proposals/Journal#Extended_list_view_palette|the Design Proposal]].<br />
<br />
<gallery><br />
Image:Journal-sort1.png|Sort palette<br />
Image:Journal-sort2.png|Sorting by file size<br />
</gallery><br />
<br />
== How To Test ==<br />
{{:{{PAGENAME}}/Testing}}<br />
== User Experience ==<br />
''If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.''<br />
<br />
== Dependencies ==<br />
None<br />
<br />
== Contingency Plan ==<br />
None necessary, revert to previous release behaviour.<br />
<br />
== Implementation ==<br />
<br />
sugar commits:<br />
<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/780eed1a3871f0cd47cdc06a655782a90eee28ea<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/4c2d26ccaeb502037484ced70b5944e3e20aa3f6<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/a4efed250c56dc6dd656bafb572a1a56e034d254<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/2c90107e36448d00dbe5a64f70024d003e7e531b<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/532594bb856c96e13462e7825187551c940d41f2<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/bc1edfa2193ca554d385c68e43c2cef0b9795a54<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/dbcd0223a87815d3b0d8c79061046d52c4418922<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/addd33e5963f27996fed46f0a34ccc4f4a0c796c<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/0a69741474c775c2dba92e527a94db9b86c27722<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/b1a05110a85ea6d1ba55cd75ccdfcb509c12276c<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/6099b087c80d7fb80856d4e157f8743ce74ec922<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/48c2eeaf5d3007f0970a0f31745efe22063c4465<br />
<br />
sugar-datastore commits:<br />
<br />
http://git.sugarlabs.org/projects/sugar-datastore/repos/mainline/commits/089ba387eafec10734ce3023665a163c531b82b4<br />
http://git.sugarlabs.org/projects/sugar-datastore/repos/mainline/commits/f3f71c3dad6fdf3b69b3624a6a584002c4c4fb28<br />
http://git.sugarlabs.org/projects/sugar-datastore/repos/mainline/commits/faa9974381f5ad70307e6c394d096b56134391e7<br />
http://git.sugarlabs.org/projects/sugar-datastore/repos/mainline/commits/7475a1fe38fca3ee4491bc272a59693805136f1e<br />
http://git.sugarlabs.org/projects/sugar-datastore/repos/mainline/commits/19845394f5f74f67e32192e3a09ce396522329bd<br />
<br />
sugar-artwork commits:<br />
<br />
http://git.sugarlabs.org/projects/sugar-artwork/repos/mainline/commits/55a2fe370eb22ac042ac1c4670f8fa3a111c8f38<br />
<br />
== Documentation ==<br />
[http://lists.sugarlabs.org/archive/sugar-devel/2010-May/023664.html Initial submission to sugar-devel (Sugar patches)]<br />
<br />
[http://lists.sugarlabs.org/archive/sugar-devel/2010-May/023658.html Initial submission to sugar-devel (DS patches)]<br />
<br />
<br />
[http://lists.sugarlabs.org/archive/sugar-devel/2010-May/024089.html Second submission to sugar-devel (Sugar patches)]<br />
<br />
[http://lists.sugarlabs.org/archive/sugar-devel/2010-May/024083.html Second submission to sugar-devel (DS patches)]<br />
<br />
[http://lists.sugarlabs.org/archive/sugar-devel/2010-May/024199.html Icons]<br />
<br />
== Release Notes ==<br />
''The Sugar Release Notes inform end-users about what is new in the release. An Example is [[0.84/Notes]]. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.''<br />
<br />
== Comments and Discussion ==<br />
* See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page. --></div>Aahttps://wiki.sugarlabs.org/index.php?title=Features/Journal_Sort&diff=56438Features/Journal Sort2010-09-03T22:40:29Z<p>Aa: /* Implementation */</p>
<hr />
<div><noinclude>{{TOCright}}<br />
[[Category:Feature Accepted 0.90]]<br />
[[Category:Feature|Journal Sorting]]<br />
</noinclude><br />
<br />
== Summary ==<br />
Implements sorting in the Journal UI as described in [[Design_Team/Proposals/Journal#Extended_list_view_palette|this Design Proposal]]. Also adds support for the two new properties (filesize and ctime) to the datastore.<br />
<br />
== Owner ==<br />
* Name: [[User:aa| Andrés Ambrois]]<br />
<br />
* Email: <andresambrois@gmail.com><br />
<br />
== Current status ==<br />
* Targeted release: 0.90<br />
* Last updated: 06/06/10<br />
* Percentage of completion: 100%<br />
<br />
== Detailed Description ==<br />
This feature adds a ToggleButton to the Journal toolbar. In its palette, the user can select the following sorting criteria: "Sort by file size", "Sort by last edit", "Sort by creation date".<br />
<br />
== Benefit to Sugar ==<br />
Sorting by filesize is vital in the field where users need to free up disk space. Currently, the only way to find candidates for deletion is to access the expanded view of each entry, one by one. This can be a very time consuming process and often leads to indiscriminate deletion and thus potential loss of valuable data. This is bad.<br />
<br />
Sorting by creation time (ctime) is also implemented as described in the Design<br />
Proposal.<br />
<br />
This feature was requested in [http://bugs.sugarlabs.org/ticket/1915 SL1915] and sponsored by [http://activitycentral.org Activity Central].<br />
<br />
== Scope ==<br />
* Add support for ctime and filesize to the datastore (DONE)<br />
* Implement sorting in the Journal (DONE)<br />
* Add new icons to sugar-artwork (DONE)<br />
<br />
==UI Design==<br />
Please see [[Design_Team/Proposals/Journal#Extended_list_view_palette|the Design Proposal]].<br />
<br />
<gallery><br />
Image:Journal-sort1.png|Sort palette<br />
Image:Journal-sort2.png|Sorting by file size<br />
</gallery><br />
<br />
== How To Test ==<br />
{{:{{PAGENAME}}/Testing}}<br />
== User Experience ==<br />
''If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.''<br />
<br />
== Dependencies ==<br />
None<br />
<br />
== Contingency Plan ==<br />
None necessary, revert to previous release behaviour.<br />
<br />
== Implementation ==<br />
<br />
sugar commits:<br />
<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/780eed1a3871f0cd47cdc06a655782a90eee28ea<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/4c2d26ccaeb502037484ced70b5944e3e20aa3f6<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/a4efed250c56dc6dd656bafb572a1a56e034d254<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/2c90107e36448d00dbe5a64f70024d003e7e531b<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/532594bb856c96e13462e7825187551c940d41f2<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/bc1edfa2193ca554d385c68e43c2cef0b9795a54<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/dbcd0223a87815d3b0d8c79061046d52c4418922<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/addd33e5963f27996fed46f0a34ccc4f4a0c796c<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/0a69741474c775c2dba92e527a94db9b86c27722<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/b1a05110a85ea6d1ba55cd75ccdfcb509c12276c<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/6099b087c80d7fb80856d4e157f8743ce74ec922<br />
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/48c2eeaf5d3007f0970a0f31745efe22063c4465<br />
<br />
sugar-datastore commits:<br />
<br />
http://git.sugarlabs.org/projects/sugar-datastore/repos/mainline/commits/089ba387eafec10734ce3023665a163c531b82b4<br />
http://git.sugarlabs.org/projects/sugar-datastore/repos/mainline/commits/f3f71c3dad6fdf3b69b3624a6a584002c4c4fb28<br />
http://git.sugarlabs.org/projects/sugar-datastore/repos/mainline/commits/faa9974381f5ad70307e6c394d096b56134391e7<br />
http://git.sugarlabs.org/projects/sugar-datastore/repos/mainline/commits/7475a1fe38fca3ee4491bc272a59693805136f1e<br />
http://git.sugarlabs.org/projects/sugar-datastore/repos/mainline/commits/19845394f5f74f67e32192e3a09ce396522329bd<br />
<br />
sugar-artwork commits:<br />
<br />
http://git.sugarlabs.org/projects/sugar-artwork/repos/mainline/commits/55a2fe370eb22ac042ac1c4670f8fa3a111c8f38<br />
<br />
== Documentation ==<br />
[http://lists.sugarlabs.org/archive/sugar-devel/2010-May/023664.html Initial submission to sugar-devel (Sugar patches)]<br />
<br />
[http://lists.sugarlabs.org/archive/sugar-devel/2010-May/023658.html Initial submission to sugar-devel (DS patches)]<br />
<br />
<br />
[http://lists.sugarlabs.org/archive/sugar-devel/2010-May/024089.html Second submission to sugar-devel (Sugar patches)]<br />
<br />
[http://lists.sugarlabs.org/archive/sugar-devel/2010-May/024083.html Second submission to sugar-devel (DS patches)]<br />
<br />
[http://lists.sugarlabs.org/archive/sugar-devel/2010-May/024199.html Icons]<br />
<br />
== Release Notes ==<br />
''The Sugar Release Notes inform end-users about what is new in the release. An Example is [[0.84/Notes]]. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.''<br />
<br />
== Comments and Discussion ==<br />
* See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page. --></div>Aahttps://wiki.sugarlabs.org/index.php?title=Features/Journal_Sort&diff=56437Features/Journal Sort2010-09-03T22:37:00Z<p>Aa: /* Current status */</p>
<hr />
<div><noinclude>{{TOCright}}<br />
[[Category:Feature Accepted 0.90]]<br />
[[Category:Feature|Journal Sorting]]<br />
</noinclude><br />
<br />
== Summary ==<br />
Implements sorting in the Journal UI as described in [[Design_Team/Proposals/Journal#Extended_list_view_palette|this Design Proposal]]. Also adds support for the two new properties (filesize and ctime) to the datastore.<br />
<br />
== Owner ==<br />
* Name: [[User:aa| Andrés Ambrois]]<br />
<br />
* Email: <andresambrois@gmail.com><br />
<br />
== Current status ==<br />
* Targeted release: 0.90<br />
* Last updated: 06/06/10<br />
* Percentage of completion: 100%<br />
<br />
== Detailed Description ==<br />
This feature adds a ToggleButton to the Journal toolbar. In its palette, the user can select the following sorting criteria: "Sort by file size", "Sort by last edit", "Sort by creation date".<br />
<br />
== Benefit to Sugar ==<br />
Sorting by filesize is vital in the field where users need to free up disk space. Currently, the only way to find candidates for deletion is to access the expanded view of each entry, one by one. This can be a very time consuming process and often leads to indiscriminate deletion and thus potential loss of valuable data. This is bad.<br />
<br />
Sorting by creation time (ctime) is also implemented as described in the Design<br />
Proposal.<br />
<br />
This feature was requested in [http://bugs.sugarlabs.org/ticket/1915 SL1915] and sponsored by [http://activitycentral.org Activity Central].<br />
<br />
== Scope ==<br />
* Add support for ctime and filesize to the datastore (DONE)<br />
* Implement sorting in the Journal (DONE)<br />
* Add new icons to sugar-artwork (DONE)<br />
<br />
==UI Design==<br />
Please see [[Design_Team/Proposals/Journal#Extended_list_view_palette|the Design Proposal]].<br />
<br />
<gallery><br />
Image:Journal-sort1.png|Sort palette<br />
Image:Journal-sort2.png|Sorting by file size<br />
</gallery><br />
<br />
== How To Test ==<br />
{{:{{PAGENAME}}/Testing}}<br />
== User Experience ==<br />
''If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.''<br />
<br />
== Dependencies ==<br />
None<br />
<br />
== Contingency Plan ==<br />
None necessary, revert to previous release behaviour.<br />
<br />
== Implementation ==<br />
<br />
* [http://git.sugarlabs.org/projects/sugar-datastore/repos/journal_sort datastore fork]<br />
* [http://git.sugarlabs.org/projects/sugar/repos/journal_sort sugar fork]<br />
<br />
== Documentation ==<br />
[http://lists.sugarlabs.org/archive/sugar-devel/2010-May/023664.html Initial submission to sugar-devel (Sugar patches)]<br />
<br />
[http://lists.sugarlabs.org/archive/sugar-devel/2010-May/023658.html Initial submission to sugar-devel (DS patches)]<br />
<br />
<br />
[http://lists.sugarlabs.org/archive/sugar-devel/2010-May/024089.html Second submission to sugar-devel (Sugar patches)]<br />
<br />
[http://lists.sugarlabs.org/archive/sugar-devel/2010-May/024083.html Second submission to sugar-devel (DS patches)]<br />
<br />
[http://lists.sugarlabs.org/archive/sugar-devel/2010-May/024199.html Icons]<br />
<br />
== Release Notes ==<br />
''The Sugar Release Notes inform end-users about what is new in the release. An Example is [[0.84/Notes]]. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.''<br />
<br />
== Comments and Discussion ==<br />
* See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page. --></div>Aahttps://wiki.sugarlabs.org/index.php?title=Features/Journal_Sort&diff=52828Features/Journal Sort2010-06-06T22:37:03Z<p>Aa: </p>
<hr />
<div><noinclude>{{TOCright}}<br />
[[Category:Feature Page Incomplete]]<br />
[[Category:Feature|Journal Sorting]]<br />
<!-- You can add categories to tie features back to real deployments/schools requesting them, for example <br />
[[Category:Features requested by School Xyz|<Feature Name>]] (the |Feature Name option sorts the entry on the category page under the first letter of <Feature Name>). --><br />
</noinclude><br />
<br />
== Summary ==<br />
Implements sorting in the Journal UI as described in [[Design_Team/Proposals/Journal#Extended_list_view_palette|this Design Proposal]]. Also adds support for the two new properties (filesize and ctime) to the datastore.<br />
<br />
== Owner ==<br />
* Name: [[User:aa| Andrés Ambrois]]<br />
<br />
* Email: <andresambrois@gmail.com><br />
<br />
== Current status ==<br />
* Targeted release: 0.90<br />
* Last updated: 06/06/10<br />
* Percentage of completion: 80%<br />
<br />
== Detailed Description ==<br />
This feature adds a ToggleButton to the Journal toolbar. In its palette, the user can select the following sorting criteria: "Sort by file size", "Sort by last edit", "Sort by creation date".<br />
<br />
== Benefit to Sugar ==<br />
Sorting by filesize is vital in the field where users need to free up disk space. Currently, the only way to find candidates for deletion is to access the expanded view of each entry, one by one. This can be a very time consuming process and often leads to indiscriminate deletion and thus potential loss of valuable data. This is bad.<br />
<br />
Sorting by creation time (ctime) is also implemented as described in the Design<br />
Proposal.<br />
<br />
This feature was requested in [http://bugs.sugarlabs.org/ticket/1915 SL1915] and sponsored by [http://activitycentral.org Activity Central].<br />
<br />
== Scope ==<br />
* Add support for ctime and filesize to the datastore (DONE)<br />
* Implement sorting in the Journal (DONE)<br />
* Add new icons to sugar-artwork (DONE)<br />
<br />
==UI Design==<br />
Please see [[Design_Team/Proposals/Journal#Extended_list_view_palette|the Design Proposal]].<br />
<br />
<gallery><br />
Image:Journal-sort1.png|Sort palette<br />
Image:Journal-sort2.png|Sorting by file size<br />
</gallery><br />
<br />
== How To Test ==<br />
{{:{{PAGENAME}}/Testing}}<br />
== User Experience ==<br />
''If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.''<br />
<br />
== Dependencies ==<br />
None<br />
<br />
== Contingency Plan ==<br />
None necessary, revert to previous release behaviour.<br />
<br />
== Documentation ==<br />
[http://lists.sugarlabs.org/archive/sugar-devel/2010-May/023664.html Initial submission to sugar-devel (Sugar patches)]<br />
<br />
[http://lists.sugarlabs.org/archive/sugar-devel/2010-May/023658.html Initial submission to sugar-devel (DS patches)]<br />
<br />
<br />
[http://lists.sugarlabs.org/archive/sugar-devel/2010-May/024089.html Second submission to sugar-devel (Sugar patches)]<br />
<br />
[http://lists.sugarlabs.org/archive/sugar-devel/2010-May/024083.html Second submission to sugar-devel (DS patches)]<br />
<br />
[http://lists.sugarlabs.org/archive/sugar-devel/2010-May/024199.html Icons]<br />
<br />
== Release Notes ==<br />
''The Sugar Release Notes inform end-users about what is new in the release. An Example is [[0.84/Notes]]. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.''<br />
<br />
== Comments and Discussion ==<br />
* See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page. --></div>Aahttps://wiki.sugarlabs.org/index.php?title=Features/Journal_Sort&diff=52827Features/Journal Sort2010-06-06T22:36:02Z<p>Aa: Created page with '<noinclude>{{TOCright}} Category:Feature Page Incomplete Journal Sorting <!-- You can add categories to tie features back to real deployments/schools req...'</p>
<hr />
<div><noinclude>{{TOCright}}<br />
[[Category:Feature Page Incomplete]]<br />
[[Category:Feature|Journal Sorting]]<br />
<!-- You can add categories to tie features back to real deployments/schools requesting them, for example <br />
[[Category:Features requested by School Xyz|<Feature Name>]] (the |Feature Name option sorts the entry on the category page under the first letter of <Feature Name>). --><br />
</noinclude><br />
<br />
'''Comments and Explanations:'''<br />
<br />
There are comments (in italic) providing guidance to fill out each section, see also the [[Features/Policy|Feature Policy Page]] for a more detailed explanation of the new-feature process. '''Copy the source to a ''new page'' named Features/''Your Feature Name'' before making changes! DO NOT EDIT THIS TEMPLATE.'''<br />
<br />
<!-- All fields on this form are required to be accepted.<br />
We also request that you maintain the same order of sections so that all of the feature pages are uniform. --><br />
<br />
<!-- The actual name of your feature page should look something like: Features/Your Feature Name. This keeps all features in the same namespace --><br />
<br />
== Summary ==<br />
Implements sorting in the Journal UI as described in [[Design_Team/Proposals/Journal#Extended_list_view_palette|this Design Proposal]]. Also adds support for the two new properties (filesize and ctime) to the datastore.<br />
<br />
== Owner ==<br />
* Name: [[User:aa| Andrés Ambrois]]<br />
<br />
* Email: <andresambrois@gmail.com><br />
<br />
== Current status ==<br />
* Targeted release: 0.90<br />
* Last updated: 06/06/10<br />
* Percentage of completion: 80%<br />
<br />
== Detailed Description ==<br />
This feature adds a ToggleButton to the Journal toolbar. In its palette, the user can select the following sorting criteria: "Sort by file size", "Sort by last edit", "Sort by creation date".<br />
<br />
== Benefit to Sugar ==<br />
Sorting by filesize is vital in the field where users need to free up disk space. Currently, the only way to find candidates for deletion is to access the expanded view of each entry, one by one. This can be a very time consuming process and often leads to indiscriminate deletion and thus potential loss of valuable data. This is bad.<br />
<br />
Sorting by creation time (ctime) is also implemented as described in the Design<br />
Proposal.<br />
<br />
This feature was requested in [http://bugs.sugarlabs.org/ticket/1915 SL1915] and sponsored by [http://activitycentral.org Activity Central].<br />
<br />
== Scope ==<br />
* Add support for ctime and filesize to the datastore (DONE)<br />
* Implement sorting in the Journal (DONE)<br />
* Add new icons to sugar-artwork (DONE)<br />
<br />
==UI Design==<br />
Please see [[Design_Team/Proposals/Journal#Extended_list_view_palette|the Design Proposal]].<br />
<br />
<gallery><br />
Image:Journal-sort1.png|Sort palette<br />
Image:Journal-sort2.png|Sorting by file size<br />
</gallery><br />
<br />
== How To Test ==<br />
{{:{{PAGENAME}}/Testing}}<br />
== User Experience ==<br />
''If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.''<br />
<br />
== Dependencies ==<br />
None<br />
<br />
== Contingency Plan ==<br />
None necessary, revert to previous release behaviour.<br />
<br />
== Documentation ==<br />
[http://lists.sugarlabs.org/archive/sugar-devel/2010-May/023664.html Initial submission to sugar-devel (Sugar patches)]<br />
<br />
[http://lists.sugarlabs.org/archive/sugar-devel/2010-May/023658.html Initial submission to sugar-devel (DS patches)]<br />
<br />
<br />
[http://lists.sugarlabs.org/archive/sugar-devel/2010-May/024089.html Second submission to sugar-devel (Sugar patches)]<br />
<br />
[http://lists.sugarlabs.org/archive/sugar-devel/2010-May/024083.html Second submission to sugar-devel (DS patches)]<br />
<br />
[http://lists.sugarlabs.org/archive/sugar-devel/2010-May/024199.html Icons]<br />
<br />
== Release Notes ==<br />
''The Sugar Release Notes inform end-users about what is new in the release. An Example is [[0.84/Notes]]. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.''<br />
<br />
== Comments and Discussion ==<br />
* See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page. --></div>Aahttps://wiki.sugarlabs.org/index.php?title=File:Journal-sort2.png&diff=52825File:Journal-sort2.png2010-06-06T22:10:05Z<p>Aa: </p>
<hr />
<div></div>Aahttps://wiki.sugarlabs.org/index.php?title=File:Journal-sort1.png&diff=52824File:Journal-sort1.png2010-06-06T22:08:34Z<p>Aa: </p>
<hr />
<div></div>Aahttps://wiki.sugarlabs.org/index.php?title=User:Aa&diff=52823User:Aa2010-06-06T21:39:56Z<p>Aa: Created page with 'Contact: andresambrois_AT_gmail.com'</p>
<hr />
<div>Contact: andresambrois_AT_gmail.com</div>Aahttps://wiki.sugarlabs.org/index.php?title=Talk:Print_Support&diff=41604Talk:Print Support2009-12-14T18:37:11Z<p>Aa: moved Talk:Print Support to Talk:Summer of Code/2009/Print Support:&#32;Moved to the correct ns to make room for proper documentation</p>
<hr />
<div>#REDIRECT [[Talk:Summer of Code/2009/Print Support]]</div>Aahttps://wiki.sugarlabs.org/index.php?title=Talk:Summer_of_Code/2009/Print_Support&diff=41603Talk:Summer of Code/2009/Print Support2009-12-14T18:37:11Z<p>Aa: moved Talk:Print Support to Talk:Summer of Code/2009/Print Support:&#32;Moved to the correct ns to make room for proper documentation</p>
<hr />
<div>Looks pretty good. A couple of quick questions, while it is still unfinished:<br />
<br />
* Why do you do the PDF conversion on the server? Shouldn't the student be able to see a WYSIWYG version, margins and all?<br />
<br />
* Is there a way for a student to cancel a request?<br />
<br />
* At the moment, Sugar opens files by mime type, and each activity handles its own mime type(s). If you save a pdf to journal to be opened by the "send to server" activity, it would actually be opened by Read. Would you plan to modify sugar to have an "open with" metadata to cue it to open with your print activity? Or would you find some other workaround?<br />
<br />
[[User:Homunq|Homunq]] 03:01, 24 March 2009 (UTC)<br />
<br />
<br />
<br />
* <br />
<br />
Thing is we don't technically do a pdf conversion, CUPS comes with an emulator of the print engine, and prints to the PDF (cups-pdf <br />
modules to be specific to create a virtual printer). And we do this <br />
because we would like for the teacher to review it. <br />
The pdf is stored in a web folder on the server, and through moodle the teacher goes through them (we provide a webpage), and <br />
approves the ones he thinks appropriate for printing.<br />
I explained it my explanation<br />
The outcome of my second draft (beta) was that students should be provided as minimal functionality as possible. <br />
They shouldn't be given too much flexibility or options. And... you get <br />
WYSIWYG only as we send the files directly from the journal.<br />
<br />
<br />
* <br />
<br />
Yep, student can cancel his request, I forgot adding it. With The function cupsCancelJob() the student can cancel the job before his <br />
request goes to server (or before it can be printed to pdf).<br />
But after actually entering the web folder, It would become a bit complex. I would have to do this:<br />
1) we would send in a query with the name of the file and a .pdf extension<br />
2) if that file exists on web folder delete, otherwise do nothing<br />
3) send suitable message back<br />
<br />
* <br />
<br />
No, no. There is ABSOLUTELY no need to interact with sugar activities, in the cups folder we have a file with the list of mime types <br />
accepted. We would also append the server supported CUPS Mimes to <br />
the clients CUPS.<br />
IF the mime type exists in cups mime.type , we are all good to do printing from journal. (that is why we require step 1)<br />
There is no reason to read the file, the server handles the necessary post script conversions!<br />
[[User:IwikiwI|IwikiwI]]<br />
<br />
== Why the distinction? ==<br />
<br />
To me, "mark for printing" and "save as PDF" should be one single option, as both should result in a PDF in the journal. "unmark for printing" would be something you did on that pdf, not on the original file. [[User:Homunq|Homunq]] 00:25, 31 March 2009 (UTC)<br />
<br />
<br />
'''Answer'''<br />
I edited my proposal a lot so its more understandable now.<br />
But my idea is use the same code, and when mark as printing is done, the pdf generated will not be shown to the user. It will be hidden and after sending it to the moodle queue, it will be deleted.And till that happenes only he can unmark for printing, Which will destroy the job before it reaches moodle's datastore.<br />
After this he's free to again mark for printing. :D<br />
<br />
And since only Write (abiword) can generate pdfs atm, we wont be able to generate pdfs for .py, or image types from other applications.<br />
A global pdf generation button would be awesome. And Unique!<br />
<br />
And the reason I do conversion for case one is, a scenario where sugar recognized format might not be recognized by the teacher's machine.<br />
<br />
[[User:IwikiwI|IwikiwI]]</div>Aahttps://wiki.sugarlabs.org/index.php?title=Print_Support&diff=41602Print Support2009-12-14T18:37:10Z<p>Aa: moved Print Support to Summer of Code/2009/Print Support:&#32;Moved to the correct ns to make room for proper documentation</p>
<hr />
<div>#REDIRECT [[Summer of Code/2009/Print Support]]</div>Aahttps://wiki.sugarlabs.org/index.php?title=Summer_of_Code/2009/Print_Support&diff=41601Summer of Code/2009/Print Support2009-12-14T18:37:10Z<p>Aa: moved Print Support to Summer of Code/2009/Print Support:&#32;Moved to the correct ns to make room for proper documentation</p>
<hr />
<div>====About you====<br />
:'''1 What is your name? '''<br />
<br />
:Vamsi Krishna Davuluri<br />
<br />
:'''2 What is your email address? '''<br />
<br />
:vamsi<dot>davuluri<at>gmail<dot>com <br />
<br />
:'''3 What is your Sugar Labs wiki username? '''<br />
<br />
:IwikiwI<br />
<br />
:'''4 What is your IRC nickname? '''<br />
<br />
:IwikiwI/iwikiwi ( Sometimes vkd, Vamsi, Vamsi_)<br />
<br />
:'''5 What is your primary language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.) '''<br />
<br />
:English, Hindi, Telugu. I prefer English!<br />
<br />
:'''6 Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.) '''<br />
<br />
:I am located in India (5:30+ GMT), I usually work in the night, from my 7 pm to 2:30 am<br />
:So any mentor should be ideal.<br />
<br />
:'''7 Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source. If not, why do you want to work on an open-source project this summer? '''<br />
<br />
:I have not been part of an open source development team nor do I have a very profound understanding of the OS development paradigm - so far, but seeing how I could never afford software which was sold at high price even though that software was the bare essential software for me to get my computer working. And as my experiences are true for almost two thirds of other students, I would like to see them not to have to put up with the buy-what-you-want software, in-fact I would love for them to grow up using free software that I make and hope that they will produce free software themselves, a few of them at least.<br />
<br />
:Although not really a group developmental project, I have coded two networks projects and a prototype game for windows. (the source is in downloads)<br />
<br />
:'''1) '''Simulation of mobile units and their movement over a network (unix network programming, and unix programming)<br />
<br />
: http://code.google.com/p/iwikiwi/<br />
<br />
:'''2) '''A client/server model for file transfer, md5 check sum, IP translations, and file size requests (unix network programming, and unix programming)<br />
<br />
: http://code.google.com/p/iwikiwi-clientserver/<br />
<br />
:'''3) '''A prototype Bounce game in OpenGL for windows<br />
<br />
: http://code.google.com/p/iwikiwi-bounce/<br />
<br />
====About your project====<br />
<br />
:'''1 What is the name of your project? '''<br />
<br />
:Print Support for the XO laptops <br />
<br />
:'''2 Describe your project in 10-20 sentences'''.<br />
<br />
:As the self explanatory name suggests, the project is to add print support to the laptops.For the time being, the print requests will be sent to the school server through a moodle print page <br />
:then the teacher can view the files through his login in the same application, and approve them for printing to a print server. We will also be including a fallback strategy that is usb printing.<br />
<br />
:''Why should my idea be considered:''<br />
<br />
:My refined version of the print support idea is actually a better way of ensuring that paper abuse will be curbed, as the kids wouldn't really take into account :all the predicaments associated with :printing. And needless to say printing does take place with the teacher's intervention. And everything takes place in a moodle environment, plus there is the added benefit of printing in the No XO case.<br />
<br />
:'''A step by step abstraction:'''<br />
<br />
:(The first step would essentially mean a Save as PDF hack and put the jobs for processing on moodle ) <br />
<br />
<br />
:'''1)'''<br />
:The right click menu of an item in the journal will have a new option, i.e. "print!". When clicked, the item will be opened with Read and if its not a recognized format, convert it with cups-pdf and open with Read. and the pdf will have metadata attached stating its details (this PDF plus metadata wont be visible to the user).The user can have a preview of his print, save it as a pdf in the journal, and send a PDFed version to moodle.<br />
:advantage cups-pdf (text will be mapped as text only)<br />
:Later on we can extend this to have a print button in every activity, so that the default activity which opens the object can print from itself.<br />
<br />
:The usecase would be, distinction of saving a pdf and sending it to printing. And the conversion is mandatory so as to prevent a scenario where the sugar file type might not be recognized by the teacher's machine.<br />
<br />
:We will be using moodle as our interface for sending print requests on the network. The interface will have a user page and a teacher page. The page will have a report of his print jobs and a status report of his live jobs. And the ability to put 3 live jobs on queue. The number of upload slots will be dynamically updated according to his live jobs pending for teacher's approval(which is a maximum of 3). And the number of free slots will automatically be filled up by the browser with the to-print PDFs. And then these objects will be sent to the moodle web folder.<br />
<br />
:(The 2nd would be implementing queuing and teacher review, reject approve facilities <br />
:'''2)''' Through moodle the teacher will have a page displaying the contents of the moodle print datastore along with user names attached, and he/she will be able to download them to his remote system, and check them and approve them for printing if he/she wishes. After his/her approval or disapproval (that is a delete along with an option why) the information is held in the datastore, and the user can view it in the form of history transactions pertaining to his id, and teacher can view a finite list of previous transactions pertaining to all. <br />
<br />
:( The 3rd usb printing on demand!)<br />
<br />
:'''3)''' The no School Server case. The simple solution to this case is to print directly through usb. And this won't be counter productive to the idea of teacher moderated printing, as the printer won't be available for just anyone; this is only a quick alternative to the 'save to portable drive and do the printing' method. <br />
<br />
:'''In-Depth analysis:'''<br />
<br />
<br />
:For step-1,We hack into Read and create a new print toolbar, one with direct printing, one with moodle printing, and one with export as pdf. For all things other than direct printing a dummy pdf is created.<br />
:For Read to send jobs to moodle and get the queue details we use xmlrpclib , and send only as much as the number of free slots . (Or a simpler way will be to bypass the dialog automatically). The execution part of this will take place dynamically as soon as the user requests the print page. And also, once the pdf is read, it is destroyed.<br />
:We will also provide a way so the user can send only pdf files through the moodle user page, which will be based on the upload many number of files module.<br />
<br />
:For step-2, We will be using the interface already created, but for the teacher we will issue global access privileges enabling him/her to access all the sent requests for his group.The approve button will initiate shell commands to send the particular file to a network printer through CUPS installed on the server.This can again be achieved through hacking into moodle and understanding how notifications are sent to the students from teacher. The notifications would be relating to whether the teacher has approved or disapproved the print. <br />
<br />
:The moodle part can be achieved through hacking the already existing plugin [http://docs.moodle.org/en/Upload_a_single_file_assignment] and looking into the moodle API and plugin documentation. From my research so far, moodle has most of all the low level details already existing within the moodle libraries. Even $_GET $_POST methods are abstracted into simpler functions.<br />
<br />
:For step-3, no new code is required; a few more dependencies are required, which wont exceed 16mb. We will be including print directly (usb) as an option under the item's right click menu too. This will have the same code as print to pdf for the most part, but will have added code to select a new default printer.<br />
<br />
:''Is there a disadvantage in relying upon moodle for network printing?''<br />
:Since the whole concept relies upon network printing, it will be feasible for moodle to coexist with the system on the school server. We will just be adding moodle as a requirement for network printing. <br />
<br />
<br />
:'''Key features:'''<br />
<br />
:* Will be able to print to any USB printer<br />
:* Will be able to output a print as a PDF<br />
:* Includes a user queue and a teacher queue<br />
:* automatically parses print requests to the print page<br />
:* Uses moodle as interface for teacher moderated printing<br />
:* A 3 live/pending jobs at a time queue.<br />
:* Teacher can approve/ disapprove printing from the queue.<br />
:* Student will have status updates in his page.<br />
:* Has a no school server case.<br />
<br />
<br />
:'''3 Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, :credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.'''<br />
<br />
:I have a fairly good understanding of communication models, and my skill with networks is quite satisfactory. And as most of the implementation is already available in form of python bindings, all that :remains is placing them together with a sound design, which I have already discussed with several community members. And I can provide as much time as is required for the work to get done. I am introduced to server side programming through django on which I had worked to develop a weblog ( I dont have the code for it, and the weblog isn't operational), all I can say is I had *fun* with the template language they had, which was mostly regexp parsing.<br />
:And I have learnt php these last few days enough to hack on moodle.<br />
<br />
:''My credentials include: ''<br />
<br />
:'''1)''' The ability to finish projects on his own, with self motivation, as the 3 projects I have attached have been made as a self interest.<br />
<br />
:'''2)''' An internship at Kenexa which had been to develop an assembly which logged database transactions, written in c#, so I have an exposure to infrastructure.<br />
<br />
:'''3)''' winner of a coding event, Mind-Hunters, at a national level technical festival.<br />
<br />
:I have already added a fix to Write so that it can export to pdf files, and I have provided a temporary fix for a screen bug, for which I will provide a complete fix.<br />
<br />
:And I have checked the feasibility of my approach by going through the source files/apis, and writing sample programs like<br />
<br />
<br />
cups_dest_t *dests, *dest;<br />
int num_dests = cupsGetDests(&dests);<br />
int job_id = cupsPrintFile(dests->name,<br />
argv[1],<br />
"Test",<br />
0, NULL);<br />
if (job_id == 0)<br />
printf("error printing file, unsupported format");<br />
<br />
:for printing<br />
<br />
:'''4 What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.'''<br />
<br />
<br />
<br />
:'''April 20th to May 26th:'''<br />
:* Research the sugar API extensively <br />
:* Write sample D-BUS communication programs and xmlrpc programs<br />
:* Hack into moodle code, and create purposeful hacks (modifying the limits for plugin in consideration, and such)<br />
:* Talk with the design team and produce prototype interface designs<br />
:* Look into moodle APIs<br />
:* Focus on the bare essential dependencies required to get the job done<br />
<br />
:My job will be not only writing working code, but regularly getting it deployed to check if the user's find it good and working to their needs or not.<br />
:So when I say community feedback, I will be using it interchangeably between actual deployment and the irc community depending on context<br />
<br />
<br />
:'''Milestone 1'''<br />
<br />
:'''Week 1 : '''<br />
:: Start work on Read and add printing buttons to it (see that they do their jobs), and write minimal journal code.<br />
<br />
:'''Week 2 : '''<br />
:: hack on browse so it can save html files, and see to it that read can convert and save all files to pdf and send to moodle.<br />
<br />
:''Milestone 1 result : Sugar side of our code will be done. ''<br />
<br />
:'''Milestone 2'''<br />
<br />
:'''Week 3 : '''<br />
:Start working on moodle's userpage.(Hack the 'upload several assignments' code and make a new plugin out of it.)<br />
:Use xml-rpc to link moodle's datastore with Read code<br />
<br />
:'''Week 4 '''<br />
:start working on moodles teacher page, and see that he/she can review only his group's assignments<br />
:And start working on a php script for shell commands to directly print to the network printer.Get mentor and community feedback. <br />
<br />
:Milestone 2 result :'' The teacher review feature and student upload features are working <br />
<br />
:'''Milestone 3''':<br />
:'''Week 5'''<br />
:Start working on creating a nice html layout for the page, get feedback and make corrections accordingly.<br />
:Test code on a server with a printer, and test if everything works, get mentor and community feedback, and if any integration bugs remain, drill them out. <br />
<br />
:Milestone 3 result: '' It would be to finish the moodle plugin, and see to it that printing can be done through it by the teacher and that we have thousands of happy XO user's faces''<br />
<br />
:'''Milestone 4'''<br />
:'''Week 6'''<br />
:Make an extended print dialog activity (use gtkprint dialog), which has options such as select printer and pages for local and pdf printing and moodle added as printer option.<br />
<br />
:'''week 7'''<br />
:Replicate the features in each activity, so that when opened with default activity in journal, they can print.<br />
<br />
:Milestone 4 result : '' Well we have everything set up folks! APART from wifi printing! get feedback<br />
<br />
:'''Then''':<br />
:Fix last minute bugs, check with a sample deployment.<br />
<br />
:'''Beyond GSoC:'''<br />
:''primary focus'':<br />
:*Add a direct network printing mechanism ( avahi if not the CUPS provided Bonjour for DNS-SD/mDNS) and print directly to the print server through wi-fi. This will be .This will be disabled when ever an XS is connected.<br />
:I have written a sample program http://pastebin.be/17562 <br />
:What this does is, it gets the list of printers from the print server, and prints to the default configured one.<br />
:It can be extended to select the print server automatically, traverse through the printers, select appropriate one. And also implement a local queue, cancel option.<br />
<br />
====You and the community====<br />
<br />
:'''1 If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.'''<br />
<br />
:'''From myself:'''<br />
<br />
:"The XO users and teachers will greatly benefit from printing, as converting something digital(which may be art, a presentation or a photo) into a physical representation is something very basic, and :something very strong. Not only will there be a good deal of happy faces, but it will also kill the effort required to copy content to a portable drive, and go to a terminal and print.<br />
:"<br />
<br />
:'''From Benjamin M. Schwartz:'''<br />
<br />
:"In order for Sugar to be adopted in schools with existing IT infrastructure, it must give users an easy way to print their documents.If that printing could be routed through a teacher-controlled visual :print queue, then in this regard Sugar would be the most preferred solution for primary education and schools with limited IT resources."<br />
<br />
:'''From Martin Langhoff'''<br />
<br />
<br />
:"So children can print their own renditions of Robocop on a Unicorn.<br />
<br />
:The goal of your project is to have a simple, effective and portable<br />
:way to print documents from the Sugar environment. The most immediate<br />
:outcome will be very straightforward printing through a School Server.<br />
: Printing is a very popular request in our DIY community so it is also<br />
:important to ensure that printing is workable even in the absence of a<br />
:School Server."<br />
<br />
<br />
<br />
:'''2 Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?'''<br />
<br />
:I think it would be wonderful to begin with my school, I come from a government funded school, not one of those fancy private schools. The kids there would definitely love the different teaching :environment. I will have a talk with the principal, and after that I will further this.<br />
<br />
:'''3 What will you do if you get stuck on your project and your mentor isn't around?'''<br />
<br />
:I will of course go through the net. developer mailing lists, and forums. And the irc channels of each component I am handling.<br />
:But more over, the community has been very helpful without having a mentor as of yet. I will look forward to the community then!<br />
<br />
:'''4 How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?'''<br />
<br />
:I intend to provide weekly updates on the wiki itself. And I will also be providing daily updates on the channel.<br />
<br />
====Miscellaneous====<br />
<br />
:'''Here is the pic with my hack [http://i41.tinypic.com/x6lq9.png]'''<br />
<br />
:'''1 What is your t-shirt size? (Yes, we know Google asks for this already; humor us.) '''<br />
<br />
:Large! (do I get a sugar tshirt?)<br />
<br />
:'''2 Describe a great learning experience you had as a child.'''<br />
<br />
:Being alone and not interacting with others is a hard bargain. It might seem appropriate during the experience (as one can brush it off as," who will interact with the lessers"), but its only after you :reach an age you realise the tragedy one has brought on himself. I can never change my past, but I am a different person now and will be in the future.<br />
<br />
:'''3 Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more?'''<br />
<br />
:My motto: There is no such thing as not able to achieve something, the only variable really is effort which differs from achievement to achievement with person to person. <br />
:what someone else can do, So can I. <br />
<br />
====Use Cases====<br />
<br />
<br />
:'''1 GPA, the SoaS pilot school in Boston MA<br />
<br />
GPA has the following network printers<br />
<br />
Their network printers are :<br />
* Xerox Phaser 3400<br />
* Xerox Phaser 3500<br />
* Xerox Phaser 6360DN<br />
* HP Laserjet 2100<br />
* Lexmark Optra T520<br />
* Lexmark Optra M410<br />
* Xerox Document Centre 470<br />
<br />
Currently they do not let students print, but since students only use a computer for an hour a week this is not a hardship. As they have students compute more they would like them to be able to print.<br />
<br />
I asked them which of the following was their current biggest problem:<br />
<br />
#1 The printers are too busy, you have to wait for your documents to print out.<br />
#2 There is not enough money to buy toner and paper.<br />
#3 The printers are too far away, the teachers have to waste time walking to get their printouts.<br />
#4 The printing system is too confusing or broken and people can't get their stuff to print on the printer they want to use.<br />
<br />
#3 is definitely this schools biggest issue.<br />
<br />
We will be collecting used computers for the SoaS project. We could probably easily also get donations of small printers for each classroom and it sounds like they would want that.<br />
<br />
====Possible User Interface Designs====<br />
<br />
{|<br />
|[[Image:print_device_mockup_for_vamsi_1.png|thumb|350px|Example print device palette showing one active print job. Job can be cancelled via (x) icon]]<br />
|[[Image:print_device_mockup_for_Vamsi_2.png|thumb|350px| Example print device palette showing several print job items with different states in the print queue.]]<br />
|}<br />
<br />
[[Category:2009_GSoC_applications]]</div>Aahttps://wiki.sugarlabs.org/index.php?title=0.86/Notes/lang-es&diff=386430.86/Notes/lang-es2009-10-01T00:32:49Z<p>Aa: Created page with '{{Translation | lang = es | source = 0.86/Notes | version = 38637}} == Lo nuevo para los usuarios == === Rediseño de la barra de herramientas de actividad === La barra de h…'</p>
<hr />
<div>{{Translation<br />
| lang = es<br />
| source = 0.86/Notes<br />
| version = 38637}}<br />
<br />
== Lo nuevo para los usuarios ==<br />
<br />
=== Rediseño de la barra de herramientas de actividad ===<br />
La barra de herramientas usada en las actividades ha sido rediseñada. El <br />
diseño anterior usando pequeñas pestañas de texto para agrupar opciones de la <br />
barra causaba un número de dificultades de usabilidad. Muchos de estos <br />
problemas fueron solucionados en el rediseño. Por ejemplo, el rediseño provee <br />
una solución para el problema de "cómo paro una actividad" (el diseño anterior <br />
de la barra no siempre mostraba un botón "Parar" visible, causando confusión <br />
en los aprendices pequeños). Entre las actividades, Navegar, Escribir, <br />
Calcular, Terminal, Leer, VisorDeImagenes, y TortugArte ya han sido portadas <br />
para usar el nuevo diseño de la barra, mientras se continúa trabajando en <br />
muchas otras. <br />
<br />
=== Cambio al manejador de ventanas Metacity ===<br />
Sugar ha cambiado de Matchbox a un nuevo manejador de ventanas: Metacity. <br />
Matchbox fue diseñado para dispositivos pequeños; fuerza a todas las <br />
aplicaciones a correr maximizadas. Sugar puede ser ejecutado en dispositivos <br />
con pantallas mucho más grandes, y mientras las actividades nativas a Sugar <br />
están diseñadas para ser ejecutadas maximidadas (en pantalla completa), <br />
algunas aplicaciones no específicamente diseñadas para Sugar pueden comportarse <br />
de maneras inesperadas cuando se corren bajo Matchbox. El cambio a Metacity <br />
significa que muchas aplicaciones "no-sugarizadas" correrán mejor dentro de <br />
Sugar (ej. Inkscape, Gimp). Nos disponemos a asegurar que las aplicaciones de <br />
escritorio "tradicionales" corran bien en Sugar, sin requerir cambios en la <br />
programación o el comportamiento. <br />
<br />
=== Actividades Flash ===<br />
Gnash ha sido añadido a la plataforma Sugar, lo cual significa que los <br />
autores de contenido educativo pueden usar herramientas de Flash para crear <br />
actividades de primera clase para Sugar. <br />
<br />
=== Pestañas en Navegar ===<br />
Algunas páginas web contienen enlaces diseñados para ser abiertos en una <br />
ventana nueva. La actividad Navegar ahora abre estos enlaces en nuevas <br />
pestañas dentro de la ventana principal de la actividad, de forma similar al <br />
comportamiento de los navegadores web más comunes, otorgando una mejor <br />
experiencia de navegación. Cabe destacar que esta funcionalidad aún no permite <br />
al usuario abrir un enlace en una pestaña nueva o crear una explícitamente. <br />
<br />
=== Redes Ad Hoc ===<br />
La nueva infraestructura para redes ad-hoc le permite conectarse con otros <br />
usuarios de Sugar sobre red inalámbrica en forma ad-hoc sin depender de <br />
ninguna infraestructura de red inalámbrica. Este es el escenario llamado <br />
"Debajo de un árbol", donde los niños pueden trabajar, jugar, y aprender <br />
colaborativamente en cualquier lugar imaginable, sin requerir ningún punto de <br />
accesso inalámbrico, el cual para muchos niños no está disponible o lo está <br />
únicamente en la escuela. (La computadora XO-1 de One Laptop Per Child provee <br />
una funcionalidad similar con su red 802.11s (mesh) basada en firmware.)<br />
<br />
La red ad-hoc permite a Sugar usar esta funcionalidad con la mayoría del <br />
hardware comúnmente hallado en las computadoras. Además, le permite compartir <br />
una conexión a internet utilizando el mismo mecanismo. <br />
<br />
=== Leer ===<br />
La actividad Leer ahora soporta archivos Epub. Epub es un formato estándar <br />
para libros electrónicos el cual esta ganando aceptación rápidamente en la <br />
comunidad de publicación y distribución de libros digitales. Un número de <br />
sitios web como feedbooks.com, epubbooks.com y Google Books proveen libros <br />
Epub de alta calidad para la descarga sin cargo. Además del soporte de Epub, <br />
esta emisión de la actividad Read también le permite asociar (añadir y editar) <br />
notas con marcadores, y tiene una vista de pantalla completa más útil que <br />
marca el nivel de la batería sin invocar el marco de Sugar.<br />
<br />
=== Actualización de Software ===<br />
El panel de control de Actualización de Software ahora está incluído en <br />
Sugar estándar. Utiliza la Biblioteca de Actividades de Sugar en <br />
http://activities.sugarlabs.org para comprobar e instalar las últimas <br />
actualizaciones de actividades disponibles. Esto facilita a los usuarios la <br />
actualización a la última versión de una actividad dada, y hace más fluida la <br />
publicación y distribución de nuevas versiones para los desarrolladores. <br />
<br />
=== Accesibilidad Mejorada ===<br />
Algunas partes de Sugar (el Diario y la vista en lista de Hogar) han sido <br />
modificadas para usar widgets Gtk+, en lugar de HippoCanvas, el cual no tenía <br />
soporte para accesibilidad. Esto es parte de un esfuerzo en marcha para hacer <br />
que Sugar funcione sin problemas con herramientas de accesibilidad como <br />
lectores de pantalla y lupas para que todos puedan beneficiarse de Sugar, <br />
independientemente de sus habilidades físicas o mentales. Entre otras mejoras <br />
de accesibilidad, más herramientas de Sugar ahora muestran sus atajos de <br />
teclado para asistir su descubrimiento y las actividades en el marco usan <br />
paletas que muestran sus nombres y sus títulos en texto.<br />
<br />
=== Configuración del teclado ===<br />
El panel de control de Sugar (que se encuentra bajo "Mis ajustes") tiene una <br />
nueva sección para seleccionar múltiples disposiciones y modelos del teclado. <br />
Esta funcionalidad permitirá al usuario que no usa un teclado QWERTY <br />
Norteamericano cambiar fácilmente a su configuración preferida. <br />
<br />
=== Mejoras en la Vista de Favoritos en el Hogar ===<br />
Retomar y lanzar nuevas actividades desde la vista de Favoritos en el Hogar <br />
han sido mejoradas simplificando las paletas de actividad de manera tal que las <br />
actividades no puedan ser borradas o removidas de la vista de favoritos <br />
accidentalmente. Toda la administración de actividades ahora se hace a través <br />
de la vista de Lista en el Hogar. Consejo: Para iniciar una nueva actividad <br />
rápidamente sin usar el menú contextual (paleta), presione la tecla "Alt" <br />
mientras hace click en el ícono de la actividad.<br />
<br />
=== Transferencia de Archivos Mejorada ===<br />
La funcionalidad de "Enviar a un amigo" del Diario, ha sido extendida para <br />
soportar transferencias mediante un servidor Jabber, anteriormente esto solo <br />
funcionaba en máquinas en la misma red local. Esto le permite ahora transferir <br />
entradas del Diario a cualquier amigo disponible, independientemente del <br />
mecanismo de comunicación subyacente (un servidor Jabber remoto, o la red <br />
local). Uno puede usar la vista de Vecindario para agregar nuevos amigos. <br />
<br />
=== Nuevo botón Compartir ===<br />
El diseño del botón de Compartir ha sido cambiado. Esperamos que sea más <br />
fácil de descubrir esa funcionalidad ahora. <br />
<br />
=== Reordenamiento de los ítems en el menú de Amigo ===<br />
Como fue pedido desde el campo, el órden en el menú de amigo ha sido <br />
alterado. Las opciones de apagado ahora están ubicadas primeras, ya que son <br />
las más frecuentemente utilizadas. La opción de Reiniciar ha sido quitada. <br />
<br />
== Actualizar a esta versión ==<br />
Por favor use las instrucciones de su distribución (SoaS, Fedora, Ubuntu, <br />
Debian, etc) para actualizarse a esta versión. <br />
<br />
== Lo nuevo para desarrolladores ==<br />
Los siguientes cambios son importantes para desarrolladores usando la <br />
plataforma de desarrollo Sucrose 0.86.<br />
<br />
=== Widgets ===<br />
* Nuevas barras de herramientas: Sugar se ha cambiado a un nuevo diseño de la<br />
barra de herramientas. El ejemplo más simple se puede encontrar en la <br />
actividad Hello World. Si desea agrupar funcionalidad en una barra de <br />
herramientas secundaria, puede consultar la actividad Terminal. Para tener una <br />
disposición consistente a través de las actividades,por favor agrupe la barra <br />
Editar y Ver a la izquierda. Los elementos en la barra deben estar alineados <br />
hacia la izquierda. <br />
* Nuevo botón Compartir: El diseño del botón Compartir ha cambiado. Si su <br />
actividad to soporta colaboración puede asignar al miembro de la clase <br />
Activity max_members el valor 1, lo cual hace insensible al botón. <br />
* CellRenderIcon: Éste nuevo widget permite agregar íconos SVG de Sugar a <br />
gtk.TreeView. El "CellRendererInvoker" es usado para la paleta <br />
consecuentemente. <br />
* RadioPalette: Clase base para ShareButton.<br />
* PaletteWindow: Se ha agregado un widget PaletteWindow.<br />
<br />
=== API ===<br />
* Para agregar la toolbar_box a la actividad, usamos una propiedad toolbar_box <br />
en vez del método set_toolbox. <br />
<br />
=== Dependencias ===<br />
* Cambio de Matchbox a Metacity. Para los autores de actividades esto significa <br />
que el tamaño de sus ventanas debe poder ser modificable por el usuario, lo <br />
cual a su vez requiere que la disposición se adapte a cambios en el tamaño de <br />
la ventana.<br />
<br />
=== Guía para autores de actividades ===<br />
Los módulos md5 y sha se han marcado como obsoletos en Python 2.6. Por favor <br />
actualice sus fuentes consecuentemente. Alentamos a cada autor, de Fructose u <br />
otras actividades, seguir las Code_guidelines <br />
(http://wiki.sugarlabs.org/go/Development_Team/Code_guidelines). Por favor ten <br />
en mente que tenemos la funcionalidad de "Ver fuente" activada y que los niños <br />
pueden ojear el código. Esperamos que encuentren actividades consistentes y <br />
bien escritas. <br />
<br />
== Lo nuevo para empaquetadores ==<br />
* sugar-base: nueva dependencia: python-decorator: <br />
http://pypi.python.org/pypi/decorator<br />
* Sugar: Metacity: El cambio al manejador de ventanas Metacity depende de <br />
este:<br />
http://git.gnome.org/cgit/metacity/commit/?id=b625ec30d99b2dcf86d8fa78b09f6d04dce3a6e0 <br />
commit que agrega una opción de la línea de comando para deshabilitar el <br />
poner en pantalla completa los ventanas maximizadas sin decoraciones <br />
automáticamente. <br />
* Sugar: El panel de control de teclado: <br />
http://www.freedesktop.org/wiki/Software/LibXklavier libxklavier >= 4.0, <br />
http://download.sugarlabs.org/sources/external/python-xklavier/ python <br />
bindings >= 0.2<br />
* Actividades Flash: Las distribuciones necesitan empaquetar la última versión <br />
de Gnash (v9).<br />
* Tabs en Navegar: Hulahop versión >= 0.5<br />
* Escribir: Abiword 2.8 será lanzado en breve y será parte de la Plataforma <br />
Sugar 0.86, así que debemos tener la última versión de la seria 2.7.x para <br />
comenzar a probarlo.<br />
* Leer: Nuevas dependencias para Leer versión >= 70 (necesario para soporte <br />
Epub ): webkitgtk (Nota: http://code.google.com/p/pywebkitgtk/downloads/list <br />
pywebkitgtk debe ser >= 1.1.6), python-lxml, python-BeautifulSoup<br />
* sugar-datastore: Los archivos LICENSE.GPL, README.txt fueron renombrados a <br />
COPYING y README; agregado archivos AUTHORS y NEWS.<br />
<br />
== Internacionalización (i18n) y Localización (l10n) ==<br />
Gracias a los miembros del equipo de traducción global, que pueden ser <br />
contactados en la lista de correos de localización <br />
(http://lists.laptop.org/listinfo/localization), tenemos las siguientes <br />
lenguas (listadas alfabéticamente) con una proporción significativa de la <br />
interfáz traducida (más del 75%):<br />
<br />
* Arábico<br />
* Holandés<br />
* Francés<br />
* Alemán<br />
* Griego<br />
* Italiano<br />
* Japonés<br />
* Portugués<br />
* Castellano<br />
* Tamíl<br />
* Vietnamita<br />
<br />
<br />
En total, 25 lenguajes cuentan con más del 50% de la interfaz de usuario <br />
traducida. <br />
<br />
== Compatibilidad ==<br />
La colaboración entre actividades Escribir no funcionará cuando las versiones <br />
de abiword no son las mismas (libabiword 2.6, 2.8).<br />
<br />
== Cambios detallados ==<br />
=== Glucose ===<br />
* [[0.86/Sugar|sugar]]<br />
* [[0.86/sugar-toolkit|sugar-toolkit]]<br />
* [[0.86/sugar-base|sugar-base]]<br />
* [[0.86/sugar-presence-service|sugar-presence-service]]<br />
* [[0.86/sugar-datastore|sugar-datastore]]<br />
* [[0.86/sugar-artwork|sugar-artwork]]<br />
* [[0.86/Etoys|etoys]]<br />
<br />
<br />
== Obtener los fuentes ==<br />
Si quieres empaquetar Sugar para tu distribución favorita, o simplemente <br />
examinar el hermoso código de Sugar ;), puedes encontrar el código fuente de <br />
cada módulo en los enlaces abajo. <br />
<br />
=== Glucose ===<br />
* http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit/sugar-toolkit-0.86.0.tar.bz2<br />
* http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.86.0.tar.bz2<br />
* http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.86.0.tar.bz2<br />
* http://download.sugarlabs.org/sources/sucrose/glucose/sugar-base/sugar-<br />
base-0.86.0.tar.bz2<br />
* http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.86.0.tar.bz2<br />
* http://download.sugarlabs.org/sources/sucrose/glucose/sugar-presence-service/sugar-presence-service-0.86.0.tar.bz2<br />
* http://download.sugarlabs.org/sources/sucrose/glucose/etoys/etoys-4.0.2319.tar.gz<br />
<br />
=== Fructose ===<br />
* http://download.sugarlabs.org/sources/sucrose/fructose/Read/Read-75.tar.bz2<br />
* http://download.sugarlabs.org/sources/sucrose/fructose/Chat/Chat-66.tar.bz2<br />
* http://download.sugarlabs.org/sources/sucrose/fructose/Terminal/Terminal-27.tar.bz2<br />
* http://download.sugarlabs.org/sources/sucrose/fructose/ImageViewer/ImageViewer-13.tar.bz2<br />
* http://download.sugarlabs.org/sources/sucrose/fructose/Jukebox/Jukebox-8.tar.bz2<br />
* http://download.sugarlabs.org/sources/sucrose/fructose/TurtleArt/TurtleArt-69.tar.bz2<br />
* http://download.sugarlabs.org/sources/sucrose/fructose/Browse/Browse-114.tar.bz2<br />
* http://download.sugarlabs.org/sources/sucrose/fructose/Etoys/Etoys-108.tar.gz<br />
* http://download.sugarlabs.org/sources/sucrose/fructose/Write/Write-67.tar.bz2<br />
* http://download.sugarlabs.org/sources/sucrose/fructose/Calculate/Calculate-28.tar.bz2<br />
* http://download.sugarlabs.org/sources/sucrose/fructose/Log/Log-23.tar.bz2<br />
* http://download.sugarlabs.org/sources/sucrose/fructose/Pippy/Pippy-34.tar.bz2<br />
<br />
=== Dependencias de Fructose ===<br />
* http://download.sugarlabs.org/sources/sucrose/glucose/hulahop/hulahop-0.6.0.tar.bz2</div>Aahttps://wiki.sugarlabs.org/index.php?title=0.86/Notes/translations&diff=386400.86/Notes/translations2009-10-01T00:28:07Z<p>Aa: </p>
<hr />
<div>[[0.86/Notes|english]] | [[0.86/Notes/lang-es|spanish]]</div>Aahttps://wiki.sugarlabs.org/index.php?title=0.86/Notes/translations&diff=386390.86/Notes/translations2009-10-01T00:27:31Z<p>Aa: Created page with 'english | spanish'</p>
<hr />
<div>[[Development Team/Jhbuild|english]] | [[Development Team/Jhbuild/lang-es|spanish]]</div>Aahttps://wiki.sugarlabs.org/index.php?title=0.86/Notes&diff=386370.86/Notes2009-10-01T00:24:24Z<p>Aa: </p>
<hr />
<div><noinclude>{{Translations}}{{GoogleTrans-en}}{{TeamHeader|Development Team|roadmap_link={{Upcoming Stable Release}}/Roadmap}}{{TOCright}}</noinclude>[[Category:Release Notes]]<br />
= Sucrose 0.86 Release Notes =<br />
<br />
== Introduction ==<br />
[[Taxonomy#Sucrose:_The_interface.2C_plus_a_set_of_demonstration_activities|Sucrose]] 0.86 is the latest version of the Sugar learning platform, consisting of [[Taxonomy#Glucose:_The_base_Sugar_environment|Glucose]], the base system environment; and [[Taxonomy#Fructose:_The_set_of_demonstration_activities|Fructose]], a set of demonstration activities.<br />
<br />
Sucrose is released every six months. Each new release contains new features, improvements, bug fixes, and translations. Sucrose 0.86 continues this tradition and is our third well-planned release to date.<br />
<br />
You can learn more about Sugar itself by studying the [[What_is_Sugar%3F|Sugar definition]] or by reading the [http://www.sugarlabs.org/index.php?template=page&page=learners comic strip] about the learning platform from Dongyun Lee. Even better, why not [[Downloads|try Sugar]]?<br />
<br />
== What is new for users ==<br />
<br />
=== Activity Toolbar redesign ===<br />
The toolbar used in the Activities has been redesigned. The previous design using small text tabs to group toolbar options together caused a number of usability difficulties. Many of these issues have been addressed in the redesign. For example, the redesign provides a solution for the "how do I stop an activity" issue, pointed out in {{Bug|452}} (the older toolbar design did not provide an always visible "Stop" button, causing confusion for our young learners). Among the Activities, Browse, Write, Calculate, Terminal, Read, ImageViewer, and Turtle Art have already been ported to use the new Toolbar design, while work on many others is under way. See [[Features/New Toolbar Design]] for more details about the new design.<br />
<br clear="all"/><br />
[[Image:0.86_Browse_new_toolbar.png|thumb|none|800px|The new '''Browse''' toolbar design. There is an activity toolbar containing the title entry, the share and the keep button.]]<br />
<br />
[[Image:write_0.86_toolbars.png|thumb|none|800px|The new '''Write''' toolbar design.]]<br />
<br />
=== Switch to Metacity window manager ===<br />
Sugar has [[Features/Metacity|switched]] from Matchbox to a new window manager, [http://en.wikipedia.org/wiki/Metacity Metacity]. Matchbox was designed for small devices; it forces ''all'' applications to run maximized. Sugar can be run on devices with much larger screens, and while activities native to Sugar are designed to be run maximized (full screen), some applications not specifically designed for Sugar can behave in unexpected ways when run with Matchbox. The switch to Metacity means that many "unsugarized" applications will run better inside of Sugar (e.g. Inkscape, Gimp). We endeavour to ensure that "traditional" desktop applications run well in Sugar, without requiring programming or behavioural changes.<br />
<br />
=== Flash Activities ===<br />
[http://www.gnashdev.org/ Gnash] has been added to the Sugar Platform, meaning that authors of education content can use [[Features/Flash_Activities | Flash tools to create first class activities]] for Sugar.<br />
<br />
[[Image:example_gnash_swf_0.86_activity.png|thumb|none|800px|Example activity using an embedded GTK+ '''Gnash''' widget.]]<br />
<br />
=== Tabs in Browse ===<br />
Some web pages contain links that are designed to be opened in a new window. The Browse Activity now opens these links in new tabs inside the main activity window, similar to the behaviour of most common web browsers, thus providing a better browsing experience. Note that this [[Features/Tabs_In_Browse | feature]] does not yet allow the user to explicitly open any link in a new tab or explicitly create a new tab.<br />
<br />
[[Image:browse_0.86_tab_support.png|thumb|none|800px|'''Browse''' with several open tabs.]]<br />
<br />
=== Ad hoc Networking ===<br />
New ad-hoc networking facilities allows you to connect with other Sugar users over wireless in an ad-hoc manner without relying on any wireless networking infrastructure. This is the so called "under-a-tree scenario", where children can work, play, and learn collaboratively in any place imaginable, without requiring any wireless access point, which for many children is unavailable or only available at school. (The One Laptop per Child XO-1 computer provides similar functionality with its firmware-based 802.11s (mesh) network.)[[Features/Ad_hoc_Networking | Ad-hoc networking]] allows Sugar to use this feature with most of the wireless hardware commonly found on computers. Furthermore it allows one to share an Internet connection using the same mechanism. Fore more details see [[Features/Ad_hoc_Networking/Testing|Ad-hoc network testing]].<br />
<br />
[[Image:ad-hoc_0.86_feature.png|thumb|none|400px|Using an ad-hoc local network in Sugar.]]<br />
<br />
=== Read ===<br />
The Read Activity now has support for [http://en.wikipedia.org/wiki/EPUB Epub] files. Epub is a standard format for ebooks which is gaining fast acceptance in the (e)book publishing and distribution community. A number of websites such as [http://www.feedbooks.com feedbooks.com], [http://www.epubbooks.com/ epubbooks.com] and [http://booksearch.blogspot.com/2009/08/download-over-million-public-domain.html Google Books] provide high-quality, Epub books for download at no charge. In addition to Epub support, this release of the Read Activity also lets one associate (add and edit) notes with bookmarks, and it has a more useful full-screen view that roughly indicates battery life without requiring the invocation of the Sugar Frame.<br />
<br />
[[Image:Read_Epub_notes.png|thumb|none|800px|'''Read''' Activity displaying an Epub book.]]<br />
<br />
=== Software Update ===<br />
The [[Features/Sugar_Update_Control_ASLO|software-update control panel]] is now included in standard Sugar. It uses the Sugar [http://activities.sugarlabs.org Activity Library] to check for and install the latest Activity updates available. This makes it easier for users to update to the latest version of a given Activity, and makes smoother for developers to publish and distribute newer version of Activities.<br />
<br />
[[Image:software_update_in_0.86_sugar.png|thumb|none|800px|'''Software update''' (found under ''My Settings'') uses the [http://activities.sugarlabs.org Activity Library] server to find and install new versions of existing installed Activities.]]<br />
<br />
=== Improved Accessibility ===<br />
Some parts of Sugar (Journal and Home list view) have been modified to use Gtk+ widgets, instead of HippoCanvas, which had no accessibility support. This is a part of an ongoing effort to make Sugar work seamlessly with accessibility tools such as screen readers and magnifiers so that everyone can benefit from Sugar, regardless of physical or mental abilities. Among other accessibility enhancements, more Sugar tools now show their keyboard shortcuts to help their discovery and Activities in the activity tray frame use palettes that show both their names and text title.<br />
<br />
[[Image:sugar_neighbourhood_0.86_accelerator.png]]<br />
[[Image:sugar_group_0.86_accelerator.png]]<br />
[[Image:sugar_home_0.86_accelerator.png]]<br />
[[Image:sugar_activity_0.86_accelerator.png]]<br />
<br />
[[Image:activity_and_title_shown_in_frame_palette.png|thumb|none|463px|Both the Activity, and the Activity session Title are now shown in the Activity Frame palette.]]<br />
<br />
=== Keyboard Settings ===<br />
The Sugar control panel (found under ''My Settings'') has a new section for selecting multiple keyboard layouts, as well as the keyboard model. This feature will allow users who do not use the US QWERTY keyboard layout/model to easily switch to their preferred configuration. More information is available in this [[Features/Keyboard_CP_Section|Feature documentation]].<br />
<br />
[[Image:Kpd_cpsection_0.86.png|thumb|none|800px|'''Keyboard''' (found under ''My Settings'') allows different keyboard layouts to be selected from within Sugar.]]<br />
<br />
=== Home Favourites View Improvements ===<br />
Resuming and starting new activities from the Home favourites view has been enhanced by simplifying the Activity palettes so that activities cannot be accidentally deleted or removed from the favourites view. All Activity management is now done via the Home List View. Tip: To quickly start a new activity without using the palette, one hold the <tt><Alt></tt> key and click an activity icon.<br />
<br />
[[Image:simplified_0.86_activity_palette.png|thumb|none|800px|Home favourites Activity pallets are now simpler, Activity management options are now available only in the Home list view.]]<br />
<br />
=== Improved File Transfer ===<br />
The Journal ''"Send to friend"'' feature has been extended to support file transfers via a Jabber server, previously this only worked for machines on the same local network. This now allows one to transfer Journal entries to any available friends, regardless of the underlying communication mechanism (a remote Jabber server, or the local network). One can use the Neighbourhood View to add new friends.<br />
<br />
[[Image:Send-to.png|thumb|none|800px|The Journal '''Send to friend''' feature now works with friends over both local networks and remote Jabber servers.]]<br />
<br />
=== New share button ===<br />
The design of the share button has changed. We hope that the functionality is easier to discover that way.<br />
[[Image:New share button.png|thumb|none|800px|The new share button.]]<br />
<br />
=== Reordered the buddy menu items ===<br />
As requested from the field ({{Bug|1206}}) the order in the buddy menu has been changed. The shutdown options is placed first, as it is the most frequently used. The Restart option has been removed.<br />
[[Image:Reordered buddy menu.png|thumb|none|800px|Reordered buddy menu items.]]<br />
<br />
==Update to this version ==<br />
Please use the instructions for your distribution (SoaS, Fedora, Ubuntu, Debian etc) of choice to upgrade to this release.<br />
<br />
== What's new for developers ==<br />
The following changes are important for developers using the Sucrose 0.86 developer platform.<br />
<br />
=== Widgets ===<br />
* '''New Toolbars:''' Sugar has switched to a new toolbar design. The simplest example can be found in the [http://git.sugarlabs.org/projects/hello-world/repos/mainline/blobs/master/activity.py#line44 hello world] activity. If you want to group functionality into a secondary toolbar you can have a look at the [http://git.sugarlabs.org/projects/terminal/repos/mainline/blobs/master/terminal.py terminal activity]. To have a consistent layout over activities please group the edit and view toolbar to the left. The items on the toolbar should be aligned to the left.<br />
* '''New Share button''': The design of the share button has changed ([[0.86/Notes#New_share_button]]). If your activity does not support collaboration you can set the activity class member max_participants to '1' which makes the share button insensitive.<br />
* '''CellRenderIcon:''' This new widget allows to place sugar svg icons in a gtk.TreeView. The '''CellRendererInvoker''' is used for the palette accordingly.<br />
* '''RadioPalette''': Base class for the ShareButton.<br />
* '''PaletteWindow''': A PaletteWindow widget has been added.<br />
<br />
=== API ===<br />
<br />
* To add the toolbar_box to the activity we use a toolbar_box property now instead of the set_toolbox method.<br />
<br />
=== Dependencies ===<br />
<br />
* Switch from [http://en.wikipedia.org/wiki/Matchbox_%28window_manager%29 Matchbox] to [http://en.wikipedia.org/wiki/Metacity Metacity]. To activity authors this means that their windows need to be user-resizable which in turn requires that the layout adapts changes in window size.<br />
<br />
=== Activity Authors guidelines ===<br />
The md5 and sha module have been deprecated in python 2.6. Please clean up your sources accordingly. We encourage every author, fructose or other activity authors to follow the [[Development_Team/Code_guidelines]]. Please mind that we have the source view functionality enabled and that kids are able to have a look at the code. They hopefully find consistent and well written activities.<br />
<br />
== What's new for packagers ==<br />
* sugar-base: new dependency: [http://pypi.python.org/pypi/decorator python-decorator]<br />
* Sugar: [[Features/Metacity | '''Metacity:''']] The switch to [http://en.wikipedia.org/wiki/Metacity Metacity] as window manager is dependent on this [http://git.gnome.org/cgit/metacity/commit/?id=b625ec30d99b2dcf86d8fa78b09f6d04dce3a6e0 commit] that adds a command line option to disable autofullscreening maximized windows without decorations.<br />
* Sugar: The keyboard control panel: [http://www.freedesktop.org/wiki/Software/LibXklavier libxklavier] >= 4.0, [http://download.sugarlabs.org/sources/external/python-xklavier/ python bindings] >= 0.2<br />
* [[Features/Flash Activities | '''Flash Activities:''']] Distributions need to package the last version of Gnash (v9).<br />
* [[Features/Tabs In Browse | '''Tabs in Browse:''']] Hulahop version >= 0.5<br />
* [[Activities/Write | '''Write:''']] Abiword 2.8 is close to be released and will be part of the Sugar Platform 0.86, so we need to have the latest release in the 2.7.x series packaged so we start testing it.<br />
* [[Activities/Read | '''Read:''']] New dependencies for Read version >= 70 (needed for epub support): webkitgtk (Note: [http://code.google.com/p/pywebkitgtk/downloads/list pywebkitgtk] has to be >= 1.1.6), python-lxml, python-BeautifulSoup,<br />
* [[0.86/sugar-datastore | '''sugar-datastore:''']] LICENSE.GPL, README.txt files were renamed to COPYING and README; added AUTHORS and NEWS new files.<br />
<br />
== Internationalization (i18n) and Localization (l10n) ==<br />
Thanks to members of the worldwide translation team, who can be found on the [http://lists.laptop.org/listinfo/localization localization mailing list], we have the following languages (listed alphabetically) which have significant support (more than 75% of the user interface translated):<br />
<br />
* Arabic<br />
* Dutch<br />
* French<br />
* German<br />
* Greek<br />
* Italian<br />
* Japanese<br />
* Portuguese<br />
* Spanish<br />
* Tamil<br />
* Vietnamese<br />
<br />
<br />
Altogether, 25 languages have more than 50% of the user interface translated.<br />
<br />
== Compatibility ==<br />
Collaboration in the Write activity will not work when the abiword backend is not the same (libabiword 2.6, 2.8).<br />
<br />
== Detailed changes ==<br />
=== Glucose ===<br />
* [[0.86/Sugar|sugar]]<br />
* [[0.86/sugar-toolkit|sugar-toolkit]]<br />
* [[0.86/sugar-base|sugar-base]]<br />
* [[0.86/sugar-presence-service|sugar-presence-service]]<br />
* [[0.86/sugar-datastore|sugar-datastore]]<br />
* [[0.86/sugar-artwork|sugar-artwork]]<br />
* [[0.86/Etoys|etoys]]<br />
<br />
=== Fructose ===<br />
[[Image:fructose_0.86.0_activity_icons.png|thumb|right|290px|'''Fructose''' Activities help provide a base level of functionality that demonstrate Sugar and some of its core features.]]<br />
* [[0.86/Terminal|Terminal]]<br />
* [[0.86/Log|Log]]<br />
* [[0.86/Read|Read]]<br />
* [[0.86/Browse|Browse]]<br />
* [[0.86/Chat|Chat]]<br />
* [[0.86/Write|Write]]<br />
* [[0.86/Calculate|Calculate]]<br />
* [[0.86/Image Viewer|Image Viewer]]<br />
* [[0.86/Jukebox|Jukebox]] <br />
* [[0.86/TurtleArt|TurtleArt]]<br />
* [[0.86/Etoys|Etoys]]<br />
* [[0.86/Pippy|Pippy]]<br />
<br />
=== Fructose dependencies ===<br />
* [[0.86/hulahop|hulahop]]<br />
<br />
== Getting the sources ==<br />
If you want to package sugar for your favourite distribution or just want to examine sugar's lovely code ;) you can find all the source code of each module at the links below. <br />
<br />
=== Glucose ===<br />
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit/sugar-toolkit-0.86.0.tar.bz2 sugar-toolkit 0.86.0]<br />
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.86.0.tar.bz2 sugar 0.86.0]<br />
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.86.0.tar.bz2 sugar-artwork 0.86.0]<br />
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-base/sugar-base-0.86.0.tar.bz2 sugar-base 0.86.0]<br />
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.86.0.tar.bz2 sugar-datastore 0.86.0]<br />
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-presence-service/sugar-presence-service-0.86.0.tar.bz2 sugar-presence-service 0.86.0]<br />
* [http://download.sugarlabs.org/sources/sucrose/glucose/etoys/etoys-4.0.2319.tar.gz etoys 4.0.2319]<br />
<br />
=== Fructose ===<br />
* [http://download.sugarlabs.org/sources/sucrose/fructose/Read/Read-75.tar.bz2 read 75]<br />
* [http://download.sugarlabs.org/sources/sucrose/fructose/Chat/Chat-66.tar.bz2 chat 66]<br />
* [http://download.sugarlabs.org/sources/sucrose/fructose/Terminal/Terminal-27.tar.bz2 terminal 27]<br />
* [http://download.sugarlabs.org/sources/sucrose/fructose/ImageViewer/ImageViewer-13.tar.bz2 imageviewer 13]<br />
* [http://download.sugarlabs.org/sources/sucrose/fructose/Jukebox/Jukebox-8.tar.bz2 jukebox 8]<br />
* [http://download.sugarlabs.org/sources/sucrose/fructose/TurtleArt/TurtleArt-69.tar.bz2 turtleart 69]<br />
* [http://download.sugarlabs.org/sources/sucrose/fructose/Browse/Browse-114.tar.bz2 browse 114]<br />
* [http://download.sugarlabs.org/sources/sucrose/fructose/Etoys/Etoys-108.tar.gz etoys 108]<br />
* [http://download.sugarlabs.org/sources/sucrose/fructose/Write/Write-67.tar.bz2 write 67]<br />
* [http://download.sugarlabs.org/sources/sucrose/fructose/Calculate/Calculate-28.tar.bz2 calculate 28]<br />
* [http://download.sugarlabs.org/sources/sucrose/fructose/Log/Log-23.tar.bz2 log 23]<br />
* [http://download.sugarlabs.org/sources/sucrose/fructose/Pippy/Pippy-34.tar.bz2 pippy 34]<br />
<br />
=== Fructose dependencies ===<br />
* [http://download.sugarlabs.org/sources/sucrose/glucose/hulahop/hulahop-0.6.0.tar.bz2 hulahop 0.6.0]<br />
<br />
== Looking at the release cycle details ==<br />
You can browse the notes of each development release in [[{{Upcoming Stable Release}}]]. Their respective sources are listed there as well.<br />
<br />
== Looking Forward to 0.88 ==<br />
Planning of the next release cycle has started at [[0.88/Roadmap]].<br />
<br />
== Credits ==<br />
Many people contributed to this release indirectly, including testing, documentation, translation, contributing to the Wiki, outreach to education and developer communities. On behalf of the community, we give our warmest thanks to the developers and contributors who made this Sugar release possible.</div>Aahttps://wiki.sugarlabs.org/index.php?title=Marketing_Team/Events/LinuxTag2009&diff=30446Marketing Team/Events/LinuxTag20092009-06-12T19:07:55Z<p>Aa: /* Sugar activities */</p>
<hr />
<div>= LinuxTag 2009 =<br />
<br />
== Event Details ==<br />
<br />
For more information, go to the [http://www.linuxtag.org/2009/en.html LinuxTag 2009 website].<br />
<br />
== Sugar Organizer ==<br />
<br />
[[User:Erikos | Simon Schampijer | simon at sugarlabs dot org]] will be organizing Sugar's presence at LinuxTag 2009.<br />
<br />
== Attendees ==<br />
<br />
Are you planning to attend? Add your name and contact info below!<br />
<br />
# [[User:Sdz | Sebastian Dziallas]]<br />
# [[User:nubae | David Van Assche]]<br />
# [[User:fab | Fabian Affolter]]<br />
# [[User:jzGreen | James Zaki]]<br />
# [[User:SeanDaly | Sean Daly]]<br />
<br />
== Sugar activities ==<br />
<br />
# We will have a booth located at 7.2a 110a. We share this booth with our friends from:<br />
## [http://www.olpc-deutschland.de/ OLPC Deutschland e.V.]<br />
## [http://www.squeak.de/ Squeak Germany]<br />
## [http://wiki.skolelinux.de/LinuxTag2009 Skolelinux Germany]<br />
## [http://www.linux4afrika.de/ Linux4Afrika]<br />
## [http://www.x2go.org X2go]<br />
# Greg gives the talk: "Education, Innovation, and Free Software"<br />
# Simon gives the talk: [http://www.linuxtag.org/2009/de/program/freies-vortragsprogramm/mittwoch/vortragsdetails.html?talkid=791 Sugar - a software playground for learning about learning"] (Saturday, 27.06 - 17.00 Saal 5)<br />
# Sebastian will be giving a barcamp session at FUDCon about various educational efforts, mainly SoaS<br />
# Pablo Casal and Eduardo Blanco from Netlabs are giving the talk: "Plan Ceibal - A country-wide OLPC deployment in Uruguay" (Saturday 27.06 - 16.00 Saal 5). They designed the initial proposal for Ceibal's network, and are currently consultors for the project.<br />
<br />
== Sugar Booth ==<br />
Our booth will be at 7.2a 110a. <br />
<br />
Please list your availability and german skills if you are interested in helping with the booth. Or if you already know which shifts you want to take, feel free to add yourself in the second table. Ideally a shift is two people, but given the space reserved at the booth size I think we can get away with one as well. Helping at the booth means answering questions regarding Sugar and Sugar Labs, demoing Sugar and flashing Soas on request. People helping at the booth will get a Linuxtag ticket.<br />
<br />
Availability:<br />
<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Name !! German !! 24.06.09 !! 25.06.09 !! 26.06.09 !! 27.06.09 !! Note<br />
|-<br />
! Schampijer<br />
| Native || yes || yes || yes || not available from 16.00 to 18.00 as he has a talk there || is there in the mornings to make sure everything is set up <br />
|-<br />
! Tomeu<br />
| None || ? || ? || full day? || full day || x<br />
|-<br />
|}<br />
<br />
Plan:<br />
<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Day !! 10.00-12.00 !! 12.00-14.00 !! 14.00-16.00 !! 16.00-18.00<br />
|-<br />
! 24.06.09<br />
| Schampijer || x || x || x<br />
|-<br />
! 25.06.09<br />
| Schampijer || x || x || x<br />
|-<br />
! 26.06.09<br />
| Sean || x || Sean || x<br />
|-<br />
! 27.06.09<br />
| x || Sean || x || Sean<br />
|-<br />
|}<br />
<br />
== TODO ==<br />
<br />
# We need a banner for the booth<br />
<br />
I have ordered one with an option for a second. [[user:SeanDaly | Sean]]<br />
<br />
== Lodging ==<br />
* Accommodation Information from [http://www.linuxtag.org/2008/en/visitors/travel.html Linuxtag]<br />
* [http://www.pension-freiraum.de/ Pension Freiraum]<br />
** Nice area with bars restaurant cafe, about 25 minutes to the conference<br />
* [http://www.hotel-funkturm-messe.de/english/home.html Hotel Funkturm]<br />
** right next door to the conference area (room 4-6 persons, 100euro per night for the room, inclusive breakfast)<br />
<br />
== Schedule ==<br />
<br />
More info as it becomes available.<br />
<br />
[[Category:Event]]</div>Aahttps://wiki.sugarlabs.org/index.php?title=Development_Team/Jhbuild/lang-es&diff=27949Development Team/Jhbuild/lang-es2009-04-24T07:57:03Z<p>Aa: </p>
<hr />
<div>{{Translation<br />
| lang = es<br />
| source = Development Team/Jhbuild<br />
| version = 27498}}<br />
<br />
{{ 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 }}<br />
<br />
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. <br />
<br />
{{anchor|Compatible platforms}}<br />
== Plataformas compatibles ==<br />
<br />
{{ 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.<br />
<br />
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 }}<br />
<br />
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. <br />
<br />
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).<br />
<br />
{{anchor|Check distro-specific instructions}}<br />
== Consulte las instrucciones específicas a una distro ==<br />
<br />
{{ 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}}<br />
<br />
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:<br />
<br />
* [[../Debian|Debian]]<br />
* [[../Fedora|Fedora]]<br />
* [[../Ubuntu|Ubuntu]]<br />
* [[../Mandriva|Mandriva]]<br />
<br />
{{anchor|Check out sugar-jhbuild}}<br />
== Checkout de sugar-jhbuild ==<br />
<br />
{{ Translated text| <br />
In a suitable directory, execute<br />
<br />
git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild | display = None }}<br />
<br />
En un directorio adecuado ejecute:<br />
<br />
git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild<br />
<br />
{{anchor|Build sugar base system and its dependencies}}<br />
== Construír Sugar y sus dependencias ==<br />
<br />
{{ Translated text | Change directory and start the build.<br />
<br />
cd sugar-jhbuild<br />
./sugar-jhbuild update<br />
./sugar-jhbuild depscheck<br />
./sugar-jhbuild build | display = None }}<br />
<br />
Cambie de directorio y comience la construcción:<br />
<br />
cd sugar-jhbuild<br />
./sugar-jhbuild update<br />
./sugar-jhbuild depscheck<br />
./sugar-jhbuild build<br />
<br />
{{anchor|Dealing with dependencies}}<br />
=== Ocupándose de las dependencias === <br />
<br />
{{ 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 }}<br />
<br />
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]<br />
<br />
{{ Translated text | Some tips:<br />
* 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 }}<br />
<br />
Algunos consejos:<br />
* 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.<br />
<br />
{{anchor|Run Sugar}}<br />
== Correr Sugar ==<br />
<br />
{{ Translated text | This command launches the Sugar emulator:<br />
<br />
./sugar-jhbuild run<br />
<br />
To exit the emulator, press Alt-Q. | display = None }}<br />
<br />
Este comando lanza el emulador de Sugar<br />
<br />
./sugar-jhbuild run<br />
<br />
Para salir del emulador, presione Alt-Q.<br />
<br />
{{anchor|Running multiple instances}}<br />
== Corriendo múltiples instancias ==<br />
<br />
{{Translated text | To run multiple instances of sugar you can start it in the following way:<br />
<br />
SUGAR_PROFILE=2 ./sugar-jhbuild run<br />
<br />
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 }}<br />
<br />
Para correr múltiples instancias de Sugar, puede lanzarlo de la manera siguiente:<br />
<br />
SUGAR_PROFILE=2 ./sugar-jhbuild run<br />
<br />
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/<br />
<br />
{{anchor|Run an individual activity}}<br />
== Correr una actividad individual ==<br />
<br />
{{Translated text | <br />
Within sugar, e.g. in Terminal, this command launches an individual activity for testing:<br />
<br />
sugar-launch [bundle name]<br />
<br />
You will see debug output appearing in Terminal. | display = None }}<br />
<br />
Dentro de Sugar, por ej, en Terminal, este comando lanza una actividad individual para probarla:<br />
<br />
sugar-launch [nombre del bundle]<br />
<br />
Verá salida de depuración apareciendo en Terminal.<br />
<br />
{{anchor|Configure the mode and resolution of Sugar}}<br />
== Configurar el modo y la resolución de Sugar ==<br />
<br />
{{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''':<br />
<br />
cd sugar-jhbuild<br />
cp install/bin/sugar-emulator install/bin/sugar-emulator.backup<br />
nano install/bin/sugar-emulator<br />
<br />
Find this piece of code: | display = None }}<br />
<br />
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''':<br />
<br />
cd sugar-jhbuild<br />
cp install/bin/sugar-emulator install/bin/sugar-emulator.backup<br />
nano install/bin/sugar-emulato<br />
<br />
Busque este pedazo de código: <br />
<br />
<PRE><br />
cmd = [ 'Xephyr' ]<br />
cmd.append(':%d' % display)<br />
cmd.append('-ac')<br />
<br />
if gtk.gdk.screen_width() < 1200 or gtk.gdk.screen_height() < 900:<br />
cmd.append('-fullscreen')<br />
else:<br />
cmd.append('-screen')<br />
cmd.append('%dx%d' % (1200, 900))<br />
</PRE> <br />
<br />
{{Translated text | <br />
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}}<br />
<br />
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"):<br />
<br />
<PRE><br />
cmd = [ 'Xephyr' ]<br />
cmd.append(':%d' % display)<br />
cmd.append('-ac')<br />
<br />
# if gtk.gdk.screen_width() < 1200 or gtk.gdk.screen_height() < 900:<br />
# cmd.append('-fullscreen')<br />
# else:<br />
cmd.append('-screen')<br />
cmd.append('%dx%d' % (800, 600))<br />
</PRE><br />
<br />
{{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.<br />
| display = None }}<br />
<br />
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.<br />
<br />
{{anchor|Other commands}}<br />
== Otras órdenes ==<br />
<br />
{{Translated text | <br />
JHBuild has several other commands that can be useful for development. You can get an overview with:<br />
<br />
./sugar-jhbuild --help-commands<br />
<br />
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.)<br />
<br />
./sugar-jhbuild update<br />
./sugar-jhbuild build<br />
./sugar-jhbuild run | display = None}}<br />
<br />
JHBuild tiene varias órdenes más que pueden ser útiles para el desarrollo. Puede obtener una descripción general con:<br />
<br />
./sugar-jhbuild --help-commands<br />
<br />
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.)<br />
<br />
./sugar-jhbuild update<br />
./sugar-jhbuild build<br />
./sugar-jhbuild run<br />
<br />
{{anchor|If build breaks after an update}}<br />
== Si la construcción se rompe luego de un update ==<br />
<br />
{{Translated text | <br />
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<br />
./sugar-jhbuild depscheck<br />
regularly and install the missing packages.<br />
<br />
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 }}<br />
<br />
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<br />
./sugar-jhbuild depscheck<br />
regularmente y de instalar los paquetes faltantes. <br />
<br />
{{anchor|From within Sugar}}<br />
== Desde dentro de Sugar ==<br />
<br />
{{Translated text | Once you have Sugar running, here are some useful commands:<br />
*'''Alt+Shift+F''' makes the frame appear and disappear<br />
*'''Ctrl-Q''' quits an activity<br />
*'''Alt+Shift+Q''' quits Sugar<br />
*'''Alt+Shift+O''' opens the search<br />
*'''Alt+Shift+R''' rotates the screen | display = None }}<br />
<br />
una vez que tenga Sugar corriendo, aquí hay algunas órdenes útiles:<br />
*'''Alt+Shift+F''' hace aparecer y desaparecer al marco<br />
*'''Ctrl-Q''' sale de una actividad<br />
*'''Alt+Shift+Q''' sale de Sugar<br />
*'''Alt+Shift+O''' abre la búsqueda<br />
*'''Alt+Shift+R''' rota la pantalla<br />
<br />
{{anchor|Customize}}<br />
== Personalizar ==<br />
<br />
{{Translated text |To customize the build create a configuration file, named ''.sugar.jhbuildrc'', in your home directory. | display = None }}<br />
Para personalizar la construcción, cree un archivo de configuración, llamado ''.sugar.jhbuildrc'', en su directorio home. <br />
<br />
{{anchor|Write access to the repositories}}<br />
=== Acceso de escritura a los repositorios ===<br />
<br />
{{Translated text | <br />
If you have write access to the repositories you can add this (if your login name happens to be marco): | display = None }}<br />
<br />
Si tiene acceso de escritura a los repositorios puede agregar esto (si su nombre de usuario fuera marco):<br />
repos['gnome.org'] = ':ext:marco@cvs.gnome.org:/cvs/gnome'<br />
repos['mozilla.org'] = ':ext:marco%gnome.org@cvs.mozilla.org:/cvsroot'<br />
repos['dev.laptop.org'] = 'git+ssh://marco@dev.laptop.org/git/'<br />
repos['dev.laptop.org/projects'] = 'git+ssh://marco@dev.laptop.org/git/projects/'<br />
<br />
{{anchor|Useful Internal Links}}<br />
== Enlaces internos útiles == <br />
{{Translated text | * [[Development Team/Understanding the Code|Understanding Sugar Code]]<br />
* [[Taxonomy]] -- explains the components of Sugar (Glucose, Fructose, Sugar, Starches)<br />
* [[Sugar Instructions]] -- how to actually use Sugar once you have it running | display = None }}<br />
<br />
* [[Development Team/Understanding the Code/lang-es|Entendiendo el código de Sugar]]<br />
* [[Taxonomy/lang-es|Taxonomía]] -- explica los componentes de Sugar (Glucosa, Fructosa, Azúcar (Sugar), Almidones)<br />
* [[Sugar Instructions/lang-es|Instrucciones de Sugar]] -- cómo usar Sugar una vez que está corriendo<br />
<br />
{{anchor|External links}}<br />
== Enlaces externos ==<br />
<br />
{{Translated text | * [http://library.gnome.org/devel/jhbuild/unstable/ JHBuild manual]<br />
* [http://www.redhatmagazine.com/2007/02/23/building-the-xo-introducing-sugar/ Red Hat Magazine article: Introducing Sugar]<br />
* [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 }}<br />
<br />
<br />
* [http://library.gnome.org/devel/jhbuild/unstable/ Manual de JHBuild]<br />
* [http://www.redhatmagazine.com/2007/02/23/building-the-xo-introducing-sugar/ Artículo de Red Hat Magazine: Presentando Sugar]<br />
* [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].<br />
<br />
[[Category:Installing Sugar]]<br />
[[Category:Jhbuild]]</div>Aahttps://wiki.sugarlabs.org/index.php?title=Development_Team/Jhbuild/lang-es&diff=27948Development Team/Jhbuild/lang-es2009-04-24T07:56:12Z<p>Aa: </p>
<hr />
<div>{{Translation<br />
| lang = es<br />
| source = Development Team/jhbuild<br />
| version = 27498}}<br />
{{Translation in Progress}}<br />
<br />
{{ 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 }}<br />
<br />
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. <br />
<br />
{{anchor|Compatible platforms}}<br />
== Plataformas compatibles ==<br />
<br />
{{ 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.<br />
<br />
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 }}<br />
<br />
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. <br />
<br />
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).<br />
<br />
{{anchor|Check distro-specific instructions}}<br />
== Consulte las instrucciones específicas a una distro ==<br />
<br />
{{ 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}}<br />
<br />
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:<br />
<br />
* [[../Debian|Debian]]<br />
* [[../Fedora|Fedora]]<br />
* [[../Ubuntu|Ubuntu]]<br />
* [[../Mandriva|Mandriva]]<br />
<br />
{{anchor|Check out sugar-jhbuild}}<br />
== Checkout de sugar-jhbuild ==<br />
<br />
{{ Translated text| <br />
In a suitable directory, execute<br />
<br />
git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild | display = None }}<br />
<br />
En un directorio adecuado ejecute:<br />
<br />
git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild<br />
<br />
{{anchor|Build sugar base system and its dependencies}}<br />
== Construír Sugar y sus dependencias ==<br />
<br />
{{ Translated text | Change directory and start the build.<br />
<br />
cd sugar-jhbuild<br />
./sugar-jhbuild update<br />
./sugar-jhbuild depscheck<br />
./sugar-jhbuild build | display = None }}<br />
<br />
Cambie de directorio y comience la construcción:<br />
<br />
cd sugar-jhbuild<br />
./sugar-jhbuild update<br />
./sugar-jhbuild depscheck<br />
./sugar-jhbuild build<br />
<br />
{{anchor|Dealing with dependencies}}<br />
=== Ocupándose de las dependencias === <br />
<br />
{{ 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 }}<br />
<br />
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]<br />
<br />
{{ Translated text | Some tips:<br />
* 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 }}<br />
<br />
Algunos consejos:<br />
* 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.<br />
<br />
{{anchor|Run Sugar}}<br />
== Correr Sugar ==<br />
<br />
{{ Translated text | This command launches the Sugar emulator:<br />
<br />
./sugar-jhbuild run<br />
<br />
To exit the emulator, press Alt-Q. | display = None }}<br />
<br />
Este comando lanza el emulador de Sugar<br />
<br />
./sugar-jhbuild run<br />
<br />
Para salir del emulador, presione Alt-Q.<br />
<br />
{{anchor|Running multiple instances}}<br />
== Corriendo múltiples instancias ==<br />
<br />
{{Translated text | To run multiple instances of sugar you can start it in the following way:<br />
<br />
SUGAR_PROFILE=2 ./sugar-jhbuild run<br />
<br />
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 }}<br />
<br />
Para correr múltiples instancias de Sugar, puede lanzarlo de la manera siguiente:<br />
<br />
SUGAR_PROFILE=2 ./sugar-jhbuild run<br />
<br />
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/<br />
<br />
{{anchor|Run an individual activity}}<br />
== Correr una actividad individual ==<br />
<br />
{{Translated text | <br />
Within sugar, e.g. in Terminal, this command launches an individual activity for testing:<br />
<br />
sugar-launch [bundle name]<br />
<br />
You will see debug output appearing in Terminal. | display = None }}<br />
<br />
Dentro de Sugar, por ej, en Terminal, este comando lanza una actividad individual para probarla:<br />
<br />
sugar-launch [nombre del bundle]<br />
<br />
Verá salida de depuración apareciendo en Terminal.<br />
<br />
{{anchor|Configure the mode and resolution of Sugar}}<br />
== Configurar el modo y la resolución de Sugar ==<br />
<br />
{{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''':<br />
<br />
cd sugar-jhbuild<br />
cp install/bin/sugar-emulator install/bin/sugar-emulator.backup<br />
nano install/bin/sugar-emulator<br />
<br />
Find this piece of code: | display = None }}<br />
<br />
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''':<br />
<br />
cd sugar-jhbuild<br />
cp install/bin/sugar-emulator install/bin/sugar-emulator.backup<br />
nano install/bin/sugar-emulato<br />
<br />
Busque este pedazo de código: <br />
<br />
<PRE><br />
cmd = [ 'Xephyr' ]<br />
cmd.append(':%d' % display)<br />
cmd.append('-ac')<br />
<br />
if gtk.gdk.screen_width() < 1200 or gtk.gdk.screen_height() < 900:<br />
cmd.append('-fullscreen')<br />
else:<br />
cmd.append('-screen')<br />
cmd.append('%dx%d' % (1200, 900))<br />
</PRE> <br />
<br />
{{Translated text | <br />
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}}<br />
<br />
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"):<br />
<br />
<PRE><br />
cmd = [ 'Xephyr' ]<br />
cmd.append(':%d' % display)<br />
cmd.append('-ac')<br />
<br />
# if gtk.gdk.screen_width() < 1200 or gtk.gdk.screen_height() < 900:<br />
# cmd.append('-fullscreen')<br />
# else:<br />
cmd.append('-screen')<br />
cmd.append('%dx%d' % (800, 600))<br />
</PRE><br />
<br />
{{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.<br />
| display = None }}<br />
<br />
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.<br />
<br />
{{anchor|Other commands}}<br />
== Otras órdenes ==<br />
<br />
{{Translated text | <br />
JHBuild has several other commands that can be useful for development. You can get an overview with:<br />
<br />
./sugar-jhbuild --help-commands<br />
<br />
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.)<br />
<br />
./sugar-jhbuild update<br />
./sugar-jhbuild build<br />
./sugar-jhbuild run | display = None}}<br />
<br />
JHBuild tiene varias órdenes más que pueden ser útiles para el desarrollo. Puede obtener una descripción general con:<br />
<br />
./sugar-jhbuild --help-commands<br />
<br />
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.)<br />
<br />
./sugar-jhbuild update<br />
./sugar-jhbuild build<br />
./sugar-jhbuild run<br />
<br />
{{anchor|If build breaks after an update}}<br />
== Si la construcción se rompe luego de un update ==<br />
<br />
{{Translated text | <br />
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<br />
./sugar-jhbuild depscheck<br />
regularly and install the missing packages.<br />
<br />
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 }}<br />
<br />
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<br />
./sugar-jhbuild depscheck<br />
regularmente y de instalar los paquetes faltantes. <br />
<br />
{{anchor|From within Sugar}}<br />
== Desde dentro de Sugar ==<br />
<br />
{{Translated text | Once you have Sugar running, here are some useful commands:<br />
*'''Alt+Shift+F''' makes the frame appear and disappear<br />
*'''Ctrl-Q''' quits an activity<br />
*'''Alt+Shift+Q''' quits Sugar<br />
*'''Alt+Shift+O''' opens the search<br />
*'''Alt+Shift+R''' rotates the screen | display = None }}<br />
<br />
una vez que tenga Sugar corriendo, aquí hay algunas órdenes útiles:<br />
*'''Alt+Shift+F''' hace aparecer y desaparecer al marco<br />
*'''Ctrl-Q''' sale de una actividad<br />
*'''Alt+Shift+Q''' sale de Sugar<br />
*'''Alt+Shift+O''' abre la búsqueda<br />
*'''Alt+Shift+R''' rota la pantalla<br />
<br />
{{anchor|Customize}}<br />
== Personalizar ==<br />
<br />
{{Translated text |To customize the build create a configuration file, named ''.sugar.jhbuildrc'', in your home directory. | display = None }}<br />
Para personalizar la construcción, cree un archivo de configuración, llamado ''.sugar.jhbuildrc'', en su directorio home. <br />
<br />
{{anchor|Write access to the repositories}}<br />
=== Acceso de escritura a los repositorios ===<br />
<br />
{{Translated text | <br />
If you have write access to the repositories you can add this (if your login name happens to be marco): | display = None }}<br />
<br />
Si tiene acceso de escritura a los repositorios puede agregar esto (si su nombre de usuario fuera marco):<br />
repos['gnome.org'] = ':ext:marco@cvs.gnome.org:/cvs/gnome'<br />
repos['mozilla.org'] = ':ext:marco%gnome.org@cvs.mozilla.org:/cvsroot'<br />
repos['dev.laptop.org'] = 'git+ssh://marco@dev.laptop.org/git/'<br />
repos['dev.laptop.org/projects'] = 'git+ssh://marco@dev.laptop.org/git/projects/'<br />
<br />
{{anchor|Useful Internal Links}}<br />
== Enlaces internos útiles == <br />
{{Translated text | * [[Development Team/Understanding the Code|Understanding Sugar Code]]<br />
* [[Taxonomy]] -- explains the components of Sugar (Glucose, Fructose, Sugar, Starches)<br />
* [[Sugar Instructions]] -- how to actually use Sugar once you have it running | display = None }}<br />
<br />
* [[Development Team/Understanding the Code/lang-es|Entendiendo el código de Sugar]]<br />
* [[Taxonomy/lang-es|Taxonomía]] -- explica los componentes de Sugar (Glucosa, Fructosa, Azúcar (Sugar), Almidones)<br />
* [[Sugar Instructions/lang-es|Instrucciones de Sugar]] -- cómo usar Sugar una vez que está corriendo<br />
<br />
{{anchor|External links}}<br />
== Enlaces externos ==<br />
<br />
{{Translated text | * [http://library.gnome.org/devel/jhbuild/unstable/ JHBuild manual]<br />
* [http://www.redhatmagazine.com/2007/02/23/building-the-xo-introducing-sugar/ Red Hat Magazine article: Introducing Sugar]<br />
* [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 }}<br />
<br />
<br />
* [http://library.gnome.org/devel/jhbuild/unstable/ Manual de JHBuild]<br />
* [http://www.redhatmagazine.com/2007/02/23/building-the-xo-introducing-sugar/ Artículo de Red Hat Magazine: Presentando Sugar]<br />
* [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].<br />
<br />
[[Category:Installing Sugar]]<br />
[[Category:Jhbuild]]</div>Aahttps://wiki.sugarlabs.org/index.php?title=Development_Team/Jhbuild/lang-es&diff=27942Development Team/Jhbuild/lang-es2009-04-24T06:49:03Z<p>Aa: New page: {{Translation | lang = es | source = Development Team/jhbuild | version = 27498}} {{Translation in Progress}}</p>
<hr />
<div>{{Translation<br />
| lang = es<br />
| source = Development Team/jhbuild<br />
| version = 27498}}<br />
{{Translation in Progress}}</div>Aahttps://wiki.sugarlabs.org/index.php?title=Development_Team/Jhbuild/translations&diff=27941Development Team/Jhbuild/translations2009-04-24T06:46:29Z<p>Aa: </p>
<hr />
<div>[[Development Team/Jhbuild|english]] | [[Development Team/Jhbuild/lang-ja|日本語]] | [[Development Team/Jhbuild/lang-es|spanish]]</div>Aahttps://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Interviews&diff=27366Summer of Code/Interviews2009-04-13T19:22:54Z<p>Aa: </p>
<hr />
<div>We would like to interview the candidates for Google Summer of Code under Sugar Labs. Please sign up for a time below. If you have been told the name of your provisional prospective mentor, and your mentor has put his/her preferred times below, please try to find a time which works for your mentor. (Note that mentor assignments are still in flux; if your provisional prospective mentor changes, we will try to accommodate your chosen time or reschedule at a convenient time for you.)<br />
<br />
Interviews will be conducted over IRC; even hours on #sugar-interview0 and half-hours on #sugar-interview1 . Please treat these like real rooms, ie, do not lurk unless you are a mentor. If you have some quick pre-interview questions, we will be in #sugar too.<br />
<br />
If you have specifically been told to sign up to interview, please sign up here. Even if your provisional prospective mentor has not indicated availability, put your available times, and your mentor will renegotiate with you later if necessary. We have invited the 9-10 proposals which are currently ranked highest, for the 4-6 slots we will probably get. However, we ''do'' want to interview you even if you have not specifically been invited; although your proposal is a long shot in that case, you may impress us, and in any case we'd like to talk to you about participating in Sugar outside of GSoC.<br />
<br />
Like many other organizations participating in GSoC, we have received more good applications than we will have funding from Google for. Almost all of our applications would be things that we'd really love to have you working on, even if we don't have space for you in GSoC. If you are interested in finishing your project and would like a mentor assigned even though we can't give you a slot, you can also contact us on the sugar-devel or gsoc mailing list and we'll work something out.<br />
<br />
== Sunday Apr 1 ==<br />
<br />
Mentors attending: Guido van Rossum, Linus Torvalds, Bill Gates ...<br />
<br />
* [http://www.timeanddate.com/counters/customcounter.html?day=1&month=04&year=2009&hour=14&min=0&sec=0&p0=0 1400 UTC]: [[User:example|example]] 18:11, 13 April 2009 (UTC) (Spanish interview preferred) (just an example - I used <nowiki>~~~~</nowiki> to add a signature, and added any special requests after.)<br />
<br />
== Wed Apr 15 ==<br />
<br />
Mentors attending: Jameson Quinn, [[User:BryanWB|BryanWB]], Luis G. Lira, [[User:Aa|aa]] ...<br />
<br />
* [http://www.timeanddate.com/counters/customcounter.html?day=15&month=04&year=2009&hour=14&min=0&sec=0&p0=0 1400 UTC]: Vamsi Krishna Davuluri (iwikiwi)<br />
<br />
* 1430 UTC: <br />
<br />
* 1500 UTC: Lucian Branescu (lucian1900)<br />
<br />
* 1530 UTC:<br />
<br />
== Thurs Apr 16 (Wed 15 in the western hemisphere) ==<br />
<br />
Mentors attending: Jameson Quinn, [[User:Aa|aa]], [[User:BryanWB|BryanWB]], [[User:Nrp|Nirav Patel]] ...<br />
<br />
* [http://www.timeanddate.com/counters/customcounter.html?day=16&month=04&year=2009&hour=0&min=0&sec=0&p0=0 0000 UTC]:<br />
<br />
* 0030 UTC:<br />
<br />
* 0100 UTC:<br />
<br />
* 0130 UTC:<br />
<br />
== Thurs Apr 16 ==<br />
<br />
Mentors attending: Jameson Quinn, Sayamindu Dasgupta ...<br />
<br />
* [http://www.timeanddate.com/counters/customcounter.html?day=16&month=04&year=2009&hour=18&min=0&sec=0&p0=0 1800 UTC]:<br />
<br />
* 1830 UTC:<br />
<br />
* 1900 UTC:<br />
<br />
* 1930 UTC:</div>Aahttps://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Interviews&diff=27288Summer of Code/Interviews2009-04-12T23:54:01Z<p>Aa: </p>
<hr />
<div>We would like to interview the top candidates for Google Summer of Code under Sugar Labs. Please sign up for a time below. If you have been told the name of your provisional prospective mentor, and your mentor has put his/her preferred times below, please try to find a time which works for your mentor. (Note that mentor assignments are still in flux; if your provisional prospective mentor changes, we will try to accomadate your chosen time or reschedule at a convenient time for you.)<br />
<br />
If you have not been told to sign up to interview (through a public comment on your application), please do not sign up here. Interview time is limited, and we are trying to interview the applicants with the best chances of admission. Like many other organizations participating in GSoC, we have received more good applications than we have funding for interviews. Almost all of our applications would be things that we'd really love to have you working on, even if we don't have space for you in GSoC. If you are interested in finishing your project and would like a mentor assigned even though we can't give you a slot, please contact us on the sugar-devel or gsoc mailing list and we'll work something out.<br />
<br />
== Wed Apr 15 ==<br />
<br />
Mentors attending: Jameson Quinn, ...<br />
<br />
* [http://www.timeanddate.com/counters/customcounter.html?day=15&month=04&year=2009&hour=14&min=0&sec=0&p0=0 1400 UTC]:<br />
<br />
* 1430 UTC:<br />
<br />
* 1500 UTC:<br />
<br />
* 1530 UTC:<br />
<br />
== Thurs Apr 16 (Wed 15 in the western hemisphere) ==<br />
<br />
Mentors attending: Jameson Quinn, Andrés Ambrois, ...<br />
<br />
* [http://www.timeanddate.com/counters/customcounter.html?day=16&month=04&year=2009&hour=0&min=0&sec=0&p0=0 0000 UTC]: Andrés<br />
<br />
* 0030 UTC:<br />
<br />
* 0100 UTC:<br />
<br />
* 0130 UTC:<br />
<br />
== Thurs Apr 16 ==<br />
<br />
Mentors attending: Jameson Quinn, ...<br />
<br />
* [http://www.timeanddate.com/counters/customcounter.html?day=16&month=04&year=2009&hour=18&min=0&sec=0&p0=0 1800 UTC]:<br />
<br />
* 1830 UTC:<br />
<br />
* 1900 UTC:<br />
<br />
* 1930 UTC:</div>Aahttps://wiki.sugarlabs.org/index.php?title=File_Sharing_Utility&diff=24568File Sharing Utility2009-03-31T12:47:50Z<p>Aa: </p>
<hr />
<div>====About you====<br />
<br />
Q.1 : '''What is your name?'''<br />
<br />
Ans : Kartik Rustagi<br />
<br />
----<br />
<br />
Q.2 : '''What is your email address?'''<br />
<br />
Ans : kashes911 [AT] gmail [DOT] com<br />
<br />
----<br />
<br />
Q.3 : '''What is your Sugar Labs wiki username?'''<br />
<br />
Ans : kashes911<br />
<br />
----<br />
<br />
Q.4 : '''What is your IRC nickname?'''<br />
<br />
Ans : kartik_rustagi<br />
<br />
----<br />
<br />
Q.5 : '''What is your primary language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.)'''<br />
<br />
Ans : English and Hindi<br />
<br />
----<br />
<br />
Q.6 : '''Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.)'''<br />
<br />
Ans : Located in New Delhi, India, UTC +530. <br />
Since most of the period of Gsoc comes at a time of summer vacation for me, therefore I am comfortable working at any time of the day.<br />
<br />
<br />
Q.7 : '''Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source. If not, why do you want to work on an open-source project this summer?'''<br />
<br />
Ans : I have done the following relevant work:<br />
<br />
->Implemented 7-zip compressed commics support in Evince Document Viewer, Gnome Bug: #532312<br />
* Link: http://ftp.gnome.org/pub/GNOME/desktop/2.23/2.23.5/NEWS<br />
<br />
-> Was involved in the designing of a Joint Architecture for Unmanned Systems (JAUS) compliant Software Development Kit as a part of a startup I am co-founder off. Things I worked on (all in c/c++):<br />
* Unix System calls<br />
* Unix,UDP and TCP sockets<br />
* Threads, semaphores and mutex.<br />
* Design of the architecture which involved making UMLs<br />
* Object oriented designing <br />
I cant provide the link to the source code since the work if proprietary. <br />
<br />
->Designed and implemented an Asynchronous Information Dissemination System using Delay Tolerant Networks. Was selected in the top 12 teams from Asia Pacific by Google as a part of Google Product Prodigy. The finals will take place in April.<br />
* Link: http://www.google.co.in/intl/en/productprodigy/finalists.html <br />
* Team: Mobile Health<br />
* Here specifically a lot of PyGtk was used along with XML DOM, imaplib, smtplib etc.<br />
TODO: Ask Google if the source code can be made public.<br />
<br />
->Implemented a peer-to-peer file search and transfer utility in python. It had the following main features:<br />
#Remote discovery of active peers<br />
#File search queries using Multicast and File transfer<br />
#Object matching using regular expressions<br />
#Link: http://code.google.com/p/p2p-lan/downloads/list<br />
<br />
->Made a distributed game based on Flash and Python and used Asynchronous servers, Mysql db, DOM in its design and implementation.<br />
#Link: http://code.google.com/p/etheravtar/downloads/list<br />
<br />
----<br />
<br />
====About your project====<br />
<br />
Q.1 : '''What is the name of your project?'''<br />
<br />
Ans : File Sharing Utility<br />
<br />
<br />
----<br />
<br />
<br />
Q.2 : '''Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?'''<br />
<br />
a) : '''What are you making'''<br />
<br />
Ans : There is a lack of file sharing ability in the Sugar Learning Platform right now. Sugar relies on Telepathy for most of its network requirement. Telepathy in turn uses XMPP Extensions as the bases of their various interfaces. The XMPP Extensions for File Repository and Sharing is XEP:0214 . There is no Telepathy interface for this XEP currently and therefore File Sharing is not their right now. Also the File Transfer API is only to send files at the most, not request them. Therefore there will be a need to design a Telepathy interface to announce files, retrieves files from contact and request a file. <br />
<br />
'''''Steps for the complete implementation :'''''<br />
<br />
1) To design a Telepathy interface to announce files, retrieves files from contact and request a file.<br />
<br />
2) Understand XEP-0214 and Telepathy enough to write a Telepathy Interface Specification for the functionality of XEP-0214.<br />
<br />
3) Implementing that interface in Gabble. <br />
<br />
4) XEP-0214 only gets you us as far finding out what files a person has. Step 4 is writing python code to actually retrieve those files, using <br />
Telepathy's existing FileTransfer API.<br />
<br />
5) Modify the Sugar interface (probably Journal and Neighborhood view) to expose this functionality to the user, i.e to give an option to share a file or not.<br />
<br />
----<br />
<br />
b) : '''Who are you making it for'''<br />
<br />
Ans : This will be of immense use for any one associated with sugar be it students, teachers and even developers since allowing such kind of functionalities will truly enhance Sugar's ability and bring to it a feature which is considered a basic utility in any platform. <br />
<br />
----<br />
<br />
c) : '''Why do they need it '''<br />
<br />
Ans : A typical use of this application is the transfer of assignments and similar work among students. Their can be many uses of this functionality for other activities as sharing has been a primary goal for the Sugar Platform. In order to connect the sugar community File Sharing according to me is some thing of prime importance.<br />
<br />
----<br />
<br />
d) : '''What technologies (programming languages, etc.) will you be using?'''<br />
<br />
Ans : Most of the programming will be done in C followed by some part in python too. A major portion of this project will be to understand Telepathy's existing interfaces therefore Telepathy will be a major technology involved. The GUI will be done using PyGTK. Other technologies involved include D-BUS as the underlying IPC mechanism, GObject etc. <br />
<br />
----<br />
<br />
Q.3 : '''What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.'''<br />
<br />
Ans : Since overall quite a lot of work is involved including learning many new things, therefore I specially aim to use the preios between filing my application and the actual begining of GSoc to maximum use. I aim to make my self done with Telepathy's existing source code in this period along with having a first draft of the TP interface to to announce files, retrieves files from contact and request a file in this period only.<br />
<br />
TODO: Detail of the timeline in the official Gsoc period to be finalised after more discussion with developers. <br />
<br />
----<br />
<br />
Q.4 : '''Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, school work, and that sort of thing, but be creative. Link to prior work or other resources as relevant.'''<br />
<br />
Ans : The biggest asset with this proposal is that this proposal has been a result of intense discussion with developers associated with the parent projects i.e Telepathy and Sugar. Very crucial issues like the viability of the implementation and the actual use of such a project for the Sugar community were taken into account before I actually sat down to write this proposal. Therefore I am very clear about the major tasks that I need to complete. Also I being in constant touch with developers had provided me with a basic approach to actually implement these tasks.<br />
Regarding the issue of my personal skills to complete this task, I have been involved in a startup which helped me realise how the principles of Software Engineering are actually brought into action in the real world. Other then this most of the work I am doing in this startup is infact in C, the major language I will be using. <br />
Regarding the Python I have done many small/mid-sized projects which make use of each of the libraries I will be needing to conceptualise this proposal. I have also done few projects which were specifically addressing the File sharing (and transfer). This again brings clarity of the process involved.<br />
Other then this my wish to contribute to the Open Source community in any way possible (Gsoc or no Gsoc) will be the biggest inspiration that will make me complete this project.<br />
<br />
----<br />
<br />
<br />
====You and the community====<br />
<br />
Q.1 : '''If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.'''<br />
<br />
Ans : <br />
<br />
''' From myself :'''<br />
<br />
With the completion of this project a very essential feature will be made available to the Sugar Platform. Having the freedom of sharing with anyone any time is essential for such a platform and this project essentially achieves that. Other than this it opens the door for other developers to make creative use of this utility for their own activities. Also it will be a way for Sugar to payback to the Telepathy Community which it makes use of for so many of its needs :)<br />
<br />
''' From Benjamin M. Schwartz : '''<br />
<br />
"So what I mean is, this feature, file sharing, has been part of the Sugar design since before Sugar existed." <br />
This was said in reference to the discussion : http://lists.sugarlabs.org/archive/sugar-devel/2007-August/003323.html <br />
<br />
''' From Andrés Ambrois :'''<br />
<br />
If this project succeeds it will be providing a very important missing piece in Sugar's vision of a learning environment, encouraging content creation and distribution in a local, peer-based fashion. <br />
<br />
From my experience here in Uruguay, the collaboration possibilities are being largely ignored in the classroom, partially because of infrastructure problems, but also because of the lack of semantically basic functions such as this. <br />
----<br />
<br />
Q.2 : '''Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?'''<br />
<br />
Ans : I would like the deployment to be at a near by Government school for the poor since they are the students that are usually isolated from the strength of electronic education and hence have the maximum curiosity to learn. <br />
<br />
----<br />
<br />
Q.3 : '''What will you do if you get stuck on your project and your mentor isn't around?'''<br />
<br />
Ans : I will do the following things in the same order: <br />
# Search about it Google<br />
# Ask people on the mailing list and IRC for the solution<br />
# Will go through the various discussion forums <br />
----<br />
<br />
Q.4 : '''How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project? '''<br />
<br />
Ans : I will do the following things : <br />
# Updating the project wiki<br />
# Sending regular updates on the mailing list <br />
# Ping IRC and asking users/developers for review <br />
----<br />
<br />
====Miscellaneous====<br />
[[Image:New-developer-challenge.png|thumb|right|An example of the kind of screenshot of your first modification to your development environment which you should include in your application. Note that the drop-down menu text has Mel's email address in place of the word "Restart" - your screenshot should contain your email instead.]]<br />
# We want to make sure that you can set up a [[DevelopmentTeam#Development_systems|development environment]] before the summer starts. Please send us a link to a screenshot of your Sugar development environment with the following modification: when you hover over the XO-person icon in the middle of Home view, the drop-down text should have your email in place of "Restart." See the image on the right for an example. It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.<br />
<br />
Ans : [[http://p2p-lan.googlecode.com/files/sugar_prerequisite.png Here is the prerequisite]]<br />
<br />
Q.6 : What is your t-shirt size? (Yes, we know Google asks for this already; humor us.)<br />
<br />
Ans : Large<br />
<br />
# Describe a great learning experience you had as a child.<br />
# Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more?<br />
<br />
<noinclude>[[Category:2009 GSoC applications]]</noinclude></div>Aahttps://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Mentors&diff=23110Summer of Code/Mentors2009-03-20T04:54:41Z<p>Aa: </p>
<hr />
<div>Our most important need right now is for quality mentors. If you (or someone you know) would make a good mentor, please nominate yourself (or them), both here on the ML and on the wiki (if you can't handle a little redundant paperwork, you're probably not a good candidate :). Include relevant information such as:<br />
<br />
*Name/contact<br />
*Timezone<br />
*What kind of projects could/would you mentor?<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor?<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
*What relevant mentoring (or related) experience do you have?<br />
*Anything else you think is relevant.<br />
<br />
Please also add this page to your watchlist. We will probably later do some kind of "community interview" process where we ask you questions on this page.<br />
<br />
=== Jameson ===<br />
<br />
*Name/contact<br />
<br />
Jameson.Quinn at gmail<br />
<br />
*Timezone<br />
<br />
US Central / Central America (UTC-6)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
PyGTK-based activities or Sugar improvements, especially interested in language or developer tools.<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I could commit up to 4-6 hours a week. If we are short on mentors and I find project(s) that are an especially good match, I could do 8 hrs (double duty). Over the summer, I hope to be helping to work on an XO deployment, hopefully on a paid basis, but am currently unemployed.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Maintainer of Develop activity, have done some tinkering with Sugar, I've been involved for over a year.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
I have several years' experience as a full-time teacher.<br />
<br />
*Anything else you think is relevant.<br />
<br />
Nah.<br />
<br />
=== [[User:Nrp|Nrp]] ===<br />
<br />
* Name/contact<br />
<br />
Nirav Patel nrpatel at gmail<br />
<br />
* Timezone<br />
<br />
UTC-5<br />
<br />
* What kind of projects could/would you mentor?<br />
<br />
Pygame or PyGTK based Activities<br />
<br />
* How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
Graduating and no job prospects, so it is likely I will have quite a<br />
bit of free time as of early May. 5 hours a week is certainly doable.<br />
<br />
* What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Some Pygame/PyGTK Activity development and a module for Pygame.<br />
<br />
* What relevant mentoring (or related) experience do you have?<br />
<br />
Teaching Assistant and miscellaneous mentoring experiences at school.<br />
<br />
* Anything else you think is relevant.<br />
<br />
I survived GSoC on the student end of things in 2008.<br />
<br />
=== Tomeu ===<br />
<br />
*Name/contact<br />
<br />
[[User:Tomeu | Tomeu Vizoso]]<br />
<br />
*Timezone<br />
<br />
Central European Time<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
PyGTK-based activities or Sugar improvements.<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I could commit up to 4-6 hours a week.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Coded activities and for the sugar shell for more than two years now.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
Last year mentored one intern at OLPC.<br />
<br />
*Anything else you think is relevant.<br />
<br />
Nah.<br />
<br />
=== Walter ===<br />
<br />
* Name/contact<br />
<br />
[[User:Walter|Walter Bender]]<br />
<br />
EST (UTC-5)<br />
<br />
* What kind of projects could/would you mentor?<br />
<br />
I am interested in Sugar activities that are relevant to daily life in the classroom. Things that help the teacher and learner enhance their approaches to problem-solving. <br />
<br />
* How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor?<br />
<br />
As much as necessary to make sure we have a successful, useful outcome.<br />
<br />
* What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
maintainer of [[Activities/TurtleArt]]<br />
<br />
* What relevant mentoring (or related) experience do you have?<br />
<br />
30 years mentoring student projects at MIT<br />
<br />
* Anything else you think is relevant.<br />
<br />
You learn through doing, so I will roll up my sleeves along side whomever I mentor, because I want to keep learning.<br />
<br />
<br />
=== [[User:Bobbyp|Bobby]] ===<br />
<br />
*Name/contact<br />
<br />
firstnamelastname at gmail, nteon on IRC<br />
<br />
*Timezone<br />
<br />
US Eastern Standard Time (UTC-5)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
PyGTK-based activities, lower level stuff.<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
Probably 4-6 hours a week.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Maintainer of Model activity, have done some tinkering with Sugar/Rainbow, rewrote boot-animation. Fairly confident with C/Python/Linux, have been involved with OLPC for about a year (although have been mostly lurking on the sugar side of things for a few months).<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
Summer camp counselor for a number of years, OLPC intern summer '08.<br />
<br />
*Anything else you think is relevant.<br />
<br />
I'm a few months behind on Sugar development, but think its a fabulous project. Let me know what you need of me.<br />
<br />
=== [[User:Sebastian|Sebastian]] ===<br />
<br />
*Name/contact<br />
<br />
Sebastian Silva (sebastian at fuentelibre.org), (gmail alternative: sebatustra)<br />
<br />
icarito on IRC<br />
<br />
*Timezone<br />
<br />
Lima, Perú (UTC-5)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
PyGTK-based activities, especially "social" activities.<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I am helping a teacher group this (northern summer), that leaves me enough time to commit to this (at least 4-6 hours a week, more if needed). It also is a great chance for some user feedback.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Community volunteer for 2 years now, developed activities, led workshops. Confident in python and GNU. Worked professionally in programming for some years.<br />
<br />
=== [[User:Wade|Wade]] ===<br />
<br />
*Name/contact<br />
<br />
Wade Brainerd (wadetb at gmail dot com) <br />
<br />
wadeb on IRC<br />
<br />
*Timezone<br />
<br />
Portland, Maine (UTC-5)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
New activities, Games, Updates to/refreshes of existing activities, Frameworks for creating activities in new languages (Flash, Ajax, Mono)<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I will be available for a single mentorship this year. I work full time as a programmer but have a flexible schedule.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Community volunteer for 2 years now, developed activities. Experienced in Python, C++, others. 11 years as a professional programmer, including 5 as a technical director and team lead.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
I was closely involved in the 2007 OLPC GSoC project, reviewing applications and communicating with students. I mentored two students informally during 2007 after their GSoC projects were not funded. Both projects were completed with my help.<br />
<br />
*Anything else you think is relevant.<br />
<br />
As the Sugar Labs Activity Team coordinator, I have plenty of access to deployments. This gives me a good handle on what student projects will most effectively advance Sugar Labs' goals in the community. <br />
<br />
As a volunteer activity developer, I have also developed many new activities myself, and overhauled existing ones.<br />
<br />
=== [[User:Lglira|Lglira]] ===<br />
<br />
*Name/contact<br />
<br />
Luis Gustavo Lira, BSc, MSc lira.lg at pucp.edu.pe<br />
<br />
*Timezone<br />
<br />
Lima, Perú (UTC-5)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
Networking, Hardware Projects, Python, Activities (science, math, entrepreneurship).<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I could mentor 1 o 2 students.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Engineer 10 years working experience, CIO and Executive level since 2006.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
Consultant for big telecomms, systems integrators, etc.<br />
Lecturer at University undergraduate and graduate level.<br />
GSoC 2007, 2008 and 2009 Mentor for OpenMoko<br />
GSoC 2008 for OLPC but my student was not funded<br />
<br />
*Anything else you think is relevant.<br />
<br />
Fellow of Lemelson Foundation RAMP-Peru, Social Entrepreneur, Free Culture activist, Appropriate Technology developer, Teaching Science, Math and Entrepeneurship in rural terciary schools.<br />
<br />
=== [[User:benlau|Ben Lau]] ===<br />
<br />
*Name/contact<br />
xbenlau at gmail.com<br />
<br />
*Timezone<br />
UTC+8<br />
<br />
*What kind of projects could/would you mentor?<br />
Video , Computer Vision , Speech Processing , Python, Activities (Educational software , Chinese language learning)<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor?<br />
I could commit up to 4-5 hours a week, able to mentor 1 student.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
10 years Linux development experience , include kernel porting (ARM), Linux driver , GTK+ , opencv , GStreamer , C/C++ , python<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
I have led two teams of university students to join an embedded system contest called Intel Cup (China) in 2006. The teams got a first prize and a second prize award finally.<br />
<br />
*Anything else you think is relevant.<br />
I am leading a team of volunteers on technical side for OLPC APAC division.<br />
<br />
=== [[User:SayaminduDasgupta|Sayamindu]] ===<br />
<br />
*Name/contact<br />
<br />
Sayamindu Dasgupta (sayamindu at gmail)<br />
<br />
unmadindu on IRC<br />
<br />
*Timezone<br />
<br />
Asia/Calcutta (UTC+0530) (I normally work on European timezones)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
Activities, l10n/i18n related projects.<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I am working a contractor for OLPC for the next few months. However, I think I can commit around 4-5 hours per week for the work.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Wrote the Imageviewer activity, maintainer of Terminal, in the process of implementing largish features to Read. Familiar with GTK+, Python, Gstreamer, etc.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
I was a mentor during SoC 2008 for the Translate toolkit project (my student worked successfully on enhancing the Pootle featureset). I have also experience informally mentoring/guiding students and volunteers for a number of Free Software projects (mostly i18n/l10n related).<br />
<br />
*Anything else you think is relevant.<br />
<br />
I was a successful student participant in Summer of Code 2007 under Federico Mena-Quintero for the GNOME project. I also helped in the rating of applications for OLPC as a mentoring organisation during 2008's SoC.<br />
<br />
<br />
<br />
=== [[User:Assim|Assim Deodia]] ===<br />
<br />
*Name/contact<br />
<br />
Assim Deodia (assim.deodia at gmail dot com)<br />
<br />
assimd on IRC<br />
<br />
*Timezone<br />
<br />
Asia/Calcutta (UTC+0530)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
[[Listen Spell]], Activities related to speech synthesis<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I can comfortably devote 4-5 hrs a week. <br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
I have developed speech server in SoCon for OLPC [http://wiki.laptop.org/go/Speech_Server| Speech Server], Deducto for OLPC and have also developed Listen Spell for OLPC in GSoC.<br />
<br />
*Anything else you think is relevant.<br />
<br />
I have successful completed Summer of Code 2008 under Dafydd Harries for the OLPC. I have also developed a low cost OMR processing application which is hosted on sourceforge [http://sourceforge.net/projects/omr-ai/| OMR AI]<br />
<br />
=== [[User:Aa|aa]] ===<br />
<br />
*Name/contact<br />
<br />
andresambrois at gmail<br />
<br />
*Timezone<br />
<br />
America/Montevideo (UTC-3)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
PyGTK-based activities and Sugar projects, especially in collaboration and networking. <br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
5-6 hours a week. Currently unemployed, but studying computer engineering. I devote most of my time to free software projects and Ceibal-related volunteering. <br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
I maintain the PlayGo activity, one of the developers of the [http://wiki.laptop.org/go/Educational_Blogger_Project| EduBlog project], written a couple of patches for sugar and currently working on some improvements. Familiar with Python, PHP, Tcl, Shell Scripting and (some) C. <br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
I've given technical talks and workshops, and was a math tutor years ago. <br />
<br />
*Anything else you think is relevant.<br />
<br />
I fear velociraptors.</div>Aahttps://wiki.sugarlabs.org/index.php?title=Summer_of_Code/Mentors&diff=23109Summer of Code/Mentors2009-03-20T04:52:31Z<p>Aa: </p>
<hr />
<div>Our most important need right now is for quality mentors. If you (or someone you know) would make a good mentor, please nominate yourself (or them), both here on the ML and on the wiki (if you can't handle a little redundant paperwork, you're probably not a good candidate :). Include relevant information such as:<br />
<br />
*Name/contact<br />
*Timezone<br />
*What kind of projects could/would you mentor?<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor?<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
*What relevant mentoring (or related) experience do you have?<br />
*Anything else you think is relevant.<br />
<br />
Please also add this page to your watchlist. We will probably later do some kind of "community interview" process where we ask you questions on this page.<br />
<br />
=== Jameson ===<br />
<br />
*Name/contact<br />
<br />
Jameson.Quinn at gmail<br />
<br />
*Timezone<br />
<br />
US Central / Central America (UTC-6)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
PyGTK-based activities or Sugar improvements, especially interested in language or developer tools.<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I could commit up to 4-6 hours a week. If we are short on mentors and I find project(s) that are an especially good match, I could do 8 hrs (double duty). Over the summer, I hope to be helping to work on an XO deployment, hopefully on a paid basis, but am currently unemployed.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Maintainer of Develop activity, have done some tinkering with Sugar, I've been involved for over a year.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
I have several years' experience as a full-time teacher.<br />
<br />
*Anything else you think is relevant.<br />
<br />
Nah.<br />
<br />
=== [[User:Nrp|Nrp]] ===<br />
<br />
* Name/contact<br />
<br />
Nirav Patel nrpatel at gmail<br />
<br />
* Timezone<br />
<br />
UTC-5<br />
<br />
* What kind of projects could/would you mentor?<br />
<br />
Pygame or PyGTK based Activities<br />
<br />
* How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
Graduating and no job prospects, so it is likely I will have quite a<br />
bit of free time as of early May. 5 hours a week is certainly doable.<br />
<br />
* What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Some Pygame/PyGTK Activity development and a module for Pygame.<br />
<br />
* What relevant mentoring (or related) experience do you have?<br />
<br />
Teaching Assistant and miscellaneous mentoring experiences at school.<br />
<br />
* Anything else you think is relevant.<br />
<br />
I survived GSoC on the student end of things in 2008.<br />
<br />
=== Tomeu ===<br />
<br />
*Name/contact<br />
<br />
[[User:Tomeu | Tomeu Vizoso]]<br />
<br />
*Timezone<br />
<br />
Central European Time<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
PyGTK-based activities or Sugar improvements.<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I could commit up to 4-6 hours a week.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Coded activities and for the sugar shell for more than two years now.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
Last year mentored one intern at OLPC.<br />
<br />
*Anything else you think is relevant.<br />
<br />
Nah.<br />
<br />
=== Walter ===<br />
<br />
* Name/contact<br />
<br />
[[User:Walter|Walter Bender]]<br />
<br />
EST (UTC-5)<br />
<br />
* What kind of projects could/would you mentor?<br />
<br />
I am interested in Sugar activities that are relevant to daily life in the classroom. Things that help the teacher and learner enhance their approaches to problem-solving. <br />
<br />
* How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor?<br />
<br />
As much as necessary to make sure we have a successful, useful outcome.<br />
<br />
* What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
maintainer of [[Activities/TurtleArt]]<br />
<br />
* What relevant mentoring (or related) experience do you have?<br />
<br />
30 years mentoring student projects at MIT<br />
<br />
* Anything else you think is relevant.<br />
<br />
You learn through doing, so I will roll up my sleeves along side whomever I mentor, because I want to keep learning.<br />
<br />
<br />
=== [[User:Bobbyp|Bobby]] ===<br />
<br />
*Name/contact<br />
<br />
firstnamelastname at gmail, nteon on IRC<br />
<br />
*Timezone<br />
<br />
US Eastern Standard Time (UTC-5)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
PyGTK-based activities, lower level stuff.<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
Probably 4-6 hours a week.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Maintainer of Model activity, have done some tinkering with Sugar/Rainbow, rewrote boot-animation. Fairly confident with C/Python/Linux, have been involved with OLPC for about a year (although have been mostly lurking on the sugar side of things for a few months).<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
Summer camp counselor for a number of years, OLPC intern summer '08.<br />
<br />
*Anything else you think is relevant.<br />
<br />
I'm a few months behind on Sugar development, but think its a fabulous project. Let me know what you need of me.<br />
<br />
=== [[User:Sebastian|Sebastian]] ===<br />
<br />
*Name/contact<br />
<br />
Sebastian Silva (sebastian at fuentelibre.org), (gmail alternative: sebatustra)<br />
<br />
icarito on IRC<br />
<br />
*Timezone<br />
<br />
Lima, Perú (UTC-5)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
PyGTK-based activities, especially "social" activities.<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I am helping a teacher group this (northern summer), that leaves me enough time to commit to this (at least 4-6 hours a week, more if needed). It also is a great chance for some user feedback.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Community volunteer for 2 years now, developed activities, led workshops. Confident in python and GNU. Worked professionally in programming for some years.<br />
<br />
=== [[User:Wade|Wade]] ===<br />
<br />
*Name/contact<br />
<br />
Wade Brainerd (wadetb at gmail dot com) <br />
<br />
wadeb on IRC<br />
<br />
*Timezone<br />
<br />
Portland, Maine (UTC-5)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
New activities, Games, Updates to/refreshes of existing activities, Frameworks for creating activities in new languages (Flash, Ajax, Mono)<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I will be available for a single mentorship this year. I work full time as a programmer but have a flexible schedule.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Community volunteer for 2 years now, developed activities. Experienced in Python, C++, others. 11 years as a professional programmer, including 5 as a technical director and team lead.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
I was closely involved in the 2007 OLPC GSoC project, reviewing applications and communicating with students. I mentored two students informally during 2007 after their GSoC projects were not funded. Both projects were completed with my help.<br />
<br />
*Anything else you think is relevant.<br />
<br />
As the Sugar Labs Activity Team coordinator, I have plenty of access to deployments. This gives me a good handle on what student projects will most effectively advance Sugar Labs' goals in the community. <br />
<br />
As a volunteer activity developer, I have also developed many new activities myself, and overhauled existing ones.<br />
<br />
=== [[User:Lglira|Lglira]] ===<br />
<br />
*Name/contact<br />
<br />
Luis Gustavo Lira, BSc, MSc lira.lg at pucp.edu.pe<br />
<br />
*Timezone<br />
<br />
Lima, Perú (UTC-5)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
Networking, Hardware Projects, Python, Activities (science, math, entrepreneurship).<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I could mentor 1 o 2 students.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Engineer 10 years working experience, CIO and Executive level since 2006.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
Consultant for big telecomms, systems integrators, etc.<br />
Lecturer at University undergraduate and graduate level.<br />
GSoC 2007, 2008 and 2009 Mentor for OpenMoko<br />
GSoC 2008 for OLPC but my student was not funded<br />
<br />
*Anything else you think is relevant.<br />
<br />
Fellow of Lemelson Foundation RAMP-Peru, Social Entrepreneur, Free Culture activist, Appropriate Technology developer, Teaching Science, Math and Entrepeneurship in rural terciary schools.<br />
<br />
=== [[User:benlau|Ben Lau]] ===<br />
<br />
*Name/contact<br />
xbenlau at gmail.com<br />
<br />
*Timezone<br />
UTC+8<br />
<br />
*What kind of projects could/would you mentor?<br />
Video , Computer Vision , Speech Processing , Python, Activities (Educational software , Chinese language learning)<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor?<br />
I could commit up to 4-5 hours a week, able to mentor 1 student.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
10 years Linux development experience , include kernel porting (ARM), Linux driver , GTK+ , opencv , GStreamer , C/C++ , python<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
I have led two teams of university students to join an embedded system contest called Intel Cup (China) in 2006. The teams got a first prize and a second prize award finally.<br />
<br />
*Anything else you think is relevant.<br />
I am leading a team of volunteers on technical side for OLPC APAC division.<br />
<br />
=== [[User:SayaminduDasgupta|Sayamindu]] ===<br />
<br />
*Name/contact<br />
<br />
Sayamindu Dasgupta (sayamindu at gmail)<br />
<br />
unmadindu on IRC<br />
<br />
*Timezone<br />
<br />
Asia/Calcutta (UTC+0530) (I normally work on European timezones)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
Activities, l10n/i18n related projects.<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I am working a contractor for OLPC for the next few months. However, I think I can commit around 4-5 hours per week for the work.<br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
Wrote the Imageviewer activity, maintainer of Terminal, in the process of implementing largish features to Read. Familiar with GTK+, Python, Gstreamer, etc.<br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
I was a mentor during SoC 2008 for the Translate toolkit project (my student worked successfully on enhancing the Pootle featureset). I have also experience informally mentoring/guiding students and volunteers for a number of Free Software projects (mostly i18n/l10n related).<br />
<br />
*Anything else you think is relevant.<br />
<br />
I was a successful student participant in Summer of Code 2007 under Federico Mena-Quintero for the GNOME project. I also helped in the rating of applications for OLPC as a mentoring organisation during 2008's SoC.<br />
<br />
<br />
<br />
=== [[User:Assim|Assim Deodia]] ===<br />
<br />
*Name/contact<br />
<br />
Assim Deodia (assim.deodia at gmail dot com)<br />
<br />
assimd on IRC<br />
<br />
*Timezone<br />
<br />
Asia/Calcutta (UTC+0530)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
[[Listen Spell]], Activities related to speech synthesis<br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
I can comfortably devote 4-5 hrs a week. <br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
I have developed speech server in SoCon for OLPC [http://wiki.laptop.org/go/Speech_Server| Speech Server], Deducto for OLPC and have also developed Listen Spell for OLPC in GSoC.<br />
<br />
*Anything else you think is relevant.<br />
<br />
I have successful completed Summer of Code 2008 under Dafydd Harries for the OLPC. I have also developed a low cost OMR processing application which is hosted on sourceforge [http://sourceforge.net/projects/omr-ai/| OMR AI]<br />
<br />
=== [[User:Aa|aa]] ===<br />
<br />
*Name/contact<br />
<br />
andresambrois at gmail<br />
<br />
*Timezone<br />
<br />
America/Montevideo (UTC-3)<br />
<br />
*What kind of projects could/would you mentor?<br />
<br />
PyGTK-based activities and Sugar projects, especially in collaboration and networking. <br />
<br />
*How much time could you devote to mentoring? Can you make the especially solid commitment of being a double-mentor? What are your other commitments over the summer?<br />
<br />
5-6 hours a week. Currently unemployed, but studying computer engineering. I devote most of my time to free software projects and Ceibal-related volunteering. <br />
<br />
*What relevant coding experience do you have (very briefly, two sentences at most)?<br />
<br />
I maintain the PlayGo activity, one of the developers of the [[http://wiki.laptop.org/go/Educational_Blogger_Project|EduBlog project]], written a couple of patches for sugar and currently working on some improvements. Familiar with Python, PHP, Tcl, Shell Scripting and (some) C. <br />
<br />
*What relevant mentoring (or related) experience do you have?<br />
<br />
I've given technical talks and workshops, and was a math tutor years ago. <br />
<br />
*Anything else you think is relevant.<br />
<br />
I fear velociraptors.</div>Aahttps://wiki.sugarlabs.org/index.php?title=Development_Team/Jhbuild&diff=19842Development Team/Jhbuild2009-02-20T17:38:00Z<p>Aa: </p>
<hr />
<div><noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude><br />
{{Translations}}<br />
<br />
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.<br />
<br />
==Compatible Platforms==<br />
<br />
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.<br />
<br />
Distros supported by the development community are Debian unstable, Fedora Rawhide, Fedora 10, and Ubuntu 8.10. 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).<br />
<br />
''' Note that Debian Unstable and derived distros (e.g. Ubuntu Intrepid) contain a bug in python-gnome that impedes running jhbuild '''<br />
<br />
To work around this use chrpath to remove the rpath setting from your system's gconf.so: <br />
<br />
sudo aptitude install chrpath<br />
find /usr/lib/python-support/python-gnome2/python2.5/gtk-2.0 -name "*.so" | sudo xargs chrpath -d<br />
<br />
==Checkout sugar-jhbuild==<br />
<br />
In a suitable directory, execute<br />
<br />
git-clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild<br />
<br />
==Build sugar base system and its dependencies==<br />
<br />
Change directory and start the build.<br />
<br />
cd sugar-jhbuild<br />
./sugar-jhbuild update<br />
./sugar-jhbuild depscheck<br />
./sugar-jhbuild build<br />
<br />
=== Dealing with dependencies ===<br />
<br />
At some point during running ''sugar-jhbuild update'' or ''sugar-jhbuild build'' you may be interrupted by an error listing some dependencies you don't have. The build will pause, and you'll see, among the text on your screen, something like this:<br />
<br />
No package '<packagename>' found<br />
<br />
Usually this means it's looking for the <packagename>-dev. Install that package. (For instance, to fix a "No package 'libsoup2.4' found" error, you'd install libsoup2.4-dev.<br />
<br />
If that doesn't work, here are some further notes:<br />
<br />
* If you're given a list of packages that aren't installed, simply install them according to your distribution's package manager (yum, apt-get, etc.) and then try re-running the sugar-jhbuild command again.<br />
* For the base packages, you may be able to use the binary packages from your GNU distribution instead of building them from scratch. Check the [[:Category:Installing Sugar|Installing]] or [[:Category:Linux distributions|Linux]] categories for specific distro info.<br />
* You may have some issues with penguintv on ubuntu, just interrupt the pull with a CTRL+C, open a shell, repeat the command manually, and accept the certificate permanently.<br />
* One other fix that I had to do was to export GTK2_RC_FILES=~/src/olpc/sugar-jhbuild/build/share/themes/sugar/gtk-2.0/gtkrc<br />
and also symlink build/share/icons/sugar to build/share/icons/hicolor. These two steps may not be necessary, but they made things work on my Ubuntu installation as of March 31, 2008. [[User:Blaketh|Blaketh]] 03:08, 31 March 2008 (EDT)<br />
<br />
==Run Sugar==<br />
<br />
This command launches the Sugar emulator:<br />
<br />
./sugar-jhbuild run<br />
<br />
To exit the emulator, press Alt-Q.<br />
<br />
== Running multiple instances==<br />
To run multiple instances of sugar you can start it in the following way:<br />
<br />
SUGAR_PROFILE=2 ./sugar-jhbuild run<br />
<br />
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/<br />
<br />
== Run an individual activity ==<br />
<br />
Within sugar, e.g. in Terminal, this command launches an individual activity for testing:<br />
<br />
sugar-launch [bundle name]<br />
<br />
You will see debug output appearing in Terminal.<br />
<br />
== Configure the mode and resolution of Sugar ==<br />
<br />
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''':<br />
<br />
cd sugar-jhbuild<br />
cp install/share/sugar/shell/emulator.py install/share/sugar/shell/emulator.py.backup<br />
nano install/share/sugar/shell/emulator.py<br />
<br />
Find this piece of code:<br />
<br />
<PRE><br />
cmd = [ 'Xephyr' ]<br />
cmd.append(':%d' % display)<br />
cmd.append('-ac')<br />
<br />
if gtk.gdk.screen_width() < 1200 or gtk.gdk.screen_height() < 900:<br />
cmd.append('-fullscreen')<br />
else:<br />
cmd.append('-screen')<br />
cmd.append('%dx%d' % (1200, 900))<br />
</PRE> <br />
<br />
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):<br />
<br />
<PRE><br />
cmd = [ 'Xephyr' ]<br />
cmd.append(':%d' % display)<br />
cmd.append('-ac')<br />
<br />
# if gtk.gdk.screen_width() < 1200 or gtk.gdk.screen_height() < 900:<br />
# cmd.append('-fullscreen')<br />
# else:<br />
cmd.append('-screen')<br />
cmd.append('%dx%d' % (800, 600))<br />
</PRE><br />
<br />
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.<br />
<br />
== Other commands ==<br />
<br />
JHBuild has several other commands that can be useful for development. You can get an overview with:<br />
<br />
./sugar-jhbuild --help-commands<br />
<br />
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.)<br />
<br />
./sugar-jhbuild update<br />
./sugar-jhbuild build<br />
./sugar-jhbuild run<br />
<br />
=== If update and build don't work ===<br />
<br />
In May 2008 there were some changes that broke updates on sugar-jhbuild. A version from before this date cannot update or build after this date; the symptoms are various, but generally include errors which mention the "build-scripts" directory. You need to rebuild from scratch in a new jhbuild directory. Something like the following:<br />
<br />
cd ..<br />
mv sugar-jhbuild sugar-jhbuild.old<br />
git-clone git://dev.laptop.org/sugar-jhbuild<br />
<br />
then, to save bandwidth, move the tar files from your old version:<br />
<br />
mkdir sugar-jhbuild/source<br />
mv sugar-jhbuild.old/source/*.tar* sugar-jhbuild/source<br />
<br />
then build:<br />
<br />
cd sugar-jhbuild<br />
./sugar-jhbuild build<br />
<br />
You may then also see some new dependencies; see the relevant instructions above. <br />
<br />
=== From within Sugar ===<br />
Once you have Sugar running, here are some useful commands:<br />
*'''Alt+Shift+F''' makes the frame appear and disappear<br />
*'''Ctrl-Q''' quits an activity<br />
*'''Alt+Shift+Q''' quits Sugar<br />
*'''Alt+Shift+O''' opens the search<br />
*'''Alt+Shift+R''' rotates the screen<br />
<br />
=== Creating an xsession for Sugar-jhbuild ===<br />
Create the file /usr/share/xsessions/sugar-jhbuild.desktop with the following content:<br />
<br />
[Desktop Entry]<br />
Encoding=UTF-8<br />
Name=Sugar jhbuild<br />
GenericName=Sugar<br />
Exec=/usr/bin/sugar-jhbuild<br />
Type=Application<br />
<br />
Create the file /usr/bin/sugar-jhbuild with the following content:<br />
<br />
#!/bin/sh<br />
export GTK2_RC_FILES=/home/walter/sugar-jhbuild/install/share/sugar/data/sugar-xo.gtkrc<br />
exec /home/walter/sugar-jhbuild/sugar-jhbuild run dbus-launch /home/walter/sugar-jhbuild/install/bin/sugar-shell<br />
<br />
where you substitute the path of wherever you installed sugar-jhbuild for "/home/walter"<br />
<br />
== Customize ==<br />
<br />
To customize the build create a configuration file, named ''.sugar.jhbuildrc'', in your home directory.<br />
<br />
=== Write access to the repositories ===<br />
<br />
If you have write access to the repositories you can add this (if your login name happens to be marco):<br />
repos['gnome.org'] = ':ext:marco@cvs.gnome.org:/cvs/gnome'<br />
repos['mozilla.org'] = ':ext:marco%gnome.org@cvs.mozilla.org:/cvsroot'<br />
repos['dev.laptop.org'] = 'git+ssh://marco@dev.laptop.org/git/'<br />
repos['dev.laptop.org/projects'] = 'git+ssh://marco@dev.laptop.org/git/projects/'<br />
<br />
==Useful Internal Links==<br />
* [[DevelopmentTeam/Understanding the Code|Understanding Sugar Code]]<br />
* [[Taxonomy]] -- explains the components of Sugar (Glucose, Fructose, Sugar, Starches)<br />
* [[Sugar Instructions]] -- how to actually use Sugar once you have it running<br />
<br />
==External links==<br />
<br />
* [http://library.gnome.org/devel/jhbuild/unstable/ JHBuild manual]<br />
* [http://www.redhatmagazine.com/2007/02/23/building-the-xo-introducing-sugar/ Red Hat Magazine article: Introducing Sugar]<br />
* [http://learn.laptop.org/tinderbox/ Tinderbox] (see the "Sugar JHBuild" tab). The old [http://dev.laptop.org/~cjb/sugar-tinder/ sugar-jhbuild tinderbox].<br />
<br />
[[Category:Installing Sugar]]<br />
[[Category:Jhbuild]]</div>Aahttps://wiki.sugarlabs.org/index.php?title=Development_Team/Jhbuild&diff=19811Development Team/Jhbuild2009-02-19T13:29:12Z<p>Aa: Mention workaround for rpath issue</p>
<hr />
<div><noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude><br />
{{Translations}}<br />
<br />
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.<br />
<br />
==Compatible Platforms==<br />
<br />
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.<br />
<br />
Distros supported by the development community are Debian unstable, Fedora Rawhide, Fedora 10, and Ubuntu 8.10. 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).<br />
<br />
''' Note that Debian Unstable and derived distros (e.g. Ubuntu Intrepid) contain a bug in python-gnome that impedes running jhbuild '''<br />
<br />
To work around this use chrpath to remove the rpath setting from your system's gconf.so: <br />
<br />
sudo aptitude install chrpath<br />
sudo chrpath -d /usr/lib/python-support/python-gnome2/python2.5/gtk-2.0/gconf.so<br />
<br />
==Checkout sugar-jhbuild==<br />
<br />
In a suitable directory, execute<br />
<br />
git-clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild<br />
<br />
==Build sugar base system and its dependencies==<br />
<br />
Change directory and start the build.<br />
<br />
cd sugar-jhbuild<br />
./sugar-jhbuild update<br />
./sugar-jhbuild depscheck<br />
./sugar-jhbuild build<br />
<br />
=== Dealing with dependencies ===<br />
<br />
At some point during running ''sugar-jhbuild update'' or ''sugar-jhbuild build'' you may be interrupted by an error listing some dependencies you don't have. The build will pause, and you'll see, among the text on your screen, something like this:<br />
<br />
No package '<packagename>' found<br />
<br />
Usually this means it's looking for the <packagename>-dev. Install that package. (For instance, to fix a "No package 'libsoup2.4' found" error, you'd install libsoup2.4-dev.<br />
<br />
If that doesn't work, here are some further notes:<br />
<br />
* If you're given a list of packages that aren't installed, simply install them according to your distribution's package manager (yum, apt-get, etc.) and then try re-running the sugar-jhbuild command again.<br />
* For the base packages, you may be able to use the binary packages from your GNU distribution instead of building them from scratch. Check the [[:Category:Installing Sugar|Installing]] or [[:Category:Linux distributions|Linux]] categories for specific distro info.<br />
* You may have some issues with penguintv on ubuntu, just interrupt the pull with a CTRL+C, open a shell, repeat the command manually, and accept the certificate permanently.<br />
* One other fix that I had to do was to export GTK2_RC_FILES=~/src/olpc/sugar-jhbuild/build/share/themes/sugar/gtk-2.0/gtkrc<br />
and also symlink build/share/icons/sugar to build/share/icons/hicolor. These two steps may not be necessary, but they made things work on my Ubuntu installation as of March 31, 2008. [[User:Blaketh|Blaketh]] 03:08, 31 March 2008 (EDT)<br />
<br />
==Run Sugar==<br />
<br />
This command launches the Sugar emulator:<br />
<br />
./sugar-jhbuild run<br />
<br />
To exit the emulator, press Alt-Q.<br />
<br />
== Running multiple instances==<br />
To run multiple instances of sugar you can start it in the following way:<br />
<br />
SUGAR_PROFILE=2 ./sugar-jhbuild run<br />
<br />
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/<br />
<br />
== Run an individual activity ==<br />
<br />
Within sugar, e.g. in Terminal, this command launches an individual activity for testing:<br />
<br />
sugar-launch [bundle name]<br />
<br />
You will see debug output appearing in Terminal.<br />
<br />
== Configure the mode and resolution of Sugar ==<br />
<br />
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''':<br />
<br />
cd sugar-jhbuild<br />
cp install/share/sugar/shell/emulator.py install/share/sugar/shell/emulator.py.backup<br />
nano install/share/sugar/shell/emulator.py<br />
<br />
Find this piece of code:<br />
<br />
<PRE><br />
cmd = [ 'Xephyr' ]<br />
cmd.append(':%d' % display)<br />
cmd.append('-ac')<br />
<br />
if gtk.gdk.screen_width() < 1200 or gtk.gdk.screen_height() < 900:<br />
cmd.append('-fullscreen')<br />
else:<br />
cmd.append('-screen')<br />
cmd.append('%dx%d' % (1200, 900))<br />
</PRE> <br />
<br />
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):<br />
<br />
<PRE><br />
cmd = [ 'Xephyr' ]<br />
cmd.append(':%d' % display)<br />
cmd.append('-ac')<br />
<br />
# if gtk.gdk.screen_width() < 1200 or gtk.gdk.screen_height() < 900:<br />
# cmd.append('-fullscreen')<br />
# else:<br />
cmd.append('-screen')<br />
cmd.append('%dx%d' % (800, 600))<br />
</PRE><br />
<br />
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.<br />
<br />
== Other commands ==<br />
<br />
JHBuild has several other commands that can be useful for development. You can get an overview with:<br />
<br />
./sugar-jhbuild --help-commands<br />
<br />
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.)<br />
<br />
./sugar-jhbuild update<br />
./sugar-jhbuild build<br />
./sugar-jhbuild run<br />
<br />
=== If update and build don't work ===<br />
<br />
In May 2008 there were some changes that broke updates on sugar-jhbuild. A version from before this date cannot update or build after this date; the symptoms are various, but generally include errors which mention the "build-scripts" directory. You need to rebuild from scratch in a new jhbuild directory. Something like the following:<br />
<br />
cd ..<br />
mv sugar-jhbuild sugar-jhbuild.old<br />
git-clone git://dev.laptop.org/sugar-jhbuild<br />
<br />
then, to save bandwidth, move the tar files from your old version:<br />
<br />
mkdir sugar-jhbuild/source<br />
mv sugar-jhbuild.old/source/*.tar* sugar-jhbuild/source<br />
<br />
then build:<br />
<br />
cd sugar-jhbuild<br />
./sugar-jhbuild build<br />
<br />
You may then also see some new dependencies; see the relevant instructions above. <br />
<br />
=== From within Sugar ===<br />
Once you have Sugar running, here are some useful commands:<br />
*'''Alt+Shift+F''' makes the frame appear and disappear<br />
*'''Ctrl-Q''' quits an activity<br />
*'''Alt+Shift+Q''' quits Sugar<br />
*'''Alt+Shift+O''' opens the search<br />
*'''Alt+Shift+R''' rotates the screen<br />
<br />
=== Creating an xsession for Sugar-jhbuild ===<br />
Create the file /usr/share/xsessions/sugar-jhbuild.desktop with the following content:<br />
<br />
[Desktop Entry]<br />
Encoding=UTF-8<br />
Name=Sugar jhbuild<br />
GenericName=Sugar<br />
Exec=/usr/bin/sugar-jhbuild<br />
Type=Application<br />
<br />
Create the file /usr/bin/sugar-jhbuild with the following content:<br />
<br />
#!/bin/sh<br />
export GTK2_RC_FILES=/home/walter/sugar-jhbuild/install/share/sugar/data/sugar-xo.gtkrc<br />
exec /home/walter/sugar-jhbuild/sugar-jhbuild run dbus-launch /home/walter/sugar-jhbuild/install/bin/sugar-shell<br />
<br />
where you substitute the path of wherever you installed sugar-jhbuild for "/home/walter"<br />
<br />
== Customize ==<br />
<br />
To customize the build create a configuration file, named ''.sugar.jhbuildrc'', in your home directory.<br />
<br />
=== Write access to the repositories ===<br />
<br />
If you have write access to the repositories you can add this (if your login name happens to be marco):<br />
repos['gnome.org'] = ':ext:marco@cvs.gnome.org:/cvs/gnome'<br />
repos['mozilla.org'] = ':ext:marco%gnome.org@cvs.mozilla.org:/cvsroot'<br />
repos['dev.laptop.org'] = 'git+ssh://marco@dev.laptop.org/git/'<br />
repos['dev.laptop.org/projects'] = 'git+ssh://marco@dev.laptop.org/git/projects/'<br />
<br />
==Useful Internal Links==<br />
* [[DevelopmentTeam/Understanding the Code|Understanding Sugar Code]]<br />
* [[Taxonomy]] -- explains the components of Sugar (Glucose, Fructose, Sugar, Starches)<br />
* [[Sugar Instructions]] -- how to actually use Sugar once you have it running<br />
<br />
==External links==<br />
<br />
* [http://library.gnome.org/devel/jhbuild/unstable/ JHBuild manual]<br />
* [http://www.redhatmagazine.com/2007/02/23/building-the-xo-introducing-sugar/ Red Hat Magazine article: Introducing Sugar]<br />
* [http://learn.laptop.org/tinderbox/ Tinderbox] (see the "Sugar JHBuild" tab). The old [http://dev.laptop.org/~cjb/sugar-tinder/ sugar-jhbuild tinderbox].<br />
<br />
[[Category:Installing Sugar]]<br />
[[Category:Jhbuild]]</div>Aahttps://wiki.sugarlabs.org/index.php?title=XOCamp_2&diff=14992XOCamp 22009-01-30T23:14:23Z<p>Aa: </p>
<hr />
<div>The second XOCamp is being held January 14-16 in Cambridge, Massachusetts. <br />
<br />
== Fundraising ==<br />
<br />
Much of the original planning for XOCamp 2, including the fundraising and -spending, was actually carried out at SugarCamp. This is documented at [[olpc:XOCamp 2/Old fundraising]].<br />
<br />
For XOCamp 2, it would be good to be able to repeat this fundraising for travel scholarships. There has been a proposal to divide half of all money raised equally, and half proportionally to remaining travel costs, among all attendants who claim a need and are coming from over 500 miles away. Thus if $600 were raised and divided among two people who spent $400 and $800 on tickets, they would get $350 and $550 respectively.<br />
<br />
All donations are tax deductible and should be sent to [[Sugar_Labs/Donate | Sugar Labs]]. Please note your donation or pledge for travel here so that it can be used for this purpose instead of the general fund.<br />
<br />
=== Pledges ===<br />
<br />
Please include contact information. Or, for anonymous donations, contact me: I'm Jameson Quinn, my email is firstname.lastname@gmail.com. (Don't just send a check or we won't know what it's for.)<br />
<br />
''Example:''<br />
<br />
* Charles Babbage pledges <b>5 pounds</b> { babbage at differenceengine dot london }<br />
<br />
''Donations''<br />
<br />
* An anonymous donor pledges $300<br />
<br />
=== Pre-Requests ===<br />
<br />
* Jameson Quinn, from Guatemala, to give a talk on Develop activity. Approximately $650 including bus and airfare.<br />
<br />
* Andres Ambrois, from Uruguay, to ???. Approximately $1300 including bus and airfare.<br />
<br />
* JonasSmedegaard, from Denmark, to help discuss .deb-based packaging. Approximately $670 including bus and airfare.<br />
<br />
* [[User:DanielDrake|DanielDrake]], from UK, approximate cost $600<br />
<br />
* [[User:RafaelOrtiz|RafaelOrtiz]], from Colombia, approximate cost $1300<br />
<br />
* John Dada, from Nigeria, approximate cost $1500<br />
<br />
* [[User:Mokurai|Ed Cherlin]], from California, to give a talk on [[creating textbooks]] approximate cost $300<br />
<br />
* Andrius Kulikauskus, from Bosnia, to discuss textbooks. He needs a ticket one way. About $350.<br />
<br />
=== Clear requests ===<br />
<br />
If you think you "need" (under your definition) help from the $300 travel fund, then please list the following info below:<br />
<br />
* Full name (for check), occupation, citizenship, address, direct travel costs (mainly plane/bus/train tickets; be ready to back it up if asked please), amount of funding from other sources<br />
<br />
(sorry, this may be more info than I need, but better too much than too little.)<br />
<br />
List:<br />
<br />
* Jonas Smedegaard; systems administrator; Denmark; Ringstedvej 24 A, 4440 Mørkøv, Denmark; DKK 3608 (approx. USD 633); DKK 0<br />
* Jameson Quinn; programmer; USA; 31 Ejercito Nacional, San Cristobal de las Casas, Chiapas, México; $445 + 1722 Mexican Pesos ~= $567; $0<br />
* Andres Ambrois; software developer; Uruguay; Rivera 4478, Montevideo, Uruguay; USD 1200 plane + USD 50 bus; 0<br />
<br />
== XOCamp diplomas ==<br />
<br />
If you want an XOCamp diploma to show people that you really did this, please put your name below.</div>Aa