https://wiki.sugarlabs.org/api.php?action=feedcontributions&user=Skierpage&feedformat=atomSugar Labs - User contributions [en]2024-03-29T10:48:40ZUser contributionsMediaWiki 1.35.2https://wiki.sugarlabs.org/index.php?title=Sandbox&diff=77055Sandbox2012-04-06T19:05:28Z<p>Skierpage: test interwiki image links</p>
<hr />
<div>== This is a title ==<br />
<br />
I can write whatever I like...<br />
<br />
* Fish<br />
* Meat<br />
* Veggies<br />
* Icecream<br />
<br />
== Test interwiki links ==<br />
The API call http://wiki.sugarlabs.org/api.php?action=query&meta=siteinfo&siprop=interwikimap dumps the set of interwiki links. [[Special:Interwiki]] provides a tool to edit them. Let's try some links.<br />
* [[olpc:Help Activity refresh]]<br />
* [[wikipedia:Constructionism (learning theory)]]<br />
<br />
== Test Interwiki image links ==<br />
Here's a screenshot from w.l.o, [[olpc:File:Activity_browse.jpg]], with the extra params that usually cause image display.<br />
: [[olpc:File:Activity_browse.jpg|right|400px|thumb|Browse activity]]<br />
doesn't seem to work?!<br />
<br />
== Video support in Mediawiki ==<br />
<br />
These examples use the [http://www.mediawikiwidgets.org/Html5media Html5media widget]:<br />
<br />
=== Webm ===<br />
<br />
{{#widget:Html5media<br />
|url=http://codewiz.org/pub/pictures/vacation/iguazu_itaipu_2010/itaipu/MVI_1052.webm<br />
|width=640<br />
|height=480<br />
}}<br />
<br />
=== AVI mpeg4 x264 ===<br />
<br />
{{#widget:Html5media<br />
|url=http://codewiz.org/pub/pictures/vacation/japan_2009/Shinkansen/00011-x264.avi<br />
|width=640<br />
|height=480<br />
}}<br />
<br />
=== OGG Theora + Vorbis ===<br />
<br />
{{#widget:Html5media<br />
|url=http://codewiz.org/pub/pictures/vacation/japan_2009/Shinkansen/00010.ogg<br />
|width=640<br />
|height=480<br />
}}<br />
<br />
=== AVI mjpeg ===<br />
<br />
{{#widget:Html5media<br />
|url=http://codewiz.org/pub/pictures/vacation/japan_2009/Shinkansen/00008-mjpeg.avi<br />
|width=640<br />
|height=480<br />
}}<br />
<br />
Link to the raw videos:<br />
<br />
* http://codewiz.org/pub/pictures/vacation/iguazu_itaipu_2010/itaipu/MVI_1052.webm<br />
* http://codewiz.org/pub/pictures/vacation/japan_2009/Shinkansen/00011-x264.avi<br />
* http://codewiz.org/pub/pictures/vacation/japan_2009/Shinkansen/00008-mjpeg.avi<br />
* http://codewiz.org/pub/pictures/vacation/japan_2009/Shinkansen/00010.ogg</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Category:Screenshots&diff=77051Category:Screenshots2012-04-06T10:04:34Z<p>Skierpage: categorization test</p>
<hr />
<div>Organize screenshots.<br />
<br />
Screenshots perhaps should also be categorized by Sugar/OLPC release version (or just replace with latest version?), locale (en_US, es,?) and if they're used in a final published manual version.<br />
<br />
Hundreds of images on {{SERVERNAME}} aren't categorized, see [[Special:AllPages/File:]]</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=File:Portfolio-thumbs.png&diff=77050File:Portfolio-thumbs.png2012-04-06T09:49:26Z<p>Skierpage: </p>
<hr />
<div>[[category:activity screenshots]]</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=File:Portfolio-Tool.png&diff=77049File:Portfolio-Tool.png2012-04-06T09:47:26Z<p>Skierpage: categorization test</p>
<hr />
<div>[[category:activity screenshots]]</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Category:Activity_screenshots&diff=77048Category:Activity screenshots2012-04-06T09:46:11Z<p>Skierpage: categorization test</p>
<hr />
<div>[[category:screenshots]]</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Category:Partial_screenshots&diff=77047Category:Partial screenshots2012-04-06T09:45:37Z<p>Skierpage: categorization test</p>
<hr />
<div>[[category:screenshots]]</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=File:Portfolio_toolbar-1.png&diff=77046File:Portfolio toolbar-1.png2012-04-06T09:45:00Z<p>Skierpage: categorization test</p>
<hr />
<div>[[Category:Partial screenshots]]<br />
[[Category:Activity screenshots]]</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Category:Activity&diff=77045Category:Activity2012-04-06T08:21:53Z<p>Skierpage: point people to Category:Activities</p>
<hr />
<div>Page was moved to [[:Category:Activity Team]].<br />
<br />
''Most of the pages in this category are '''in error''''', Activites belong in [[:Category:Activities]].</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Sandbox&diff=77044Sandbox2012-04-06T08:13:10Z<p>Skierpage: /* Test interwiki links */ typo</p>
<hr />
<div>== This is a title ==<br />
<br />
I can write whatever I like...<br />
<br />
* Fish<br />
* Meat<br />
* Veggies<br />
* Icecream<br />
<br />
== Test interwiki links ==<br />
The API call http://wiki.sugarlabs.org/api.php?action=query&meta=siteinfo&siprop=interwikimap dumps the set of interwiki links. Let's try some.<br />
* [[olpc:Help Activity refresh]]<br />
* [[wikipedia:Constructionism (learning theory)]]<br />
<br />
=== Another title ===<br />
<br />
blah blah blah...<br />
<br />
== Video support in Mediawiki ==<br />
<br />
These examples use the [http://www.mediawikiwidgets.org/Html5media Html5media widget]:<br />
<br />
=== Webm ===<br />
<br />
{{#widget:Html5media<br />
|url=http://codewiz.org/pub/pictures/vacation/iguazu_itaipu_2010/itaipu/MVI_1052.webm<br />
|width=640<br />
|height=480<br />
}}<br />
<br />
=== AVI mpeg4 x264 ===<br />
<br />
{{#widget:Html5media<br />
|url=http://codewiz.org/pub/pictures/vacation/japan_2009/Shinkansen/00011-x264.avi<br />
|width=640<br />
|height=480<br />
}}<br />
<br />
=== OGG Theora + Vorbis ===<br />
<br />
{{#widget:Html5media<br />
|url=http://codewiz.org/pub/pictures/vacation/japan_2009/Shinkansen/00010.ogg<br />
|width=640<br />
|height=480<br />
}}<br />
<br />
=== AVI mjpeg ===<br />
<br />
{{#widget:Html5media<br />
|url=http://codewiz.org/pub/pictures/vacation/japan_2009/Shinkansen/00008-mjpeg.avi<br />
|width=640<br />
|height=480<br />
}}<br />
<br />
Link to the raw videos:<br />
<br />
* http://codewiz.org/pub/pictures/vacation/iguazu_itaipu_2010/itaipu/MVI_1052.webm<br />
* http://codewiz.org/pub/pictures/vacation/japan_2009/Shinkansen/00011-x264.avi<br />
* http://codewiz.org/pub/pictures/vacation/japan_2009/Shinkansen/00008-mjpeg.avi<br />
* http://codewiz.org/pub/pictures/vacation/japan_2009/Shinkansen/00010.ogg</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Sandbox&diff=77043Sandbox2012-04-06T08:12:10Z<p>Skierpage: test interwiki links</p>
<hr />
<div>== This is a title ==<br />
<br />
I can write whatever I like...<br />
<br />
* Fish<br />
* Meat<br />
* Veggies<br />
* Icecream<br />
<br />
== Test interwiki links ==<br />
The API call http://wiki.sugarlabs.org/api.php?action=query&meta=siteinfo&siprop=interwikimap dumps the set of interwiki links. Let's try some.<br />
* [[olpc:Help Manual refresh]]<br />
* [[wikipedia:Constructionism (learning theory)]]<br />
<br />
=== Another title ===<br />
<br />
blah blah blah...<br />
<br />
== Video support in Mediawiki ==<br />
<br />
These examples use the [http://www.mediawikiwidgets.org/Html5media Html5media widget]:<br />
<br />
=== Webm ===<br />
<br />
{{#widget:Html5media<br />
|url=http://codewiz.org/pub/pictures/vacation/iguazu_itaipu_2010/itaipu/MVI_1052.webm<br />
|width=640<br />
|height=480<br />
}}<br />
<br />
=== AVI mpeg4 x264 ===<br />
<br />
{{#widget:Html5media<br />
|url=http://codewiz.org/pub/pictures/vacation/japan_2009/Shinkansen/00011-x264.avi<br />
|width=640<br />
|height=480<br />
}}<br />
<br />
=== OGG Theora + Vorbis ===<br />
<br />
{{#widget:Html5media<br />
|url=http://codewiz.org/pub/pictures/vacation/japan_2009/Shinkansen/00010.ogg<br />
|width=640<br />
|height=480<br />
}}<br />
<br />
=== AVI mjpeg ===<br />
<br />
{{#widget:Html5media<br />
|url=http://codewiz.org/pub/pictures/vacation/japan_2009/Shinkansen/00008-mjpeg.avi<br />
|width=640<br />
|height=480<br />
}}<br />
<br />
Link to the raw videos:<br />
<br />
* http://codewiz.org/pub/pictures/vacation/iguazu_itaipu_2010/itaipu/MVI_1052.webm<br />
* http://codewiz.org/pub/pictures/vacation/japan_2009/Shinkansen/00011-x264.avi<br />
* http://codewiz.org/pub/pictures/vacation/japan_2009/Shinkansen/00008-mjpeg.avi<br />
* http://codewiz.org/pub/pictures/vacation/japan_2009/Shinkansen/00010.ogg</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=SoaS/Testing&diff=76094SoaS/Testing2012-03-04T05:20:07Z<p>Skierpage: also link to activity matrix results</p>
<hr />
<div>* Most recent test results are in sections underneath [[Community/Distributions/Fedora-SoaS#Testing_Results]]<br />
* Some test results from 2010 are in the table on [[Sugar on a Stick QA]]<br />
* Some test results in 2009 were reported as subpages of this page, see list below.<br />
* Some test results for SoaS testing, along with other Sugar environments, are in a [https://docs.google.com/spreadsheet/ccc?key=0AntaXnq4oy2_dHpvZHhLeGRQYzc1cDlRZU9Mc1NldGc#gid=0 Google Docs spreadsheet]<br />
* Activity testing results in SoaS, along with other Sugar environments, are on the pages [[Sugar Creation Kit/sck/Activity Matrix(A to I)]] and [[Sugar Creation Kit/sck/Activity Matrix(J to Z)|...(J to Z)]]<br />
<br />
== Subpages of {{FULLPAGENAME}}==<br />
{{Special:PrefixIndex/{{FULLPAGENAME}}/}}<br />
<br />
[[Category:Testing]]</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Testing/Reports/Activity_Matrix_(A_to_I)&diff=76093Testing/Reports/Activity Matrix (A to I)2012-03-04T05:18:22Z<p>Skierpage: add Category:Testing</p>
<hr />
<div>* '''Use the ← left___________Center_____________right → links in the colored bar below<br />
:to connect to another part of this Annotated Guide to Sugar'''<br />
{| width="100%" cellpadding="0" cellspacing="0"<br />
|-<br />
|width=25% align=left bgcolor=#C3D9FF|&larr; '''[[Sugar_Creation_Kit/sck/Introduction_to_Sugar_Interface|Introduction to the Sugar Interface]]'''<br />
|width=50% align=center bgcolor=#C3D9FF|'''[[Sugar_Creation_Kit#All_Prebuilt_VirtualBox_Appliances|VirtualBox Appliances]]'''<br />
|width=25% align=right bgcolor=#C3D9FF| '''[[Sugar_Creation_Kit#Community_Distributions_Complete_Listing|Community Distributions]]''' &rarr;<br />
|}<br />
{| width="100%" cellpadding="0" cellspacing="0"<br />
|-<br />
|width=25% align=left bgcolor=#C3D9FF|&larr; '''[[Sugar_Creation_Kit/sck/How_to_use_Chat-es| Cómo usar Chat ]]'''<br />
|width=50% align=center bgcolor=#C3D9FF|'''[[Sugar_Creation_Kit/sck/Introduction_to_Sugar_Interface-es|Introducción a la interfaz de Azúcar]]'''<br />
|width=25% align=right bgcolor=#C3D9FF| '''←[[Sugar_Creation_Kit#Introducci.C3.B3n_a_la_interfaz_de_Az.C3.BAcar|Azúcar Creación Kit ]]'''<br />
|}<br />
<br />
*GO TO: [[Sugar_Creation_Kit/sck/Activity_Matrix(J_to_Z)|'''Most Recent-Activity Test Results J thru Z''']]<br />
<br />
====='''Most Recent-Activity Test Results - (A to I)'''=====<br />
*:: Please help edit this wiki page with your test results.<br />
<br />
*This is a list of Activity Tests for [http://wiki.sugarlabs.org/go/Dextrose Dextrose]; [[Sugar_on_a_Stick/Coconut|Soas-v5 Coconut]]; [[Trisquel_On_A_Sugar_Toast|Trisquel-5-Sugar]]; [[Sugar_on_a_Stick/Pineapple|SoaS-v6 Pineapple]] and [http://wiki.laptop.org/go/Release_notes/11.3.0 os833]<br />
*Click here to go to [http://wiki.sugarlabs.org/go/Talk:Sugar_Creation_Kit/sck/Activity_Matrix'''Older Versions of Sugar''' ] testing of Activities on SoaS-v1 to SoaS-v4 <br />
* Also see this Google Spreadsheet '''Tests-Sugar-0.94.1''': https://docs.google.com/spreadsheet/ccc?key=0AntaXnq4oy2_dHpvZHhLeGRQYzc1cDlRZU9Mc1NldGc#gid=0<br />
::Authored by Alan Jhonn Aguiar Schwyn<br />
<br />
* '''A Master list of Activities and testing in various versions of Sugar are listed below:'''<br />
:'''Tested from a Booted Live CD using a [http://download.sugarlabs.org/images/ASLOxo6-3.iso ASLOxo USB]-stick''' Files were copied to a 4 GB USB-stick from the burned CD<br />
: Activities were tested using a ACER ASPIRE ONE N450 10" netbook with external USB DVD/CD. Except for activities tested on the XO-1 and XO-1.5<br />
<br />
*Sources: ASLOxo CD + Activities announced on the sugar-devel@lists.sugarlabs.org. Updated to:-- 06 Feb 2012 <br />
<br />
*'''KEY''' Included on DVD or ASLOxo '''(version #) yes/no ASLO''' ('''-64''') = 64 bit<br />
{| class="wikitable sortable"<br />
<br />
|+Did activity start-stop-save and resume from journal? (yes/no); share offered = [[File:Mesh_key_f1_small.png |15px]]; recommended = & <br />
<br />
|-<br />
<br />
!Alphabetic !![http://download.sugarlabs.org/activities/ Activites] Numeric!![http://koji.fedoraproject.org/koji/getfile?taskID=3764890&name=Fedora-17-Nightly-20120205.21-i686-Live-soas.iso SoaS-v7] 0.95.4!!0.92.2 XO-1.5 os874!!0.88.1 XO-1 [http://wiki.sugarlabs.org/go/Dextrose os508dx] !!0.94.1-[[Sugar_on_a_Stick/Pineapple|SoaS-v6 Pineapple]] !!0.94-[[Community/Distributions/Sweets_Distribution|Sweets]] [[Trisquel_On_A_Sugar_Toast|Trisquel-5-Sugar]] !!0.92.1-[[Sugar_on_a_Stick/Coconut|Soas-v5 Coconut]] !!0.94.1 XO-1 [http://wiki.laptop.org/go/Release_notes/11.3.0 os833]!!0.94.1 XO-1.5 [http://wiki.laptop.org/go/Release_notes/11.3.0 os833]!! class="unsortable" | Notes and Bug No.<br />
<br />
|-<br />
<br />
|Abacus ||4293 ||31 yes||19 yes ||19 yes||26 yes||13 yes||19 yes||24 yes||24 yes|| Multiple forms of Abacus that work and teach math<br />
<br />
|-<br />
<br />
|ajedrez||4268||&nbsp; ||&nbsp;||&nbsp; ||1 yes? ASLO*||&nbsp; ||&nbsp; ||1 yes ASLO||&nbsp; ||Ceibal-Chess *extends past screen on 10"netbook not fully sugarized<br />
<br />
|-<br />
<br />
|Analyze || 4200 ||8 yes ASLO *||&nbsp;||&nbsp;||8 yes* ASLO||8 yes* ASLO||8 yes* ASLO||8 yes*ASLO||&nbsp; ||Analyze is an Activity that displays your networking, X (graphical) display, and presence service status. It is useful to developers, testers and end-users as an easy way to monitor and submit data for monitoring/debugging networking/X issues.*no longer sees Presence service on jabber<br />
<br />
|-<br />
<br />
|APRS-xo ||4087||&nbsp;||&nbsp;||&nbsp;||14 yes ASLO *||14 yes ASLO *||&nbsp;||&nbsp;||14 yes ASLO*||This amateur radio program will update your position and status on all of the global APRS web pages once every 10 minutes * '''Callsign & Password required'''<br />
<br />
|-<br />
<br />
|Arithmetic||4204 ||2 yes ASLO*||&nbsp;||2 yes||2 yes ASLO||2 yes ||3 yes||2 yes ASLO[[File:Mesh_key_f1_small.png |15px]]||&nbsp;||Arithmetic is an activity that allows learners to compete in maths <br />
challenges. Learners choose their a difficulty level and whether to do addition, subtraction, multiplication or division. Challenges work by<br />
Arithmetic providing questions to every learner sharing the activity. Responses to those questions are checked and timed. The results are presented on a scoreboard." * does not save activity's name in journal<br />
<br />
|-<br />
<br />
|Backup &||4326 ||5 yes ASLO||&nbsp;||&nbsp; ||5 yes ASLO||5 yes ASLO||5 yes ASLO||&nbsp; ||5 yes ASLO||Backup stores the content of the Sugar Journal (or rather the Sugar data store) as multi-entry Journal entry bundles (JEBs) on external storage media.<br />
The Restore activity can be used to write back the content of these bundles.<br />
<br />
Supports any data store from 0.84 on, including those with version support. <br />
<br />
|-<br />
<br />
|blockhead||4207 ||7 '''no'''ASLO *||&nbsp; ||&nbsp; ||7 '''no''' ASLO||7 '''no'''||7 '''no'''||&nbsp;||&nbsp;|| Game add Blocks to teach addition * starts to grey screen<br />
<br />
|-<br />
<br />
|Blockparty||4232 ||7 yes ASLO||&nbsp;||&nbsp; ||7 yes ASLO||7 yes||7 yes||7 yes ASLO||&nbsp;|| falling blocks of various shapes- game - <enter> starts <esc> stops<br />
<br />
|-<br />
<br />
|boxes ||4371||22 yes ASLO||&nbsp; ||&nbsp; ||&nbsp; ||22 yes ||&nbsp; ||22 yes ASLO ||&nbsp; ||Game to fill boxes XO avitar(you) versus installed opponent.<br />
<br />
|-<br />
<br />
|Browse||4024 ||131 yes ASLO; 130***||122.2 yes||129 yes||131'''no''' **;129'''no''' ASLO; 130'''no''' ASLO**||129 yes||'''no'''||131'''no''' ASLO * ##;129.1 yes||129.1 yes||*will not start. '''surf-115''' is used in Soas-v5 and Soas-v6 ** browse 131 and 130 are not compatible uses gtk +3''' ***No bookmarks http://bugs.sugarlabs.org/ticket/3300 ## '''cannot erase''' lose working browser!<br />
<br />
|-<br />
<br />
|C.M.D||4478 ||1 yes ASLO||&nbsp; ||&nbsp; ||1 yes ASLO||1 yes ASLO||&nbsp; ||&nbsp; ||&nbsp; ||Units Conversion-Text based in Spanish<br />
<br />
|-<br />
The Flip activity is available for download from the [http://activities.sugarlabs.org Sugar activity portal]: [http://activities.sugarlabs.org/en-US/sugar/addon/4518 Flip]<br />
|Calculate||4076 ||38 yes||37 yes||&nbsp;||38 yes||38 yes||37 yes||37 yes [[File:Mesh_key_f1_small.png |15px]]<br />
||37 yes||great calculator <br />
<br />
|-<br />
<br />
|calendario &||4360||4 yes ASLO||&nbsp; ||&nbsp;||3 yes ASLO||3 yes||3 yes||3 yes ASLO[[File:Mesh_key_f1_small.png |15px]]||&nbsp; ||Calendario is a daily activity for sugar, this will allow children to introduce activities per day so they are reminded of past, present and future activities.<br />
|-<br />
<br />
|Card sort||4217 ||6 yes ASLO||&nbsp;||&nbsp;||&nbsp;||6 yes||6 yes;||6 yes ASLO[[File:Mesh_key_f1_small.png |15px]]||&nbsp;||sort cards-game<br />
<br />
|-<br />
<br />
|Cartoon Builder||4037||9 yes ASLO||&nbsp;||&nbsp; ||9 yes ASLO||11 yes ||9 yes||9 yes* ASLO[[File:Mesh_key_f1_small.png |15px]]||&nbsp;||MaMaMedia Cartoon Builder (put animations in strip and play) MaMaMedia * long load<br />
<br />
|-<br />
<br />
|Chat||4069 ||73 yes||70 yes||70 yes||73 yes||73 yes||71 yes; 73 yes||71 yes [[File:Mesh_key_f1_small.png |15px]]||71 yes||[http://wiki.laptop.org/go/Tests/Activity/Chat/Public_chat Chat] [http://en.flossmanuals.net/chat Chat]<br />
<br />
|-<br />
<br />
|cebalradio ||4365||1 '''no'''***ASLO||&nbsp; ||&nbsp; || 1'''no''' ASLO*||&nbsp; ||&nbsp; ||&nbsp; ||1 yes ASLO ** [[File:Mesh_key_f1_small.png |15px]]||*no sound or connection **Plays radio [https://sites.google.com/site/sugaractivities/home/programando-en-la-xo/sugarizar-una-aplicacion How to get Cebal_Radio to work on an XO-1](in spanish) also see:[[Sugar_Creation_Kit#How_to_Sugarize_an_Application| How_to_Sugarize_an_Application]] ***Crashes<br />
<br />
|-<br />
<br />
|Clock||4191 ||7 yes||6 yes||&nbsp; ||7 yes||5 yes||6 yes||6 yes||6 yes||A simple Activity to learn how to read and tell the time -5 <br />
<br />
|-<br />
<br />
|Classroom Broadcast ||4507 ||&nbsp;||&nbsp; ||&nbsp; ||no 4 ASLO*; no 3 ASLO||'''no 4*'''||'''no 4*'''||6 '''no''' **||&nbsp; ||*4 after start nothing in Acer Aspire ONE N450 ** Starts to Green Button then nothing - "force quit<br />
"Release notes:-New clasroomBroadcast activity based on vnclauncher<br />
it broadcast a sugar screen for teachers use (for example).<br />
Caveats:*Needs X11VNC to start<br />
<br />
<br />
|-<br />
<br />
|colors ||4067 ||15 '''no'''*ASLO||&nbsp;||15 yes||15 '''no*''' ASLO||15 yes||15 '''no'''*||&nbsp;||&nbsp;||colors drawing program * fails to start<br />
<br />
|-<br />
<br />
|Color Deducto ||4221 ||4 yes ASLO||&nbsp;||&nbsp;||4 yes ASLO||4 yes ASLO||4 yes ASLO||&nbsp;||&nbsp;||a logic game involving deduction<br />
<br />
|-<br />
<br />
|conozco_alimemtos||4324||2 yes ASLO||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||2 yes ASLO ||&nbsp; || food groups - spanish <br />
<br />
|-<br />
<br />
|conozco_america ||4464||3 yes ASLO;||&nbsp; ||&nbsp; ||3 yes ASLO||3 yes ASLO ||3 yes ASLO ||&nbsp; ||&nbsp; ||Answer questions on geography - english<br />
<br />
|-<br />
<br />
|conozco-paraguay ||4469||7 yes ASLO||&nbsp; ||&nbsp; ||&nbsp; ||2 yes ASLO ||&nbsp; ||&nbsp; ||&nbsp; ||geography-sounds<br />
<br />
|-<br />
<br />
|Connect||&nbsp;||22 yes ASLO||&nbsp; ||&nbsp;||22 yes* ASLO ||22 yes* |&nbsp;||22 yes *||22 yes* [[File:Mesh_key_f1_small.png |15px]]||&nbsp;|| [http://wiki.laptop.org/go/Connect Connect][http://dev.laptop.org/~morgan/bundles/Connect-22.xo Connect-22.xo] * requires a shared user to connect to play<br />
<br />
|-<br />
<br />
|constellationflashcards||4318||1 '''no'''ASLO*||&nbsp; ||&nbsp; ||1 '''no'''ASLO*||1 '''no'''*||&nbsp; ||1 '''no''' *||&nbsp; ||*starts but no constellation shown in quiz<br />
<br />
|-<br />
<br />
|countries||4528||33 yes ASLO||&nbsp; ||&nbsp; ||33 yes ASLO||&nbsp; ||&nbsp; ||33 yes ASLO||&nbsp;||Players have to type in a country for each letter of the alphabet. Successes are rewarded with the display of the country's flag. The activity 'knows' the English names of 212 countries. '''no icon (grey circle)'''<br />
<br />
<br />
|-<br />
<br />
|deducto||4220 ||4 yes ASLO||&nbsp;||&nbsp; ||4 yes ASLO ||4 yes ASLO ||4 yes ASLO||&nbsp;||&nbsp;||a logic game involving deduction<br />
<br />
|-<br />
<br />
|Develop ||4058 ||39 '''no'''*ASLO||&nbsp;||&nbsp; ||39 '''no*''' ASLO||39 '''no*''' ASLO||39 yes||39 yes?[[File:Mesh_key_f1_small.png |15px]]** ASLO ||&nbsp;||open-sugar-apps [http://wiki.laptop.org/go/Develop Develop]'''Develop a new or existing activity''' * fails to start ** new and open fail<br />
<br />
|-<br />
<br />
|Distance ||4264 ||&nbsp;||22 yes||22 yes||18 yes* ASLO||18 yes*||18 yes *||28 yes [[File:Mesh_key_f1_small.png |15px]]||28 yes||worked beween XO-1 and Acer Aspire One * starts but needs 2 XO-1 to work<br />
<br />
|-<br />
<br />
|Domino ||4212 ||8 yes ASLO||&nbsp;||&nbsp; ||8 yes ASLO||8 yes ASLO||8 yes ASLO||8 yes ASLO [[File:Mesh_key_f1_small.png |15px]]||&nbsp; ||game of dominos<br />
<br />
|-<br />
<br />
|DrGeoii||4323 ||1112 yes ASLO||&nbsp;||&nbsp;||1112 yes ASLO||1112 yes ASLO ||1112 yes ASLO||1112 yes ASLO||&nbsp;||Complex Geometry with Macros (non standard sugar interface) Use <esc> to get exit drop down or click on white box top left corner<br />
<br />
|-<br />
<br />
|EatBoom||4225||2 '''no''' ASLO *||&nbsp; ||&nbsp; ||&nbsp; ||2 yes||&nbsp; ||&nbsp; ||&nbsp; ||game uses arrow keys to move *fails to start<br />
<br />
|-<br />
<br />
|Ecomundo||4213 ||2 yes||&nbsp;||&nbsp; ||2 yes ASLO||2 yes ASLO ||2 yes ASLO||&nbsp;||&nbsp;||rabbits vs fox game<br />
<br />
|-<br />
<br />
|Edit||4349 ||8 yes ASLO ||&nbsp;||&nbsp; ||8 yes ASLO||8 yes ASLO||8 yes ASLO||&nbsp; ||8 yes ASLO [[File:Mesh_key_f1_small.png |15px]]||simple text editor <br />
<br />
|-<br />
<br />
|el_secreto_de_grakken ||4473||&nbsp;||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||4 yes ASLO ||&nbsp; ||Text based - spanish<br />
<br />
|-<br />
<br />
|elementsactivity ||4214||2 '''no'''*ASLO||&nbsp; ||&nbsp; ||2 '''no'''ASLO*||2 yes ASLO||&nbsp; ||2 yes ASLO ||&nbsp; ||atomic periodic table with wikipedia links (spanish) * failed to start<br />
<br />
|-<br />
<br />
|End Game ||4565 ||28 yes ASLO||&nbsp; ||&nbsp; ||28 yes ASLO ||28 yes ASLO ||28 yes ASLO ||&nbsp; ||&nbsp; ||chess- unable to figure out actions<br />
<br />
|-<br />
<br />
|Etoys ||4030 ||116 '''no'''*||113 yes||116 yes||116 yes||116 yes||113 '''no''' ||113 yes [[File:Mesh_key_f1_small.png |15px]]||113 yes|| Etoys *DBusError<br />
<br />
|-<br />
<br />
|filemixauto||4402||5 yes ASLO;||&nbsp; ||&nbsp; ||&nbsp; ||5 yes ||&nbsp; ||&nbsp; ||&nbsp; ||Audio File Looper/Mixer/Processor for Children--sound works<br />
<br />
|-<br />
<br />
|fileshare||4266||10 yes ASLO *||&nbsp; ||&nbsp; ||10 yes ASLO *||&nbsp; ||&nbsp; ||&nbsp; ||10 yes ASLO * [[File:Mesh_key_f1_small.png |15px]]||FileShare is an activity that allows the user to share files from their journal to other xo's or to a central server. *unable to test shareing<br />
<br />
|-<br />
<br />
|Finance||4040 ||3 yes ASLO*||3 yes||&nbsp;||3 yes ASLO||3 yes||3 yes||3 yes ASLO||6 yes||Double Entry accounting *(?) button over rides another in top bar<br />
<br />
|-<br />
<br />
|Firefox ||4262 ||6 yes ASLO||yes 6 ASLO||yes 6 ASLO||yes 6 ASLO||yes ASLO||6 yes ASLO||6 yes ASLO ||&nbsp; ||Does not access sugar-journal shows:"failed to load" pop up message after exit, but '''works well''' Download: [http://people.sugarlabs.org/Tgillard/firefox-6.xo firefox-6.xo]<br />
<br />
|-<br />
<br />
|Flip ||4518 ||2 yes ASLO||&nbsp; ||&nbsp; ||2 yes ASLO||2 yes ASLO||2 yes ASLO||2 yes ASLO||&nbsp; ||Click on a dot and it will reverse its state (color) and that of its immediate neighbors to the north, south, east, and west. You win when all of the dots are of the same state (color). <br />
<br />
|-<br />
<br />
|Flipsticks||4044 ||11; 7 yes ASLO||&nbsp;||8 yes||11; 7 yes ASLO||8 yes||11 yes ASLO;7 yes ||7 yes ASLO [[File:Mesh_key_f1_small.png |15px]]||&nbsp;||animation game;stick figures <br />
<br />
|-<br />
<br />
|follow_me||4354 ||22 yes ASLO||&nbsp; ||&nbsp; ||14 yes ASLO ||14 yes ||14 yes ||&nbsp; ||&nbsp; ||A simple little game which requires good concentration. Click on highlighted pictures<br />
Pupils are presented with an ever increasing sequence of pictures which they have to imitate.<br />
The Best Score is 'remembered' so the game provides a continual challenge to improve. My best is 40.<br />
<br />
|-<br />
<br />
|foodforce ||4206 ||2-5 yes ASLO||&nbsp;||&nbsp; ||3 '''no'''* ASLO ||2-5 yes||2-5 yes||&nbsp;||&nbsp;||learn about world hunger in interactive training *crashes on start new game plays nice sound track<br />
<br />
|-<br />
<br />
|fotoToon ||4253||10 yes ASLO||7 yes||6 yes||5 yes ASLO||5 yes ||5 yes ||10yes ||10 yes||Add images and notes to circles on screen<br />
<br />
|-<br />
<br />
|freecell||4054||3 ''yes?''' ASLO*||&nbsp;||&nbsp; ||3 yes ASLO||3 yes||3 yes||&nbsp;||&nbsp; ||Card Game *MessageNotUnderstood: UndefinedObje... still plays<br />
<br />
|-<br />
<br />
|Free From Malaria ||4309 ||4-2 yesASLO*||&nbsp; ||&nbsp;||yes 4 ASLO||4.2a yes ||4 yes ||&nbsp; ||&nbsp; ||need to click license screen to start- (OK) Series of colored drawings showing mosquitos-starts *NO SOUND<br />
<br />
|-<br />
<br />
|Gcompris_admin||4314||17 '''no'''ASLO*||&nbsp;||&nbsp; ||15 '''no''' ASLO||17 '''no'''ASLO*; 15 '''no''' ASLO*||15 '''no''' ASLO*||15 '''no'''* ASLO||&nbsp; ||Teachers Admin of Gcompris-15 - Gcompris_administration-15.xo *Could not find the board menu or plug in execution error<br />
<br />
|-<br />
<br />
|Gcompris||4313||17 yes ASLO****||&nbsp; ||&nbsp;||17 yes ASLO;||17 yes ASLO***; 15 yes ASLO ||15 yes||15 yes ASLO**||&nbsp; ||Package of GCompris Programs -114 activities with music (v9.3) *failed to start **slow load + 2 minutes (BIG) ***quick load ****"Journal full" after exit<br />
<br />
|-<br />
<br />
|get_ia_books||4194 ||5 yes ASLO****||&nbsp;||&nbsp;||5 yes ASLO||5 '''yes*'''||5 yes||15 yes ASLO||&nbsp; || import as: Deja Vu PDF -(B/W-Color) '''*b/w pdf version starts in read in Trisquel 5'''****"Journal full" <br />
<br />
|-<br />
<br />
|Get_books||4304 ||10 yes ASLO****||7 yes ||5 yes||6 and 5 '''no'''* ASLO||10 yes ASLO***;'''6 and 5 yes**'''||6 '''no'''||6 '''no''' ASLO||10 yes||pdf/epub *failed to start '''** pdf version starts in read in Trisquel 5''' ***10 is indexed by categories; reads .pdf download<br />
<br />
|-<br />
<br />
|GeoGebra||4284||5 yes ASLO||&nbsp; ||&nbsp; ||&nbsp; ||5 yes ASLO * ||&nbsp; ||&nbsp; ||5 '''no''' ASLO ** ||Plotting Proram - "Dynamic Mathematics for Everyone" http://ww.geogebra.org/ *does not save to sugar-journal **starts to white screen<br />
<br />
|-<br />
<br />
|geojam||4356||1 yes ASLO||&nbsp; ||&nbsp; ||&nbsp; ||1 yes ||&nbsp; ||&nbsp; ||&nbsp; ||Downloads google maps from internet -Spanish<br />
<br />
|-<br />
<br />
|HelloWorld ||4418||5; 4 yes ASLO||2 yes||&nbsp; ||5 '''no''' *; 3 yes ASLO||3 yes||3 yes ||5 '''no'' ASLO *; 3 yes ||3 yes||simple program to print Hello World! on screen *failed to start<br />
<br />
|-<br />
<br />
|Help||4051||13 '''no''' ASLO*||12 yes ||&nbsp; ||13 '''no'''* ASLO||13 yes||13 '''no'''||13 yes ||13 yes||*failed to start<br />
<br />
|-<br />
<br />
|help_arabic ||4332|| 5 '''no''' ASLO*||&nbsp; ||&nbsp; ||5 '''no''' *||'''5 yes''' ||5 '''no'''||5 yes ASLO ||&nbsp; ||*failed to start<br />
<br />
|-<br />
<br />
|Hop-a-round||4209 ||2 yes?*ASLO||&nbsp;||&nbsp; ||&nbsp;||2 yes?*||&nbsp; ||&nbsp; ||&nbsp;||grasshopper teaches how to round numbers *only initial screen starts<br />
<br />
|-<br />
<br />
|I can Read||4529||3 yes ASLO*; 1 yes ASLO||&nbsp; ||&nbsp; ||1 yes ASLO-64 ||&nbsp; ||&nbsp; ||1 yes ASLO||&nbsp;||I can read is an activity for introducing the basics of phonetic reading. It displays letters and images and associated sound files, such as 'A as in apple'. It also puts the letters into a context that coalesces into words and phrases as more letters are added. Students can hear sounds and record their own voice either repeating the sound or reading aloud *spanish<br />
<br />
|-<br />
<br />
|Image viewer||4032||19 yes ||17 yes||17 yes||19 yes||19 yes ||17 yes||18 yes [[File:Mesh_key_f1_small.png |15px]] ||18 yes||Display images from Journal<br />
<br />
|-<br />
<br />
|Implode ||4086 ||10 yes ASLO||10 yes||10 yes||10 yes||10 yes||10 yes||10 yes||10 yes||Game-Delete sets of blocks <br />
<br />
|-<br />
<br />
|InfoSlicer||4042 ||12 yes ASLO||9 yes||&nbsp;||yes 12||8 yes||12 yes ||12 yes ASLO||10 yes|| Downloads articles from Wikipedia - 12 does DL of "olpc" article OK<br />
<br />
|-<br />
<br />
|IRC ||4029 ||10 yes||yes 10 ||9 yes||10 yes||9 yes||10 yes||10 yes ASLO||&nbsp;||freenode IRC #sugar & #sugar-es (translate en to es)<br />
<br />
|-<br />
<br />
|&ndash; ||&nbsp;||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp;||&nbsp;<br />
<br />
|-<br />
<br />
|&ndash; ||&nbsp;||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp;||&nbsp;<br />
<br />
|-<br />
<br />
|&ndash; ||&nbsp;||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp;||&nbsp;<br />
<br />
|-<br />
<br />
|&ndash; ||&nbsp;||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp;||&nbsp;<br />
<br />
|-<br />
<br />
|&ndash; ||&nbsp;||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp;||&nbsp;<br />
<br />
|}<br />
*GO TO: [[Sugar_Creation_Kit/sck/Activity_Matrix(J_to_Z)|'''Most Recent-Activity Test Results J thru Z''']]<br />
<br />
* '''Use the ← left___________Center_____________right → links in the colored bar below<br />
:to connect to another part of this Annotated Guide to Sugar'''<br />
{| width="100%" cellpadding="0" cellspacing="0"<br />
|-<br />
|width=25% align=left bgcolor=#C3D9FF|&larr; '''[[Sugar_Creation_Kit/sck/Introduction_to_Sugar_Interface|Introduction to the Sugar Interface]]'''<br />
|width=50% align=center bgcolor=#C3D9FF|'''[[Sugar_Creation_Kit#All_Prebuilt_VirtualBox_Appliances|VirtualBox Appliances]]'''<br />
|width=25% align=right bgcolor=#C3D9FF| '''[[Sugar_Creation_Kit#Community_Distributions_Complete_Listing|Community Distributions]]''' &rarr;<br />
|}<br />
{| width="100%" cellpadding="0" cellspacing="0"<br />
|-<br />
|width=25% align=left bgcolor=#C3D9FF|&larr; '''[[Sugar_Creation_Kit/sck/How_to_use_Chat-es| Cómo usar Chat ]]'''<br />
|width=50% align=center bgcolor=#C3D9FF|'''[[Sugar_Creation_Kit/sck/Introduction_to_Sugar_Interface-es|Introducción a la interfaz de Azúcar]]'''<br />
|width=25% align=right bgcolor=#C3D9FF| '''←[[Sugar_Creation_Kit#Introducci.C3.B3n_a_la_interfaz_de_Az.C3.BAcar|Azúcar Creación Kit ]]'''<br />
|}<br />
[[Category:Testing]]</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Category:Testing&diff=76092Category:Testing2012-03-04T05:06:30Z<p>Skierpage: remove bogus PrefIndex invocation</p>
<hr />
<div>Pages with Sugar testing results and observations.</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=0.94/Testing&diff=760910.94/Testing2012-03-04T05:04:26Z<p>Skierpage: /* SoaS */ better link</p>
<hr />
<div><noinclude><br />
[[Category:Testing]]<br />
</noinclude><br />
== How to contribute with testing ==<br />
It is very important to get feedback during the development cycle to fix bugs as early as possible and to get a stable release at the end. The order of stability depends among other things as well on '''you'''. <br />
<br />
If you find bugs please report them into the [http://bugs.sugarlabs.org/ Sugar Labs bug tracker] indicating the 0.93.x version in the ticket version field. If you have hardware from OLPC you can use one of the current development builds for testing: [http://build.laptop.org/11.3.0/os3/ os3] for the i686 architecture (XO 1 and XO 1.5) and [http://build.laptop.org/F14-arm/os41/ os41] for the new ARM hardware (XO 1.75). Hardware specific bugs especially with the new 1.75 hardware please report at the [http://dev.laptop.org/ OLPC bug tracker]. The current development version is as well available in [http://fedoraproject.org/wiki/Releases/16 Fedora 16] and [[Development_Team/Jhbuild |sugar-jhbuild]] (sugar* master branches).<br />
<br />
==Test builds==<br />
===OLPC 11.3===<br />
* [http://build.laptop.org/11.3.0/os3/ os3] for the i686 architecture (XO 1 and XO 1.5)<br />
* [http://build.laptop.org/F14-arm/os41/ os41] for the new ARM hardware (XO 1.75)<br />
* {{Iframe|See this testing request for [[0.94/Testing|Sugar 0.94]] |http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg22538.html|900|700|1}}<br />
<br />
===Dextrose 3===<br />
* {{Iframe|See this testing request for '''Sugar 0.92.4''' |http://lists.sugarlabs.org/archive/dextrose/2011-August/001349.html|900|700|1}}<br />
===SoaS===<br />
<br />
See [[Sugar on a Stick/Beta]].<br />
<br />
* Testing suggestions for v4:[[Talk:0.90/Testing]]<br />
<br />
* Testing results are in sections below [[Community/Distributions/Fedora-SoaS#Testing Results|Testing Results]] on the page [[Community/Distributions/Fedora-SoaS]]<br />
<br />
==Testing plans==<br />
<br />
<br />
==How to write a good bug report==<br />
You should note the following in the [[BugSquad/Bug Report|bug report]]:<br />
* the version you are using<br />
* steps to reproduce<br />
<br />
In most cases it is of interest to the developers to look at the Sugar logs. Instructions how to get the logs can be seen [[BugSquad/Get Logs]].</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=SoaS/Testing&diff=76090SoaS/Testing2012-03-04T03:26:20Z<p>Skierpage: also a Google Docs spreadsheet</p>
<hr />
<div>* Most test results are in sections underneath [[Community/Distributions/Fedora-SoaS#Testing_Results]]<br />
* Some test results are in the table on [[Sugar on a Stick QA]]<br />
* Some test results in 2009 were reported as subpages of this page, see list below.<br />
* Some test results for SoaS testing, along with other Sugar environments, are in a [https://docs.google.com/spreadsheet/ccc?key=0AntaXnq4oy2_dHpvZHhLeGRQYzc1cDlRZU9Mc1NldGc#gid=0 Google Docs spreadsheet]<br />
<br />
== Subpages of {{FULLPAGENAME}}==<br />
{{Special:PrefixIndex/{{FULLPAGENAME}}/}}<br />
<br />
[[Category:Testing]]</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=SoaS/Testing&diff=76089SoaS/Testing2012-03-04T03:23:02Z<p>Skierpage: create this guidepost page for all the subpages of it.</p>
<hr />
<div>* Most test results are in sections underneath [[Community/Distributions/Fedora-SoaS#Testing_Results]]<br />
* Some test results are in the table on [[Sugar on a Stick QA]]<br />
* Some test results in 2009 were reported as subpages of this page, see list below.<br />
<br />
== Subpages of {{FULLPAGENAME}}==<br />
{{Special:PrefixIndex/{{FULLPAGENAME}}/}}<br />
<br />
[[Category:Testing]]</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Testing/Reports/Sugar_on_a_Stick&diff=76088Testing/Reports/Sugar on a Stick2012-03-04T03:20:28Z<p>Skierpage: /* Testing Results */ link to other test results</p>
<hr />
<div>* '''Use the ← left________________________right → links in the colored bar below<br />
:to connect to another part of this Annotated Guide to Sugar'''<br />
{| width="100%" cellpadding="0" cellspacing="0"<br />
|-<br />
|width=25% align=left bgcolor=#C3D9FF|&larr; '''[[Sugar_Creation_Kit/sck/Introduction_to_Sugar_Interface|Introduction to the Sugar Interface]]'''<br />
|width=50% align=center bgcolor=#C3D9FF|'''[[Sugar_Creation_Kit#All_Prebuilt_VirtualBox_Appliances|VirtualBox Appliances]]'''<br />
|width=25% align=right bgcolor=#C3D9FF| '''[[Sugar_Creation_Kit#Community_Distributions_Complete_Listing|Community Distributions]]''' &rarr;<br />
|}<br />
{| width="100%" cellpadding="0" cellspacing="0"<br />
|-<br />
|width=25% align=left bgcolor=#C3D9FF|&larr; '''[[Sugar_Creation_Kit/sck/How_to_use_Chat-es| Cómo usar Chat ]]'''<br />
|width=50% align=center bgcolor=#C3D9FF|'''[[Sugar_Creation_Kit/sck/Introduction_to_Sugar_Interface-es|Introducción a la interfaz de Azúcar]]<br />
|width=25% align=right bgcolor=#C3D9FF|'''←[[Sugar_Creation_Kit#Introducci.C3.B3n_a_la_interfaz_de_Az.C3.BAcar|Azúcar Creación Kit ]]'''<br />
|}<br />
==[[File:Soas-pineapple.svg|200px|link=Sugar_on_a_Stick/Pineapple]] SoaS v6 Pineapple ==<br />
::Final Version released 11/09/2011<br />
:Direct Download: http://spins.fedoraproject.org/soas/#downloads<br />
<br />
===[[File:VirtualBox.png|30px]][[Sugar_Creation_Kit#v6_Pineapple]] VirtualBox Appliance===<br />
::Just [[Sugar_Creation_Kit/sck/VirtualBox_Import|'''import''']] 2 files from above link ^<br />
* SoaS v6 Pineapple prebuilt VirtualBox Appliance<br />
<br />
===About my computer===<br />
:Build: Sugar on a Stick 6 (Pineapple)<br />
: Fedora Release 16 (Verne)<br />
:Sugar:0.94.1<br />
:V1.05<br />
<br />
[[Community/Distributions/Fedora-SoaS#MacBook_Persistent_SoaS_v5_and_SoaS_v6_EFI_Boot_USB|'''Soas-Booting_EFI_USB for MacBook Pro''']]<br />
:::click this link ^<br />
<br />
===Activities===<br />
'''Key ==> update'''<br />
pippy 43 ==>44<br />
moon 13<br />
log 26 ==>27<br />
visual match 30 ==>34<br />
speak 34 ==>35<br />
typing turtle 28<br />
ruler 13 ==>14<br />
turtle art 120 ==>131<br />
jukebox 23<br />
irc 10<br />
chat 73<br />
maze 14 ==>15<br />
etoys 116<br />
abacus 16 ==>28<br />
write 77<br />
clock 7<br />
record 93<br />
calculate 38<br />
image viewer 19<br />
physics 9<br />
memorize 39<br />
terminal 35<br />
surf 115<br />
* liveinst installs to USB correctly (4 GB USB device: custom / ext4 no swap )<br />
* F16 liveusb-creator (GUI) works fine to make persistent 2GB USB device from .iso<br />
<br />
==[[File:Soas-coconut.svg|200px|link=Sugar_on_a_Stick/Coconut]] SoaS v5 Coconut==<br />
*'''Final release'''10/09/2011<br />
:http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Coconut<br />
<br />
===[[File:VirtualBox.png|30px]][[Sugar_Creation_Kit#v5_Coconut]] VirtualBox Appliance===<br />
::Just [[Sugar_Creation_Kit/sck/VirtualBox_Import|'''import''']] 2 files from above link ^<br />
* SoaS v5 Coconut prebuilt VirtualBox Appliance<br />
<br />
===About my Computer===<br />
:Sugar on a Stick 5 (Coconut)<br />
:Fedora release 15 (Lovelock)<br />
:Sugar: 0.92.4<br />
<br />
===Activities===<br />
*Software List (All favorites) <br />
<br />
Write 76<br />
etoys 116<br />
record 93<br />
chat 71<br />
Turtle Art 114<br />
physics 8<br />
terminal 34<br />
pippy 40<br />
calculate 37<br />
turtle art 114<br />
Speak 29<br />
memorize 36<br />
pippy 41<br />
clock 6<br />
log 24<br />
abacus 19<br />
IRC 10<br />
surf 115<br />
<br />
:Control Panel / Network Application works<br />
<br />
* liveinst installs to USB correctly (4 GB USB device: custom / ext4 no swap )<br />
* F16 liveusb-creator (GUI) works fine to make persistent 2GB USB device from .iso<br />
<br />
===Bugs===<br />
*SoaS v5 Coconut Beta only connects to jabber if using wired connection on boot<br />
::http://bugs.sugarlabs.org/ticket/3100<br />
<br />
==[[File:Usb1.png|75px]] SoaS f17 [[Sugar_Creation_Kit/sck/tools_livecd-iso-to-disk|'''tools_livecd-iso-to-disk install''']] to 2 GB USB-stick with persistence.==<br />
* Transcript of an install<br />
<br />
==[[LiveOS_image|Reference: LiveOS_image]]==<br />
*Details and information on file system used in SoaS<br />
<br />
==MacBook Persistent SoaS v5 and SoaS v6 EFI Boot USB==<br />
:'''Boots directly from the USB device''' NEW<br />
:F15 Downlink: http://download.fedoraproject.org/pub/alt/spins/linux/releases/15/Spins/x86_64/Fedora-15-x86_64-Live-SoaS.iso <br />
:F16 Downlink: http://alt.fedoraproject.org/pub/alt/stage/16.RC4/Spins/x86_64/Fedora-16-x86_64-Live-SoaS.iso <br />
* '''Latest F16-RC4 and RC5 have the updated kernel and boot an EFI USB device directly on a MacBookPro i7 (11/03/2011)'''<br />
:I just successfully made a f16 RC4 EFI Boot USB in VirtualBox on My Macbook Pro i7......nice ; used x86-64 live Desktop and liveinst then installed additions (for USB Access)<br />
::Download of Live-desktop for Virtualbox:http://alt.fedoraproject.org/pub/alt/stage/16.RC4/Live/x86_64/Fedora-16-x86_64-Live-Desktop.iso<br />
::VirtualBox Downloads: http://www.oracle.com/technetwork/server-storage/virtualbox/downloads/index.html including additions<br />
::My Smolt Mac Profile:http://www.smolts.org/client/show/pub_3947102b-ca8d-49f6-9a2d-d1ab91b74448<br />
::Chat works just had chat with mulawa1 on USB on Mac<br />
*Note: EFI USB does NOT boot on MacBook Air. trying to figure out why<br />
*'''need update the video parameters for various Macs'''- https://bugzilla.redhat.com/show_bug.cgi?id=528232#c20 - https://bugzilla.redhat.com/show_bug.cgi?id=528232#c85 <br />
Is that an original MacBook Air? According to this page it does not boot EFI in 64 bits: Bert:<br />
:'''List of Macs that boot in EFI''': http://www.everymac.com/mac-answers/snow-leopard-mac-os-x-faq/mac-os-x-snow-leopard-64-bit-macs-64-bit-efi-boot-in-64-bit-mode.html<br />
:'''f16 Common Bugs''':https://fedoraproject.org/wiki/Common_F16_bugs#Incorrect_partition_type_assigned_to_.2Fboot_partition_on_GPT-labelled_disks<br />
::: Boot Flag: http://blog.christophersmart.com/2009/12/02/fedora-mac-and-efi/ older info to look at<br />
::Possible Fix: tested with grub2-efi, and then I can boot Air with xdriver=vesa nomodeset<br />
* Fix for EFI in v6? :::http://lists.fedoraproject.org/pipermail/test/2011-October/104146.html<br />
:'''Kernel upgrade''' to fix this: http://kojipkgs.fedoraproject.org/packages/kernel/3.1.0/7.fc16/x86_64/kernel-3.1.0-7.fc16.x86_64.rpm is in RC4<br />
:::https://bugzilla.redhat.com/show_bug.cgi?id=748516<br />
::Look at Further adventures in EFI booting: http://mjg59.dreamwidth.org/4957.html<br />
:WORKS WITH SoaS v5 Coconut and SoaS v6 Pineapple<br />
:does not work with wired cat5 connection '''no internet connections available'''<br />
:[[File:EFI_Boot.JPG|150px]] <===click on image to enlarge<br />
:To Boot Hold "Option" Key when starting Mac. Hold key until EFI USB Icon Appears then select it right arrow ===> (EFI)<br />
:KEY: (x)= device name<br />
: Use the {{Code|sudo blkid}} command in a terminal to see the USB and other device names for discs attached to the system. <!-- mount has a lot of extraneous info and the device may not automount and so not be present. --><br />
::ie: /dev/sdb; /dev/sdc; /dev/sdd.... '''IMPORTANT very dangerous if you use the wrong one'''<br />
====Build EFI USB Boot Stick====<br />
*From booted f16-x86 64 hard disk install<br />
Run "yum install livecd-tools" so it installs all the required<br />
dependencies and then use livecd-iso-to-disk<br />
<br />
Boots:MacBook-Proi7<br />
-EFI-Boot-USB<br />
hold option key on power up<br />
select --> EFI Boot <br />
* Has Persistence<br />
*2 GB Firefly USB<br />
*>'''formatted in F16-64 disk utility VERY IMPORTANT''' <<br />
fat /dev/sdb<br />
fat /dev/sdb1<br />
* '''(Built in F16-64 gnome3-shell 3.2.1 on Acer Aspire One N450)'''<br />
*Download link: http://alt.fedoraproject.org/pub/alt/stage/16.RC4/Spins/x86_64/Fedora-16-x86_64-Live-SoaS.iso<br />
====root terminal command line:====<br />
<br />
'''sudo livecd-iso-to-disk --format --efi --overlay-size-mb 300 --home-size-mb 175 --delete-home --unencrypted-home Fedora-16-x86_64-Live-SoaS.iso /dev/sd(x)''' (x)=device name<br />
Verifying image...<br />
/home/(user)/Downloads/Fedora-16-x86_64-Live-SoaS.iso: <br />
Fragment sums: <br />
Fragment count: 20<br />
Press [Esc] to abort check.<br />
Checking: 100.0%<br />
The media check is complete, the result is: PASS.<br />
It is OK to use this media.<br />
WARNING: THIS WILL DESTROY ANY DATA ON /dev/sdb!!!<br />
Press Enter to continue or ctrl-c to abort<br />
wipefs: WARNING: /dev/sdb: appears to contain 'dos' partition table<br />
Waiting for devices to settle...<br />
mkdosfs 3.0.11 (24 Dec 2010)<br />
Copying live image to target device.<br />
squashfs.img<br />
417943552 100% 7.55MB/s 0:00:52 (xfer#1, to-check=0/1)<br />
sent 417994645 bytes received 31 bytes 7812984.60 bytes/sec<br />
total size is 417943552 speedup is 1.00<br />
osmin.img<br />
8192 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1)<br />
sent 8265 bytes received 31 bytes 16592.00 bytes/sec<br />
total size is 8192 speedup is 0.99<br />
Updating boot config file<br />
Initializing persistent overlay file<br />
300+0 records in<br />
300+0 records out<br />
314572800 bytes (315 MB) copied, 32.5186 s, 9.7 MB/s<br />
Initializing persistent /home<br />
175+0 records in<br />
175+0 records out<br />
183500800 bytes (184 MB) copied, 23.6238 s, 7.8 MB/s<br />
Formatting unencrypted /home<br />
mke2fs 1.41.14 (22-Dec-2010)<br />
Filesystem label=<br />
OS type: Linux<br />
Block size=1024 (log=0)<br />
Fragment size=1024 (log=0)<br />
Stride=0 blocks, Stripe width=0 blocks<br />
44880 inodes, 179200 blocks<br />
8960 blocks (5.00%) reserved for the super user<br />
First data block=1<br />
Maximum filesystem blocks=67371008<br />
22 block groups<br />
8192 blocks per group, 8192 fragments per group<br />
2040 inodes per group<br />
Superblock backups stored on blocks: <br />
8193, 24577, 40961, 57345, 73729<br />
Writing inode tables: done <br />
Creating journal (4096 blocks): done<br />
Writing superblocks and filesystem accounting information: done<br />
This filesystem will be automatically checked every 35 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override.<br />
tune2fs 1.41.14 (22-Dec-2010)<br />
Setting maximal mount count to -1<br />
Setting interval between checks to 0 seconds<br />
Installing boot loader<br />
Target device is now set up with a Live image!<br />
<br />
====Control-panel====<br />
Sugar on a Stick 6 (Pineapple)<br />
Fedora release 16 (Verne)<br />
0.94.1<br />
Firmware: MBP81.88Z.0047.B1E.1109091244<br />
Wireless Firmware: N/A<br />
<br />
====activities====<br />
> = Updates<br />
<br />
pippy 43<br />
moon 13<br />
log 26<br />
visual match 30<br />
speak 34<br />
typing turtle 28<br />
ruler 13 > 28<br />
turtle art 120 > 122<br />
jukebox 23<br />
irc 10<br />
chat 73<br />
maze 14<br />
etoys 116<br />
abacus 26 > 28<br />
write 77<br />
clock 7<br />
record 93<br />
calculate 38<br />
image viewer 19<br />
physics 9<br />
memorize 39<br />
terminal 35<br />
surf 115<br />
<br />
'<br />
<br />
==[[Talk:Community/Distributions/Fedora-SoaS#dd_img_Boot_Tests_in_MacBook_Pro_i7|Boot tests of dd img USB's in a MacBook i7]]==<br />
;READ THIS FIRST^<br />
:Synopsis: Only EFI .img Boots Mac.<br />
<br />
<br />
==='''How to Write your own .img file'''===<br />
Run "yum install livecd-tools" so it installs all the required<br />
dependencies and then use livecd-iso-to-disk<br />
*use Disk Utility in f16 to format the USB as Master boot Record and /dev/sd(x)1 as FAT first.<br />
*Command Line to use in root terminal:<br />
sudo livecd-iso-to-disk --reset-mbr --format --overlay-size-mb 300 --home-size-mb 175 --delete-home --unencrypted-home Fedora-16-release-i686-Live-SoaS.iso /dev/sd(x)<br />
<br />
===make .img file from inserted USB===<br />
:'''Do this before you boot the USB.'''<br />
:( This will avoid network collisions when running multiple copies on the network.)<br />
:the unique ssh keys are generated on first boot of a SoaS USB<br />
dd if=/dev/sd(x) of=Soas-v6-Pineapple.img<br />
<br />
==[[File:Usb1.png]] dd writable 2GB USB Soas-v5-Coconut-USB .img==<br />
:'''Download:''' http://download.sugarlabs.org/images/Soas_Coconuts.img<br />
<br />
:built with liveusb-creator in F16 with persistence file from<br />
::http://kojipkgs.fedoraproject.org/images/livecd/163/163/Fedora-15-x86_64-Live-SoaS.iso<br />
:USB 2 GB Firefly<br />
:reduced to 1.66 GiB with gparted*<br />
* Never started so has original Name___; Color___==> startup<br />
<br />
===Write to a 2 GB (1.95 GiB) USB device===<br />
dd if=Soas_Coconuts.img of=/dev/sd(x) bs=2M<br />
956+0 records in<br />
956+0 records out<br />
2004877312 bytes (2.0 GB) copied, 93.2584 s, 21.5 MB/s<br />
<br />
*NOTE dd may complain that it is unable to write to your USB device "No space left on device."<br />
:Disregard as it will work (this is due to gparted resizing)<br />
<br />
===Write to a Smaller 2 GB (1.87GiB) USB device===<br />
dd if=Soas_Coconuts.img of=/dev/sd(x) bs=2M<br />
dd: writing `/dev/sdg': No space left on device<br />
956+0 records in<br />
955+0 records out<br />
2003828736 bytes (2.0 GB) copied, 316.111 s, 6.3 MB/s<br />
<br />
==[[File:Usb1.png]] dd writable 2GB USB Soas-v6-Pineapple-USB .img==<br />
*Download: http://people.sugarlabs.org/Tgillard/soas-v6-i686.img<br />
* Never started so has original Name___; Color___==> startup<br />
==[[File:Usb1.png]] dd writable 1 GB EFI Boot (MAC) USB Soas-v6-Pineapple x86-USB .img ==<br />
:'''Download:''' http://people.sugarlabs.org/Tgillard/SoaS-15-1-EFI.img<br />
*note file is mis-named<br />
: persistent; fits in a 1 GB USB<br />
: How to build: [[Community/Distributions/Fedora-SoaS#MacBook_Persistent_SoaS_v5_and_SoaS_v6_EFI_Boot_USB]]<br />
*'''NOTE DO NOT USE THIS .img file with image-writer-mac'''<br />
* For Booting a Mac ONLY do not use on a PC<br />
:This is a dd created .img from a working USB<br />
===About my computer===<br />
Sugar on a Stick 6 (Pineapple)<br />
Fedora release 16 (Verne)<br />
sugar 0.94.1<br />
<br />
===Write to a 1 GB USB device===<br />
sudo su<br />
Password<br />
dd if=SoaS-15-1-EFI.img of=/dev/sd(x) bs=2M<br />
489+1 records in<br />
489+1 records out<br />
1026555904 bytes (1.0 GB) copied, 216.577 s, 4.7 MB/s<br />
*Write your own:<br />
sudo livecd-iso-to-disk --format --efi --overlay-size-mb 300 --home-size-mb 175 --delete-home --unencrypted-home Fedora-16-x86_64-Live-SoaS.iso /dev/sd(x)<br />
<br />
==[[File:OLPCXO.png]][[File:Soas-pineapple.svg|200px|link=Sugar_on_a_Stick/Pineapple]] F16 SoaS Pineapple USB boot for XO-1==<br />
:(graphical) liveusb-creator in F16 gnome3-shell- with Fedora-16-i686-Live-SoaS.iso selected<br />
:boots XO-1 with a Live USB image<br />
:Formatted the USB device in F16 gnome3-shell disk utility as fat with LIVE label. Installation said it was Setting up OLPC boot file at end.<br />
:USB is very slow but it boots from the USB device<br />
:(USB in right slot when powered on)<br />
:connects to WEP Access Point and Updates correctly<br />
*'''This USB device image will not boot XO-1.5'''<br />
<br />
===liveusb-creator record===<br />
-------------------------------------<br />
Fedora-16-i686-Live-SoaS.iso selected<br />
Warning: The Master Boot Record on your device does not match your system's syslinux MBR.<br />
If you have trouble booting this stick, try running the liveusb-creator with the --reset-mbr option.<br />
Verifying filesystem...<br />
Verifying ISO MD5 checksum<br />
ISO MD5 checksum passed<br />
Extracting live image to USB device...<br />
Wrote to device at 6 MB/sec<br />
Creating 1687MB persistent overlay<br />
Setting up OLPC boot file...<br />
Installing bootloader...<br />
Marked /dev/sdb1 as bootable<br />
Unmounting /media/LIVE<br />
Complete! (0:07:23)<br />
<br />
==[[File:VirtualBox.png|50px]] SoaS v6 Desktop EFI USB device Builder prebuilt VirtualBox Appliance==<br />
<br />
:http://download.sugarlabs.org/images/VirtualBox/f16-live-RC4-Desktop-sugaruser.ovf<br />
:http://download.sugarlabs.org/images/VirtualBox/f16-live-RC4-Desktop-sugaruser-disk1.vmdk<br />
:builds EFI 2GB USB devices that boot MacBook Pro i7 (8.1 Intel)<br />
::Just import 2 files from above link ^<br />
:root=sugarroot user=sugar pswd=sugaruser<br />
: Allows building of EFI Boot USB devices (self contained)<br />
* F16-Desktop x86-64 Virtual Machine<br />
:requires a x86_64 computer <br />
:IMPORTANT: There is NO WIRELESS (wired works) or AUDIO available when booted from this EFI Boot USB<br />
<br />
# '''Contains RC4 F15 and F16 x86_64-Live-SoaS.iso files in the Download directory'''<br />
# Script in Desktop to run in terminal<br />
*'''How to use the VM to create an EFI boot USB'''<br />
Start Virtual Appliance<br />
start Terminal (Applications/system tools/terminal)<br />
In terminal: cd Downloads<br />
Insert a 2 GB or larger USB<br />
type "mount" to get USB device name ie: /dev/sdb; /dev/sdc/; etc Be certain of this to get this wrong is dangerous. <br />
minimize<br />
start Applications/Accessories/gedit<br />
In Gedit Open /Desktop/livecd-iso-to-disk.txt<br />
edit command line to show correct USB device name.<br />
copy corrected command line<br />
Paste into terminal <br />
:builds EFI 2GB USB devices that boot MacBook Pro i7 (8.1 Intel)<br />
:THIS IS A DANGEROUS OPERATION. BE CERTAIN THE USB DEVICE NAME IS CORRECT<br />
root=sugarroot user=sugar pswd=sugaruser<br />
:'''Please Test''' all suggestions on comments are welcome Please edit wiki.<br />
<br />
==F16 SoaS Pineapple USB boot image for XO-1==<br />
:(graphical) liveusb-creator in f16 gnome3-shell- with Fedora-16-i686-Live-SoaS.iso selected<br />
:boots XO-1 as a live USB device<br />
:I formatted the USB device disk first in F16 gnome3-shell disk utility as Master Boot Record and fat partition with LIVE label<br />
:Then ran liveusb-creator (graphical)<br />
:USB is quite slow but it does boot from the USB device<br />
:(USB in right bottom slot when powered on)<br />
:connects to WEP Access Point and Updates correctly<br />
<br />
===liveusb-creator record===<br />
-------------------------------------<br />
Fedora-16-i686-Live-SoaS.iso selected<br />
Warning: The Master Boot Record on your device does not match your system's syslinux MBR.<br />
If you have trouble booting this stick, try running the liveusb-creator with the --reset-mbr option.<br />
Verifying filesystem...<br />
Verifying ISO MD5 checksum<br />
ISO MD5 checksum passed<br />
Extracting live image to USB device...<br />
Wrote to device at 6 MB/sec<br />
Creating 1687MB persistent overlay<br />
Setting up OLPC boot file...<br />
Installing bootloader...<br />
Marked /dev/sdb1 as bootable<br />
Unmounting /media/LIVE<br />
Complete! (0:07:23)<br />
===About my computer===<br />
:Build: Sugar on a Stick 6 (Pineapple)<br />
: Fedora Release 16 (Verne)<br />
:Sugar:0.94.2<br />
:Firmware:Q2E46<br />
:Wireless firmware:9.34.3 p23<br />
<br />
*(Connects via jabber.sugarlabs.org to a XO-1.5 running os874 sugar 0.92.2)<br />
<br />
='''Testing Results'''=<br />
*Sections below here report on testing of recent Sugar on a Stick-(SoaS) and Fedora Nightly Composes and Remixes.<br />
*See also test results table in [[Sugar on a Stick QA]] , and [[Special:PrefixIndex/SoaS/Testing/|subpages]] of [[SoaS/Testing]].<br />
<br />
=Fedora SoaS Spin=<br />
*http://alt.fedoraproject.org/pub/alt/spins/linux/releases/16/<br />
*http://fedoraproject.org/get-fedora<br />
*https://spins.fedoraproject.org/soas/#downloads<br />
*Latest Nightly Spins: http://koji.fedoraproject.org/koji/tasks?method=createLiveCD&owner=kevin&state=all&view=tree&order=-id<br />
:'''Current Download Page'''<br />
<br />
=Nightly live Composes=<br />
*AutoQA (rats install):http://autoqa-stg.fedoraproject.org/resultsdb/frontend/search?type=Testcase&terms=rats_install<br />
*http://alt.fedoraproject.org/pub/alt/nightly-composes/<br />
::Note all nightly compose are ephemeral builds for testing and are erased when the next build happens. <br />
<br />
*http://koji.fedoraproject.org/koji/tasks?method=createLiveCD&owner=kevin&state=all&view=tree&order=-id<br />
::Current status of All createLiveCD Tasks in Koji<br />
::see latest builds and their status<br />
::Retrieve recent older Nightly Composes<br />
*All Composes: http://koji.fedoraproject.org/koji/tasks?state=all&view=flat&method=createLiveCD&order=-id<br />
<br />
===Fedora-17-Nightly-20120226.09-i686-Live-soas===<br />
*boots correctly<br />
*Wireless AP cannot remain connected<br />
:https://bugzilla.redhat.com/show_bug.cgi?id=795880<br />
:Related? http://bugs.sugarlabs.org/ticket/3298 <br />
*Wireless Ad-Hoc AP's visible and connect correctly<br />
*No other changes from previous nightly SoaS live CD<br />
<br />
===Fedora-17-Alpha-RC4-x86_64-Live-Desktop install to VirtualBox===<br />
*VirtualBox 4.1.6 r74714 for OSX<br />
MacBook Pro i7<br />
1256 MB memory<br />
12 MB Video Memory<br />
Enable IO APIC; Enable VT-x/AMD-V; Enable Nested Paging<br />
8 GB expanding HD<br />
*'''uses llvm pipe software acceleration'''<br />
*GNOME 3.3.5 (Not fallback)<br />
*liveinst<br />
:use whole disk [lvm]<br />
*firstboot<br />
*GNOME 3.3.5<br />
*Update<br />
*reboot<br />
*Add/Remove Programs<br />
:sugar- check all options<br />
*log out/login to sugar<br />
*works fine<br />
*sees avatars on jabber<br />
Fedora release 17 (Beefy Miracle)<br />
Sugar 0.95.4<br />
VirtualBox<br />
=====VirtualBox Test of Memory Required=====<br />
*MacBook Pro i7<br />
#1256 MB boots - installs<br />
# 768 MB (VB Default) boots with "Oh-No" then, after long wait, gnome3 shell - installs<br />
# 512 MB (starts display manager) boots with "Oh-No" "Gnome 3 Failed to load" (close) long wait enters Gnome fallback mode- (much CD activity).<br />
: - install does not start.<br />
:Message that 769 MB memory is required. (I have been told that this is hard wired in anaconda)<br />
<br />
===Fedora-17-Alpha-RC3-i686-Live-Desktop.iso===<br />
====Testing-Live CD====<br />
has circular greyed graphical boot artwork<br />
after plymouth daemon start in booting eventually switches to f in circular artwork<br />
Gnome 3.3.5<br />
/*\ wireless ABRT warning: problem in network manager:<br />
"gnome-0.9.3-0.2 git 2012020215.f17 detected"<br />
Wireless WEP cuts in and out.<br />
====Install to HD====<br />
use whole disk [lvm]<br />
f17 artwork for anaconda<br />
has circular greyed graphical boot artwork<br />
after plymouth daemon start in booting eventually switches to f in circular artwork<br />
Firstboot works OK allows [X] NTP selection<br />
Gnome 3.3.5<br />
Intel IGD<br />
Add/Remove:<br />
sugar-emulator<br />
Constructionist learning platform<br />
Logout triggers a [890.44115] endless scroll.<br />
Power off and reboot<br />
Logs in properly via gdm to gnome and sugar.<br />
*Wireless AP and Ad Hoc not seen in sugar (f1) Network Neighborhood<br />
* 55 software updates<br />
logout/login<br />
*sugar<br />
Ad-Hoc AP's show in (f1) Network Neighborhood<br />
NO Wireless AP's<br />
<br />
===Fedora-17-Alpha-i686-Live-RC2-SoaS===<br />
*Last Alpha build of SoaS<br />
http://dl.fedoraproject.org/pub/alt/stage/17-Alpha.RC2/Live/i686/Fedora-17-Alpha-i686-Live-SoaS.iso<br />
====liveusb-creator====<br />
*Built in LDXE/MyFiles 2 partition USB with ''tools_livecd-iso-to-disk.sh''to /dev/sda1<br />
:: LDXE 3GB/MyFiles 5GB<br />
:Fedora-17-Alpha-i686-Live-RC2-SoaS.iso loaded in MyFiles <br />
:2 GB Firefly USB fat 16 label LIVE boot flag set<br />
:1047 MB overlay (limited by 2 GB USB-stick and fat 16)<br />
::dd fails on larger size<br />
====Boot USB-stick====<br />
*boots to name and color<br />
*Sees Jabber<br />
*No wireless AP's or Ad-Hoc AP's<br />
====About my Computer====<br />
Sugar on a Stick 7<br />
Fedora release 17 (Beefy Miracle)<br />
0.95.4<br />
====Update====<br />
yum install sugar* (26 pkg install 3 pkg upgrade 24M) TEST on persistent USB-stick <br />
Adds many activities but not wireless AP's<br />
====Activities that start====<br />
*Activities that "do not start" not listed<br />
* ==> cp/software update<br />
chat 73<br />
maze 15<br />
moon 13<br />
ruler 17<br />
portfolio 20<br />
write 77<br />
typing turtle 29<br />
jukebox 23<br />
turtle art 134<br />
irc 10<br />
pippy 44<br />
image viewer 19<br />
speak 35<br />
log 26<br />
calculate 38<br />
memorize 39<br />
terminal 35<br />
clock 7<br />
visual match 34<br />
physics 9<br />
browse 131<br />
=====added======<br />
measure 36<br />
distance 25<br />
infoslicer 11<br />
pukllanapac 8<br />
==AfterCP/software update==<br />
TamTamMini 62<br />
TamTamEdit 62<br />
TamTamJam 62<br />
TamTamSynthLa 62<br />
calendario 5<br />
flipsticks 11<br />
log 27<br />
speak 36<br />
pippy 46<br />
<br />
===Fedora-17-Nightly-20120218.10-i686-Live-soas===<br />
*No wireless AP<br />
*No major changes from earlier nightly<br />
<br />
===Fedora-17-Nightly-20120217.09-i686-Live-desktop===<br />
*http://koji.fedoraproject.org/koji/getfile?taskID=3798907&name=Fedora-17-Nightly-20120217.09-i686-Live-desktop.iso<br />
*boots to fireworks background<br />
*Gnome 3.3.5<br />
*Firefox 10.0.1-<br />
::google look-up works (so it is ON LINE)<br />
===='''Wireless AP-test'''====<br />
:requested by adamw on #fedora-bugzappers<br />
:shows wireless [on]/wireless on<br />
::Lists 3 wireless AP's<br />
*Click on wireless AP [on] list: NO POP-UP for settings occurs<br />
*System Settings/Network:<br />
::Wireless [ON] /Wireless Disconnected<br />
::3 wireless AP's show in [Network Name] dropdown click on it it will not hold it ins window [Configure] is greyed out<br />
<br />
===Fedora-17-Alpha-RC1-i386-netinst===<br />
*http://dl.fedoraproject.org/pub/alt/stage/17-Alpha.RC1/Fedora/i386/iso/Fedora-17-Alpha-i386-netinst.iso<br />
*set up [configure network] for wirelss-enter wep password<br />
*Use whole disk [LVM] selected <br />
*f17 artwork and background<br />
:external USB 350 GB Disk)<br />
*Sugar-Desktop Environment ONLY - (Gnome deselected)<br />
*Reboot<br />
*Firstboot:<br />
:'''synch network time greyed out''<br />
*gdm login works-f17 background<br />
*No wireless AP or Ad-Hoc<br />
*Jabber works<br />
*'''yum install works'''<br />
====About my Computer====<br />
sugar on a stick 7<br />
Fedora release 17 (Beefy Miracle)<br />
0.95.4<br />
V1.05<br />
====Activities====<br />
[[File:Mesh_key_f1_small.png |15px]]= Share offered<br />
Key= @ Not a Favorite<br />
==> Update<br />
@Playgo 5 '''Failed to start (Stop)'''<br />
Browse 131<br />
Chat 73 [[File:Mesh_key_f1_small.png |15px]]<br />
Maze 15 [[File:Mesh_key_f1_small.png |15px]] '''sharing causes crash RuntimeError: get buddy is not tread safe and will crash your activity (hard) Use lookup_buddy'''<br />
Moon 13<br />
@Abacus 31 '''Failed to start (Stop)'''<br />
Ruler 17 <br />
@Portfolio 20 <br />
Write 77 [[File:Mesh_key_f1_small.png |15px]]<br />
Etoys 116 '''DBusError: Process /usr/share/sugar-presence-service exited with a status 1'''<br />
@Finance 3 '''Failed to start (Stop)'''<br />
@Typing Turtle 29 <br />
@Jukebox 23 <br />
Turtle Art 134 [[File:Mesh_key_f1_small.png |15px]]<br />
@IRC 10 <br />
@Analyze 8 '''Failed to start (Stop)'''<br />
Pippy 44 [[File:Mesh_key_f1_small.png |15px]] '''ImportError: cannot import name physics'''<br />
implode 9 '''Failed to start (Stop)'''<br />
@puklianapac 8<br />
@Image Viewer 19 [[File:Mesh_key_f1_small.png |15px]]<br />
Speak 35 [[File:Mesh_key_f1_small.png |15px]]<br />
Log 26 ==> 27<br />
Calculate 38 [[File:Mesh_key_f1_small.png |15px]]<br />
Memorize 39 [[File:Mesh_key_f1_small.png |15px]]<br />
@Terminal 35<br />
Record 93 '''Failed to start (Stop) sugar3,bundle.MalformedBundleException: Actiity Bundle /usr/share/sugar/activities/Record.activity must specify either class or exec'''<br />
@Clock 7 <br />
@Visual Match 34<br />
flipsticks 2 ==>11<br />
@physics 9<br />
Paint 32 '''Failed to start (Stop)'''<br />
infoslicer 11 looks up OLPC from web<br />
<br />
*Presenceservice log : IOError: [Errno2] No such file or directory:''home/robert/.sugar/default/buddy-icon.jpg'<br />
<br />
===Fedora-17-Nightly-20120214.09-i686-Live-kde===<br />
====Normal boot of CD====<br />
*Error Message:<br />
(^) Logging in liveuser...<br />
Warning: Cannot open consolekit session: Unable to open session: Unable to get information about the calling process<br />
*'''Fireworks Background - NEW Artwork''' while loading. Then fades to black background<br />
*Logout /login liveuser<br />
: get Fireworks background again while loading Then fades to black background<br />
<br />
====Boot with enforcing=0 ====<br />
*Error Message:<br />
(^) Logging in liveuser...<br />
Warning: Cannot open consolekit session: Unable to open session: Unable to get information about the calling process<br />
*'''Fireworks Background - NEW Artwork''' while loading. Then fades to black background<br />
*NO CHANGE<br />
*no repomd file when invoking yum install<br />
<br />
===Fedora-17-Nightly-20120213.15-i686-Live-soas===<br />
:http://koji.fedoraproject.org/koji/getfile?taskID=3787937&name=Fedora-17-Nightly-20120213.15-i686-Live-soas.iso<br />
* Normal Boot : boots to Name and color screens<br />
*'''enforcing=0 Not Required for boot''' NEW<br />
*NO Changes in Activities from previous build<br />
*Yum does not work "No repomd file" https://bugzilla.redhat.com/show_bug.cgi?id=790530<br />
*'''CP/Modem Configuration does not open'''<br />
====liveinst====<br />
fails unless use<br />
Custom:<br />
Delete partition - this is 8GB USB Stick<br />
Create: <br />
bios boot 2<br />
/ext4 7000 <br />
swap 500<br />
*USB install boots and completes firstboot/gdm login correctly <br />
:enforcing=0 Not Required<br />
<br />
===Fedora-17-Nightly-20120210.09-i686-Live-soas===<br />
Burn to CD<br />
ACER ASPIRE ONE N450 + external USB DVD/CD<br />
* Normal Boot :enforcing=0 : boots to Name and color screens<br />
====About my Computer====<br />
sugar on a stick 7<br />
Fedora release 17 (Beefy Miracle)<br />
0.95.4<br />
V1.05<br />
====Activities====<br />
[[File:Mesh_key_f1_small.png |15px]]= Share offered<br />
Key= @ Not a Favorite<br />
==> Update<br />
@ Browse 131<br />
Chat 73 [[File:Mesh_key_f1_small.png |15px]]<br />
Maze 15 [[File:Mesh_key_f1_small.png |15px]] '''causes crash RuntimeError: get buddy is not tread safe and will crash your activity (hard) Use lookup_buddy'''<br />
Moon 13<br />
Abacus 31 '''Failed to start (Stop)'''<br />
Ruler 17 <br />
@Portfolio 20 <br />
Write 77 [[File:Mesh_key_f1_small.png |15px]]<br />
Etoys 116 '''DBusError: Process /usr/share/sugar-presence-service exited with a status 1'''<br />
Typing Turtle 29 <br />
Jukebox 23 <br />
Turtle Art 134 [[File:Mesh_key_f1_small.png |15px]]<br />
IRC 10 <br />
Pippy 44 [[File:Mesh_key_f1_small.png |15px]] '''ImportError: cannot import name physics'''<br />
Image Viewer 19 [[File:Mesh_key_f1_small.png |15px]]<br />
Speak 35 [[File:Mesh_key_f1_small.png |15px]]<br />
Log 26 ==> 27<br />
Calculate 38 [[File:Mesh_key_f1_small.png |15px]]<br />
Memorize 39 [[File:Mesh_key_f1_small.png |15px]]<br />
Terminal 35<br />
Record 93 '''Failed to start (Stop) sugar3,bundle.MalformedBundleException: Actiity Bundle /usr/share/sugar/activities/Record.activity must specify either class or exec'''<br />
Clock 7 <br />
Visual Match 34<br />
Physics 9<br />
Read 94 <br />
<br />
====Network====<br />
*Wired connection works with Browse<br />
:: Wired OK<br />
:: No Wireless or Ad-Hoc AP's<br />
*Yum does not work "No repomd file"<br />
<br />
===Fedora-17-Nightly-20120210.09-i686-Live-desktop===<br />
Burn to CD<br />
ACER ASPIRE ONE N450 + external USB DVD/CD<br />
* Basic graphics Boot<br />
:Live system user gdm<br />
:Does not log in returns to login<br />
* Normal Boot<br />
:enforcing=0 <br />
: Gnome 3.3.5 - (not fallback)<br />
:Network<br />
:: Wired OK<br />
:: Wireless (failed)<br />
*Yum does not work "No repomd file"<br />
*Synaptic cannot access sources<br />
*Firefox 10.0.1 starts works on internet<br />
*Install to Hard Drive - (16 GB USB-Stick)<br />
:Basic/ Use All Space /LVM<br />
*Unhandled Exeption-fails<br />
<br />
===Fedora-17-Alpha-TC2-i686-Live-KDE===<br />
http://dl.fedoraproject.org/pub/alt/stage/17-Alpha.TC2/Live/i686/Fedora-17-Alpha-TC2-i686-Live-KDE.iso<br />
Burn to CD<br />
ACER ASPIRE ONE N450 + external USB DVD/CD<br />
* Normal Boot<br />
enforcing=0 <br />
*'''>logging in liveuser...Warning: Cannot open consolekit session: Unable to open session: Unable to get information about the calling process.''' (OK)<br />
*Loads KDE Desktop<br />
====Network====<br />
:: Wired OK - Web browser works<br />
:: Wireless (failed) Error- Network Error adding connection: No session found for uid 1000 (No session found for uid 1000)<br />
*Xterm: Yum does not work "No repomd file"<br />
*Software Management / Updates /check for updates<br />
*Firewall/Disable yes<br />
*Liveusb-creator- :Already loaded<br />
====Install to HD====<br />
16 GB USB-stick<br />
Use all disk - LVM checked<br />
Copying live image to hard drive.<br />
'''f16 artwork'''<br />
Congratulations<br />
===Boot USB-stick===<br />
enforcing=0<br />
*Firstboot<br />
.Warning: Cannot open consolekit session: Unable to open session: Unable to get information about the calling process.''' (OK)<br />
*Loads KDE Desktop<br />
====Network====<br />
:: Wired OK - Web browser works<br />
:: Wireless (failed) Error- Network Error adding connection: No session found for uid 1000 (No session found for uid 1000)<br />
*Software Management / Updates /check for updates<br />
*Xterm: Yum does not work "No repomd file"<br />
===Fedora-17-Alpha-TC2-i686-Live-Desktop===<br />
Burn to CD<br />
ACER ASPIRE ONE N450 external USB DVD/CD<br />
<br />
*Boot fails at "Started Display Manager" (loops 5 times and halts)<br />
*add enforcing=0 (loops 5 times goes to text login)<br />
:root #<br />
:startx boots to new background screen (fireworks)<br />
<br />
*System Settings<br />
: Gnome 3.3.5 - (working corectly not fallback)<br />
:Network<br />
:: Wired OK<br />
:: Wireless (failed)<br />
:User Accounts<br />
::Add User-(standard) add password<br />
*Log out<br />
:exit<br />
:Text Console<br />
*Login to user/password<br />
:startx<br />
:: '''Gnome3 Failed to load: Fallback'''<br />
<br />
*Firefox 10.0.1 starts<br />
<br />
*Install to Hard Drive - (16 GB USB-Stick)<br />
:Basic/ Use All Space / Use LVM<br />
:TZ/root password<br />
:formatting '''f16 Artwork'''<br />
:Installing bootloader<br />
*Reboot<br />
<br />
*Boot USB<br />
*Firstboot<br />
:Syncronize date and time over the network (greyed out)<br />
:Smolt send<br />
*Login Fails cycles back<br />
*Same for root<br />
Anaconda FAILS<br />
====Fix for USER Login====<br />
I just installed from the Live CD [1] to a 16 GB USB stick and got it to boot and login.<br />
*Problem;<br />
firstboot is not writing the passwords for the user that is entered in it. This causes the install to be useless as it cannot be logged in to.<br />
*Fix:<br />
I added selinux=0 s (run level 1) to the boot line of the USB<br />
It booted to console prompt<br />
root<br />
(no password) #<br />
Entered commands:<br />
selinux=0<br />
useradd xxxxx<br />
passwd xxxxxxx<br />
login<br />
*logged in to gdm sucessfully.<br />
GNOME 3.3.5 came up<br />
the useradd user is admin.<br />
*This seems to bypass the firstboot errors.<br />
<br />
[1] http://dl.fedoraproject.org/pub/alt/stage/17-Alpha.TC2/Live/i686/Fedora-17-Alpha-TC2-i686-Live-Desktop.iso<br />
<br />
===Fedora-17-Alpha-TC2-i686-Live-SoaS===<br />
http://dl.fedoraproject.org/pub/alt/stage/17-Alpha.TC2/Live/i686/Fedora-17-Alpha-TC2-i686-Live-SoaS.iso --[[User:Satellit|Satellit]] 21:13, 9 February 2012 (EST)<br />
*Boots<br />
*'''No Wireless AP's or Ad-Hoc network Points'''<br />
* Speech feature in frame works<br />
====About my Computer====<br />
Sugar on a Stick 7<br />
Fedora releast 17 (Beefy Miracle)<br />
Sugar 0.95.4<br />
Firmware V1.05<br />
====Activities====<br />
[[File:Mesh_key_f1_small.png |15px]]= Share offered<br />
Key= @ Not a Favorite<br />
==> Update<br />
@ Browse 131<br />
Chat 73 [[File:Mesh_key_f1_small.png |15px]]<br />
Maze 15 [[File:Mesh_key_f1_small.png |15px]] '''causes crash RuntimeError: get buddy is not tread safe and will crash your activity (hard) Use lookup_buddy'''<br />
Moon 13<br />
Abacus 31 '''Failed to start (Stop)'''<br />
Ruler 17 <br />
@Portfolio 20 <br />
Write 77 [[File:Mesh_key_f1_small.png |15px]]<br />
Etoys 116 '''DBusError: Process /usr/share/sugar-presence-service exited with a status 1'''<br />
Typing Turtle 29 <br />
Jukebox 23 <br />
Turtle Art 134 [[File:Mesh_key_f1_small.png |15px]]<br />
IRC 10 <br />
Pippy 44 [[File:Mesh_key_f1_small.png |15px]] '''ImportError: cannot import name physics'''<br />
Image Viewer 19 [[File:Mesh_key_f1_small.png |15px]]<br />
Speak 35 [[File:Mesh_key_f1_small.png |15px]]<br />
Log 26 ==> 27<br />
Calculate 38 [[File:Mesh_key_f1_small.png |15px]]<br />
Memorize 39 [[File:Mesh_key_f1_small.png |15px]]<br />
Terminal 35<br />
Record 93 '''Failed to start (Stop) sugar3,bundle.MalformedBundleException: Actiity Bundle /usr/share/sugar/activities/Record.activity must specify either class or exec'''<br />
Clock 7 <br />
Visual Match 34 [[File:Mesh_key_f1_small.png |15px]]<br />
Physics 9 <br />
@Read 94 '''Failed to start (Stop) AttributeError; 'module' object has no attributes 'EditToolbar' '''<br />
<br />
====liveinst to USB-stick====<br />
*Anaconda 17.7-1.fc17.i686<br />
*16 GB USB Stick fat32<br />
[Configure Network] greyed out<br />
*Custom (this reformats the USB-stick)<br />
Bios boot 2<br />
/ ext4 15000<br />
swap 317<br />
*Congratulations-(reboot)<br />
*Reboot USB-stick with '''enforcing=0'''<br />
* Can't open font TRUE<br />
*firstboot<br />
[ ]Synchronize date and time over the network '''greyed out'''<br />
'''NOTE: if boot of USB Stick does not have enforcing=0 on boot line firstboot fails'''<br />
'''enforcing=0 has to be entered on boot line every time the USB-stick is booted or login fails'''<br />
*'''Does not let me log in as user registered in firstboot'''<br />
* '''root login fails also'''<br />
<br />
===Fedora-17-Nightly-20120208.15-i686-Live-soas-FAILS===<br />
http://koji.fedoraproject.org/koji/getfile?taskID=3773474&name=Fedora-17-Nightly-20120208.15-i686-Live-soas.iso<br />
*Does not boot - problem with start x starting?<br />
*boot selinux-0 setenforce=0 nomodeset<br />
::started display manager.....last entry<br />
*Basic Video<br />
::started display manager.....last entry<br />
<br />
===Fedora-17-Nightly-20120205.21-i686-Live-soas===<br />
http://koji.fedoraproject.org/koji/getfile?taskID=3764890&name=Fedora-17-Nightly-20120205.21-i686-Live-soas.iso<br />
<br />
====About my Computer====<br />
Sugar on a Stick 7<br />
Fedora release 17 (Beefy Miracle)<br />
0.95.4 '''new'''<br />
V1.05<br />
====Activities====<br />
*no changes except<br />
turtle art (131) now 134 '''new'''<br />
<br />
====Speech Feature====<br />
*'''New feature''' in bottom right frame.<br />
:> ''Say selected text''<br />
:> ''Stop playback''<br />
::Pitch and Rate are adjustable<br />
*Reads selected text from sugarlabs wiki (Browse 130) and IRC 10.<br />
====Bugs====<br />
*No Wireless AP or Ad-Hoc<br />
*Can't open font file TRUE<br />
:boots past this error with no problem<br />
*'''f16 Artwork'''<br />
<br />
====[[Sugar_Creation_Kit/sck/liveinst|liveinst to USB]]====<br />
*Also works for HD install with:<br />
:http://koji.fedoraproject.org/koji/getfile?taskID=3766433&name=Fedora-17-Nightly-20120206.11-x86_64-Live-desktop.iso<br />
:2012/02/07<br />
*'''WORKS''' anaconda-17.5-1.fc17.i686<br />
*4 GB USB-stick<br />
bios boot 1<br />
ext4 / 3900<br />
no swap<br />
<br />
===Fedora-17-Nightly-20120202.09-i686-Live-soas===<br />
http://koji.fedoraproject.org/koji/getfile?taskID=3757139&name=Fedora-17-Nightly-20120202.09-i686-Live-soas.iso<br />
====About my Computer====<br />
Sugar on a Stick 7<br />
Fedora release 17 (Beefy Miracle)<br />
0.95.1<br />
V1.05<br />
<br />
====Activities====<br />
chat 73<br />
maze 15<br />
moon 13<br />
abacus 31<br />
ruler 17<br />
portfolio 20<br />
write 77<br />
etoys 116<br />
typing turtle 29<br />
jukebox 23<br />
turtle art 131<br />
irc 10<br />
memorize 39<br />
pippy 44<br />
image viewer 19<br />
speak 35<br />
log 26 ==>27<br />
calculate 38<br />
terminal 35<br />
record 93<br />
clock 7<br />
visual match 34<br />
physics 9<br />
browse 130<br />
read 94<br />
<br />
====Bugs====<br />
*No Wireless AP or Ad-Hoc<br />
<br />
====[[Sugar_Creation_Kit/sck/liveinst|liveinst to USB]]====<br />
*'''WORKS''' anaconda-17.5-1.fc17.i686<br />
*4 GB USB-stick<br />
bios boot 1<br />
ext4 / 3900<br />
no swap<br />
====CD Boots Mac-x86_64====<br />
*http://koji.fedoraproject.org/koji/getfile?taskID=3757142&name=Fedora-17-Nightly-20120202.09-x86_64-Live-soas.iso<br />
*hold "option " key until see windows CD to right of Mac HD Icon. select and boot<br />
*''''No wired or wireless connections'''<br />
<br />
===Fedora-17-Alpha-TC1-netinst.iso===<br />
*installed Feb 03 2012<br />
*http://dl.fedoraproject.org/pub/alt/stage/17-Alpha.TC1/Fedora/i386/iso/Fedora-17-Alpha-i386-netinst.iso<br />
====[[Sugar_Creation_Kit/sck/netinstall|install testing]]====<br />
*320 GB Seagate external USB Hard Drive<br />
*ACER ASPIRE ONE N450 with external USB DVD/CD drive<br />
*boot from burned CD<br />
*Use whole disk<br />
*Customize Now<br />
#GNOME<br />
#Sugar-desktop<br />
:Select extra sugar components including sugar-emulator<br />
*Finished-reboot from USB Hard dirve<br />
*Firstboot<br />
*Select Sugar from gdm switcher on log in<br />
<br />
====About my Computer====<br />
Build Fedora release 17 (rawhide)<br />
Sugar 0.95.4<br />
Firmware V1.05<br />
====Bugs====<br />
*No wireless AP's on f1 Network Neighborhood<br />
:https://bugzilla.redhat.com/show_bug.cgi?id=783712<br />
:Wired cat5 network sees jabber.sugarlabs.org<br />
====GNOME 3.3.4====<br />
*Firefox 10.0<br />
*libre Office 3 included but [grey] invisible icons<br />
====VirtualBox netinstall====<br />
:http://dl.fedoraproject.org/pub/alt/stage/17-Alpha.TC1/Fedora/i386/iso/Fedora-17-Alpha-i386-netinst.iso<br />
*on boot: <TAB> backspace thru quiet add to command line:<br />
selinux=0 setenforce=0 nomodeset<br />
*Required to get VirtualBox to install.<br />
*'''4-5 minutes to load''' be patient<br />
*Defaults to text based install<br />
:no selection of installation changes- installs 192 packages<br />
*Overall install takes over 1 Hr.<br />
*'''Install only boots to login prompt''' root and password only<br />
:Bug:https://bugzilla.redhat.com/show_bug.cgi?id=785652<br />
<br />
==Fedora-17-Nightly-20120120.10-i686-Live-soas==<br />
:Link:http://koji.fedoraproject.org/koji/getfile?taskID=3718102&name=Fedora-17-Nightly-20120120.10-i686-Live-soas.iso<br />
*Boots Properly<br />
*Sees Jabber on wired connection<br />
*'''Does not see wireless AP or AD-Hoc on f1 screen'''<br />
: https://bugzilla.redhat.com/show_bug.cgi?id=783712 http://bugs.sugarlabs.org/ticket/3298<br />
: does not have driver for ACER ASPIRE ONE N450? it has always worked before<br />
*Has Documents Folder in left bottom corner screen in Journal View<br />
:Allows Drag-drop of files to Documents <br />
===CP About my Computer===<br />
Build: Sugar on a Stick 7<br />
Fedora release 17 (Beefy Miracle)<br />
Sugar: 0.95.1<br />
Firmware:V1.05<br />
===Applications===<br />
'''key +==> updates version no.'''<br />
maze 14 +==>15<br />
chat 73<br />
moon 13<br />
abacus 31<br />
ruler 17<br />
portfolio 20 (not a favorite) -shows starred (selected) items from sugar-journal<br />
write 77<br />
etoys 116 - '''DBusError:process /usr/bin/sugar-presence-service exited with status 1'''<br />
typing turtle 29<br />
jukebox 23<br />
Turtle art 131 <br />
irc 10<br />
memorize 39 <br />
pippy 44 - physics: ImportError: cannot import name physics<br />
image viewer 19<br />
speak 35 <br />
log 26 +==>27<br />
calculate 38<br />
terminal 35<br />
record 93 - no sound on ACER ASPIRE ONE N450<br />
clock 7 - Starts with analog clock<br />
visual match 34<br />
physics 9<br />
surf 115<br />
browse 130 (not a favorite) works '''No bookmarks''' http://bugs.sugarlabs.org/ticket/3300<br />
read 94 (not a favorite) *fails to start when try to open txt file<br />
<br />
===Errors===<br />
*Etoys and log do not color after use on (f3) Home ring<br />
*"liveinst" from root terminal: <br />
Traceback (most recent call last):<br />
File "/usr/sbin/anaconda" line 606, in <module><br />
from pyanaconda import kickstart<br />
File "/usr/lib/python2.7/site-packages/pyanaconda/kickstart.py", line 32, in <module><br />
from errors import*<br />
ImportError: no module named errors<br />
:'''Will not install to Hard Disk'''<br />
==Fedora-16-Nightly-20111016.20-i686-Live-soas==<br />
:http://koji.fedoraproject.org/koji/getfile?taskID=3435814&name=Fedora-16-Nightly-20111016.20-i686-Live-soas.iso<br />
===create USB with livecd-iso-to-disk script===<br />
*'''2GB firefly USB formatted fat 16 with boot flag'''<br />
# ./livecd-iso-to-disk.sh --reset-mbr --overlay-size-mb 300 --home-size-mb 175 --delete-home --unencrypted-home /home/robert/Desktop/Fedora-16-Nightly-20111016.20-i686-Live-soas.iso /dev/sdg1<br />
Verifying image...<br />
./livecd-iso-to-disk.sh: line 385: checkisomd5: command not found<br />
Are you SURE you want to continue?<br />
Press Enter to continue or ctrl-c to abort<br />
Copying live image to USB stick<br />
Updating boot config file<br />
Initializing persistent overlay file<br />
300+0 records in<br />
300+0 records out<br />
314572800 bytes (315 MB) copied, 41.3084 s, 7.6 MB/s<br />
Initializing persistent /home<br />
175+0 records in<br />
175+0 records out<br />
183500800 bytes (184 MB) copied, 26.235 s, 7.0 MB/s<br />
Formatting unencrypted /home<br />
mke2fs 1.41.4 (27-Jan-2009)<br />
Filesystem label=<br />
OS type: Linux<br />
Block size=1024 (log=0)<br />
Fragment size=1024 (log=0)<br />
44880 inodes, 179200 blocks<br />
8960 blocks (5.00%) reserved for the super user<br />
First data block=1<br />
Maximum filesystem blocks=67371008<br />
22 block groups<br />
8192 blocks per group, 8192 fragments per group<br />
2040 inodes per group<br />
Superblock backups stored on blocks: <br />
8193, 24577, 40961, 57345, 73729<br />
Writing inode tables: done <br />
Creating journal (4096 blocks): done<br />
Writing superblocks and filesystem accounting information: done<br />
This filesystem will be automatically checked every 33 mounts or<br />
180 days, whichever comes first. Use tune2fs -c or -i to override.<br />
tune2fs 1.41.4 (27-Jan-2009)<br />
Setting maximal mount count to -1<br />
Setting interval between checks to 0 seconds<br />
Installing boot loader<br />
USB stick set up as live image!<br />
*'''Boots Fine'''<br />
<br />
<br />
===Install to HD (liveinst)===<br />
==== F16 disk utility ====<br />
format HD<br />
format partion ext4<br />
* Discovered that using gparted to format the HD partition on Ubuntu causes liveinst failure as it cannot see the 1 MiB first partition.<br />
: '''NOR can the installer'''<br />
====liveinst====<br />
Boot Live SoaS CD<br />
terminal:<br />
liveinst<br />
custom<br />
ext4 / [format] (not allowed to use existing ext4 fs)<br />
installing bootloader<br />
*'''Works Great. boots to firstboot....gdm login'''<br />
:F1 Network neigborhood shows jabber avitars<br />
<br />
===Boots on MacBook Pro i7===<br />
CD <br />
option key ==> windows<br />
has efi folder but does not show up on Mac<br />
<br />
<br />
<br />
* '''Use the ← left________________________right → links in the colored bar below<br />
:to connect to another part of this Annotated Guide to Sugar'''<br />
{| width="100%" cellpadding="0" cellspacing="0"<br />
|-<br />
|width=25% align=left bgcolor=#C3D9FF|&larr; '''[[Sugar_Creation_Kit/sck/Introduction_to_Sugar_Interface|Introduction to the Sugar Interface]]'''<br />
|width=50% align=center bgcolor=#C3D9FF|'''[[Sugar_Creation_Kit#All_Prebuilt_VirtualBox_Appliances|VirtualBox Appliances]]'''<br />
|width=25% align=right bgcolor=#C3D9FF| '''[[Sugar_Creation_Kit#Community_Distributions_Complete_Listing|Community Distributions]]''' &rarr;<br />
|}<br />
{| width="100%" cellpadding="0" cellspacing="0"<br />
|-<br />
|width=25% align=left bgcolor=#C3D9FF|&larr; '''[[Sugar_Creation_Kit/sck/How_to_use_Chat-es| Cómo usar Chat ]]'''<br />
|width=50% align=center bgcolor=#C3D9FF|'''[[Sugar_Creation_Kit/sck/Introduction_to_Sugar_Interface-es|Introducción a la interfaz de Azúcar]]'''<br />
|width=25% align=right bgcolor=#C3D9FF| '''←[[Sugar_Creation_Kit#Introducci.C3.B3n_a_la_interfaz_de_Az.C3.BAcar|Azúcar Creación Kit ]]'''<br />
|}</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Sugar_on_a_Stick_QA&diff=76087Sugar on a Stick QA2012-03-04T03:17:08Z<p>Skierpage: /* Smoke tests */ fix wiki links</p>
<hr />
<div><noinclude><div id="contentSub"><span class="subpages">< [[Sugar on a Stick]]</span></div><br />
[[Category:Testing]]<br />
[[Category:Sugar on a Stick]]<br />
</noinclude><br />
<br />
This page is for QA activities related to [[Sugar on a Stick]]. We are currently testing the v.4.0 Mango Lassi release, so this page is a work in progress and may be rough.<br />
<br />
== How to add a test result ==<br />
<br />
Copy-paste the template below to another line at the bottom of the [[#Test results]] table.<br />
<br />
<pre><br />
|-<br />
| <!-- nightly build number --><br />
| <!-- tester's SL wiki username --><br />
| <!-- does it boot? --><br />
| <!--Neighborhood? --><br />
| <!-- Browse --><br />
| <!-- Etoys --><br />
| <!-- Chat --><br />
| <!-- Terminal --><br />
| <!-- Turtle Art --><br />
| <!--IRC --><br />
| <!-- Log --><br />
| <!-- Write --><br />
| <!-- Record --><br />
| <!-- Physics --><br />
| <!-- Read --><br />
</pre><br />
<br />
Add results for each of the [[#Smoke tests]] as follows:<br />
<br />
<pre><br />
| <!-- name of test --> style="background: lime" | yes<br />
| <!-- name of test --> style="background: orange" | partially working (comments go here)<br />
| <!-- name of test --> style="background: red" | not working (describe failure)<br />
</pre><br />
<br />
== Test results ==<br />
<br />
{|border="1" cellspacing="0" width="100%" align="center" class="wikitable sortable"<br />
! Nightly build<br />
! Tested by<br />
! Boots?<br />
! Neighborhood?<br />
! Browse<br />
! Etoys<br />
! Chat<br />
! Terminal<br />
! Turtle Art<br />
! IRC<br />
! Log<br />
! Write<br />
! Record<br />
! Physics<br />
! Read<br />
|-<br />
| <!-- Nightly build --> 20100429.16.iso<br />
| <!-- Tested by --> [[User:Mchua|Mchua]]<br />
| <!-- Boots? --> style="background: lime" | yes<br />
| <!-- Neighborhood? --> style="background: orange" | with [https://admin.fedoraproject.org/updates/telepathy-gabble-0.9.11-1.fc13 telepathy-gabble update]<br />
| <!-- Browse --> style="background: lime" | yes<br />
| <!-- Etoys --> style="background: lime" | yes<br />
| <!-- Chat --> style="background: lime" | yes<br />
| <!-- Terminal --> style="background: lime" | yes<br />
| <!-- Turtle Art --> style="background: lime" | yes<br />
| <!-- IRC --> style="background: lime" | yes <br />
| <!-- Log --> style="background: lime" | yes<br />
| <!-- Write --> style="background: lime" | yes<br />
| <!-- Record --> style="background: lime" | yes <br />
| <!-- Physics --> style="background: lime" | yes<br />
| <!-- Read --> style="background: orange" | yes, but no book files to open<br />
|-<br />
| <!-- nightly build number -->RC3/Spins/Fedora-13-i686-Live-SoaS as 2GB USB<br />
| <!-- tester's SL wiki username --> [[User:Satellit|satellit]]<br />
| <!-- does it boot? -->style="background: lime" |yes <br />
| <!--Neighborhood? -->style="background: lime" |yes <br />
| <!-- Browse -->style="background: lime" |yes<br />
| <!-- Etoys -->style="background: lime" |yes<br />
| <!-- Chat -->style="background: lime" |yes-2 way with xo-1 & Blueberry[http://wiki.sugarlabs.org/go/Talk:Sugar_on_a_Stick/Mirabelle]<br />
| <!-- Terminal -->style="background: lime" | yes<br />
| <!-- Turtle Art -->style="background: lime" |yes<br />
| <!--IRC -->style="background: lime" |yes<br />
| <!-- Log -->style="background: lime" |yes<br />
| <!-- Write -->style="background: lime" |yes-2 way with xo-1 & Blueberry; colors and fonts working[http://wiki.sugarlabs.org/go/Talk:Sugar_on_a_Stick/Mirabelle]<br />
| <!-- Record -->style="background: orange" |yes but no sound on some netbooks<br />
| <!-- Physics -->style="background: lime" |yes<br />
| <!-- Read -->style= |Broken-Not included<br />
|-<br />
| <!-- nightly build number -->soas-i386-20100611.15.iso (rawhide) as 4 GB USB<br />
| <!-- tester's SL wiki username --> [[User:Satellit|satellit]]<br />
| <!-- does it boot? -->style="background: lime" |yes <br />
| <!--Neighborhood? -->style="background: lime" |yes <br />
| <!-- Browse -->style="background: lime" |yes<br />
| <!-- Etoys -->style="background: lime" |yes<br />
| <!-- Chat -->style="background: lime" |yes<br />
| <!-- Terminal -->style="background: lime" | yes<br />
| <!-- Turtle Art -->style="background: lime" |yes-Turtle Blocks 88<br />
| <!-- IRC -->style="background: lime" |yes<br />
| <!-- Log -->style="background: lime" |yes<br />
| <!-- Write -->style="background: lime" |yes<br />
| <!-- Record -->style="background: orange" |yes but no sound on some netbooks<br />
| <!-- Physics -->style="background: lime" |yes<br />
| <!-- Read -->style= |Broken-Not included<br />
|-<br />
| <!-- nightly build number -->Fedora-14-x86_64-Live-SoaS.iso '''F14 Final Release''' [http://wiki.sugarlabs.org/go/Talk:Sugar_on_a_Stick_QA#Soas_v4_Soas_Boots_on_Mac_Air Soas_v4_Soas_Boots_on_Mac_Air]<br />
| <!-- tester's SL wiki username --> [[User:Satellit|satellit]]<br />
| <!-- does it boot? -->style="background: lime" |yes [https://bugzilla.redhat.com/show_bug.cgi?id=649013 bugzilla#649013]<br />
| <!--Neighborhood? -->style="background: orange" |yes [http://bugs.sugarlabs.org/ticket/2483 SL#2483][http://bugs.sugarlabs.org/ticket/2395 SL#2395]<br />
| <!-- Browse -->style="background: lime" |yes 119<br />
| <!-- Etoys -->style="background: lime" |yes 116<br />
| <!-- Chat -->style="background: lime" |yes 68<br />
| <!-- Terminal -->style="background: lime" |yes 31<br />
| <!-- Turtle Art -->style="background: lime" |yes Turtle Blocks 100<br />
| <!--IRC -->style="background: lime" |yes 6<br />
| <!-- Log -->style="background: lime" |yes 24<br />
| <!-- Write -->style="background: lime" |yes 71<br />
| <!-- Record -->style="background: orange" |yes 66 but no sound on some netbooks<br />
| <!-- Physics -->style="background: lime" |yes 5<br />
| <!-- Read -->style= |Broken not included ''fix coming''<br />
|-<br />
| <!-- nightly build number --><br />
| <!-- tester's SL wiki username --><br />
| <!-- does it boot? --><br />
| <!--Neighborhood? --><br />
| <!-- Browse --><br />
| <!-- Etoys --><br />
| <!-- Chat --><br />
| <!-- Terminal --><br />
| <!-- Turtle Art --><br />
| <!--IRC --><br />
| <!-- Log --><br />
| <!-- Write --><br />
| <!-- Record --><br />
| <!-- Physics --><br />
| <!-- Read --><br />
|-<br />
| <!-- nightly build number --><br />
| <!-- tester's SL wiki username --><br />
| <!-- does it boot? --><br />
| <!--Neighborhood? --><br />
| <!-- Browse --><br />
| <!-- Etoys --><br />
| <!-- Chat --><br />
| <!-- Terminal --><br />
| <!-- Turtle Art --><br />
| <!--IRC --><br />
| <!-- Log --><br />
| <!-- Write --><br />
| <!-- Record --><br />
| <!-- Physics --><br />
| <!-- Read --><br />
|-<br />
| <!-- nightly build number --><br />
| <!-- tester's SL wiki username --><br />
| <!-- does it boot? --><br />
| <!--Neighborhood? --><br />
| <!-- Browse --><br />
| <!-- Etoys --><br />
| <!-- Chat --><br />
| <!-- Terminal --><br />
| <!-- Turtle Art --><br />
| <!--IRC --><br />
| <!-- Log --><br />
| <!-- Write --><br />
| <!-- Record --><br />
| <!-- Physics --><br />
| <!-- Read --><br />
|-<br />
| <!-- nightly build number --><br />
| <!-- tester's SL wiki username --><br />
| <!-- does it boot? --><br />
| <!--Neighborhood? --><br />
| <!-- Browse --><br />
| <!-- Etoys --><br />
| <!-- Chat --><br />
| <!-- Terminal --><br />
| <!-- Turtle Art --><br />
| <!--IRC --><br />
| <!-- Log --><br />
| <!-- Write --><br />
| <!-- Record --><br />
| <!-- Physics --><br />
| <!-- Read --><br />
|-<br />
|}<br />
<br />
== Smoke tests ==<br />
<br />
* '''Boot:''' [[Talk:Sugar_on_a_Stick_release_process#Test_Matrix|Test Matrix]] Does it boot? Can you choose a name and colors, and navigate through the Neighborhood/Friends/Home/Journal screens?<br />
* '''Neighborhood?''' Can you get on Jabber and see other Sugar users in your Neighborhood? (This also implies that your wifi or wired Network Connection works.)<br />
* '''Activity tests:''' For each Activity, the following criteria must be met:<br />
** The Activity starts from Home view.<br />
** You can perform a basic action in the Activity (for instance, loading a webpage in Browse, or joining a channel with IRC, or typing some words in Write.)<br />
** The Activity can be stopped via the button in the Frame.<br />
** The Activity session is saved in the Journal.<br />
** The Activity can be shared with other Sugar users in your Neighborhood.<br />
** '''Collaboration Test Reports:''' [[Talk:Sugar_on_a_Stick_release_process#Collaboration |Collaboration]]<br />
** '''Activities tested to be compatible with Mango Lassi''' [[Features/Soas_V4/ASLOxo_Activity_Test_Table#Activity_Test_Results |Activity Testing]]<br />
<br />
== Bug reports ==<br />
* [[Sugar on a Stick Bugs]]<br />
*:Also [[Sugar on a Stick/Bugs]]</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Sugar_on_a_Stick_QA&diff=76086Sugar on a Stick QA2012-03-04T03:15:26Z<p>Skierpage: /* Bug reports */ fix wiki links</p>
<hr />
<div><noinclude><div id="contentSub"><span class="subpages">< [[Sugar on a Stick]]</span></div><br />
[[Category:Testing]]<br />
[[Category:Sugar on a Stick]]<br />
</noinclude><br />
<br />
This page is for QA activities related to [[Sugar on a Stick]]. We are currently testing the v.4.0 Mango Lassi release, so this page is a work in progress and may be rough.<br />
<br />
== How to add a test result ==<br />
<br />
Copy-paste the template below to another line at the bottom of the [[#Test results]] table.<br />
<br />
<pre><br />
|-<br />
| <!-- nightly build number --><br />
| <!-- tester's SL wiki username --><br />
| <!-- does it boot? --><br />
| <!--Neighborhood? --><br />
| <!-- Browse --><br />
| <!-- Etoys --><br />
| <!-- Chat --><br />
| <!-- Terminal --><br />
| <!-- Turtle Art --><br />
| <!--IRC --><br />
| <!-- Log --><br />
| <!-- Write --><br />
| <!-- Record --><br />
| <!-- Physics --><br />
| <!-- Read --><br />
</pre><br />
<br />
Add results for each of the [[#Smoke tests]] as follows:<br />
<br />
<pre><br />
| <!-- name of test --> style="background: lime" | yes<br />
| <!-- name of test --> style="background: orange" | partially working (comments go here)<br />
| <!-- name of test --> style="background: red" | not working (describe failure)<br />
</pre><br />
<br />
== Test results ==<br />
<br />
{|border="1" cellspacing="0" width="100%" align="center" class="wikitable sortable"<br />
! Nightly build<br />
! Tested by<br />
! Boots?<br />
! Neighborhood?<br />
! Browse<br />
! Etoys<br />
! Chat<br />
! Terminal<br />
! Turtle Art<br />
! IRC<br />
! Log<br />
! Write<br />
! Record<br />
! Physics<br />
! Read<br />
|-<br />
| <!-- Nightly build --> 20100429.16.iso<br />
| <!-- Tested by --> [[User:Mchua|Mchua]]<br />
| <!-- Boots? --> style="background: lime" | yes<br />
| <!-- Neighborhood? --> style="background: orange" | with [https://admin.fedoraproject.org/updates/telepathy-gabble-0.9.11-1.fc13 telepathy-gabble update]<br />
| <!-- Browse --> style="background: lime" | yes<br />
| <!-- Etoys --> style="background: lime" | yes<br />
| <!-- Chat --> style="background: lime" | yes<br />
| <!-- Terminal --> style="background: lime" | yes<br />
| <!-- Turtle Art --> style="background: lime" | yes<br />
| <!-- IRC --> style="background: lime" | yes <br />
| <!-- Log --> style="background: lime" | yes<br />
| <!-- Write --> style="background: lime" | yes<br />
| <!-- Record --> style="background: lime" | yes <br />
| <!-- Physics --> style="background: lime" | yes<br />
| <!-- Read --> style="background: orange" | yes, but no book files to open<br />
|-<br />
| <!-- nightly build number -->RC3/Spins/Fedora-13-i686-Live-SoaS as 2GB USB<br />
| <!-- tester's SL wiki username --> [[User:Satellit|satellit]]<br />
| <!-- does it boot? -->style="background: lime" |yes <br />
| <!--Neighborhood? -->style="background: lime" |yes <br />
| <!-- Browse -->style="background: lime" |yes<br />
| <!-- Etoys -->style="background: lime" |yes<br />
| <!-- Chat -->style="background: lime" |yes-2 way with xo-1 & Blueberry[http://wiki.sugarlabs.org/go/Talk:Sugar_on_a_Stick/Mirabelle]<br />
| <!-- Terminal -->style="background: lime" | yes<br />
| <!-- Turtle Art -->style="background: lime" |yes<br />
| <!--IRC -->style="background: lime" |yes<br />
| <!-- Log -->style="background: lime" |yes<br />
| <!-- Write -->style="background: lime" |yes-2 way with xo-1 & Blueberry; colors and fonts working[http://wiki.sugarlabs.org/go/Talk:Sugar_on_a_Stick/Mirabelle]<br />
| <!-- Record -->style="background: orange" |yes but no sound on some netbooks<br />
| <!-- Physics -->style="background: lime" |yes<br />
| <!-- Read -->style= |Broken-Not included<br />
|-<br />
| <!-- nightly build number -->soas-i386-20100611.15.iso (rawhide) as 4 GB USB<br />
| <!-- tester's SL wiki username --> [[User:Satellit|satellit]]<br />
| <!-- does it boot? -->style="background: lime" |yes <br />
| <!--Neighborhood? -->style="background: lime" |yes <br />
| <!-- Browse -->style="background: lime" |yes<br />
| <!-- Etoys -->style="background: lime" |yes<br />
| <!-- Chat -->style="background: lime" |yes<br />
| <!-- Terminal -->style="background: lime" | yes<br />
| <!-- Turtle Art -->style="background: lime" |yes-Turtle Blocks 88<br />
| <!-- IRC -->style="background: lime" |yes<br />
| <!-- Log -->style="background: lime" |yes<br />
| <!-- Write -->style="background: lime" |yes<br />
| <!-- Record -->style="background: orange" |yes but no sound on some netbooks<br />
| <!-- Physics -->style="background: lime" |yes<br />
| <!-- Read -->style= |Broken-Not included<br />
|-<br />
| <!-- nightly build number -->Fedora-14-x86_64-Live-SoaS.iso '''F14 Final Release''' [http://wiki.sugarlabs.org/go/Talk:Sugar_on_a_Stick_QA#Soas_v4_Soas_Boots_on_Mac_Air Soas_v4_Soas_Boots_on_Mac_Air]<br />
| <!-- tester's SL wiki username --> [[User:Satellit|satellit]]<br />
| <!-- does it boot? -->style="background: lime" |yes [https://bugzilla.redhat.com/show_bug.cgi?id=649013 bugzilla#649013]<br />
| <!--Neighborhood? -->style="background: orange" |yes [http://bugs.sugarlabs.org/ticket/2483 SL#2483][http://bugs.sugarlabs.org/ticket/2395 SL#2395]<br />
| <!-- Browse -->style="background: lime" |yes 119<br />
| <!-- Etoys -->style="background: lime" |yes 116<br />
| <!-- Chat -->style="background: lime" |yes 68<br />
| <!-- Terminal -->style="background: lime" |yes 31<br />
| <!-- Turtle Art -->style="background: lime" |yes Turtle Blocks 100<br />
| <!--IRC -->style="background: lime" |yes 6<br />
| <!-- Log -->style="background: lime" |yes 24<br />
| <!-- Write -->style="background: lime" |yes 71<br />
| <!-- Record -->style="background: orange" |yes 66 but no sound on some netbooks<br />
| <!-- Physics -->style="background: lime" |yes 5<br />
| <!-- Read -->style= |Broken not included ''fix coming''<br />
|-<br />
| <!-- nightly build number --><br />
| <!-- tester's SL wiki username --><br />
| <!-- does it boot? --><br />
| <!--Neighborhood? --><br />
| <!-- Browse --><br />
| <!-- Etoys --><br />
| <!-- Chat --><br />
| <!-- Terminal --><br />
| <!-- Turtle Art --><br />
| <!--IRC --><br />
| <!-- Log --><br />
| <!-- Write --><br />
| <!-- Record --><br />
| <!-- Physics --><br />
| <!-- Read --><br />
|-<br />
| <!-- nightly build number --><br />
| <!-- tester's SL wiki username --><br />
| <!-- does it boot? --><br />
| <!--Neighborhood? --><br />
| <!-- Browse --><br />
| <!-- Etoys --><br />
| <!-- Chat --><br />
| <!-- Terminal --><br />
| <!-- Turtle Art --><br />
| <!--IRC --><br />
| <!-- Log --><br />
| <!-- Write --><br />
| <!-- Record --><br />
| <!-- Physics --><br />
| <!-- Read --><br />
|-<br />
| <!-- nightly build number --><br />
| <!-- tester's SL wiki username --><br />
| <!-- does it boot? --><br />
| <!--Neighborhood? --><br />
| <!-- Browse --><br />
| <!-- Etoys --><br />
| <!-- Chat --><br />
| <!-- Terminal --><br />
| <!-- Turtle Art --><br />
| <!--IRC --><br />
| <!-- Log --><br />
| <!-- Write --><br />
| <!-- Record --><br />
| <!-- Physics --><br />
| <!-- Read --><br />
|-<br />
| <!-- nightly build number --><br />
| <!-- tester's SL wiki username --><br />
| <!-- does it boot? --><br />
| <!--Neighborhood? --><br />
| <!-- Browse --><br />
| <!-- Etoys --><br />
| <!-- Chat --><br />
| <!-- Terminal --><br />
| <!-- Turtle Art --><br />
| <!--IRC --><br />
| <!-- Log --><br />
| <!-- Write --><br />
| <!-- Record --><br />
| <!-- Physics --><br />
| <!-- Read --><br />
|-<br />
|}<br />
<br />
== Smoke tests ==<br />
<br />
* '''Boot:''' [http://wiki.sugarlabs.org/go/Talk:Sugar_on_a_Stick_release_process#Test_Matrix TestMatrix] Does it boot? Can you choose a name and colors, and navigate through the Neighborhood/Friends/Home/Journal screens?<br />
* '''Neighborhood?''' Can you get on Jabber and see other Sugar users in your Neighborhood? (This also implies that your wifi or wired Network Connection works.)<br />
* '''Activity tests:''' For each Activity, the following criteria must be met:<br />
** The Activity starts from Home view.<br />
** You can perform a basic action in the Activity (for instance, loading a webpage in Browse, or joining a channel with IRC, or typing some words in Write.)<br />
** The Activity can be stopped via the button in the Frame.<br />
** The Activity session is saved in the Journal.<br />
** The Activity can be shared with other Sugar users in your Neighborhood.<br />
** '''Collaboration Test Reports:''' [http://wiki.sugarlabs.org/go/Talk:Sugar_on_a_Stick_release_process#Collaboration Collaboration]<br />
** '''Activities tested to be compatible with Mango Lassi''' [http://wiki.sugarlabs.org/go/Features/Soas_V4/ASLOxo_Activity_Test_Table#Activity_Test_Results Activity Testing]<br />
<br />
== Bug reports ==<br />
* [[Sugar on a Stick Bugs]]<br />
*:Also [[Sugar on a Stick/Bugs]]</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Sugar_Creation_Kit/sck/Activity_Matrix&diff=74205Sugar Creation Kit/sck/Activity Matrix2012-01-15T00:09:03Z<p>Skierpage: /* Test */ fix wiki markup</p>
<hr />
<div>*Copied from old page http://wiki.sugarlabs.org/go/Features/Soas_V4/ASLOxo_Activity_Test_Table#Activity_Test_Results<br />
:Plan to do updates here --[[User:Satellit|Satellit]] 11:46, 6 January 2012 (EST)<br />
==Install Test Table==<br />
<br />
*'''Activities main Page: http://wiki.sugarlabs.org/go/Activities'''<br />
: Also: http://wiki.laptop.org/go/Activities/All<br />
*Old Install testing Page(Archive):<br />
:'''Go To:''' [http://wiki.sugarlabs.org/go/Talk:Sugar_Creation_Kit/sck/Activity_Matrix '''Tests older than SoaS-v5''']<br />
:Original Wiki page: http://wiki.sugarlabs.org/go/Talk:Sugar_on_a_Stick_release_process#Test_Matrix<br />
<br />
==Activity Test Table==<br />
<br />
'''Used to report Compatibility of Sugar Activities'''<br />
<br />
:What activities will work in different versions of Sugar<br />
<br />
===This is a very simple "Smoke Test" sequence to be enlarged upon. Please add to it===<br />
<br />
====Test====<br />
''' Did activity start-stop-save and resume from journal?'''<br />
<br />
=====How To Test=====<br />
*Updated Jan 06 2011<br />
: This wiki page is being slowly updated for later versions of ASLO activities and Soas Versions --[[User:Satellit|Satellit]] 13:10, 6 January 2012 (EST)<br />
<br />
'''On your PC:'''<br />
<br />
:# Download <code>ASLOxo6-2.iso</code> from '''http://download.sugarlabs.org/images/ASLOxo6-2.iso''' ---- [http://download.sugarlabs.org/images/ASLOxo6.2-Contents.txt ASLOxo6.2-List of Contents] <br />
:# Burn CD from <code>ASLOxo6-2.iso</code><br />
:# Copy-Paste the contents of the CD to a 2nd USB-stick; labeled "ASLOxo" .<br />
<br />
'''Boot a Soas USB or a running Soas CD'''<br />
<br />
:# Insert ASLOxo USB-stick into a USB slot, wait for it to mount.<br />
:# Select the Journal on top of Sugar's Frame.<br />
:# Drop down to bottom-left corner of screen, the Frame will retract and show two USB icons.<br />
:# Select the 2nd (right) USB (ASLOxo).<br />
:# [[Sugar_Creation_Kit/sck/Drag-Drop|Drag-drop]] the desired application.xo (hold down the left button and drag the entry) from the listing into the sugar-journal on the bottom (left USB icon) corner of the monitor OR double click on application.xo in the list of the ASLOxo USB-stick.<br />
<br />
'''The Activity should:'''<br />
<br />
:* Start normally;<br />
:* Shut down normally;<br />
:* Collaborate (if that is an enabled feature);<br />
:* Resume from the saved Journal;<br />
<br />
'''All behavior should be identical to a download in Browse from activities.sugarlabs.org (ASLO) [http://activities.sugarlabs.org].'''<br />
<br />
<br />
=====Updates=====<br />
{| class="wikitable sortable"<br />
<br />
|+Please update when you make major edits to the Activity Test Table below:<br />
<br />
|-<br />
<br />
! Revision Type !!Activity Number!! class="unsortable" |Date Revised!! class="unsortable" |XO-1 !! class="unsortable" |[http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Coconut SoaS-v5 Coconut]!! class="unsortable" |[http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Pineapple SoaS-v6 Pineapple]!! class="unsortable" |Blank!! class="unsortable" |Blank!! class="unsortable" |User- Notes and Bug Numbers<br />
<br />
|-<br />
<br />
|All ||&nbsp;||Jan 06 2011 ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp;||&nbsp; ||satellit-Initial setup<br />
<br />
|-<br />
<br />
|All||&nbsp;||Jan 06 2011 ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||satellit_-Blank out old entries<br />
<br />
|-<br />
<br />
|&nbsp;||&nbsp;||&nbsp; ||&nbsp; ||&nbsp;|&nbsp;||&nbsp;||&nbsp; ||&nbsp;<br />
<br />
|-<br />
<br />
|&nbsp;||&nbsp;||&nbsp;||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp;<br />
|-<br />
<br />
|&nbsp;||&nbsp;||&nbsp;||&nbsp;||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp;<br />
<br />
|-<br />
<br />
|&nbsp;||&nbsp;||&nbsp;||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp;<br />
<br />
|-<br />
<br />
|&nbsp;||&nbsp;||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp;||&nbsp;<br />
<br />
|-<br />
<br />
|&ndash; ||&nbsp;||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp;<br />
<br />
|}<br />
<br />
====Activity Test Table====<br />
<br />
<br />
<br />
*'''Add this Code to make more Lines'''<br />
<br />
* It will look correct when editing<br />
<pre><br />
|-<br />
|&ndash; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp;<br />
|-<br />
|&ndash; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp;<br />
|}<br />
</pre><br />
<br />
:'''list of activity developer pages''': http://wiki.sugarlabs.org/go/Activities<br />
<br />
:'''OLPC Activities''': http://wiki.laptop.org/go/Activities<br />
<br />
:'''Sugar_on_a_Stick/Activity_Criteria''': http://wiki.sugarlabs.org/go/Talk:Sugar_on_a_Stick/Activity_Criteria<br />
<br />
:'''Numeric field is used here: http://download.sugarlabs.org/activities/'''<br />
<br />
<br />
====='''KEY'''=====<br />
<br />
Included on CD <br />
:(version #) yes/no<br />
<br />
*=On [http://download.sugarlabs.org/images/ASLOxo6-2.iso ASLOxo6-2] CD<br />
: yes/no (version #)<br />
<br />
====='''Most Recent-Activity Test Results'''=====<br />
*:'''UNDER CONSTRUCTION''' please help edit this wiki page with your test results<br />
*This is a list of Activity Tests for [http://wiki.sugarlabs.org/go/Dextrose Dextrose]; [[Sugar_on_a_Stick/Coconut|Soas-v5 Coconut]][[Trisquel_On_A_Sugar_Toast|Trisquel-5-Sugar]] and [[Sugar_on_a_Stick/Pineapple|SoaS-v6 Pineapple]]<br />
*Click here to go to [[Sugar_Creation_Kit/sck/Activity_Matrix#Activity_Test_Results_up_to_Soas-v4|'''Older Versions of Sugar''' testing of SoaS-v1 to SoaS-v4 ]]<br />
<br />
* '''A Master list of Activities and testing in various versions of Sugar are listed below:'''<br />
<br />
:'''Tested from Live CD and ASLOxo USB-stick except for XO-1 and XO-1.5'''<br />
: Tested with ACER ASPIRE ONE N450 10" netbook with external USB DVD/CD.<br />
: (Some of the larger Activities may work if installed to a Hard Disk)<br />
<br />
{| class="wikitable sortable"<br />
<br />
|+Did activity start-stop-save and resume from journal? (yes/no) <br />
<br />
|-<br />
<br />
!Alphabetic !! Numeric [ ]!!XO-1.5 os874!! XO-1 os508dx [http://wiki.sugarlabs.org/go/Dextrose Dextrose] !![[Sugar_on_a_Stick/Pineapple|SoaS-v6 Pineapple]] !![[Trisquel_On_A_Sugar_Toast|Trisquel-5-Sugar]] !![[Sugar_on_a_Stick/Coconut|Soas-v5 Coconut]] !! Empty !! Empty !! class="unsortable" | Notes and Bug No.<br />
<br />
|-<br />
<br />
|Abacus ||4293 ||19 yes ||19 yes||26 yes||13 yes||19 yes||&nbsp;||&nbsp;||[[Activities/Abacus |Abacus]] [http://wiki.laptop.org/go/Tests/Activity/Abacus Abacus]|<br />
<br />
|-<br />
<br />
|Analyze || 4200 [http://download.sugarlabs.org/activities/4200/] ||&nbsp;||&nbsp;||8 yes*||8 yes*||&nbsp;||&nbsp;||&nbsp; ||Analyze is an Activity that displays your networking, X (graphical) display, and presence service status. It is useful to developers, testers and end-users as an easy way to monitor and submit data for monitoring/debugging networking/X issues.[http://wiki.sugarlabs.org/go/Activities/Analyze] [http://wiki.laptop.org/go/Analyze Analyze][http://wiki.laptop.org/go/Tests/Activity/Analyze]*no longer sees Presence service<br />
<br />
|-<br />
<br />
|APRS-xo ||4087||&nbsp;||&nbsp;||14 yes*||14 yes*||&nbsp;||&nbsp;||&nbsp;||This amateur radio program will update your position and status on all of the global APRS web pages once every 10 minutes *Callsign & Password required<br />
<br />
|-<br />
<br />
|Arithmetic||4204 [http://download.sugarlabs.org/activities/4204/]||&nbsp;||2 yes||2 yes||2 yes ||3 yes||&nbsp;||&nbsp;||Arithmetic is an activity that allows learners to compete in maths [http://activities.sugarlabs.org/en-US/sugar/addon/4204]<br />
challenges. Learners choose their a difficulty level and whether to do<br />
addition, subtraction, multiplication or division. Challenges work by<br />
Arithmetic providing questions to every learner sharing the activity.<br />
Responses to those questions are checked and timed. The results are<br />
presented on a scoreboard."<br />
<br />
|-<br />
<br />
|Backup||4326 [http://download.sugarlabs.org/activities/4326/]||&nbsp;||&nbsp; ||5 yes||5 yes ||5 yes||&nbsp; ||&nbsp; ||Backup stores the content of the Sugar Journal (or rather the Sugar data store) as multi-entry Journal entry bundles (JEBs) on external storage media.[http://activities.sugarlabs.org/en-US/sugar/addon/4326]<br />
The Restore activity can be used to write back the content of these bundles.<br />
<br />
Supports any data store from 0.84 on, including those with version support. <br />
<br />
|-<br />
<br />
|blockhead||4207 [http://download.sugarlabs.org/activities/4207/]||&nbsp; ||&nbsp; ||7 '''no'''||7 '''no'''||7 '''no'''||&nbsp;||&nbsp;|| Game add Blocks to teach addition<br />
<br />
|-<br />
<br />
|Blockparty||4232 [http://download.sugarlabs.org/activities/4232/]||&nbsp;||&nbsp; ||7 yes||7 yes||7 yes||&nbsp;||&nbsp;|| falling blocks of various shapes- game [http://wiki.laptop.org/go/Block_Party Blockparty-7]<br />
<br />
|-<br />
<br />
|Browse||4024 [http://download.sugarlabs.org/activities/4024/]||122.2 yes||129 yes||'''no''' 130**||129 yes||'''no'''||&nbsp;||&nbsp;||*will not start. '''surf-115''' is used in Soas-v5 and Soas-v6 [http://wiki.laptop.org/go/Tests/Activity/Browse Browse ] [http://wiki.laptop.org/go/Tests/Browse/Sharing_bookmarks]27797 ''' ** browse 130 is not compatible uses gtk +3'''<br />
<br />
|-<br />
<br />
|Calculate||4076 [http://download.sugarlabs.org/activities/4076/] ||37 yes||&nbsp;||38 yes||38 yes||37 yes||&nbsp;||&nbsp;||great calculator [http://wiki.laptop.org/go/Calculate Calculate 30][http://wiki.laptop.org/go/Tests/Activity/Calculate]<br />
<br />
|-<br />
<br />
|calendario||&nbsp;||&nbsp; ||&nbsp;||3 yes||3 yes||3 yes||&nbsp;||&nbsp; ||Calendario is a daily activity for sugar, this will allow children to introduce activities per day so they are reminded of past, present and future activities.[http://wiki.sugarlabs.org/go/Activities/calendario calendario] [http://yaderv.fedorapeople.org/Calendario-1.xo Calendario-1.xo]<br />
<br />
|-<br />
<br />
|Card sort||4217 [http://download.sugarlabs.org/activities/4217/]||&nbsp;||&nbsp;||&nbsp;||6 yes||6 yes;||&nbsp;||&nbsp;||sort cards-game<br />
<br />
|-<br />
<br />
|Cartoon Builder||4037 [http://download.sugarlabs.org/activities/4037/]||&nbsp;||&nbsp; ||9 yes||11 yes ||9 yes||&nbsp;||&nbsp;||MaMaMedia Cartoon Builder (put animations in strip and play) MaMaMedia<br />
<br />
|-<br />
<br />
|CatInAPond ||&nbsp;||&nbsp; ||&nbsp; ||'''no*''' ||'''no*''' ||'''no''' ||&nbsp; ||&nbsp; ||*fails to start<br />
<br />
|-<br />
<br />
|Chat||4069 [http://download.sugarlabs.org/activities/4069/]||70 yes||70 yes||73 yes||73 yes||71 yes; 73 yes||&nbsp;||&nbsp;||[http://wiki.laptop.org/go/Tests/Activity/Chat/Public_chat Chat] [http://en.flossmanuals.net/chat Chat]<br />
<br />
|-6<br />
<br />
|cebalradio ||&nbsp;||&nbsp; ||&nbsp; || '''no''' 1||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||no sound or connection<br />
<br />
|-<br />
<br />
|Clock||4191 ||6 yes||&nbsp; ||7 yes||5 yes||6 yes||&nbsp;||&nbsp;||A simple Activity to learn how to read and tell the time -5 [http://wiki.laptop.org/go/Clock_activity Clock_activity] <br />
<br />
|-<br />
<br />
|Classroom Broadcast ||4507 [http://download.sugarlabs.org/activities/4507/]||&nbsp; ||&nbsp; ||no 4*; no 3||'''no 4*'''||'''no 4*'''||&nbsp; ||&nbsp; ||*4 after start nothing in Acer Aspire ONE N450<br />
<br />
|-<br />
<br />
|colors ||4067 [http://download.sugarlabs.org/activities/4067/]||&nbsp;||15 yes||15 '''no*'''||15 yes||15 '''no'''*||&nbsp;||&nbsp;||colors drawing program * fails to start<br />
<br />
|-<br />
<br />
|Color Deducto ||4221 [http://download.sugarlabs.org/activities/4221/]||&nbsp;||&nbsp;||4 yes||4 yes||4 yes||&nbsp;||&nbsp;||a logic game involving deduction<br />
<br />
|-<br />
<br />
|conozco_america ||&nbsp;||&nbsp; ||&nbsp; ||3 yes ||3 yes ||3 yes ||&nbsp; ||&nbsp; ||Answer questions on geography<br />
<br />
|-<br />
<br />
|Connect||&nbsp;||&nbsp; ||&nbsp;||22 yes* ||22 yes* |&nbsp;||22 yes *||&nbsp;||&nbsp;|| [http://wiki.laptop.org/go/Connect Connect][http://dev.laptop.org/~morgan/bundles/Connect-22.xo] * requires a shared user to connect to play<br />
<br />
|-<br />
<br />
|deducto||4220 [http://download.sugarlabs.org/activities/4220/]||&nbsp;||&nbsp; ||4 yes ||4 yes ||4 yes ||&nbsp;||&nbsp;||a logic game involving deduction<br />
<br />
|-<br />
<br />
|Develop ||4058 [http://download.sugarlabs.org/activities/4058/]||&nbsp;||&nbsp; ||39 '''no*'''||39 yes||39 yes||&nbsp; ||&nbsp;||open-sugar-apps [http://wiki.laptop.org/go/Develop]'''Develop a new or existing activity''' * fails to start<br />
<br />
|-<br />
<br />
|Distance ||4264 [http://download.sugarlabs.org/activities/4264/] ||22 yes||22 yes||18 yes*||18 yes*||18 yes *||&nbsp;||&nbsp;||worked beween XO-1 and Acer Aspire One [http://wiki.laptop.org/go/Tests/Activity/Distance Distance-tests][http://wiki.laptop.org/go/Acoustic_Tape_Measure Acoustic_Tape_Measure] * starts but needs 2 XO-1 to work<br />
<br />
|-<br />
<br />
|Domino ||4212 [http://download.sugarlabs.org/activities/42127/]||&nbsp;||&nbsp; ||8 yes||&nbsp; ||8 yes||&nbsp;||&nbsp; ||game of dominos<br />
<br />
|-<br />
<br />
|DrGeoii||4323 [http://download.sugarlabs.org/activities/4323/][http://download.sugarlabs.org/activities/4323/]||&nbsp;||&nbsp;||1112 yes||&nbsp; ||1112 yes||&nbsp;||&nbsp;||Complex Geometry with Macros [http://wiki.laptop.org/go/DrGeo][http://activities.sugarlabs.org/addon/4323][http://people.ofset.org/hilaire/DrGeoII-10.08.xo] (non standard sugar interface) Use <esc> to get exit drop down<br />
<br />
|-<br />
<br />
|Ecomundo||4213 [http://download.sugarlabs.org/activities/4213/]||&nbsp;||&nbsp; ||2 yes||&nbsp; ||2 yes||&nbsp;||&nbsp;||rabbits vs fox game<br />
<br />
|-<br />
<br />
|Edit||&nbsp;||&nbsp; ||&nbsp; ||8 yes||&nbsp; ||8 yes||&nbsp; ||&nbsp; ||text editor [http://activities.sugarlabs.org/downloads/file/27083/edit-6.xo 27083]<br />
<br />
|-<br />
<br />
|End Game ||4565 [http://download.sugarlabs.org/activities/4565/]||&nbsp; ||&nbsp; ||yes 28||&nbsp; ||28 yes ||&nbsp; ||&nbsp; ||chess- unable to figure out actions<br />
<br />
<br />
|-<br />
<br />
|Etoys ||4030 [http://download.sugarlabs.org/activities/4030/] ||113 yes||113 yes||116 yes||116 yes||116 yes;113 '''no''' ||&nbsp;||&nbsp;||[http://wiki.laptop.org/go/Tests/Activity/eToys eToys][http://wiki.laptop.org/go/Etoys Etoys]<br />
<br />
|-<br />
<br />
|Finance||4040 [http://download.sugarlabs.org/activities/4040/]||3 yes||&nbsp;||3 yes||&nbsp;||3 yes||&nbsp;||&nbsp; ||Double Entry accounting<br />
<br />
|-<br />
<br />
|Firefox||4262 [http://download.sugarlabs.org/activities/4262/] ||yes 6||yes 6||yes 6||yes||6 yes||&nbsp; ||&nbsp; ||Does not access sugar-journal shows:"failed to load" pop up message after exit, but '''works well''' [http://wiki.laptop.org/go/Firefox] Download: [http://people.sugarlabs.org/Tgillard/firefox-6.xo firefox-6.xo]<br />
<br />
|-<br />
<br />
|Flip ||4518 [http://download.sugarlabs.org/activities/4518/]||&nbsp; ||&nbsp; ||yes 2||&nbsp; ||2 yes||&nbsp; ||&nbsp; ||game of dots<br />
<br />
|-<br />
<br />
|Flipsticks||4044 [http://download.sugarlabs.org/activities/4044/]||&nbsp;||8 yes||7 yes||8 yes||7 yes ||&nbsp;||&nbsp;||animation game;stick figures [http://wiki.laptop.org/go/Flipsticks] [http://activities.sugarlabs.org/addon/4044 4044]<br />
<br />
|-<br />
<br />
|follow_me||4354 [http://download.sugarlabs.org/activities/4354/] ||&nbsp; ||&nbsp; ||14 yes ||&nbsp; ||14 yes ||&nbsp; ||&nbsp; ||A simple little game which requires good concentration.[http://activities.sugarlabs.org/downloads/file/27090/follow_me-3.xo follow_me-3][http://activities.sugarlabs.org/addon/4354 4354] <br />
Pupils are presented with an ever increasing sequence of pictures which they have to imitate.<br />
The Best Score is 'remembered' so the game provides a continual challenge to improve. My best is 40.<br />
<br />
|-<br />
<br />
|Foodforce ||4206 [http://download.sugarlabs.org/activities/4026/]||&nbsp;||&nbsp; ||3 '''no'''* ||&nbsp; ||2-5 yes||&nbsp;||&nbsp;||learn about world hunger in interactive training [http://wiki.laptop.org/go/Food_Force_2]*crashes on start new game plays nice sound track<br />
<br />
<br />
|-<br />
<br />
|FotoToon ||&nbsp;||7 yes||6 yes||5 yes||&nbsp; ||5 yes ||&nbsp; ||&nbsp; ||Add images and notes to circles on screen<br />
<br />
|-<br />
<br />
|freecell||&nbsp;||&nbsp;||&nbsp; ||3 yes||3 yes||3 yes||&nbsp;||&nbsp; ||Card Game <br />
<br />
|-<br />
<br />
|Free From Malaria ||4309 [http://download.sugarlabs.org/activities/4309/]||&nbsp; ||&nbsp;||yes 4 ||&nbsp; ||4 yes ||&nbsp; ||&nbsp; ||need to click license screen to start- (OK) Series of colored drawings showing mosquitos-starts NO SOUND<br />
<br />
|-<br />
<br />
|Gcompris_admin||&nbsp;||&nbsp;||&nbsp; ||15 '''no''||yes||15 '''no'''*||&nbsp;||&nbsp; ||Teachers Admin of Gcompris-15 - Gcompris_administration-15.xo *Could not find the board menu or plug in execution error<br />
<br />
|-<br />
<br />
|Gcompris||&nbsp;||&nbsp; ||&nbsp;||15 '''no'''*||yes ||15 yes||&nbsp;||&nbsp; ||Package of GCompris Programs (v9.3) [http://wiki.sugarlabs.org/go/Activities/GCompris GCompris]ASLOxo *failed to start<br />
<br />
|-<br />
<br />
|Get I A Books||4194 [http://download.sugarlabs.org/activities/4194/]||&nbsp;||&nbsp;||5 yes||&nbsp;||5 yes||&nbsp;||&nbsp; || import as: Deja Vu PDF -(B/W-Color) [http://wiki.sugarlabs.org/go/Activities/Get_Internet_Archive_Books Get_Internet_Archive_Books]<br />
<br />
|-<br />
<br />
|Get_books||4304 [http://download.sugarlabs.org/activities/4304/]||7 yes ||5 yes||6 and 5 '''no'''*||&nbsp;||6 '''no'''||&nbsp;||&nbsp; ||pdf/epub *failed to start<br />
<br />
|-<br />
<br />
|HelloWorld ||&nbsp;||2 yes||&nbsp; ||3 yes||&nbsp; ||3 yes ||&nbsp; ||&nbsp; ||simple program to print Hello World! on screen<br />
<br />
|-<br />
<br />
|Help||4051 [http://download.sugarlabs.org/activities/4051/]||12 yes ||&nbsp; ||13 '''no'''*||&nbsp; ||13 '''no'''||&nbsp; ||&nbsp; ||*failed to start<br />
<br />
|-<br />
<br />
|help_arabic ||&nbsp;||&nbsp; ||&nbsp; ||5 '''no''' *||&nbsp; ||5 '''no'''||&nbsp; ||&nbsp; ||*failed to start<br />
<br />
|-<br />
<br />
|Hop-a-round||4209 [http://download.sugarlabs.org/activities/4209/]||&nbsp;||&nbsp; ||&nbsp;||&nbsp; ||&nbsp;|&nbsp; ||&nbsp; ||&nbsp;||grasshopper teaches how to round numbers<br />
<br />
|-<br />
<br />
|Image viewer||4032 [http://download.sugarlabs.org/activities/4032/]||17 yes||17 yes||19 yes||19 yes ||17 yes||&nbsp; ||&nbsp; ||&nbsp;<br />
<br />
|-<br />
<br />
|Implode ||4086 [http://download.sugarlabs.org/activities/4086/]||10 yes||10 yes||10 yes||&nbsp; ||10 yes||&nbsp;||&nbsp;||Delete sets of blocks [http://wiki.laptop.org/go/Implode Implode] [http://wiki.laptop.org/go/Tests/Activity/Implode]<br />
<br />
|-<br />
<br />
|InfoSlicer||4042 [http://download.sugarlabs.org/activities/4042/]||9 yes||&nbsp;||yes 12;||8 yes||12 yes ||&nbsp;||&nbsp; || [http://wiki.sugarlabs.org/go/Activities/InfoSlicer InfoSlicer] 12 does DL "olpc" OK<br />
<br />
|-<br />
<br />
|IRC ||4029 [http://download.sugarlabs.org/activities/4029/]||yes 10 ||9 yes||10 yes||9 yes||10 yes||&nbsp;||&nbsp;||freenode IRC #sugar & #sugar-es (translate en to es)<br />
<br />
|-<br />
<br />
|Jam2Jam||4290 [http://download.sugarlabs.org/activities/4290/]||&nbsp;||&nbsp; ||2-'''no''*||&nbsp; ||2'''no''' ||&nbsp;||&nbsp;||music jam *(crashes)<br />
<br />
|-<br />
<br />
|jamedit ||4519 [http://download.sugarlabs.org/activities/4519/]||&nbsp; ||&nbsp; ||yes 1||&nbsp; ||1 yes ||&nbsp; ||&nbsp; ||nice text writer-(does not save to journal-saves to activity)-does not stop with out save<br />
<br />
|-<br />
<br />
|Jigsaw puzzle||4046 [http://download.sugarlabs.org/activities/4046/]||&nbsp;||&nbsp; ||8 yes||8 yes||8 yes||&nbsp;||&nbsp;||create and play with jigsaw puzzles [http://wiki.laptop.org/go/Jigsaw_Puzzle Jigsaw_Puzzle]<br />
<br />
|-<br />
<br />
|joke_machine||4064 [http://download.sugarlabs.org/activities/4064/]||&nbsp;||&nbsp; ||12 yes ||12 yes||12 yes||&nbsp; ||&nbsp; ||[http://wiki.laptop.org/go/Joke_Machine joke_machine ]<br />
<br />
|-<br />
<br />
|Jukebox||4045 [http://download.sugarlabs.org/activities/4045/]||21 yes||20 yes||23 yes ||&nbsp; ||18 yes ||&nbsp; ||&nbsp; ||starts-no music to test with **Faint sound of record audio on XO-1<br />
<br />
|-<br />
<br />
|Kandid ||4254||&nbsp;||&nbsp; ||9 yes** ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||evolving population of images *very slow load on XO-1 (Too Big) **Introduction - Details... tabs do not work<br />
<br />
|-<br />
<br />
|Labyrinth ||4078||11 yes||11 yes||11 yes||11 yes||&nbsp; ||&nbsp; ||&nbsp; ||join ideas in boxes (outliner)<br />
<br />
|-<br />
<br />
|Library ||&nbsp;||&nbsp; ||&nbsp; ||1 yes||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||journal viewer<br />
<br />
|-<br />
<br />
|Log||4056 ||24 yes||24 yes||26 yes ||26 yes||24 yes ||&nbsp; ||&nbsp; ||[http://wiki.laptop.org/go/Log Log][http://wiki.laptop.org/go/Tests/Activity/Log Log]<br />
<br />
|-<br />
<br />
|Maze ||4071 ||9 yes||9 yes||14 yes||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||navigate a maze with cursor arrows [http://wiki.laptop.org/go/Maze Maze][http://wiki.laptop.org/go/Tests/Activity/Maze]<br />
<br />
|-<br />
<br />
|Map ||4211||&nbsp;||&nbsp; ||9 '''no''' ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||Road maps+satellit Google Maps-searchable [http://wiki.sugarlabs.org/go/Activities/Map][http://wiki.laptop.org/go/Map_(activity)] *failed to start<br />
<br />
|-<br />
<br />
|Mapstats ||4202||&nbsp;||&nbsp; ||1 '''no'''** ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||* number entry field does not always work **failed to start<br />
<br />
<br />
|-<br />
<br />
|Measure ||4197 ||32 yes||32 yes||36 yes ||yes 36 ||&nbsp; ||&nbsp; ||&nbsp; ||sensor controls only appear on OLPC XO hardware [http://wiki.laptop.org/go/Measure][http://activities.sugarlabs.org/downloads/file/27012/measure-32.xo Measure 32] 27796 sees microphone on Acer Aspire ONE N450 in stereo (2 channels)<br />
<br />
|-<br />
<br />
|Memorize ||4063 ||36 yes||36 yes||39 yes||36 yes ||36 yes ||&nbsp; ||&nbsp; ||[http://wiki.laptop.org/go/Memorize] [http://wiki.laptop.org/go/Tests/Activity/Memorize]<br />
<br />
|-<br />
<br />
|Moon ||4034 ||12 yes;||11 yes||13 yes ||11 yes||&nbsp; ||&nbsp; ||&nbsp; ||Moon Map with Information [http://wiki.laptop.org/go/Tests/Activity/Moon] [http://wiki.laptop.org/go/Moon]<br />
<br />
|-<br />
<br />
|Mouse-Cam||4487||&nbsp; ||&nbsp; ||yes 2||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||2 does not change speed of mouse in ACER ASPIRE ONE N450<br />
<br />
|-<br />
<br />
|operjam ||4503;||&nbsp; ||&nbsp; ||yes 1||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||(ok) permission screen - Opera web browser-starts/works<br />
<br />
|-<br />
<br />
|OOo4kids1.0_en-es-fr ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; |&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||full open office suite (NC#702) Spreadsheet opens OOo.odf on 2nd ASLOxo USB and saved it in Activities folder (default) [http://freshmeat.net/projects/ooo4kids]Download: [http://download.ooo4kids.org/en/download-ooo4kids-XO] web:[http://wiki.ooo4kids.org/index.php/Main_Page]<br />
<br />
|-<br />
<br />
|ooo-4kids||&nbsp;||&nbsp; ||&nbsp; ||yes 2 ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||open office port to .xo<br />
<br />
|-<br />
<br />
|Open Video Chat||experimental 4305||&nbsp;||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||includes g-streamer binaries-Open Video Chat is a simple chat activity that allows two participants to communicate over a video chat.<br />
<br />
|-<br />
<br />
|Paint||4082||34.1 yes||31 yes||31 yes ||33 yes||&nbsp; ||&nbsp; ||&nbsp; ||[http://wiki.laptop.org/go/Tests/Activity/Paint Paint] <br />
<br />
|-<br />
<br />
|Panorama ||3524||&nbsp; ||&nbsp; ||yes 2 ? ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||Takes multiple Pictures (ACER ASPIRE ONE N450) does not save but one - runs off screen with multiple pictures<br />
<br />
|-<br />
<br />
|Physics ||4192||8 yes||8 yes||9 yes ||8 yes ||8 yes||&nbsp; ||&nbsp; ||Laws of Physics displayed in Game [http://wiki.laptop.org/go/Physics_(activity)]<br />
<br />
|-<br />
<br />
|Pippy ||4041||40 yes||40 yes||43 yes; '''no 44'''||43 yes||41 yes ||&nbsp; ||&nbsp; || [http://wiki.laptop.org/go/Pippy] [http://wiki.laptop.org/go/Tests/Activity/Pippy] 44-crashes on camera,locks up sugar<br />
<br />
|-<br />
<br />
|PlayGo ||4083||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||[http://wiki.laptop.org/go/PlayGo]<br />
<br />
|-<br />
<br />
|Plot||&nbsp;||&nbsp;||&nbsp; ||3 yes ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||Plot Graphs<br />
<br />
|-<br />
<br />
|pointillism ||4523;||&nbsp; ||&nbsp; ||4 yes ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||points fill in screen<br />
<br />
|-<br />
<br />
|Portfolio||&nbsp;||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||[http://wiki.sugarlabs.org/go/Activities/Portfolio Portfolio][http://wiki.sugarlabs.org/images/3/3f/Portfolio-20.xo Download]<br />
<br />
|-<br />
<br />
|Poll 26||4074||&nbsp;||27 yes||27 yes ||27 yes||&nbsp; ||&nbsp; ||&nbsp; ||MaMaMedia Poll Builder-create a poll [http://wiki.laptop.org/go/Poll_Builder] <br />
<br />
|-<br />
<br />
|Pukllanapac||4320||&nbsp; ||&nbsp; ||8||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||[[Activities/Pukllanapac]] Pukllanapac is a sliding-puzzle game [http://activities.sugarlabs.org/addon/4320] <br />
<br />
|-<br />
<br />
|Read||4028 ||90 yes||86 yes||no 94||92 yes||no||&nbsp; ||&nbsp; ||http://wiki.laptop.org/go/Tests/Activity/Read] bug: http://bugs.sugarlabs.org/ticket/1900* [http://activities.sugarlabs.org/en-US/sugar/addon/4028]*sugar-read-79-1.fc14.noarch requires gnome-python2-evince 94-failed to start<br />
<br />
|-<br />
<br />
|Read SD Comics||4340||&nbsp; ||&nbsp; ||2 yes ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||file manager-looks for comics on USB/SD [http://activities.sugarlabs.org/addon/4340 4340]<br />
<br />
|-<br />
<br />
|Read ETexts||4034||&nbsp; ||&nbsp; ||23 yes ||22 yes ||&nbsp; ||&nbsp; ||&nbsp; ||zip fle downloads e-books<br />
<br />
|-<br />
<br />
|Record ||&nbsp;||92.1 yes||87 yes||93 yes ||79 yes||93 yes ||&nbsp; ||&nbsp; ||[http://activities.sugarlabs.org/downloads/file/27004/record-86.xo record-86][http://wiki.laptop.org/go/Tests/Activity/Record][http://wiki.laptop.org/go/Record] <br />
<br />
|-<br />
<br />
|Reflection ||4517||&nbsp; ||&nbsp; ||yes 3 ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp;<br />
<br />
|-<br />
<br />
|Restore 3 ||4327||&nbsp;||yes |3 yes ||yes ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||Activity to restore the Journal content from Journal entry bundles (JEBs) like those written by the Backup activity.[http://activities.sugarlabs.org/en-US/sugar/addon/4327]<br />
<br />
Supports any data store from 0.84 on, including those with version support. You can use Backup to dump the contents of one data store and use Restore to import them into any other data store.<br />
Only entries older than what's in the backup will be overwritten, so it's safe to run it multiple times and even import backups from other (non-malicious) users.<br />
<br />
|-<br />
<br />
|Roots ||4521||&nbsp; ||&nbsp; ||yes 1||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||Genealogy activity<br />
<br />
|-<br />
<br />
|Ruler ||4192 ||8 yes||7 yes||13 yes ||&nbsp; ||&nbsp; ||&nbsp; || |&nbsp;||[http://wiki.laptop.org/go/Tests/Activity/Ruler Ruler Tests]display ruler scales [http://wiki.laptop.org/go/Ruler Ruler] <br />
<br />
|-<br />
<br />
|Scratch||4029 ||19 yes;||19 yes ||19 yes* ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||[http://wiki.laptop.org/go/Scratch][http://wiki.laptop.org/go/Tests/Activity/Scratch Scratch] *slow start<br />
<br />
|-<br />
<br />
|Slide rule ||4222||&nbsp; ||&nbsp; ||24 yes ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||learn to use slide rule. How to Use: [http://wiki.sugarlabs.org/go/Activities/Sliderule]<br />
<br />
|-<br />
<br />
|Slider Puzzle||4047||&nbsp;||&nbsp; ||8 yes ||8 yes ||&nbsp; ||&nbsp; ||&nbsp; ||MaMaMedia Slider Puzzle (Slide blocks to make picture) [http://wiki.laptop.org/go/Slider_Puzzle]<br />
<br />
|-<br />
<br />
|Socialcalc||4084||&nbsp;||&nbsp; ||5 '''no''*||&nbsp; ||&nbsp; ||&nbsp; || ||nice spreadsheet-slow start **only partial opening no spreadsheet(XO-1) [http://wiki.laptop.org/go/SocialCalc] *failed to start<br />
<br />
|-<br />
<br />
|Speak||4038 ||25 yes||20 yes||34 yes; yes 35 ||25 yes ||29 yes||&nbsp; ||&nbsp; ||[http://wiki.laptop.org/go/Speak] [http://wiki.laptop.org/go/Tests/Activity/Speak]<br />
<br />
|-<br />
<br />
|Spirolaterals||4331 ||&nbsp; ||20 yes ||yes 23 ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp;||Maze Game -2 [http://activities.sugarlabs.org/addon/4331 4331]<br />
<br />
|-<br />
<br />
|StarChart||4300||&nbsp; ||&nbsp; ||12 yes||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||V2.0 build 115 map of the sky showing the position of the visible stars, some of the larger and brighter deep-sky objects (DSOs), the "classical" planets, the sun and the moon. [http://wiki.laptop.org/go/StarChart]<br />
<br />
|-<br />
<br />
|stopwatch||4263||9 yes||8 yes ||5 yes ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||stop watches to start and stop [http://wiki.laptop.org/go/Stopwatch] <br />
<br />
|-<br />
<br />
|Story Builder||4073||&nbsp;||&nbsp; ||16 and 15 '''no'''*||16 yes||&nbsp; ||&nbsp; ||&nbsp; ||MaMaMedia Story Builder *quits to journal<br />
<br />
|-<br />
<br />
|Sugar_commander ||4291||&nbsp;||yes 8||8 yes||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||views of files and journal<br />
<br />
|-<br />
<br />
|Surf 115||&nbsp;||&nbsp;||no||115 yes||115 yes||115 yes ||&nbsp; ||&nbsp; ||Download [http://people.sugarlabs.org/Tgillard/Surf-115.xo Surf-115.xo][http://dev.laptop.org/~bobbyp/surf/Surf-106.xo] [http://www.olpcnews.com/forum/index.php?topic=4512.msg31246]<br />
<br />
|-<br />
<br />
|Tam Tam Edit ||4059 ||55 yes||&nbsp; ||yes 62 ||55 yes ||&nbsp; ||&nbsp; ||&nbsp; ||plays music *(EeePC900 stutters sound) [http://wiki.laptop.org/go/Tests/Activity/TamTamEdit] 62 sound<br />
<br />
|-<br />
<br />
|tam Tam Mini||4061||58 yes||53 yes||yes* 62 ||58 yes||&nbsp; ||&nbsp; ||&nbsp; ||plays music [http://wiki.laptop.org/go/Tests/Activity/TamTamMini]*62 no sound<br />
<br />
|-<br />
<br />
|tam Tam Synth Lab ||4062 ||55 yes|| &nbsp; ||54 yes*||55 yes* |&nbsp; ||&nbsp; ||&nbsp;||&nbsp; ||*can not test starts fine [http://wiki.laptop.org/go/Tests/Activity/TamTamSynth]<br />
<br />
|-<br />
<br />
|Tam Tam Jam ||4060||56 yes ||&nbsp; ||55 yes* ||56 yes||&nbsp; ||&nbsp; ||&nbsp; ||* no sound [http://wiki.laptop.org/go/Tests/Activity/TamTamJam] &=no playback*=sugar-tamtam-common-0-0.5.20100201git.fc14.i686 requires python(abi) = 0:2.6<br />
<br />
|-<br />
<br />
|Terminal||4204]||31 yes||31 yes ||35 yes ||34 yes ||34 yes ||&nbsp; ||&nbsp; ||[http://activities.sugarlabs.org/en-US/sugar/addon/4204][http://wiki.laptop.org/go/Tests/Activity/Terminal][http://wiki.laptop.org/go/Terminal]<br />
<br />
|-<br />
<br />
|Tetris Mat ||&nbsp;||&nbsp; ||1 yes||1 yes* ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||*to large for 10"netbook screen<br />
<br />
|-<br />
<br />
|totem ||&nbsp;||&nbsp; ||&nbsp; || 2'''no'''* ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||* fails to start<br />
<br />
|-<br />
<br />
|Turtle-art||4298 ||107 yes||106 yes ||120 yes; yes130||120 yes ||114 yes ||&nbsp; ||&nbsp; ||Mini branch of Turtle Art [http://wiki.laptop.org/go/Turtle_Art] [http://wiki.laptop.org/go/Tests/Activity/TurtleArt]<br />
<br />
|-<br />
<br />
|Turtle-blocks||4027||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||Mainline branch of Turtle Art 27795-not on ASLOxo<br />
<br />
|-<br />
<br />
|Turtle in a Pond ||4516||&nbsp; ||&nbsp; ||yes 6; yes 4; yes 3||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||like simple GO program<br />
<br />
|-<br />
<br />
|Turtle Machine||&nbsp;||&nbsp; ||11 yes||11 yes ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp;<br />
<br />
|-<br />
<br />
|Tux-paint||4088||&nbsp; ||&nbsp; ||6 yes ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp;<br />
<br />
|-<br />
<br />
|Typing Turtle ||4203||27 yes||26 yes ||28 yes ||27 yes||&nbsp; ||&nbsp; ||&nbsp; ||Typing Training w/Keyboard<br />
<br />
|-<br />
<br />
|View slides ||4039||&nbsp;||&nbsp; ||12 yes||13 yes||&nbsp; ||&nbsp; ||&nbsp; || view pictures - sees photos taken by record<br />
<br />
|-<br />
<br />
|Visual match||4246||&nbsp; ||28 yes||30 yes;yes 34||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp;<br />
<br />
|-<br />
<br />
|VncLauncher ||&nbsp;||&nbsp;||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||finds IP; cannot test [http://wiki.laptop.org/go/VNC_Launcher]<br />
<br />
|-<br />
<br />
|Weigh -23 ||4525||&nbsp; ||&nbsp;||yes 23?||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||27812 Needs (help); I cannot figure out how to change tare weights<br />
<br />
|-<br />
<br />
|Wikipedia-en||&nbsp; ||26 yes||&nbsp; ||10 '''no'''*||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||* failed to start ACER ASPIRE ONE N450<br />
|-<br />
<br />
|Wikipedia-es||&nbsp;||26 yes||&nbsp; ||no* 33||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||*failed to start ACER ASPIRE ONE N450<br />
<br />
|-<br />
<br />
|WirelessGraph ||4301||&nbsp; ||&nbsp; ||7 yes ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||wireless link quality<br />
<br />
|-<br />
<br />
|Write||4021||75 yes||70 yes ||77 yes ||77 yes ||76 yes ||&nbsp; ||&nbsp;|| [http://wiki.laptop.org/go/Tests/Activity/Write]<br />
<br />
|-<br />
<br />
|Words||4315||4 yes||7 yes||yes ||yes ||&nbsp; ||&nbsp; ||&nbsp; ||Translate words English to French/German/Italian/Portuguese/Spanish + Speaks word [http://activities.sugarlabs.org/en-US/sugar/addon/4315][http://wiki.laptop.org/go/Words] <br />
<br />
|-<br />
<br />
|Xaos||4299||&nbsp; ||yes ||no ||no ||&nbsp; ||&nbsp; ||&nbsp; ||fractal editor [http://wiki.laptop.org/go/XaoS]<br />
<br />
|-<br />
<br />
|Xoeditor||4085||&nbsp;||yes||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; || Change colors of XO Avitar - cannot save results<br />
<br />
|-<br />
<br />
|XoPhoto ||&nbsp;||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||[http://wiki.laptop.org/go/Xophoto][http://wiki.laptop.org/go/File:XoPhoto-7.xo]<br />
<br />
|-<br />
<br />
|x2o ||4223 ||&nbsp;||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||Game move objects against ramps [http://wiki.laptop.org/go/Tests/Activity/x2o]<br />
<br />
|-<br />
<br />
|Yum Downloader ||4501 ||&nbsp; ||&nbsp; ||'''no''' 3* ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||*fails to find rpm closes<br />
<br />
|-<br />
<br />
|&ndash; ||&nbsp;||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp;<br />
<br />
|-<br />
<br />
|&ndash; ||&nbsp;||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp;<br />
<br />
|-<br />
<br />
|&ndash; ||&nbsp;||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp;<br />
<br />
|-<br />
<br />
|&ndash; ||&nbsp;||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp;<br />
<br />
|-<br />
<br />
|&ndash; ||&nbsp;||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp;<br />
<br />
|-<br />
<br />
|&ndash; ||&nbsp;||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp; ||&nbsp;<br />
<br />
|}</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Dextrose&diff=71403Dextrose2011-11-18T06:22:15Z<p>Skierpage: /* Dextrose 2 - World Edition */ fix link</p>
<hr />
<div>__NOTOC__<br />
<br />
[[File:Dextrose-2-intl-logo.png|600px]] [[File:Dextrose-mascotte-120x96.png]]<br />
<noinclude>{{TeamHeader|Dextrose|home=Dextrose|xbgColor=ffe792|join_label=Get Involved}}[[Category:Project]]</noinclude><br />
<br />
[[Image:Dextrose_main.png|640px|frameless|right]]<br />
<br />
== The deployments' XO Operating System ==<br />
<br />
Dextrose is a Sugar distribution for XO laptops jointly developed by [http://activitycentral.org Activity Central], [http://paraguayeduca.org/ Paraguay Educa], [http://www.ceibal.edu.uy/ Plan Ceibal] in collaboration with OLPC and the Sugar community.<br />
<br />
Our focus is stability and usability in the classroom, but we've also merged some<br />
new features contributed by deployments and freelance contributors.<br />
<br />
== New features in Dextrose2 ==<br />
<br />
* Backport of [[0.88/Notes|Sugar 0.88]] ([[User:Bernie|Bernie Innocenti]])<br />
* [[Features/Journal_Sort|Journal sorting options]] ([[User:Aa|Andrés Ambrois]])<br />
* [[:File:Dextrose_resource_monitoring.png|Intuitive resource monitoring]] ([[User:M_anish|Anish Mangal]])<br />
* [[Features/Backup_and_Restore|Journal Backup/restore to removable devices]] ([[User:tch|Martin Abente]], [[User:Earias|Esteban Arias]])<br />
* [[Features/Backup_and_Restore|Journal Backup/restore to schoolserver]] ([[User:tch|Martin Abente]])<br />
* Protected activities support ([[User:tch | Martin Abente]])<br />
* Improved GSM/3G handling ([[User:Dcastelo|Daniel Castelo]], [[User:tch|Martin Abente]])<br />
* [[:File:Dextrose_tabbed_browsing.png|Tabbed browsing]] ([[User:M_anish|Anish Mangal]])<br />
* [[:File:Dextrose_teclado_virtual.png|Virtual keyboard]] ([[User:Earias|Esteban Arias]])<br />
* [[:File:Accessibility_control_panel_2.png|Accessibility features]] ([[User:Earias|Esteban Arias]])<br />
* [[:File:Dextrose_journal_repair.png|Journal repair functionality]] ([[User:Earias|Esteban Arias]])<br />
* [[Features/Touchpad_control_panel_section|Fast switching between touchpad and pen-tablet modes]] ([[User:Walter|Walter Bender]])<br />
* OLPC Microformat support in activity updater (Akash Gangil, [[User:M_anish|Anish Mangal]])<br />
* [[Features/Sugar_Adhoc_Networks|Ad-hoc Networks]] ([[User:Erikos|Simon Schampijer]])<br />
* Ability to reissue registration to schoolserver ([[User:tch|Martin Abente]])<br />
* [http://download.sugarlabs.org/dextrose/testing/dxo2/rpms-freeworld/ freeworld codecs] for most multimedia formats, including MP3 music and H264 videos ([[User:Bernie|Bernie Innocenti]])<br />
* [http://codewiz.org/wiki/pictures/sugar/deployment/paraguay/caacupe/escuela_485_daniel_ortellado/dextrose-testing Extensive field testing] ([[User:Bernie|Bernie Innocenti]])<br />
* Lease information display in Control Panel->About My Computer()<br />
* Automatic crashlog reporting and manual feedback reporting, with server side daemon ([[User:Alsroot|Aleksey Lim]], [[User:tch|Martin Abente]], Mukesh Gupta)<br />
* Notification system ([[User:tch|Martin Abente]])<br />
* Automatic yum based updater ([[User:tch|Martin Abente]], [[User:Alsroot|Aleksey Lim]], [[User:M_anish|Anish Mangal]])<br />
* Nearly complete Spanish Translations ([[User:tch|Martin Abente]], Sebastian Codas:scs, Carlos Garay:car|0s)<br />
* One Click Share 3G ([[User:tch|Martin Abente]])<br />
<br />
== Dextrose 2 - World Edition ==<br />
<br />
[[File:Download-dextrose-py.png]]<br />
<br />
'''This is a release build''' targeted for use by multiple deployments worldwide. We do appreciate feedback and bug reports.<br />
<br />
{| class="wikitable"<br />
! Hardware<br />
! OS Images<br />
! Size<br />
! Date<br />
|-<br />
| [[File:Xo-1.png]] XO-1, without GNOME<br />
| [http://download.sugarlabs.org/dextrose/testing/dxo2/xo1/intl/os508dx.img os508dx.img] <br />
[http://download.sugarlabs.org/dextrose/testing/dxo2/xo1/intl/os508dx.crc os508dx.crc]<br />
| 411MB<br />
| Apr 1 2011<br />
|-<br />
| [[File:Xo-1.5.png]] XO-1.5, without GNOME<br />
| [http://download.sugarlabs.org/dextrose/testing/dxo2/xo1.5/intl/os508dx.zd os508dx.zd]<br />
| 339MB<br />
| Apr 1 2011<br />
|}<br />
<br />
GNOME builds are currently unsupported. If you require GNOME for evaluation purposes in your deployment, please ask on the [http://lists.sugarlabs.org/listinfo/dextrose Dextrose mailing-list]. For more details on this release, see the [[Dextrose/2|Dextrose 2]] pages: [[Dextrose/2/Changelog|Change Log]], [[Dextrose/2/Todo|Todo List]].<br />
<br />
[[Dextrose/3|Development releases]] | [[Dextrose/Resources|Older releases]]<br />
<br />
== Knowing your way around the new features ==<br />
<br />
* [http://people.sugarlabs.org/anish/3g_configuration.pdf 3G Modem configuration]<br />
* [http://people.sugarlabs.org/anish/3g_sharing.pdf 3G Connection sharing]<br />
* [http://people.sugarlabs.org/anish/feedback.pdf Manual feedback submission]<br />
* [http://people.sugarlabs.org/anish/resources.pdf Understanding the resources icon and lease information]<br />
<br />
== Installation ==<br />
<br />
=== XO-1 ===<br />
<br />
[[File:Xo-1.png|right]]<br />
[[File:XO-XP.png|right]]<br />
<br />
* First, ensure that your laptop is [http://wiki.laptop.org/go/Activation_and_developer_keys unlocked].<br />
* Download both <tt>'''osXXXXX.img'''</tt> and <tt>'''osXXXXX.crc'''</tt> to the root directory of a USB stick or SD card.<br />
* Drop to the "'''ok'''" prompt by pressing [[File:Esc.svg|24px]] (Esc) repeatedly during boot<br />
* Type the command: {{Code|'''copy-nand u:\osNdx.img'''}} for a USB stick or {{Code|'''copy-nand sd:\osNdx.img'''}} for a SD card followed by [[File:Key_enter.jpg|50px]] (enter)<br />
* Wait for the display to fill in with color and the "'''ok'''" prompt to return<br />
* Type the command {{Code|'''reboot'''}} followed by [[File:Key_enter.jpg|50px]] (enter)<br />
* The XO will reboot, finish writing, reboot itself, and take you to the naming and color choice process<br />
* During the reboots, keep the charger connected to allow OFW to self-update<br />
<br />
'''See also''' the [http://wiki.sugarlabs.org/go/Talk:Downloads#Upgrade_an_XO-1_to_Sugar_0.84_with_Fedora_11_and_Gnome detailed instructions].<br />
<br />
=== XO-1.5 ===<br />
<br />
[[File:Xo-1.5.png|right]]<br />
[[File:XO-HS.png|right]]<br />
<br />
* First, ensure that your laptop is [http://wiki.laptop.org/go/Activation_and_developer_keys unlocked].<br />
* Download <tt>'''osXXXXX.zd'''</tt> to the root directory of a USB stick<br />
* Drop to the "'''ok'''" prompt by pressing [[File:Esc.svg|24px]] (Esc) repeatedly during boot<br />
* Type the command: {{Code|'''fs-update u:\osXXXXX.zd'''}} followed by [[File:Key_enter.jpg|50px]] (enter)<br />
* Wait for the display to fill in with color and the "'''ok'''" prompt to return<br />
* Type the command {{Code|'''reboot'''}} followed by [[File:Key_enter.jpg|50px]] (enter)<br />
* The XO will reboot and take you to the naming and color choice process<br />
<br />
'''See also''' the [http://wiki.laptop.org/go/F11_for_1.5 detailed instructions].<br />
<br />
=== XO-1.75 ===<br />
<br />
The XO-1.75 is not supported at this time. Please [[Dextrose/Contacts|contact us]] if you are planning to deploy Dextrose on XO-1.75.<br />
<br />
=== Other netbooks ===<br />
<br />
Please [[Dextrose/Contacts|contact us]] if you need support for running Dextrose on non-XO hardware.<br />
<br />
<br />
== Using Dextrose in your deployment ==<br />
<br />
We're happy to help other deployments produce their own OS images independently of us,<br />
thus exploiting the [http://www.gnu.org/philosophy/free-sw.html Freedom #1] provided by Free Software.<br />
<br />
=== Subpages ===<br />
{{Special:PrefixIndex/{{PAGENAME}}/}}</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Features/GTK3/Porting&diff=71402Features/GTK3/Porting2011-11-18T06:20:45Z<p>Skierpage: Category:Developer</p>
<hr />
<div>=Porting an existing activity to GTK3=<br />
This is a guide to porting an existing activity from GTK2 to [http://developer.gnome.org/gtk3/stable/ GTK3]. It also shows the changes to use the new Sugar toolkit that also now uses [[Features/GTK3|GTK3]]. This guide uses the [http://git.sugarlabs.org/hello-world hello-world] activity as a simple example.<br />
<br />
==Preparation==<br />
Before you start porting your activity you are encouraged to branch off a stable branch. This will allow you to keep on doing stable releases on the stable branch and new releases on the master branch.<br />
<br />
The latest release was version 3. We highly recommend that you use the 'sugar-0.94' as the stable branch name because this will keep the repositories consistent and eases the development work. In git you can create a branch like this:<br />
git branch sugar-0.94<br />
<br />
This creates a local branch, as you can see by running 'git branch'; you should see the following:<br />
<br />
<pre><br />
[erikos@T61 helloworld]$ git branch<br />
* master<br />
sugar-0.94<br />
</pre><br />
<br />
The 'sugar-0.94' branch is only available locally, as you can see by running 'git branch -r' which shows the remote branches:<br />
<br />
<pre><br />
[erikos@T61 helloworld]$ git branch -r<br />
origin/HEAD -> origin/master<br />
origin/master<br />
origin/sucrose-0.84<br />
</pre><br />
<br />
The only branch available besides the master branch is the 'sucrose-0.84' branch. Let's push now our new branch to the remote repository to make it available for others:<br />
<pre><br />
git push origin sugar-0.94<br />
</pre><br />
<br />
The branch is now listed as a remote branch. You can verify as well on your [http://git.sugarlabs.org/hello-world/mainline gitorious page].<br />
<pre><br />
[erikos@T61 helloworld]$ git branch -r<br />
origin/HEAD -> origin/master<br />
origin/master<br />
origin/sucrose-0.84<br />
origin/sugar-0.94<br />
</pre><br />
<br />
You can switch now between those branches using 'git checkout <branch>'. And you can use 'git branch' to see which branch you are on (the one with the * before is the branch you are currently on).<br />
<pre><br />
git checkout sugar-0.94<br />
git checkout master<br />
</pre><br />
<br />
==Cleanup, adopt to API changes in the sugar-toolkit==<br />
''This should be done only on the master branch''! In the new sugar-toolkit we have removed old API, you should adjust your activity accordingly:<br />
* the keep button has been removed completely<br />
* the old-style toolbar has been removed<br />
<br />
==Port the activity from GTK2 to GTK3==<br />
To start, change the importing instruction for GTK from<br />
import gtk<br />
to<br />
from gi.repository import Gtk<br />
Then you have to change each call that involves Gtk, for example creating a button will look now like this:<br />
button = Gtk.Button()<br />
<br />
A simple hello world program in GTK3 looks like this:<br />
<pre><br />
from gi.repository import Gtk<br />
<br />
def _destroy_cb(widget, data=None):<br />
Gtk.main_quit()<br />
<br />
w = Gtk.Window()<br />
w.connect("destroy", _destroy_cb)<br />
label = Gtk.Label('Hello World!')<br />
w.add(label)<br />
w.show_all()<br />
<br />
Gtk.main()<br />
</pre><br />
<br />
For porting your activity you do have to change your calls for accessing widgets and services in the new GTK3 sugar-toolkit as well. The new namespace is called sugar3, trying to reflect that GTK3 is the underlying technology. For example the import of the base activity class has to be changed from<br />
from sugar.activity import activity<br />
to<br />
from sugar3.activity import activity<br />
<br />
The changes that were needed to port the hello-world activity can be seen in [http://git.sugarlabs.org/hello-world/mainline/commit/508e1c518b56cbde5508e560c8a2ff38a3518583 this commit].<br />
<br />
Ok, let's do these changes now for your activity. Make sure you are in your master branch using the 'git branch' command (the master branch should have a '*' before it). Make your changes, commit them ('git commit -a') and push them to the remote repository ('git push origin master').<br />
<br />
===Tools===<br />
There are tools to help you do the porting. There is a script in the pygobject repository for porting called [http://git.gnome.org/browse/pygobject/tree/pygi-convert.sh pygi-convert.sh], more info about the script can be found in [http://live.gnome.org/PyGObject/IntrospectionPorting the PyGObject Introspection Porting guide]. <br />
<br />
If you are having trouble finding how a particular GTK class/method/constant has been named in PyGI, run [http://dev.laptop.org/~dsd/20110806/pygi-enumerate.py pygi-enumerate.py] and grep the output. (this app lists all identified methods and constants).<br />
<br />
<br />
=== Constructor considerations ===<br />
<br />
With PyGI it is possible to use Python-like constructors, or "new" functions e.g. the following are (usually) equivalent:<br />
label = Gtk.Button()<br />
label = Gtk.Button.new()<br />
<br />
However, the first form is preferred: it is more Python-like. Internally, the difference is that Gtk.Label.new() translates to a call to gtk_label_new(), whereas Gtk.Label() (the preferred form) will directly construct an instance of GtkLabel at the GObject level.<br />
<br />
If the constructor takes parameters, they '''must''' be named. The parameters correspond to GObject properties in the API documentation which are usually marked as "Construct". For example, the following code will not work:<br />
<br />
expander = Gtk.Expander("my expander")<br />
<br />
The (confusing) error is:<br />
TypeError: GObject.__init__() takes exactly 0 arguments (1 given)<br />
<br />
The solution is to go to the [http://developer.gnome.org/gtk3/3.2/GtkExpander.html#GtkExpander.properties GtkExpander API documentation] and find the appropriate property that we wish to set. In this case it is <b>label</b> (which is a Construct property, further increasing our confidence of success), so the code should be:<br />
<br />
expander = Gtk.Expander(label="my expander")<br />
<br />
Combining the two points above, if you wish to call a construct-like function such as gtk_button_new_with_label(), you do have the option of calling Gtk.Button.new_with_label(), however if we check the [http://developer.gnome.org/gtk3/3.2/GtkButton.html#GtkButton.properties GtkButton properties] we see one called "label" which is equivalent. Therefore gtk_button_new_with_label("foo") should be called as:<br />
button = Gtk.Button(label="foo")<br />
<br />
=== HBox, VBox, pack_start and pack_end ===<br />
<br />
GtkHBox and GtkVBox, commonly used containers in GTK2 code, have pack_start and pack_end methods. These take 4 parameters:<br />
# The widget to pack into the container<br />
# '''expand''': Whether the child should receive extra space when the container grows (default True)<br />
# '''fill''': True if space given to child by the expand option is actually allocated to child, rather than just padding it. This parameter has no effect if expand is set to False. A child is always allocated the full height of a gtk.HBox and the full width of a gtk.VBox. This option affects the other dimension. (default True)<br />
# '''padding''': extra space in pixels to put between child and its neighbor (default 0)<br />
<br />
In PyGTK, the expand, fill and padding parameters were optional: if unspecified, the default values above were used. In PyGI, these parameters are '''not''' optional: all 4 must be specified. Hence the rules for adding in the extra parameters are:<br />
<br />
# If '''expand''' was not set, use value True<br />
# If '''fill''' was not set, use value True. (however, if expand is False, this parameter gets ignored so False is an equally acceptable option when expand=False)<br />
# If padding was not set, use value 0.<br />
<br />
These parameters can be specified either as positional arguments or as named keyword arguments, however all 4 must always be specified. Some developers prefer keyword arguments, arguing that the following:<br />
<pre>box.pack_start(widget, expand=True, fill=False, padding=4)</pre><br />
is much more readable than:<br />
<pre>box.pack_start(widget, True, False, 4)</pre><br />
<br />
However, these functions are called extremely often; any mildly seasoned GTK developer will have memorized the order and meaning of the parameters. Some developers therefore prefer to avoid the extra work of dropping in hundreds of keyword arguments throughout the code and just use the positional ones. This is really up to you.<br />
<br />
If you are using pack_start with the default values (expand=True, fill=True and padding=0), you can avoid using pack_start (and the parameter pain that it brings with it) by just using .add for some added cleanliness, e.g.<br />
<pre>box.pack_start(widget, True, True, 0)</pre><br />
can be replaced with:<br />
<pre>box.add(widget)</pre><br />
<br />
This is as far as you need to go for now. However, in GTK3, GtkVBox and GtkHBox have been deprecated, which means they might be removed in GTK4. The replacement is to use GtkBox directly, and you may wish to make this change now. e.g.:<br />
<pre>vbox = Gtk.Box(orientation=Gtk.Orientation.VERTICAL)</pre><br />
<br />
However, it must be noted that if GtkBox is used directly (instead of using GtkHBox/GtkVBox), the default value of '''expand''' is now '''False'''. The implications of this are:<br />
# You need to check your .add() calls, as previously they would behave as pack_start with expand=True, but now they will behave as expand=False (you need to change them to use pack_start with expand=True to retain the old behaviour)<br />
# Every single pack_start call that has expand=False and padding=0 (and any value of fill) can be converted to .add() for cleanliness<br />
<br />
=== GtkAlignment considerations ===<br />
<br />
In PyGTK, the gtk.Alignment constructor takes four optional parameters:<br />
# xalign: the fraction of horizontal free space to the left of the child widget. Ranges from 0.0 to 1.0. Default value 0.0.<br />
# yalign: the fraction of vertical free space above the child widget. Ranges from 0.0 to 1.0. Default value 0.0.<br />
# xscale: the fraction of horizontal free space that the child widget absorbs, from 0.0 to 1.0. Default value 0.0.<br />
# yscale: the fraction of vertical free space that the child widget absorbs, from 0.0 to 1.0. Default value 0.0<br />
<br />
In PyGI/GTK3, these parameters are still optional when used in the Gtk.Alignment constructor (as keyword arguments, as explained above). However, the default values have changed. They are now:<br />
# xalign: default value 0.5<br />
# yalign: default value 0.5<br />
# xscale: default value 1<br />
# yscale: default value 1<br />
<br />
If your code was relying on the default value of 0 for any of these parameters in PyGTK, you will now need to explicitly specify that in your constructor. Similarly, if you were previously using construction parameters to select the now-default values, those parameters can be dropped.<br />
<br />
Additionally, PyGTK accepted these construction parameters as positional arguments. As explained above, they must now be converted to keyword arguments.<br />
<br />
==Make a release==<br />
===Versioning===<br />
If you do new releases the versioning of the GTK2 and GTK3 release should be different. For GTK2 releases you should use dotted versions for new development releases major versions. Let's have a look at hello-world as an example. The latest release of hello-world was version 3. Bug fix releases should be named 3.1 then 3.2 and so on. The new releases for the new development branch should be starting with a major number, in this case 4.<br />
<br />
== Tips to Activity Developers ==<br />
<br />
===Going from Drawable to Cairo===<br />
<br />
GTK-3 does not support gtk Drawable objects, so the first step is to get your activity running under Cairo.<br />
<br />
<pre><br />
import cairo<br />
<br />
# From activity.Activity, you inherit a canvas.<br />
# Create a Cairo context from the window.<br />
cairo_context = self.canvas.get_window().cairo_create()<br />
<br />
# Create an XLib surface to be used for drawing<br />
xlib_surface = surface.create_similar(cairo.CONTENT_COLOR,<br />
gtk.gdk.screen_width(),<br />
gtk.gdk.screen_height())<br />
<br />
# You'll need a Cairo context from which you'll build a GTK Cairo context<br />
cairo_context = cairo.Context(xlib_surface)<br />
cairo_context = gtk.gdk.CairoContext(cairo_context)<br />
<br />
# Use this context as you would a Drawable, substituting Cairo commands<br />
# for gtk commands, e.g.,<br />
cairo_context.move_to(0, 0)<br />
cairo_context.line_to(100, 100)<br />
# Cairo uses floats from 0 to 1 for RGB values<br />
cairo_context.set_source_rgb(r, g, b)<br />
cairo_context.rectangle(x, y, w, h)<br />
cairo_context.fill()<br />
<br />
# To invalidate a region to force a refresh, use:<br />
self.canvas.queue_draw_area(x, y, w, h)<br />
<br />
# Handle the expose event<br />
def do_expose_event(self, event):<br />
# Create the cairo context<br />
cairo_context = self.canvas.get_window().cairo_create(<br />
cairo_context.rectangle(event.area.x, event.area.y,<br />
event.area.width, event.area.height)<br />
cairo_context.clip()<br />
cairo_context.set_source_surface(xlib_surface)<br />
cairo_context.paint()<br />
</pre><br />
<br />
Pango is a bit different when used with Cairo:<br />
<br />
<pre><br />
import pango, pangocairo<br />
<br />
# Again, from the xlib_surface...<br />
cairo_context = cairo.Context(xlib_surface)<br />
<br />
# Create a PangoCairo context<br />
cairo_context = pangocairo.CairoContext(cairo_context)<br />
<br />
# The pango layout is created from the Cairo context<br />
pango_layout = cairo_context.create_layout()<br />
<br />
# You still use pango to set up font descriptions.<br />
fd = pango.FontDescription('Sans')<br />
fd.set_size(12 * pango.SCALE)<br />
<br />
# Tell your pango layout about your font description<br />
pango_layout.set_font_description(fd)<br />
<br />
# Write text to your pango layout<br />
pango_layout.set_text('Hello world')<br />
<br />
# Position it within the Cairo context<br />
cairo_context.save()<br />
cairo_context.translate(x, y)<br />
cairo_context.rotate(pi / 3) # You can rotate text and images in Cairo<br />
cairo_context.set_source_rgb(1, 0, 0)<br />
<br />
# Finally, draw the text<br />
cairo_context.update_layout(pango_layout)<br />
cairo_context.show_layout(pango_layout)<br />
cairo_context.restore()<br />
</pre><br />
<br />
To draw a bitmap...<br />
<br />
<pre><br />
# Again, from the xlib_surface...<br />
cairo_context = cairo.Context(xlib_surface)<br />
<br />
# Create a gtk context<br />
cairo_context = gtk.gdk.CairoContext(cairo_context)<br />
cairo_context.set_source_pixbuf(pixbuf, x, y)<br />
cairo_context.rectangle(x, y, w, h)<br />
cairo_context.fill()<br />
</pre><br />
<br />
To read a pixel from the xlib surface...<br />
<br />
<pre><br />
# create a new 1x1 cairo surface<br />
cairo_surface = cairo.ImageSurface(cairo.FORMAT_RGB24, 1, 1);<br />
cairo_context = cairo.Context(cairo_surface)<br />
# translate xlib_surface so that target pixel is at 0, 0<br />
cairo_context.set_source_surface(xlib_surface, -x, -y)<br />
cairo_context.rectangle(0,0,1,1)<br />
cairo_context.set_operator(cairo.OPERATOR_SOURCE)<br />
cairo_context.fill()<br />
cairo_surface.flush() # ensure all writing is done<br />
# Read the pixel<br />
return (ord(pixels[2]), ord(pixels[1]), ord(pixels[0]), 0)<br />
</pre><br />
<br />
===Going from Cairo in GTK-2 to Cairo in GTK-3===<br />
<br />
Not much changes, but...<br />
<br />
The Cairo/Pango interaction is a little different:<br />
<pre><br />
from gi.repository import Pango, PangoCairo<br />
<br />
cairo_context = ...<br />
pango_layout = PangoCairo.create_layout(cairo_context)<br />
fd = Pango.FontDescription('Sans')<br />
fd.set_size(12 * pango.SCALE)<br />
pango_layout.set_font_description(fd)<br />
pango_layout.set_text('Hello World', -1)<br />
cairo_context.set_source_rgb(1, 0, 0)<br />
PangoCairo.update_layout(cairo_context, pango_layout)<br />
PangoCairo.show_layout(cairo_context, pango_layout)<br />
</pre><br />
<br />
===Taking a screenshot and making a thumbnail===<br />
To make a screenshot of the window:<br />
<pre><br />
width, height = window.get_width(), window.get_height()<br />
thumb_surface = Gdk.Window.create_similar_surface(window,<br />
cairo.CONTENT_COLOR,<br />
width, height)<br />
<br />
thumb_width, thumb_height = style.zoom(100), style.zoom(80)<br />
cairo_context = cairo.Context(thumb_surface)<br />
thumb_scale_w = thumb_width * 1.0 / width<br />
thumb_scale_h = thumb_height * 1.0 / height<br />
cairo_context.scale(thumb_scale_w, thumb_scale_h)<br />
Gdk.cairo_set_source_window(cairo_context, window, 0, 0)<br />
cairo_context.paint()<br />
thumb_surface.write_to_png(png_path_or_filelike_object)<br />
</pre><br />
<br />
[[Category:Developer]]</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Features/GTK3/Porting&diff=71401Features/GTK3/Porting2011-11-18T06:14:10Z<p>Skierpage: /* Porting an exisiting activity to GTK3 */ rewrite and shorten intro, link GTK3, consistently use "GTK3", replace some pre tags with space</p>
<hr />
<div>=Porting an existing activity to GTK3=<br />
This is a guide to porting an existing activity from GTK2 to [http://developer.gnome.org/gtk3/stable/ GTK3]. It also shows the changes to use the new Sugar toolkit that also now uses [[Features/GTK3|GTK3]]. This guide uses the [http://git.sugarlabs.org/hello-world hello-world] activity as a simple example.<br />
<br />
==Preparation==<br />
Before you start porting your activity you are encouraged to branch off a stable branch. This will allow you to keep on doing stable releases on the stable branch and new releases on the master branch.<br />
<br />
The latest release was version 3. We highly recommend that you use the 'sugar-0.94' as the stable branch name because this will keep the repositories consistent and eases the development work. In git you can create a branch like this:<br />
git branch sugar-0.94<br />
<br />
This creates a local branch, as you can see by running 'git branch'; you should see the following:<br />
<br />
<pre><br />
[erikos@T61 helloworld]$ git branch<br />
* master<br />
sugar-0.94<br />
</pre><br />
<br />
The 'sugar-0.94' branch is only available locally, as you can see by running 'git branch -r' which shows the remote branches:<br />
<br />
<pre><br />
[erikos@T61 helloworld]$ git branch -r<br />
origin/HEAD -> origin/master<br />
origin/master<br />
origin/sucrose-0.84<br />
</pre><br />
<br />
The only branch available besides the master branch is the 'sucrose-0.84' branch. Let's push now our new branch to the remote repository to make it available for others:<br />
<pre><br />
git push origin sugar-0.94<br />
</pre><br />
<br />
The branch is now listed as a remote branch. You can verify as well on your [http://git.sugarlabs.org/hello-world/mainline gitorious page].<br />
<pre><br />
[erikos@T61 helloworld]$ git branch -r<br />
origin/HEAD -> origin/master<br />
origin/master<br />
origin/sucrose-0.84<br />
origin/sugar-0.94<br />
</pre><br />
<br />
You can switch now between those branches using 'git checkout <branch>'. And you can use 'git branch' to see which branch you are on (the one with the * before is the branch you are currently on).<br />
<pre><br />
git checkout sugar-0.94<br />
git checkout master<br />
</pre><br />
<br />
==Cleanup, adopt to API changes in the sugar-toolkit==<br />
''This should be done only on the master branch''! In the new sugar-toolkit we have removed old API, you should adjust your activity accordingly:<br />
* the keep button has been removed completely<br />
* the old-style toolbar has been removed<br />
<br />
==Port the activity from GTK2 to GTK3==<br />
To start, change the importing instruction for GTK from<br />
import gtk<br />
to<br />
from gi.repository import Gtk<br />
Then you have to change each call that involves Gtk, for example creating a button will look now like this:<br />
button = Gtk.Button()<br />
<br />
A simple hello world program in GTK3 looks like this:<br />
<pre><br />
from gi.repository import Gtk<br />
<br />
def _destroy_cb(widget, data=None):<br />
Gtk.main_quit()<br />
<br />
w = Gtk.Window()<br />
w.connect("destroy", _destroy_cb)<br />
label = Gtk.Label('Hello World!')<br />
w.add(label)<br />
w.show_all()<br />
<br />
Gtk.main()<br />
</pre><br />
<br />
For porting your activity you do have to change your calls for accessing widgets and services in the new GTK3 sugar-toolkit as well. The new namespace is called sugar3, trying to reflect that GTK3 is the underlying technology. For example the import of the base activity class has to be changed from<br />
from sugar.activity import activity<br />
to<br />
from sugar3.activity import activity<br />
<br />
The changes that were needed to port the hello-world activity can be seen in [http://git.sugarlabs.org/hello-world/mainline/commit/508e1c518b56cbde5508e560c8a2ff38a3518583 this commit].<br />
<br />
Ok, let's do these changes now for your activity. Make sure you are in your master branch using the 'git branch' command (the master branch should have a '*' before it). Make your changes, commit them ('git commit -a') and push them to the remote repository ('git push origin master').<br />
<br />
===Tools===<br />
There are tools to help you do the porting. There is a script in the pygobject repository for porting called [http://git.gnome.org/browse/pygobject/tree/pygi-convert.sh pygi-convert.sh], more info about the script can be found in [http://live.gnome.org/PyGObject/IntrospectionPorting the PyGObject Introspection Porting guide]. <br />
<br />
If you are having trouble finding how a particular GTK class/method/constant has been named in PyGI, run [http://dev.laptop.org/~dsd/20110806/pygi-enumerate.py pygi-enumerate.py] and grep the output. (this app lists all identified methods and constants).<br />
<br />
<br />
=== Constructor considerations ===<br />
<br />
With PyGI it is possible to use Python-like constructors, or "new" functions e.g. the following are (usually) equivalent:<br />
label = Gtk.Button()<br />
label = Gtk.Button.new()<br />
<br />
However, the first form is preferred: it is more Python-like. Internally, the difference is that Gtk.Label.new() translates to a call to gtk_label_new(), whereas Gtk.Label() (the preferred form) will directly construct an instance of GtkLabel at the GObject level.<br />
<br />
If the constructor takes parameters, they '''must''' be named. The parameters correspond to GObject properties in the API documentation which are usually marked as "Construct". For example, the following code will not work:<br />
<br />
expander = Gtk.Expander("my expander")<br />
<br />
The (confusing) error is:<br />
TypeError: GObject.__init__() takes exactly 0 arguments (1 given)<br />
<br />
The solution is to go to the [http://developer.gnome.org/gtk3/3.2/GtkExpander.html#GtkExpander.properties GtkExpander API documentation] and find the appropriate property that we wish to set. In this case it is <b>label</b> (which is a Construct property, further increasing our confidence of success), so the code should be:<br />
<br />
expander = Gtk.Expander(label="my expander")<br />
<br />
Combining the two points above, if you wish to call a construct-like function such as gtk_button_new_with_label(), you do have the option of calling Gtk.Button.new_with_label(), however if we check the [http://developer.gnome.org/gtk3/3.2/GtkButton.html#GtkButton.properties GtkButton properties] we see one called "label" which is equivalent. Therefore gtk_button_new_with_label("foo") should be called as:<br />
button = Gtk.Button(label="foo")<br />
<br />
=== HBox, VBox, pack_start and pack_end ===<br />
<br />
GtkHBox and GtkVBox, commonly used containers in GTK2 code, have pack_start and pack_end methods. These take 4 parameters:<br />
# The widget to pack into the container<br />
# '''expand''': Whether the child should receive extra space when the container grows (default True)<br />
# '''fill''': True if space given to child by the expand option is actually allocated to child, rather than just padding it. This parameter has no effect if expand is set to False. A child is always allocated the full height of a gtk.HBox and the full width of a gtk.VBox. This option affects the other dimension. (default True)<br />
# '''padding''': extra space in pixels to put between child and its neighbor (default 0)<br />
<br />
In PyGTK, the expand, fill and padding parameters were optional: if unspecified, the default values above were used. In PyGI, these parameters are '''not''' optional: all 4 must be specified. Hence the rules for adding in the extra parameters are:<br />
<br />
# If '''expand''' was not set, use value True<br />
# If '''fill''' was not set, use value True. (however, if expand is False, this parameter gets ignored so False is an equally acceptable option when expand=False)<br />
# If padding was not set, use value 0.<br />
<br />
These parameters can be specified either as positional arguments or as named keyword arguments, however all 4 must always be specified. Some developers prefer keyword arguments, arguing that the following:<br />
<pre>box.pack_start(widget, expand=True, fill=False, padding=4)</pre><br />
is much more readable than:<br />
<pre>box.pack_start(widget, True, False, 4)</pre><br />
<br />
However, these functions are called extremely often; any mildly seasoned GTK developer will have memorized the order and meaning of the parameters. Some developers therefore prefer to avoid the extra work of dropping in hundreds of keyword arguments throughout the code and just use the positional ones. This is really up to you.<br />
<br />
If you are using pack_start with the default values (expand=True, fill=True and padding=0), you can avoid using pack_start (and the parameter pain that it brings with it) by just using .add for some added cleanliness, e.g.<br />
<pre>box.pack_start(widget, True, True, 0)</pre><br />
can be replaced with:<br />
<pre>box.add(widget)</pre><br />
<br />
This is as far as you need to go for now. However, in GTK3, GtkVBox and GtkHBox have been deprecated, which means they might be removed in GTK4. The replacement is to use GtkBox directly, and you may wish to make this change now. e.g.:<br />
<pre>vbox = Gtk.Box(orientation=Gtk.Orientation.VERTICAL)</pre><br />
<br />
However, it must be noted that if GtkBox is used directly (instead of using GtkHBox/GtkVBox), the default value of '''expand''' is now '''False'''. The implications of this are:<br />
# You need to check your .add() calls, as previously they would behave as pack_start with expand=True, but now they will behave as expand=False (you need to change them to use pack_start with expand=True to retain the old behaviour)<br />
# Every single pack_start call that has expand=False and padding=0 (and any value of fill) can be converted to .add() for cleanliness<br />
<br />
=== GtkAlignment considerations ===<br />
<br />
In PyGTK, the gtk.Alignment constructor takes four optional parameters:<br />
# xalign: the fraction of horizontal free space to the left of the child widget. Ranges from 0.0 to 1.0. Default value 0.0.<br />
# yalign: the fraction of vertical free space above the child widget. Ranges from 0.0 to 1.0. Default value 0.0.<br />
# xscale: the fraction of horizontal free space that the child widget absorbs, from 0.0 to 1.0. Default value 0.0.<br />
# yscale: the fraction of vertical free space that the child widget absorbs, from 0.0 to 1.0. Default value 0.0<br />
<br />
In PyGI/GTK3, these parameters are still optional when used in the Gtk.Alignment constructor (as keyword arguments, as explained above). However, the default values have changed. They are now:<br />
# xalign: default value 0.5<br />
# yalign: default value 0.5<br />
# xscale: default value 1<br />
# yscale: default value 1<br />
<br />
If your code was relying on the default value of 0 for any of these parameters in PyGTK, you will now need to explicitly specify that in your constructor. Similarly, if you were previously using construction parameters to select the now-default values, those parameters can be dropped.<br />
<br />
Additionally, PyGTK accepted these construction parameters as positional arguments. As explained above, they must now be converted to keyword arguments.<br />
<br />
==Make a release==<br />
===Versioning===<br />
If you do new releases the versioning of the GTK2 and GTK3 release should be different. For GTK2 releases you should use dotted versions for new development releases major versions. Let's have a look at hello-world as an example. The latest release of hello-world was version 3. Bug fix releases should be named 3.1 then 3.2 and so on. The new releases for the new development branch should be starting with a major number, in this case 4.<br />
<br />
== Tips to Activity Developers ==<br />
<br />
===Going from Drawable to Cairo===<br />
<br />
GTK-3 does not support gtk Drawable objects, so the first step is to get your activity running under Cairo.<br />
<br />
<pre><br />
import cairo<br />
<br />
# From activity.Activity, you inherit a canvas.<br />
# Create a Cairo context from the window.<br />
cairo_context = self.canvas.get_window().cairo_create()<br />
<br />
# Create an XLib surface to be used for drawing<br />
xlib_surface = surface.create_similar(cairo.CONTENT_COLOR,<br />
gtk.gdk.screen_width(),<br />
gtk.gdk.screen_height())<br />
<br />
# You'll need a Cairo context from which you'll build a GTK Cairo context<br />
cairo_context = cairo.Context(xlib_surface)<br />
cairo_context = gtk.gdk.CairoContext(cairo_context)<br />
<br />
# Use this context as you would a Drawable, substituting Cairo commands<br />
# for gtk commands, e.g.,<br />
cairo_context.move_to(0, 0)<br />
cairo_context.line_to(100, 100)<br />
# Cairo uses floats from 0 to 1 for RGB values<br />
cairo_context.set_source_rgb(r, g, b)<br />
cairo_context.rectangle(x, y, w, h)<br />
cairo_context.fill()<br />
<br />
# To invalidate a region to force a refresh, use:<br />
self.canvas.queue_draw_area(x, y, w, h)<br />
<br />
# Handle the expose event<br />
def do_expose_event(self, event):<br />
# Create the cairo context<br />
cairo_context = self.canvas.get_window().cairo_create(<br />
cairo_context.rectangle(event.area.x, event.area.y,<br />
event.area.width, event.area.height)<br />
cairo_context.clip()<br />
cairo_context.set_source_surface(xlib_surface)<br />
cairo_context.paint()<br />
</pre><br />
<br />
Pango is a bit different when used with Cairo:<br />
<br />
<pre><br />
import pango, pangocairo<br />
<br />
# Again, from the xlib_surface...<br />
cairo_context = cairo.Context(xlib_surface)<br />
<br />
# Create a PangoCairo context<br />
cairo_context = pangocairo.CairoContext(cairo_context)<br />
<br />
# The pango layout is created from the Cairo context<br />
pango_layout = cairo_context.create_layout()<br />
<br />
# You still use pango to set up font descriptions.<br />
fd = pango.FontDescription('Sans')<br />
fd.set_size(12 * pango.SCALE)<br />
<br />
# Tell your pango layout about your font description<br />
pango_layout.set_font_description(fd)<br />
<br />
# Write text to your pango layout<br />
pango_layout.set_text('Hello world')<br />
<br />
# Position it within the Cairo context<br />
cairo_context.save()<br />
cairo_context.translate(x, y)<br />
cairo_context.rotate(pi / 3) # You can rotate text and images in Cairo<br />
cairo_context.set_source_rgb(1, 0, 0)<br />
<br />
# Finally, draw the text<br />
cairo_context.update_layout(pango_layout)<br />
cairo_context.show_layout(pango_layout)<br />
cairo_context.restore()<br />
</pre><br />
<br />
To draw a bitmap...<br />
<br />
<pre><br />
# Again, from the xlib_surface...<br />
cairo_context = cairo.Context(xlib_surface)<br />
<br />
# Create a gtk context<br />
cairo_context = gtk.gdk.CairoContext(cairo_context)<br />
cairo_context.set_source_pixbuf(pixbuf, x, y)<br />
cairo_context.rectangle(x, y, w, h)<br />
cairo_context.fill()<br />
</pre><br />
<br />
To read a pixel from the xlib surface...<br />
<br />
<pre><br />
# create a new 1x1 cairo surface<br />
cairo_surface = cairo.ImageSurface(cairo.FORMAT_RGB24, 1, 1);<br />
cairo_context = cairo.Context(cairo_surface)<br />
# translate xlib_surface so that target pixel is at 0, 0<br />
cairo_context.set_source_surface(xlib_surface, -x, -y)<br />
cairo_context.rectangle(0,0,1,1)<br />
cairo_context.set_operator(cairo.OPERATOR_SOURCE)<br />
cairo_context.fill()<br />
cairo_surface.flush() # ensure all writing is done<br />
# Read the pixel<br />
return (ord(pixels[2]), ord(pixels[1]), ord(pixels[0]), 0)<br />
</pre><br />
<br />
===Going from Cairo in GTK-2 to Cairo in GTK-3===<br />
<br />
Not much changes, but...<br />
<br />
The Cairo/Pango interaction is a little different:<br />
<pre><br />
from gi.repository import Pango, PangoCairo<br />
<br />
cairo_context = ...<br />
pango_layout = PangoCairo.create_layout(cairo_context)<br />
fd = Pango.FontDescription('Sans')<br />
fd.set_size(12 * pango.SCALE)<br />
pango_layout.set_font_description(fd)<br />
pango_layout.set_text('Hello World', -1)<br />
cairo_context.set_source_rgb(1, 0, 0)<br />
PangoCairo.update_layout(cairo_context, pango_layout)<br />
PangoCairo.show_layout(cairo_context, pango_layout)<br />
</pre><br />
<br />
===Taking a screenshot and making a thumbnail===<br />
To make a screenshot of the window:<br />
<pre><br />
width, height = window.get_width(), window.get_height()<br />
thumb_surface = Gdk.Window.create_similar_surface(window,<br />
cairo.CONTENT_COLOR,<br />
width, height)<br />
<br />
thumb_width, thumb_height = style.zoom(100), style.zoom(80)<br />
cairo_context = cairo.Context(thumb_surface)<br />
thumb_scale_w = thumb_width * 1.0 / width<br />
thumb_scale_h = thumb_height * 1.0 / height<br />
cairo_context.scale(thumb_scale_w, thumb_scale_h)<br />
Gdk.cairo_set_source_window(cairo_context, window, 0, 0)<br />
cairo_context.paint()<br />
thumb_surface.write_to_png(png_path_or_filelike_object)<br />
</pre></div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Talk:Features/Content_support&diff=56456Talk:Features/Content support2010-09-04T10:40:12Z<p>Skierpage: /* Browse can handle content bundles directly */ sign</p>
<hr />
<div>I'd argue for a somewhat different approach to achieving the same goals. Instead of introducing yet another modal dialog, why not eliminate the list view and replace it with the star function in the Journal itself. Any object that is starred will show up on the Home View. (Ideally, there would be multiple stars corresponding to multiple Home Views, e.g., one for school, one for home...)<br />
<br />
Features of this approach:<br />
* No confusing list view<br />
* Media objects in list view<br />
* Utilization of star in Journal view which currently does nothing<br />
* Reutilization of current Journal filters<br />
<br />
--[[User:Walter|Walter]] 16:39, 20 July 2010 (EDT)<br />
== Home views as Journal favorites views ==<br />
<br />
I imagine the Home view becoming tightly integrated with the Journal through the Journal favorites as Walter suggests.<br />
<br />
The 'List' Home view should be replaced by a Journal icon that would take the learner to a "non-favorite"-limited filter in the Journal view of the currently-selected Home group. Where "Home group" would be the alternate views such as, School, Games, Music, Photos, etc., created by new Journal tagging features. (The default Home view, would continue to be the favorite list of installed Activities.)<br />
<br />
A sub-row of Home group icons (which would instantly reveal on hover) would be provided on the Home view Frame button palette to allow the learner to jump to alternate Favorite views. The Favorites Home view button would gain the same sub-row palette, and the alternate view patterns would be a sub-palette that would reveal only on a persistent hover or right-mouse button click.<br />
<br />
To complement the easy Journal access from the Home view, we should provide a direct Home view button on the Journal toolbar&mdash;the Journal Favorites view (aka, Home view). To conserve the valuable toolbar space, this should qualify for one of the corner positions. (Are we reserving the corners for alert beacons or what?)<br />
<br />
--[[User:FGrose|FGrose]] 16:33, 21 July 2010 (EDT)<br />
<br />
http://lists.sugarlabs.org/archive/sugar-devel/2010-July/025615.html describes a Journal group design to support Activity and content grouping. --[[User:FGrose|FGrose]] 11:26, 28 July 2010 (EDT)<br />
<br />
== (Ab)using the Journal for stuff that the user didn't do, create, or access ==<br />
<br />
Both of these comments break a pretty core concept of the current journal design, in my opinion.<br />
<br />
http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg07888.html<br />
: Amend the "non-favorite" filter above to include only learner-tagged objects/events. Then we could extend the Journal concept to My Journal and Others' Journals (some higher level filter with appropriate colors and names). This would accommodate shared Journals and the core content that came with the Sugar image. --[[User:FGrose|FGrose]] 17:52, 21 July 2010 (EDT)<br />
<br />
:This proposal somewhat exasperates the confusion over things pre-installed in the Journal, but this is a preexisting problem. --[[User:Walter|Walter]] 20:55, 21 July 2010 (EDT)<br />
:: True, but with the concept of My Journal vs. Others', a System Journal may come to conveniently represent the machine (with appropriate groups, such as event and error logs, that are more closely associated with the system vs. the learner). We could find a natural way to introduce pre-installed content, which, once activated, become learner Activity instances, such as the e-book with my annotations and last page number, etc. --[[User:FGrose|FGrose]] 23:17, 21 July 2010 (EDT)<br />
:::It is the "natural way to introduce pre-installed content" part I still struggle with, but as I said, this is a preexisting problem and shouldn't be roadblock to this feature proposal. --[[User:Walter|Walter]] 08:22, 22 July 2010 (EDT)<br />
<br />
== Adding a search interface for non-user-created content ==<br />
<br />
I like these suggestions a lot; it seems to me quite important to implement a first pass for use/testing/discussion.<br />
<br />
The idea of making better use of the home screen for finding/accessing content in particular could be enhanced by making good use of the search bar there (currently disabled). <br />
<br />
The results of a search should be an interface for discovering content of all sorts. It could also replace the current software update interface. I'd like to see it include (copied in part from [http://dev.laptop.org/ticket/10244 bug 10244]):<br />
<br />
# Support discovery of local and remote content, including:<br />
#* Content available locally on the machine<br />
#* Content whose metadata / last known location is on the machine (found by searching a local metadata catalog)<br />
#* Content whose metadata / last known location is in a public catalog (found by visiting a URL)<br />
#:<br />
# Support discovery of many types of content:<br />
#* activities and content bundles (using .xo/.xol microformats or other)<br />
#* individual books (using OPDS data or other)<br />
#* journal entries (using standardized journal metadata if searching "others' public journals")<br />
#:<br />
# Support the notion of updates<br />
#* Checking for new catalog data and offering to update local catalog data when searches are run<br />
#* Checking metalists of available (distributed) catalogs and offering to check new catalogs for more activities/content<br />
#* Comparing version IDs or timestamps for activities/content that have it<br />
#* Offering hints as to the number of updates available for content already stored locally <br />
#*: <small>(as the current Activity Update interface offers. the default hint should probably be less bold; rather than a page listing the updates in detail and asking you to click "go!")</small><br />
<br />
== Browse can handle content bundles directly ==<br />
<br />
''The widely-deployed .xol content bundles only have minimal support (they can only be launched from the journal).''<br />
: Not true, you can view .xol (or any ZIP file) contents in Browse ''without installing or unpacking'' using the jar: protocol ({{bug|1258}}).<br />
<br />
Copy and paste the following into your browse bar , including the "jar:" on the front.<br />
jar:http://wiki.laptop.org/images/3/3e/Biology-9.jar!/Biology/index.en.html<br />
<br />
This has some interesting implications.<br />
* Sugar code doesn't have to keep a .xol and a Library directory in sync, installing and uninstalling the latter as .xols are opened and erased.<br />
* The file system determines if a content bundle conflicts with another.<br />
* Instead of making web pages telling readers how great some content is, they can view it for themselves before they download.<br />
<br />
There are limitations to this:<br />
* Some collections have an index.html that does a meta http-equiv refresh to a path in file:///home/olpc/Library , this won't work (and I think breaks anyway in other Sugar environments)<br />
* Some collections (Biology, NatureImages, TranslationDictionary) reference a /usr/share/library-common/css/master.css). This won't work if you browse them remotely.<br />
* I don't know what the performance implications are. I know Firefox 3.6 has additional performance boosts as Mozilla moved more files into a single runtime .jar file.<br />
-- [[User:Skierpage|Skierpage]] 06:40, 4 September 2010 (EDT)</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Talk:Features/Content_support&diff=56455Talk:Features/Content support2010-09-04T10:28:52Z<p>Skierpage: /* Browse can handle content bundles directly */ new section</p>
<hr />
<div>I'd argue for a somewhat different approach to achieving the same goals. Instead of introducing yet another modal dialog, why not eliminate the list view and replace it with the star function in the Journal itself. Any object that is starred will show up on the Home View. (Ideally, there would be multiple stars corresponding to multiple Home Views, e.g., one for school, one for home...)<br />
<br />
Features of this approach:<br />
* No confusing list view<br />
* Media objects in list view<br />
* Utilization of star in Journal view which currently does nothing<br />
* Reutilization of current Journal filters<br />
<br />
--[[User:Walter|Walter]] 16:39, 20 July 2010 (EDT)<br />
== Home views as Journal favorites views ==<br />
<br />
I imagine the Home view becoming tightly integrated with the Journal through the Journal favorites as Walter suggests.<br />
<br />
The 'List' Home view should be replaced by a Journal icon that would take the learner to a "non-favorite"-limited filter in the Journal view of the currently-selected Home group. Where "Home group" would be the alternate views such as, School, Games, Music, Photos, etc., created by new Journal tagging features. (The default Home view, would continue to be the favorite list of installed Activities.)<br />
<br />
A sub-row of Home group icons (which would instantly reveal on hover) would be provided on the Home view Frame button palette to allow the learner to jump to alternate Favorite views. The Favorites Home view button would gain the same sub-row palette, and the alternate view patterns would be a sub-palette that would reveal only on a persistent hover or right-mouse button click.<br />
<br />
To complement the easy Journal access from the Home view, we should provide a direct Home view button on the Journal toolbar&mdash;the Journal Favorites view (aka, Home view). To conserve the valuable toolbar space, this should qualify for one of the corner positions. (Are we reserving the corners for alert beacons or what?)<br />
<br />
--[[User:FGrose|FGrose]] 16:33, 21 July 2010 (EDT)<br />
<br />
http://lists.sugarlabs.org/archive/sugar-devel/2010-July/025615.html describes a Journal group design to support Activity and content grouping. --[[User:FGrose|FGrose]] 11:26, 28 July 2010 (EDT)<br />
<br />
== (Ab)using the Journal for stuff that the user didn't do, create, or access ==<br />
<br />
Both of these comments break a pretty core concept of the current journal design, in my opinion.<br />
<br />
http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg07888.html<br />
: Amend the "non-favorite" filter above to include only learner-tagged objects/events. Then we could extend the Journal concept to My Journal and Others' Journals (some higher level filter with appropriate colors and names). This would accommodate shared Journals and the core content that came with the Sugar image. --[[User:FGrose|FGrose]] 17:52, 21 July 2010 (EDT)<br />
<br />
:This proposal somewhat exasperates the confusion over things pre-installed in the Journal, but this is a preexisting problem. --[[User:Walter|Walter]] 20:55, 21 July 2010 (EDT)<br />
:: True, but with the concept of My Journal vs. Others', a System Journal may come to conveniently represent the machine (with appropriate groups, such as event and error logs, that are more closely associated with the system vs. the learner). We could find a natural way to introduce pre-installed content, which, once activated, become learner Activity instances, such as the e-book with my annotations and last page number, etc. --[[User:FGrose|FGrose]] 23:17, 21 July 2010 (EDT)<br />
:::It is the "natural way to introduce pre-installed content" part I still struggle with, but as I said, this is a preexisting problem and shouldn't be roadblock to this feature proposal. --[[User:Walter|Walter]] 08:22, 22 July 2010 (EDT)<br />
<br />
== Adding a search interface for non-user-created content ==<br />
<br />
I like these suggestions a lot; it seems to me quite important to implement a first pass for use/testing/discussion.<br />
<br />
The idea of making better use of the home screen for finding/accessing content in particular could be enhanced by making good use of the search bar there (currently disabled). <br />
<br />
The results of a search should be an interface for discovering content of all sorts. It could also replace the current software update interface. I'd like to see it include (copied in part from [http://dev.laptop.org/ticket/10244 bug 10244]):<br />
<br />
# Support discovery of local and remote content, including:<br />
#* Content available locally on the machine<br />
#* Content whose metadata / last known location is on the machine (found by searching a local metadata catalog)<br />
#* Content whose metadata / last known location is in a public catalog (found by visiting a URL)<br />
#:<br />
# Support discovery of many types of content:<br />
#* activities and content bundles (using .xo/.xol microformats or other)<br />
#* individual books (using OPDS data or other)<br />
#* journal entries (using standardized journal metadata if searching "others' public journals")<br />
#:<br />
# Support the notion of updates<br />
#* Checking for new catalog data and offering to update local catalog data when searches are run<br />
#* Checking metalists of available (distributed) catalogs and offering to check new catalogs for more activities/content<br />
#* Comparing version IDs or timestamps for activities/content that have it<br />
#* Offering hints as to the number of updates available for content already stored locally <br />
#*: <small>(as the current Activity Update interface offers. the default hint should probably be less bold; rather than a page listing the updates in detail and asking you to click "go!")</small><br />
<br />
== Browse can handle content bundles directly ==<br />
<br />
''The widely-deployed .xol content bundles only have minimal support (they can only be launched from the journal).''<br />
: Not true, you can view .xol (or any ZIP file) contents in Browse ''without installing or unpacking'' using the jar: protocol ({{bug|1258}}).<br />
<br />
Copy and paste the following into your browse bar , including the "jar:" on the front.<br />
jar:http://wiki.laptop.org/images/3/3e/Biology-9.jar!/Biology/index.en.html<br />
<br />
This has some interesting implications.<br />
* Sugar code doesn't have to keep a .xol and a Library directory in sync, installing and uninstalling the lattr<br />
* The file system ensures uniqueness of content bundles<br />
* Instead of making web pages telling readers how great some content is, they can view it for themselves before they download.<br />
<br />
=== Limitations ===<br />
* Some collections have an index.html that does a meta http-equiv refresh to a path in file:///home/olpc/Library , this won't work (and I think breaks anyway in other Sugar environments)<br />
* Some collections (Biology, NatureImages, TranslationDictionary) reference a /usr/share/library-common/css/master.css). This won't work if you browse them remotely.<br />
* I don't know what the performance implications are. I know Firefox 3.6 has additional performance boosts as Mozilla moved more files into a single runtime .jar file.</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=User_talk:Wade/Unified_Bundles&diff=56311User talk:Wade/Unified Bundles2010-08-28T20:16:35Z<p>Skierpage: /* Mozilla can open compressed files, including bundles */ still works</p>
<hr />
<div>== Making FCAs inside other activities ==<br />
An interesting idea which might be relevant to this proposal is the spawning of FCAs from other activities. The general idea is that I created this killer Etoys app and I want to share it with the world, not as a journal entry but as a activity itself. LFaraone 23:17, 6 April 2009 (UTC)<br />
<br />
== Yet another scheme of implementing viewers ==<br />
startup scripts(launchers) could be parts of sugar itself and contain only metadata about viewer activity.<br />
<br />
It should mean that sugar all time has the full list of possible launchers. When user starts bundle with launcher mentioned in exec section, launcher will check if proper viewer activity is installed if it doesn't launcher will install it from ASLO, otherwise(for example in case of bad internet connection) distributor should preinstall these activities(anyway this case is only distribution specific).<br />
<br />
In that case we have list of stable launchers(since they don't have much code) and in anytime we could download last version of viewer activity from ASLO.<br />
<br />
[[User:Alsroot|Alsroot]] 00:40, 7 April 2009 (UTC)<br />
<br />
== Unified Objects ==<br />
<br />
See also [[User:Alsroot/trash/Unified Objects| Unified Objects]]<br />
<br />
[[User:Alsroot|Alsroot]] 06:14, 8 April 2009 (UTC)<br />
: A good parallel! [[User:Sj|+sj]] [[User Talk:Sj|<font color="#ff6996">+</font>]]<br />
<br />
== content viewers ==<br />
<br />
content viewers should get the functionality of being made as slide-shows. For example, inside the jukebox activity, one should be able to add various media files, i.e., a playlist. It would appear in the journal as a jukebox activity. The same with image viewer, creating slideshows of images. Just some thoughts on the idea that launching new viewer activities, and these viewer activities could be usefull. [[User:HoboPrimate|HoboPrimate]] 19:27, 10 April 2009 (UTC)<br />
<br />
== Just open Browse! ==<br />
<br />
A dedicated "Web Content Viewer" makes little sense. Just pass the file:/// URL to existing machinery to open a URL (thus opening up Browse) and declare victory!<br />
<br />
I don't see much benefit to opening web content in something that's sort of like Browse but isn't. Look at the 8.2.0 Help activity, the moment you follow an external URL you might as well be running Browse instead of the same code in a different skin.<br />
<br />
Any changes to Browse (like remembering your current location, annotating books, etc.) seem best handled by an extension, like the existing eReader one.<br />
<br />
-- [[User:Skierpage|Skierpage]] 02:45, 10 August 2009 (UTC)<br />
<br />
=== Mozilla can open compressed files, including bundles ===<br />
<br />
BTW, one trick of Mozilla code is that it can open compressed files using the jar: protocol;<br /><br />
<tt>jar:''protocol:/URL''!''/path/in/zip/file''</tt><br />
<br />
Thus the activity.info can tell Browse to open the URL jar:file:///home/olpc/Activities/SomeBrowserStuff.xo!/content/index.html and you need never unpack the ZIP file, browsing the HTML just works. I've verified this with the Net Bible collection, I believe it's true for other collections. -- [[User:Skierpage|Skierpage]] 02:45, 10 August 2009 (UTC)<br />
: Still works in OLPC 10.1.2 (os852), Browse can view content in a compressed bundle. You could either view directly in the Journal or from a copy under Activities, without unpacking. The enhancement bug for this feature is {{bug|1258}}: "support browsing HTML content within bundles instead of unzipping them". -- [[User:Skierpage|Skierpage]] 16:16, 28 August 2010 (EDT)</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Activities/Help&diff=55885Activities/Help2010-08-17T07:15:54Z<p>Skierpage: add the activity icon (copied from OLPC)</p>
<hr />
<div><noinclude>{{TOCright}}[[Category:Activities|Help]]</noinclude>[[Image:activity-help.svg|left]]<br />
[http://activities.sugarlabs.org/en-US/sugar/addon/4051 Activity Library] | [http://git.sugarlabs.org/projects/help Source] | [http://en.flossmanuals.net/xo Floss Manual] | [http://dev.laptop.org/query?component=help-activity&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&order=priority OLPC Trac tickets]<br />
<br />
==Goals of the Help Activity==<br />
<br />
# Provide users with easy access to documentation and manuals<br />
# Let people understand that Sugar is a Community Project and that we would like their help<br />
# Invite users to join the community by asking a question<br />
# Make visible the fact that we are real people<br />
<br />
==User Experience==<br />
<br />
I am hoping our design people will help here. I think it should be a<br />
blurb about being a community project, invitation to ask a question and<br />
a link to the manual in a reader.<br />
<br />
: This is great stuff that belongs on the [http://git.sugarlabs.org/projects/browse/repos/mainline/blobs/master/data/index.html Browse home page] in a '''Getting help''' section. If the home page were generated (as it was in OLPC releases see ticket {{bug|574}}) then it could detect if the Help content is installed and link to it as well as online doc) You can also also add the first two items to the Sugar/8_4 introductory section at http://flossmanuals.net. -- [[User:Skierpage|Skierpage]] 21:37, 26 May 2009 (UTC)<br />
<br />
==Specific tasks we should be sure to cover==<br />
<br />
* providing information how to setup network --> just explaning to go to F1 and to click on the essid <br />
* function buttons F1-4 => minimal information about views world,group,me,journal/activities,<br />
* how to set language => short cut to setting menu.<br />
<br />
==Asking a Question==<br />
<br />
We don't have a email client so we'll need people to ask a question on<br />
a web page. We'll need to explain to them that they can't use it if<br />
they are offline.<br />
<br />
<br />
We should ask for the email address so we can answer them.<br />
<br />
For a first iteration questions will be directed to IAEP and community<br />
members will be asked to reply. Replying with a link to an FAQ or<br />
Wiki page with an answer is to be encouraged.<br />
<br />
If we get into any sort of dialog with the question we should invite<br />
them to subscribe to IAEP and to help the community.<br />
<br />
Sept '09 - We are now moving toward Launchpad for questions so we could potentially direct people to that website.<br />
<br />
==Nice to Have Features==<br />
<br />
* Look up what version of Sugar they are running and point them to the appropriate manual for that version.<br />
*: If the Browse activity's home page were part of Sugar then it could link to the appropriate local file:// and/or online URLs. This home page could either be static and updated with each Sugar release; or it could dynamically built from a template as it was in the OLPC OS releases, and detect if the user has local help pages. You can also detect in JavaScript if a local file:// URL exists, [http://www.skierpage.com/olpc/show_help.html here's some code]. -- [[User:Skierpage|Skierpage]] 04:53, 26 May 2009 (UTC)<br />
<br />
==Next Steps==<br />
* Put the content of the help activity into a form that can be managed with version control so we can make different versions for the XO and SoaS and potentially let deployments customize it. - ticket {{Bug|885}}<br />
*: The content is currently managed on http://flossmanuals.net , which uses TWiki for editing and version history. You can go to http://en.flossmanuals.net/remix and make a Sugar 0.84 manual from the Sugar/8_4 manual items. I believe this is how someone (Sj?) loaded the HTML into http://git.sugarlabs.org/projects/help/repos/mainline/trees/master/help -- [[User:Skierpage|Skierpage]] 05:21, 26 May 2009 (UTC)<br />
<br />
==Resources==<br />
[[OLPC:release 8.2.0]] ships with the [[olpc:Help activity]]. This is a dedicated browser that shows pages describing the XO-1 laptop and its software including Sugar version 0.82. This activity is hosted at http://git.sugarlabs.org/projects/help and its material comes from community editing at http://flossmanuals.net.<br />
<br />
* Trac Tickets: [http://dev.laptop.org/query?component=help-activity&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&order=priority OLPC]<br />
* French version [http://activities.sugarlabs.org/en-US/sugar/addon/4195 Helpfr], [[Activities/Helpfr]] in Sugar 0.84</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=File:Activity-help.svg&diff=55884File:Activity-help.svg2010-08-17T06:47:49Z<p>Skierpage: The 2008-09-16 version from [[olpc:Image:Activity-help.svg] , http://wiki.laptop.org/images/2/23/Activity-help.svg</p>
<hr />
<div>The 2008-09-16 version from [[olpc:Image:Activity-help.svg] , http://wiki.laptop.org/images/2/23/Activity-help.svg</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Documentation_Team&diff=55883Documentation Team2010-08-17T06:35:39Z<p>Skierpage: /* Sugar FLOSS manual */ mention how this became the Help activity!</p>
<hr />
<div>{{Translations <br />
| [[Documentation Team|english]] &#124; [[Documentation Team/lang-es|español]] }}<br />
<noinclude>{{TeamHeader|Documentation Team|home=Documentation}}{{TOCright}}</noinclude><br />
== Mission ==<br />
{{:Documentation Team/Mission}}<br />
== Sugar FLOSS manual ==<br />
FLOSS Manuals held a BookSprint during the last week of August 2008 in Austin, TX; together, we wrote separate but combinable (remixable) manuals for Sugar, individual Sugar Activities and the hardware it may run on, such as the XO. <br />
{| border=0<br />
|-<br />
|colspan=2 align="center"|{{Iframe|available as: [[File:HTML.gif|link=http://en.flossmanuals.net/Sugar]] |http://en.flossmanuals.net/Sugar|936|1000}}<br />
|-<br />
||[[File:Sugarlabs_mainpage_07.png|link=http://flossmanuals.net/Sugar]]<br />
|valign="center"|<br />
: or as a [[File:PDF.PNG|link={{FlossmanualPDF}}]] of 128 pages, 8.3 MBytes (for saving or printing).<br />
|}<br />
<br />
The manuals for a number of Sugar Activities are now published (including manuals for [http://en.flossmanuals.net/write_activity '''Write'''], [http://en.flossmanuals.net/terminal '''Terminal'''], [http://en.flossmanuals.net/chat '''Chat'''], [http://en.flossmanuals.net/browse '''Browse'''], [http://en.flossmanuals.net/record '''Record'''], and [http://en.flossmanuals.net/turtleart '''Turtle Art''']). <br />
People "remixed" these manuals to form the [[Activities/Help|Help activity]] for the XO laptop; a version of this is on the web at http://laptop.org/manual/<br />
<br />
Please help us improve these manuals by going to http://en.flossmanuals.net/write where the editable versions reside. Note that we are including tutorials and notes to parents and teachers as part of the documentation effort. Helping expanding these sections would be greatly appreciated.<br />
<br />
Those who participated include: Adam Hyde, Anne Gentle, David Farning, Mikus Grinbergs, Brian Jordan, Adam Holt, Janet Swisher, Morgan Collett, Yama Ploskonka, David Cramer, Emily Kaplan, Faisal Anwar, Christoph Derndorfer, Sandy Culver, Aaron Konstam, and the Sugar community. <br />
<br />
Many thanks also to [http://www.motive.com Motive], our hosts in Austin.<br />
<br />
===Translation===<br />
We are translating the Sugar FLOSS manual into<br />
Spanish ([http://translate.flossmanuals.net/bin/view/Sugar_es es]),<br />
French ([http://translate.flossmanuals.net/bin/view/Sugar_fr fr]),<br />
Dutch ([http://translate.flossmanuals.net/bin/view/Sugar_nl nl]),<br />
German ([http://translate.flossmanuals.net/bin/view/Sugar_de de]),<br />
and Portuguese ([http://translate.flossmanuals.net/bin/view/Sugar_pt pt]). Please help us.<br />
<br />
'''See also'''<br />
* [http://wiki.laptop.org/go/OLPC_Publications OLPC Publications] in the OLPC Wiki.<br />
* OLPC Austria's [http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Activity Handbook]<br />
<br />
==Topic Ideas==<br />
* Setup a development environment. With and without jhbuild.<br />
* "Write your activity" tutorial. It should include:<br />
** graphic controls,<br />
** datastore, <br />
** collaboration.<br />
<br />
== Programming References ==<br />
=== [http://api.sugarlabs.org API] ===<br />
<br />
The [[Documentation Team/API_Documentation | API guide ]] explains how to get started documenting api.<br />
<br />
References <br />
* http://wiki.laptop.org/go/API_reference?<br />
* Probably we should document the datastore dbus API. I'm not sure what's the best way to generate documentation for it. It's so small that a wiki page might be the simpler solution for now.<br />
* Existing collaboration documentation is at [http://wiki.laptop.org/go/Category:Collaboration Collaboration].<br />
<br />
:* Morgs, my impression after a 3 minutes look over the available documentation is that there is little written with activity authors in mind, and that it's dispersed in several pages and mixed with implementation docs. Is that impression correct? I would like to have a couple of things: 1 complete documentation of the API which interest activity authors (with good links to dbus documentation since it's used so heavily) 2 A complete tutorial as part of the "manual". One of the Tubes pages looks like a pretty good start in this respect. Does it make sense to you? Can we make it happen? -- [[User:Marcopg|Marcopg]]<br />
::* Yes we can! --[[User:Morgs|Morgs]] 13:50, 16 May 2008 (UTC)<br />
::* Hey, I came up with an alternate "reference" implementation for collaboration when I wrote Colors!, I think it's a lot easier to understand and could be the basis for a good tutorial. The only weird thing is, I wanted my activity class to receive DBus signals directly, so I subclassed ExportedGObject but initialized late - hacky, I know. It would be nice if this were not needed! [http://dev.laptop.org/git?p=activities/colors;a=blob;f=colors.py;h=c262f55e46519248418a07e3c4eed1ab4207fa09;hb=5822328cab1162b32452dfb915b33d98307b55d1#l579] [[User:Wade|Wade]] 18:49, 18 May 2008 (UTC)<br />
* Low level API (non-python activities). We should just move bert document on this wiki.<br />
:this is the page http://wiki.laptop.org/go/Low-level_Activity_API but it must be complemented with <br />
:* http://wiki.laptop.org/go/Sugar_Factory<br />
:* http://www.catmoran.com/olpc/#sugxterm<br />
<br />
== Tutorials ==<br />
<br />
* Probably good to have a pygame tutorial, it's probably the best thing we have at the moment to do free form graphics stuff.<br />
* Etoys based activity tutorial - we now have an Etoys Activity manual set up on FLOSS Manuals. Feel free to contribute here: [http://en.flossmanuals.net/bin/view/Etoys/WebHome|Etoys]<br />
* Ideally, each Activity will have a tutorial within a manual on FLOSS Manuals. Here's a rough outline for each Activity Manual:<br />
<br />
Introduction<br />
<br />
Getting Started <br />
<br />
Tutorials<br />
<br />
Reference<br />
<br />
== Glossary ==<br />
<br />
[[Documentation Team/Glossary | Glossary]]<br />
<br />
== Subpages ==<br />
<br />
{{Special:PrefixIndex/{{PAGENAMEE}}/}}<br />
<br />
<br />
[[Category:Documentation Team]]<br />
[[Category:General public]]<br />
[[Category:Team]]</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Jhbuild&diff=39119Development Team/Jhbuild2009-10-12T00:45:05Z<p>Skierpage: /* Prerequisites */ specifically, git-core</p>
<hr />
<div><noinclude>{{Translations}}{{GoogleTrans-en}}{{TOCright}}</noinclude><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.<br />
It can also run a Sugar session in a window on your desktop using the [[wikipedia:Xephyr]] nested X window server.<br />
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 />
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).<br />
<br />
==Check distro-specific instructions==<br />
<br />
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:<br />
<br />
* [[/Debian | Debian]]<br />
* [[/Fedora | Fedora]]<br />
:Here are some [http://www.youtube.com/profile?user=pleabargain&view=videos&query=jhbuild videos of the Fedora jhbuild install process]. <br />
* [[/Ubuntu | Ubuntu]]<br />
* [[/Mandriva | Mandriva]]<br />
<br />
==Some general advice==<br />
<br />
Note: Like most other Unix applications, sugar-jhbuild should never be run as root. It may easily screw up your whole system and/or break in unexpected ways if you do. If you get any permissions error, there's something wrong with your installation that should be fixed.<br />
<br />
If you're stuck or if you get strange errors, feel free to ask for help on the [[Sugar_Labs/Contacts#irc.freenode.net_channels|#sugar IRC channel]] or the [[Sugar_Labs/Contacts#Developer_Lists|sugar-devel mailing list]]. Don't waste too much time chasing strange problems: usually it's caused by some basic, easy to fix problem. You might also want to check the [http://dev.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=sugar-jhbuild bug tracker] to see if it's a known issue.<br />
<br />
==Jhbuild FAQ==<br />
:Q: <br />
::<dgd> jhbuild build on fedora11 requires 29 packages but on Ubuntu904 38... should I be concerned with the difference in number?<br />
:A:<br />
::<sdziallas> dgd: this can be caused by different packaging policies...<br />
::<dgd> sdziallas, ergo not a reason for concern, thanks!<br />
<br />
definitely do not compile as root with jhbuild -- you'll run into funky problems -- Colin A. :)<br />
<br />
==Prerequisites==<br />
; python<br />
: The sugar-jhbuild command is a Python script, so you need the Python interpreter.<br />
; git<br />
: To get the source code of sugar-jhbuild itself and many other Sugar packages you need the <tt>git</tt> command-line tool from the distributed version control system of the same name. In many distributions the minimal package you need to install is "git-core".<br />
; svn<br />
: A few packages (as of September 2009, only squeak) do not yet use git, and you need the <tt>svn</tt> command-line tool from the Subversion version control system to get their source code.<br />
<br />
These should be enough to run sugar-jhbuild on a typical Linux or Mac installation. Running <tt>sugar-jhbuild depscheck</tt> (see below) will probably list dozens of additional required packages.<br />
<br />
==Check out sugar-jhbuild==<br />
<br />
In a suitable directory (i.e. usually your user's home directory i.e. /home/yourusername/~), execute<br />
git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild<br />
<br />
::Make sure you are in the _user's_ home directory<br />
:: video http://www.youtube.com/watch?v=Tdr1bs4rQ_s<br />
<br />
You'll know if it worked if you get something like this:<br />
<pre><br />
localhost ~]$ git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild<br />
Initialized empty Git repository in /home/denny/sugar-jhbuild/.git/<br />
remote: Counting objects: 4688, done.<br />
remote: Compressing objects: 100% (1998/1998), done.<br />
remote: Total 4688 (delta 2759), reused 4488 (delta 2638)<br />
Receiving objects: 100% (4688/4688), 1.86 MiB | 197 KiB/s, done.<br />
Resolving deltas: 100% (2759/2759), done.<br />
</pre><br />
<br />
==Build sugar base system and its dependencies==<br />
<br />
Go into the directory you created and start the build. It takes about 30 minutes on a 1.6ghz machine with a wireless G connection.<br />
<br />
cd sugar-jhbuild<br />
./sugar-jhbuild update<br />
./sugar-jhbuild depscheck<br />
./sugar-jhbuild build<br />
::[http://www.youtube.com/results?search_query=pleabargain+jhbuild&search_type=&aq=f Here are videos of the process]. Before saying that [http://www.youtube.com/ Youtube] is unfriendly to Linux because of the flash player, try installing it. [http://get.adobe.com/flashplayer/ Adobe flash works] on my Ubuntu 9.04 and Fedora 11 without hitch.<br />
<br />
And now run it.<br />
./sugar-jhbuild run<br />
<br />
If it doesn't run or you have other problems read on.<br />
=== Dealing with dependencies ===<br />
<br />
''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).<br />
<br />
If you notice that there's a package missing from the <code>./sugar-jhbuild depscheck </code> output (i.e. it's required for Sugar to work properly and not installed, but depscheck does not mention it), please [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 file a bug report] (login required first, but currently no automatic redirection to login page) against the sugar-jhbuild Component in the [http://dev.sugarlabs.org/ Sugar Labs bug tracker].<br />
<br />
===Some tips and known issues===<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.<br />
*25 Aug 9: hulahop doesnt' build correctly. http://lists.sugarlabs.org/archive/sugar-devel/2009-August/018540.html The 'fix' is running autoconf.<br />
::Question. How do you run autoconf to fix this problem?<br />
::: when you get asked because of the error, choose the configure stage<br />
<br />
== Run Sugar ==<br />
<br />
This command launches the Sugar emulator in a nested X session:<br />
<br />
./sugar-jhbuild run<br />
<br />
To exit the emulator, press Alt-Q.<br />
<br />
To set debug variables, modify <code>~/.sugar/debug</code> (this file will be created on first run of Sugar).<br />
<br />
Note that due to a [http://dev.sugarlabs.org/ticket/342 bug in Xephyr] your keyboard might not work as expected. A partial workaround is to run <code>setxkbmap &lt;keymap name&gt;</code> by adding this command line to <code>~/.sugar/debug</code>. Most "regular" keys should work fine after that, some "special keys" (e.g. cursor up/down) might still refuse to operate as intended.<br />
<br />
The "keymap name" usually is a two letter country code, e.g. "de" for german or "fr" for french.<br />
<br />
== Running multiple instances ==<br />
To run an additional instance of sugar, you can start the second instance 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 fullscreen or specify a size (in pixels):<br />
<br />
./sugar-jhbuild run sugar-emulator --fullscreen<br />
./sugar-jhbuild run sugar-emulator --dimensions 1200x900<br />
<br />
The default size of 800x600 is currently the minimum that should work without issues. I.e. activities should be tested to work in this mode (and in others as well).<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 -a --clean<br />
./sugar-jhbuild run<br />
<br />
The use of -a and --clean flags are needed when a file is removed so that autogen.sh is run. '''Note:''' Some packages, e.g., squeak and etoys, don't have a ''make clean''. Just ignore the error.<br />
<br />
== If build breaks after an update ==<br />
<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].<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 />
== 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 />
* [[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[http://en.flossmanuals.net/sugar]<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>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Jhbuild&diff=37392Development Team/Jhbuild2009-09-15T05:46:21Z<p>Skierpage: remove stray text</p>
<hr />
<div><noinclude>{{Translations}}{{GoogleTrans-en}}{{TOCright}}</noinclude><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.<br />
It can also run a Sugar session in a window on your desktop using the [[wikipedia:Xephyr]] nested X window server.<br />
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 />
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).<br />
<br />
==Check distro-specific instructions==<br />
<br />
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:<br />
<br />
* [[/Debian | Debian]]<br />
* [[/Fedora | Fedora]]<br />
:Here are some [http://www.youtube.com/profile?user=pleabargain&view=videos&query=jhbuild videos of the Fedora jhbuild install process]. <br />
* [[/Ubuntu | Ubuntu]]<br />
* [[/Mandriva | Mandriva]]<br />
<br />
==Some general advice==<br />
<br />
Note: Like most other Unix applications, sugar-jhbuild should never be run as root. It may easily screw up your whole system and/or break in unexpected ways if you do. If you get any permissions error, there's something wrong with your installation that should be fixed.<br />
<br />
If you're stuck or if you get strange errors, feel free to ask for help on the [[Sugar_Labs/Contacts#irc.freenode.net_channels|#sugar IRC channel]] or the [[Sugar_Labs/Contacts#Developer_Lists|sugar-devel mailing list]]. Don't waste too much time chasing strange problems: usually it's caused by some basic, easy to fix problem. You might also want to check the [http://dev.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=sugar-jhbuild bug tracker] to see if it's a known issue.<br />
<br />
==Jhbuild FAQ==<br />
Q: <br />
<dgd> jhbuild build on fedora11 requires 29 packages but on Ubuntu904 38... should I be concerned with the difference in number?<br />
A:<br />
<sdziallas> dgd: this can be caused by different packaging policies...>>><dgd> sdziallas, ergo not a reason for concern, thanks!<br />
<br />
definitely do not compile as root with jhbuild -- you'll run into funky problems -- Colin A. :)<br />
<br />
==Prerequisites==<br />
; python<br />
: The sugar-jhbuild command is a Python script, so you need the Python interpreter.<br />
; git<br />
: To get the source code of sugar-jhbuild itself and many other Sugar packages you need the <tt>git</tt> command-line tool from the distributed version control system of the same name.<br />
; svn<br />
: A few packages (as of September 2009, only squeak) do not yet use git, and you need the <tt>svn</tt> command-line tool from the Subversion version control system to get their source code.<br />
<br />
These should be enough to run sugar-jhbuild on a typical Linux or Mac installation. Running <tt>sugar-jhbuild depscheck</tt> (see below) will probably list dozens of additional required packages.<br />
<br />
==Check out sugar-jhbuild==<br />
<br />
In a suitable directory (i.e. usually your user's home directory i.e. /home/yourusername/~), execute<br />
git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild<br />
<br />
::Make sure you are in the _user's_ home directory<br />
:: video http://www.youtube.com/watch?v=Tdr1bs4rQ_s<br />
<br />
You'll know if it worked if you get something like this:<br />
<pre><br />
localhost ~]$ git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild<br />
Initialized empty Git repository in /home/denny/sugar-jhbuild/.git/<br />
remote: Counting objects: 4688, done.<br />
remote: Compressing objects: 100% (1998/1998), done.<br />
remote: Total 4688 (delta 2759), reused 4488 (delta 2638)<br />
Receiving objects: 100% (4688/4688), 1.86 MiB | 197 KiB/s, done.<br />
Resolving deltas: 100% (2759/2759), done.<br />
</pre><br />
<br />
==Build sugar base system and its dependencies==<br />
<br />
Go into the directory you created and start the build. It takes about 30 minutes on a 1.6ghz machine with a wireless G connection.<br />
<br />
cd sugar-jhbuild<br />
./sugar-jhbuild update<br />
./sugar-jhbuild depscheck<br />
./sugar-jhbuild build<br />
::[http://www.youtube.com/results?search_query=pleabargain+jhbuild&search_type=&aq=f Here are videos of the process]. Before saying that [http://www.youtube.com/ Youtube] is unfriendly to Linux because of the flash player, try installing it. [http://get.adobe.com/flashplayer/ Adobe flash works] on my Ubuntu 9.04 and Fedora 11 without hitch.<br />
<br />
And now run it.<br />
./sugar-jhbuild run<br />
<br />
If it doesn't run or you have other problems read on.<br />
=== Dealing with dependencies ===<br />
<br />
''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).<br />
<br />
If you notice that there's a package missing from the <code>./sugar-jhbuild depscheck </code> output (i.e. it's required for Sugar to work properly and not installed, but depscheck does not mention it), please [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 file a bug report] (login required first, but currently no automatic redirection to login page) against the sugar-jhbuild Component in the [http://dev.sugarlabs.org/ Sugar Labs bug tracker].<br />
<br />
===Some tips and known issues===<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.<br />
*25 Aug 9: hulahop doesnt' build correctly. http://lists.sugarlabs.org/archive/sugar-devel/2009-August/018540.html The 'fix' is running autoconf.<br />
::Question. How do you run autoconf to fix this problem?<br />
::: when you get asked because of the error, choose the configure stage<br />
<br />
== Run Sugar ==<br />
<br />
This command launches the Sugar emulator in a nested X session:<br />
<br />
./sugar-jhbuild run<br />
<br />
To exit the emulator, press Alt-Q.<br />
<br />
To set debug variables, modify <code>~/.sugar/debug</code> (this file will be created on first run of Sugar).<br />
<br />
Note that due to a [http://dev.sugarlabs.org/ticket/342 bug in Xephyr] your keyboard might not work as expected. A partial workaround is to run <code>setxkbmap &lt;keymap name&gt;</code> by adding this command line to <code>~/.sugar/debug</code>. Most "regular" keys should work fine after that, some "special keys" (e.g. cursor up/down) might still refuse to operate as intended.<br />
<br />
The "keymap name" usually is a two letter country code, e.g. "de" for german or "fr" for french.<br />
<br />
== Running multiple instances ==<br />
To run an additional instance of sugar, you can start the second instance 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 fullscreen or specify a size (in pixels):<br />
<br />
./sugar-jhbuild run sugar-emulator --fullscreen<br />
./sugar-jhbuild run sugar-emulator --dimensions 1200x900<br />
<br />
The default size of 800x600 is currently the minimum that should work without issues. I.e. activities should be tested to work in this mode (and in others as well).<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 -a --clean<br />
./sugar-jhbuild run<br />
<br />
The use of -a and --clean flags are needed when a file is removed so that autogen.sh is run. '''Note:''' Some packages, e.g., squeak and etoys, don't have a ''make clean''. Just ignore the error.<br />
<br />
== If build breaks after an update ==<br />
<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].<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 />
== 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 />
* [[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[http://en.flossmanuals.net/sugar]<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>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Jhbuild&diff=37389Development Team/Jhbuild2009-09-15T05:20:48Z<p>Skierpage: intro paragraph, various cleanup</p>
<hr />
<div><noinclude>{{Translations}}{{GoogleTrans-en}}{{TOCright}}</noinclude><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.<br />
It can also run a Sugar session in a window on your desktop using the [[wikipedia:Xephyr]] nested X window server.<br />
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 />
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).<br />
<br />
==Check distro-specific instructions==<br />
<br />
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:<br />
<br />
* [[/Debian | Debian]]<br />
* [[/Fedora | Fedora]]<br />
:Here are some [http://www.youtube.com/profile?user=pleabargain&view=videos&query=jhbuild videos of the Fedora jhbuild install process]. <br />
* [[/Ubuntu | Ubuntu]]<br />
* [[/Mandriva | Mandriva]]<br />
<br />
==Some general advice==<br />
<br />
Note: Like most other Unix applications, sugar-jhbuild should never be run as root. It may easily screw up your whole system and/or break in unexpected ways if you do. If you get any permissions error, there's something wrong with your installation that should be fixed.<br />
<br />
If you're stuck or if you get strange errors, feel free to ask for help on the [[Sugar_Labs/Contacts#irc.freenode.net_channels|#sugar IRC channel]] or the [[Sugar_Labs/Contacts#Developer_Lists|sugar-devel mailing list]]. Don't waste too much time chasing strange problems: usually it's caused by some basic, easy to fix problem. You might also want to check the [http://dev.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=sugar-jhbuild bug tracker] to see if it's a known issue.<br />
<br />
==Jhbuild FAQ==<br />
Q: <br />
<dgd> jhbuild build on fedora11 requires 29 packages but on Ubuntu904 38... should I be concerned with the difference in number?<br />
A:<br />
<sdziallas> dgd: this can be caused by different packaging policies...>>><dgd> sdziallas, ergo not a reason for concern, thanks!<br />
<br />
definitely do not compile as root with jhbuild -- you'll run into funky problems -- Colin A. :)<br />
<br />
==Prerequisites==<br />
; python<br />
: The sugar-jhbuild command is a Python script, so you need the Python interpreter.<br />
; git<br />
: To get the source code of sugar-jhbuild itself and many other Sugar packages you need the <tt>git</tt> command-line tool from the distributed version control system of the same name.<br />
; svn<br />
: A few packages (as of September 2009, only squeak) do not yet use git, and you need the <tt>svn</tt> command-line tool from the Subversion version control system to get their source code.<br />
<br />
These should be enough to run sugar-jhbuild on a typical Linux or Mac installation. Running <tt>sugar-jhbuild depscheck</tt> (see below) will probably list dozens of additional required packages.<br />
<br />
==Check out sugar-jhbuild==<br />
<br />
In a suitable directory (i.e. usually your user's home directory i.e. /home/yourusername/~), execute<br />
git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild<br />
<br />
::Make sure you are in the _user's_ home directory<br />
:: video http://www.youtube.com/watch?v=Tdr1bs4rQ_s<br />
<br />
You'll know if it worked if you get something like this:<br />
<pre><br />
localhost ~]$ git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild<br />
Initialized empty Git repository in /home/denny/sugar-jhbuild/.git/<br />
remote: Counting objects: 4688, done.<br />
remote: Compressing objects: 100% (1998/1998), done.<br />
remote: Total 4688 (delta 2759), reused 4488 (delta 2638)<br />
Receiving objects: 100% (4688/4688), 1.86 MiB | 197 KiB/s, done.<br />
Resolving deltas: 100% (2759/2759), done.<br />
</pre><br />
<br />
==Build sugar base system and its dependencies==<br />
<br />
Go into the directory you created and start the build. It takes about 30 minutes on a 1.6ghz machine with a wireless G connection.<br />
<br />
cd sugar-jhbuild<br />
./sugar-jhbuild update<br />
./sugar-jhbuild depscheck<br />
./sugar-jhbuild build<br />
::[http://www.youtube.com/results?search_query=pleabargain+jhbuild&search_type=&aq=f Here are videos of the process]. Before saying that [http://www.youtube.com/ Youtube] is unfriendly to Linux because of the flash player, try installing it. [http://get.adobe.com/flashplayer/ Adobe flash works] on my Ubuntu 9.04 and Fedora 11 without hitch.<br />
<br />
And now run it.<br />
./sugar-jhbuild run<br />
<br />
If it doesn't run or you have other problems read on.<br />
=== Dealing with dependencies ===<br />
<br />
''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).<br />
<br />
If you notice that there's a package missing from the <code>./sugar-jhbuild depscheck </code> output (i.e. it's required for Sugar to work properly and not installed, but depscheck does not mention it), please [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 file a bug report] (login required first, but currently no automatic redirection to login page) against the sugar-jhbuild Component in the [http://dev.sugarlabs.org/ Sugar Labs bug tracker].<br />
<br />
===Some tips and known issues===<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.<br />
*25 Aug 9: hulahop doesnt' build correctly. http://lists.sugarlabs.org/archive/sugar-devel/2009-August/018540.html The 'fix' is running autoconf.<br />
::Question. How do you run autoconf to fix this problem?<br />
::: when you get asked because of the error, choose the configure stage<br />
<br />
== Run Sugar ==<br />
<br />
This command launches the Sugar emulator in a nested X session:<br />
<br />
./sugar-jhbuild run<br />
<br />
To exit the emulator, press Alt-Q.<br />
<br />
To set debug variables, modify <code>~/.sugar/debug</code> (this file will be created on first run of Sugar).<br />
<br />
Note that due to a [http://dev.sugarlabs.org/ticket/342 bug in Xephyr] your keyboard might not work as expected. A partial workaround is to run <code>setxkbmap &lt;keymap name&gt;</code> by adding this command line to <code>~/.sugar/debug</code>. Most "regular" keys should work fine after that, some "special keys" (e.g. cursor up/down) might still refuse to operate as intended.<br />
<br />
The "keymap name" usually is a two letter country code, e.g. "de" for german or "fr" for french.<br />
<br />
== Running multiple instances ==<br />
To run an additional instance of sugar, you can start the second instance 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 fullscreen or specify a size (in pixels):<br />
<br />
./sugar-jhbuild run sugar-emulator --fullscreen<br />
./sugar-jhbuild run sugar-emulator --dimensions 1200x900<br />
<br />
The default size of 800x600 is currently the minimum that should work without issues. I.e. activities should be tested to work in this mode (and in others as well).<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 -a --clean<br />
./sugar-jhbuild run<br />
<br />
The use of -a and --clean flags are needed when a file is removed so that autogen.sh is run. '''Note:''' Some packages, e.g., squeak and etoys, don't have a ''make clean''. Just ignore the error.<br />
<br />
== If build breaks after an update ==<br />
<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].<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 />
== 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 />
* [[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[http://en.flossmanuals.net/sugar]<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]]nested in</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Jhbuild&diff=37381Development Team/Jhbuild2009-09-15T04:48:28Z<p>Skierpage: /* Run an individual activity */ use formatting, not square brackets</p>
<hr />
<div><noinclude>{{Translations}}{{GoogleTrans-en}}{{TOCright}}</noinclude><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 />
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).<br />
<br />
==Check distro-specific instructions==<br />
<br />
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:<br />
<br />
* [[/Debian | Debian]]<br />
* [[/Fedora | Fedora]]<br />
:Here are some [http://www.youtube.com/profile?user=pleabargain&view=videos&query=jhbuild videos of the Fedora jhbuild install process]. <br />
* [[/Ubuntu | Ubuntu]]<br />
* [[/Mandriva | Mandriva]]<br />
<br />
==Some general advice==<br />
<br />
Note: Like most other Unix applications, sugar-jhbuild should never be run as root. It may easily screw up your whole system and/or break in unexpected ways if you do. If you get any permissions error, there's something wrong with your installation that should be fixed.<br />
<br />
If you're stuck or if you get strange errors, feel free to ask for help on the [[Sugar_Labs/Contacts#irc.freenode.net_channels|#sugar IRC channel]] or the [[Sugar_Labs/Contacts#Developer_Lists|sugar-devel mailing list]]. Don't waste too much time chasing strange problems: usually it's caused by some basic, easy to fix problem. You might also want to check the [http://dev.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=sugar-jhbuild bug tracker] to see if it's a known issue.<br />
<br />
==Jhbuild FAQ==<br />
Q: <br />
<dgd> jhbuild build on fedora11 requires 29 packages but on Ubuntu904 38... should I be concerned with the difference in number?<br />
A:<br />
<sdziallas> dgd: this can be caused by different packaging policies...>>><dgd> sdziallas, ergo not a reason for concern, thanks!<br />
<br />
definitely do not compile as root with jhbuild -- you'll run into funky problems -- Colin A. :)<br />
<br />
==Prequisites==<br />
; python<br />
: The sugar-jhbuild command is a Python script, so you need the Python interpreter.<br />
; git<br />
: To get the source code of sugar-jhbuild itself and many other Sugar packages you need the <tt>git</tt> command-line tool from the distributed version control system of the same name.<br />
; svn<br />
: A few packages (as of September 2009, only squeak) do not yet use git, and you need the <tt>svn</tt> command-line tool from the Subversion version control system to get their source code.<br />
<br />
These should be enough to run sugar-jhbuild on a typical Linux or Mac installation. Running <tt>sugar-jhbuild depscheck</tt> (see below) will probably list dozens of additional required packages.<br />
<br />
==Check out sugar-jhbuild==<br />
<br />
In a suitable directory (i.e. usually your user's home directory i.e. /home/yourusername/~), execute<br />
git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild<br />
<br />
::Make sure you are in the _user's_ home directory<br />
:: video http://www.youtube.com/watch?v=Tdr1bs4rQ_s<br />
<br />
You'll know if it worked if you get something like this:<br />
<pre><br />
localhost ~]$ git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild<br />
Initialized empty Git repository in /home/denny/sugar-jhbuild/.git/<br />
remote: Counting objects: 4688, done.<br />
remote: Compressing objects: 100% (1998/1998), done.<br />
remote: Total 4688 (delta 2759), reused 4488 (delta 2638)<br />
Receiving objects: 100% (4688/4688), 1.86 MiB | 197 KiB/s, done.<br />
Resolving deltas: 100% (2759/2759), done.<br />
</pre><br />
<br />
==Build sugar base system and its dependencies==<br />
<br />
Go into the directory you created and start the build. It takes about 30 minutes on a 1.6ghz machine with a wireless G connection.<br />
<br />
cd sugar-jhbuild<br />
./sugar-jhbuild update<br />
./sugar-jhbuild depscheck<br />
./sugar-jhbuild build<br />
::[http://www.youtube.com/results?search_query=pleabargain+jhbuild&search_type=&aq=f Here are videos of the process]. Before saying that [http://www.youtube.com/ Youtube] is unfriendly to Linux because of the flash player, try installing it. [http://get.adobe.com/flashplayer/ Adobe flash works] on my Ubuntu 9.04 and Fedora 11 without hitch.<br />
<br />
And now run it.<br />
./sugar-jhbuild run<br />
<br />
If it doesn't run or you have other problems read on.<br />
=== Dealing with dependencies ===<br />
<br />
''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).<br />
<br />
If you notice that there's a package missing from the <code>./sugar-jhbuild depscheck </code> output (i.e. it's required for Sugar to work properly and not installed, but depscheck does not mention it), please [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 file a bug report] (login required first, but currently no automatic redirection to login page) against the sugar-jhbuild Component in the [http://dev.sugarlabs.org/ Sugar Labs bug tracker].<br />
<br />
===Some tips and known issues===<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.<br />
*25 Aug 9: hulahop doesnt' build correctly. http://lists.sugarlabs.org/archive/sugar-devel/2009-August/018540.html The 'fix' is running autoconf.<br />
::Question. How do you run autoconf to fix this problem?<br />
::: when you get asked because of the error, choose the configure stage<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 />
Note that due to a [http://dev.sugarlabs.org/ticket/342 bug in Xephyr] your keyboard might not work as expected. A partial workaround is to run <code>setxkbmap &lt;keymap name&gt;</code> in <code>~/.sugar/debug</code> (this file will be created on first run of Sugar). Most "regular" keys should work fine after that, some "special keys" (e.g. cursor up/down) might still refuse to operate as intended.<br />
<br />
The "keymap name" usually is a two letter country code, e.g. "de" for german or "fr" for french.<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 fullscreen or specify a size (in pixels):<br />
<br />
./sugar-jhbuild run sugar-emulator --fullscreen<br />
./sugar-jhbuild run sugar-emulator --dimensions 1200x900<br />
<br />
The default size of 800x600 is currently the minimum that should work without issues. I.e. activities should be tested to work in this mode (and in others as well).<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 -a --clean<br />
./sugar-jhbuild run<br />
<br />
The use of -a and --clean flags are needed when a file is removed so that autogen.sh is run. '''Note:''' Some packages, e.g., squeak and etoys, don't have a ''make clean''. Just ignore the error.<br />
<br />
== If build breaks after an update ==<br />
<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].<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 />
== 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 />
* [[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[http://en.flossmanuals.net/sugar]<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>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Jhbuild&diff=37376Development Team/Jhbuild2009-09-15T02:53:05Z<p>Skierpage: /* Prequisites */ mention that many more packages will be needed later.</p>
<hr />
<div><noinclude>{{Translations}}{{GoogleTrans-en}}{{TOCright}}</noinclude><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 />
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).<br />
<br />
==Check distro-specific instructions==<br />
<br />
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:<br />
<br />
* [[/Debian | Debian]]<br />
* [[/Fedora | Fedora]]<br />
:Here are some [http://www.youtube.com/profile?user=pleabargain&view=videos&query=jhbuild videos of the Fedora jhbuild install process]. <br />
* [[/Ubuntu | Ubuntu]]<br />
* [[/Mandriva | Mandriva]]<br />
<br />
==Some general advice==<br />
<br />
Note: Like most other Unix applications, sugar-jhbuild should never be run as root. It may easily screw up your whole system and/or break in unexpected ways if you do. If you get any permissions error, there's something wrong with your installation that should be fixed.<br />
<br />
If you're stuck or if you get strange errors, feel free to ask for help on the [[Sugar_Labs/Contacts#irc.freenode.net_channels|#sugar IRC channel]] or the [[Sugar_Labs/Contacts#Developer_Lists|sugar-devel mailing list]]. Don't waste too much time chasing strange problems: usually it's caused by some basic, easy to fix problem. You might also want to check the [http://dev.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=sugar-jhbuild bug tracker] to see if it's a known issue.<br />
<br />
==Jhbuild FAQ==<br />
Q: <br />
<dgd> jhbuild build on fedora11 requires 29 packages but on Ubuntu904 38... should I be concerned with the difference in number?<br />
A:<br />
<sdziallas> dgd: this can be caused by different packaging policies...>>><dgd> sdziallas, ergo not a reason for concern, thanks!<br />
<br />
definitely do not compile as root with jhbuild -- you'll run into funky problems -- Colin A. :)<br />
<br />
==Prequisites==<br />
; python<br />
: The sugar-jhbuild command is a Python script, so you need the Python interpreter.<br />
; git<br />
: To get the source code of sugar-jhbuild itself and many other Sugar packages you need the <tt>git</tt> command-line tool from the distributed version control system of the same name.<br />
; svn<br />
: A few packages (as of September 2009, only squeak) do not yet use git, and you need the <tt>svn</tt> command-line tool from the Subversion version control system to get their source code.<br />
<br />
These should be enough to run sugar-jhbuild on a typical Linux or Mac installation. Running <tt>sugar-jhbuild depscheck</tt> (see below) will probably list dozens of additional required packages.<br />
<br />
==Check out sugar-jhbuild==<br />
<br />
In a suitable directory (i.e. usually your user's home directory i.e. /home/yourusername/~), execute<br />
git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild<br />
<br />
::Make sure you are in the _user's_ home directory<br />
:: video http://www.youtube.com/watch?v=Tdr1bs4rQ_s<br />
<br />
You'll know if it worked if you get something like this:<br />
<pre><br />
localhost ~]$ git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild<br />
Initialized empty Git repository in /home/denny/sugar-jhbuild/.git/<br />
remote: Counting objects: 4688, done.<br />
remote: Compressing objects: 100% (1998/1998), done.<br />
remote: Total 4688 (delta 2759), reused 4488 (delta 2638)<br />
Receiving objects: 100% (4688/4688), 1.86 MiB | 197 KiB/s, done.<br />
Resolving deltas: 100% (2759/2759), done.<br />
</pre><br />
<br />
==Build sugar base system and its dependencies==<br />
<br />
Go into the directory you created and start the build. It takes about 30 minutes on a 1.6ghz machine with a wireless G connection.<br />
<br />
cd sugar-jhbuild<br />
./sugar-jhbuild update<br />
./sugar-jhbuild depscheck<br />
./sugar-jhbuild build<br />
::[http://www.youtube.com/results?search_query=pleabargain+jhbuild&search_type=&aq=f Here are videos of the process]. Before saying that [http://www.youtube.com/ Youtube] is unfriendly to Linux because of the flash player, try installing it. [http://get.adobe.com/flashplayer/ Adobe flash works] on my Ubuntu 9.04 and Fedora 11 without hitch.<br />
<br />
And now run it.<br />
./sugar-jhbuild run<br />
<br />
If it doesn't run or you have other problems read on.<br />
=== Dealing with dependencies ===<br />
<br />
''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).<br />
<br />
If you notice that there's a package missing from the <code>./sugar-jhbuild depscheck </code> output (i.e. it's required for Sugar to work properly and not installed, but depscheck does not mention it), please [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 file a bug report] (login required first, but currently no automatic redirection to login page) against the sugar-jhbuild Component in the [http://dev.sugarlabs.org/ Sugar Labs bug tracker].<br />
<br />
===Some tips and known issues===<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.<br />
*25 Aug 9: hulahop doesnt' build correctly. http://lists.sugarlabs.org/archive/sugar-devel/2009-August/018540.html The 'fix' is running autoconf.<br />
::Question. How do you run autoconf to fix this problem?<br />
::: when you get asked because of the error, choose the configure stage<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 />
Note that due to a [http://dev.sugarlabs.org/ticket/342 bug in Xephyr] your keyboard might not work as expected. A partial workaround is to run <code>setxkbmap &lt;keymap name&gt;</code> in <code>~/.sugar/debug</code> (this file will be created on first run of Sugar). Most "regular" keys should work fine after that, some "special keys" (e.g. cursor up/down) might still refuse to operate as intended.<br />
<br />
The "keymap name" usually is a two letter country code, e.g. "de" for german or "fr" for french.<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 fullscreen or specify a size (in pixels):<br />
<br />
./sugar-jhbuild run sugar-emulator --fullscreen<br />
./sugar-jhbuild run sugar-emulator --dimensions 1200x900<br />
<br />
The default size of 800x600 is currently the minimum that should work without issues. I.e. activities should be tested to work in this mode (and in others as well).<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 -a --clean<br />
./sugar-jhbuild run<br />
<br />
The use of -a and --clean flags are needed when a file is removed so that autogen.sh is run. '''Note:''' Some packages, e.g., squeak and etoys, don't have a ''make clean''. Just ignore the error.<br />
<br />
== If build breaks after an update ==<br />
<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].<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 />
== 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 />
* [[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[http://en.flossmanuals.net/sugar]<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>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Development_Team/Jhbuild&diff=37368Development Team/Jhbuild2009-09-15T00:57:46Z<p>Skierpage: Add /*Prerequisites */ mentioning python, git, svn</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 />
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).<br />
<br />
==Check distro-specific instructions==<br />
<br />
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:<br />
<br />
* [[/Debian | Debian]]<br />
* [[/Fedora | Fedora]]<br />
:Here are some [http://www.youtube.com/profile?user=pleabargain&view=videos&query=jhbuild videos of the Fedora jhbuild install process]. <br />
* [[/Ubuntu | Ubuntu]]<br />
* [[/Mandriva | Mandriva]]<br />
<br />
==Some general advice==<br />
<br />
Note: Like most other Unix applications, sugar-jhbuild should never be run as root. It may easily screw up your whole system and/or break in unexpected ways if you do. If you get any permissions error, there's something wrong with your installation that should be fixed.<br />
<br />
If you're stuck or if you get strange errors, feel free to ask for help on the [[Sugar_Labs/Contacts#irc.freenode.net_channels|#sugar IRC channel]] or the [[Sugar_Labs/Contacts#Developer_Lists|sugar-devel mailing list]]. Don't waste too much time chasing strange problems: usually it's caused by some basic, easy to fix problem. You might also want to check the [http://dev.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=sugar-jhbuild bug tracker] to see if it's a known issue.<br />
<br />
==Jhbuild FAQ==<br />
Q: <br />
<dgd> jhbuild build on fedora11 requires 29 packages but on Ubuntu904 38... should I be concerned with the difference in number?<br />
A:<br />
<sdziallas> dgd: this can be caused by different packaging policies...>>><dgd> sdziallas, ergo not a reason for concern, thanks!<br />
<br />
definitely do not compile as root with jhbuild -- you'll run into funky problems -- Colin A. :)<br />
<br />
==Prequisites==<br />
; python<br />
: The sugar-jhbuild command is a Python script, so you need the Python interpreter.<br />
; git<br />
: To get the source code of sugar-jhbuild itself and many other Sugar packages you need the <tt>git</tt> command-line tool from the distributed version control system of the same name.<br />
; svn<br />
: A few packages (as of September 2009, only squeak) do not yet use git, and you need the <tt>svn</tt> command-line tool from the Subversion version control system to get their source code.<br />
<br />
==Check out sugar-jhbuild==<br />
<br />
In a suitable directory (i.e. usually your user's home directory i.e. /home/yourusername/~), execute<br />
git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild<br />
<br />
::Make sure you are in the _user's_ home directory<br />
:: video http://www.youtube.com/watch?v=Tdr1bs4rQ_s<br />
<br />
You'll know if it worked if you get something like this:<br />
<pre><br />
localhost ~]$ git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild<br />
Initialized empty Git repository in /home/denny/sugar-jhbuild/.git/<br />
remote: Counting objects: 4688, done.<br />
remote: Compressing objects: 100% (1998/1998), done.<br />
remote: Total 4688 (delta 2759), reused 4488 (delta 2638)<br />
Receiving objects: 100% (4688/4688), 1.86 MiB | 197 KiB/s, done.<br />
Resolving deltas: 100% (2759/2759), done.<br />
</pre><br />
<br />
==Build sugar base system and its dependencies==<br />
<br />
Go into the directory you created and start the build. It takes about 30 minutes on a 1.6ghz machine with a wireless G connection.<br />
<br />
cd sugar-jhbuild<br />
./sugar-jhbuild update<br />
./sugar-jhbuild depscheck<br />
./sugar-jhbuild build<br />
::[http://www.youtube.com/results?search_query=pleabargain+jhbuild&search_type=&aq=f Here are videos of the process]. Before saying that [http://www.youtube.com/ Youtube] is unfriendly to Linux because of the flash player, try installing it. [http://get.adobe.com/flashplayer/ Adobe flash works] on my Ubuntu 9.04 and Fedora 11 without hitch.<br />
<br />
And now run it.<br />
./sugar-jhbuild run<br />
<br />
If it doesn't run or you have other problems read on.<br />
=== Dealing with dependencies ===<br />
<br />
''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).<br />
<br />
If you notice that there's a package missing from the <code>./sugar-jhbuild depscheck </code> output (i.e. it's required for Sugar to work properly and not installed, but depscheck does not mention it), please [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 file a bug report] (login required first, but currently no automatic redirection to login page) against the sugar-jhbuild Component in the [http://dev.sugarlabs.org/ Sugar Labs bug tracker].<br />
<br />
===Some tips and known issues===<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.<br />
*25 Aug 9: hulahop doesnt' build correctly. http://lists.sugarlabs.org/archive/sugar-devel/2009-August/018540.html The 'fix' is running autoconf.<br />
::Question. How do you run autoconf to fix this problem?<br />
::: when you get asked because of the error, choose the configure stage<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 />
Note that due to a [http://dev.sugarlabs.org/ticket/342 bug in Xephyr] your keyboard might not work as expected. A partial workaround is to run <code>setxkbmap &lt;keymap name&gt;</code> in <code>~/.sugar/debug</code> (this file will be created on first run of Sugar). Most "regular" keys should work fine after that, some "special keys" (e.g. cursor up/down) might still refuse to operate as intended.<br />
<br />
The "keymap name" usually is a two letter country code, e.g. "de" for german or "fr" for french.<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 fullscreen or specify a size (in pixels):<br />
<br />
./sugar-jhbuild run sugar-emulator --fullscreen<br />
./sugar-jhbuild run sugar-emulator --dimensions 1200x900<br />
<br />
The default size of 800x600 is currently the minimum that should work without issues. I.e. activities should be tested to work in this mode (and in others as well).<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 -a --clean<br />
./sugar-jhbuild run<br />
<br />
The use of -a and --clean flags are needed when a file is removed so that autogen.sh is run. '''Note:''' Some packages, e.g., squeak and etoys, don't have a ''make clean''. Just ignore the error.<br />
<br />
== If build breaks after an update ==<br />
<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].<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 />
== 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 />
* [[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[http://en.flossmanuals.net/sugar]<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>Skierpagehttps://wiki.sugarlabs.org/index.php?title=User_talk:Wade/Unified_Bundles&diff=35056User talk:Wade/Unified Bundles2009-08-10T02:45:42Z<p>Skierpage: /* Just open Browse! */ new section</p>
<hr />
<div>== Making FCAs inside other activities ==<br />
An interesting idea which might be relevant to this proposal is the spawning of FCAs from other activities. The general idea is that I created this killer Etoys app and I want to share it with the world, not as a journal entry but as a activity itself. LFaraone 23:17, 6 April 2009 (UTC)<br />
<br />
== Yet another scheme of implementing viewers ==<br />
startup scripts(launchers) could be parts of sugar itself and contain only metadata about viewer activity.<br />
<br />
It should mean that sugar all time has the full list of possible launchers. When user starts bundle with launcher mentioned in exec section, launcher will check if proper viewer activity is installed if it doesn't launcher will install it from ASLO, otherwise(for example in case of bad internet connection) distributor should preinstall these activities(anyway this case is only distribution specific).<br />
<br />
In that case we have list of stable launchers(since they don't have much code) and in anytime we could download last version of viewer activity from ASLO.<br />
<br />
[[User:Alsroot|Alsroot]] 00:40, 7 April 2009 (UTC)<br />
<br />
== Unified Objects ==<br />
<br />
See also [[Unified Objects]]<br />
<br />
[[User:Alsroot|Alsroot]] 06:14, 8 April 2009 (UTC)<br />
: A good parallel! [[User:Sj|+sj]] [[User Talk:Sj|<font color="#ff6996">+</font>]]<br />
<br />
== content viewers ==<br />
<br />
content viewers should get the functionality of being made as slide-shows. For example, inside the jukebox activity, one should be able to add various media files, i.e., a playlist. It would appear in the journal as a jukebox activity. The same with image viewer, creating slideshows of images. Just some thoughts on the idea that launching new viewer activities, and these viewer activities could be usefull. [[User:HoboPrimate|HoboPrimate]] 19:27, 10 April 2009 (UTC)<br />
<br />
== Just open Browse! ==<br />
<br />
A dedicated "Web Content Viewer" makes little sense. Just pass the file:/// URL to existing machinery to open a URL (thus opening up Browse) and declare victory!<br />
<br />
I don't see much benefit to opening web content in something that's sort of like Browse but isn't. Look at the 8.2.0 Help activity, the moment you follow an external URL you might as well be running Browse instead of the same code in a different skin.<br />
<br />
Any changes to Browse (like remembering your current location, annotating books, etc.) seem best handled by an extension, like the existing eReader one.<br />
<br />
-- [[User:Skierpage|Skierpage]] 02:45, 10 August 2009 (UTC)<br />
<br />
=== Mozilla can open compressed files, including bundles ===<br />
<br />
BTW, one trick of Mozilla code is that it can open compressed files using the jar: protocol;<br /><br />
<tt>jar:''protocol:/URL''!''/path/in/zip/file''</tt><br />
<br />
Thus the activity.info can tell Browse to open the URL jar:file:///home/olpc/Activities/SomeBrowserStuff.xo!/content/index.html and you need never unpack the ZIP file, browsing the HTML just works. I've verified this with the Net Bible collection, I believe it's true for other collections. -- [[User:Skierpage|Skierpage]] 02:45, 10 August 2009 (UTC)</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Features/Feature_Template&diff=33263Features/Feature Template2009-07-13T01:58:04Z<p>Skierpage: improve guideline</p>
<hr />
<div><noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude><br />
<br />
'''Comments and Explanations:'''<br />
<br />
There are comments (in italic) providing guidance to fill out each section, see also [[Features/Policy]]. '''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 />
''A sentence or two summarizing what this feature is and what it will do. This information is used for the overall feature summary page for each release.''<br />
<br />
== Owner ==<br />
''This should link to your home wiki page so we know who you are''<br />
* Name: [[User:AcountName| Your Name]]<br />
<br />
''Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or technical issues need to be resolved''<br />
* Email: <your email address so we can contact you, invite you to meetings, etc.><br />
<br />
== Current status ==<br />
* Targeted release: (SUGAR_VERSION)<br />
* Last updated: (DATE)<br />
* Percentage of completion: XX%<br />
<br />
== Detailed Description ==<br />
''Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better.''<br />
<br />
== Benefit to Sugar ==<br />
''What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will Sugar become a better platform or project because of this feature?''<br />
<br />
== Scope ==<br />
''What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?''<br />
<br />
== How To Test ==<br />
''This does not need to be a full-fledged document. Describe the dimensions of tests that this feature is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be.''<br />
<br />
''Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.''<br />
<br />
''A good "how to test" should answer these four questions:''<br />
<br />
* ''What special hardware / data / etc. is needed (if any)?<br />
* ''How do I prepare my system to test this feature? What packages need to be installed, config files edited, etc.?<br />
* ''What specific actions do I perform to check that the feature is working like it's supposed to?<br />
* ''What are the expected results of those actions?''<br />
<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 />
''What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like python?''<br />
<br />
== Contingency Plan ==<br />
''If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. If you feature is not completed in time we want to assure others that other parts of Sugar will not be in jeopardy.''<br />
<br />
== Documentation ==<br />
''Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved.''<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 --><br />
<br />
<br />
[[Category:Feature Page Incomplete]]<br />
[[Category:Feature]]<br />
----<br />
''You can add categories to tie features back to real deployments/schools requesting them, for example <nowiki>[[</nowiki>Category:Features requested by School Xyz]]''</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=0.86/Feature_List&diff=332620.86/Feature List2009-07-13T01:57:14Z<p>Skierpage: /* Feature Process */ surely "features into Sugar", not Fedora? Use actual page name.</p>
<hr />
<div>== Sugar 0.86 Accepted Features ==<br />
<br />
These features have been accepted by the Release Manager for the Sugar 0.86 Release.<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Complete !!Name !!Summary !!Updated<br />
|-<br />
| 0% || [[Features/Buddy_Positioning | Buddy Positioning]] || Use the identity of the neighborhood icons (buddy color or nick name) to seed the position to get a more stable positioning in the neighborhood view. || 2009-06-15<br />
|- <br />
|}<br />
<br />
== Feature Process ==<br />
<br />
* The process for adding, proposing, and accepting new features into Sugar is on the [[Features/Policy]] page.<br />
* The deadline for proposing and completing new features is the ''Feature Freeze'' on the [[0.86/Roadmap#Schedule | 0.86 Schedule]] <br />
* Feature pages in process but not targeted for a particular release can be found in [[:Category:Feature Page Incomplete]]<br />
<br />
<br />
<br />
[[Category:Feature]]</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Features/Policy&diff=33261Features/Policy2009-07-13T01:54:59Z<p>Skierpage: /* How do I propose a feature idea, even if I can't build it myself? */ better explanation of copying the feature template</p>
<hr />
<div><noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude><br />
<br />
= I want to know... =<br />
== What is a feature? ==<br />
A feature is defined as a significant change or enhancement to the version of Sugar currently under development that may or may not include new packages.<br />
<br />
Features are usually considered to meet one or more of the following objectives:<br />
<br />
# highly user visible changes (beyond artwork or theme changes)<br />
# improvements or changes that require non-trivial cross-package integration<br />
# exciting new capabilities we can trumpet Sugar having -- some of this is good public relations. Some examples might include:<br />
#* adding of new functionality to the Sugar platform Examples: version support in the datastore, file-sharing<br />
#* work Sugar contributors are doing upstream as part of their work for Sugar<br />
#* new features from upstream that we are making available in Sugar for the first time<br />
# significant enough that if not completed properly or without a proper backup plan could delay the release<br />
# noteworthy enough to call out in the release notes<br />
<br />
== What is an enhancement? ==<br />
Enhancements are:<br />
# Less documented improvements to a Sugar release which do follow the feature process and do not fit the feature definition above<br />
# Added to the release summary by anyone under heading of Other Enhancements. The release summary for each release lives in the following wiki branches:<br> | [[0.82]] | [[0.84]] | [[0.86]] | [[0.88]] | <br />
#* The wiki template, <nowiki>{{Upcoming Stable Release}}</nowiki> can be used for convenience and general references.<br />
<br />
== Is ''<XXX>'' a feature? ==<br />
It's sometimes easy to mistake new packages, or enhancements, for features. Features have a very specific definition, but here are some questions to ask yourself before engaging the feature process.<br />
<br />
# Is this change very visible to end users?<br />
#* In this case "end user" means "someone in the audience for this change", which could be desktop users, developers, or system administrators. <br />
# Does this change require intervention?<br />
#* This might be a configuration file format change, or something else that will perturb unsuspecting end users.<br />
#* A change that requires a very simple intervention to revert behavior is not necessarily a feature. <br />
# Is this something that will interest the lay press?<br />
#* The lay press in this case includes Education-oriented sites.<br />
<br />
== What does the feature process ''look'' like? ==<br />
Individual features are tracked on separate wiki pages in the Features/ namespace. Individual features are organized using ''categories''.<br />
<br />
# New feature ideas may be added at any time to the wiki<br />
#* Your Feature has the [[:Category:Feature Page Incomplete]]<br />
# New feature desired for a particular release is targeted as such and feature page is complete<br />
#* Feature owners believes feature is ready for presentation to the Release Manager for ''acceptance''<br />
#* Move your feature to the [[:Category:Feature Ready for Release Manager]]<br />
# Feature passes sanity check by Release Manager<br />
## Accepted: The Release Manager moves the Feature to <nowiki>[[Category:Feature Accepted Sucrose <version>]]</nowiki>, such as, [[:Category:Feature Accepted Sucrose {{Upcoming Stable Release}}]].<br />
## Denied: The Release Manager moves the Feature to [[:Category:Feature Page Incomplete]] for rework or future resubmission<br />
<br />
= Starting the process =<br />
== How do I propose a feature idea, even if I can't build it myself? ==<br />
Community members are encouraged to create new pages for features that enhance or improve Sugar. Anyone can propose new features for Sugar by following these steps:<br />
<br />
# Copy the markup from the [[Features/Feature_Template]]<br />
#* [{{fullurl:Features/Feature_Template|action=edit}} click here to load it]<br />
#* select all the markup and copy<br />
# Add a new wiki subpage named [[Features]]/''Your feature name'' and paste the template markup into it.<br />
# Add details for each of the sections required in the [[Features/Feature_Template | Template]].<br />
#* The template adds <code><nowiki>[[Category:Feature Page Incomplete]]</nowiki></code> to the wiki page.<br />
# Put a watch on your page by clicking the watch link so you can see changes other people make to your page. <br />
#* You must be logged in to do this. <br />
<br />
These pages do not have to be complete and are useful for brainstorming or work in process.<br />
<br />
== How do I propose a feature I'm going to help build or own? ==<br />
<br />
In order to be considered an official feature accepted for the next Sugar release, the feature should be formally documented on a separate wiki page which includes the following information.<br />
<br />
# Summary of the feature<br />
# A designated owner with a link to Sugar home page. The owner is responsible for:<br />
## making sure the feature is completed according to the schedule<br />
## communicating periodic status<br />
## attending feature status meetings<br />
# Current status<br />
## last updated<br />
## estimated percentage of completion<br />
# Description of the new feature<br />
# Detailed explanation of what the new feature will do and how it will be implemented<br />
# Benefit to Sugar<br />
# Scope<br />
# How To Test<br />
# Dependencies--on other packages or features<br />
# Contingency plan<br />
# Link to documentation<br />
# Important information for release notes<br />
<br />
<br />
* Put a ''watch'' on your page so you are notified when its category changes. You must be logged in, then click the ''watch'' link at the top of the page.<br />
* A blank template is available at [[Features/Feature Template]]<br />
<br />
== What does the feature form look like? ==<br />
[[Features/Feature_Template | Feature Template]]<br />
<br />
== How does a feature get accepted? ==<br />
Acceptance by the Release Manger is a sanity check, presumed in most cases to be a formality, to ensure that new features compliment Sugar guidelines and is manageable, prior to publicizing as officially targeted for the next release.<br />
<br />
Feature acceptance is agreement by the Release Manager that a particular feature is:<br />
# consistent with the goals and policies of Sugar<br />
# supported by the Sugar community<br />
# suitable for listing as an Official Feature of the next release of Sugar<br />
# important to track prior to feature freeze and could affect timeliness of release<br />
<br />
== What do I need to do over the course of the release cycle? ==<br />
# Feature pages should be updated to reflect the current status of the feature by the following milestones on the [[Development_Team/Release/Roadmap | Release schedule]]:<br />
#* Alpha Freeze --features not 100% complete at alpha should be updated no less than every two weeks<br />
#* Beta Freeze<br />
# One week prior to Beta Freeze all features will evaluated based on test results to date<br />
# At Beta Freeze all feature pages should be at 100% completion, and if necessary, the feature page adjusted to reflect everything completed (so as to reflect 100% completion).<br />
# The Release Manager will send individual reminders and announcements to sugar-devel list as necessary<br />
# A summary status for all the features targeted to a particular release will be collected on a summary page which references and briefly explains the feature.<br />
#* The Release Manager will maintain this page.<br />
#* This page will be located at: <nowiki>http://wiki.sugarlabs.org/go/<current release>/Feature List</nowiki>, such as [[{{Upcoming Stable Release}}/Feature List]]<br />
# Reminders to developers about upcoming feature deadlines will be sent to sugar-devel<br />
# Nag mail to developers with delinquent feature page updates will be emailed privately and shamed in a nice way on sugar-devel<br />
<br />
= During the process =<br />
<br />
== How do I show the status of a feature I own? ==<br />
Feature pages should be updated to reflect the current status of the feature.<br />
<br />
== Are there deadlines for features? ==<br />
* New features may be proposed (using the guidelines above) and accepted no later than the '''Feature Freeze''' milestone<br />
* By the time of Alpha freeze:<br />
** the "Scope" section of the feature must be fleshed out and well defined so that the extent of the work to be completed is understood.<br />
** defined criteria for success or failure of the feature.<br />
** '''fixme''': need to clarify this section more<br />
* By the time of Alpha Freeze, test plans must be complete.<br />
* New features must be feature complete or close enough to completion by Alpha freeze that a majority of its functionality can be suitably tested--the "feature is testable". <br />
* At ''feature freeze'' the Release Manager will present a final feature status to the release team which the release team will review and comment on<br />
* After final review by the Release Manager at Feature Freeze the final ''accepted Feature'' list (Release Road Map) will be publicly announced.<br />
<br />
== What is the process for dropping a feature? ==<br />
A feature will be proposed for a vote to be dropped from the ''Accepted Feature'' list by the Release Manager if one of the following occurs:<br />
<br />
* Feature is incomplete or not testable at ''Feature Freeze''<br />
* Feature owner fails to consistently provide status.<br />
<br />
Partially completed features can still be listed as ''accepted'' for the upcoming release if the wiki page describing the feature is tailored to reflect the completed work. Dropped features can be proposed again for inclusion in the next release.<br />
<br />
= Policy questions =<br />
== Why does this process matter or why should I care? ==<br />
We want to actively promote new features to the world. As a Sugar developer you benefit from this promotion by attracting testers and more users to make it better.<br />
<br />
== Is there a way to get an exception from this policy? ==<br />
Features not meeting the guidelines above may be brought to the Release Manager for review.<br />
<br />
== Who is responsible for this process? ==<br />
The person responsible for managing the release, the Release Manager, is designated by the community to fulfill the task.<br />
<br />
The feature owner is responsible for watching any owned pages for state changes, using the wiki watch feature.<br />
<br />
Current Release Manager: Simon Schampijer<br />
<br />
[[Category:Feature]]</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Design_Team/Proposals/Toolbars/Activity-wide_Toolbar_mock-ups&diff=33260Design Team/Proposals/Toolbars/Activity-wide Toolbar mock-ups2009-07-13T00:28:20Z<p>Skierpage: Category:Proposal</p>
<hr />
<div><noinclude>{{TOCright}}<!-- START OF BLOCK -- 1. COPY & PASTE this BLOCK to below the END OF BLOCK line.<br />
2. PASTE it before any pre-existing proposal,<br />
3. then OVERWRITE the place holders with your information,<br />
4. and DELETE the START & END OF BLOCK instruction lines.<br />
5. Click [Show preview] to check formatting, and adjust as necessary.<br />
6. Click [Save page] to complete the edit.<br />
--><br />
===<Your proposal's pithy name here>=== <!-- Leave the === prefix and suffix ===<br />
--><br />
:'''Rationale:''' <!-- leave this line --><br />
:: <Your rationale here><br />
:'''Features:''' <!-- leave this line --><br />
:# <1st feature here><br />
:# <2nd feature here><br />
:'''Implementation Details:''' <!-- leave this line --><br />
:: <Details here><br />
:'''Reviewer Comments:''' <!-- leave this line --><br />
:: comments here <!-- reviewers: leave the :: prefix and overwrite up to this signature code: --~~~~ <br />
END OF BLOCK line --></noinclude><br />
<!-- Pre-existing Proposal Block --><br />
<br />
==[[Design Team/Proposals/Toolbars/Icons|Icons]]==<br />
<br />
=== Activity wide Toolbar mock-ups ===<br />
<br />
TODO:<br />
* Lots and lots of icon work<br />
** find meaningful visual replacements for all text tab labels<br />
** improve icon design for the stand in versions used below<br />
* Icons should (somehow) reveal their original tab text names<br />
** a still open design question<br />
** really text + icons would be clearer, but space is limited<br />
<br />
==== Top level Activity toolbar for TurtleArt ====<br />
[[Image:toolbar_mockup_gary_turtle_art-52_activity.png|thumb|centre|640px|Example showing basic top level Activity toolbar. Note that I am not trying to redesign TA's toolbar user interface, I am trying to swap in the new proposed design without changing any existing tab/tool design from Walter. The top level Activity toolbar is present at all times. It provides access to naming, collaboration, icons for existing TA tabs, the keep (version) icon, the stop icon.]]<br />
<br />
==== Icon replacement of "Share with:" menu ====<br />
[[Image:toolbar_mockup_gary_turtle_art-52_share_with.png|thumb|centre|640px|Share with is replaced with an button icon and palette to provide enough space for the tabs to move into the main Activity toolbar as icons. Note that this leaves just enough space for six replacement tab icons (enough to cover the existing Write toolbar tab content). Note that the toolbar icon would change to indicate the collaboration state.]]<br />
<br />
===== Private icon v1 =====<br />
[[Image:toolbar_mockup_gary_share_with.png|thumb|centre|640px|Nice and simple modification to the "private" icon, as shown in existing mock-ups]]<br />
<br />
===== Private icon v2 =====<br />
[[Image:toolbar_mockup_gary_share_with_v2.png|thumb|centre|640px|Small "private" rework trying to indicate isolation/boundary. Based on the media-playback-start icon.]]<br />
<br />
==== Example TrutleArt "Project" tab ====<br />
[[Image:toolbar_mockup_gary_turtle_art-52_project.png|thumb|centre|640px|I've used TA's Activity icon for the primary "project" tab, this could be a technique used for all default tab contents if needed. We could also design a generic "project" icon and perhaps use it in other activities. Note that the secondary toolbar is pinned open (it's icon was clicked once), an that this triggers a resize of the below canvas to fit the space (well see lot's of Activity bugs with resizing, but we already have this issue to fix due to now needing to support screen pixel dimensions other than 1200x900).]]<br />
<br />
==== Example TrutleArt "Edit" tab ====<br />
[[Image:toolbar_mockup_gary_turtle_art-52_edit.png|thumb|centre|640px|using Eben's generic icon for edit here, it's a good strong, memorable silhouette icon (though it may not be clear in all cultures). Worth noting that icons that have clear names are going to be important, imaging a teacher trying to explain which icon to click or in text documentation, i.e "Click the scissors icon if you need to use copy and paste."]]<br />
<br />
==== Example TrutleArt "Save as" tab ====<br />
[[Image:toolbar_mockup_gary_turtle_art-52_save_as.png|thumb|centre|640px|I've just tried to show Walter's existing "Save at" tab here, though I do think import/export is a better text description ;-)]]<br />
<br />
<noinclude><br />
==Subpages==<br />
{{Special:PrefixIndex/{{PAGENAMEE}}/}}<br />
</noinclude><br />
<br />
[[Category:Proposal]]</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Features/Tabs_In_Browse&diff=32810Features/Tabs In Browse2009-07-08T21:54:53Z<p>Skierpage: remove redundant h1</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 }}{{TOCright}}</noinclude><br />
<br />
== Summary ==<br />
Pages to be opened in new windows are opened now in a small popup window without any controls. This feature opens those pages in a new tab inside the activity window.<br />
<br />
== Owner ==<br />
* Name: [[User:Tomeu| Tomeu Vizoso]]<br />
* Email: tomeu@sugarlabs.org<br />
<br />
== Current status ==<br />
* Targeted release: 0.86<br />
* Last updated: July 6th 2009<br />
* Percentage of completion: 50%<br />
<br />
== Detailed Description ==<br />
New pages will open in a new tab similarly to other browsers, though this feature isn't proposing any way for the user to explicitly open any link in a new tab.<br />
<br />
== Benefit to Sugar ==<br />
Some sites expect that new pages will open in a window with the same navigation capabilities of the main window. Currently those sites break when new pages are open in dialog-like windows.<br />
<br />
== Scope ==<br />
It requires changes in the Browse activity and in Hulahop (which is only used currently by Browse).<br />
<br />
== How To Test ==<br />
Go to a web page with links that open in new windows and check that after clicking on such a link, a new tab is created and the new page loaded there. Switch between tabs and check that the address bar changes accordingly and the buttons affect the current tab.<br />
<br />
== User Experience ==<br />
Links that used to open in a new window will open in a new tab inside the main window.<br />
<br />
== Dependencies ==<br />
The maintainer of Hulahop and Browse need to accept the patches.<br />
<br />
== Contingency Plan ==<br />
None necessary, revert to previous release behaviour.<br />
<br />
== Documentation ==<br />
None other than this page.<br />
<br />
== Release Notes ==<br />
Links that would open in a new window now open in new tabs inside the main activity window, so they don't loose the toolbar, nor notifications, etc.<br />
<br />
== Comments and Discussion ==<br />
* See [[Talk:Features/Tabs In Browse]] <!-- 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 --><br />
<br />
==[[Features]] Subpages==<br />
{{Special:PrefixIndex/Features/}}<br />
<br />
[[Category:FeaturePageIncomplete]]<br />
[[Category:Feature]]</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Category:Feature&diff=32756Category:Feature2009-07-07T23:55:37Z<p>Skierpage: explain related Category:Feature requests.</p>
<hr />
<div>Proposed features for Sugar. See [[Features/Policy]].<br />
<br />
To see which deployments and schools have requested which feature, see subcategories of [[:Category:Feature requests]].</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Sugar_on_a_Stick/Goals&diff=32755Sugar on a Stick/Goals2009-07-07T23:50:42Z<p>Skierpage: add Category:Features requested by Gardner Pilot Academy, though this isn't the best way to do it</p>
<hr />
<div><noinclude>{{GoogleTrans-en}}{{TeamHeader|Sugar on a Stick|home=Project Home|xbgColor=ffe792|join_label=Get Involved}}{{TOCright}}</noinclude><br />
<br />
From Caroline Meeks post, http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg05998.html<br />
<br />
I am going to try to answer this, or actually I hope start a brainstorming session that will get us towards a feature list.<br />
<br />
I am going to try to use the Customer Role of an Agile process. That means I'm going to try to talk as much about the result I want to see as I can and as little as I can about how to get to it. I do know that some of this is in the works. I also know that some of it will require the heavens to deliver us yet another genius programmer with a new skill set to accomplish by September. But the job of the role of Customer is my mind is to talk about what I'd like to see, what the business case for it is and what the priority is. I hope other people will join me in this role as i think its crucial information for the technical team to have.<br />
<br />
==Solid Collaboration==<br />
* Priority A for [[Gardner Pilot Academy|GPA Project]]. - Defining what this looks like and how we get there is an important discussion and i don't have all those answers. This encompasses local and jabber collaboration.<br />
* Priority(?) Switch on sugar control panel to turn on/off jabber and use only local network for collaboration [satellit07/05/2009]<br />
<br />
* Four network configurations are envisioned for use of this feature at GPA:<br />
# Computers on same LAN segment See related http://dev.sugarlabs.org/ticket/1012<br />
# Computers on same LAN no VLAN or bridge segment restrictions (aka bug 1012 resolved).<br />
# Computers IP connected to a server inside the firewall only. e.g. School Server in school.<br />
# Computers anywhere on the Internet accessing publicly addressable school server (or any Jabber implementation)<br />
<br />
==Straightforward Teacher "Assignment" -> Student -> Teacher workflow==<br />
* Priority B for GPA. For example. Teacher creates a template to scaffold student writing. Students do the writing assignment and the teacher "collects" them. Maybe this happens with Moodle or maybe its done all in Sugar? <br />
<br />
==Straightforward Sugarization==<br />
* Priority A for Sugar. By this I mean that a programmer who has created a game for linux or the web could look at our documentation and examples and tell his/her boss, "yes I see how we can make this available for Sugar and it will be a better experience for kids in a classroom through Sugar." Sugarizing should not mean giving up aggregating data for the teacher. It should be a better user experience because: automatic saving, cooler collaboration, easier installation and more consistent performance, easier for teachers to find, available to the million kids with XOs.<br />
<br />
==Backup and Restore with School Server==<br />
Sugar on SoaS and Netbooks backs up and restores with XS<br />
* Priority A for GPA,<br />
<br />
Now also tracked here: http://wiki.sugarlabs.org/go/Features/Back_Up_and_Restore<br />
<br />
==Combine Sugar Live CD, Boothelper, & USB Creator on one image==<br />
* Priority B for SoaS<br />
* Priority(?) Down-loadable Application to clone sugar.iso files and USB sugar on a sticks from a running sugar desktop [satellit 07/05/2009]<br />
<br />
==Sugar on a Stick works with a VM==<br />
* Priority B for GPA - it still has to boot on its own also.<br />
* Priority(?)Custom Boot CD with autostart VMPlayer (in sqfs) to run USB "VM's on a stick" on insertion [satellit 07/05/2009]<br />
<br />
==A Sugar machine can also run a SoaS ==<br />
* Priority C - Use case. Say you are in a 1-1 Netbook deployment. Your netbook breaks and it'll be a week till its repaired. It would be cool to burn a Stick for that kid from the XS backup and they could then use a teacher's netbook or some kid who is in Gym that period's netbook and still get to participate in the lesson.<br />
<br />
==Sugar works on preIntel Macs==<br />
* Priority C for GPA, Priority B for Sugar.<br />
<br />
==Sugar works on lesser hardware, say Pentium III 256M==<br />
* Priority C for SoaS<br />
<br />
==Avoid surplus Activity launching==<br />
Don't let the user keep opening activities until the machine crashes or is driven to its knees.<br />
* Priority C for GPA<br />
<br />
==Less cluttered, more consistent neighborhood view==<br />
* Priority C for Sugar<br />
<br />
I am copying the Server list because I think many of the things I think are the most important next steps for Sugar require interfacing with, and improvements in the XS.<br />
<br />
Priorities are my current opinions and I tried to not bias them with how hard I think the tasks are. They are about how important I think they are, in my opinion, with my customer hat on, to either the GPA pilot, Sugar and its marketing, and partnerships and adoption, or the Sugar on a Stick project. I don't think for a second that things should be done in priority order. <br />
<br />
So I hope everyone else sticks their necks out and says what features they want, what the use cases are and what they think their relative importance are. Then we can narrow our focus back down to what we can do for September.<br />
<br />
[[Category:Features requested by Gardner Pilot Academy]]</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Features/Feature_Template&diff=32754Features/Feature Template2009-07-07T23:48:31Z<p>Skierpage: /* Features Subpages */ typo</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 }}{{TOCright}}</noinclude><br />
<br />
'''Comments and Explanations:'''<br />
<br />
There are comments (in italic) providing guidance to fill out each section. '''Copy the source to a ''new page'' named Features/''Your Feature Name'' before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR FEATURE.'''<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 />
''A sentence or two summarizing what this feature is and what it will do. This information is used for the overall feature summary page for each release.''<br />
<br />
== Owner ==<br />
''This should link to your home wiki page so we know who you are''<br />
* Name: [[User:AcountName| Your Name]]<br />
<br />
''Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or technical issues need to be resolved''<br />
* Email: <your email address so we can contact you, invite you to meetings, etc.><br />
<br />
== Current status ==<br />
* Targeted release: (SUGAR_VERSION)<br />
* Last updated: (DATE)<br />
* Percentage of completion: XX%<br />
<br />
== Detailed Description ==<br />
''Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better.''<br />
<br />
== Benefit to Sugar ==<br />
''What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will Sugar become a better platform or project because of this feature?''<br />
<br />
== Scope ==<br />
''What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?''<br />
<br />
== How To Test ==<br />
''This does not need to be a full-fledged document. Describe the dimensions of tests that this feature is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be.''<br />
<br />
''Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.''<br />
<br />
''A good "how to test" should answer these four questions:''<br />
<br />
* ''What special hardware / data / etc. is needed (if any)?<br />
* ''How do I prepare my system to test this feature? What packages need to be installed, config files edited, etc.?<br />
* ''What specific actions do I perform to check that the feature is working like it's supposed to?<br />
* ''What are the expected results of those actions?''<br />
<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 />
''What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like python?''<br />
<br />
== Contingency Plan ==<br />
''If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. If you feature is not completed in time we want to assure others that other parts of Sugar will not be in jeopardy.''<br />
<br />
== Documentation ==<br />
''Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved.''<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 --><br />
<br />
==[[Features]] Subpages==<br />
{{Special:PrefixIndex/Features/}}<br />
----<br />
''You can add categories to tie features back to real deployments/schools requesting them, for example <nowiki>[[</nowiki>Category:Features requested by School Xyz]]''<br />
[[Category:FeaturePageIncomplete]]<br />
[[Category:Feature]]</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Features/Backup_and_Restore&diff=32753Features/Backup and Restore2009-07-07T23:47:54Z<p>Skierpage: /* Features Subpages */</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 }}{{TOCright}}</noinclude><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/YourFeatureName. This keeps all features in the same namespace --><br />
<br />
== Summary ==<br />
Easily back up and restore the Journal of a computer running Sugar (includes SoAS and SoLinux with top priority SoAS). Also, easily back up and restore the full Sugar installation. Beyond the Journal, this includes the activities, any configuration of the OS and the everything needed to restore to its original state.<br />
<br />
This feature is a top priority for Gardner Pilot Academy but also requests by essentially every XO deployment.<br />
<br />
== Owner ==<br />
* Name: [[User:Gregorio| Greg Smith]]<br />
<br />
* Email: gregsmithpm at gmail.com<br />
<br />
== Current status ==<br />
* Targeted release: ? <br />
* Last updated: July 7, 2009<br />
* Percentage of completion: ?<br />
<br />
== Detailed Description ==<br />
For all the items listed below, implement solution with XS and if possible as a software solution on one or more standard Linux distributions.<br />
<br />
''Backup and Restore of the Journal''<br />
* Allow time based backup and restore of the journal. Check for Journal changes on the Sugar computer. Copy any changes to the server on a regular basis. Stagger the copies so that not all Sugar computers backup at the same time. See implementation of this with XO and XS at: http://wiki.laptop.org/go/XS_Blueprints:Datastore_Simple_Backup_and_Restore<br />
<br />
* Provide a web based GUI to restore one or all backed up journal entries. The user would boot up any Sugar implementation (user name/password based security is also important) and point their Web browser at a URL on the server. Preferable to automatically take you to the right page (aka the page where your particular Sugar instance is backed up) but would also accept seeing a list of Sugar Journals by user name and picking the right one. Clicking on a single Journal entry or on a link for "full journal" would download those items back in to the journal of the Sugar computer.<br />
<br />
* Provide a user initiated backup of the journal. In this case a User would use their web browser to go to a page on the server and click the "backup" link. Then the server would check for changes since the last backup and copy everything from that journal to the server. Same case as above for restore.<br />
<br />
* Backup and restor of full sugar instance. Same as above (AKA user initiated and time based server/script) but for the full Sugar instance. This can be only the full instance and does not need to list individual files. For restoring SoAS should support booting up with a USB stick, going to the page, then removing the USB stick and inserting a new one, then clicking restore. This would copy the full Sugar instance to the new USB stick. This would now be a clone of the original USB stick. Also, implement a "clone" feature which allows the same work flow as above but without a server. That is, put a SoAS in a computer, copy it to the computer then restore it to a new USB stick with the full SoAS including configuration.<br />
<br />
* Implementing a standard Linux package to do this for Sugar would be fine.<br />
<br />
* See also this bug in Sugar: http://dev.sugarlabs.org/ticket/75 and http://dev.sugarlabs.org/ticket/916<br />
<br />
== Benefit to Sugar ==<br />
Ensures that kids and teachers don't lose their work. Backup and restore over the WAN is a major growth technology in commercial SW. e.g. see: http://www.carbonite.com/<br />
<br />
A Sugar implementation would be a big feature promotable publicly. Could also be used for a sneaker net type collaboration of last resort. i.e. "get my journal entry off this web page" to move something from one Xo to another.<br />
<br />
== Scope ==<br />
Will need client side and server software. May need to move a Linux package to SoAS and may need to push new code upstream to support Journal/Datastore implementation.<br />
<br />
== How To Test ==<br />
Create some entries in a journal. Then test with:<br />
* SoAS 8.6 or later and a single computer.<br />
* SoAs 8.6 or later with XS running 0.5 or later.<br />
* SoAS 8.6 or later with Linux distribution<br />
* Test backup and restore of a single journal entry<br />
* Test backup and restore of a full SoAS image. Make sure to use the SoAS so that it changes some files and configurations. <br />
* Test time based backup, preferably with several SoAS computers.<br />
<br />
In all cases, ensure that the files are backed up on the server and can be restored on the SoAS. Make sure to open the files in the journal and run them. Also, make sure to cold boot any full images and confirm that changes were saved.<br />
<br />
== User Experience ==<br />
Requires a new "web site" on the server for back up and restore.<br />
Requires a configuration option on SoAS to set the time and files to be backed up.<br />
<br />
== Dependencies ==<br />
''What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like python?''<br />
<br />
* See http://dev.sugarlabs.org/ticket/916 for changes to allow registering SoaS to a XS.<br />
* Also ds-backup-client package is required to backup to an XS along with a patch to allow it to work on SoaS in addition to an XO.<br />
<br />
Unknown.<br />
<br />
== Contingency Plan ==<br />
Plan B is to find a manual way to execute a script which does an "rcp" or other file transfer to a server. Then allows restore via script as well.<br />
<br />
== Documentation ==<br />
See XS example above. Will need more documentation.<br />
<br />
== Release Notes ==<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 --><br />
<br />
==[[Features]] Subpages==<br />
{{Special:PrefixIndex/Features/}}<br />
<br />
[[Category:FeaturePageIncomplete]]<br />
[[Category:Feature]]<br />
[[Category:Features requested by Gardner Pilot Academy]]</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Features/Backup_and_Restore&diff=32752Features/Backup and Restore2009-07-07T23:47:26Z<p>Skierpage: remove redundant h1; identify as Category:Features requested by Gardner Pilot Academy</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 }}{{TOCright}}</noinclude><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/YourFeatureName. This keeps all features in the same namespace --><br />
<br />
== Summary ==<br />
Easily back up and restore the Journal of a computer running Sugar (includes SoAS and SoLinux with top priority SoAS). Also, easily back up and restore the full Sugar installation. Beyond the Journal, this includes the activities, any configuration of the OS and the everything needed to restore to its original state.<br />
<br />
This feature is a top priority for Gardner Pilot Academy but also requests by essentially every XO deployment.<br />
<br />
== Owner ==<br />
* Name: [[User:Gregorio| Greg Smith]]<br />
<br />
* Email: gregsmithpm at gmail.com<br />
<br />
== Current status ==<br />
* Targeted release: ? <br />
* Last updated: July 7, 2009<br />
* Percentage of completion: ?<br />
<br />
== Detailed Description ==<br />
For all the items listed below, implement solution with XS and if possible as a software solution on one or more standard Linux distributions.<br />
<br />
''Backup and Restore of the Journal''<br />
* Allow time based backup and restore of the journal. Check for Journal changes on the Sugar computer. Copy any changes to the server on a regular basis. Stagger the copies so that not all Sugar computers backup at the same time. See implementation of this with XO and XS at: http://wiki.laptop.org/go/XS_Blueprints:Datastore_Simple_Backup_and_Restore<br />
<br />
* Provide a web based GUI to restore one or all backed up journal entries. The user would boot up any Sugar implementation (user name/password based security is also important) and point their Web browser at a URL on the server. Preferable to automatically take you to the right page (aka the page where your particular Sugar instance is backed up) but would also accept seeing a list of Sugar Journals by user name and picking the right one. Clicking on a single Journal entry or on a link for "full journal" would download those items back in to the journal of the Sugar computer.<br />
<br />
* Provide a user initiated backup of the journal. In this case a User would use their web browser to go to a page on the server and click the "backup" link. Then the server would check for changes since the last backup and copy everything from that journal to the server. Same case as above for restore.<br />
<br />
* Backup and restor of full sugar instance. Same as above (AKA user initiated and time based server/script) but for the full Sugar instance. This can be only the full instance and does not need to list individual files. For restoring SoAS should support booting up with a USB stick, going to the page, then removing the USB stick and inserting a new one, then clicking restore. This would copy the full Sugar instance to the new USB stick. This would now be a clone of the original USB stick. Also, implement a "clone" feature which allows the same work flow as above but without a server. That is, put a SoAS in a computer, copy it to the computer then restore it to a new USB stick with the full SoAS including configuration.<br />
<br />
* Implementing a standard Linux package to do this for Sugar would be fine.<br />
<br />
* See also this bug in Sugar: http://dev.sugarlabs.org/ticket/75 and http://dev.sugarlabs.org/ticket/916<br />
<br />
== Benefit to Sugar ==<br />
Ensures that kids and teachers don't lose their work. Backup and restore over the WAN is a major growth technology in commercial SW. e.g. see: http://www.carbonite.com/<br />
<br />
A Sugar implementation would be a big feature promotable publicly. Could also be used for a sneaker net type collaboration of last resort. i.e. "get my journal entry off this web page" to move something from one Xo to another.<br />
<br />
== Scope ==<br />
Will need client side and server software. May need to move a Linux package to SoAS and may need to push new code upstream to support Journal/Datastore implementation.<br />
<br />
== How To Test ==<br />
Create some entries in a journal. Then test with:<br />
* SoAS 8.6 or later and a single computer.<br />
* SoAs 8.6 or later with XS running 0.5 or later.<br />
* SoAS 8.6 or later with Linux distribution<br />
* Test backup and restore of a single journal entry<br />
* Test backup and restore of a full SoAS image. Make sure to use the SoAS so that it changes some files and configurations. <br />
* Test time based backup, preferably with several SoAS computers.<br />
<br />
In all cases, ensure that the files are backed up on the server and can be restored on the SoAS. Make sure to open the files in the journal and run them. Also, make sure to cold boot any full images and confirm that changes were saved.<br />
<br />
== User Experience ==<br />
Requires a new "web site" on the server for back up and restore.<br />
Requires a configuration option on SoAS to set the time and files to be backed up.<br />
<br />
== Dependencies ==<br />
''What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like python?''<br />
<br />
* See http://dev.sugarlabs.org/ticket/916 for changes to allow registering SoaS to a XS.<br />
* Also ds-backup-client package is required to backup to an XS along with a patch to allow it to work on SoaS in addition to an XO.<br />
<br />
Unknown.<br />
<br />
== Contingency Plan ==<br />
Plan B is to find a manual way to execute a script which does an "rcp" or other file transfer to a server. Then allows restore via script as well.<br />
<br />
== Documentation ==<br />
See XS example above. Will need more documentation.<br />
<br />
== Release Notes ==<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 --><br />
<br />
==[[Features]] Subpages==<br />
{{Special:PrefixIndex/Features/}}<br />
----<br />
''You can add categories to tie features back to real deployments/schools requesting them, for example <nowiki>[[</nowiki>Category:Feature requested by School Xyz]]''<br />
[[Category:FeaturePageIncomplete]]<br />
[[Category:Feature]]<br />
[[Category:Features requested by Gardner Pilot Academy]]</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Category:Feature_requests&diff=32751Category:Feature requests2009-07-07T23:46:14Z<p>Skierpage: improve</p>
<hr />
<div>This category is ''not'' for features and proposals. Rather, you can use subcategories of this to identify those [[:Category:Feature|features]] requested by particular schools and deployments.</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Category:Feature_requests&diff=32748Category:Feature requests2009-07-07T23:45:34Z<p>Skierpage: document</p>
<hr />
<div>This category is ''not'' for features and proposals. Rather, you can use subcategories of this to identify features that different schools and deployments request.</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Category:Features_requested_by_Gardner_Pilot_Academy&diff=32747Category:Features requested by Gardner Pilot Academy2009-07-07T23:44:15Z<p>Skierpage: document</p>
<hr />
<div>[[Category:Feature requests]]</div>Skierpagehttps://wiki.sugarlabs.org/index.php?title=Gardner_Pilot_Academy&diff=32746Gardner Pilot Academy2009-07-07T23:43:36Z<p>Skierpage: /* Sugar Feature Requests */ suggest :Category:Features requested by Gardner Pilot Academy</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 }}{{TOCright}}</noinclude><br />
<br />
=Gardner Pilot Academy=<br />
Boston Public Schools - Allston http://www.rabbitnet.net/gpa/<br />
<br />
GPA is partnering with Solution Grove and Sugar Labs to pilot [[Sugar on a Stick]].<br />
<br />
The Gardner Pilot Academy is the flagship full-service community school within the Boston Public Schools (BPS). The school's vision is to educate the minds and develop the characters of all students in partnership with families and community. To achieve this GPA provides high quality teaching along with a range of social, emotional and enrichment programs delivered by means of partnerships with an array of community organizations and individuals. Over the past twelve years, GPA has developed strong associations with four universities, several health and mental health agencies, the YMCA, and various organizations teaching visual and performing arts. As one of just 20 pilot schools in the BPS, GPA is exempt from district mandates. Therefore, GPA has autonomy in the areas of budget and personnel, along with the freedom to implement innovative curricula, assessments, and interventions.<br />
<br />
Located in a culturally and linguistically varied section of Boston, the GPA serves quite a diverse student population. GPA's 336 students and their families speak more than 13 languages ranging from Spanish to Khmer (all of which are supported by Sugar). Demographically, 15.2% are African American, 59.1% are Hispanic, 10.7% are White and 13.1% are Asian. Over 85% of the students meet the federal poverty guidelines for participation in the Free or Reduced Price Lunch Program. The majority of GPA's students fall within a group of students considered to be academically at risk. <br />
<br />
GPA is located only a few blocks from Harvard Business School and so is convenient for project development participants who may be students at one of Boston’s many universities.<br />
<br />
The school currently has a single computer lab with older computers running Windows 2000. We will be soliciting donations of used equipment from local business to supplement these existing resources. Sugar can be used at all elementary levels and curriculum areas. <br />
<br />
==Current computers at GPA==<br />
<br />
* A computer lab with about 20 EVO D500 1.7 GHz Pentium 4, 500 MB RAM computers running Windows 2000<br />
* 20 new Apple laptops in a mobile cart (OSX, hardware details unknown, no Parallels)<br />
* Each teacher has a MacBook with Parallels 3.0 <br />
<br />
There are two teachers in the school especially interested in starting with Sugar:<br />
<br />
* 4th Grade teacher who wants to do portfolios<br />
* Science Teacher who wants to pilot with the 5th grade to support a new district mandate for writing in Science<br />
<br />
==The Summer Program==<br />
<br />
Classes run from July 6 to Aug 17th from 8:30 am to 5pm. The lead teachers over the summer work 10am to 5pm during the school year so we will have good continuity.<br />
<br />
They will not be using the mac laptop cart and the summer teachers do not have macbooks. <br />
<br />
We will be using the computer lab and we will be talking to the school about putting more computer into classrooms and other locations.<br />
<br />
===2nd Grade===<br />
<br />
Next Tuesday we will work with the 2nd Graders on their science and social studies. The theme of the week is responsibility and the environment. They will be learning about their community and preping for a cleanup of the local Charles River.<br />
<br />
The goal of the first project will be to label a map of where they do the clean up with what they find during their cleanup.<br />
<br />
We have half an hour on Tuesday. After kids get their keys and boot up, enter their name and colors we will have them go to Turtle Art. We will prepare maps and preload them on the sticks and show them how to bring them into Turtle Art. Then we'll show them how to have the turtle label them. Next week, after their cleanup they can label what they find on the clean-up.<br />
<br />
Maps:<br />
* http://www.paddleboston.com/boston/boston_map.jpg<br />
* http://screencast.com/t/kLcW3O7Tyb4<br />
* http://screencast.com/t/IngjAlCySu<br />
<br />
===3rd Grade===<br />
<br />
We are hoping that the kids can create a US version of the Uruguay geography/facts game. Any ideas on how to make that easy to do? The vision is they will learn things in class then make them into questions to put into the game. We will meet with the third grade on Thursday afternoons.<br />
<br />
==Looking for Summer Volunteers and Work-Study Students==<br />
<br />
We are currently looking for committed volunteers and work-study students for the Summer. We have some funding for Work Study so if you know any eligible students please let us know.<br />
<br />
Ideally we would like a team of 3 people, each working around 20 hours per week, consisting of a technical person, a person with education experience and a marketing person.<br />
<br />
==Project Goals==<br />
<br />
For the GPA School: <br />
* Student Learning, <br />
* Teacher Participation, <br />
* Parent Perception and <br />
* Greater GPA School community perception of the project.<br />
<br />
Our goals for the Sugar Project are:<br />
* Sugar on a Stick projects replicated at other schools,<br />
* Improved Sugar for everyone, including OLPC XO children,<br />
* Increased visibility of Sugar, and<br />
* Knowledge and best practices gained for using Sugar in US Schools.<br />
<br />
More detail in our Balanced Score Card: http://spreadsheets.google.com/ccc?key=px5yPvIlUlLtsrYpZdVG_EQ<br />
<br />
<br />
'''Status for the Computer Lab'''<br />
<br />
Boots with the boot-helper CD and connects to the internet if the broadcom drivers are installed.<br />
<br />
==Critical Path Technical Issues==<br />
<br />
Our biggest issue is collaboration. We either need to get local colaboration, jabber collaboration or a local XS working<br />
<br />
* Ticket 1014 http://dev.sugarlabs.org/ticket/1014 - Jabber keeps dying, then it falls back to Salut, that only finds one computer, then it tried Jabber again, works briefly, dies.<br />
<br />
* Ticket 1012 - not collaborating locally<br />
<br />
== How you can help - Technical Tickets ==<br />
<br />
The following tickets will help this deployment.<br />
<br />
* [[http://dev.sugarlabs.org/ticket/75 Ticket 75]]Backup and Restore of user data on a USB Stick<br />
<br />
* [[http://dev.sugarlabs.org/ticket/74 Ticket 74]] Clone a Stick. Let a teacher customize a Sugar Stick then clone it, without files or personality, for students to use.<br />
<br />
* Can't get Computer Lab Machines to Boot from USB''' - The BIOS says it should be trying to boot from the USB but its not looking at the USB. A google search confirms that this is not a sugar problem, its an EVO D500 problem. I'm hoping we find a solution. http://dev.sugarlabs.org/ticket/599 <br />
Google Search on EVO D500 usb boot gives this result: http://forums13.itrc.hp.com/service/forums/bizsupport/questionanswer.do?admit=109447627+1237587827991+28353475&threadId=1038476<br />
<br />
* Boot Helper Floppy - This is easier then a CD because the computer has to be turned on to open the CD Drawer and put in the CD then you have to turn it off again and reboot.http://dev.sugarlabs.org/ticket/597<br />
<br />
* [[http://dev.sugarlabs.org/ticket/579 Ticket 579]]. We have several donated computers. A requirement for the donations was that we wiped the harddrives. Thus it would be great if we had an installable operating system enabled quick user switching between USBs. This is also impacted by 907, described below.<br />
<br />
* [[http://dev.sugarlabs.org/ticket/598 Ticket 598]] and [[http://dev.sugarlabs.org/ticket/907 Ticket 907]] . One way to enable faster switching between Windows and Sugar is a Virtual Machine solution that will allow students to put in their USB Sticks and use all the personal data from the Sticks so they can use any computer. To do this we need to change the way we put data onto the USB and use different partitions for the boot and the data (Ticket 907). <br />
<br />
==== Sugar Feature Requests ====<br />
This link records an in process list of priorities for Sugar development with a focus on success at the Gardner Pilot Academy: <br><br />
[[Sugar_on_a_Stick/Goals]]<br />
Other feature requests by {{PAGENAME}} are in [[:Category:Features requested by Gardner Pilot Academy]]<br />
<br />
It is extracted from this thread on the Sugar Devel List: <br><br />
http://lists.sugarlabs.org/archive/sugar-devel/2009-July/016205.html<br />
<br />
Please propose additional suggestions on that list. After clarifying and validating the Feature Requests, add them to the Goals page.<br />
<br />
Also, on the pages describing features that {{PAGENAME}} request, add <nowiki>[[</nowiki>Category:Features requested by Gardner Pilot Academy]].<br />
<br />
[[Category:Project]]</div>Skierpage