Sugar Labs - User contributions [en]

Translation Team/Pootle Projects/Repositories

2014-12-27T01:25:44Z

Jdsimmons: /* Fructose */

The Objective of this page is keep a updated list of the repositories where Pootle will push the translations.
If you are a maintainer and change the repository of your project, please notify to the pootle maintainers.
Pootle will pull and push to the master branch.

= Glucose =

{| class="wikitable"
|-
! Module !! Maintainer !! Repository !! Project
|-
| sugar || SugarLabs || git@github.com:sugarlabs/sugar.git || [http://translate.sugarlabs.org/projects/sugar/ sugar]
|-
| sugar-toolkit-gtk3 || SugarLabs || git@github.com:sugarlabs/sugar-toolkit-gtk3.git || [http://translate.sugarlabs.org/projects/sugar-toolkit-gtk3/ sugar-toolkit-gk3]
|}

= Fructose =

{| class="wikitable"
|-
! Module !! Maintainer !! Repository !! Project
|-
| Calculate || || ||
|-
| Chat || Walter || git@github.com:walterbender/chat.git || [http://translate.sugarlabs.org/projects/Chat/ Chat]
|-
| ImageViewer || Godiard || git@github.com:godiard/imageviewer-activity.git || [http://translate.sugarlabs.org/projects/ImageViewer/ ImageViewer]
|-
| Jukebox || Godiard || git@github.com:godiard/jukebox-activity.git || [http://translate.sugarlabs.org/projects/Jukebox/ Jukebox]
|-
| Log || Ignacio || git@github.com:ignaciouy/log.git || [http://translate.sugarlabs.org/projects/Log/ Log]
|-
| Paint || Godiard || git@github.com:godiard/paint-activity.git || [http://translate.sugarlabs.org/projects/Paint/ Paint]
|-
| Pippy || Walter || git@github.com:walterbender/Pippy.git || [http://translate.sugarlabs.org/projects/Pippy/ Pippy]
|-
| Portfolio || Walter || git@github.com:walterbender/portfolio || [http://translate.sugarlabs.org/projects/Portfolio/ Portfolio]
|-
| Read || Godiard || git@github.com:godiard/read-activity.git || [http://translate.sugarlabs.org/projects/Read/ Read]
|-
| ReadETexts || Jdsimmons || git@github.com:jdsimmons/readetexts.git ||
|-
| Record || Godiard || git@github.com:godiard/record-activity.git || [http://translate.sugarlabs.org/projects/Record/ Record]
|-
| Speak || Walter || git@github.com:walterbender/speak.git || [http://translate.sugarlabs.org/projects/Speak/ Speak]
|-
| Terminal || Godiard || git@github.com:godiard/terminal-activity.git || [http://translate.sugarlabs.org/projects/Terminal/ Terminal]
|-
| TurtleArt || Walter || git@github.com:walterbender/turtleart.git || [http://translate.sugarlabs.org/projects/TurtleArt/ TurtleArt]
|-
| TurtleArtExtras || Walter || git@github.com:walterbender/turtleextras.git || [http://translate.sugarlabs.org/projects/TurtleArtExtras/ TurtleArtExtras]
|-
| Web || Godiard || git@github.com:sugarlabs/browse-activity.git || [http://translate.sugarlabs.org/projects/Web/ Web]
|-
| Write || Godiard || git@github.com:godiard/write-activity.git || [http://translate.sugarlabs.org/projects/Write/ Write]
|}

= Honey =

{| class="wikitable"
|-
! Module !! Maintainer !! Repository !! Project
|-
| Abacus || Walter || git@github.com:walterbender/abacus.git || [http://translate.sugarlabs.org/projects/Abacus/ Abacus]
|-
| Calendario || || ||
|-
| ClassromBroadcast || || ||
|-
| Clock || Cristian || git@github.com/cristian99garcia/ClockActivity.git || [http://translate.sugarlabs.org/projects/Clock/ Clock]
|-
| Distance || || ||
|-
| Finance || Godiard || git@github.com:godiard/finance-activity.git || [http://translate.sugarlabs.org/projects/Finance/ Finance]
|-
| FotoToon || Godiard || git@github.com:godiard/fototoon-activity.git || [http://translate.sugarlabs.org/projects/FotoToon/ FotoToon]
|-
| GetBooks || Godiard || git@github.com:godiard/get-books-activity.git ||
|-
| IKnowAmerica || AlanJAS || git@github.com:AlanJAS/iknowAmerica.git || [http://translate.sugarlabs.org/projects/IKnowAmerica/ IKnowAmerica]
|-
| Implode || || ||
|-
| Infoslicer || Walter || git@github.com:walterbender/infoslicer.git || [http://translate.sugarlabs.org/projects/InfoSlicer/ InfoSlicer]
|-
| Jigsaw puzzle|| || ||
|-
| Labyrinth || || ||
|-
| Maze || Godiard || git@github.com:godiard/maze-activity.git || [http://translate.sugarlabs.org/projects/Maze/ Maze]
|-
| Measure || Walter || git@github.com:walterbender/Measure.git || [http://translate.sugarlabs.org/projects/Measure/ Measure]
|-
| Memorize || Godiard || git@github.com:godiard/memorize-activity.git || [http://translate.sugarlabs.org/projects/Memorize/ Memorize]
|-
| Moon || || ||
|-
| Physics || Walter || git@github.com:walterbender/physics.git || [http://translate.sugarlabs.org/projects/Physics/ Physics]
|-
| Ruler || Walter || git@github.com:walterbender/ruler.git || [http://translate.sugarlabs.org/projects/Ruler/ Ruler]
|-
| Chart (SimpleGraph) || || ||
|-
| Slider puzzle || || ||
|-
| StopWatch || || ||
|-
| Story || Walter || git@github.com:walterbender/story.git || [http://translate.sugarlabs.org/projects/Story/ Story]
|-
| SimpleGNUChess || Walter || git@github.com:walterbender/sugarchess.git || [http://translate.sugarlabs.org/projects/SimpleGNUChess/ SimpleGNUChess]
|-
| TamTam Suite || || ||
|-
| TypingTurtle || GOdiard || git@github.com:godiard/typing-turtle-activity.git || [http://translate.sugarlabs.org/projects/TypingTurtle/ TypingTurtle]
|-
| ViewSlides || Jdsimmons || git@github.com:jdsimmons/viewslides.git ||
|-
| Dimensions || Walter || git@github.com:walterbender/dimensions.git || [http://translate.sugarlabs.org/projects/Dimensions/ Dimensions]
|-
| Watch Listen || || ||
|-
| Words || Godiard || git@github.com:godiard/words-activity.git || [http://translate.sugarlabs.org/projects/Words/ Words]
|-
| XoEditor || Walter || git@github.com:walterbender/xocolors.git || [http://translate.sugarlabs.org/projects/XoEditor/ XoEditor]
|}

= Honey2 =

{| class="wikitable"
|-
! Module !! Maintainer !! Repository !! Project
|-
| Analyze || || ||
|-
| AnalyzeJournal || Walter || git@github.com:walterbender/AnalyzeJournal.git || [http://translate.sugarlabs.org/projects/AnalyzeJournal/ AnalyzeJournal]
|-
| Annotate || || ||
|-
| Arithmetic || || ||
|-
| Biorhythm || AlanJAS || git@github.com:AlanJAS/biorhythm.git || [http://translate.sugarlabs.org/projects/Biorhythm/ Biorhythm]
|-
| Bridge || || ||
|-
| CardSort || Walter || git@github.com:walterbender/cardsort.git || [http://translate.sugarlabs.org/projects/CardSort/ CardSort]
|-
| CartoonBuilder || || ||
|-
| Colors || || ||
|-
| Convert || || ||
|-
| CookieSearch || Walter || git@github.com:walterbender/cookiesearch.git || [http://translate.sugarlabs.org/projects/CookieSearch/ CookieSearch]
|-
| Deducto || Walter || git@github.com:walterbender/deducto.git || [http://translate.sugarlabs.org/projects/Deducto/ Deducto]
|-
| Domino || Godiard || git@github.com:godiard/domino-activity.git || [http://translate.sugarlabs.org/projects/Domino/ Domino]
|-
| Dots and boxes || AlanJAS || git@github.com:AlanJAS/dotsAndBoxes.git || [http://translate.sugarlabs.org/projects/DotsAndBoxes/ DotsAndBoxes]
|-
| Erikos || Walter || git@github.com:walterbender/erikos.git || [http://translate.sugarlabs.org/projects/Erikos/ Erikos]
|-
| Flip || Walter || git@github.com:walterbender/flip.git || [http://translate.sugarlabs.org/projects/Flip/ Flip]
|-
| FlipSticks || || ||
|-
| Followme Butia || AlanJAS || git@github.com:AlanJAS/followme.git || [http://translate.sugarlabs.org/projects/FollowMeButia/ FollowMeButia]
|-
| FractionBounce || Walter || git@github.com:walterbender/fractionbounce.git || [http://translate.sugarlabs.org/projects/FractionBounce/ FractionBounce]
|-
| Get IA Books || Jdsimmons || git@github.com:jdsimmons/getiabooks.git ||
|-
| Gogo || || ||
|-
| Graph Plotter || || ||
|-
| Hello Mesh || || ||
|-
| HMouse || || ||
|-
| IknowIndia || AlanJAS || git@github.com:AlanJAS/iknowIndia.git || [http://translate.sugarlabs.org/projects/IknowIndia/ IknowIndia]
|-
| IknowPeru || AlanJAS || git@github.com:AlanJAS/iknowPeru.git || [http://translate.sugarlabs.org/projects/IknowPeru/ IknowPeru]
|-
| IknowUruguay || AlanJAS || git@github.com:AlanJAS/iknowUruguay.git || [http://translate.sugarlabs.org/projects/IknowUruguay/ IknowUruguay]
|-
| IKnowRwanda || AlanJAS || git@github.com:AlanJAS/iknowRwanda.git || [http://translate.sugarlabs.org/projects/IKnowRwanda/ IKnowRwanda]
|-
| IKnowSriLanka || AlanJAS || git@github.com:AlanJAS/iknowSriLanka.git || [http://translate.sugarlabs.org/projects/IKnowSriLanka/ IKnowSriLanka]
|-
| IKnowMadagascar || AlanJAS || git@github.com:AlanJAS/iknowMadagascar.git || [http://translate.sugarlabs.org/projects/IKnowMadagascar/ IKnowMadagascar]
|-
| Jamedia || || ||
|-
| Joke Machine || || ||
|-
| Jump || AlanJAS || git@github.com:AlanJAS/jump.git || [http://translate.sugarlabs.org/projects/Jump/ Jump]
|-
| Kandid || || ||
|-
| Karma 6 Englih animal identification || || ||
|-
| Lanzar || || ||
|-
| Level || || ||
|-
| LocoSugar || Walter || git@github.com:walterbender/locosugar.git || [http://translate.sugarlabs.org/projects/LocoSugar/ LocoSugar]
|-
| Mateton || || ||
|-
| Nutrition ||Walter || git@github.com:walterbender/nutrition.git || [http://translate.sugarlabs.org/projects/Nutrition/ Nutrition]
|-
| Panorama || AlanJAS || git@github.com:AlanJAS/panorama.git || [http://translate.sugarlabs.org/projects/Panorama/ Panorama]
|-
| Paths || Walter || git@github.com:walterbender/paths.git || [http://translate.sugarlabs.org/projects/Paths/ Paths]
|-
| Play Go || || ||
|-
| Plot || || ||
|-
| Pointillism || AlanJAS || git@github.com:AlanJAS/pointillism.git || [http://translate.sugarlabs.org/projects/Pointillism/ Pointillism]
|-
| Poll builder || || ||
|-
| Pukllanapac || Walter || git@github.com:walterbender/pukllanapac.git || [http://translate.sugarlabs.org/projects/Pukllanapac/ Pukllanapac]
|-
| PyDebug || || ||
|-
| Read SD Comics || Jdsimmons || git@github.com:jdsimmons/read-sd-comics.git ||
|-
| Recall || Walter || git@github.com:walterbender/recall.git || [http://translate.sugarlabs.org/projects/Recall/ Recall]
|-
| Reflection || Walter || git@github.com:walterbender/reflection.git || [http://translate.sugarlabs.org/projects/Reflection/ Reflection]
|-
| SlideRuler || Walter || git@github.com:walterbender/slideruler.git || [http://translate.sugarlabs.org/projects/SlideRuler/ SlideRuler]
|-
| StarChart || Walter || git@github.com:walterbender/starchart.git || [http://translate.sugarlabs.org/projects/StarChart/ StarChart]
|-
| StoryBuilder || || ||
|-
| SugarCommander || Jdsimmons || git@github.com:jdsimmons/sugar-commander.git ||
|-
| Telescope || || ||
|-
| Timeline || || ||
|-
| TurtlePond || Walter || git@github.com:walterbender/turtlepond.git || [http://translate.sugarlabs.org/projects/TurtlePond/ TurtlePond]
|-
| Yupana || Walter || git@github.com:walterbender/yupana.git || [http://translate.sugarlabs.org/projects/Yupana/ Yupana]
|}

Translation Team/Pootle Projects/Repositories

2014-12-26T02:37:01Z

Jdsimmons: /* Honey */

The Objective of this page is keep a updated list of the repositories where Pootle will push the translations.
If you are a maintainer and change the repository of your project, please notify to the pootle maintainers.
Pootle will pull and push to the master branch.

= Glucose =

{| class="wikitable"
|-
! Module !! Maintainer !! Repository !! Project
|-
| sugar || SugarLabs || git@github.com:sugarlabs/sugar.git || [http://translate.sugarlabs.org/projects/sugar/ sugar]
|-
| sugar-toolkit-gtk3 || SugarLabs || git@github.com:sugarlabs/sugar-toolkit-gtk3.git || [http://translate.sugarlabs.org/projects/sugar-toolkit-gtk3/ sugar-toolkit-gk3]
|}

= Fructose =

{| class="wikitable"
|-
! Module !! Maintainer !! Repository !! Project
|-
| Calculate || || ||
|-
| Chat || Walter || git@github.com:walterbender/chat.git || [http://translate.sugarlabs.org/projects/Chat/ Chat]
|-
| ImageViewer || Godiard || git@github.com:godiard/imageviewer-activity.git || [http://translate.sugarlabs.org/projects/ImageViewer/ ImageViewer]
|-
| Jukebox || Godiard || git@github.com:godiard/jukebox-activity.git || [http://translate.sugarlabs.org/projects/Jukebox/ Jukebox]
|-
| Log || Ignacio || git@github.com:ignaciouy/log.git || [http://translate.sugarlabs.org/projects/Log/ Log]
|-
| Paint || Godiard || git@github.com:godiard/paint-activity.git || [http://translate.sugarlabs.org/projects/Paint/ Paint]
|-
| Pippy || Walter || git@github.com:walterbender/Pippy.git || [http://translate.sugarlabs.org/projects/Pippy/ Pippy]
|-
| Portfolio || Walter || git@github.com:walterbender/portfolio || [http://translate.sugarlabs.org/projects/Portfolio/ Portfolio]
|-
| Read || Godiard || git@github.com:godiard/read-activity.git || [http://translate.sugarlabs.org/projects/Read/ Read]
|-
| ReadETexts || || ||
|-
| Record || Godiard || git@github.com:godiard/record-activity.git || [http://translate.sugarlabs.org/projects/Record/ Record]
|-
| Speak || Walter || git@github.com:walterbender/speak.git || [http://translate.sugarlabs.org/projects/Speak/ Speak]
|-
| Terminal || Godiard || git@github.com:godiard/terminal-activity.git || [http://translate.sugarlabs.org/projects/Terminal/ Terminal]
|-
| TurtleArt || Walter || git@github.com:walterbender/turtleart.git || [http://translate.sugarlabs.org/projects/TurtleArt/ TurtleArt]
|-
| TurtleArtExtras || Walter || git@github.com:walterbender/turtleextras.git || [http://translate.sugarlabs.org/projects/TurtleArtExtras/ TurtleArtExtras]
|-
| Web || Godiard || git@github.com:sugarlabs/browse-activity.git || [http://translate.sugarlabs.org/projects/Web/ Web]
|-
| Write || Godiard || git@github.com:godiard/write-activity.git || [http://translate.sugarlabs.org/projects/Write/ Write]
|}

= Honey =

{| class="wikitable"
|-
! Module !! Maintainer !! Repository !! Project
|-
| Abacus || Walter || git@github.com:walterbender/abacus.git || [http://translate.sugarlabs.org/projects/Abacus/ Abacus]
|-
| Calendario || || ||
|-
| ClassromBroadcast || || ||
|-
| Clock || Cristian || git@github.com/cristian99garcia/ClockActivity.git || [http://translate.sugarlabs.org/projects/Clock/ Clock]
|-
| Distance || || ||
|-
| Finance || Godiard || git@github.com:godiard/finance-activity.git || [http://translate.sugarlabs.org/projects/Finance/ Finance]
|-
| FotoToon || Godiard || git@github.com:godiard/fototoon-activity.git || [http://translate.sugarlabs.org/projects/FotoToon/ FotoToon]
|-
| GetBooks || Godiard || git@github.com:godiard/get-books-activity.git ||
|-
| IKnowAmerica || AlanJAS || git@github.com:AlanJAS/iknowAmerica.git || [http://translate.sugarlabs.org/projects/IKnowAmerica/ IKnowAmerica]
|-
| Implode || || ||
|-
| Infoslicer || Walter || git@github.com:walterbender/infoslicer.git || [http://translate.sugarlabs.org/projects/InfoSlicer/ InfoSlicer]
|-
| Jigsaw puzzle|| || ||
|-
| Labyrinth || || ||
|-
| Maze || Godiard || git@github.com:godiard/maze-activity.git || [http://translate.sugarlabs.org/projects/Maze/ Maze]
|-
| Measure || Walter || git@github.com:walterbender/Measure.git || [http://translate.sugarlabs.org/projects/Measure/ Measure]
|-
| Memorize || Godiard || git@github.com:godiard/memorize-activity.git || [http://translate.sugarlabs.org/projects/Memorize/ Memorize]
|-
| Moon || || ||
|-
| Physics || Walter || git@github.com:walterbender/physics.git || [http://translate.sugarlabs.org/projects/Physics/ Physics]
|-
| Ruler || Walter || git@github.com:walterbender/ruler.git || [http://translate.sugarlabs.org/projects/Ruler/ Ruler]
|-
| Chart (SimpleGraph) || || ||
|-
| Slider puzzle || || ||
|-
| StopWatch || || ||
|-
| Story || Walter || git@github.com:walterbender/story.git || [http://translate.sugarlabs.org/projects/Story/ Story]
|-
| SimpleGNUChess || Walter || git@github.com:walterbender/sugarchess.git || [http://translate.sugarlabs.org/projects/SimpleGNUChess/ SimpleGNUChess]
|-
| TamTam Suite || || ||
|-
| TypingTurtle || GOdiard || git@github.com:godiard/typing-turtle-activity.git || [http://translate.sugarlabs.org/projects/TypingTurtle/ TypingTurtle]
|-
| ViewSlides || Jdsimmons || git@github.com:jdsimmons/viewslides.git ||
|-
| Dimensions || Walter || git@github.com:walterbender/dimensions.git || [http://translate.sugarlabs.org/projects/Dimensions/ Dimensions]
|-
| Watch Listen || || ||
|-
| Words || Godiard || git@github.com:godiard/words-activity.git || [http://translate.sugarlabs.org/projects/Words/ Words]
|-
| XoEditor || Walter || git@github.com:walterbender/xocolors.git || [http://translate.sugarlabs.org/projects/XoEditor/ XoEditor]
|}

= Honey2 =

{| class="wikitable"
|-
! Module !! Maintainer !! Repository !! Project
|-
| Analyze || || ||
|-
| AnalyzeJournal || Walter || git@github.com:walterbender/AnalyzeJournal.git || [http://translate.sugarlabs.org/projects/AnalyzeJournal/ AnalyzeJournal]
|-
| Annotate || || ||
|-
| Arithmetic || || ||
|-
| Biorhythm || AlanJAS || git@github.com:AlanJAS/biorhythm.git || [http://translate.sugarlabs.org/projects/Biorhythm/ Biorhythm]
|-
| Bridge || || ||
|-
| CardSort || Walter || git@github.com:walterbender/cardsort.git || [http://translate.sugarlabs.org/projects/CardSort/ CardSort]
|-
| CartoonBuilder || || ||
|-
| Colors || || ||
|-
| Convert || || ||
|-
| CookieSearch || Walter || git@github.com:walterbender/cookiesearch.git || [http://translate.sugarlabs.org/projects/CookieSearch/ CookieSearch]
|-
| Deducto || Walter || git@github.com:walterbender/deducto.git || [http://translate.sugarlabs.org/projects/Deducto/ Deducto]
|-
| Domino || Godiard || git@github.com:godiard/domino-activity.git || [http://translate.sugarlabs.org/projects/Domino/ Domino]
|-
| Dots and boxes || AlanJAS || git@github.com:AlanJAS/dotsAndBoxes.git || [http://translate.sugarlabs.org/projects/DotsAndBoxes/ DotsAndBoxes]
|-
| Erikos || Walter || git@github.com:walterbender/erikos.git || [http://translate.sugarlabs.org/projects/Erikos/ Erikos]
|-
| Flip || Walter || git@github.com:walterbender/flip.git || [http://translate.sugarlabs.org/projects/Flip/ Flip]
|-
| FlipSticks || || ||
|-
| Followme Butia || AlanJAS || git@github.com:AlanJAS/followme.git || [http://translate.sugarlabs.org/projects/FollowMeButia/ FollowMeButia]
|-
| FractionBounce || Walter || git@github.com:walterbender/fractionbounce.git || [http://translate.sugarlabs.org/projects/FractionBounce/ FractionBounce]
|-
| Get IA Books || Jdsimmons || git@github.com:jdsimmons/getiabooks.git ||
|-
| Gogo || || ||
|-
| Graph Plotter || || ||
|-
| Hello Mesh || || ||
|-
| HMouse || || ||
|-
| IknowIndia || AlanJAS || git@github.com:AlanJAS/iknowIndia.git || [http://translate.sugarlabs.org/projects/IknowIndia/ IknowIndia]
|-
| IknowPeru || AlanJAS || git@github.com:AlanJAS/iknowPeru.git || [http://translate.sugarlabs.org/projects/IknowPeru/ IknowPeru]
|-
| IknowUruguay || AlanJAS || git@github.com:AlanJAS/iknowUruguay.git || [http://translate.sugarlabs.org/projects/IknowUruguay/ IknowUruguay]
|-
| IKnowRwanda || AlanJAS || git@github.com:AlanJAS/iknowRwanda.git || [http://translate.sugarlabs.org/projects/IKnowRwanda/ IKnowRwanda]
|-
| IKnowSriLanka || AlanJAS || git@github.com:AlanJAS/iknowSriLanka.git || [http://translate.sugarlabs.org/projects/IKnowSriLanka/ IKnowSriLanka]
|-
| IKnowMadagascar || AlanJAS || git@github.com:AlanJAS/iknowMadagascar.git || [http://translate.sugarlabs.org/projects/IKnowMadagascar/ IKnowMadagascar]
|-
| Jamedia || || ||
|-
| Joke Machine || || ||
|-
| Jump || AlanJAS || git@github.com:AlanJAS/jump.git || [http://translate.sugarlabs.org/projects/Jump/ Jump]
|-
| Kandid || || ||
|-
| Karma 6 Englih animal identification || || ||
|-
| Lanzar || || ||
|-
| Level || || ||
|-
| LocoSugar || Walter || git@github.com:walterbender/locosugar.git || [http://translate.sugarlabs.org/projects/LocoSugar/ LocoSugar]
|-
| Mateton || || ||
|-
| Nutrition ||Walter || git@github.com:walterbender/nutrition.git || [http://translate.sugarlabs.org/projects/Nutrition/ Nutrition]
|-
| Panorama || AlanJAS || git@github.com:AlanJAS/panorama.git || [http://translate.sugarlabs.org/projects/Panorama/ Panorama]
|-
| Paths || Walter || git@github.com:walterbender/paths.git || [http://translate.sugarlabs.org/projects/Paths/ Paths]
|-
| Play Go || || ||
|-
| Plot || || ||
|-
| Pointillism || AlanJAS || git@github.com:AlanJAS/pointillism.git || [http://translate.sugarlabs.org/projects/Pointillism/ Pointillism]
|-
| Poll builder || || ||
|-
| Pukllanapac || Walter || git@github.com:walterbender/pukllanapac.git || [http://translate.sugarlabs.org/projects/Pukllanapac/ Pukllanapac]
|-
| PyDebug || || ||
|-
| Read SD Comics || Jdsimmons || git@github.com:jdsimmons/read-sd-comics.git ||
|-
| Recall || Walter || git@github.com:walterbender/recall.git || [http://translate.sugarlabs.org/projects/Recall/ Recall]
|-
| Reflection || Walter || git@github.com:walterbender/reflection.git || [http://translate.sugarlabs.org/projects/Reflection/ Reflection]
|-
| SlideRuler || Walter || git@github.com:walterbender/slideruler.git || [http://translate.sugarlabs.org/projects/SlideRuler/ SlideRuler]
|-
| StarChart || Walter || git@github.com:walterbender/starchart.git || [http://translate.sugarlabs.org/projects/StarChart/ StarChart]
|-
| StoryBuilder || || ||
|-
| SugarCommander || Jdsimmons || git@github.com:jdsimmons/sugar-commander.git ||
|-
| Telescope || || ||
|-
| Timeline || || ||
|-
| TurtlePond || Walter || git@github.com:walterbender/turtlepond.git || [http://translate.sugarlabs.org/projects/TurtlePond/ TurtlePond]
|-
| Yupana || Walter || git@github.com:walterbender/yupana.git || [http://translate.sugarlabs.org/projects/Yupana/ Yupana]
|}

Translation Team/Pootle Projects/Repositories

2014-12-26T02:29:50Z

Jdsimmons: /* Honey2 */

The Objective of this page is keep a updated list of the repositories where Pootle will push the translations.
If you are a maintainer and change the repository of your project, please notify to the pootle maintainers.
Pootle will pull and push to the master branch.

= Glucose =

{| class="wikitable"
|-
! Module !! Maintainer !! Repository !! Project
|-
| sugar || SugarLabs || git@github.com:sugarlabs/sugar.git || [http://translate.sugarlabs.org/projects/sugar/ sugar]
|-
| sugar-toolkit-gtk3 || SugarLabs || git@github.com:sugarlabs/sugar-toolkit-gtk3.git || [http://translate.sugarlabs.org/projects/sugar-toolkit-gtk3/ sugar-toolkit-gk3]
|}

= Fructose =

{| class="wikitable"
|-
! Module !! Maintainer !! Repository !! Project
|-
| Calculate || || ||
|-
| Chat || Walter || git@github.com:walterbender/chat.git || [http://translate.sugarlabs.org/projects/Chat/ Chat]
|-
| ImageViewer || Godiard || git@github.com:godiard/imageviewer-activity.git || [http://translate.sugarlabs.org/projects/ImageViewer/ ImageViewer]
|-
| Jukebox || Godiard || git@github.com:godiard/jukebox-activity.git || [http://translate.sugarlabs.org/projects/Jukebox/ Jukebox]
|-
| Log || Ignacio || git@github.com:ignaciouy/log.git || [http://translate.sugarlabs.org/projects/Log/ Log]
|-
| Paint || Godiard || git@github.com:godiard/paint-activity.git || [http://translate.sugarlabs.org/projects/Paint/ Paint]
|-
| Pippy || Walter || git@github.com:walterbender/Pippy.git || [http://translate.sugarlabs.org/projects/Pippy/ Pippy]
|-
| Portfolio || Walter || git@github.com:walterbender/portfolio || [http://translate.sugarlabs.org/projects/Portfolio/ Portfolio]
|-
| Read || Godiard || git@github.com:godiard/read-activity.git || [http://translate.sugarlabs.org/projects/Read/ Read]
|-
| ReadETexts || || ||
|-
| Record || Godiard || git@github.com:godiard/record-activity.git || [http://translate.sugarlabs.org/projects/Record/ Record]
|-
| Speak || Walter || git@github.com:walterbender/speak.git || [http://translate.sugarlabs.org/projects/Speak/ Speak]
|-
| Terminal || Godiard || git@github.com:godiard/terminal-activity.git || [http://translate.sugarlabs.org/projects/Terminal/ Terminal]
|-
| TurtleArt || Walter || git@github.com:walterbender/turtleart.git || [http://translate.sugarlabs.org/projects/TurtleArt/ TurtleArt]
|-
| TurtleArtExtras || Walter || git@github.com:walterbender/turtleextras.git || [http://translate.sugarlabs.org/projects/TurtleArtExtras/ TurtleArtExtras]
|-
| Web || Godiard || git@github.com:sugarlabs/browse-activity.git || [http://translate.sugarlabs.org/projects/Web/ Web]
|-
| Write || Godiard || git@github.com:godiard/write-activity.git || [http://translate.sugarlabs.org/projects/Write/ Write]
|}

= Honey =

{| class="wikitable"
|-
! Module !! Maintainer !! Repository !! Project
|-
| Abacus || Walter || git@github.com:walterbender/abacus.git || [http://translate.sugarlabs.org/projects/Abacus/ Abacus]
|-
| Calendario || || ||
|-
| ClassromBroadcast || || ||
|-
| Clock || Cristian || git@github.com/cristian99garcia/ClockActivity.git || [http://translate.sugarlabs.org/projects/Clock/ Clock]
|-
| Distance || || ||
|-
| Finance || Godiard || git@github.com:godiard/finance-activity.git || [http://translate.sugarlabs.org/projects/Finance/ Finance]
|-
| FotoToon || Godiard || git@github.com:godiard/fototoon-activity.git || [http://translate.sugarlabs.org/projects/FotoToon/ FotoToon]
|-
| GetBooks || Godiard || git@github.com:godiard/get-books-activity.git ||
|-
| IKnowAmerica || AlanJAS || git@github.com:AlanJAS/iknowAmerica.git || [http://translate.sugarlabs.org/projects/IKnowAmerica/ IKnowAmerica]
|-
| Implode || || ||
|-
| Infoslicer || Walter || git@github.com:walterbender/infoslicer.git || [http://translate.sugarlabs.org/projects/InfoSlicer/ InfoSlicer]
|-
| Jigsaw puzzle|| || ||
|-
| Labyrinth || || ||
|-
| Maze || Godiard || git@github.com:godiard/maze-activity.git || [http://translate.sugarlabs.org/projects/Maze/ Maze]
|-
| Measure || Walter || git@github.com:walterbender/Measure.git || [http://translate.sugarlabs.org/projects/Measure/ Measure]
|-
| Memorize || Godiard || git@github.com:godiard/memorize-activity.git || [http://translate.sugarlabs.org/projects/Memorize/ Memorize]
|-
| Moon || || ||
|-
| Physics || Walter || git@github.com:walterbender/physics.git || [http://translate.sugarlabs.org/projects/Physics/ Physics]
|-
| Ruler || Walter || git@github.com:walterbender/ruler.git || [http://translate.sugarlabs.org/projects/Ruler/ Ruler]
|-
| Chart (SimpleGraph) || || ||
|-
| Slider puzzle || || ||
|-
| StopWatch || || ||
|-
| Story || Walter || git@github.com:walterbender/story.git || [http://translate.sugarlabs.org/projects/Story/ Story]
|-
| SimpleGNUChess || Walter || git@github.com:walterbender/sugarchess.git || [http://translate.sugarlabs.org/projects/SimpleGNUChess/ SimpleGNUChess]
|-
| TamTam Suite || || ||
|-
| TypingTurtle || GOdiard || git@github.com:godiard/typing-turtle-activity.git || [http://translate.sugarlabs.org/projects/TypingTurtle/ TypingTurtle]
|-
| ViewSlides || || ||
|-
| Dimensions || Walter || git@github.com:walterbender/dimensions.git || [http://translate.sugarlabs.org/projects/Dimensions/ Dimensions]
|-
| Watch Listen || || ||
|-
| Words || Godiard || git@github.com:godiard/words-activity.git || [http://translate.sugarlabs.org/projects/Words/ Words]
|-
| XoEditor || Walter || git@github.com:walterbender/xocolors.git || [http://translate.sugarlabs.org/projects/XoEditor/ XoEditor]
|}

= Honey2 =

{| class="wikitable"
|-
! Module !! Maintainer !! Repository !! Project
|-
| Analyze || || ||
|-
| AnalyzeJournal || Walter || git@github.com:walterbender/AnalyzeJournal.git || [http://translate.sugarlabs.org/projects/AnalyzeJournal/ AnalyzeJournal]
|-
| Annotate || || ||
|-
| Arithmetic || || ||
|-
| Biorhythm || AlanJAS || git@github.com:AlanJAS/biorhythm.git || [http://translate.sugarlabs.org/projects/Biorhythm/ Biorhythm]
|-
| Bridge || || ||
|-
| CardSort || Walter || git@github.com:walterbender/cardsort.git || [http://translate.sugarlabs.org/projects/CardSort/ CardSort]
|-
| CartoonBuilder || || ||
|-
| Colors || || ||
|-
| Convert || || ||
|-
| CookieSearch || Walter || git@github.com:walterbender/cookiesearch.git || [http://translate.sugarlabs.org/projects/CookieSearch/ CookieSearch]
|-
| Deducto || Walter || git@github.com:walterbender/deducto.git || [http://translate.sugarlabs.org/projects/Deducto/ Deducto]
|-
| Domino || Godiard || git@github.com:godiard/domino-activity.git || [http://translate.sugarlabs.org/projects/Domino/ Domino]
|-
| Dots and boxes || AlanJAS || git@github.com:AlanJAS/dotsAndBoxes.git || [http://translate.sugarlabs.org/projects/DotsAndBoxes/ DotsAndBoxes]
|-
| Erikos || Walter || git@github.com:walterbender/erikos.git || [http://translate.sugarlabs.org/projects/Erikos/ Erikos]
|-
| Flip || Walter || git@github.com:walterbender/flip.git || [http://translate.sugarlabs.org/projects/Flip/ Flip]
|-
| FlipSticks || || ||
|-
| Followme Butia || AlanJAS || git@github.com:AlanJAS/followme.git || [http://translate.sugarlabs.org/projects/FollowMeButia/ FollowMeButia]
|-
| FractionBounce || Walter || git@github.com:walterbender/fractionbounce.git || [http://translate.sugarlabs.org/projects/FractionBounce/ FractionBounce]
|-
| Get IA Books || Jdsimmons || git@github.com:jdsimmons/getiabooks.git ||
|-
| Gogo || || ||
|-
| Graph Plotter || || ||
|-
| Hello Mesh || || ||
|-
| HMouse || || ||
|-
| IknowIndia || AlanJAS || git@github.com:AlanJAS/iknowIndia.git || [http://translate.sugarlabs.org/projects/IknowIndia/ IknowIndia]
|-
| IknowPeru || AlanJAS || git@github.com:AlanJAS/iknowPeru.git || [http://translate.sugarlabs.org/projects/IknowPeru/ IknowPeru]
|-
| IknowUruguay || AlanJAS || git@github.com:AlanJAS/iknowUruguay.git || [http://translate.sugarlabs.org/projects/IknowUruguay/ IknowUruguay]
|-
| IKnowRwanda || AlanJAS || git@github.com:AlanJAS/iknowRwanda.git || [http://translate.sugarlabs.org/projects/IKnowRwanda/ IKnowRwanda]
|-
| IKnowSriLanka || AlanJAS || git@github.com:AlanJAS/iknowSriLanka.git || [http://translate.sugarlabs.org/projects/IKnowSriLanka/ IKnowSriLanka]
|-
| IKnowMadagascar || AlanJAS || git@github.com:AlanJAS/iknowMadagascar.git || [http://translate.sugarlabs.org/projects/IKnowMadagascar/ IKnowMadagascar]
|-
| Jamedia || || ||
|-
| Joke Machine || || ||
|-
| Jump || AlanJAS || git@github.com:AlanJAS/jump.git || [http://translate.sugarlabs.org/projects/Jump/ Jump]
|-
| Kandid || || ||
|-
| Karma 6 Englih animal identification || || ||
|-
| Lanzar || || ||
|-
| Level || || ||
|-
| LocoSugar || Walter || git@github.com:walterbender/locosugar.git || [http://translate.sugarlabs.org/projects/LocoSugar/ LocoSugar]
|-
| Mateton || || ||
|-
| Nutrition ||Walter || git@github.com:walterbender/nutrition.git || [http://translate.sugarlabs.org/projects/Nutrition/ Nutrition]
|-
| Panorama || AlanJAS || git@github.com:AlanJAS/panorama.git || [http://translate.sugarlabs.org/projects/Panorama/ Panorama]
|-
| Paths || Walter || git@github.com:walterbender/paths.git || [http://translate.sugarlabs.org/projects/Paths/ Paths]
|-
| Play Go || || ||
|-
| Plot || || ||
|-
| Pointillism || AlanJAS || git@github.com:AlanJAS/pointillism.git || [http://translate.sugarlabs.org/projects/Pointillism/ Pointillism]
|-
| Poll builder || || ||
|-
| Pukllanapac || Walter || git@github.com:walterbender/pukllanapac.git || [http://translate.sugarlabs.org/projects/Pukllanapac/ Pukllanapac]
|-
| PyDebug || || ||
|-
| Read SD Comics || Jdsimmons || git@github.com:jdsimmons/read-sd-comics.git ||
|-
| Recall || Walter || git@github.com:walterbender/recall.git || [http://translate.sugarlabs.org/projects/Recall/ Recall]
|-
| Reflection || Walter || git@github.com:walterbender/reflection.git || [http://translate.sugarlabs.org/projects/Reflection/ Reflection]
|-
| SlideRuler || Walter || git@github.com:walterbender/slideruler.git || [http://translate.sugarlabs.org/projects/SlideRuler/ SlideRuler]
|-
| StarChart || Walter || git@github.com:walterbender/starchart.git || [http://translate.sugarlabs.org/projects/StarChart/ StarChart]
|-
| StoryBuilder || || ||
|-
| SugarCommander || Jdsimmons || git@github.com:jdsimmons/sugar-commander.git ||
|-
| Telescope || || ||
|-
| Timeline || || ||
|-
| TurtlePond || Walter || git@github.com:walterbender/turtlepond.git || [http://translate.sugarlabs.org/projects/TurtlePond/ TurtlePond]
|-
| Yupana || Walter || git@github.com:walterbender/yupana.git || [http://translate.sugarlabs.org/projects/Yupana/ Yupana]
|}

Translation Team/Pootle Projects/Repositories

2014-12-26T02:15:42Z

Jdsimmons: /* Honey2 */

The Objective of this page is keep a updated list of the repositories where Pootle will push the translations.
If you are a maintainer and change the repository of your project, please notify to the pootle maintainers.
Pootle will pull and push to the master branch.

= Glucose =

{| class="wikitable"
|-
! Module !! Maintainer !! Repository !! Project
|-
| sugar || SugarLabs || git@github.com:sugarlabs/sugar.git || [http://translate.sugarlabs.org/projects/sugar/ sugar]
|-
| sugar-toolkit-gtk3 || SugarLabs || git@github.com:sugarlabs/sugar-toolkit-gtk3.git || [http://translate.sugarlabs.org/projects/sugar-toolkit-gtk3/ sugar-toolkit-gk3]
|}

= Fructose =

{| class="wikitable"
|-
! Module !! Maintainer !! Repository !! Project
|-
| Calculate || || ||
|-
| Chat || Walter || git@github.com:walterbender/chat.git || [http://translate.sugarlabs.org/projects/Chat/ Chat]
|-
| ImageViewer || Godiard || git@github.com:godiard/imageviewer-activity.git || [http://translate.sugarlabs.org/projects/ImageViewer/ ImageViewer]
|-
| Jukebox || Godiard || git@github.com:godiard/jukebox-activity.git || [http://translate.sugarlabs.org/projects/Jukebox/ Jukebox]
|-
| Log || Ignacio || git@github.com:ignaciouy/log.git || [http://translate.sugarlabs.org/projects/Log/ Log]
|-
| Paint || Godiard || git@github.com:godiard/paint-activity.git || [http://translate.sugarlabs.org/projects/Paint/ Paint]
|-
| Pippy || Walter || git@github.com:walterbender/Pippy.git || [http://translate.sugarlabs.org/projects/Pippy/ Pippy]
|-
| Portfolio || Walter || git@github.com:walterbender/portfolio || [http://translate.sugarlabs.org/projects/Portfolio/ Portfolio]
|-
| Read || Godiard || git@github.com:godiard/read-activity.git || [http://translate.sugarlabs.org/projects/Read/ Read]
|-
| ReadETexts || || ||
|-
| Record || Godiard || git@github.com:godiard/record-activity.git || [http://translate.sugarlabs.org/projects/Record/ Record]
|-
| Speak || Walter || git@github.com:walterbender/speak.git || [http://translate.sugarlabs.org/projects/Speak/ Speak]
|-
| Terminal || Godiard || git@github.com:godiard/terminal-activity.git || [http://translate.sugarlabs.org/projects/Terminal/ Terminal]
|-
| TurtleArt || Walter || git@github.com:walterbender/turtleart.git || [http://translate.sugarlabs.org/projects/TurtleArt/ TurtleArt]
|-
| TurtleArtExtras || Walter || git@github.com:walterbender/turtleextras.git || [http://translate.sugarlabs.org/projects/TurtleArtExtras/ TurtleArtExtras]
|-
| Web || Godiard || git@github.com:sugarlabs/browse-activity.git || [http://translate.sugarlabs.org/projects/Web/ Web]
|-
| Write || Godiard || git@github.com:godiard/write-activity.git || [http://translate.sugarlabs.org/projects/Write/ Write]
|}

= Honey =

{| class="wikitable"
|-
! Module !! Maintainer !! Repository !! Project
|-
| Abacus || Walter || git@github.com:walterbender/abacus.git || [http://translate.sugarlabs.org/projects/Abacus/ Abacus]
|-
| Calendario || || ||
|-
| ClassromBroadcast || || ||
|-
| Clock || Cristian || git@github.com/cristian99garcia/ClockActivity.git || [http://translate.sugarlabs.org/projects/Clock/ Clock]
|-
| Distance || || ||
|-
| Finance || Godiard || git@github.com:godiard/finance-activity.git || [http://translate.sugarlabs.org/projects/Finance/ Finance]
|-
| FotoToon || Godiard || git@github.com:godiard/fototoon-activity.git || [http://translate.sugarlabs.org/projects/FotoToon/ FotoToon]
|-
| GetBooks || Godiard || git@github.com:godiard/get-books-activity.git ||
|-
| IKnowAmerica || AlanJAS || git@github.com:AlanJAS/iknowAmerica.git || [http://translate.sugarlabs.org/projects/IKnowAmerica/ IKnowAmerica]
|-
| Implode || || ||
|-
| Infoslicer || Walter || git@github.com:walterbender/infoslicer.git || [http://translate.sugarlabs.org/projects/InfoSlicer/ InfoSlicer]
|-
| Jigsaw puzzle|| || ||
|-
| Labyrinth || || ||
|-
| Maze || Godiard || git@github.com:godiard/maze-activity.git || [http://translate.sugarlabs.org/projects/Maze/ Maze]
|-
| Measure || Walter || git@github.com:walterbender/Measure.git || [http://translate.sugarlabs.org/projects/Measure/ Measure]
|-
| Memorize || Godiard || git@github.com:godiard/memorize-activity.git || [http://translate.sugarlabs.org/projects/Memorize/ Memorize]
|-
| Moon || || ||
|-
| Physics || Walter || git@github.com:walterbender/physics.git || [http://translate.sugarlabs.org/projects/Physics/ Physics]
|-
| Ruler || Walter || git@github.com:walterbender/ruler.git || [http://translate.sugarlabs.org/projects/Ruler/ Ruler]
|-
| Chart (SimpleGraph) || || ||
|-
| Slider puzzle || || ||
|-
| StopWatch || || ||
|-
| Story || Walter || git@github.com:walterbender/story.git || [http://translate.sugarlabs.org/projects/Story/ Story]
|-
| SimpleGNUChess || Walter || git@github.com:walterbender/sugarchess.git || [http://translate.sugarlabs.org/projects/SimpleGNUChess/ SimpleGNUChess]
|-
| TamTam Suite || || ||
|-
| TypingTurtle || GOdiard || git@github.com:godiard/typing-turtle-activity.git || [http://translate.sugarlabs.org/projects/TypingTurtle/ TypingTurtle]
|-
| ViewSlides || || ||
|-
| Dimensions || Walter || git@github.com:walterbender/dimensions.git || [http://translate.sugarlabs.org/projects/Dimensions/ Dimensions]
|-
| Watch Listen || || ||
|-
| Words || Godiard || git@github.com:godiard/words-activity.git || [http://translate.sugarlabs.org/projects/Words/ Words]
|-
| XoEditor || Walter || git@github.com:walterbender/xocolors.git || [http://translate.sugarlabs.org/projects/XoEditor/ XoEditor]
|}

= Honey2 =

{| class="wikitable"
|-
! Module !! Maintainer !! Repository !! Project
|-
| Analyze || || ||
|-
| AnalyzeJournal || Walter || git@github.com:walterbender/AnalyzeJournal.git || [http://translate.sugarlabs.org/projects/AnalyzeJournal/ AnalyzeJournal]
|-
| Annotate || || ||
|-
| Arithmetic || || ||
|-
| Biorhythm || AlanJAS || git@github.com:AlanJAS/biorhythm.git || [http://translate.sugarlabs.org/projects/Biorhythm/ Biorhythm]
|-
| Bridge || || ||
|-
| CardSort || Walter || git@github.com:walterbender/cardsort.git || [http://translate.sugarlabs.org/projects/CardSort/ CardSort]
|-
| CartoonBuilder || || ||
|-
| Colors || || ||
|-
| Convert || || ||
|-
| CookieSearch || Walter || git@github.com:walterbender/cookiesearch.git || [http://translate.sugarlabs.org/projects/CookieSearch/ CookieSearch]
|-
| Deducto || Walter || git@github.com:walterbender/deducto.git || [http://translate.sugarlabs.org/projects/Deducto/ Deducto]
|-
| Domino || Godiard || git@github.com:godiard/domino-activity.git || [http://translate.sugarlabs.org/projects/Domino/ Domino]
|-
| Dots and boxes || AlanJAS || git@github.com:AlanJAS/dotsAndBoxes.git || [http://translate.sugarlabs.org/projects/DotsAndBoxes/ DotsAndBoxes]
|-
| Erikos || Walter || git@github.com:walterbender/erikos.git || [http://translate.sugarlabs.org/projects/Erikos/ Erikos]
|-
| Flip || Walter || git@github.com:walterbender/flip.git || [http://translate.sugarlabs.org/projects/Flip/ Flip]
|-
| FlipSticks || || ||
|-
| Followme Butia || AlanJAS || git@github.com:AlanJAS/followme.git || [http://translate.sugarlabs.org/projects/FollowMeButia/ FollowMeButia]
|-
| FractionBounce || Walter || git@github.com:walterbender/fractionbounce.git || [http://translate.sugarlabs.org/projects/FractionBounce/ FractionBounce]
|-
| Get IA Books || Jdsimmons || git@github.com:jdsimmons/getiabooks.git ||
|-
| Gogo || || ||
|-
| Graph Plotter || || ||
|-
| Hello Mesh || || ||
|-
| HMouse || || ||
|-
| IknowIndia || AlanJAS || git@github.com:AlanJAS/iknowIndia.git || [http://translate.sugarlabs.org/projects/IknowIndia/ IknowIndia]
|-
| IknowPeru || AlanJAS || git@github.com:AlanJAS/iknowPeru.git || [http://translate.sugarlabs.org/projects/IknowPeru/ IknowPeru]
|-
| IknowUruguay || AlanJAS || git@github.com:AlanJAS/iknowUruguay.git || [http://translate.sugarlabs.org/projects/IknowUruguay/ IknowUruguay]
|-
| IKnowRwanda || AlanJAS || git@github.com:AlanJAS/iknowRwanda.git || [http://translate.sugarlabs.org/projects/IKnowRwanda/ IKnowRwanda]
|-
| IKnowSriLanka || AlanJAS || git@github.com:AlanJAS/iknowSriLanka.git || [http://translate.sugarlabs.org/projects/IKnowSriLanka/ IKnowSriLanka]
|-
| IKnowMadagascar || AlanJAS || git@github.com:AlanJAS/iknowMadagascar.git || [http://translate.sugarlabs.org/projects/IKnowMadagascar/ IKnowMadagascar]
|-
| Jamedia || || ||
|-
| Joke Machine || || ||
|-
| Jump || AlanJAS || git@github.com:AlanJAS/jump.git || [http://translate.sugarlabs.org/projects/Jump/ Jump]
|-
| Kandid || || ||
|-
| Karma 6 Englih animal identification || || ||
|-
| Lanzar || || ||
|-
| Level || || ||
|-
| LocoSugar || Walter || git@github.com:walterbender/locosugar.git || [http://translate.sugarlabs.org/projects/LocoSugar/ LocoSugar]
|-
| Mateton || || ||
|-
| Nutrition ||Walter || git@github.com:walterbender/nutrition.git || [http://translate.sugarlabs.org/projects/Nutrition/ Nutrition]
|-
| Panorama || AlanJAS || git@github.com:AlanJAS/panorama.git || [http://translate.sugarlabs.org/projects/Panorama/ Panorama]
|-
| Paths || Walter || git@github.com:walterbender/paths.git || [http://translate.sugarlabs.org/projects/Paths/ Paths]
|-
| Play Go || || ||
|-
| Plot || || ||
|-
| Pointillism || AlanJAS || git@github.com:AlanJAS/pointillism.git || [http://translate.sugarlabs.org/projects/Pointillism/ Pointillism]
|-
| Poll builder || || ||
|-
| Pukllanapac || Walter || git@github.com:walterbender/pukllanapac.git || [http://translate.sugarlabs.org/projects/Pukllanapac/ Pukllanapac]
|-
| PyDebug || || ||
|-
| Read SD Comics || || ||
|-
| Recall || Walter || git@github.com:walterbender/recall.git || [http://translate.sugarlabs.org/projects/Recall/ Recall]
|-
| Reflection || Walter || git@github.com:walterbender/reflection.git || [http://translate.sugarlabs.org/projects/Reflection/ Reflection]
|-
| SlideRuler || Walter || git@github.com:walterbender/slideruler.git || [http://translate.sugarlabs.org/projects/SlideRuler/ SlideRuler]
|-
| StarChart || Walter || git@github.com:walterbender/starchart.git || [http://translate.sugarlabs.org/projects/StarChart/ StarChart]
|-
| StoryBuilder || || ||
|-
| SugarCommander || Jdsimmons || git@github.com:jdsimmons/sugar-commander.git ||
|-
| Telescope || || ||
|-
| Timeline || || ||
|-
| TurtlePond || Walter || git@github.com:walterbender/turtlepond.git || [http://translate.sugarlabs.org/projects/TurtlePond/ TurtlePond]
|-
| Yupana || Walter || git@github.com:walterbender/yupana.git || [http://translate.sugarlabs.org/projects/Yupana/ Yupana]
|}

Google Code In 2013

2013-10-23T14:33:24Z

Jdsimmons: /* Mentors */

This is the project page for the Sugar Labs application to Google Code In. Sugar Labs community members: please feel free to add tasks below. We'll do an edit before final applications are due on 28 Oct 2013.

== Message to potential participants ==

It is important that you obtain permission of your parents.

Es importante que obtengas el permiso de tus padres para participar.

http://www.google-melange.com/gci/document/show/gci_program/google/gci2013/help_page#eligibility

Please see the Contest Rules for Eligibility and Registration process.

http://www.google-melange.com/gci/document/show/gci_program/google/gci2013/terms_and_conditions

'''Details regarding the required forms and paperwork are here: [[Google Code In 2013/Participate#Students]].'''

== Why we are participating ==

Sugar is written and maintained by volunteers, who range from seasoned professionals to children as young as 12-years of age. Children who have grown up with Sugar have transitioned from Sugar users to Sugar App developers to Sugar maintainers. They hang out on IRC with the global Sugar developer community and are full-fledged members of the Sugar development team. It is this latter group of children we hope will participate in and benefit from Google Code-in. Specifically we want to re-enforce the message that Sugar belongs to its users and that they have both ownership and the responsibility that ownership implies. Just as learning is not something done to you, but something you do, learning with Sugar ultimately means participating in the Sugar development process. At Sugar Labs, we are trying to bring the culture of Free Software into the culture of school. So the Code-in is not just an opportunity for us to get some tasks accomplished, it is quintessential to our overall mission.

== Tasks ==
Tasks must fall within one of these five categories:
;Code: Tasks related to writing or refactoring code
;Documentation/Training: Tasks related to creating/editing documents and helping others learn more
;Outreach/Research: Tasks related to community management, outreach/marketing, or studying problems and recommending solutions
;Quality Assurance: Tasks related to testing and ensuring code is of high quality.
;User Interface: Tasks related to user experience research or user interface design and interaction

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
!Title !! Description !! Hours !! Mentor !! Category !! Tag
|-
|Portfolio videos || align=left | [[Google Code In 2013/Portfolio_videos|Add a mechanism for exporting .ogv (voice over still images) of a portfolio presentation]] || 20 || walterbender || Code || activity
|-
|Abacus gestures || align=left | [[Google Code In 2013/Abacus gestures|Add gestures to resize custom abacus|]] || 20 || walterbender || Code || activity
|-
|Portfolio videos || align=left | [[Google Code In 2013/Portfolio_videos|Add a mechanism for exporting .ogv (voice over still images) of a portfolio presentation]] || 20 || walterbender || Code || activity

|-
|Activity/Journal views || align=left | [http://bugs.sugarlabs.org/ticket/806 Activities list view is very similar to Journal view and users delete activities instead of journal entries] || || || UI || activity
|-
|Sugar version || align=left | [http://bugs.sugarlabs.org/ticket/1442 Reject activity bundles which require a newer version of Sugar] || || || Code || sugar
|-
|Multiple school servers || align=left | [http://bugs.sugarlabs.org/ticket/362 can't register with multiple school servers] || || || Code || sugar
|-
|Neighborhood view || align=left | [http://bugs.sugarlabs.org/ticket/381 Neighbourhood view icons should be placed in a spatially repeatable way] || || || UI || sugar
|-
|Force close || align=left | [http://bugs.sugarlabs.org/ticket/1646 No way to force-close (kill) an activity] || || || Code || toolkit
|-
|Screenshot || align=left | [http://bugs.sugarlabs.org/ticket/4015 Touch: make take screenshot available] || || || UI || sugar
|-
|Brightness mode || align=left | [http://bugs.sugarlabs.org/ticket/4016 Touch: change brightness and mode] || || || UI || sugar
|-
|OSK design || align=left | [http://bugs.sugarlabs.org/ticket/4581 Shift key on OSK looks the same in all modes] || || || UI || sugar
|-
|Mic volume || align=left | [http://bugs.sugarlabs.org/ticket/800 Set audio capture volumes] || || || Code || sugar
|-
|Bug reporting || align=left | [http://bugs.sugarlabs.org/ticket/1050 inform user about exceptions, offer to file a bug report] || || || Code || sugar
|-
|Multi-person send || align=left | [http://bugs.sugarlabs.org/ticket/1471 Send a file to more than one person at a time] || || || Code || sugar
|-
|Filter for bundles || align=left | [http://bugs.sugarlabs.org/ticket/1712 Add journal filter for .xo bundles] || || || Code || sugar
|-
|Screensaver || align=left | [http://bugs.sugarlabs.org/ticket/2105 add a screensaver to Sugar] || || || Code || sugar
|-
|Network forget || align=left | [http://bugs.sugarlabs.org/ticket/2264 Network, forget, or remove as favourite] || || || Code || sugar
|-
|Release hidden resources || align=left | [http://bugs.sugarlabs.org/ticket/2416 provide framework code for releasing resources while hidden] || || || Code || sugar
|-
|setlocale || align=left | [http://bugs.sugarlabs.org/ticket/2433 class Activity should setlocale] || || || Code || toolkit
|-
|Upgrade restrictions || align=left | [http://bugs.sugarlabs.org/ticket/2452 Sugar should not offer to upgrade system activities] || || || Code || sugar
|-
|Transfer all metadata || align=left | [http://bugs.sugarlabs.org/ticket/2473 transfer entire data store entry, including arbitrary metadata] || || || Code || sugar
|-
|Journal progress || align=left | [http://bugs.sugarlabs.org/ticket/2480 Journal file actions need progress/busy indication] || || || Code || sugar
|-
|CDMA modems || align=left | [http://bugs.sugarlabs.org/ticket/2528 Sugar should support CDMA modems as well as GSM] || || || Code || sugar
|-
|Proxies || align=left | [http://bugs.sugarlabs.org/ticket/2821 Sugar should directly get proxy settings from gconf] || || gonzalo_odiard|| Code || sugar
|-
|rfkill || align=left | [http://bugs.sugarlabs.org/ticket/2869 Radio/wireless control should interact with rfkill] || || || Code || sugar
|-
|set mimetypes || align=left | [http://bugs.sugarlabs.org/ticket/2924 set mimetype in detail view] || || || Code || sugar
|-
|Drag to clipboard || align=left | [http://bugs.sugarlabs.org/ticket/2989 Be able to drag and drop items from Journal to clipboard] || || || Code || sugar
|-
|Absolute date/time || align=left | [http://bugs.sugarlabs.org/ticket/3002 Show absolute date in creation time sort mode] || || || Code || sugar
|-
|Time filters || align=left | [http://bugs.sugarlabs.org/ticket/3026 Time filter only cuts off the end of the list instead of offering disjunct time spans] || || || Code || sugar
|-
|Canvas-only screenshot || align=left | [http://bugs.sugarlabs.org/ticket/3028 Add modifier to take screenshot only with the canvas] || || || Code || sugar
|-
|View Source paths || align=left | [http://bugs.sugarlabs.org/ticket/3073 Reveal path to View source entries] || || || Code || toolkit
|-
|Stop pulsing icon || align=left | [http://bugs.sugarlabs.org/ticket/3092 Stop start-up icon pulsing when an activity fails to start] || || || Code || toolkit
|-
|Icon-slicer dependency || align=left | [http://bugs.sugarlabs.org/ticket/3143 remove icon-slicer dependency] || || || Code || activity
|-
|Activity-specific metadata || align=left | [http://bugs.sugarlabs.org/ticket/3209 Journal should support display of activity-specific metadata] || || walter || Code || sugar
|-
|gtk-accelerator || align=left | [http://bugs.sugarlabs.org/ticket/3412 Use gtk_accelerator_parse() instead of egg for key handling] || || || Code || sugar
|-
|Show progress on install || align=left | [http://bugs.sugarlabs.org/ticket/3627 Installing an activity should show progress information] || || || Code || sugar
|-
|fullscreen property || align=left | [http://bugs.sugarlabs.org/ticket/3665 expose _is_fullscreen as a window property] || || walter || Code || activity
|-
|Duplicate progress bar || align=left | [http://bugs.sugarlabs.org/ticket/3672 duplicate function in view source needs progress bar] || || walter || Code || toolkit
|-
|Supported mimetypes || align=left | [http://bugs.sugarlabs.org/ticket/3826 Get supported audio and video mime types from gstreamer] || || || Code || toolkit
|-
|Set time || align=left | [http://bugs.sugarlabs.org/ticket/3829 Allow Sugar users to adjust clock time and date] || || || Code || sugar
|-
|Additional folders in Journal || align=left | [http://bugs.sugarlabs.org/ticket/3856 Add other folders to Journal] || || || Code || sugar
|-
|Wifi rescan || align=left | [http://bugs.sugarlabs.org/ticket/3876 Sugar needs method to force wifi network rescan] || || || Code || sugar
|-
|forced view updates || align=left | [http://bugs.sugarlabs.org/ticket/3877 Sugar needs method to force Buddy/Shared Activities Network view update] || || || Code || sugar
|-
|Button design || align=left | [http://bugs.sugarlabs.org/ticket/4257 Toolbar overflow button: add a better looking arrow] || || walter || UI || sugar
|-
|Language control panel || align=left | [http://bugs.sugarlabs.org/ticket/4327 Language CP module displays combo text in 2nd preferred language] || || || Code || sugar
|-
|MessageBox || align=left | [http://bugs.sugarlabs.org/ticket/4398 Toolkit: add MessageBox] || || manuq || Code || toolkit
|-
|Image preview on clipboard || align=left | [http://bugs.sugarlabs.org/ticket/4614 sugar: implement preview on clipboard button for images] || || || Code || sugar
|-
|Use latest toolbars in MYOSA examples || align=left | Make Your Own Sugar Activities! describes our current toolbar code as "new" and uses the old style in examples. Correct this. || || James Simmons || Code || activity
|}

== Mentors ==
;NOTES TO MENTORS:
:Please refer to [[Google Code In 2013/Participate#Mentors]] for details regarding enrolling as a mentor.
:Please add yourself to the list below.
:Feel free to add new tasks to the table above.

Depending on the project, we will assign multiple mentors from our various development and support teams.

* Walter Bender - also org admin for GCI
* Martin Abente
* Sandra Thaxter
* James Simmons

[[Category: GCI2013]]

Google Code In 2013

2013-10-23T14:31:56Z

Jdsimmons: /* Tasks */

Google Code-In 2012/GCI2012 followup

2013-01-22T15:51:11Z

Jdsimmons:

Listed on this page are the completed tasks, one per row. If you were the mentor for a given task, please review the list of completed tasks
and if the task is completely incorporated, just delete the row from the table. Otherwise, add some annotation to the follow-up needed or
comment columns.

To get more information on a task, append the "Key" onto a URL to see the original history of the task on the GCI Melange server.

e.g.

add 7986212 to the end of:

http://www.google-melange.com/gci/task/view/google/gci2012/

to see the history of that task on Melange
http://www.google-melange.com/gci/task/view/google/gci2012/7986212

{| class="wikitable"
|-
! Key!! Title!! Type!! Tags!! Mentors!! Student!! Follow-up Needed!! Comment
|-
| 7986212 || Accelerometer || User Interface || sugar || Tony Forster || Ben || ||
|-
| 8150202 || Accelerometer emulator || Code || activity || Walter Bender || Aneesh Dogra || ||
|-
| 8145202 || Add customization to Letter Match || Code || activity || Walter Bender || Aneesh Dogra || ||
|-
| 8127202 || Add move timer to Sugar GNUChess || Code || activity || Walter Bender || Aneesh Dogra || ||
|-
| 8084205 || adjustable clock || Code || activity || Walter Bender || Scimonster || ||
|-
| 7959255 || Browse i18n improvement || Code || sugar || Chris Leonard || Aneesh Dogra || delete git clone? || patch landed
|-
| 7978217 || Calculate activity bug fix || Code || activity || Walter Bender || Aneesh Dogra || ||
|-
| 7960238 || Calculate activity bug fix too || Code || activity || Walter Bender || Aneesh Dogra || ||
|-
| 8015208 || Calculate activity enhancement 1 || Code || Calculate || Walter Bender, Manuel Kaufmann || Aneesh Dogra || ||
|-
| 7959211 || Calculate activity enhancement 2 || Code || Calculate || Walter Bender, Manuel Kaufmann || Aneesh Dogra || ||
|-
| 8021207 || Calculate activity enhancement 3 || Code || Calculate || Walter Bender, Manuel Kaufmann || Aneesh Dogra || ||
|-
| 8024206 || Calculate activity enhancement 4 || Code || Calculate || Walter Bender, Manuel Kaufmann || Agustín Zubiaga || ||
|-
| 8024207 || Calculate activity enhancement 5 || Code || Calculate || Walter Bender, Manuel Kaufmann || Aneesh Dogra || ||
|-
| 8018206 || Calculate activity enhancement 6 || Code || Calculate || Walter Bender, Manuel Kaufmann || Aneesh Dogra || ||
|-
| 7994218 || CantaBichos i18n || Code || i18n || Luke Faraone, Walter Bender, Chris Leonard || Aneesh Dogra || git merge needed || http://git.sugarlabs.org/cantabichos/cantabichos/merge_requests
|-
| 7958217 || Conozco Elementos Químicos i18n || Code || i18n || Luke Faraone, Chris Leonard, Walter Bender || Aneesh Dogra || git repo rename, add to pootle || http://git.sugarlabs.org/conozco-elementos-qu-micos-translation
|-
| 7994219 || Conozco Peru i18n || Code || i18n || Luke Faraone, Chris Leonard, Walter Bender || Aneesh Dogra || Add to Pootle || https://bugs.sugarlabs.org/ticket/4293
|-
| 8115206 || ConstellationFlashCard cleanup || Code || activity || Walter Bender || Aneesh Dogra || ||
|-
| 7974243 || ConstellationsFlashCards i18n || Code || i18n || Luke Faraone, Chris Leonard, Walter Bender || Aneesh Dogra || Add to Pootle || https://bugs.sugarlabs.org/ticket/4347
|-
| 7955223 || Convert Clock to GTK3 || Code || gtk3 || Walter Bender || Kshitij Kumar || ||
|-
| 8077207 || Convert ConstellationsFlashCards to new toolbar style and GTK3 || Code || activity || Walter Bender || Aneesh Dogra || ||
|-
| 7945226 || Convert Get IA Books to GTK3 || Code || gtk3 || Walter Bender || Aneesh Dogra || Not published on ASLO ||
|-
| 7961221 || Convert IRC to GTK3 || Code || gtk3 || Walter Bender || Aneesh Dogra || ||
|-
| 7948228 || Convert Memorize to GTK3 || Code || gtk3 || Walter Bender || Kshitij Kumar || ||
|-
| 7974262 || Convert Moon to GTK3 || Code || gtk3 || Walter Bender || Kshitij Kumar || NeedsWork ||
|-
| 7948229 || Convert Physics to GTK3 || Code || gtk3 || Walter Bender || Daniel Francis || ||
|-
| 8092208 || Convert physics to SugarGames || Code || activity || Walter Bender || Daniel Francis || ||
|-
| 7987230 || Convert Read Etexts to GTK3 || Code || gtk3 || Walter Bender || Aneesh Dogra || Not published on ASLO ||
|-
| 8049202 || Convert Slider Puzzle to GTK3 || Code || gtk3 || Walter Bender || Aneesh Dogra || ||
|-
| 8048203 || Convert Speak to GTK3 || Code || gtk3 || Walter Bender || Iva Dobreva || ||
|-
| 7948230 || Convert TamTamEdit to GTK3 || Code || gtk3 || Walter Bender || Aaron || ||
|-
| 7958230 || Convert View Slides to GTK3 || Code || gtk3 || Walter Bender || Aneesh Dogra || Not published on ASLO ||
|-
| 7992214 || Create new Sugar Labs home page || Documentation/Training || www || John Tierney || cheekujodhpur || ||
|-
| 8056202 || Create RPM for TurtleArt || Code || packaging || Jeffrey Elkner, Walter Bender, Luke Faraone || Daniel Francis || ||
|-
| 7945216 || CucaraSims i18n || Code || i18n || Luke Faraone, Walter Bender, Chris Leonard || Aneesh Dogra || git merge needed || http://git.sugarlabs.org/cucarasims/cucarasims/merge_requests
|-
| 7998224 || Fototoon: Export as a book || Code || activity || Gonzalo Odiard || Agustín Zubiaga || ||
|-
| 8022216 || Free Cell i18n || Code || i18n || Luke Faraone, Chris Leonard, Walter Bender || CWong || Place merge request, add to Pootle || http://git.sugarlabs.org/~cwong/freecell/cwongs-mainline
|-
| 8018207 || GTK2-to-GTK3 conversion || Code || gtk3 || Walter Bender, Manuel Kaufmann || cheekujodhpur || ||
|-
| 7986211 || How are we doing? || User Interface || learning || ClaudiaU || Clayton Condon || ||
|-
| 7959222 || How to create a collection || Documentation/Training || doc || JZA || CWong || ||
|-
| 7987234 || How to get git installed in Windows || Documentation/Training || doc || Walter Bender || Sumit Shyamsukha || ||
|-
| 8006228 || How-to video: Sugar on a Stick || Documentation/Training || doc || Walter Bender, John Tierney || cheekujodhpur || ||
|-
| 8017217 || How-to video: Sugar on a Stick (Windows 8) || Documentation/Training || doc || Walter Bender, John Tierney || Sumit Shyamsukha || ||
|-
| 8007217 || How-to videos || Documentation/Training || doc || John Tierney || Julian || ||
|-
| 8018203 || Implement a presentation mode in Fototoon || Code || activity || Gonzalo Odiard || Agustín Zubiaga || ||
|-
| 8047202 || Improve text handling in Fototoon || Code || activity || Gonzalo Odiard || Agustín Zubiaga || ||
|-
| 7972208 || Infoslicer enhancement (journal images) || Code || activity || Manuel Kaufmann || Aneesh Dogra || ||
|-
| 7978207 || Infoslicer enhancement (wikislices) || Code || activity || Manuel Kaufmann || Aneesh Dogra || ||
|-
| 7988217 || Installing Sugar over a low-bandwidth connection || Outreach/Research || soas || Walter Bender || Sumit Shyamsukha || ||
|-
| 8118202 || IRC activity defaults || Code || activity || Walter Bender || Aneesh Dogra || ||
|-
| 8095215 || Level Tool || Code || activity || Tony Forster, Walter Bender || Aneesh Dogra || ||
|-
| 8085209 || Local wiki snapshot export to Journal || Code || activity || Walter Bender || Aneesh Dogra || ||
|-
| 8011208 || Log activity enhancement || Code || Log || Walter Bender, Manuel Kaufmann || Agustín Zubiaga || ||
|-
| 8019215 || Make your own Sugar activity: Webkit || Documentation/Training || doc || James Simmons || Kshitij Kumar || Chapter Not Finished ||
|-
| 8016205 || Manage on-line credentials || User Interface || || rgs || Ben || ||
|-
| 8019209 || Moon activity enhancement 1 || Code || Moon || Walter Bender, Manuel Kaufmann || cheekujodhpur || ||
|-
| 7959212 || Moon activity enhancement 2 || Code || Moon || Walter Bender, Manuel Kaufmann || Marius Gavrilescu || ||
|-
| 8137205 || move ConstellationsFlashCards results to toolbar || Code || activity || Walter Bender || Aneesh Dogra || ||
|-
| 7972217 || Multilanguage screen-shots || Documentation/Training || i18n || Chris Leonard || Yatharth Agarwal || downloaded || should be wiki'ed
|-
| 8001204 || Multiple Homeviews || Code || sugar || Walter Bender || Daniel Francis || ||
|-
| 7947214 || New Features || User Interface || future || Walter Bender, JZA || Clayton Condon || ||
|-
| 8019207 || Orphaned activities || Quality Assurance || maintenance || Gonzalo Odiard || Marius Gavrilescu || ||
|-
| 7968208 || Package toolbar utils || Code || toolkit || Walter Bender || Daniel Francis || ||
|-
| 8164204 || Pausing GST when playing audio || Code || activity || Walter Bender || Aneesh Dogra || ||
|-
| 7949211 || Pootle helper-script || Code || i18n || Chris Leonard || Aviral Dasgupta || downloaded || compare to alsroot solution, implement one of them
|-
| 8210204 || port custom toolbar to GTK3 (Ruler) || Code || activity || Walter Bender || Aneesh Dogra || ||
|-
| 8147206 || port play_audio_file to gst 1.0 || Code || activity || Walter Bender || Aneesh Dogra || ||
|-
| 7994231 || Port to Python3 || Outreach/Research || future || Walter Bender || Kshitij Kumar || ||
|-
| 7997213 || RESERVED Wiki clean up (7 of 20) || Documentation/Training || || Frederick Grose, Luke Faraone || Aneesh Dogra || ||
|-
| 7953211 || Set background image || Code || sugar || Walter Bender || Agustín Zubiaga || ||
|-
| 8024204 || Special Needs || User Interface || sugar || Martín Abente Lahaye || MinSik CHO || ||
|-
| 8021205 || Stopwatch enhancement || Code || StopWatch || Walter Bender, Manuel Kaufmann || Andrew || ||
|-
| 7982214 || Sugar assessment tools || Outreach/Research || assessment || Tony Forster, ClaudiaU || Clayton Condon || ||
|-
| 7984217 || Sugar Documentation || Quality Assurance || doc || Tony Forster || Kshitij Kumar || ||
|-
| 8020208 || Sugar FLOSS Manual || Documentation/Training || doc, update, documentation, technical writing, || JZA || Kshitij Kumar || ||
|-
| 7952220 || Sugar i18n || Quality Assurance || i18n || Luke Faraone || Iva Dobreva || || should be wiki'ed
|-
| 8019210 || Sugar in the Cloud || Outreach/Research || future || Luis Gustavo Lira || braden || ||
|-
| 7984216 || Sugar in your school (opportunities) || Outreach/Research || outreach || Tony Forster, ClaudiaU || Kshitij Kumar || ||
|-
| 8013202 || Sugar in your school (roadblocks) || Outreach/Research || outreach || Tony Forster, ClaudiaU || Kshitij Kumar || ||
|-
| 8032204 || Sugar Network Contributor Hub look and feel || User Interface || sugar-network || Aleksey Lim || HD || ||
|-
| 7971214 || Sugar on a Stick guide || Documentation/Training || soas || satellit || Michael Jin || ||
|-
| 7972209 || Sugar on Android || Outreach/Research || future || Andrés Aguirre Dorelo || John Kim || ||
|-
| 7977210 || Sugar Touch || Quality Assurance || maintenance || Tony Forster || CWong || ||
|-
| 7949215 || Sugar VM || Documentation/Training || soas || satellit || Michael Jin || ||
|-
| 8025208 || Sugarize Python Turtle module || Code || activity || Walter Bender || Aaron || ||
|-
| 8016213 || SVG internationalization || Outreach/Research || i18n, svg, javascript || JZA || Kshitij Kumar || ||
|-
| 7994220 || Theorie i18n || Code || i18n || Luke Faraone, Walter Bender, Chris Leonard || Aneesh Dogra || Add to Pootle || https://bugs.sugarlabs.org/ticket/4291
|-
| 7970230 || Touch UI || User Interface || sugar || Walter Bender || Anish Basu || NeedsReview ||
|-
| 7949212 || Turtle Art nutrition || Code || activity || Walter Bender || Rafael || ||
|-
| 7966208 || Turtle Art tutorial || Documentation/Training || activity || Jeffrey Elkner, Tony Forster, Walter Bender || Anna-Mariya Mateyna || ||
|-
| 7976214 || Turtle Art with Sensors Tutorial || Documentation/Training || activity || Tony Forster, Walter Bender || Toshita Barve || ||
|-
| 8094204 || Update the Spansih version of Using Sugar in the Classroom to Sugar 0.98 || Documentation/Training || documentation || Walter Bender || Rafael || ||
|-
| 8133205 || user-defined units for Ruler Tool || Code || activity || Walter Bender || Aneesh Dogra || ||
|-
| 8101206 || Using Sugar in the Classroom || Documentation/Training || documentation || Walter Bender || Rafael || ||
|-
| 8106205 || video chat for Sugar Chess || Code || activity || Walter Bender || Aneesh Dogra || ||
|-
| 7998222 || Web lightbox feature || Code || www || Walter Bender || cheekujodhpur || ||
|-
| 7950210 || Write activity enhancement || Code || Write || Gonzalo Odiard || Aneesh Dogra || ||

|}

GoogleCodeIn2012/MYOSA

2012-11-14T17:16:43Z

Jdsimmons: /* Possible tasks */

The manual [http://en.flossmanuals.net/make-your-own-sugar-activities/index/ Make Your Own Sugar Activities!] was written by James Simmons a few years ago. It is still the most complete guide to making Sugar Activities, but it is already out of date. Two things have changed since it was first published:

# Sugar now uses GTK3 to create user interfaces. The examples in the book use the older GTK, which is still available, but Activities should start using the new GTK3. The examples need to be updated and re-tested.
# When James wrote the book he hoped it would help students write their own Activities. Whether the book helped or not, the fact is that students '''are''' writing Sugar Activities and even contributing to the Sugar environment itself. It is time for these students to stand up and be counted. Show off what you know, put your bio in the "About The Authors" chapter, and enjoy the benefits of being a published author. Impress friends, family, girls, boys, and future employers.

Of the two reasons to update the book the second one is clearly the most important.

== Possible tasks ==

# Create versions of the code samples in the book that work with GTK 3. These will go in the Git repository alongside the old versions (instead of just replacing them).
# Have you "Sugarized" an application not originally written for Sugar? Write a chapter explaining how you did it!
# Find a PyGame application that uses olpcgames, rework it to use SugarGame, and write up how you did it!
# Have you worked on improvements to Sugar itself? Tell us about it! Did your changes become part of the official Sugar distribution? How did you make that happen? How did you do testing, version control, etc? We want the whole story!
# Some applications use WebKit to display HTML and make it possible to create Activities using HTML5 and JavaScript. The current manual doesn't explain how to use the WebKit component in an Activity. We could use a chapter on this, with sample code.
# The current manual only talks about making Activities using Python. Have you made an Activity using a different language than that? Write a chapter about it!
# Do you know how to do something else that isn't in the book but should be? Write a chapter about it!
# Can you do a good translation from English to Spanish (or Spanish to English?) There is a Spanish version of the book at http://en.flossmanuals.net/como-hacer-una-actividad-sugar/. We need to make any improvements to one manual have a translated version in the other. Some of our authors may prefer to write in Spanish, so we might need translators for both directions.

We'll write the manual using software called Booktype, which is like a Wiki that can make books. All you need is a web browser. The Sugar Browse Activity should be fine. The books will be published for free on the Internet Archive, as webpages on the FLOSS Manuals website, and as attractive printed books and Kindle e-books on Amazon.com sites in the U.S. and Europe. Currently the printed book cover shows a picture of James Simmons and lists him as the sole author. The new edition will list '''all''' contributors and the back may have a sort of collage of the contributor's photos. The mentor may also buy copies of the printed book for the contributors and ship them to wherever they live.

GoogleCodeIn2012/MYOSA

2012-11-13T23:36:15Z

Jdsimmons:

The manual [http://en.flossmanuals.net/make-your-own-sugar-activities/index/ Make Your Own Sugar Activities!] was written by James Simmons a few years ago. It is still the most complete guide to making Sugar Activities, but it is already out of date. Two things have changed since it was first published:

# Sugar now uses GTK3 to create user interfaces. The examples in the book use the older GTK, which is still available, but Activities should start using the new GTK3. The examples need to be updated and re-tested.
# When James wrote the book he hoped it would help students write their own Activities. Whether the book helped or not, the fact is that students '''are''' writing Sugar Activities and even contributing to the Sugar environment itself. It is time for these students to stand up and be counted. Show off what you know, put your bio in the "About The Authors" chapter, and enjoy the benefits of being a published author. Impress friends, family, girls, boys, and future employers.

Of the two reasons to update the book the second one is clearly the most important.

== Possible tasks ==

# Create versions of the code samples in the book that work with GTK 3. These will go in the Git repository alongside the old versions (instead of just replacing them).
# Have you "Sugarized" an application not originally written for Sugar? Write a chapter explaining how you did it!
# Find a PyGame application that uses olpcgames, rework it to use SugarGame, and write up how you did it!
# Have you worked on improvements to Sugar itself? Tell us about it! Did your changes become part of the official Sugar distribution? How did you make that happen? How did you do testing, version control, etc? We want the whole story!
# Do you know how to do something else that isn't in the book but should be? Write a chapter about it!
# Can you do a good translation from English to Spanish (or Spanish to English?) There is a Spanish version of the book at http://en.flossmanuals.net/como-hacer-una-actividad-sugar/. We need to make any improvements to one manual have a translated version in the other. Some of our authors may prefer to write in Spanish, so we might need translators for both directions.

We'll write the manual using software called Booktype, which is like a Wiki that can make books. All you need is a web browser. The Sugar Browse Activity should be fine. The books will be published for free on the Internet Archive, as webpages on the FLOSS Manuals website, and as attractive printed books and Kindle e-books on Amazon.com sites in the U.S. and Europe. Currently the cover shows a picture of James Simmons and lists him as the sole author. The new edition will list all contributors and the back may have a sort of collage of the contributor's photos. The mentor may also buy copies of the printed book for the contributors and ship them to wherever they live.

GoogleCodeIn2012/MYOSA

2012-11-13T23:28:26Z

Jdsimmons: /* Possible tasks */

The manual [http://en.flossmanuals.net/make-your-own-sugar-activities/index/ Make Your Own Sugar Activities!] was written by James Simmons a few years ago. It is still the most complete guide to making Sugar Activities, but it is already out of date. Two things have changed since it was first published:

# Python is now at version 3, and will not run code for version 2. Python 3 uses GTK3 to create user interfaces and that will also break existing code. The examples in the book need to be updated and re-tested.
# When James wrote the book he hoped it would help students write their own Activities. Whether the book helped or not, the fact is that students '''are''' writing Sugar Activities and even contributing to the Sugar environment itself. It is time for these students to stand up and be counted. Show off what you know, put your bio in the "About The Authors" chapter, and enjoy the benefits of being a published author. Impress friends, family, girls, boys, and future employers.

Of the two reasons to update the book the second one is clearly the most important.

== Possible tasks ==

# Create versions of the code samples in the book that work with GTK 3. These will go in the Git repository alongside the old versions (instead of just replacing them).
# Have you "Sugarized" an application not originally written for Sugar? Write a chapter explaining how you did it!
# Find a PyGame application that uses olpcgames, rework it to use SugarGame, and write up how you did it!
# Have you worked on improvements to Sugar itself? Tell us about it! Did your changes become part of the official Sugar distribution? How did you make that happen? How did you do testing, version control, etc? We want the whole story!
# Do you know how to do something else that isn't in the book but should be? Write a chapter about it!
# Can you do a good translation from English to Spanish (or Spanish to English?) There is a Spanish version of the book at http://en.flossmanuals.net/como-hacer-una-actividad-sugar/. We need to make any improvements to one manual have a translated version in the other. Some of our authors may prefer to write in Spanish, so we might need translators for both directions.

We'll write the manual using software called Booktype, which is like a Wiki that can make books. All you need is a web browser. The Sugar Browse Activity should be fine. The books will be published for free on the Internet Archive, as webpages on the FLOSS Manuals website, and as attractive printed books and Kindle e-books on Amazon.com sites in the U.S. and Europe.

GoogleCodeIn2012/MYOSA

2012-11-13T20:22:17Z

Jdsimmons: Created page with "The manual [http://en.flossmanuals.net/make-your-own-sugar-activities/index/ Make Your Own Sugar Activities!] was written by James Simmons a few years ago. It is still the mo..."

The manual [http://en.flossmanuals.net/make-your-own-sugar-activities/index/ Make Your Own Sugar Activities!] was written by James Simmons a few years ago. It is still the most complete guide to making Sugar Activities, but it is already out of date. Two things have changed since it was first published:

# Python is now at version 3, and will not run code for version 2. Python 3 uses GTK3 to create user interfaces and that will also break existing code. The examples in the book need to be updated and re-tested.
# When James wrote the book he hoped it would help students write their own Activities. Whether the book helped or not, the fact is that students '''are''' writing Sugar Activities and even contributing to the Sugar environment itself. It is time for these students to stand up and be counted. Show off what you know, put your bio in the "About The Authors" chapter, and enjoy the benefits of being a published author. Impress friends, family, girls, boys, and future employers.

Of the two reasons to update the book the second one is clearly the most important.

== Possible tasks ==

# Create versions of the code samples in the book that work with Python 3 and GTK 3. These will go in the Git repository alongside the old versions (instead of just replacing them).
# Have you "Sugarized" an application not originally written for Sugar? Write a chapter explaining how you did it!
# Find a PyGame application that uses olpcgames, rework it to use SugarGame, and write up how you did it!
# Have you worked on improvements to Sugar itself? Tell us about it! Did your changes become part of the official Sugar distribution? How did you make that happen? How did you do testing, version control, etc? We want the whole story!
# Do you know how to do something else that isn't in the book but should be? Write a chapter about it!
# Can you do a good translation from English to Spanish (or Spanish to English?) There is a Spanish version of the book at http://en.flossmanuals.net/como-hacer-una-actividad-sugar/. We need to make any improvements to one manual have a translated version in the other. Some of our authors may prefer to write in Spanish, so we might need translators for both directions.

We'll write the manual using software called Booktype, which is like a Wiki that can make books. All you need is a web browser. The Sugar Browse Activity should be fine. The books will be published for free on the Internet Archive, as webpages on the FLOSS Manuals website, and as attractive printed books and Kindle e-books on Amazon.com sites in the U.S. and Europe.

Google Code-In 2012

2012-11-13T19:29:34Z

Jdsimmons: /* Tasks */

Sugar Labs is <strike>applying to</strike> participating in Google Code-in for 2012.

=== Message to potential participants ===

It is important that you obtain permission of your parents.

Es importante que obtengas el permiso de tus padres para participar.

http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/help_page#eligibility

Please see the Contest Rules for Eligibility and Registration process.

http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/terms_and_conditions

=== Why we are applying ===

Sugar is written and maintained by volunteers, who range from seasoned professionals to children as young as 12-years of age. Children who have grown up with Sugar have transitioned from Sugar users to Sugar App developers to Sugar maintainers. They hang out on IRC with the global Sugar developer community and are full-fledged members of the Sugar development team. It is this latter group of children we hope will participate in and benefit from Google Code-in. Specifically we want to re-enforce the message that Sugar belongs to its users and that they have both ownership and the responsibility that ownership implies. Just as learning is not something done to you, but something you do, learning with Sugar ultimately means participating in the Sugar development process. At Sugar Labs, we are trying to bring the culture of Free Software into the culture of school. So the Code-in is not just an opportunity for us to get some tasks accomplished, it is quintessential to our overall mission.

=== About GCI ===

[http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/help_page Code-in FAQ]

=== Tasks ===
This [[GoogleCodeIn2012/GCI2012_Brainstorming|brainstorming]] page lists some general categories from which specific individual tasks can be specified. (Note: We had [[Summer_of_Code/2012#Project_candidates|a number of tasks]] listed in our GSOC application that may be relevant to GCI. We also have many [[Features]] that are still pending.)

;Code: Tasks related to writing or refactoring code
# Write a new pootle-helper script for doing preventative [[GoogleCodeIn2012/MsgfmtChecker|msgfmt checks]].
# Sugarize [[GoogleCodeIn2012/Virtaal|Virtaal]] for L10n "bootstrapping".
# Convert Sugar activities from [[Features/GTK3/Porting|GTK-2 to GTK-3]] framework.
# [[Features/Touch/Development|Enable touch]] for activities that use direct keyboard input.
# Implement the [[Features/Background_image_on_home_view|set background image on Home View Feature]].
# Package Sugar activity utilities (e.g., [http://git.sugarlabs.org/portfolio/portfolio/blobs/master/toolbar_utils.py]) for inclusion in the [http://git.sugarlabs.org/sugar-toolkit-gtk3 Sugar toolkit].

;Documentation/Training: Tasks related to creating/editing documents and helping others learn more
# Write a [[GoogleCodeIn2012/Turtle Art|Turtle Art]] introductory tutorial.
# Identify and document a generalized (ideally automated) method for taking nearly identical screen shots with the desktop set to a selected list of different languages. (Possibly Orca?).
# Flesh out the [[Features/GTK3/Porting|GTK-2 to GTK-3]] conversion documentation to include more comprehensive coverage of Pango.
# Better document the process of creating and using [[Sugar_on_a_Stick|Sugar on a Stick]], the LiveUSB version of Sugar.
# Better document the process of running Sugar in a [[Sugar_Creation_Kit/VirtualBox|virtual machine (VM)]].
# Create videos on how to use Sugar and how to use core Sugar activities.
# Update and add new content to the manual [http://en.flossmanuals.net/make-your-own-sugar-activities/index/ Make Your Own Sugar Activities]! (details [[GoogleCodeIn2012/MYOSA|here]]).

;Outreach/Research: Tasks related to community management, outreach/marketing, or studying problems and recommending solutions
# Research internationalization of [[GoogleCodeIn2012/SVG images| SVG images]].
# Research what [[Platform_Team/sugar-stats|metadata about Sugar activity usage]] would be helpful to teachers for assessment purposes.
# Research what opportunities/roadblocks exist for running Sugar in your local schools.
# Research what is missing from Sugar that makes it unused by your local schools.
# Research the issues involved with porting Sugar to "the Cloud".
# Research the issues involved with porting Sugar to Android.

;Quality Assurance: Tasks related to testing and ensuring code is of high quality.
# Do an analysis of which Sugar activities are are orphaned.
# Do an analysis of which Sugar activities are touch-enabled or need modifications to support touch.
# Do an analysis of which Sugar activities are lacking in documentation (e.g., [[Activities|Activity wiki page]]).
# Do an analysis of which Sugar activities are have issues running on non-x86 architectures (e.g. ARM).
# Do an analysis of which Sugar activities are lacking i18n support.

;User Interface: Tasks related to user experience research or user interface design and interaction
# Analyze Sugar from the point of view of special needs and make recommendations for improvements.
# Help us design the Sugar affordances for Sugar on tablet computers (Sugar Touch).
# Develop new Maliit keyboard files for additional languages(beyond those already developed by garycmartin).
# Think of ways to further leverage the use of an accelerometer in Sugar (and other common sensors found in portable computing devices).
# Assessing how Sugar is used by students. What is learnt? Survey students and teachers. How well does it deliver its goals?
# Survey Sugar users to find out what UI features they want from Sugar in the future.

=== Mentors ===
Depending on the project, we will assign multiple mentors from our various development and support teams.
* Chris Leonard
* Walter Bender
* Claudia Urrea
* Pacita Pena
* Rosamel Ramirez
* Sdenka Salas
* Sam Greenfeld
* Gonzalo Odiard
* Simon Schampijer
* Manuel Quiñones
* Tony Forster
* Guzman Trinidad
* Adam Holt
* Sean Daly
* Manuel Kaufmann
* Mark Bradley
* Alan Aguiar
* Bernie Innocenti
* Daniel Drake
* Martin Abente
* Raul Guttierrez Segales
* C Scott Ananian
et al.

[[Category: GCI2012]]

Google Code-In 2012

2012-11-13T19:28:24Z

Jdsimmons: /* Tasks */

Sugar Labs is <strike>applying to</strike> participating in Google Code-in for 2012.

=== Message to potential participants ===

It is important that you obtain permission of your parents.

Es importante que obtengas el permiso de tus padres para participar.

http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/help_page#eligibility

Please see the Contest Rules for Eligibility and Registration process.

http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/terms_and_conditions

=== Why we are applying ===

Sugar is written and maintained by volunteers, who range from seasoned professionals to children as young as 12-years of age. Children who have grown up with Sugar have transitioned from Sugar users to Sugar App developers to Sugar maintainers. They hang out on IRC with the global Sugar developer community and are full-fledged members of the Sugar development team. It is this latter group of children we hope will participate in and benefit from Google Code-in. Specifically we want to re-enforce the message that Sugar belongs to its users and that they have both ownership and the responsibility that ownership implies. Just as learning is not something done to you, but something you do, learning with Sugar ultimately means participating in the Sugar development process. At Sugar Labs, we are trying to bring the culture of Free Software into the culture of school. So the Code-in is not just an opportunity for us to get some tasks accomplished, it is quintessential to our overall mission.

=== About GCI ===

[http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/help_page Code-in FAQ]

=== Tasks ===
This [[GoogleCodeIn2012/GCI2012_Brainstorming|brainstorming]] page lists some general categories from which specific individual tasks can be specified. (Note: We had [[Summer_of_Code/2012#Project_candidates|a number of tasks]] listed in our GSOC application that may be relevant to GCI. We also have many [[Features]] that are still pending.)

;Code: Tasks related to writing or refactoring code
# Write a new pootle-helper script for doing preventative [[GoogleCodeIn2012/MsgfmtChecker|msgfmt checks]].
# Sugarize [[GoogleCodeIn2012/Virtaal|Virtaal]] for L10n "bootstrapping".
# Convert Sugar activities from [[Features/GTK3/Porting|GTK-2 to GTK-3]] framework.
# [[Features/Touch/Development|Enable touch]] for activities that use direct keyboard input.
# Implement the [[Features/Background_image_on_home_view|set background image on Home View Feature]].
# Package Sugar activity utilities (e.g., [http://git.sugarlabs.org/portfolio/portfolio/blobs/master/toolbar_utils.py]) for inclusion in the [http://git.sugarlabs.org/sugar-toolkit-gtk3 Sugar toolkit].

;Documentation/Training: Tasks related to creating/editing documents and helping others learn more
# Write a [[GoogleCodeIn2012/Turtle Art|Turtle Art]] introductory tutorial.
# Identify and document a generalized (ideally automated) method for taking nearly identical screen shots with the desktop set to a selected list of different languages. (Possibly Orca?).
# Flesh out the [[Features/GTK3/Porting|GTK-2 to GTK-3]] conversion documentation to include more comprehensive coverage of Pango.
# Better document the process of creating and using [[Sugar_on_a_Stick|Sugar on a Stick]], the LiveUSB version of Sugar.
# Better document the process of running Sugar in a [[Sugar_Creation_Kit/VirtualBox|virtual machine (VM)]].
# Create videos on how to use Sugar and how to use core Sugar activities.
# Update and add new content to the manual [http://en.flossmanuals.net/make-your-own-sugar-activities/index/ Make Your Own Sugar Activities]! (details here).

;Outreach/Research: Tasks related to community management, outreach/marketing, or studying problems and recommending solutions
# Research internationalization of [[GoogleCodeIn2012/SVG images| SVG images]].
# Research what [[Platform_Team/sugar-stats|metadata about Sugar activity usage]] would be helpful to teachers for assessment purposes.
# Research what opportunities/roadblocks exist for running Sugar in your local schools.
# Research what is missing from Sugar that makes it unused by your local schools.
# Research the issues involved with porting Sugar to "the Cloud".
# Research the issues involved with porting Sugar to Android.

;Quality Assurance: Tasks related to testing and ensuring code is of high quality.
# Do an analysis of which Sugar activities are are orphaned.
# Do an analysis of which Sugar activities are touch-enabled or need modifications to support touch.
# Do an analysis of which Sugar activities are lacking in documentation (e.g., [[Activities|Activity wiki page]]).
# Do an analysis of which Sugar activities are have issues running on non-x86 architectures (e.g. ARM).
# Do an analysis of which Sugar activities are lacking i18n support.

;User Interface: Tasks related to user experience research or user interface design and interaction
# Analyze Sugar from the point of view of special needs and make recommendations for improvements.
# Help us design the Sugar affordances for Sugar on tablet computers (Sugar Touch).
# Develop new Maliit keyboard files for additional languages(beyond those already developed by garycmartin).
# Think of ways to further leverage the use of an accelerometer in Sugar (and other common sensors found in portable computing devices).
# Assessing how Sugar is used by students. What is learnt? Survey students and teachers. How well does it deliver its goals?
# Survey Sugar users to find out what UI features they want from Sugar in the future.

=== Mentors ===
Depending on the project, we will assign multiple mentors from our various development and support teams.
* Chris Leonard
* Walter Bender
* Claudia Urrea
* Pacita Pena
* Rosamel Ramirez
* Sdenka Salas
* Sam Greenfeld
* Gonzalo Odiard
* Simon Schampijer
* Manuel Quiñones
* Tony Forster
* Guzman Trinidad
* Adam Holt
* Sean Daly
* Manuel Kaufmann
* Mark Bradley
* Alan Aguiar
* Bernie Innocenti
* Daniel Drake
* Martin Abente
* Raul Guttierrez Segales
* C Scott Ananian
et al.

[[Category: GCI2012]]

Google Code-In 2012

2012-11-13T19:27:15Z

Jdsimmons: /* Tasks */

Sugar Labs is <strike>applying to</strike> participating in Google Code-in for 2012.

=== Message to potential participants ===

It is important that you obtain permission of your parents.

Es importante que obtengas el permiso de tus padres para participar.

http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/help_page#eligibility

Please see the Contest Rules for Eligibility and Registration process.

http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/terms_and_conditions

=== Why we are applying ===

Sugar is written and maintained by volunteers, who range from seasoned professionals to children as young as 12-years of age. Children who have grown up with Sugar have transitioned from Sugar users to Sugar App developers to Sugar maintainers. They hang out on IRC with the global Sugar developer community and are full-fledged members of the Sugar development team. It is this latter group of children we hope will participate in and benefit from Google Code-in. Specifically we want to re-enforce the message that Sugar belongs to its users and that they have both ownership and the responsibility that ownership implies. Just as learning is not something done to you, but something you do, learning with Sugar ultimately means participating in the Sugar development process. At Sugar Labs, we are trying to bring the culture of Free Software into the culture of school. So the Code-in is not just an opportunity for us to get some tasks accomplished, it is quintessential to our overall mission.

=== About GCI ===

[http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/help_page Code-in FAQ]

=== Tasks ===
This [[GoogleCodeIn2012/GCI2012_Brainstorming|brainstorming]] page lists some general categories from which specific individual tasks can be specified. (Note: We had [[Summer_of_Code/2012#Project_candidates|a number of tasks]] listed in our GSOC application that may be relevant to GCI. We also have many [[Features]] that are still pending.)

;Code: Tasks related to writing or refactoring code
# Write a new pootle-helper script for doing preventative [[GoogleCodeIn2012/MsgfmtChecker|msgfmt checks]].
# Sugarize [[GoogleCodeIn2012/Virtaal|Virtaal]] for L10n "bootstrapping".
# Convert Sugar activities from [[Features/GTK3/Porting|GTK-2 to GTK-3]] framework.
# [[Features/Touch/Development|Enable touch]] for activities that use direct keyboard input.
# Implement the [[Features/Background_image_on_home_view|set background image on Home View Feature]].
# Package Sugar activity utilities (e.g., [http://git.sugarlabs.org/portfolio/portfolio/blobs/master/toolbar_utils.py]) for inclusion in the [http://git.sugarlabs.org/sugar-toolkit-gtk3 Sugar toolkit].

;Documentation/Training: Tasks related to creating/editing documents and helping others learn more
# Write a [[GoogleCodeIn2012/Turtle Art|Turtle Art]] introductory tutorial.
# Identify and document a generalized (ideally automated) method for taking nearly identical screen shots with the desktop set to a selected list of different languages. (Possibly Orca?).
# Flesh out the [[Features/GTK3/Porting|GTK-2 to GTK-3]] conversion documentation to include more comprehensive coverage of Pango.
# Better document the process of creating and using [[Sugar_on_a_Stick|Sugar on a Stick]], the LiveUSB version of Sugar.
# Better document the process of running Sugar in a [[Sugar_Creation_Kit/VirtualBox|virtual machine (VM)]].
# Create videos on how to use Sugar and how to use core Sugar activities.
# Update and add new content to the manual [http://en.flossmanuals.net/make-your-own-sugar-activities/index/|Make Your Own Sugar Activities]! (details here).

;Outreach/Research: Tasks related to community management, outreach/marketing, or studying problems and recommending solutions
# Research internationalization of [[GoogleCodeIn2012/SVG images| SVG images]].
# Research what [[Platform_Team/sugar-stats|metadata about Sugar activity usage]] would be helpful to teachers for assessment purposes.
# Research what opportunities/roadblocks exist for running Sugar in your local schools.
# Research what is missing from Sugar that makes it unused by your local schools.
# Research the issues involved with porting Sugar to "the Cloud".
# Research the issues involved with porting Sugar to Android.

;Quality Assurance: Tasks related to testing and ensuring code is of high quality.
# Do an analysis of which Sugar activities are are orphaned.
# Do an analysis of which Sugar activities are touch-enabled or need modifications to support touch.
# Do an analysis of which Sugar activities are lacking in documentation (e.g., [[Activities|Activity wiki page]]).
# Do an analysis of which Sugar activities are have issues running on non-x86 architectures (e.g. ARM).
# Do an analysis of which Sugar activities are lacking i18n support.

;User Interface: Tasks related to user experience research or user interface design and interaction
# Analyze Sugar from the point of view of special needs and make recommendations for improvements.
# Help us design the Sugar affordances for Sugar on tablet computers (Sugar Touch).
# Develop new Maliit keyboard files for additional languages(beyond those already developed by garycmartin).
# Think of ways to further leverage the use of an accelerometer in Sugar (and other common sensors found in portable computing devices).
# Assessing how Sugar is used by students. What is learnt? Survey students and teachers. How well does it deliver its goals?
# Survey Sugar users to find out what UI features they want from Sugar in the future.

=== Mentors ===
Depending on the project, we will assign multiple mentors from our various development and support teams.
* Chris Leonard
* Walter Bender
* Claudia Urrea
* Pacita Pena
* Rosamel Ramirez
* Sdenka Salas
* Sam Greenfeld
* Gonzalo Odiard
* Simon Schampijer
* Manuel Quiñones
* Tony Forster
* Guzman Trinidad
* Adam Holt
* Sean Daly
* Manuel Kaufmann
* Mark Bradley
* Alan Aguiar
* Bernie Innocenti
* Daniel Drake
* Martin Abente
* Raul Guttierrez Segales
* C Scott Ananian
et al.

[[Category: GCI2012]]

Features/Show Thumb Drives As Hierarchical

2011-11-21T20:43:23Z

Jdsimmons: /* User Experience */

<noinclude>
[[Category:Feature Page Incomplete]]
[[Category:Feature|<Feature Name>]]

</noinclude>

== Summary ==
There is a desire from many users to replace the part of the Journal UI that represents files on thumb drives and SD cards as if they were Journal entries, instead of what they actually are, which is files within directories. I suggest that only Journal entries should be represented as such, and that thumb drives and SD cards should be represented conventionally.

== Owner ==
''This should link to your home wiki page so we know who you are''
* Name: [[User:Jdsimmons| James Simmons]]

* Email: <nicestep@gmail.com>

== Current status ==
* Targeted release: (SUGAR_VERSION)
* Last updated: (DATE)
* Percentage of completion: XX%

== Detailed Description ==
There is a desire from many users to replace the part of the Journal UI that represents files on thumb drives and SD cards as if they were Journal entries, instead of what they actually are, which is files within directories. Representing these files as if they are Journal entries creates an expectation in the user that they will behave as Journal entries do, and in fact they do not. It also makes it difficult, perhaps impossible, to deal with directories on the thumb drive or SD card.

== Benefit to Sugar ==
Plan Ceibal has created an Activity "Leer Pendrive" which simply displays the contents of removable devices as a GTK file chooser and lets people copy selected files to the clipboard, from where they can be pasted into the Journal. I understand there was a big demand for this. I followed this up with my own Activity, Sugar Commander, which lets you copy files directly to the Journal without using the clipboard. I understand that this Activity has a following and is routinely included on XOs in Australia. Neither of these Activities allow you to copy from the Journal to a thumb drive, and there is a legitimate need to do this.

The beneficiaries of this feature will be teachers, older students, and others who need to deal with thumb drives and SD cards and move data in and out of the Journal.

== Scope ==
See the code for the Sugar Commander Activity for a simple implementation of this idea.

==UI Design==
Have a look at the Sugar Commander Activity:

http://activities.sugarlabs.org/en-US/sugar/addon/4291

== How To Test ==
{{:{{PAGENAME}}/Testing}}
== User Experience ==
If this is done well, when the user switches from viewing the Journal to viewing the contents of a removable drive he will see a conventional representation of files and directories like a GTK file chooser and will be able to copy files from this into the Journal and copy Journal entries into the file system. He'll also be able to create directories on the thumb drive, rename things, etc.

If the feature is implemented well then children who never use thumb drives, etc. won't know the new feature is there.

== Dependencies ==
''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, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?''

== Contingency Plan ==
''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 your feature is not completed in time, we want to assure others that other parts of Sugar will not be in jeopardy.''

== Documentation ==
''Is there upstream documentation on this feature, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.''

== Release Notes ==
''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.''

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

Features/Show Thumb Drives As Hierarchical

2011-11-21T20:37:26Z

Jdsimmons: /* Benefit to Sugar */

<noinclude>
[[Category:Feature Page Incomplete]]
[[Category:Feature|<Feature Name>]]

</noinclude>

== Summary ==
There is a desire from many users to replace the part of the Journal UI that represents files on thumb drives and SD cards as if they were Journal entries, instead of what they actually are, which is files within directories. I suggest that only Journal entries should be represented as such, and that thumb drives and SD cards should be represented conventionally.

== Owner ==
''This should link to your home wiki page so we know who you are''
* Name: [[User:Jdsimmons| James Simmons]]

* Email: <nicestep@gmail.com>

== Current status ==
* Targeted release: (SUGAR_VERSION)
* Last updated: (DATE)
* Percentage of completion: XX%

== Detailed Description ==
There is a desire from many users to replace the part of the Journal UI that represents files on thumb drives and SD cards as if they were Journal entries, instead of what they actually are, which is files within directories. Representing these files as if they are Journal entries creates an expectation in the user that they will behave as Journal entries do, and in fact they do not. It also makes it difficult, perhaps impossible, to deal with directories on the thumb drive or SD card.

== Benefit to Sugar ==
Plan Ceibal has created an Activity "Leer Pendrive" which simply displays the contents of removable devices as a GTK file chooser and lets people copy selected files to the clipboard, from where they can be pasted into the Journal. I understand there was a big demand for this. I followed this up with my own Activity, Sugar Commander, which lets you copy files directly to the Journal without using the clipboard. I understand that this Activity has a following and is routinely included on XOs in Australia. Neither of these Activities allow you to copy from the Journal to a thumb drive, and there is a legitimate need to do this.

The beneficiaries of this feature will be teachers, older students, and others who need to deal with thumb drives and SD cards and move data in and out of the Journal.

== Scope ==
See the code for the Sugar Commander Activity for a simple implementation of this idea.

==UI Design==
Have a look at the Sugar Commander Activity:

http://activities.sugarlabs.org/en-US/sugar/addon/4291

== How To Test ==
{{:{{PAGENAME}}/Testing}}
== User Experience ==
If this is done well, when the user switches from viewing the Journal to viewing the contents of a removable drive he will see a conventional representation of files and directories like a GTK file chooser and will be able to copy files from this into the Journal and copy Journal entries into the file system. He'll also be able to create directories on the thumb drive, rename things, etc.

== Dependencies ==
''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, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?''

== Contingency Plan ==
''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 your feature is not completed in time, we want to assure others that other parts of Sugar will not be in jeopardy.''

== Documentation ==
''Is there upstream documentation on this feature, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.''

== Release Notes ==
''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.''

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

Features/Show Thumb Drives As Hierarchical

2011-11-21T20:34:12Z

Jdsimmons: /* User Experience */

<noinclude>
[[Category:Feature Page Incomplete]]
[[Category:Feature|<Feature Name>]]

</noinclude>

== Summary ==
There is a desire from many users to replace the part of the Journal UI that represents files on thumb drives and SD cards as if they were Journal entries, instead of what they actually are, which is files within directories. I suggest that only Journal entries should be represented as such, and that thumb drives and SD cards should be represented conventionally.

== Owner ==
''This should link to your home wiki page so we know who you are''
* Name: [[User:Jdsimmons| James Simmons]]

* Email: <nicestep@gmail.com>

== Current status ==
* Targeted release: (SUGAR_VERSION)
* Last updated: (DATE)
* Percentage of completion: XX%

== Detailed Description ==
There is a desire from many users to replace the part of the Journal UI that represents files on thumb drives and SD cards as if they were Journal entries, instead of what they actually are, which is files within directories. Representing these files as if they are Journal entries creates an expectation in the user that they will behave as Journal entries do, and in fact they do not. It also makes it difficult, perhaps impossible, to deal with directories on the thumb drive or SD card.

== Benefit to Sugar ==
Plan Ceibal has created an Activity "Leer Pendrive" which simply displays the contents of removable devices as a GTK file chooser and lets people copy selected files to the clipboard, from where they can be pasted into the Journal. I understand there was a big demand for this. I followed this up with my own Activity, Sugar Commander, which lets you copy files directly to the Journal without using the clipboard. I understand that this Activity has a following and is routinely included on XOs in Australia. Neither of these Activities allow you to copy from the Journal to a thumb drive, and there is a legitimate need to do this.

== Scope ==
See the code for the Sugar Commander Activity for a simple implementation of this idea.

==UI Design==
Have a look at the Sugar Commander Activity:

http://activities.sugarlabs.org/en-US/sugar/addon/4291

== How To Test ==
{{:{{PAGENAME}}/Testing}}
== User Experience ==
If this is done well, when the user switches from viewing the Journal to viewing the contents of a removable drive he will see a conventional representation of files and directories like a GTK file chooser and will be able to copy files from this into the Journal and copy Journal entries into the file system. He'll also be able to create directories on the thumb drive, rename things, etc.

== Dependencies ==
''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, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?''

== Contingency Plan ==
''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 your feature is not completed in time, we want to assure others that other parts of Sugar will not be in jeopardy.''

== Documentation ==
''Is there upstream documentation on this feature, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.''

== Release Notes ==
''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.''

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

Features/Show Thumb Drives As Hierarchical

2011-11-21T20:31:08Z

Jdsimmons: /* UI Design */

<noinclude>
[[Category:Feature Page Incomplete]]
[[Category:Feature|<Feature Name>]]

</noinclude>

== Summary ==
There is a desire from many users to replace the part of the Journal UI that represents files on thumb drives and SD cards as if they were Journal entries, instead of what they actually are, which is files within directories. I suggest that only Journal entries should be represented as such, and that thumb drives and SD cards should be represented conventionally.

== Owner ==
''This should link to your home wiki page so we know who you are''
* Name: [[User:Jdsimmons| James Simmons]]

* Email: <nicestep@gmail.com>

== Current status ==
* Targeted release: (SUGAR_VERSION)
* Last updated: (DATE)
* Percentage of completion: XX%

== Detailed Description ==
There is a desire from many users to replace the part of the Journal UI that represents files on thumb drives and SD cards as if they were Journal entries, instead of what they actually are, which is files within directories. Representing these files as if they are Journal entries creates an expectation in the user that they will behave as Journal entries do, and in fact they do not. It also makes it difficult, perhaps impossible, to deal with directories on the thumb drive or SD card.

== Benefit to Sugar ==
Plan Ceibal has created an Activity "Leer Pendrive" which simply displays the contents of removable devices as a GTK file chooser and lets people copy selected files to the clipboard, from where they can be pasted into the Journal. I understand there was a big demand for this. I followed this up with my own Activity, Sugar Commander, which lets you copy files directly to the Journal without using the clipboard. I understand that this Activity has a following and is routinely included on XOs in Australia. Neither of these Activities allow you to copy from the Journal to a thumb drive, and there is a legitimate need to do this.

== Scope ==
See the code for the Sugar Commander Activity for a simple implementation of this idea.

==UI Design==
Have a look at the Sugar Commander Activity:

http://activities.sugarlabs.org/en-US/sugar/addon/4291

== How To Test ==
{{:{{PAGENAME}}/Testing}}
== User Experience ==
''If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.''

== Dependencies ==
''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, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?''

== Contingency Plan ==
''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 your feature is not completed in time, we want to assure others that other parts of Sugar will not be in jeopardy.''

== Documentation ==
''Is there upstream documentation on this feature, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.''

== Release Notes ==
''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.''

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

Features/Show Thumb Drives As Hierarchical

2011-11-21T20:28:32Z

Jdsimmons: /* Scope */

<noinclude>
[[Category:Feature Page Incomplete]]
[[Category:Feature|<Feature Name>]]

</noinclude>

== Summary ==
There is a desire from many users to replace the part of the Journal UI that represents files on thumb drives and SD cards as if they were Journal entries, instead of what they actually are, which is files within directories. I suggest that only Journal entries should be represented as such, and that thumb drives and SD cards should be represented conventionally.

== Owner ==
''This should link to your home wiki page so we know who you are''
* Name: [[User:Jdsimmons| James Simmons]]

* Email: <nicestep@gmail.com>

== Current status ==
* Targeted release: (SUGAR_VERSION)
* Last updated: (DATE)
* Percentage of completion: XX%

== Detailed Description ==
There is a desire from many users to replace the part of the Journal UI that represents files on thumb drives and SD cards as if they were Journal entries, instead of what they actually are, which is files within directories. Representing these files as if they are Journal entries creates an expectation in the user that they will behave as Journal entries do, and in fact they do not. It also makes it difficult, perhaps impossible, to deal with directories on the thumb drive or SD card.

== Benefit to Sugar ==
Plan Ceibal has created an Activity "Leer Pendrive" which simply displays the contents of removable devices as a GTK file chooser and lets people copy selected files to the clipboard, from where they can be pasted into the Journal. I understand there was a big demand for this. I followed this up with my own Activity, Sugar Commander, which lets you copy files directly to the Journal without using the clipboard. I understand that this Activity has a following and is routinely included on XOs in Australia. Neither of these Activities allow you to copy from the Journal to a thumb drive, and there is a legitimate need to do this.

== Scope ==
See the code for the Sugar Commander Activity for a simple implementation of this idea.

==UI Design==
''Does the feature have a direct impact on the work flow, or does it need a UI? Link here mockups, or add detailed descriptions.''

== How To Test ==
{{:{{PAGENAME}}/Testing}}
== User Experience ==
''If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.''

== Dependencies ==
''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, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?''

== Contingency Plan ==
''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 your feature is not completed in time, we want to assure others that other parts of Sugar will not be in jeopardy.''

== Documentation ==
''Is there upstream documentation on this feature, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.''

== Release Notes ==
''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.''

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

Features/Show Thumb Drives As Hierarchical

2011-11-21T20:26:13Z

Jdsimmons: /* Benefit to Sugar */

<noinclude>
[[Category:Feature Page Incomplete]]
[[Category:Feature|<Feature Name>]]

</noinclude>

== Summary ==
There is a desire from many users to replace the part of the Journal UI that represents files on thumb drives and SD cards as if they were Journal entries, instead of what they actually are, which is files within directories. I suggest that only Journal entries should be represented as such, and that thumb drives and SD cards should be represented conventionally.

== Owner ==
''This should link to your home wiki page so we know who you are''
* Name: [[User:Jdsimmons| James Simmons]]

* Email: <nicestep@gmail.com>

== Current status ==
* Targeted release: (SUGAR_VERSION)
* Last updated: (DATE)
* Percentage of completion: XX%

== Detailed Description ==
There is a desire from many users to replace the part of the Journal UI that represents files on thumb drives and SD cards as if they were Journal entries, instead of what they actually are, which is files within directories. Representing these files as if they are Journal entries creates an expectation in the user that they will behave as Journal entries do, and in fact they do not. It also makes it difficult, perhaps impossible, to deal with directories on the thumb drive or SD card.

== Benefit to Sugar ==
Plan Ceibal has created an Activity "Leer Pendrive" which simply displays the contents of removable devices as a GTK file chooser and lets people copy selected files to the clipboard, from where they can be pasted into the Journal. I understand there was a big demand for this. I followed this up with my own Activity, Sugar Commander, which lets you copy files directly to the Journal without using the clipboard. I understand that this Activity has a following and is routinely included on XOs in Australia. Neither of these Activities allow you to copy from the Journal to a thumb drive, and there is a legitimate need to do this.

== Scope ==
''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?''

==UI Design==
''Does the feature have a direct impact on the work flow, or does it need a UI? Link here mockups, or add detailed descriptions.''

== How To Test ==
{{:{{PAGENAME}}/Testing}}
== User Experience ==
''If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.''

== Dependencies ==
''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, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?''

== Contingency Plan ==
''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 your feature is not completed in time, we want to assure others that other parts of Sugar will not be in jeopardy.''

== Documentation ==
''Is there upstream documentation on this feature, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.''

== Release Notes ==
''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.''

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

Features/Show Thumb Drives As Hierarchical

2011-11-21T20:17:59Z

Jdsimmons:

<noinclude>
[[Category:Feature Page Incomplete]]
[[Category:Feature|<Feature Name>]]

</noinclude>

== Summary ==
There is a desire from many users to replace the part of the Journal UI that represents files on thumb drives and SD cards as if they were Journal entries, instead of what they actually are, which is files within directories. I suggest that only Journal entries should be represented as such, and that thumb drives and SD cards should be represented conventionally.

== Owner ==
''This should link to your home wiki page so we know who you are''
* Name: [[User:Jdsimmons| James Simmons]]

* Email: <nicestep@gmail.com>

== Current status ==
* Targeted release: (SUGAR_VERSION)
* Last updated: (DATE)
* Percentage of completion: XX%

== Detailed Description ==
There is a desire from many users to replace the part of the Journal UI that represents files on thumb drives and SD cards as if they were Journal entries, instead of what they actually are, which is files within directories. Representing these files as if they are Journal entries creates an expectation in the user that they will behave as Journal entries do, and in fact they do not. It also makes it difficult, perhaps impossible, to deal with directories on the thumb drive or SD card.

== Benefit to Sugar ==
''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?''

''Make sure to note here as well if this feature has been requested by a specific deployment, or if it has emerged from a bug report.''

== Scope ==
''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?''

==UI Design==
''Does the feature have a direct impact on the work flow, or does it need a UI? Link here mockups, or add detailed descriptions.''

== How To Test ==
{{:{{PAGENAME}}/Testing}}
== User Experience ==
''If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.''

== Dependencies ==
''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, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?''

== Contingency Plan ==
''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 your feature is not completed in time, we want to assure others that other parts of Sugar will not be in jeopardy.''

== Documentation ==
''Is there upstream documentation on this feature, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.''

== Release Notes ==
''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.''

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

Features/Show Thumb Drives As Hierarchical

2011-11-21T20:10:07Z

Jdsimmons: Created page with "<noinclude> Category:Feature Page Incomplete <Feature Name> <!-- You can add categories to tie features back to real deployments/schools requesting them,..."

<noinclude>
[[Category:Feature Page Incomplete]]
[[Category:Feature|<Feature Name>]]

</noinclude>

'''Comments and Explanations:'''

There are comments (in italic) providing guidance to fill out each section, see also the [[Features/Policy|Feature Policy Page]] for a more detailed explanation of the new-feature process. '''Copy the source to a ''new page'' named Features/''Your Feature Name'' before making changes! DO NOT EDIT THIS TEMPLATE.'''





== Summary ==
''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.''

== Owner ==
''This should link to your home wiki page so we know who you are''
* Name: [[User:AcountName| Your Name]]

''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''
* Email: <your email address so we can contact you, invite you to meetings, etc.>

== Current status ==
* Targeted release: (SUGAR_VERSION)
* Last updated: (DATE)
* Percentage of completion: XX%

== Detailed Description ==
''Expand on the summary, if appropriate. A couple of sentences suffices to explain the goal, but the more details you can provide the better.''

== Benefit to Sugar ==
''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?''

''Make sure to note here as well if this feature has been requested by a specific deployment, or if it has emerged from a bug report.''

== Scope ==
''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?''

==UI Design==
''Does the feature have a direct impact on the work flow, or does it need a UI? Link here mockups, or add detailed descriptions.''

== How To Test ==
{{:{{PAGENAME}}/Testing}}
== User Experience ==
''If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.''

== Dependencies ==
''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, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?''

== Contingency Plan ==
''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 your feature is not completed in time, we want to assure others that other parts of Sugar will not be in jeopardy.''

== Documentation ==
''Is there upstream documentation on this feature, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.''

== Release Notes ==
''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.''

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

Activity Team/Resources

2011-01-17T17:52:00Z

Jdsimmons: /* Activity development tutorials */

<noinclude>{{GoogleTrans-en}}{{TeamHeader|Activity Team}}</noinclude>{{TOCright}}

==Getting started in Activity development==
If you have no experience developing Sugar activities, these resources will help get you started.

=== Activity development tutorials ===
{|
|-
|[[File:Sugarlabs_mainpage_07.png|link=http://en.flossmanuals.net/ActivitiesGuideSugar]]
|valign="center"|The official introduction to writing Sugar activities is the Flossmanuals book [http://en.flossmanuals.net/ActivitiesGuideSugar/Introduction Make Your Own Sugar Activities!] by James Simmons.
|}

====Setting up a Sugar environment====

Please see [[Downloads | Get Sugar]] for details on how to best get Sugar running.

If you decide to use a Virtual Machine (VM) or a secondary machine (such as an OLPC XO) for testing your activities, an editor with support for editing files over an SFTP connection can come in handy. [http://www.activestate.com/komodo-edit/downloads Komodo Edit] with the Remote Drive Tree extension and [http://www.eclipse.org Eclipse] with the [http://www.jcraft.com/eclipse-sftp/ SFTP Plugin] are examples.

====Python Reference & Tutorials====
* http://docs.python.org/
* http://diveintopython.org/
* [http://pleac.sourceforge.net/pleac_python/index.html PLEAC - Programming Language Examples Alike Cookbook]
* http://code.google.com/edu/languages/google-python-class/

Python is the language Sugar is written in and is also used by most activities. If you don't already know Python well, you should familiarize yourself with it before continuing.

====PyGTK Reference & Tutorials====
* http://www.pygtk.org/docs/pygtk/index.html
* http://www.pygtk.org/docs/pygobject/index.html

PyGTK is the user interface toolkit used by Sugar activities. Bookmark these two links as you will reference them frequently during development.

* http://www.pygtk.org/pygtk2tutorial/index.html

The following sections of the PyGTK tutorial are most relevant to activity development.

: 1. Introduction
: 2. Getting Started
: 3. Moving On
: 4. Packing Widgets
: 5. Widget Overview
: 6. The Button Widget
: 7. Adjustments
: 8. Range Widgets
: 9. Miscellaneous Widgets
: 10. Container Widgets
: 12. Drawing Area

Also see:

* http://www.majorsilence.com/PyGTK_Book

====Sugar Activities====
* [[Development Team/Almanac|Sugar Almanac]]

The Sugar Almanac contains all the information you need to start writing Sugar activities, ranging from directory structure to bundle format to API reference. It also contains answers to common questions and examples of common tasks.

* http://api.sugarlabs.org/

This automatically updated site contains the official API documentation for Sugar. Though it is currently quite sparse, the source code is included with the documentation and it's useful to have that at your fingertips.

* [[Development Team/Low-level Activity API|Low-Level Activity API]]

Activities can be written in any programming language, as long as it can connect to D-Bus and provide an X11 interface. This documents Sugar's low-level API, in particular for use by activities written in languages other than Python.

====Cairo Graphics====
* http://www.tortall.net/mu/wiki/CairoTutorial

Cairo is the graphics library used in Sugar. The tutorial is a good introduction to the API as well as vector graphics programming in general.

====Pygame====
* http://www.pygame.org/
* [[Development_Team/sugargame]]

Pygame is a library for developing 2D sprite-based games using Python. Sugargame is a package which makes it possible to embed Pygame into a Sugar activity.

====Sugar [[Human Interface Guidelines]] (HIG)====
* [[Human Interface Guidelines]].

Required reading before planning the user interface for your activity. These pages give a good introduction to the thought process behind the Sugar environment and will help a lot when designing your activity.

====i18n (Localisation) Best Practices====
* [[Translation_Team/i18n_Best_Practices]].

Once you have strings in your Activity, here are some general tips which will make your translators happy :-)

====JSON introduction====
* http://www.json.org/fatfree.html

JSON is a data format commonly used to store activity data in the Journal.

* http://simplejson.googlecode.com/svn/tags/simplejson-2.0.8/docs/index.html

Currently, the recommended JSON library is simplejson. It has also become the standard JSON library in Python 2.6+.

NOTE: There is an odd thing about simplejson - in python25 it lives in ''simplejson'' module, but in python26 it uses ''json'' module. So, use something like [http://git.sugarlabs.org/projects/sugar-port/repos/mainline/blobs/master/json.py this] to wrap it.

====Git introduction====
Git is the version control software used by Sugar Labs. It is a distributed version control system and is quite powerful, but requires a lot of command line use.

* [[Activity Team/Git|Git]]

====XML routines====
There are [http://docs.python.org/library/markup.html dozens] Python classes to satisfy the XML standard, but if you want just save/load parameters use "Zen of XML" in Python - [http://effbot.org/zone/element.htm ElementTree] library. It's supported out of the box in Python 2.5 (xml.etree.ElementTree module). In previous versions you'll have to install library by yourself.

But if you just need a simple configuration format to read/write Python objects, check out JSON instead.

====Speech synthesizing====
If you want to add a speech synthesizer for English and other languages, try the [[Activity_Team/gst-plugins-espeak|gst-plugins-espeak]] plugin for gstreamer.

==Activity Development Resources==
This is an open area for posting links related to activity development.

===Sample code===

* [http://git.sugarlabs.org/projects/hello-world Hello World] activity.
* An example of [[Activity Team/Sample code/Ruler|a simple activity that uses Cairo graphics]]
* An [http://uclug.org/images/Sugar.odp OpenOffice presentation] that touches on many of the issues encountered by first-time Sugar developers. Some items covered are: What is Sugar and Sugar Labs; What are some development environments; Some Sugar specific python statements for a PyGTK activity; Activity distribution. You can also [http://media.libsyn.com/media/dsyates/101309uclug0020.ogg listen] to the creator ([http://wiki.sugarlabs.org/go/User:Ossfm ossfm]) give the presentation at a LUG meeting (starting at 9 minutes and 55 seconds).

===Profiling in Python===

import os
import cProfile
import lsprofcalltree

profiler = cProfile.Profile()
profiler.enable()

# code to profile goes here

profiler.disable()
profiler.dump_stats('/tmp/profile')

Use kcachegrind to view the results.

===References===
* http://docs.python.org/ The official Python documentation.
* http://www.pygtk.org/docs/pygtk/index.html PyGTK API reference
* http://www.pygtk.org/docs/pygobject/index.html PyGObject API reference. Contains a few important things missing from the PyGTK API such as timers and idle callbacks.
* http://api.sugarlabs.org/ The official Sugar API documentation (quite sparse but includes all the source code).
* [[Development Team/Almanac]] Detailed Sugar API overview. Quite in depth and offers answers to common questions.
* http://pygstdocs.berlios.de/ Python GStreamer bindings.
* [[Human Interface Guidelines]] The design behind the Sugar interface. Very important to read and understand before planning your activity's user interface.
* http://cairographics.org/documentation/pycairo/ Cairo Python API reference. Very sparse, use the tutorial instead.
* [[Development Team/Low-level Activity API]] Information on how activities interact with Sugar independent of programming language.
* http://www.pygame.org/ The Pygame game development library.
* [[Development Team/sugargame]] Python package which makes it possible to embed Pygame in a Sugar activity.

===Tutorials and Whitepapers===
* http://diveintopython.org/ An online book which teaches Python step by step.
* http://www.pygtk.org/pygtk2tutorial/index.html A very informative step-by-step introduction to PyGTK.
* http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Introduction to activity development by OLPC Austria.
* [[OLPC:Sugar Activity Tutorial]] Another introduction to activity development.
* http://www.tortall.net/mu/wiki/CairoTutorial A great introduction to Cairo in PyGTK and vector graphics drawing in general.
* http://www.json.org/fatfree.html An overview of the JSON data format.
* http://simplejson.googlecode.com/svn/tags/simplejson-2.0.8/docs/index.html Documentation for the recommended JSON library.
* [[OLPC:Shared Sugar Activities]] High level overview of collaboration.
* [[OLPC:Collaboration Tutorial]] Step by step tutorial on integrating collaboration into an activity.
* [[Activity_Team/Modifing_an_Activity]] Information describing simple modifications that can be made to common Sugar activities.
* [[Activity Team/Compatibility Tips]] Information on ensuring your activity is portable to the various distributions that run Sugar.

==== Old tutorials ====

* Porting a PyGTK game to Sugar, [http://www.redhatmagazine.com/2007/04/05/building-the-xo-porting-a-pygtk-game-to-sugar-part-one/ Part 1] and [http://www.redhatmagazine.com/2007/04/26/building-the-xo-porting-a-pygtk-game-to-sugar-part-two/ Part 2], Red Hat Magazine.
* [http://wiki.laptop.org/go/Beyond_Hello_World Beyond Hello World], wiki.laptop.org

===Community resources===
* http://bugs.sugarlabs.org/ Bug tracking for Sugar and activities. Go here to report bugs in the Sugar toolkit. Each activity should have its own component here.
* http://git.sugarlabs.org/ Gitorious source code hosting.
* http://git.sugarlabs.org/events.atom RSS feed of all Sugar development activity. Great for keeping an eye on the project as a whole.

===Non-English resources===
* http://sites.google.com/site/sugaractivities/ Spanish language activity development site in Uruguay.

==Stuck?==

If you have a question, don't hesitate to ask the activity team. We are happy to help and can often save you a lot of hunting for answers.

We hang out in #sugar on irc.freenode.net, and you can always [http://lists.sugarlabs.org/listinfo/sugar-devel subscribe] and post questions to sugar-devel@lists.sugarlabs.org.

[[Category:Activity Team]]
[[Category:Resource]]

Activity Team/Resources

2011-01-17T17:51:17Z

Jdsimmons: /* Activity development tutorials */

<noinclude>{{GoogleTrans-en}}{{TeamHeader|Activity Team}}</noinclude>{{TOCright}}

==Getting started in Activity development==
If you have no experience developing Sugar activities, these resources will help get you started.

=== Activity development tutorials ===
{|
|-
|[[File:Sugarlabs_mainpage_07.png|link=http://en.flossmanuals.net/ActivitiesGuideSugar]]
|valign="center"|The official introduction to writing Sugar activities is the Flossmanuals book [http://en.flossmanuals.net/ActivitiesGuideSugar/Introduction Make Your Own Sugar Activities!], by James Simmons.
|}

====Setting up a Sugar environment====

Please see [[Downloads | Get Sugar]] for details on how to best get Sugar running.

If you decide to use a Virtual Machine (VM) or a secondary machine (such as an OLPC XO) for testing your activities, an editor with support for editing files over an SFTP connection can come in handy. [http://www.activestate.com/komodo-edit/downloads Komodo Edit] with the Remote Drive Tree extension and [http://www.eclipse.org Eclipse] with the [http://www.jcraft.com/eclipse-sftp/ SFTP Plugin] are examples.

====Python Reference & Tutorials====
* http://docs.python.org/
* http://diveintopython.org/
* [http://pleac.sourceforge.net/pleac_python/index.html PLEAC - Programming Language Examples Alike Cookbook]
* http://code.google.com/edu/languages/google-python-class/

Python is the language Sugar is written in and is also used by most activities. If you don't already know Python well, you should familiarize yourself with it before continuing.

====PyGTK Reference & Tutorials====
* http://www.pygtk.org/docs/pygtk/index.html
* http://www.pygtk.org/docs/pygobject/index.html

PyGTK is the user interface toolkit used by Sugar activities. Bookmark these two links as you will reference them frequently during development.

* http://www.pygtk.org/pygtk2tutorial/index.html

The following sections of the PyGTK tutorial are most relevant to activity development.

: 1. Introduction
: 2. Getting Started
: 3. Moving On
: 4. Packing Widgets
: 5. Widget Overview
: 6. The Button Widget
: 7. Adjustments
: 8. Range Widgets
: 9. Miscellaneous Widgets
: 10. Container Widgets
: 12. Drawing Area

Also see:

* http://www.majorsilence.com/PyGTK_Book

====Sugar Activities====
* [[Development Team/Almanac|Sugar Almanac]]

The Sugar Almanac contains all the information you need to start writing Sugar activities, ranging from directory structure to bundle format to API reference. It also contains answers to common questions and examples of common tasks.

* http://api.sugarlabs.org/

This automatically updated site contains the official API documentation for Sugar. Though it is currently quite sparse, the source code is included with the documentation and it's useful to have that at your fingertips.

* [[Development Team/Low-level Activity API|Low-Level Activity API]]

Activities can be written in any programming language, as long as it can connect to D-Bus and provide an X11 interface. This documents Sugar's low-level API, in particular for use by activities written in languages other than Python.

====Cairo Graphics====
* http://www.tortall.net/mu/wiki/CairoTutorial

Cairo is the graphics library used in Sugar. The tutorial is a good introduction to the API as well as vector graphics programming in general.

====Pygame====
* http://www.pygame.org/
* [[Development_Team/sugargame]]

Pygame is a library for developing 2D sprite-based games using Python. Sugargame is a package which makes it possible to embed Pygame into a Sugar activity.

====Sugar [[Human Interface Guidelines]] (HIG)====
* [[Human Interface Guidelines]].

Required reading before planning the user interface for your activity. These pages give a good introduction to the thought process behind the Sugar environment and will help a lot when designing your activity.

====i18n (Localisation) Best Practices====
* [[Translation_Team/i18n_Best_Practices]].

Once you have strings in your Activity, here are some general tips which will make your translators happy :-)

====JSON introduction====
* http://www.json.org/fatfree.html

JSON is a data format commonly used to store activity data in the Journal.

* http://simplejson.googlecode.com/svn/tags/simplejson-2.0.8/docs/index.html

Currently, the recommended JSON library is simplejson. It has also become the standard JSON library in Python 2.6+.

NOTE: There is an odd thing about simplejson - in python25 it lives in ''simplejson'' module, but in python26 it uses ''json'' module. So, use something like [http://git.sugarlabs.org/projects/sugar-port/repos/mainline/blobs/master/json.py this] to wrap it.

====Git introduction====
Git is the version control software used by Sugar Labs. It is a distributed version control system and is quite powerful, but requires a lot of command line use.

* [[Activity Team/Git|Git]]

====XML routines====
There are [http://docs.python.org/library/markup.html dozens] Python classes to satisfy the XML standard, but if you want just save/load parameters use "Zen of XML" in Python - [http://effbot.org/zone/element.htm ElementTree] library. It's supported out of the box in Python 2.5 (xml.etree.ElementTree module). In previous versions you'll have to install library by yourself.

But if you just need a simple configuration format to read/write Python objects, check out JSON instead.

====Speech synthesizing====
If you want to add a speech synthesizer for English and other languages, try the [[Activity_Team/gst-plugins-espeak|gst-plugins-espeak]] plugin for gstreamer.

==Activity Development Resources==
This is an open area for posting links related to activity development.

===Sample code===

* [http://git.sugarlabs.org/projects/hello-world Hello World] activity.
* An example of [[Activity Team/Sample code/Ruler|a simple activity that uses Cairo graphics]]
* An [http://uclug.org/images/Sugar.odp OpenOffice presentation] that touches on many of the issues encountered by first-time Sugar developers. Some items covered are: What is Sugar and Sugar Labs; What are some development environments; Some Sugar specific python statements for a PyGTK activity; Activity distribution. You can also [http://media.libsyn.com/media/dsyates/101309uclug0020.ogg listen] to the creator ([http://wiki.sugarlabs.org/go/User:Ossfm ossfm]) give the presentation at a LUG meeting (starting at 9 minutes and 55 seconds).

===Profiling in Python===

import os
import cProfile
import lsprofcalltree

profiler = cProfile.Profile()
profiler.enable()

# code to profile goes here

profiler.disable()
profiler.dump_stats('/tmp/profile')

Use kcachegrind to view the results.

===References===
* http://docs.python.org/ The official Python documentation.
* http://www.pygtk.org/docs/pygtk/index.html PyGTK API reference
* http://www.pygtk.org/docs/pygobject/index.html PyGObject API reference. Contains a few important things missing from the PyGTK API such as timers and idle callbacks.
* http://api.sugarlabs.org/ The official Sugar API documentation (quite sparse but includes all the source code).
* [[Development Team/Almanac]] Detailed Sugar API overview. Quite in depth and offers answers to common questions.
* http://pygstdocs.berlios.de/ Python GStreamer bindings.
* [[Human Interface Guidelines]] The design behind the Sugar interface. Very important to read and understand before planning your activity's user interface.
* http://cairographics.org/documentation/pycairo/ Cairo Python API reference. Very sparse, use the tutorial instead.
* [[Development Team/Low-level Activity API]] Information on how activities interact with Sugar independent of programming language.
* http://www.pygame.org/ The Pygame game development library.
* [[Development Team/sugargame]] Python package which makes it possible to embed Pygame in a Sugar activity.

===Tutorials and Whitepapers===
* http://diveintopython.org/ An online book which teaches Python step by step.
* http://www.pygtk.org/pygtk2tutorial/index.html A very informative step-by-step introduction to PyGTK.
* http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Introduction to activity development by OLPC Austria.
* [[OLPC:Sugar Activity Tutorial]] Another introduction to activity development.
* http://www.tortall.net/mu/wiki/CairoTutorial A great introduction to Cairo in PyGTK and vector graphics drawing in general.
* http://www.json.org/fatfree.html An overview of the JSON data format.
* http://simplejson.googlecode.com/svn/tags/simplejson-2.0.8/docs/index.html Documentation for the recommended JSON library.
* [[OLPC:Shared Sugar Activities]] High level overview of collaboration.
* [[OLPC:Collaboration Tutorial]] Step by step tutorial on integrating collaboration into an activity.
* [[Activity_Team/Modifing_an_Activity]] Information describing simple modifications that can be made to common Sugar activities.
* [[Activity Team/Compatibility Tips]] Information on ensuring your activity is portable to the various distributions that run Sugar.

==== Old tutorials ====

* Porting a PyGTK game to Sugar, [http://www.redhatmagazine.com/2007/04/05/building-the-xo-porting-a-pygtk-game-to-sugar-part-one/ Part 1] and [http://www.redhatmagazine.com/2007/04/26/building-the-xo-porting-a-pygtk-game-to-sugar-part-two/ Part 2], Red Hat Magazine.
* [http://wiki.laptop.org/go/Beyond_Hello_World Beyond Hello World], wiki.laptop.org

===Community resources===
* http://bugs.sugarlabs.org/ Bug tracking for Sugar and activities. Go here to report bugs in the Sugar toolkit. Each activity should have its own component here.
* http://git.sugarlabs.org/ Gitorious source code hosting.
* http://git.sugarlabs.org/events.atom RSS feed of all Sugar development activity. Great for keeping an eye on the project as a whole.

===Non-English resources===
* http://sites.google.com/site/sugaractivities/ Spanish language activity development site in Uruguay.

==Stuck?==

If you have a question, don't hesitate to ask the activity team. We are happy to help and can often save you a lot of hunting for answers.

We hang out in #sugar on irc.freenode.net, and you can always [http://lists.sugarlabs.org/listinfo/sugar-devel subscribe] and post questions to sugar-devel@lists.sugarlabs.org.

[[Category:Activity Team]]
[[Category:Resource]]

Activity Team/Resources

2011-01-17T17:50:24Z

Jdsimmons: /* Activity development tutorials */

<noinclude>{{GoogleTrans-en}}{{TeamHeader|Activity Team}}</noinclude>{{TOCright}}

==Getting started in Activity development==
If you have no experience developing Sugar activities, these resources will help get you started.

=== Activity development tutorials ===
{|
|-
|[[File:Sugarlabs_mainpage_07.png|link=http://en.flossmanuals.net/ActivitiesGuideSugar]]
|valign="center"|The official introduction to writing Sugar activities is the Flossmanuals book [http://en.flossmanuals.net/ActivitiesGuideSugar/Introduction Writing Sugar Activities], by James Simmons.
|}

====Setting up a Sugar environment====

Please see [[Downloads | Get Sugar]] for details on how to best get Sugar running.

If you decide to use a Virtual Machine (VM) or a secondary machine (such as an OLPC XO) for testing your activities, an editor with support for editing files over an SFTP connection can come in handy. [http://www.activestate.com/komodo-edit/downloads Komodo Edit] with the Remote Drive Tree extension and [http://www.eclipse.org Eclipse] with the [http://www.jcraft.com/eclipse-sftp/ SFTP Plugin] are examples.

====Python Reference & Tutorials====
* http://docs.python.org/
* http://diveintopython.org/
* [http://pleac.sourceforge.net/pleac_python/index.html PLEAC - Programming Language Examples Alike Cookbook]
* http://code.google.com/edu/languages/google-python-class/

Python is the language Sugar is written in and is also used by most activities. If you don't already know Python well, you should familiarize yourself with it before continuing.

====PyGTK Reference & Tutorials====
* http://www.pygtk.org/docs/pygtk/index.html
* http://www.pygtk.org/docs/pygobject/index.html

PyGTK is the user interface toolkit used by Sugar activities. Bookmark these two links as you will reference them frequently during development.

* http://www.pygtk.org/pygtk2tutorial/index.html

The following sections of the PyGTK tutorial are most relevant to activity development.

: 1. Introduction
: 2. Getting Started
: 3. Moving On
: 4. Packing Widgets
: 5. Widget Overview
: 6. The Button Widget
: 7. Adjustments
: 8. Range Widgets
: 9. Miscellaneous Widgets
: 10. Container Widgets
: 12. Drawing Area

Also see:

* http://www.majorsilence.com/PyGTK_Book

====Sugar Activities====
* [[Development Team/Almanac|Sugar Almanac]]

The Sugar Almanac contains all the information you need to start writing Sugar activities, ranging from directory structure to bundle format to API reference. It also contains answers to common questions and examples of common tasks.

* http://api.sugarlabs.org/

This automatically updated site contains the official API documentation for Sugar. Though it is currently quite sparse, the source code is included with the documentation and it's useful to have that at your fingertips.

* [[Development Team/Low-level Activity API|Low-Level Activity API]]

Activities can be written in any programming language, as long as it can connect to D-Bus and provide an X11 interface. This documents Sugar's low-level API, in particular for use by activities written in languages other than Python.

====Cairo Graphics====
* http://www.tortall.net/mu/wiki/CairoTutorial

Cairo is the graphics library used in Sugar. The tutorial is a good introduction to the API as well as vector graphics programming in general.

====Pygame====
* http://www.pygame.org/
* [[Development_Team/sugargame]]

Pygame is a library for developing 2D sprite-based games using Python. Sugargame is a package which makes it possible to embed Pygame into a Sugar activity.

====Sugar [[Human Interface Guidelines]] (HIG)====
* [[Human Interface Guidelines]].

Required reading before planning the user interface for your activity. These pages give a good introduction to the thought process behind the Sugar environment and will help a lot when designing your activity.

====i18n (Localisation) Best Practices====
* [[Translation_Team/i18n_Best_Practices]].

Once you have strings in your Activity, here are some general tips which will make your translators happy :-)

====JSON introduction====
* http://www.json.org/fatfree.html

JSON is a data format commonly used to store activity data in the Journal.

* http://simplejson.googlecode.com/svn/tags/simplejson-2.0.8/docs/index.html

Currently, the recommended JSON library is simplejson. It has also become the standard JSON library in Python 2.6+.

NOTE: There is an odd thing about simplejson - in python25 it lives in ''simplejson'' module, but in python26 it uses ''json'' module. So, use something like [http://git.sugarlabs.org/projects/sugar-port/repos/mainline/blobs/master/json.py this] to wrap it.

====Git introduction====
Git is the version control software used by Sugar Labs. It is a distributed version control system and is quite powerful, but requires a lot of command line use.

* [[Activity Team/Git|Git]]

====XML routines====
There are [http://docs.python.org/library/markup.html dozens] Python classes to satisfy the XML standard, but if you want just save/load parameters use "Zen of XML" in Python - [http://effbot.org/zone/element.htm ElementTree] library. It's supported out of the box in Python 2.5 (xml.etree.ElementTree module). In previous versions you'll have to install library by yourself.

But if you just need a simple configuration format to read/write Python objects, check out JSON instead.

====Speech synthesizing====
If you want to add a speech synthesizer for English and other languages, try the [[Activity_Team/gst-plugins-espeak|gst-plugins-espeak]] plugin for gstreamer.

==Activity Development Resources==
This is an open area for posting links related to activity development.

===Sample code===

* [http://git.sugarlabs.org/projects/hello-world Hello World] activity.
* An example of [[Activity Team/Sample code/Ruler|a simple activity that uses Cairo graphics]]
* An [http://uclug.org/images/Sugar.odp OpenOffice presentation] that touches on many of the issues encountered by first-time Sugar developers. Some items covered are: What is Sugar and Sugar Labs; What are some development environments; Some Sugar specific python statements for a PyGTK activity; Activity distribution. You can also [http://media.libsyn.com/media/dsyates/101309uclug0020.ogg listen] to the creator ([http://wiki.sugarlabs.org/go/User:Ossfm ossfm]) give the presentation at a LUG meeting (starting at 9 minutes and 55 seconds).

===Profiling in Python===

import os
import cProfile
import lsprofcalltree

profiler = cProfile.Profile()
profiler.enable()

# code to profile goes here

profiler.disable()
profiler.dump_stats('/tmp/profile')

Use kcachegrind to view the results.

===References===
* http://docs.python.org/ The official Python documentation.
* http://www.pygtk.org/docs/pygtk/index.html PyGTK API reference
* http://www.pygtk.org/docs/pygobject/index.html PyGObject API reference. Contains a few important things missing from the PyGTK API such as timers and idle callbacks.
* http://api.sugarlabs.org/ The official Sugar API documentation (quite sparse but includes all the source code).
* [[Development Team/Almanac]] Detailed Sugar API overview. Quite in depth and offers answers to common questions.
* http://pygstdocs.berlios.de/ Python GStreamer bindings.
* [[Human Interface Guidelines]] The design behind the Sugar interface. Very important to read and understand before planning your activity's user interface.
* http://cairographics.org/documentation/pycairo/ Cairo Python API reference. Very sparse, use the tutorial instead.
* [[Development Team/Low-level Activity API]] Information on how activities interact with Sugar independent of programming language.
* http://www.pygame.org/ The Pygame game development library.
* [[Development Team/sugargame]] Python package which makes it possible to embed Pygame in a Sugar activity.

===Tutorials and Whitepapers===
* http://diveintopython.org/ An online book which teaches Python step by step.
* http://www.pygtk.org/pygtk2tutorial/index.html A very informative step-by-step introduction to PyGTK.
* http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Introduction to activity development by OLPC Austria.
* [[OLPC:Sugar Activity Tutorial]] Another introduction to activity development.
* http://www.tortall.net/mu/wiki/CairoTutorial A great introduction to Cairo in PyGTK and vector graphics drawing in general.
* http://www.json.org/fatfree.html An overview of the JSON data format.
* http://simplejson.googlecode.com/svn/tags/simplejson-2.0.8/docs/index.html Documentation for the recommended JSON library.
* [[OLPC:Shared Sugar Activities]] High level overview of collaboration.
* [[OLPC:Collaboration Tutorial]] Step by step tutorial on integrating collaboration into an activity.
* [[Activity_Team/Modifing_an_Activity]] Information describing simple modifications that can be made to common Sugar activities.
* [[Activity Team/Compatibility Tips]] Information on ensuring your activity is portable to the various distributions that run Sugar.

==== Old tutorials ====

* Porting a PyGTK game to Sugar, [http://www.redhatmagazine.com/2007/04/05/building-the-xo-porting-a-pygtk-game-to-sugar-part-one/ Part 1] and [http://www.redhatmagazine.com/2007/04/26/building-the-xo-porting-a-pygtk-game-to-sugar-part-two/ Part 2], Red Hat Magazine.
* [http://wiki.laptop.org/go/Beyond_Hello_World Beyond Hello World], wiki.laptop.org

===Community resources===
* http://bugs.sugarlabs.org/ Bug tracking for Sugar and activities. Go here to report bugs in the Sugar toolkit. Each activity should have its own component here.
* http://git.sugarlabs.org/ Gitorious source code hosting.
* http://git.sugarlabs.org/events.atom RSS feed of all Sugar development activity. Great for keeping an eye on the project as a whole.

===Non-English resources===
* http://sites.google.com/site/sugaractivities/ Spanish language activity development site in Uruguay.

==Stuck?==

If you have a question, don't hesitate to ask the activity team. We are happy to help and can often save you a lot of hunting for answers.

We hang out in #sugar on irc.freenode.net, and you can always [http://lists.sugarlabs.org/listinfo/sugar-devel subscribe] and post questions to sugar-devel@lists.sugarlabs.org.

[[Category:Activity Team]]
[[Category:Resource]]

Activities/Read SD Comics

2010-10-20T14:14:21Z

Jdsimmons: /* Description & Goals */

<noinclude>{{TOCright}}[[Category:Activities|Read SD Comics]]</noinclude>
== Description & Goals==

Read SD Comics is my second attempt at creating a comic book reading Activity for the XO laptop. View Slides was the first. Read SD Comics actually has fewer features than View Slides. You can't share documents, there are no annotations and no support for multiple bookmarks, and you cannot create and edit slide collections. It just reads image collections in Zip and .CBZ archives.

Why create an Activity that does the same thing as View Slides but with fewer features? The answer is simple: Read SD Comics does not read image archives in the Journal. Instead, the comic files are kept on an SD card or other external storage, and the Journal only stores a link to the comic file plus metadata like the page you left off on, title, description, etc.

If you own an XO laptop you should be able to see the advantage of this approach. Every XO laptop has a place to insert an SD card. The slot is designed to make the card difficult to remove, so it is essentially internal storage. You can get a cheap SD card (or a micro SD with an adapter) and easily add up to 8 gigabytes of storage to your XO.

Unfortunately, the SD card isn't good for much because Sugar works with the Journal and the Journal uses internal storage only. Since internal storage has to hold the operating system, etc. you have only about 500 megabytes to hold your stuff. A long comic book can easily be over 60 megabytes you just can't store much of a collection in the Journal. You can, however, store lots of them on an SD card.

The Journal Activity makes the SD card ''look'' like part of the Journal, but it is not. The files are listed in the reverse order of when they were created, not by when you last read them. You cannot rename the files. You can launch View Slides to read them, but when you are done you will get a "Keep Error" and the page you left off on will not be saved.

When you use Read SD Comics the experience is much better. If you start from the Activity ring you will be prompted to select a CBZ or Zip file using a standard file selection component. When you make your selection you'll see a preview of the first page of the comic. Click on the "Read Comic" button at the bottom of the screen, and the path to the file you selected will be stored in the Journal and your comic will be loaded for reading.

At this point you can treat the comic as if it actually is in the Journal rather than merely linked to it. You'll have all the advantages of a Journal entry without filling up the all too limited space the Journal on the XO provides.

The interface to Read SD Comics is similar to the core Read activity. You can use the up and down arrows or the game controller to move from page to page. Use plus and minus keys to zoom and unzoom the page.

The Activity should work on all versions of Sugar from .82 on up. On older versions of Sugar you'll see an old style toolbar instead of the one shown in the screen shots, but the available functions will be the same.

== Comic Books on the Internet ==

Some books at Project Gutenberg are already in a suitable format. Try downloading this file from [http://www.gutenberg.org/ebooks/21078 Project Gutenberg]. Look for the file format "Raw page images".

If you want to read some free comic books the Internet Archive has a bunch of them. Use [http://www.archive.org/search.php?query=comics%20cbr this query] to see a list of them. They are mostly in the .cbr format, and those will need to be converted to the .cbz (Zip) format to be used with this Activity. The program Comix under Linux can do this conversion for you if you have the unrar utility installed, or you can simply unrar the .cbr file to get the images, then package the images in a zip file:

unrar e LoneRangerDell100.cbr
zip LoneRangerDell100 *.jpg

If you use Windows you can use the free [http://www.7zip.org 7zip File Manager] to extract the files from the .cbr and pack them up again in a zip file.

== Current Features ==

* Currently you can load a zip file containing images and page through them in sequence like a book. The images will be resized to best fit in the current screen resolution without scrolling. If you change the screen orientation the image will be resized to fit the new orientation.
* You can hide the mouse pointer (or make it visible again) by pressing the "square" button to the lower right of the XO screen (or numeric keypad "Home" on any other computer). This removes a source of distraction when viewing images.
* You can zoom the image to fit the width of the screen and scroll it vertically. This is handy for reading scanned in books with smaller print. Also new with version 7 you can hide and show the toolbar by pressing Alt-Enter on the keyboard, giving you the ability to view your slides using the full screen.

== Source ==

* http://git.sugarlabs.org/projects/read-sd-comics
* [http://activities.sugarlabs.org/en-US/sugar/addon/4340/ Sugar Activity Library page]

Activities/Read SD Comics

2010-10-20T14:06:54Z

Jdsimmons: /* Slide Collections on the Internet */

<noinclude>{{TOCright}}[[Category:Activities|Read SD Comics]]</noinclude>
== Description & Goals==

Read SD Comics is my second attempt at creating a comic book reading Activity for the XO laptop. View Slides was the first. Read SD Comics actually has fewer features than View Slides. You can't share documents, there are no annotations and no support for multiple bookmarks, and you cannot create and edit slide collections. It just reads image collections in Zip and .CBZ archives.

Why create an Activity that does the same thing as View Slides but with fewer features? The answer is simple: Read SD Comics does not read image archives in the Journal. Instead, the comic files are kept on an SD card or other external storage, and the Journal only stores a link to the comic file plus metadata like the page you left off on, title, description, etc.

If you own an XO laptop you should be able to see the advantage of this approach. Every XO laptop has a place to insert an SD card. The slot is designed to make the card difficult to remove. If you have a cheap SD card you can add up to 8 gigabytes of storage to your XO.

Unfortunately, the SD card isn't good for much because Sugar works with the Journal and the Journal is on internal storage only. Since internal storage has to hold the operating system, etc. you have only about 500 megabytes to hold your stuff. Since a long comic book can easily be over 60 megabytes you just can't store much of a collection in the Journal. You can, however, store lots of them on an SD card.

The Journal Activity makes the SD card files look like part of the Journal, but they are not. They are listed in the reverse order of when they were created. You cannot rename them. You can launch View Slides to read them, but when you are done you will get a "Keep Error" and the page you left off on will not be saved.

When you use Read SD Comics the experience is much better. If you start from the Activity ring you will be prompted to select a CBZ or Zip file using a standard file selection component. When you make your selection you'll see a preview of the first page of the comic. Then you click on the "Read Comic" button at the bottom of the screen, and the path to the file you selected will be stored in the Journal and your comic will be loaded for reading.

At this point you can treat the comic as if it actually is in the Journal rather than merely linked to it. You'll have all the advantages of a Journal entry without filling up the all too limited space the Journal on the XO provides.

The interface to Read SD Comics is similar to the core Read activity, which should not be surprising as the toolbar code was adapted from Read's toolbar. You can use the up and down arrows or the game controller to move from page to page. Use plus and minus keys to zoom and unzoom the page.

== Comic Books on the Internet ==

Some books at Project Gutenberg are already in a suitable format. Try downloading this file from [http://www.gutenberg.org/ebooks/21078 Project Gutenberg]. Look for the file format "Raw page images".

If you want to read some free comic books the Internet Archive has a bunch of them. Use [http://www.archive.org/search.php?query=comics%20cbr this query] to see a list of them. They are mostly in the .cbr format, and those will need to be converted to the .cbz (Zip) format to be used with this Activity. The program Comix under Linux can do this conversion for you if you have the unrar utility installed, or you can simply unrar the .cbr file to get the images, then package the images in a zip file:

unrar e LoneRangerDell100.cbr
zip LoneRangerDell100 *.jpg

If you use Windows you can use the free [http://www.7zip.org 7zip File Manager] to extract the files from the .cbr and pack them up again in a zip file.

== Current Features ==

* Currently you can load a zip file containing images and page through them in sequence like a book. The images will be resized to best fit in the current screen resolution without scrolling. If you change the screen orientation the image will be resized to fit the new orientation.
* You can hide the mouse pointer (or make it visible again) by pressing the "square" button to the lower right of the XO screen (or numeric keypad "Home" on any other computer). This removes a source of distraction when viewing images.
* You can zoom the image to fit the width of the screen and scroll it vertically. This is handy for reading scanned in books with smaller print. Also new with version 7 you can hide and show the toolbar by pressing Alt-Enter on the keyboard, giving you the ability to view your slides using the full screen.

== Source ==

* http://git.sugarlabs.org/projects/read-sd-comics
* [http://activities.sugarlabs.org/en-US/sugar/addon/4340/ Sugar Activity Library page]

Activities/Read SD Comics

2010-10-20T14:03:25Z

Jdsimmons: /* Source */

<noinclude>{{TOCright}}[[Category:Activities|Read SD Comics]]</noinclude>
== Description & Goals==

Read SD Comics is my second attempt at creating a comic book reading Activity for the XO laptop. View Slides was the first. Read SD Comics actually has fewer features than View Slides. You can't share documents, there are no annotations and no support for multiple bookmarks, and you cannot create and edit slide collections. It just reads image collections in Zip and .CBZ archives.

Why create an Activity that does the same thing as View Slides but with fewer features? The answer is simple: Read SD Comics does not read image archives in the Journal. Instead, the comic files are kept on an SD card or other external storage, and the Journal only stores a link to the comic file plus metadata like the page you left off on, title, description, etc.

If you own an XO laptop you should be able to see the advantage of this approach. Every XO laptop has a place to insert an SD card. The slot is designed to make the card difficult to remove. If you have a cheap SD card you can add up to 8 gigabytes of storage to your XO.

Unfortunately, the SD card isn't good for much because Sugar works with the Journal and the Journal is on internal storage only. Since internal storage has to hold the operating system, etc. you have only about 500 megabytes to hold your stuff. Since a long comic book can easily be over 60 megabytes you just can't store much of a collection in the Journal. You can, however, store lots of them on an SD card.

The Journal Activity makes the SD card files look like part of the Journal, but they are not. They are listed in the reverse order of when they were created. You cannot rename them. You can launch View Slides to read them, but when you are done you will get a "Keep Error" and the page you left off on will not be saved.

When you use Read SD Comics the experience is much better. If you start from the Activity ring you will be prompted to select a CBZ or Zip file using a standard file selection component. When you make your selection you'll see a preview of the first page of the comic. Then you click on the "Read Comic" button at the bottom of the screen, and the path to the file you selected will be stored in the Journal and your comic will be loaded for reading.

At this point you can treat the comic as if it actually is in the Journal rather than merely linked to it. You'll have all the advantages of a Journal entry without filling up the all too limited space the Journal on the XO provides.

The interface to Read SD Comics is similar to the core Read activity, which should not be surprising as the toolbar code was adapted from Read's toolbar. You can use the up and down arrows or the game controller to move from page to page. Use plus and minus keys to zoom and unzoom the page.

== Slide Collections on the Internet ==

Some books at Project Gutenberg are already in a suitable format. Try downloading this file from [http://www.gutenberg.org/ebooks/21078 Project Gutenberg]. Look for the file format "Raw page images".

If you want to read some free comic books the Internet Archive has a bunch of them. Use [http://www.archive.org/search.php?query=comics%20cbr this query] to see a list of them. They are in the .cbr format, and will need to be converted to the .cbz (Zip) format to be used with View Slides. The program Comix under Linux can do this conversion for you if you have the unrar utility installed, or you can simply unrar the .cbr file to get the images, then package the images in a zip file:

unrar e LoneRangerDell100.cbr
zip LoneRangerDell100 *.jpg

If you use Windows you can use the free [http://www.7zip.org 7zip File Manager] to extract the files from the .cbr and pack them up again in a zip file.

== Current Features ==

* Currently you can load a zip file containing images and page through them in sequence like a book. The images will be resized to best fit in the current screen resolution without scrolling. If you change the screen orientation the image will be resized to fit the new orientation.
* You can hide the mouse pointer (or make it visible again) by pressing the "square" button to the lower right of the XO screen (or numeric keypad "Home" on any other computer). This removes a source of distraction when viewing images.
* You can zoom the image to fit the width of the screen and scroll it vertically. This is handy for reading scanned in books with smaller print. Also new with version 7 you can hide and show the toolbar by pressing Alt-Enter on the keyboard, giving you the ability to view your slides using the full screen.

== Source ==

* http://git.sugarlabs.org/projects/read-sd-comics
* [http://activities.sugarlabs.org/en-US/sugar/addon/4340/ Sugar Activity Library page]

Activities/Read SD Comics

2010-10-19T20:09:01Z

Jdsimmons: /* Description & Goals */

<noinclude>{{TOCright}}[[Category:Activities|Read SD Comics]]</noinclude>
== Description & Goals==

Read SD Comics is my second attempt at creating a comic book reading Activity for the XO laptop. View Slides was the first. Read SD Comics actually has fewer features than View Slides. You can't share documents, there are no annotations and no support for multiple bookmarks, and you cannot create and edit slide collections. It just reads image collections in Zip and .CBZ archives.

Why create an Activity that does the same thing as View Slides but with fewer features? The answer is simple: Read SD Comics does not read image archives in the Journal. Instead, the comic files are kept on an SD card or other external storage, and the Journal only stores a link to the comic file plus metadata like the page you left off on, title, description, etc.

If you own an XO laptop you should be able to see the advantage of this approach. Every XO laptop has a place to insert an SD card. The slot is designed to make the card difficult to remove. If you have a cheap SD card you can add up to 8 gigabytes of storage to your XO.

Unfortunately, the SD card isn't good for much because Sugar works with the Journal and the Journal is on internal storage only. Since internal storage has to hold the operating system, etc. you have only about 500 megabytes to hold your stuff. Since a long comic book can easily be over 60 megabytes you just can't store much of a collection in the Journal. You can, however, store lots of them on an SD card.

The Journal Activity makes the SD card files look like part of the Journal, but they are not. They are listed in the reverse order of when they were created. You cannot rename them. You can launch View Slides to read them, but when you are done you will get a "Keep Error" and the page you left off on will not be saved.

When you use Read SD Comics the experience is much better. If you start from the Activity ring you will be prompted to select a CBZ or Zip file using a standard file selection component. When you make your selection you'll see a preview of the first page of the comic. Then you click on the "Read Comic" button at the bottom of the screen, and the path to the file you selected will be stored in the Journal and your comic will be loaded for reading.

At this point you can treat the comic as if it actually is in the Journal rather than merely linked to it. You'll have all the advantages of a Journal entry without filling up the all too limited space the Journal on the XO provides.

The interface to Read SD Comics is similar to the core Read activity, which should not be surprising as the toolbar code was adapted from Read's toolbar. You can use the up and down arrows or the game controller to move from page to page. Use plus and minus keys to zoom and unzoom the page.

== Slide Collections on the Internet ==

Some books at Project Gutenberg are already in a suitable format. Try downloading this file from [http://www.gutenberg.org/ebooks/21078 Project Gutenberg]. Look for the file format "Raw page images".

If you want to read some free comic books the Internet Archive has a bunch of them. Use [http://www.archive.org/search.php?query=comics%20cbr this query] to see a list of them. They are in the .cbr format, and will need to be converted to the .cbz (Zip) format to be used with View Slides. The program Comix under Linux can do this conversion for you if you have the unrar utility installed, or you can simply unrar the .cbr file to get the images, then package the images in a zip file:

unrar e LoneRangerDell100.cbr
zip LoneRangerDell100 *.jpg

If you use Windows you can use the free [http://www.7zip.org 7zip File Manager] to extract the files from the .cbr and pack them up again in a zip file.

== Current Features ==

* Currently you can load a zip file containing images and page through them in sequence like a book. The images will be resized to best fit in the current screen resolution without scrolling. If you change the screen orientation the image will be resized to fit the new orientation.
* You can hide the mouse pointer (or make it visible again) by pressing the "square" button to the lower right of the XO screen (or numeric keypad "Home" on any other computer). This removes a source of distraction when viewing images.
* You can zoom the image to fit the width of the screen and scroll it vertically. This is handy for reading scanned in books with smaller print. Also new with version 7 you can hide and show the toolbar by pressing Alt-Enter on the keyboard, giving you the ability to view your slides using the full screen.

== Source ==

* http://git.sugarlabs.org/projects/viewslides
* [http://activities.sugarlabs.org/en-US/sugar/addon/4039 Sugar Activity Library page]

Activities/Read SD Comics

2010-10-19T19:41:03Z

Jdsimmons: /* Description & Goals */

<noinclude>{{TOCright}}[[Category:Activities|Read SD Comics]]</noinclude>
== Description & Goals==

Read SD Comics is my second attempt at creating a comic book reading Activity for the XO laptop. View Slides was the first. Read SD Comics actually has fewer features than View Slides. You can't share documents, there are no annotations and no support for multiple bookmarks, and you cannot create and edit slide collections. It just reads image collections in Zip and .CBZ archives.

Why create an Activity that does the same thing as View Slides but with fewer features? The answer is simple: Read SD Comics does not read image archives in the Journal. Instead, the comic files are kept on an SD card or other external storage, and the Journal only stores a link to the comic file plus metadata like the page you left off on, title, description, etc.

If you own an XO laptop you should be able to see the advantage of this approach. Every XO laptop has a place to insert an SD card. The slot is designed to make the card difficult to remove. If you have a cheap SD card you can add up to 8 gigabytes of storage to your XO.

Unfortunately, the SD card isn't good for much because Sugar works with the Journal and the Journal is on internal storage only. Since internal storage has to hold the operating system, etc. you have only about 500 megabytes to hold your stuff. Since a long comic book can easily be over 60 megabytes you just can't store much of a collection in the Journal. You can, however, store lots of them on an SD card.

The Journal Activity makes the SD card files look like part of the Journal, but they are not. They are listed in the reverse order of when they were created

The interface to Read SD Comics is similar to the core Read activity, which should not be surprising as the toolbar code was adapted from Read's toolbar. You can use the up and down arrows or the game controller to move from page to page.

== Slide Collections on the Internet ==

Some books at Project Gutenberg are already in a suitable format. Try downloading this file from [http://www.gutenberg.org/ebooks/21078 Project Gutenberg]. Look for the file format "Raw page images".

If you want to read some free comic books the Internet Archive has a bunch of them. Use [http://www.archive.org/search.php?query=comics%20cbr this query] to see a list of them. They are in the .cbr format, and will need to be converted to the .cbz (Zip) format to be used with View Slides. The program Comix under Linux can do this conversion for you if you have the unrar utility installed, or you can simply unrar the .cbr file to get the images, then package the images in a zip file:

unrar e LoneRangerDell100.cbr
zip LoneRangerDell100 *.jpg

If you use Windows you can use the free [http://www.7zip.org 7zip File Manager] to extract the files from the .cbr and pack them up again in a zip file.

== Current Features ==

* Currently you can load a zip file containing images and page through them in sequence like a book. The images will be resized to best fit in the current screen resolution without scrolling. If you change the screen orientation the image will be resized to fit the new orientation.
* You can hide the mouse pointer (or make it visible again) by pressing the "square" button to the lower right of the XO screen (or numeric keypad "Home" on any other computer). This removes a source of distraction when viewing images.
* You can zoom the image to fit the width of the screen and scroll it vertically. This is handy for reading scanned in books with smaller print. Also new with version 7 you can hide and show the toolbar by pressing Alt-Enter on the keyboard, giving you the ability to view your slides using the full screen.

== Source ==

* http://git.sugarlabs.org/projects/viewslides
* [http://activities.sugarlabs.org/en-US/sugar/addon/4039 Sugar Activity Library page]

Activities/Read SD Comics

2010-10-19T19:23:35Z

Jdsimmons: /* Description & Goals */

<noinclude>{{TOCright}}[[Category:Activities|Read SD Comics]]</noinclude>
== Description & Goals==

Read SD Comics is my second attempt at creating a comic book reading Activity for the XO laptop. View Slides was the first. Read SD Comics actually has fewer features than View Slides. You can't share documents, there are no annotations and no support for multiple bookmarks, and you cannot create and edit slide collections. It just reads image collections in Zip and .CBZ archives.

Why create an Activity that does the same thing as View Slides but with fewer features? The answer is simple: Read SD Comics does not read image archives in the Journal. Instead, the comic files are kept on an SD card or other external storage, and the Journal only stores a link to the comic file plus metadata like the page you left off on, title, description, etc.

If you own an XO laptop you should be able to see the advantage of this approach. Every XO laptop has a place to insert an SD card. The slot is designed to make the card difficult to remove. If you have a cheap SD card you can add up to 8 gigabytes of storage to your XO.

Unfortunately, the SD card isn't good for much because Sugar works with the Journal and the Journal is on internal storage only. Since internal storage has to hold the operating system, etc. you have only about 500 megabytes to hold your stuff. Since a long comic book can easily be over 60 megabytes you just can't store much of a collection in the Journal. You can, however, store lots of them on an SD card.

The interface to Read SD Comics is similar to the core Read activity, which should not be surprising as the toolbar code was adapted from Read's toolbar. You can use the up and down arrows or the game controller to move from page to page.

== Slide Collections on the Internet ==

Some books at Project Gutenberg are already in a suitable format. Try downloading this file from [http://www.gutenberg.org/ebooks/21078 Project Gutenberg]. Look for the file format "Raw page images".

If you want to read some free comic books the Internet Archive has a bunch of them. Use [http://www.archive.org/search.php?query=comics%20cbr this query] to see a list of them. They are in the .cbr format, and will need to be converted to the .cbz (Zip) format to be used with View Slides. The program Comix under Linux can do this conversion for you if you have the unrar utility installed, or you can simply unrar the .cbr file to get the images, then package the images in a zip file:

unrar e LoneRangerDell100.cbr
zip LoneRangerDell100 *.jpg

If you use Windows you can use the free [http://www.7zip.org 7zip File Manager] to extract the files from the .cbr and pack them up again in a zip file.

== Current Features ==

* Currently you can load a zip file containing images and page through them in sequence like a book. The images will be resized to best fit in the current screen resolution without scrolling. If you change the screen orientation the image will be resized to fit the new orientation.
* You can hide the mouse pointer (or make it visible again) by pressing the "square" button to the lower right of the XO screen (or numeric keypad "Home" on any other computer). This removes a source of distraction when viewing images.
* You can zoom the image to fit the width of the screen and scroll it vertically. This is handy for reading scanned in books with smaller print. Also new with version 7 you can hide and show the toolbar by pressing Alt-Enter on the keyboard, giving you the ability to view your slides using the full screen.

== Source ==

* http://git.sugarlabs.org/projects/viewslides
* [http://activities.sugarlabs.org/en-US/sugar/addon/4039 Sugar Activity Library page]

Activities/Read SD Comics

2010-10-19T19:16:34Z

Jdsimmons: Created page with "<noinclude>{{TOCright}}Read SD Comics</noinclude> == Description & Goals== Read SD Comics is my second attempt at creating a comic book reading Activity ..."

Activities/Sugar Commander

2010-03-30T21:35:45Z

Jdsimmons:

<noinclude>{{TOCright}}
[[Category:Activities|Sugar Commander]]</noinclude>

[http://activities.sugarlabs.org/en-US/sugar/addon/4291/ Activity Library download] | [http://git.sugarlabs.org/projects/sugar-commander Source] |

== Description & Goals==

Sugar Commander is a utility Activity that improves the experience of working with the Journal. It can do most things the Journal Activity itself can do with the exception of resuming Activities and copying Journal entries to files. (These functions are forbidden to ordinary Activities by Sugar).

== Current Features ==

Unlike the Journal Activity, which represents the contents of thumb drives and SD cards as if they were Journal entries, this Activity has a tab for files and directories and another tab for Journal entries. You can choose a file from anywhere in the file system and add it to the Journal as an entry. You can browse the Journal sorted by title or MIME type. You can select Journal entries and edit the title, description, and tags, plus see the preview image, without opening a new window. You can also delete Journal entries you don't want.

== Source ==

http://git.sugarlabs.org/projects/sugar-commander

Activities/Sugar Commander

2010-03-30T21:31:38Z

Jdsimmons: Created page with '<noinclude>{{TOCright}} Sugar Commander</noinclude> [http://activities.sugarlabs.org/en-US/sugar/addon/4291/ Activity Library download] | [http://git.sug…'

Sugar on a Stick/E-Books

2009-12-05T21:03:55Z

Jdsimmons:

Links of sources of e-books for children

*[http://www.archive.org/details/iacl Internet Archive Children's Library] Good source of illustrated books in several formats. DejaVu format is recommended.

*[http://drscavanaugh.org/ebooks/libraries/childrens_collections.htm Drs. Cavanaugh list]

*[http://www.gutenberg.org/wiki/Category:Children%27s_Bookshelf Project Gutenberg Children's Bookshelf] Mostly plain text books which can be read with the Read Etexts activity.

*[http://www.snee.com/epubkidsbooks/ Snee] Selection from Project Gutenberg.

*[http://www.epubbooks.com/genres epubBooks]

*[http://manybooks.net/about/ Manybooks.net]

*[http://www.onlinecourses.org/2009/11/11/100-useful-links-for-ebook-lovers/ 100 Useful Links for eBook Lovers] (lots of free book sources, don't know how much children's material there is- sorry)

*[http://onlinedegreeprograms.org/blog/2009/100-free-audio-books-you-should-have-read-by-now/ 100 Free Audio Books You Should Have Read By Now] (more links that need sorting through for suitable material but there is a children's section further down the page – audio ogg format books will play in Browse and could help for folks with visual disabilities or with spoken language learning).
**Audio book: [http://www.gutenberg.org/files/23897/ogg/23897-06.ogg '''The Owl and the Pussycat by Edward Lear''']

*[http://www.loc.gov/rr/rarebook/digitalcoll/digitalcoll-children.html US Library of Congress Rare Book Children's Literature Collection] A small number of classic children's stories in online and PDF formats.

*[http://www.baen.com/library/ Baen Free Library] Current and classic science fiction books which can be read online using Browse or downloaded in RTF format and read with Read Etexts. Most of the titles are suitable for older children.

*[http://craphound.com/littlebrother/download/ Little Brother] An excellent young adult science fiction novel that can be downloaded for free. EPUB, Plain Text, PDF, and XO library bundle versions are available.

*[http://digital.library.upenn.edu/women/_collections/newbery/newbery.html Newbery Medal Winners by Women Authors] HTML with original illustrations.

*[http://feedbooks.com/type/Young%20Readers/books/top Feedbooks Young Readers category]

*[http://en.childrenslibrary.org/ International Children's Digital Library] Books in many languages for young readers to read online.

Sugar on a Stick/E-Books

2009-12-02T16:10:14Z

Jdsimmons:

Links of sources of e-books for children

*[http://drscavanaugh.org/ebooks/libraries/childrens_collections.htm Drs. Cavanaugh list]

*[http://manybooks.net/about/ Manybooks.net]

*[http://www.epubbooks.com/genres epubBooks]

*[http://www.snee.com/epubkidsbooks/ Snee]

*[http://www.onlinecourses.org/2009/11/11/100-useful-links-for-ebook-lovers/ 100 Useful Links for eBook Lovers] (lots of free book sources, don't know how much children's material there is- sorry)

*[http://onlinedegreeprograms.org/blog/2009/100-free-audio-books-you-should-have-read-by-now/ 100 Free Audio Books You Should Have Read By Now] (more links that need sorting through for suitable material, audio ogg books could help for folks with visual disabilities or with spoken language learning).

*[http://www.archive.org/details/iacl Internet Archive Children's Library] Good source of illustrated books in several formats. DejaVu format is recommended.

*[http://www.gutenberg.org/wiki/Category:Children%27s_Bookshelf Project Gutenberg Children's Bookshelf] Mostly plain text books which can be read with the Read Etexts activity.

*[http://www.baen.com/library/ Baen Free Library] Current and classic science fiction books which can be read online using Browse or downloaded in RTF format and read with Read Etexts. Most of the titles are suitable for older children.

*[http://craphound.com/littlebrother/download/ Little Brother] An excellent young adult science fiction novel that can be downloaded for free. EPUB, Plain Text, PDF, and XO library bundle versions are available.

Sugar on a Stick/E-Books

2009-12-02T15:52:44Z

Jdsimmons:

Activities/Read Etexts

2009-10-07T22:29:29Z

Jdsimmons: /* The Baen Free Library */

== Description & Goals==

''"Outside of a dog, a book is man's best friend. Inside of a dog it's too dark to read."'' -- Groucho Marx

The Read Etexts activity is meant to allow the XO laptop to read Project Gutenberg ETexts, which are plain text files. The original goal of this Activity was to create a stopgap for reading plain text files until the core Read activity was able to do that. Read Etexts has become much more than that, adding features that core Read does not have, like text to speech with word highlighting, and most recently the ability to search the Project Gutenberg offline catalog and download books.

Since the [http://manybooks.net/ ManyBooks.net] website offers Project Gutenberg titles as PDFs you might wonder why you would need an Activity to read plain text files. It is a matter of personal preference. If you have a choice between a text file and a PDF, you may find that the text file is easier on the eyes than a PDF, takes up less space in the Journal (especially in zip format), and uses less memory to read. You will also find that the offline catalog search (Books tab) is a really convenient way to download books.

The interface to Read Etexts is very similar to the core Read activity, which should not be surprising as the toolbar code was adapted from Read's toolbar. You can use the up and down arrows or the game controller to scroll pages, and the '+' and '-' keys to adjust the font size. Use Page Up and Page Down to move to the previous and next pages respectively.

[http://www.gutenberg.org/wiki/Main_Page Project Gutenberg] is a website where you can download thousands of public domain books for free. There are books for every interest: classics, history, childen's novels, science fiction, and much, much more. [http://www.gutenberg.org/browse/loccs/pz Browse By Library of Congress Class: Language and Literatures: Juvenile belles lettres] will give you a list of books suitable for young readers.

Read ETexts can read books in plain text format or in Zip format. These are by far the most popular formats on the Gutenberg website. If for some reason you cannot use the Catalog search to get a book you can also download books from the website using the Browse activity. You should download one of the Zip file formats. These can be encoded as us-ascii text or as iso-8859-1; Read Etexts can handle either one. The iso-8859-1 encoding is used for books that need accent marks, etc. Save the Zip file to the Journal, change the Journal entry name to match the title of the book, and then resume it using the Read Etexts option on the Resume menu. See the first screenshot.

== Current Features ==

* Currently Read Etexts can be used to read Gutenberg Etexts, either as text files or as zip files containing one text file. The toolbars include Activity, Read (skip to page), Edit (copy to clipboard, search for text) and View (zoom text bigger or smaller). The Books toolbar comes up if you launch Read Etexts from the Activity ring. This toolbar supports searching the Project Gutenberg offline catalog and downloading books.
* Book sharing is supported.
* The power management code from the core Read activity has been added, with a few minor changes, and seems to work OK.
* Text to speech with Karaoke highlighting. The purpose of this is to produce a tool to help someone learn to read. Support for text to speech on the XO laptop is done using a gstreamer plugin for espeak. This plugin currently is not part of the software included on the XO, but is installed on Sugar on a Stick. You do '''not''' need this plugin installed to use Read Etexts, but you will of course not have text to speech working unless you do.
* The Books toolbar lets you search for books in Project Gutenberg's offline catalog. Enter in words that you would expect to find in the title or author of a book, then press Enter. A table will appear in the lower half of the screen listing book titles and authors that contain all of the words. Select a book from that table and click the download button and the book will arrive in a minute or so. The download tries to get the best available version of the book. For instance, it will try to download an 8 bit version of the book, and if there is none it will try to get a 7 bit version. (8 bit files contain accents and diacritical marks; the 7 bit versions do not. Not every text has both versions).
* You can download several books to the Journal in one session. Each book will be given a Journal entry when it downloads.
* The Activity has an annotation feature that enables the user to attach notes to pages in the text. These annotations are stored in a pickle file that is included in the Zip file containing the document. When you share a document your annotations will go along with it. For the recipient it will be sort of like buying a used textbook that has all the important stuff already marked up.
* The Activity supports multiple bookmarks in a document, and easy navigating between them. This is in addition to the current feature that remembers where you left off when you last read a document.
* The Activity supports highlightings passages in text. The highlight is shown as a yellow background (like a hi-lighter pen would make) plus a single underline. You can highlight multiple passages on a page.
* Word wrap is supported for those text documents that require it. Read Etexts considers a line of text to be no more than 80 characters, so a page break is calculated based on how many 80 character strings will fit in the paragraphs, plus one. A page will not break in the middle of a paragraph, so not every page is the same number of lines.
* With version 17 you can now read texts from the Baen Free Library in the Rich Text Format (RTF). Read Etexts will automatically convert RTF documents to plain text format for reading.

== Using Text to Speech ==

Read Etexts uses software called gstreamer espeak plugin to read text aloud and to perform callbacks which enable the word being spoken to be highlighted. This plugin is not yet included with the normal XO software distribution, but is included in Sugar on a Stick.

To start text to speech you simply press the check mark button on the XO's display (Numeric Keypad "End" on a standard keyboard). This button will also pause and resume speech. Only the current page will be spoken, and always starting from the first word on the page unless you are resuming after pausing. You need to have the text control containing the text to be spoken in focus. I use the check button because you can use it when the XO is folded into its ebook reader configuration. There is also a Play/Pause button on the Speech tab of the toolbar that you can use instead.

If your system does not have the needed software to support text to speech you will ''not'' see the Speech tool bar. This is intentional.

The toolbar is very much like the one in the Speak activity and was adapted from its code. It allows you to change the language, pitch, and rate of speech. You can only do this while the Activity is not speaking. You can pause the speech, change its rate, pitch,or language, and then resume.

== Sharing Documents ==

This activity uses code adapted from the core Read activity for document sharing over the network. To share a document with someone that person must also have the Read Etexts activity installed, and it should be the same version for best results. You can invite an individual to join the activity or share it with the whole neighborhood, but either way only those who have the activity installed will see the invitation.

When someone accepts the invitation to join the activity a copy of the document is sent to his computer for him to read. When he exits the activity the document will be saved in the journal.

== The Baen Free Library ==

The [http://www.baen.com/library/ Baen Free Library] is a website from Baen Books that publishes free etexts of some of their books with the idea that this will ultimately increase sales of the printed editions. So far it seems to be working. Unfortunately, the formats they offer for downloading are not currently supported by any reading Activity for Sugar. The closest thing to a supported format is RTF (Rich Text Format) which you can load into the Write Activity. Write is a poor choice for reading etexts, unfortunately.

Version 17 of Read Etexts solves this problem by converting RTF to a plain text file automatically. So now, in addition to the great classics of literature by dead authors that Project Gutenberg gives you you can also read fairly current science fiction from Baen Books.

You can use the Browse Activity to download RTF files from the site. Be sure to choose the RTF file, not the zipped up RTF file. The zipped version ''should'' work, but the website does something to it that keeps it from getting a proper MIME type. I was able to use Browse on my XO running Sugar .82 to download RTFs. If Browse doesn't work for you an alternative is to use another computer to download the file to a thumb drive, then copy that file from the thumb drive to the Journal.

When you Restore the file for the first time be sure to do it with Read Etexts, ''not'' Write. Write does something to the file that prevents Read Etexts from being able to convert it properly. Once you open it with Read Etexts it will be given the Read Etexts icon and will open with the correct Activity by default.

I'm dedicating this feature to the author Howard L. Myers. His book ''The Creatures of Man'' is available for download from the website. Back in 1974 I was graduating from High School and subscribing to ''Galaxy'' magazine. ''Galaxy'' ran a couple of cracking good yarns by Myers, writing as "Verge Foray", in the May and June issues. I was really looking forward to more in the series, and even wrote an incoherent letter to the magazine asking for more Verge Foray stories. I only found out this year why no more stories ever came. Howard L. Myers had died in 1971.

== Planned Features ==

* All planned features have been implemented. All that remains are bug fixes.

== Bugs ==

* Text to speech does not work perfectly. The gstreamer plugin combined with newer versions of espeak works much better than the original speech-dispatcher code did, but in Sugar on a Stick on ''some'' machines the text highlighting lags badly behind the spoken words.

== Source ==

http://git.sugarlabs.org/projects/readetexts

== The Movie! ==

See the future of reading, here today, by watching [http://www.dailymotion.com/video/xa4bhu_readetexts-the-movie_tech Read Etexts: The Movie].

''"You are interested in the future, because it is where we will spend the rest of our lives. And remember my friends, future events such as these will affect you in the future."'' -- Edward D. Wood

[[Category:Activities]]

Activities/Read Etexts

2009-10-07T22:27:51Z

Jdsimmons: /* Sharing Documents */

== Description & Goals==

''"Outside of a dog, a book is man's best friend. Inside of a dog it's too dark to read."'' -- Groucho Marx

The Read Etexts activity is meant to allow the XO laptop to read Project Gutenberg ETexts, which are plain text files. The original goal of this Activity was to create a stopgap for reading plain text files until the core Read activity was able to do that. Read Etexts has become much more than that, adding features that core Read does not have, like text to speech with word highlighting, and most recently the ability to search the Project Gutenberg offline catalog and download books.

Since the [http://manybooks.net/ ManyBooks.net] website offers Project Gutenberg titles as PDFs you might wonder why you would need an Activity to read plain text files. It is a matter of personal preference. If you have a choice between a text file and a PDF, you may find that the text file is easier on the eyes than a PDF, takes up less space in the Journal (especially in zip format), and uses less memory to read. You will also find that the offline catalog search (Books tab) is a really convenient way to download books.

The interface to Read Etexts is very similar to the core Read activity, which should not be surprising as the toolbar code was adapted from Read's toolbar. You can use the up and down arrows or the game controller to scroll pages, and the '+' and '-' keys to adjust the font size. Use Page Up and Page Down to move to the previous and next pages respectively.

[http://www.gutenberg.org/wiki/Main_Page Project Gutenberg] is a website where you can download thousands of public domain books for free. There are books for every interest: classics, history, childen's novels, science fiction, and much, much more. [http://www.gutenberg.org/browse/loccs/pz Browse By Library of Congress Class: Language and Literatures: Juvenile belles lettres] will give you a list of books suitable for young readers.

Read ETexts can read books in plain text format or in Zip format. These are by far the most popular formats on the Gutenberg website. If for some reason you cannot use the Catalog search to get a book you can also download books from the website using the Browse activity. You should download one of the Zip file formats. These can be encoded as us-ascii text or as iso-8859-1; Read Etexts can handle either one. The iso-8859-1 encoding is used for books that need accent marks, etc. Save the Zip file to the Journal, change the Journal entry name to match the title of the book, and then resume it using the Read Etexts option on the Resume menu. See the first screenshot.

== Current Features ==

* Currently Read Etexts can be used to read Gutenberg Etexts, either as text files or as zip files containing one text file. The toolbars include Activity, Read (skip to page), Edit (copy to clipboard, search for text) and View (zoom text bigger or smaller). The Books toolbar comes up if you launch Read Etexts from the Activity ring. This toolbar supports searching the Project Gutenberg offline catalog and downloading books.
* Book sharing is supported.
* The power management code from the core Read activity has been added, with a few minor changes, and seems to work OK.
* Text to speech with Karaoke highlighting. The purpose of this is to produce a tool to help someone learn to read. Support for text to speech on the XO laptop is done using a gstreamer plugin for espeak. This plugin currently is not part of the software included on the XO, but is installed on Sugar on a Stick. You do '''not''' need this plugin installed to use Read Etexts, but you will of course not have text to speech working unless you do.
* The Books toolbar lets you search for books in Project Gutenberg's offline catalog. Enter in words that you would expect to find in the title or author of a book, then press Enter. A table will appear in the lower half of the screen listing book titles and authors that contain all of the words. Select a book from that table and click the download button and the book will arrive in a minute or so. The download tries to get the best available version of the book. For instance, it will try to download an 8 bit version of the book, and if there is none it will try to get a 7 bit version. (8 bit files contain accents and diacritical marks; the 7 bit versions do not. Not every text has both versions).
* You can download several books to the Journal in one session. Each book will be given a Journal entry when it downloads.
* The Activity has an annotation feature that enables the user to attach notes to pages in the text. These annotations are stored in a pickle file that is included in the Zip file containing the document. When you share a document your annotations will go along with it. For the recipient it will be sort of like buying a used textbook that has all the important stuff already marked up.
* The Activity supports multiple bookmarks in a document, and easy navigating between them. This is in addition to the current feature that remembers where you left off when you last read a document.
* The Activity supports highlightings passages in text. The highlight is shown as a yellow background (like a hi-lighter pen would make) plus a single underline. You can highlight multiple passages on a page.
* Word wrap is supported for those text documents that require it. Read Etexts considers a line of text to be no more than 80 characters, so a page break is calculated based on how many 80 character strings will fit in the paragraphs, plus one. A page will not break in the middle of a paragraph, so not every page is the same number of lines.
* With version 17 you can now read texts from the Baen Free Library in the Rich Text Format (RTF). Read Etexts will automatically convert RTF documents to plain text format for reading.

== Using Text to Speech ==

Read Etexts uses software called gstreamer espeak plugin to read text aloud and to perform callbacks which enable the word being spoken to be highlighted. This plugin is not yet included with the normal XO software distribution, but is included in Sugar on a Stick.

To start text to speech you simply press the check mark button on the XO's display (Numeric Keypad "End" on a standard keyboard). This button will also pause and resume speech. Only the current page will be spoken, and always starting from the first word on the page unless you are resuming after pausing. You need to have the text control containing the text to be spoken in focus. I use the check button because you can use it when the XO is folded into its ebook reader configuration. There is also a Play/Pause button on the Speech tab of the toolbar that you can use instead.

If your system does not have the needed software to support text to speech you will ''not'' see the Speech tool bar. This is intentional.

The toolbar is very much like the one in the Speak activity and was adapted from its code. It allows you to change the language, pitch, and rate of speech. You can only do this while the Activity is not speaking. You can pause the speech, change its rate, pitch,or language, and then resume.

== Sharing Documents ==

This activity uses code adapted from the core Read activity for document sharing over the network. To share a document with someone that person must also have the Read Etexts activity installed, and it should be the same version for best results. You can invite an individual to join the activity or share it with the whole neighborhood, but either way only those who have the activity installed will see the invitation.

When someone accepts the invitation to join the activity a copy of the document is sent to his computer for him to read. When he exits the activity the document will be saved in the journal.

== The Baen Free Library ==

The [http://www.baen.com/library/ Baen Free Library] is a website from Baen Books that publishes free etexts of some of their books with the idea that this will ultimately increase sales of the printed editions. So far it seems to be working. Unfortunately, the formats they offer for downloading are not currently supported by any reading Activity for Sugar. The closest thing to a supported format is RTF (Rich Text Format) which you can load into the Write Activity. Write is a poor choice for reading etexts, unfortunately.

Version 17 of Read Etexts solves this problem by converting RTF to a plain text file automatically. So now, in addition to the great classics of literature by dead authors that Project Gutenberg gives you you can also read fairly current science fiction from Baen Books.

You can use the Browse Activity to download RTF files from the site. Be sure to choose the RTF file, not the zipped up RTF file. The zipped version ''should'' work, but the website does something to it that keeps it from getting a proper MIME type. I was able to use Browse on my XO running Sugar .82 to download RTFs. If Browse doesn't work for you an alternative is to use another computer to download the file to a thumb drive.

When you restore the file for the first time be sure to do it with Read Etexts, ''not'' Write. Write does something to the file that prevents Read Etexts from being able to convert it properly. Once you open it with Read Etexts it will be given the Read Etexts icon and will open with the correct Activity by default.

I'm dedicating this feature to the author Howard L. Myers. His book ''The Creatures of Man'' is available for download from the website. Back in 1974 I was graduating from High School and subscribing to ''Galaxy'' magazine. ''Galaxy'' ran a couple of cracking good yarns by Myers, writing as "Verge Foray", in the May and June issues. I was really looking forward to more in the series, and even wrote an incoherent letter to the magazine asking for more Verge Foray stories. I only found out this year why no more stories ever came. Howard L. Myers had died in 1971.

== Planned Features ==

* All planned features have been implemented. All that remains are bug fixes.

== Bugs ==

* Text to speech does not work perfectly. The gstreamer plugin combined with newer versions of espeak works much better than the original speech-dispatcher code did, but in Sugar on a Stick on ''some'' machines the text highlighting lags badly behind the spoken words.

== Source ==

http://git.sugarlabs.org/projects/readetexts

== The Movie! ==

See the future of reading, here today, by watching [http://www.dailymotion.com/video/xa4bhu_readetexts-the-movie_tech Read Etexts: The Movie].

''"You are interested in the future, because it is where we will spend the rest of our lives. And remember my friends, future events such as these will affect you in the future."'' -- Edward D. Wood

[[Category:Activities]]

Activities/Read Etexts

2009-10-07T22:26:59Z

Jdsimmons: /* Using Text to Speech */

== Description & Goals==

''"Outside of a dog, a book is man's best friend. Inside of a dog it's too dark to read."'' -- Groucho Marx

The Read Etexts activity is meant to allow the XO laptop to read Project Gutenberg ETexts, which are plain text files. The original goal of this Activity was to create a stopgap for reading plain text files until the core Read activity was able to do that. Read Etexts has become much more than that, adding features that core Read does not have, like text to speech with word highlighting, and most recently the ability to search the Project Gutenberg offline catalog and download books.

Since the [http://manybooks.net/ ManyBooks.net] website offers Project Gutenberg titles as PDFs you might wonder why you would need an Activity to read plain text files. It is a matter of personal preference. If you have a choice between a text file and a PDF, you may find that the text file is easier on the eyes than a PDF, takes up less space in the Journal (especially in zip format), and uses less memory to read. You will also find that the offline catalog search (Books tab) is a really convenient way to download books.

The interface to Read Etexts is very similar to the core Read activity, which should not be surprising as the toolbar code was adapted from Read's toolbar. You can use the up and down arrows or the game controller to scroll pages, and the '+' and '-' keys to adjust the font size. Use Page Up and Page Down to move to the previous and next pages respectively.

[http://www.gutenberg.org/wiki/Main_Page Project Gutenberg] is a website where you can download thousands of public domain books for free. There are books for every interest: classics, history, childen's novels, science fiction, and much, much more. [http://www.gutenberg.org/browse/loccs/pz Browse By Library of Congress Class: Language and Literatures: Juvenile belles lettres] will give you a list of books suitable for young readers.

Read ETexts can read books in plain text format or in Zip format. These are by far the most popular formats on the Gutenberg website. If for some reason you cannot use the Catalog search to get a book you can also download books from the website using the Browse activity. You should download one of the Zip file formats. These can be encoded as us-ascii text or as iso-8859-1; Read Etexts can handle either one. The iso-8859-1 encoding is used for books that need accent marks, etc. Save the Zip file to the Journal, change the Journal entry name to match the title of the book, and then resume it using the Read Etexts option on the Resume menu. See the first screenshot.

== Current Features ==

* Currently Read Etexts can be used to read Gutenberg Etexts, either as text files or as zip files containing one text file. The toolbars include Activity, Read (skip to page), Edit (copy to clipboard, search for text) and View (zoom text bigger or smaller). The Books toolbar comes up if you launch Read Etexts from the Activity ring. This toolbar supports searching the Project Gutenberg offline catalog and downloading books.
* Book sharing is supported.
* The power management code from the core Read activity has been added, with a few minor changes, and seems to work OK.
* Text to speech with Karaoke highlighting. The purpose of this is to produce a tool to help someone learn to read. Support for text to speech on the XO laptop is done using a gstreamer plugin for espeak. This plugin currently is not part of the software included on the XO, but is installed on Sugar on a Stick. You do '''not''' need this plugin installed to use Read Etexts, but you will of course not have text to speech working unless you do.
* The Books toolbar lets you search for books in Project Gutenberg's offline catalog. Enter in words that you would expect to find in the title or author of a book, then press Enter. A table will appear in the lower half of the screen listing book titles and authors that contain all of the words. Select a book from that table and click the download button and the book will arrive in a minute or so. The download tries to get the best available version of the book. For instance, it will try to download an 8 bit version of the book, and if there is none it will try to get a 7 bit version. (8 bit files contain accents and diacritical marks; the 7 bit versions do not. Not every text has both versions).
* You can download several books to the Journal in one session. Each book will be given a Journal entry when it downloads.
* The Activity has an annotation feature that enables the user to attach notes to pages in the text. These annotations are stored in a pickle file that is included in the Zip file containing the document. When you share a document your annotations will go along with it. For the recipient it will be sort of like buying a used textbook that has all the important stuff already marked up.
* The Activity supports multiple bookmarks in a document, and easy navigating between them. This is in addition to the current feature that remembers where you left off when you last read a document.
* The Activity supports highlightings passages in text. The highlight is shown as a yellow background (like a hi-lighter pen would make) plus a single underline. You can highlight multiple passages on a page.
* Word wrap is supported for those text documents that require it. Read Etexts considers a line of text to be no more than 80 characters, so a page break is calculated based on how many 80 character strings will fit in the paragraphs, plus one. A page will not break in the middle of a paragraph, so not every page is the same number of lines.
* With version 17 you can now read texts from the Baen Free Library in the Rich Text Format (RTF). Read Etexts will automatically convert RTF documents to plain text format for reading.

== Using Text to Speech ==

Read Etexts uses software called gstreamer espeak plugin to read text aloud and to perform callbacks which enable the word being spoken to be highlighted. This plugin is not yet included with the normal XO software distribution, but is included in Sugar on a Stick.

To start text to speech you simply press the check mark button on the XO's display (Numeric Keypad "End" on a standard keyboard). This button will also pause and resume speech. Only the current page will be spoken, and always starting from the first word on the page unless you are resuming after pausing. You need to have the text control containing the text to be spoken in focus. I use the check button because you can use it when the XO is folded into its ebook reader configuration. There is also a Play/Pause button on the Speech tab of the toolbar that you can use instead.

If your system does not have the needed software to support text to speech you will ''not'' see the Speech tool bar. This is intentional.

The toolbar is very much like the one in the Speak activity and was adapted from its code. It allows you to change the language, pitch, and rate of speech. You can only do this while the Activity is not speaking. You can pause the speech, change its rate, pitch,or language, and then resume.

== Sharing Documents ==

This activity uses code adapted from the core Read activity for document sharing over the network. To share a document with someone that person must also have the Read Etexts activity installed, and it should be the same version for best results. You can invite an individual to join the activity or share it with the whole neighborhood, but either way only those who have the activity installed will see the invitation.

When someone accepts the invitation to join the activity a copy of the document is sent to his computer for him to read. When he exits the activity the document will be saved in the journal. The Journal entry will be titled "Read Etexts Activity", not the title of the book. Of course the recipient can modify this title to match the actual title of the book, but the activity currently will not do this for her.

This is a bit different from the core Read activity because I actually save a copy of the received document in the Journal, whereas Read does not. If you try to resume a shared Read activity when the document is not currently being shared you will get an empty document.

== The Baen Free Library ==

The [http://www.baen.com/library/ Baen Free Library] is a website from Baen Books that publishes free etexts of some of their books with the idea that this will ultimately increase sales of the printed editions. So far it seems to be working. Unfortunately, the formats they offer for downloading are not currently supported by any reading Activity for Sugar. The closest thing to a supported format is RTF (Rich Text Format) which you can load into the Write Activity. Write is a poor choice for reading etexts, unfortunately.

Version 17 of Read Etexts solves this problem by converting RTF to a plain text file automatically. So now, in addition to the great classics of literature by dead authors that Project Gutenberg gives you you can also read fairly current science fiction from Baen Books.

You can use the Browse Activity to download RTF files from the site. Be sure to choose the RTF file, not the zipped up RTF file. The zipped version ''should'' work, but the website does something to it that keeps it from getting a proper MIME type. I was able to use Browse on my XO running Sugar .82 to download RTFs. If Browse doesn't work for you an alternative is to use another computer to download the file to a thumb drive.

When you restore the file for the first time be sure to do it with Read Etexts, ''not'' Write. Write does something to the file that prevents Read Etexts from being able to convert it properly. Once you open it with Read Etexts it will be given the Read Etexts icon and will open with the correct Activity by default.

I'm dedicating this feature to the author Howard L. Myers. His book ''The Creatures of Man'' is available for download from the website. Back in 1974 I was graduating from High School and subscribing to ''Galaxy'' magazine. ''Galaxy'' ran a couple of cracking good yarns by Myers, writing as "Verge Foray", in the May and June issues. I was really looking forward to more in the series, and even wrote an incoherent letter to the magazine asking for more Verge Foray stories. I only found out this year why no more stories ever came. Howard L. Myers had died in 1971.

== Planned Features ==

* All planned features have been implemented. All that remains are bug fixes.

== Bugs ==

* Text to speech does not work perfectly. The gstreamer plugin combined with newer versions of espeak works much better than the original speech-dispatcher code did, but in Sugar on a Stick on ''some'' machines the text highlighting lags badly behind the spoken words.

== Source ==

http://git.sugarlabs.org/projects/readetexts

== The Movie! ==

See the future of reading, here today, by watching [http://www.dailymotion.com/video/xa4bhu_readetexts-the-movie_tech Read Etexts: The Movie].

''"You are interested in the future, because it is where we will spend the rest of our lives. And remember my friends, future events such as these will affect you in the future."'' -- Edward D. Wood

[[Category:Activities]]

Activities/Read Etexts

2009-09-07T20:20:43Z

Jdsimmons: /* The Baen Free Library */

== Description & Goals==

''"Outside of a dog, a book is man's best friend. Inside of a dog it's too dark to read."'' -- Groucho Marx

The Read Etexts activity is meant to allow the XO laptop to read Project Gutenberg ETexts, which are plain text files. The original goal of this Activity was to create a stopgap for reading plain text files until the core Read activity was able to do that. Read Etexts has become much more than that, adding features that core Read does not have, like text to speech with word highlighting, and most recently the ability to search the Project Gutenberg offline catalog and download books.

Since the [http://manybooks.net/ ManyBooks.net] website offers Project Gutenberg titles as PDFs you might wonder why you would need an Activity to read plain text files. It is a matter of personal preference. If you have a choice between a text file and a PDF, you may find that the text file is easier on the eyes than a PDF, takes up less space in the Journal (especially in zip format), and uses less memory to read. You will also find that the offline catalog search (Books tab) is a really convenient way to download books.

The interface to Read Etexts is very similar to the core Read activity, which should not be surprising as the toolbar code was adapted from Read's toolbar. You can use the up and down arrows or the game controller to scroll pages, and the '+' and '-' keys to adjust the font size. Use Page Up and Page Down to move to the previous and next pages respectively.

[http://www.gutenberg.org/wiki/Main_Page Project Gutenberg] is a website where you can download thousands of public domain books for free. There are books for every interest: classics, history, childen's novels, science fiction, and much, much more. [http://www.gutenberg.org/browse/loccs/pz Browse By Library of Congress Class: Language and Literatures: Juvenile belles lettres] will give you a list of books suitable for young readers.

Read ETexts can read books in plain text format or in Zip format. These are by far the most popular formats on the Gutenberg website. If for some reason you cannot use the Catalog search to get a book you can also download books from the website using the Browse activity. You should download one of the Zip file formats. These can be encoded as us-ascii text or as iso-8859-1; Read Etexts can handle either one. The iso-8859-1 encoding is used for books that need accent marks, etc. Save the Zip file to the Journal, change the Journal entry name to match the title of the book, and then resume it using the Read Etexts option on the Resume menu. See the first screenshot.

== Current Features ==

* Currently Read Etexts can be used to read Gutenberg Etexts, either as text files or as zip files containing one text file. The toolbars include Activity, Read (skip to page), Edit (copy to clipboard, search for text) and View (zoom text bigger or smaller). The Books toolbar comes up if you launch Read Etexts from the Activity ring. This toolbar supports searching the Project Gutenberg offline catalog and downloading books.
* Book sharing is supported.
* The power management code from the core Read activity has been added, with a few minor changes, and seems to work OK.
* Text to speech with Karaoke highlighting. The purpose of this is to produce a tool to help someone learn to read. Support for text to speech on the XO laptop is done using a gstreamer plugin for espeak. This plugin currently is not part of the software included on the XO, but is installed on Sugar on a Stick. You do '''not''' need this plugin installed to use Read Etexts, but you will of course not have text to speech working unless you do.
* The Books toolbar lets you search for books in Project Gutenberg's offline catalog. Enter in words that you would expect to find in the title or author of a book, then press Enter. A table will appear in the lower half of the screen listing book titles and authors that contain all of the words. Select a book from that table and click the download button and the book will arrive in a minute or so. The download tries to get the best available version of the book. For instance, it will try to download an 8 bit version of the book, and if there is none it will try to get a 7 bit version. (8 bit files contain accents and diacritical marks; the 7 bit versions do not. Not every text has both versions).
* You can download several books to the Journal in one session. Each book will be given a Journal entry when it downloads.
* The Activity has an annotation feature that enables the user to attach notes to pages in the text. These annotations are stored in a pickle file that is included in the Zip file containing the document. When you share a document your annotations will go along with it. For the recipient it will be sort of like buying a used textbook that has all the important stuff already marked up.
* The Activity supports multiple bookmarks in a document, and easy navigating between them. This is in addition to the current feature that remembers where you left off when you last read a document.
* The Activity supports highlightings passages in text. The highlight is shown as a yellow background (like a hi-lighter pen would make) plus a single underline. You can highlight multiple passages on a page.
* Word wrap is supported for those text documents that require it. Read Etexts considers a line of text to be no more than 80 characters, so a page break is calculated based on how many 80 character strings will fit in the paragraphs, plus one. A page will not break in the middle of a paragraph, so not every page is the same number of lines.
* With version 17 you can now read texts from the Baen Free Library in the Rich Text Format (RTF). Read Etexts will automatically convert RTF documents to plain text format for reading.

== Using Text to Speech ==

Read Etexts uses software called Speech Dispatcher to read text aloud and to perform callbacks which enable the word being spoken to be highlighted. Speech Dispatcher is not yet included with the normal XO software distribution, but will be included in version .84.

To start text to speech you simply press the check mark button on the XO's display (Numeric Keypad "End" on a standard keyboard). This button will also pause and resume speech. Only the current page will be spoken, and always starting from the first word on the page unless you are resuming after pausing. You need to have the text control containing the text to be spoken in focus. I use the check button because you can use it when the XO is folded into its ebook reader configuration. There is also a Play/Pause button on the Speech tab of the toolbar that you can use instead.

If your system does not have the needed software to support text to speech you will ''not'' see the Speech tool bar. This is intentional.

The toolbar is very much like the one in the Speak activity and was adapted from its code. It allows you to change the language, pitch, and rate of speech. You can only do this while the Activity is not speaking. You can pause the speech, change its rate, pitch,or language, and then resume.

The latest version of Read Etexts supports either speech-dispatcher or the gstreamer espeak plugin developed by Aleksey Lim for the Sugar project. This plugin should be part of Sugar on a Stick and future releases of Sugar for the XO. This plugin works much better than speech-dispatcher does and does not require running a demon program or doing any configuration.

== Sharing Documents ==

This activity uses code adapted from the core Read activity for document sharing over the network. To share a document with someone that person must also have the Read Etexts activity installed, and it should be the same version for best results. You can invite an individual to join the activity or share it with the whole neighborhood, but either way only those who have the activity installed will see the invitation.

When someone accepts the invitation to join the activity a copy of the document is sent to his computer for him to read. When he exits the activity the document will be saved in the journal. The Journal entry will be titled "Read Etexts Activity", not the title of the book. Of course the recipient can modify this title to match the actual title of the book, but the activity currently will not do this for her.

This is a bit different from the core Read activity because I actually save a copy of the received document in the Journal, whereas Read does not. If you try to resume a shared Read activity when the document is not currently being shared you will get an empty document.

== The Baen Free Library ==

The [http://www.baen.com/library/ Baen Free Library] is a website from Baen Books that publishes free etexts of some of their books with the idea that this will ultimately increase sales of the printed editions. So far it seems to be working. Unfortunately, the formats they offer for downloading are not currently supported by any reading Activity for Sugar. The closest thing to a supported format is RTF (Rich Text Format) which you can load into the Write Activity. Write is a poor choice for reading etexts, unfortunately.

Version 17 of Read Etexts solves this problem by converting RTF to a plain text file automatically. So now, in addition to the great classics of literature by dead authors that Project Gutenberg gives you you can also read fairly current science fiction from Baen Books.

You can use the Browse Activity to download RTF files from the site. Be sure to choose the RTF file, not the zipped up RTF file. The zipped version ''should'' work, but the website does something to it that keeps it from getting a proper MIME type. I was able to use Browse on my XO running Sugar .82 to download RTFs. If Browse doesn't work for you an alternative is to use another computer to download the file to a thumb drive.

When you restore the file for the first time be sure to do it with Read Etexts, ''not'' Write. Write does something to the file that prevents Read Etexts from being able to convert it properly. Once you open it with Read Etexts it will be given the Read Etexts icon and will open with the correct Activity by default.

I'm dedicating this feature to the author Howard L. Myers. His book ''The Creatures of Man'' is available for download from the website. Back in 1974 I was graduating from High School and subscribing to ''Galaxy'' magazine. ''Galaxy'' ran a couple of cracking good yarns by Myers, writing as "Verge Foray", in the May and June issues. I was really looking forward to more in the series, and even wrote an incoherent letter to the magazine asking for more Verge Foray stories. I only found out this year why no more stories ever came. Howard L. Myers had died in 1971.

== Planned Features ==

* All planned features have been implemented. All that remains are bug fixes.

== Bugs ==

* Text to speech does not work perfectly. The gstreamer plugin combined with newer versions of espeak works much better than the original speech-dispatcher code did, but in Sugar on a Stick on ''some'' machines the text highlighting lags badly behind the spoken words.

== Source ==

http://git.sugarlabs.org/projects/readetexts

== The Movie! ==

See the future of reading, here today, by watching [http://www.dailymotion.com/video/xa4bhu_readetexts-the-movie_tech Read Etexts: The Movie].

''"You are interested in the future, because it is where we will spend the rest of our lives. And remember my friends, future events such as these will affect you in the future."'' -- Edward D. Wood

[[Category:Activities]]

Activities/Read Etexts

2009-09-07T20:09:55Z

Jdsimmons: /* Sharing Documents */

== Description & Goals==

''"Outside of a dog, a book is man's best friend. Inside of a dog it's too dark to read."'' -- Groucho Marx

The Read Etexts activity is meant to allow the XO laptop to read Project Gutenberg ETexts, which are plain text files. The original goal of this Activity was to create a stopgap for reading plain text files until the core Read activity was able to do that. Read Etexts has become much more than that, adding features that core Read does not have, like text to speech with word highlighting, and most recently the ability to search the Project Gutenberg offline catalog and download books.

Since the [http://manybooks.net/ ManyBooks.net] website offers Project Gutenberg titles as PDFs you might wonder why you would need an Activity to read plain text files. It is a matter of personal preference. If you have a choice between a text file and a PDF, you may find that the text file is easier on the eyes than a PDF, takes up less space in the Journal (especially in zip format), and uses less memory to read. You will also find that the offline catalog search (Books tab) is a really convenient way to download books.

The interface to Read Etexts is very similar to the core Read activity, which should not be surprising as the toolbar code was adapted from Read's toolbar. You can use the up and down arrows or the game controller to scroll pages, and the '+' and '-' keys to adjust the font size. Use Page Up and Page Down to move to the previous and next pages respectively.

[http://www.gutenberg.org/wiki/Main_Page Project Gutenberg] is a website where you can download thousands of public domain books for free. There are books for every interest: classics, history, childen's novels, science fiction, and much, much more. [http://www.gutenberg.org/browse/loccs/pz Browse By Library of Congress Class: Language and Literatures: Juvenile belles lettres] will give you a list of books suitable for young readers.

Read ETexts can read books in plain text format or in Zip format. These are by far the most popular formats on the Gutenberg website. If for some reason you cannot use the Catalog search to get a book you can also download books from the website using the Browse activity. You should download one of the Zip file formats. These can be encoded as us-ascii text or as iso-8859-1; Read Etexts can handle either one. The iso-8859-1 encoding is used for books that need accent marks, etc. Save the Zip file to the Journal, change the Journal entry name to match the title of the book, and then resume it using the Read Etexts option on the Resume menu. See the first screenshot.

== Current Features ==

* Currently Read Etexts can be used to read Gutenberg Etexts, either as text files or as zip files containing one text file. The toolbars include Activity, Read (skip to page), Edit (copy to clipboard, search for text) and View (zoom text bigger or smaller). The Books toolbar comes up if you launch Read Etexts from the Activity ring. This toolbar supports searching the Project Gutenberg offline catalog and downloading books.
* Book sharing is supported.
* The power management code from the core Read activity has been added, with a few minor changes, and seems to work OK.
* Text to speech with Karaoke highlighting. The purpose of this is to produce a tool to help someone learn to read. Support for text to speech on the XO laptop is done using a gstreamer plugin for espeak. This plugin currently is not part of the software included on the XO, but is installed on Sugar on a Stick. You do '''not''' need this plugin installed to use Read Etexts, but you will of course not have text to speech working unless you do.
* The Books toolbar lets you search for books in Project Gutenberg's offline catalog. Enter in words that you would expect to find in the title or author of a book, then press Enter. A table will appear in the lower half of the screen listing book titles and authors that contain all of the words. Select a book from that table and click the download button and the book will arrive in a minute or so. The download tries to get the best available version of the book. For instance, it will try to download an 8 bit version of the book, and if there is none it will try to get a 7 bit version. (8 bit files contain accents and diacritical marks; the 7 bit versions do not. Not every text has both versions).
* You can download several books to the Journal in one session. Each book will be given a Journal entry when it downloads.
* The Activity has an annotation feature that enables the user to attach notes to pages in the text. These annotations are stored in a pickle file that is included in the Zip file containing the document. When you share a document your annotations will go along with it. For the recipient it will be sort of like buying a used textbook that has all the important stuff already marked up.
* The Activity supports multiple bookmarks in a document, and easy navigating between them. This is in addition to the current feature that remembers where you left off when you last read a document.
* The Activity supports highlightings passages in text. The highlight is shown as a yellow background (like a hi-lighter pen would make) plus a single underline. You can highlight multiple passages on a page.
* Word wrap is supported for those text documents that require it. Read Etexts considers a line of text to be no more than 80 characters, so a page break is calculated based on how many 80 character strings will fit in the paragraphs, plus one. A page will not break in the middle of a paragraph, so not every page is the same number of lines.
* With version 17 you can now read texts from the Baen Free Library in the Rich Text Format (RTF). Read Etexts will automatically convert RTF documents to plain text format for reading.

== Using Text to Speech ==

Read Etexts uses software called Speech Dispatcher to read text aloud and to perform callbacks which enable the word being spoken to be highlighted. Speech Dispatcher is not yet included with the normal XO software distribution, but will be included in version .84.

To start text to speech you simply press the check mark button on the XO's display (Numeric Keypad "End" on a standard keyboard). This button will also pause and resume speech. Only the current page will be spoken, and always starting from the first word on the page unless you are resuming after pausing. You need to have the text control containing the text to be spoken in focus. I use the check button because you can use it when the XO is folded into its ebook reader configuration. There is also a Play/Pause button on the Speech tab of the toolbar that you can use instead.

If your system does not have the needed software to support text to speech you will ''not'' see the Speech tool bar. This is intentional.

The toolbar is very much like the one in the Speak activity and was adapted from its code. It allows you to change the language, pitch, and rate of speech. You can only do this while the Activity is not speaking. You can pause the speech, change its rate, pitch,or language, and then resume.

The latest version of Read Etexts supports either speech-dispatcher or the gstreamer espeak plugin developed by Aleksey Lim for the Sugar project. This plugin should be part of Sugar on a Stick and future releases of Sugar for the XO. This plugin works much better than speech-dispatcher does and does not require running a demon program or doing any configuration.

== Sharing Documents ==

This activity uses code adapted from the core Read activity for document sharing over the network. To share a document with someone that person must also have the Read Etexts activity installed, and it should be the same version for best results. You can invite an individual to join the activity or share it with the whole neighborhood, but either way only those who have the activity installed will see the invitation.

When someone accepts the invitation to join the activity a copy of the document is sent to his computer for him to read. When he exits the activity the document will be saved in the journal. The Journal entry will be titled "Read Etexts Activity", not the title of the book. Of course the recipient can modify this title to match the actual title of the book, but the activity currently will not do this for her.

This is a bit different from the core Read activity because I actually save a copy of the received document in the Journal, whereas Read does not. If you try to resume a shared Read activity when the document is not currently being shared you will get an empty document.

== The Baen Free Library ==

The [http://www.baen.com/library/ Baen Free Library] is a website from Baen Books that publishes free etexts of some of their books with the idea that this will ultimately increase sales of the printed editions. So far it seems to be working. Unfortunately, the formats they offer for downloading are not currently supported by any reading Activity for Sugar. The closest thing to a supported format is RTF (Rich Text Format) which you can load into the Write Activity. Write is a poor choice for reading etexts, unfortunately.

Version 17 of Read Etexts solves this problem by converting RTF to a plain text file automatically. So now, in addition to the great classics of literature by dead authors that Project Gutenberg gives you you can also read fairly current science fiction from Baen Books.

You can use the Browse Activity to download RTF files from the site. Be sure to choose the RTF file, not the zipped up RTF file. The zipped version ''should'' work, but the website does something to it that keeps it from getting a proper MIME type. I was able to use Browse on my XO running Sugar .82 to download RTFs. If Browse doesn't work for you an alternative is to use another computer to download the file to a thumb drive.

When you restore the file for the first time be sure to do it with Read Etexts, ''not'' Write. Write does something to the file that prevents Read Etexts from being able to convert it properly. Once you open it with Read Etexts it will be given the Read Etexts icon and will open with the correct Activity by default.

== Planned Features ==

* All planned features have been implemented. All that remains are bug fixes.

== Bugs ==

* Text to speech does not work perfectly. The gstreamer plugin combined with newer versions of espeak works much better than the original speech-dispatcher code did, but in Sugar on a Stick on ''some'' machines the text highlighting lags badly behind the spoken words.

== Source ==

http://git.sugarlabs.org/projects/readetexts

== The Movie! ==

See the future of reading, here today, by watching [http://www.dailymotion.com/video/xa4bhu_readetexts-the-movie_tech Read Etexts: The Movie].

''"You are interested in the future, because it is where we will spend the rest of our lives. And remember my friends, future events such as these will affect you in the future."'' -- Edward D. Wood

[[Category:Activities]]

Activities/Read Etexts

2009-09-07T19:30:09Z

Jdsimmons: /* Current Features */

== Description & Goals==

''"Outside of a dog, a book is man's best friend. Inside of a dog it's too dark to read."'' -- Groucho Marx

The Read Etexts activity is meant to allow the XO laptop to read Project Gutenberg ETexts, which are plain text files. The original goal of this Activity was to create a stopgap for reading plain text files until the core Read activity was able to do that. Read Etexts has become much more than that, adding features that core Read does not have, like text to speech with word highlighting, and most recently the ability to search the Project Gutenberg offline catalog and download books.

Since the [http://manybooks.net/ ManyBooks.net] website offers Project Gutenberg titles as PDFs you might wonder why you would need an Activity to read plain text files. It is a matter of personal preference. If you have a choice between a text file and a PDF, you may find that the text file is easier on the eyes than a PDF, takes up less space in the Journal (especially in zip format), and uses less memory to read. You will also find that the offline catalog search (Books tab) is a really convenient way to download books.

The interface to Read Etexts is very similar to the core Read activity, which should not be surprising as the toolbar code was adapted from Read's toolbar. You can use the up and down arrows or the game controller to scroll pages, and the '+' and '-' keys to adjust the font size. Use Page Up and Page Down to move to the previous and next pages respectively.

[http://www.gutenberg.org/wiki/Main_Page Project Gutenberg] is a website where you can download thousands of public domain books for free. There are books for every interest: classics, history, childen's novels, science fiction, and much, much more. [http://www.gutenberg.org/browse/loccs/pz Browse By Library of Congress Class: Language and Literatures: Juvenile belles lettres] will give you a list of books suitable for young readers.

Read ETexts can read books in plain text format or in Zip format. These are by far the most popular formats on the Gutenberg website. If for some reason you cannot use the Catalog search to get a book you can also download books from the website using the Browse activity. You should download one of the Zip file formats. These can be encoded as us-ascii text or as iso-8859-1; Read Etexts can handle either one. The iso-8859-1 encoding is used for books that need accent marks, etc. Save the Zip file to the Journal, change the Journal entry name to match the title of the book, and then resume it using the Read Etexts option on the Resume menu. See the first screenshot.

== Current Features ==

* Currently Read Etexts can be used to read Gutenberg Etexts, either as text files or as zip files containing one text file. The toolbars include Activity, Read (skip to page), Edit (copy to clipboard, search for text) and View (zoom text bigger or smaller). The Books toolbar comes up if you launch Read Etexts from the Activity ring. This toolbar supports searching the Project Gutenberg offline catalog and downloading books.
* Book sharing is supported.
* The power management code from the core Read activity has been added, with a few minor changes, and seems to work OK.
* Text to speech with Karaoke highlighting. The purpose of this is to produce a tool to help someone learn to read. Support for text to speech on the XO laptop is done using a gstreamer plugin for espeak. This plugin currently is not part of the software included on the XO, but is installed on Sugar on a Stick. You do '''not''' need this plugin installed to use Read Etexts, but you will of course not have text to speech working unless you do.
* The Books toolbar lets you search for books in Project Gutenberg's offline catalog. Enter in words that you would expect to find in the title or author of a book, then press Enter. A table will appear in the lower half of the screen listing book titles and authors that contain all of the words. Select a book from that table and click the download button and the book will arrive in a minute or so. The download tries to get the best available version of the book. For instance, it will try to download an 8 bit version of the book, and if there is none it will try to get a 7 bit version. (8 bit files contain accents and diacritical marks; the 7 bit versions do not. Not every text has both versions).
* You can download several books to the Journal in one session. Each book will be given a Journal entry when it downloads.
* The Activity has an annotation feature that enables the user to attach notes to pages in the text. These annotations are stored in a pickle file that is included in the Zip file containing the document. When you share a document your annotations will go along with it. For the recipient it will be sort of like buying a used textbook that has all the important stuff already marked up.
* The Activity supports multiple bookmarks in a document, and easy navigating between them. This is in addition to the current feature that remembers where you left off when you last read a document.
* The Activity supports highlightings passages in text. The highlight is shown as a yellow background (like a hi-lighter pen would make) plus a single underline. You can highlight multiple passages on a page.
* Word wrap is supported for those text documents that require it. Read Etexts considers a line of text to be no more than 80 characters, so a page break is calculated based on how many 80 character strings will fit in the paragraphs, plus one. A page will not break in the middle of a paragraph, so not every page is the same number of lines.
* With version 17 you can now read texts from the Baen Free Library in the Rich Text Format (RTF). Read Etexts will automatically convert RTF documents to plain text format for reading.

== Using Text to Speech ==

Read Etexts uses software called Speech Dispatcher to read text aloud and to perform callbacks which enable the word being spoken to be highlighted. Speech Dispatcher is not yet included with the normal XO software distribution, but will be included in version .84.

To start text to speech you simply press the check mark button on the XO's display (Numeric Keypad "End" on a standard keyboard). This button will also pause and resume speech. Only the current page will be spoken, and always starting from the first word on the page unless you are resuming after pausing. You need to have the text control containing the text to be spoken in focus. I use the check button because you can use it when the XO is folded into its ebook reader configuration. There is also a Play/Pause button on the Speech tab of the toolbar that you can use instead.

If your system does not have the needed software to support text to speech you will ''not'' see the Speech tool bar. This is intentional.

The toolbar is very much like the one in the Speak activity and was adapted from its code. It allows you to change the language, pitch, and rate of speech. You can only do this while the Activity is not speaking. You can pause the speech, change its rate, pitch,or language, and then resume.

The latest version of Read Etexts supports either speech-dispatcher or the gstreamer espeak plugin developed by Aleksey Lim for the Sugar project. This plugin should be part of Sugar on a Stick and future releases of Sugar for the XO. This plugin works much better than speech-dispatcher does and does not require running a demon program or doing any configuration.

== Sharing Documents ==

This activity uses code adapted from the core Read activity for document sharing over the network. To share a document with someone that person must also have the Read Etexts activity installed, and it should be the same version for best results. You can invite an individual to join the activity or share it with the whole neighborhood, but either way only those who have the activity installed will see the invitation.

When someone accepts the invitation to join the activity a copy of the document is sent to his computer for him to read. When he exits the activity the document will be saved in the journal. The Journal entry will be titled "Read Etexts Activity", not the title of the book. Of course the recipient can modify this title to match the actual title of the book, but the activity currently will not do this for her.

This is a bit different from the core Read activity because I actually save a copy of the received document in the Journal, whereas Read does not. If you try to resume a shared Read activity when the document is not currently being shared you will get an empty document.

== Planned Features ==

* All planned features have been implemented. All that remains are bug fixes.

== Bugs ==

* Text to speech does not work perfectly. The gstreamer plugin combined with newer versions of espeak works much better than the original speech-dispatcher code did, but in Sugar on a Stick on ''some'' machines the text highlighting lags badly behind the spoken words.

== Source ==

http://git.sugarlabs.org/projects/readetexts

== The Movie! ==

See the future of reading, here today, by watching [http://www.dailymotion.com/video/xa4bhu_readetexts-the-movie_tech Read Etexts: The Movie].

''"You are interested in the future, because it is where we will spend the rest of our lives. And remember my friends, future events such as these will affect you in the future."'' -- Edward D. Wood

[[Category:Activities]]

Video Using Sugar

2009-08-23T15:42:32Z

Jdsimmons:

* [http://www.dailymotion.com/video/x8zwgr_sugar-084-using-journal_tech Using the Journal]
* [http://www.dailymotion.com/video/x8zwl4_sugar-084-using-source-view_tech Using View Source]
* [http://www.dailymotion.com/user/sugarlabs/video/x9coz8_turtleartbasics_creation Turtle Art basics]
* [http://www.dailymotion.com/user/sugarlabs/video/x9cpzd_turtleartportfoliobasics_creation Turtle Art Portfolio basics]
* [http://www.dailymotion.com/user/sugarlabs/video/x9c0cl_xoman_creation XO Editor basics]
* [http://www.dailymotion.com/sugarlabs/video/15743402 Creating a customized Memory game]
* [http://www.dailymotion.com/user/sugarlabs/video/x9dsjf_hotcold-game_creation Hot-Cold game written in Turtle Art]
* [http://vimeo.com/5093861 Installing a XO bundle in Sugar]
* [http://vimeo.com/5093894 Installing InfoSlicer from Sugar Labs git repo]
* [http://vimeo.com/5093916 Playing with OOo4Kids in Sugar]
* [http://vimeo.com/5291250 Discovering the SocialCalc activity]
* [http://vimeo.com/5291223 Discovering the Physics activity]
* [http://www.ceibal.edu.uy/contenidos/areas_conocimiento/mat/desigualdadtriang/qu_es_un_programa.html Introduction to Python in Sugar]
* [http://vimeo.com/5757068 Overview of Sugar activity Read Etext]
* [http://vimeo.com/5730323 Overview of the french Helpfr (Aide) activity for Sugar]
* [http://www.dailymotion.com/user/sugarlabs/video/x9yrxj_continent-game_tech Turtle Art Continent Game]
* [http://www.dailymotion.com/user/sugarlabs/video/x9xz9o_stategame Turtle Art State Game]
* [http://www.dailymotion.com/user/sugarlabs/video/x9zy4v_where-is-the-gardner-schooly_tech Gardner School Game]
* [http://mail.google.com/mail/?shva=1#inbox/123166ec37e04b5e Using the Physics Activity]
* [http://www.dailymotion.com/user/delphi923/video/xa6p7g_how-to-boot-sugar-on-a-netbook_tech How to boot Sugar on a netbook]
* [http://www.youtube.com/results?search_query=pleabargain+sugar+neighborhood&search_type=&aq=f Discovering the neighborhood]
* [http://www.dailymotion.com/relevance/search/sugar+labs/video/xa4bhu_readetexts-the-movie_tech Read Etexts: The Movie]
* [http://www.dailymotion.com/relevance/search/sugar+labs/video/xa4eua_reading-with-the-sugar-desktop_tech Reading With The Sugar Desktop]

Activities/Get Internet Archive Books

2009-08-11T01:47:00Z

Jdsimmons: /* Source */

== Description & Goals==

The Internet Archive is a website containing around a million public domain ebooks created by scanning page images from books in various libraries. Because of this the ebooks have pages that look like the books they came from, including illustrations and other page decorations. It may be the best source of free books for younger readers, as well as for books in languages other than English.

This Activity will use the [http://www.archive.org/advancedsearch.php Advanced Search] capabilities of the [http://www.archive.org/index.php Internet Archive website] to enable browsing the website's catalog, getting information on the books therein, and downloading these books to the Journal. Its user interface is similar to the offline catalog search of Read Etexts, but where that Activity is used for both getting books and reading them this one will concern itself only with getting the books, so they may be read with the Read Activity.

== Current Features ==

The Activity will allow searching on Title and Author. The books found will be listed in a table containing Author, Title, Volume (if any) and Language. Selecting the entry in the table will display other metadata about the book above the table: the book's description and subject, publisher, etc. The user may then download the selected book to the Journal where it will be given a title meta tag containing title and author and an appropriate MIME type.

I support these formats for downloading:

* PDF
* Black and White PDF
* Deja Vu

The other formats Project Gutenberg offers are Text and Flipbook. A Flipbook is a collection of image files in a Zip archive along with some Javascript. You could use View Slides to read these, but the page images are too small to be readable. Also, text files for the Internet Archive are created with OCR software with no attempt to format or proofread it, so I probably won't offer this one either.

Deja Vu is a special format for books composed of scanned in page images. It gives better results with more highly compressed files than you get with PDFs. Typically a Deja Vu book is half the size of a Color PDF. Deja Vu is the default download format, but if you are using an XO with version .82 of Sugar you may find that Deja Vu support in the Read Activity is not very robust. For .82 choose one of the PDF formats. The B/W PDF format is not available for every book, but it uses notably less disk space than the Color version.

The metadata for the downloaded book is stored in the Journal entry's Description field.

== Planned Features ==

I consider this Activity to be feature complete. The only thing I might do is find some data to put in the Journal entry it creates for itself. At the moment that Journal entry is empty.

== Bugs ==

# I'd like the Activity to start up with the search field having the focus. I put in code that should do this but it isn't working.

== Source ==

http://git.sugarlabs.org/projects/get-internet-archive-books

== The Movie! ==

See [http://www.dailymotion.com/video/xa4eua_reading-with-the-sugar-desktop_tech Reading With The Sugar Desktop] at Daily Motion.

[[Category:Activities]]

Activities/Read Etexts

2009-08-11T01:35:17Z

Jdsimmons: /* The Movie! */

== Description & Goals==

''"Outside of a dog, a book is man's best friend. Inside of a dog it's too dark to read."'' -- Groucho Marx

The Read Etexts activity is meant to allow the XO laptop to read Project Gutenberg ETexts, which are plain text files. The original goal of this Activity was to create a stopgap for reading plain text files until the core Read activity was able to do that. Read Etexts has become much more than that, adding features that core Read does not have, like text to speech with word highlighting, and most recently the ability to search the Project Gutenberg offline catalog and download books.

Since the [http://manybooks.net/ ManyBooks.net] website offers Project Gutenberg titles as PDFs you might wonder why you would need an Activity to read plain text files. It is a matter of personal preference. If you have a choice between a text file and a PDF, you may find that the text file is easier on the eyes than a PDF, takes up less space in the Journal (especially in zip format), and uses less memory to read. You will also find that the offline catalog search (Books tab) is a really convenient way to download books.

The interface to Read Etexts is very similar to the core Read activity, which should not be surprising as the toolbar code was adapted from Read's toolbar. You can use the up and down arrows or the game controller to scroll pages, and the '+' and '-' keys to adjust the font size. Use Page Up and Page Down to move to the previous and next pages respectively.

[http://www.gutenberg.org/wiki/Main_Page Project Gutenberg] is a website where you can download thousands of public domain books for free. There are books for every interest: classics, history, childen's novels, science fiction, and much, much more. [http://www.gutenberg.org/browse/loccs/pz Browse By Library of Congress Class: Language and Literatures: Juvenile belles lettres] will give you a list of books suitable for young readers.

Read ETexts can read books in plain text format or in Zip format. These are by far the most popular formats on the Gutenberg website. If for some reason you cannot use the Catalog search to get a book you can also download books from the website using the Browse activity. You should download one of the Zip file formats. These can be encoded as us-ascii text or as iso-8859-1; Read Etexts can handle either one. The iso-8859-1 encoding is used for books that need accent marks, etc. Save the Zip file to the Journal, change the Journal entry name to match the title of the book, and then resume it using the Read Etexts option on the Resume menu. See the first screenshot.

== Current Features ==

* Currently Read Etexts can be used to read Gutenberg Etexts, either as text files or as zip files containing one text file. The toolbars include Activity, Read (skip to page), Edit (copy to clipboard, search for text) and View (zoom text bigger or smaller). The Books toolbar comes up if you launch Read Etexts from the Activity ring. This toolbar supports searching the Project Gutenberg offline catalog and downloading books.
* Book sharing is supported.
* The power management code from the core Read activity has been added, with a few minor changes, and seems to work OK.
* Text to speech with Karaoke highlighting. The purpose of this is to produce a tool to help someone learn to read. Support for text to speech on the XO laptop is done using a gstreamer plugin for espeak. This plugin currently is not part of the software included on the XO, but is installed on Sugar on a Stick. You do '''not''' need this plugin installed to use Read Etexts, but you will of course not have text to speech working unless you do.
* The Books toolbar lets you search for books in Project Gutenberg's offline catalog. Enter in words that you would expect to find in the title or author of a book, then press Enter. A table will appear in the lower half of the screen listing book titles and authors that contain all of the words. Select a book from that table and click the download button and the book will arrive in a minute or so. The download tries to get the best available version of the book. For instance, it will try to download an 8 bit version of the book, and if there is none it will try to get a 7 bit version. (8 bit files contain accents and diacritical marks; the 7 bit versions do not. Not every text has both versions).
* You can download several books to the Journal in one session. Each book will be given a Journal entry when it downloads.
* The Activity has an annotation feature that enables the user to attach notes to pages in the text. These annotations are stored in a pickle file that is included in the Zip file containing the document. When you share a document your annotations will go along with it. For the recipient it will be sort of like buying a used textbook that has all the important stuff already marked up.
* The Activity supports multiple bookmarks in a document, and easy navigating between them. This is in addition to the current feature that remembers where you left off when you last read a document.
* The Activity supports highlightings passages in text. The highlight is shown as a yellow background (like a hi-lighter pen would make) plus a single underline. You can highlight multiple passages on a page.
* Word wrap is supported for those text documents that require it. Read Etexts considers a line of text to be no more than 80 characters, so a page break is calculated based on how many 80 character strings will fit in the paragraphs, plus one. A page will not break in the middle of a paragraph, so not every page is the same number of lines.

== Using Text to Speech ==

Read Etexts uses software called Speech Dispatcher to read text aloud and to perform callbacks which enable the word being spoken to be highlighted. Speech Dispatcher is not yet included with the normal XO software distribution, but will be included in version .84.

To start text to speech you simply press the check mark button on the XO's display (Numeric Keypad "End" on a standard keyboard). This button will also pause and resume speech. Only the current page will be spoken, and always starting from the first word on the page unless you are resuming after pausing. You need to have the text control containing the text to be spoken in focus. I use the check button because you can use it when the XO is folded into its ebook reader configuration. There is also a Play/Pause button on the Speech tab of the toolbar that you can use instead.

If your system does not have the needed software to support text to speech you will ''not'' see the Speech tool bar. This is intentional.

The toolbar is very much like the one in the Speak activity and was adapted from its code. It allows you to change the language, pitch, and rate of speech. You can only do this while the Activity is not speaking. You can pause the speech, change its rate, pitch,or language, and then resume.

The latest version of Read Etexts supports either speech-dispatcher or the gstreamer espeak plugin developed by Aleksey Lim for the Sugar project. This plugin should be part of Sugar on a Stick and future releases of Sugar for the XO. This plugin works much better than speech-dispatcher does and does not require running a demon program or doing any configuration.

== Sharing Documents ==

This activity uses code adapted from the core Read activity for document sharing over the network. To share a document with someone that person must also have the Read Etexts activity installed, and it should be the same version for best results. You can invite an individual to join the activity or share it with the whole neighborhood, but either way only those who have the activity installed will see the invitation.

When someone accepts the invitation to join the activity a copy of the document is sent to his computer for him to read. When he exits the activity the document will be saved in the journal. The Journal entry will be titled "Read Etexts Activity", not the title of the book. Of course the recipient can modify this title to match the actual title of the book, but the activity currently will not do this for her.

This is a bit different from the core Read activity because I actually save a copy of the received document in the Journal, whereas Read does not. If you try to resume a shared Read activity when the document is not currently being shared you will get an empty document.

== Planned Features ==

* All planned features have been implemented. All that remains are bug fixes.

== Bugs ==

* Text to speech does not work perfectly. The gstreamer plugin combined with newer versions of espeak works much better than the original speech-dispatcher code did, but in Sugar on a Stick on ''some'' machines the text highlighting lags badly behind the spoken words.

== Source ==

http://git.sugarlabs.org/projects/readetexts

== The Movie! ==

See the future of reading, here today, by watching [http://www.dailymotion.com/video/xa4bhu_readetexts-the-movie_tech Read Etexts: The Movie].

''"You are interested in the future, because it is where we will spend the rest of our lives. And remember my friends, future events such as these will affect you in the future."'' -- Edward D. Wood

[[Category:Activities]]

Activities/Read Etexts

2009-08-11T01:34:37Z

Jdsimmons: /* The Movie! */

== Description & Goals==

''"Outside of a dog, a book is man's best friend. Inside of a dog it's too dark to read."'' -- Groucho Marx

The Read Etexts activity is meant to allow the XO laptop to read Project Gutenberg ETexts, which are plain text files. The original goal of this Activity was to create a stopgap for reading plain text files until the core Read activity was able to do that. Read Etexts has become much more than that, adding features that core Read does not have, like text to speech with word highlighting, and most recently the ability to search the Project Gutenberg offline catalog and download books.

Since the [http://manybooks.net/ ManyBooks.net] website offers Project Gutenberg titles as PDFs you might wonder why you would need an Activity to read plain text files. It is a matter of personal preference. If you have a choice between a text file and a PDF, you may find that the text file is easier on the eyes than a PDF, takes up less space in the Journal (especially in zip format), and uses less memory to read. You will also find that the offline catalog search (Books tab) is a really convenient way to download books.

The interface to Read Etexts is very similar to the core Read activity, which should not be surprising as the toolbar code was adapted from Read's toolbar. You can use the up and down arrows or the game controller to scroll pages, and the '+' and '-' keys to adjust the font size. Use Page Up and Page Down to move to the previous and next pages respectively.

[http://www.gutenberg.org/wiki/Main_Page Project Gutenberg] is a website where you can download thousands of public domain books for free. There are books for every interest: classics, history, childen's novels, science fiction, and much, much more. [http://www.gutenberg.org/browse/loccs/pz Browse By Library of Congress Class: Language and Literatures: Juvenile belles lettres] will give you a list of books suitable for young readers.

Read ETexts can read books in plain text format or in Zip format. These are by far the most popular formats on the Gutenberg website. If for some reason you cannot use the Catalog search to get a book you can also download books from the website using the Browse activity. You should download one of the Zip file formats. These can be encoded as us-ascii text or as iso-8859-1; Read Etexts can handle either one. The iso-8859-1 encoding is used for books that need accent marks, etc. Save the Zip file to the Journal, change the Journal entry name to match the title of the book, and then resume it using the Read Etexts option on the Resume menu. See the first screenshot.

== Current Features ==

* Currently Read Etexts can be used to read Gutenberg Etexts, either as text files or as zip files containing one text file. The toolbars include Activity, Read (skip to page), Edit (copy to clipboard, search for text) and View (zoom text bigger or smaller). The Books toolbar comes up if you launch Read Etexts from the Activity ring. This toolbar supports searching the Project Gutenberg offline catalog and downloading books.
* Book sharing is supported.
* The power management code from the core Read activity has been added, with a few minor changes, and seems to work OK.
* Text to speech with Karaoke highlighting. The purpose of this is to produce a tool to help someone learn to read. Support for text to speech on the XO laptop is done using a gstreamer plugin for espeak. This plugin currently is not part of the software included on the XO, but is installed on Sugar on a Stick. You do '''not''' need this plugin installed to use Read Etexts, but you will of course not have text to speech working unless you do.
* The Books toolbar lets you search for books in Project Gutenberg's offline catalog. Enter in words that you would expect to find in the title or author of a book, then press Enter. A table will appear in the lower half of the screen listing book titles and authors that contain all of the words. Select a book from that table and click the download button and the book will arrive in a minute or so. The download tries to get the best available version of the book. For instance, it will try to download an 8 bit version of the book, and if there is none it will try to get a 7 bit version. (8 bit files contain accents and diacritical marks; the 7 bit versions do not. Not every text has both versions).
* You can download several books to the Journal in one session. Each book will be given a Journal entry when it downloads.
* The Activity has an annotation feature that enables the user to attach notes to pages in the text. These annotations are stored in a pickle file that is included in the Zip file containing the document. When you share a document your annotations will go along with it. For the recipient it will be sort of like buying a used textbook that has all the important stuff already marked up.
* The Activity supports multiple bookmarks in a document, and easy navigating between them. This is in addition to the current feature that remembers where you left off when you last read a document.
* The Activity supports highlightings passages in text. The highlight is shown as a yellow background (like a hi-lighter pen would make) plus a single underline. You can highlight multiple passages on a page.
* Word wrap is supported for those text documents that require it. Read Etexts considers a line of text to be no more than 80 characters, so a page break is calculated based on how many 80 character strings will fit in the paragraphs, plus one. A page will not break in the middle of a paragraph, so not every page is the same number of lines.

== Using Text to Speech ==

Read Etexts uses software called Speech Dispatcher to read text aloud and to perform callbacks which enable the word being spoken to be highlighted. Speech Dispatcher is not yet included with the normal XO software distribution, but will be included in version .84.

To start text to speech you simply press the check mark button on the XO's display (Numeric Keypad "End" on a standard keyboard). This button will also pause and resume speech. Only the current page will be spoken, and always starting from the first word on the page unless you are resuming after pausing. You need to have the text control containing the text to be spoken in focus. I use the check button because you can use it when the XO is folded into its ebook reader configuration. There is also a Play/Pause button on the Speech tab of the toolbar that you can use instead.

If your system does not have the needed software to support text to speech you will ''not'' see the Speech tool bar. This is intentional.

The toolbar is very much like the one in the Speak activity and was adapted from its code. It allows you to change the language, pitch, and rate of speech. You can only do this while the Activity is not speaking. You can pause the speech, change its rate, pitch,or language, and then resume.

The latest version of Read Etexts supports either speech-dispatcher or the gstreamer espeak plugin developed by Aleksey Lim for the Sugar project. This plugin should be part of Sugar on a Stick and future releases of Sugar for the XO. This plugin works much better than speech-dispatcher does and does not require running a demon program or doing any configuration.

== Sharing Documents ==

This activity uses code adapted from the core Read activity for document sharing over the network. To share a document with someone that person must also have the Read Etexts activity installed, and it should be the same version for best results. You can invite an individual to join the activity or share it with the whole neighborhood, but either way only those who have the activity installed will see the invitation.

When someone accepts the invitation to join the activity a copy of the document is sent to his computer for him to read. When he exits the activity the document will be saved in the journal. The Journal entry will be titled "Read Etexts Activity", not the title of the book. Of course the recipient can modify this title to match the actual title of the book, but the activity currently will not do this for her.

This is a bit different from the core Read activity because I actually save a copy of the received document in the Journal, whereas Read does not. If you try to resume a shared Read activity when the document is not currently being shared you will get an empty document.

== Planned Features ==

* All planned features have been implemented. All that remains are bug fixes.

== Bugs ==

* Text to speech does not work perfectly. The gstreamer plugin combined with newer versions of espeak works much better than the original speech-dispatcher code did, but in Sugar on a Stick on ''some'' machines the text highlighting lags badly behind the spoken words.

== Source ==

http://git.sugarlabs.org/projects/readetexts

== The Movie! ==

See the future of reading, here today, by watching [http://www.dailymotion.com/video/xa4bhu_readetexts-the-movie_tech Read Etexts: The Movie].

"You are interested in the future, because it is where we will spend the rest of our lives. And remember my friends, future events such as these will affect you in the future." Edward D. Wood

[[Category:Activities]]

Activities/Read Etexts

2009-08-10T18:38:13Z

Jdsimmons: /* Current Features */

== Description & Goals==

''"Outside of a dog, a book is man's best friend. Inside of a dog it's too dark to read."'' -- Groucho Marx

The Read Etexts activity is meant to allow the XO laptop to read Project Gutenberg ETexts, which are plain text files. The original goal of this Activity was to create a stopgap for reading plain text files until the core Read activity was able to do that. Read Etexts has become much more than that, adding features that core Read does not have, like text to speech with word highlighting, and most recently the ability to search the Project Gutenberg offline catalog and download books.

Since the [http://manybooks.net/ ManyBooks.net] website offers Project Gutenberg titles as PDFs you might wonder why you would need an Activity to read plain text files. It is a matter of personal preference. If you have a choice between a text file and a PDF, you may find that the text file is easier on the eyes than a PDF, takes up less space in the Journal (especially in zip format), and uses less memory to read. You will also find that the offline catalog search (Books tab) is a really convenient way to download books.

The interface to Read Etexts is very similar to the core Read activity, which should not be surprising as the toolbar code was adapted from Read's toolbar. You can use the up and down arrows or the game controller to scroll pages, and the '+' and '-' keys to adjust the font size. Use Page Up and Page Down to move to the previous and next pages respectively.

[http://www.gutenberg.org/wiki/Main_Page Project Gutenberg] is a website where you can download thousands of public domain books for free. There are books for every interest: classics, history, childen's novels, science fiction, and much, much more. [http://www.gutenberg.org/browse/loccs/pz Browse By Library of Congress Class: Language and Literatures: Juvenile belles lettres] will give you a list of books suitable for young readers.

Read ETexts can read books in plain text format or in Zip format. These are by far the most popular formats on the Gutenberg website. If for some reason you cannot use the Catalog search to get a book you can also download books from the website using the Browse activity. You should download one of the Zip file formats. These can be encoded as us-ascii text or as iso-8859-1; Read Etexts can handle either one. The iso-8859-1 encoding is used for books that need accent marks, etc. Save the Zip file to the Journal, change the Journal entry name to match the title of the book, and then resume it using the Read Etexts option on the Resume menu. See the first screenshot.

== Current Features ==

* Currently Read Etexts can be used to read Gutenberg Etexts, either as text files or as zip files containing one text file. The toolbars include Activity, Read (skip to page), Edit (copy to clipboard, search for text) and View (zoom text bigger or smaller). The Books toolbar comes up if you launch Read Etexts from the Activity ring. This toolbar supports searching the Project Gutenberg offline catalog and downloading books.
* Book sharing is supported.
* The power management code from the core Read activity has been added, with a few minor changes, and seems to work OK.
* Text to speech with Karaoke highlighting. The purpose of this is to produce a tool to help someone learn to read. Support for text to speech on the XO laptop is done using a gstreamer plugin for espeak. This plugin currently is not part of the software included on the XO, but is installed on Sugar on a Stick. You do '''not''' need this plugin installed to use Read Etexts, but you will of course not have text to speech working unless you do.
* The Books toolbar lets you search for books in Project Gutenberg's offline catalog. Enter in words that you would expect to find in the title or author of a book, then press Enter. A table will appear in the lower half of the screen listing book titles and authors that contain all of the words. Select a book from that table and click the download button and the book will arrive in a minute or so. The download tries to get the best available version of the book. For instance, it will try to download an 8 bit version of the book, and if there is none it will try to get a 7 bit version. (8 bit files contain accents and diacritical marks; the 7 bit versions do not. Not every text has both versions).
* You can download several books to the Journal in one session. Each book will be given a Journal entry when it downloads.
* The Activity has an annotation feature that enables the user to attach notes to pages in the text. These annotations are stored in a pickle file that is included in the Zip file containing the document. When you share a document your annotations will go along with it. For the recipient it will be sort of like buying a used textbook that has all the important stuff already marked up.
* The Activity supports multiple bookmarks in a document, and easy navigating between them. This is in addition to the current feature that remembers where you left off when you last read a document.
* The Activity supports highlightings passages in text. The highlight is shown as a yellow background (like a hi-lighter pen would make) plus a single underline. You can highlight multiple passages on a page.
* Word wrap is supported for those text documents that require it. Read Etexts considers a line of text to be no more than 80 characters, so a page break is calculated based on how many 80 character strings will fit in the paragraphs, plus one. A page will not break in the middle of a paragraph, so not every page is the same number of lines.

== Using Text to Speech ==

Read Etexts uses software called Speech Dispatcher to read text aloud and to perform callbacks which enable the word being spoken to be highlighted. Speech Dispatcher is not yet included with the normal XO software distribution, but will be included in version .84.

To start text to speech you simply press the check mark button on the XO's display (Numeric Keypad "End" on a standard keyboard). This button will also pause and resume speech. Only the current page will be spoken, and always starting from the first word on the page unless you are resuming after pausing. You need to have the text control containing the text to be spoken in focus. I use the check button because you can use it when the XO is folded into its ebook reader configuration. There is also a Play/Pause button on the Speech tab of the toolbar that you can use instead.

If your system does not have the needed software to support text to speech you will ''not'' see the Speech tool bar. This is intentional.

The toolbar is very much like the one in the Speak activity and was adapted from its code. It allows you to change the language, pitch, and rate of speech. You can only do this while the Activity is not speaking. You can pause the speech, change its rate, pitch,or language, and then resume.

The latest version of Read Etexts supports either speech-dispatcher or the gstreamer espeak plugin developed by Aleksey Lim for the Sugar project. This plugin should be part of Sugar on a Stick and future releases of Sugar for the XO. This plugin works much better than speech-dispatcher does and does not require running a demon program or doing any configuration.

== Sharing Documents ==

This activity uses code adapted from the core Read activity for document sharing over the network. To share a document with someone that person must also have the Read Etexts activity installed, and it should be the same version for best results. You can invite an individual to join the activity or share it with the whole neighborhood, but either way only those who have the activity installed will see the invitation.

When someone accepts the invitation to join the activity a copy of the document is sent to his computer for him to read. When he exits the activity the document will be saved in the journal. The Journal entry will be titled "Read Etexts Activity", not the title of the book. Of course the recipient can modify this title to match the actual title of the book, but the activity currently will not do this for her.

This is a bit different from the core Read activity because I actually save a copy of the received document in the Journal, whereas Read does not. If you try to resume a shared Read activity when the document is not currently being shared you will get an empty document.

== Planned Features ==

* All planned features have been implemented. All that remains are bug fixes.

== Bugs ==

* Text to speech does not work perfectly. The gstreamer plugin combined with newer versions of espeak works much better than the original speech-dispatcher code did, but in Sugar on a Stick on ''some'' machines the text highlighting lags badly behind the spoken words.

== Source ==

http://git.sugarlabs.org/projects/readetexts

== The Movie! ==

See the future of reading, here today, by watching [http://www.dailymotion.com/video/xa4bhu_readetexts-the-movie_tech Read Etexts: The Movie]. You are interested in the future, because it is where we will spend the rest of our lives. And remember my friends, future events such as these will affect you in the future.

[[Category:Activities]]

Activities/Read Etexts

2009-08-10T18:32:40Z

Jdsimmons: /* Planned Features */

== Description & Goals==

''"Outside of a dog, a book is man's best friend. Inside of a dog it's too dark to read."'' -- Groucho Marx

The Read Etexts activity is meant to allow the XO laptop to read Project Gutenberg ETexts, which are plain text files. The original goal of this Activity was to create a stopgap for reading plain text files until the core Read activity was able to do that. Read Etexts has become much more than that, adding features that core Read does not have, like text to speech with word highlighting, and most recently the ability to search the Project Gutenberg offline catalog and download books.

Since the [http://manybooks.net/ ManyBooks.net] website offers Project Gutenberg titles as PDFs you might wonder why you would need an Activity to read plain text files. It is a matter of personal preference. If you have a choice between a text file and a PDF, you may find that the text file is easier on the eyes than a PDF, takes up less space in the Journal (especially in zip format), and uses less memory to read. You will also find that the offline catalog search (Books tab) is a really convenient way to download books.

The interface to Read Etexts is very similar to the core Read activity, which should not be surprising as the toolbar code was adapted from Read's toolbar. You can use the up and down arrows or the game controller to scroll pages, and the '+' and '-' keys to adjust the font size. Use Page Up and Page Down to move to the previous and next pages respectively.

[http://www.gutenberg.org/wiki/Main_Page Project Gutenberg] is a website where you can download thousands of public domain books for free. There are books for every interest: classics, history, childen's novels, science fiction, and much, much more. [http://www.gutenberg.org/browse/loccs/pz Browse By Library of Congress Class: Language and Literatures: Juvenile belles lettres] will give you a list of books suitable for young readers.

Read ETexts can read books in plain text format or in Zip format. These are by far the most popular formats on the Gutenberg website. If for some reason you cannot use the Catalog search to get a book you can also download books from the website using the Browse activity. You should download one of the Zip file formats. These can be encoded as us-ascii text or as iso-8859-1; Read Etexts can handle either one. The iso-8859-1 encoding is used for books that need accent marks, etc. Save the Zip file to the Journal, change the Journal entry name to match the title of the book, and then resume it using the Read Etexts option on the Resume menu. See the first screenshot.

== Current Features ==

* Currently Read Etexts can be used to read Gutenberg Etexts, either as text files or as zip files containing one text file. The toolbars include Activity, Read (skip to page), Edit (copy to clipboard, search for text) and View (zoom text bigger or smaller). The Books toolbar comes up if you launch Read Etexts from the Activity ring. This toolbar supports searching the Project Gutenberg offline catalog and downloading books.
* Book sharing is supported.
* The power management code from the core Read activity has been added, with a few minor changes, and seems to work OK.
* Text to speech with Karaoke highlighting. The purpose of this is to produce a tool to help someone learn to read. Support for text to speech on the XO laptop is done using a gstreamer plugin for espeak. This plugin currently is not part of the software included on the XO, but is installed on Sugar on a Stick. You do '''not''' need this plugin installed to use Read Etexts, but you will of course not have text to speech working unless you do.
* The Books toolbar lets you search for books in Project Gutenberg's offline catalog. Enter in words that you would expect to find in the title or author of a book, then press Enter. A table will appear in the lower half of the screen listing book titles and authors that contain all of the words. Select a book from that table and click the download button and the book will arrive in a minute or so. The download tries to get the best available version of the book. For instance, it will try to download an 8 bit version of the book, and if there is none it will try to get a 7 bit version. (8 bit files contain accents and diacritical marks; the 7 bit versions do not. Not every text has both versions).
* You can download several books to the Journal in one session. Each book will be given a Journal entry when it downloads.
* The Activity has an annotation feature that enables the user to attach notes to pages in the text. These annotations are stored in a pickle file that is included in the Zip file containing the document. When you share a document your annotations will go along with it. For the recipient it will be sort of like buying a used textbook that has all the important stuff already marked up.
* The Activity supports multiple bookmarks in a document, and easy navigating between them. This is in addition to the current feature that remembers where you left off when you last read a document.

== Using Text to Speech ==

Read Etexts uses software called Speech Dispatcher to read text aloud and to perform callbacks which enable the word being spoken to be highlighted. Speech Dispatcher is not yet included with the normal XO software distribution, but will be included in version .84.

To start text to speech you simply press the check mark button on the XO's display (Numeric Keypad "End" on a standard keyboard). This button will also pause and resume speech. Only the current page will be spoken, and always starting from the first word on the page unless you are resuming after pausing. You need to have the text control containing the text to be spoken in focus. I use the check button because you can use it when the XO is folded into its ebook reader configuration. There is also a Play/Pause button on the Speech tab of the toolbar that you can use instead.

If your system does not have the needed software to support text to speech you will ''not'' see the Speech tool bar. This is intentional.

The toolbar is very much like the one in the Speak activity and was adapted from its code. It allows you to change the language, pitch, and rate of speech. You can only do this while the Activity is not speaking. You can pause the speech, change its rate, pitch,or language, and then resume.

The latest version of Read Etexts supports either speech-dispatcher or the gstreamer espeak plugin developed by Aleksey Lim for the Sugar project. This plugin should be part of Sugar on a Stick and future releases of Sugar for the XO. This plugin works much better than speech-dispatcher does and does not require running a demon program or doing any configuration.

== Sharing Documents ==

This activity uses code adapted from the core Read activity for document sharing over the network. To share a document with someone that person must also have the Read Etexts activity installed, and it should be the same version for best results. You can invite an individual to join the activity or share it with the whole neighborhood, but either way only those who have the activity installed will see the invitation.

When someone accepts the invitation to join the activity a copy of the document is sent to his computer for him to read. When he exits the activity the document will be saved in the journal. The Journal entry will be titled "Read Etexts Activity", not the title of the book. Of course the recipient can modify this title to match the actual title of the book, but the activity currently will not do this for her.

This is a bit different from the core Read activity because I actually save a copy of the received document in the Journal, whereas Read does not. If you try to resume a shared Read activity when the document is not currently being shared you will get an empty document.

== Planned Features ==

* All planned features have been implemented. All that remains are bug fixes.

== Bugs ==

* Text to speech does not work perfectly. The gstreamer plugin combined with newer versions of espeak works much better than the original speech-dispatcher code did, but in Sugar on a Stick on ''some'' machines the text highlighting lags badly behind the spoken words.

== Source ==

http://git.sugarlabs.org/projects/readetexts

== The Movie! ==

See the future of reading, here today, by watching [http://www.dailymotion.com/video/xa4bhu_readetexts-the-movie_tech Read Etexts: The Movie]. You are interested in the future, because it is where we will spend the rest of our lives. And remember my friends, future events such as these will affect you in the future.

[[Category:Activities]]

Activities/Read Etexts

2009-08-10T18:28:56Z

Jdsimmons: /* Bugs */

== Description & Goals==

''"Outside of a dog, a book is man's best friend. Inside of a dog it's too dark to read."'' -- Groucho Marx

The Read Etexts activity is meant to allow the XO laptop to read Project Gutenberg ETexts, which are plain text files. The original goal of this Activity was to create a stopgap for reading plain text files until the core Read activity was able to do that. Read Etexts has become much more than that, adding features that core Read does not have, like text to speech with word highlighting, and most recently the ability to search the Project Gutenberg offline catalog and download books.

Since the [http://manybooks.net/ ManyBooks.net] website offers Project Gutenberg titles as PDFs you might wonder why you would need an Activity to read plain text files. It is a matter of personal preference. If you have a choice between a text file and a PDF, you may find that the text file is easier on the eyes than a PDF, takes up less space in the Journal (especially in zip format), and uses less memory to read. You will also find that the offline catalog search (Books tab) is a really convenient way to download books.

The interface to Read Etexts is very similar to the core Read activity, which should not be surprising as the toolbar code was adapted from Read's toolbar. You can use the up and down arrows or the game controller to scroll pages, and the '+' and '-' keys to adjust the font size. Use Page Up and Page Down to move to the previous and next pages respectively.

[http://www.gutenberg.org/wiki/Main_Page Project Gutenberg] is a website where you can download thousands of public domain books for free. There are books for every interest: classics, history, childen's novels, science fiction, and much, much more. [http://www.gutenberg.org/browse/loccs/pz Browse By Library of Congress Class: Language and Literatures: Juvenile belles lettres] will give you a list of books suitable for young readers.

Read ETexts can read books in plain text format or in Zip format. These are by far the most popular formats on the Gutenberg website. If for some reason you cannot use the Catalog search to get a book you can also download books from the website using the Browse activity. You should download one of the Zip file formats. These can be encoded as us-ascii text or as iso-8859-1; Read Etexts can handle either one. The iso-8859-1 encoding is used for books that need accent marks, etc. Save the Zip file to the Journal, change the Journal entry name to match the title of the book, and then resume it using the Read Etexts option on the Resume menu. See the first screenshot.

== Current Features ==

* Currently Read Etexts can be used to read Gutenberg Etexts, either as text files or as zip files containing one text file. The toolbars include Activity, Read (skip to page), Edit (copy to clipboard, search for text) and View (zoom text bigger or smaller). The Books toolbar comes up if you launch Read Etexts from the Activity ring. This toolbar supports searching the Project Gutenberg offline catalog and downloading books.
* Book sharing is supported.
* The power management code from the core Read activity has been added, with a few minor changes, and seems to work OK.
* Text to speech with Karaoke highlighting. The purpose of this is to produce a tool to help someone learn to read. Support for text to speech on the XO laptop is done using a gstreamer plugin for espeak. This plugin currently is not part of the software included on the XO, but is installed on Sugar on a Stick. You do '''not''' need this plugin installed to use Read Etexts, but you will of course not have text to speech working unless you do.
* The Books toolbar lets you search for books in Project Gutenberg's offline catalog. Enter in words that you would expect to find in the title or author of a book, then press Enter. A table will appear in the lower half of the screen listing book titles and authors that contain all of the words. Select a book from that table and click the download button and the book will arrive in a minute or so. The download tries to get the best available version of the book. For instance, it will try to download an 8 bit version of the book, and if there is none it will try to get a 7 bit version. (8 bit files contain accents and diacritical marks; the 7 bit versions do not. Not every text has both versions).
* You can download several books to the Journal in one session. Each book will be given a Journal entry when it downloads.
* The Activity has an annotation feature that enables the user to attach notes to pages in the text. These annotations are stored in a pickle file that is included in the Zip file containing the document. When you share a document your annotations will go along with it. For the recipient it will be sort of like buying a used textbook that has all the important stuff already marked up.
* The Activity supports multiple bookmarks in a document, and easy navigating between them. This is in addition to the current feature that remembers where you left off when you last read a document.

== Using Text to Speech ==

Read Etexts uses software called Speech Dispatcher to read text aloud and to perform callbacks which enable the word being spoken to be highlighted. Speech Dispatcher is not yet included with the normal XO software distribution, but will be included in version .84.

To start text to speech you simply press the check mark button on the XO's display (Numeric Keypad "End" on a standard keyboard). This button will also pause and resume speech. Only the current page will be spoken, and always starting from the first word on the page unless you are resuming after pausing. You need to have the text control containing the text to be spoken in focus. I use the check button because you can use it when the XO is folded into its ebook reader configuration. There is also a Play/Pause button on the Speech tab of the toolbar that you can use instead.

If your system does not have the needed software to support text to speech you will ''not'' see the Speech tool bar. This is intentional.

The toolbar is very much like the one in the Speak activity and was adapted from its code. It allows you to change the language, pitch, and rate of speech. You can only do this while the Activity is not speaking. You can pause the speech, change its rate, pitch,or language, and then resume.

The latest version of Read Etexts supports either speech-dispatcher or the gstreamer espeak plugin developed by Aleksey Lim for the Sugar project. This plugin should be part of Sugar on a Stick and future releases of Sugar for the XO. This plugin works much better than speech-dispatcher does and does not require running a demon program or doing any configuration.

== Sharing Documents ==

This activity uses code adapted from the core Read activity for document sharing over the network. To share a document with someone that person must also have the Read Etexts activity installed, and it should be the same version for best results. You can invite an individual to join the activity or share it with the whole neighborhood, but either way only those who have the activity installed will see the invitation.

When someone accepts the invitation to join the activity a copy of the document is sent to his computer for him to read. When he exits the activity the document will be saved in the journal. The Journal entry will be titled "Read Etexts Activity", not the title of the book. Of course the recipient can modify this title to match the actual title of the book, but the activity currently will not do this for her.

This is a bit different from the core Read activity because I actually save a copy of the received document in the Journal, whereas Read does not. If you try to resume a shared Read activity when the document is not currently being shared you will get an empty document.

== Planned Features ==

* I plan to add another annotation feature that enables the user to highlight passages in the text. These highlights will be stored in the pickle file that will be included in the Zip file containing the document. When you share a document your highlights will go along with it.

== Bugs ==

* Text to speech does not work perfectly. The gstreamer plugin combined with newer versions of espeak works much better than the original speech-dispatcher code did, but in Sugar on a Stick on ''some'' machines the text highlighting lags badly behind the spoken words.

== Source ==

http://git.sugarlabs.org/projects/readetexts

== The Movie! ==

See the future of reading, here today, by watching [http://www.dailymotion.com/video/xa4bhu_readetexts-the-movie_tech Read Etexts: The Movie]. You are interested in the future, because it is where we will spend the rest of our lives. And remember my friends, future events such as these will affect you in the future.

[[Category:Activities]]