Google Code-In 2012: Difference between revisions
m →Tasks |
|||
| Line 44: | Line 44: | ||
|[[GoogleCodeIn2012/OSK|On-screen keyboard support]] || align=left | Enable touch for activities that use direct keyboard input. || 20 || || code || touch | |[[GoogleCodeIn2012/OSK|On-screen keyboard support]] || align=left | Enable touch for activities that use direct keyboard input. || 20 || || code || touch | ||
|- | |- | ||
|[[GoogleCodeIn2012/Homeview_image|Set background image]] || align=left | Implement the set background image on Home View Feature. || 40 || | |[[GoogleCodeIn2012/Homeview_image|Set background image]] || align=left | Implement the set background image on Home View Feature. || 40 || walterbender || code || sugar | ||
|- | |- | ||
|[[GoogleCodeIn2012/Multiple_homeview|Multiple Homeviews]] || align=left | Implement the multiple homeview feature || 60 || | |[[GoogleCodeIn2012/Multiple_homeview|Multiple Homeviews]] || align=left | Implement the multiple homeview feature || 60 || walterbender || code || sugar | ||
|- | |- | ||
|[[GoogleCodeIn2012/Toolbar_utils|Package toolbar utils]] || align=left | Package Sugar activity utilities || 2 || | |[[GoogleCodeIn2012/Toolbar_utils|Package toolbar utils]] || align=left | Package Sugar activity utilities || 2 || walterbender || code || toolkit | ||
|- | |- | ||
|[[GoogleCodeIn2012/Infoslicer-wikislices|Infoslicer enhancement (wikislices)]] || align=left | Extend the Infoslicer activity to be able to use the local content in the Wikislices project. || 20 || humitos || code || activity | |[[GoogleCodeIn2012/Infoslicer-wikislices|Infoslicer enhancement (wikislices)]] || align=left | Extend the Infoslicer activity to be able to use the local content in the Wikislices project. || 20 || humitos || code || activity | ||
| Line 56: | Line 56: | ||
|[[GoogleCodeIn2012/PyTurtle|Sugarize Python Turtle module]] || align=left | Will require port of the Python turtle module to GTK (currently it is QT) || 60 || || code || activity | |[[GoogleCodeIn2012/PyTurtle|Sugarize Python Turtle module]] || align=left | Will require port of the Python turtle module to GTK (currently it is QT) || 60 || || code || activity | ||
|- | |- | ||
|[[GoogleCodeIn2012/Nutrition|Turtle Art nutrition]] || align=left | Further develop the prototype Turtle Nutrition plug-in into a stand-alone activity. || 60 || | |[[GoogleCodeIn2012/Nutrition|Turtle Art nutrition]] || align=left | Further develop the prototype Turtle Nutrition plug-in into a stand-alone activity. || 60 || walterbender || code || activity | ||
|- | |- | ||
|[[GoogleCodeIn2012/Portfolio_videos|Portfolio videos]] || align=left | Add a mechanism for exporting .ogv (voice over still images) of a portfolio presentation || 40 || | |[[GoogleCodeIn2012/Portfolio_videos|Portfolio videos]] || align=left | Add a mechanism for exporting .ogv (voice over still images) of a portfolio presentation || 40 || walterbender || code || activity | ||
|- | |- | ||
|[[GoogleCodeIn2012/Journal_view|Unified journal view]] || align=left | Rather than viewing the details of a Journal entry on a separate page make the details appear in an expandable in-line format || 120 || || code || sugar | |[[GoogleCodeIn2012/Journal_view|Unified journal view]] || align=left | Rather than viewing the details of a Journal entry on a separate page make the details appear in an expandable in-line format || 120 || || code || sugar | ||
| Line 74: | Line 74: | ||
|[[GoogleCodeIn2012/Mallard|Implement help mechanism for activities using Mallard]] || align=left | Mallard is a markup language that makes it easy to provide user help. It would be a nice feature to add Mallard-like help to activities but is programmed in Mono. It would nice to have a native Python version accessed through a mechanism similar to the view source mechanism. || 60 || || code || sugar | |[[GoogleCodeIn2012/Mallard|Implement help mechanism for activities using Mallard]] || align=left | Mallard is a markup language that makes it easy to provide user help. It would be a nice feature to add Mallard-like help to activities but is programmed in Mono. It would nice to have a native Python version accessed through a mechanism similar to the view source mechanism. || 60 || || code || sugar | ||
|- | |- | ||
|[[GoogleCodeIn2012/Turtle_Art|Turtle Art tutorial]] || align=left | Write a Turtle Art introductory tutorial || 60 || | |[[GoogleCodeIn2012/Turtle_Art|Turtle Art tutorial]] || align=left | Write a Turtle Art introductory tutorial || 60 || walterbender || documentation/training || activity | ||
|- | |- | ||
|[[GoogleCodeIn2012/I18n_screeshots|Multilanguage screen-shots]] || align=left | 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?). || 60 || || documentation/training || i18n | |[[GoogleCodeIn2012/I18n_screeshots|Multilanguage screen-shots]] || align=left | 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?). || 60 || || documentation/training || i18n | ||
| Line 92: | Line 92: | ||
|[[GoogleCodeIn2012/FLOSSMANUAL_Sugar|Sugar FLOSS Manual]] || align=left | Update and add new content to the manual Sugar Manual || 20 || || documentation/training || doc | |[[GoogleCodeIn2012/FLOSSMANUAL_Sugar|Sugar FLOSS Manual]] || align=left | Update and add new content to the manual Sugar Manual || 20 || || documentation/training || doc | ||
|- | |- | ||
|[[GoogleCodeIn2012/MYOSA|Make your own Sugar activity]] || align=left | Update and add new content to the manual Make Your Own Sugar Activities || 40 || | |[[GoogleCodeIn2012/MYOSA|Make your own Sugar activity]] || align=left | Update and add new content to the manual Make Your Own Sugar Activities || 40 || nicestep || documentation/training || doc | ||
|- | |- | ||
|[[GoogleCodeIn2012/SVG_images|SVG internationalization]] || align=left | Research internationalization of SVG images. || 120 || || outreach/research || i18n | |[[GoogleCodeIn2012/SVG_images|SVG internationalization]] || align=left | Research internationalization of SVG images. || 120 || || outreach/research || i18n | ||
| Line 104: | Line 104: | ||
|[[GoogleCodeIn2012/Sugar_in_the_cloud|Sugar in the Cloud]] || align=left | Research the issues involved with porting Sugar to the Cloud. || 60 || || outreach/research || future | |[[GoogleCodeIn2012/Sugar_in_the_cloud|Sugar in the Cloud]] || align=left | Research the issues involved with porting Sugar to the Cloud. || 60 || || outreach/research || future | ||
|- | |- | ||
|[[GoogleCodeIn2012/Sugar_on_Android|Sugar on Android]] || align=left | Research the issues involved with porting Sugar to Android. || 120 || | |[[GoogleCodeIn2012/Sugar_on_Android|Sugar on Android]] || align=left | Research the issues involved with porting Sugar to Android. || 120 || aguirrea || outreach/research || future | ||
|- | |- | ||
|[[GoogleCodeIn2012/Sugar_and_CGG|Copyleft Games]] || align=left | Research how Sugar Labs might leverage the work of copyleftgames.org and CGG might leverage the work of Sugar Labs. || 20 || || outreach/research || activity | |[[GoogleCodeIn2012/Sugar_and_CGG|Copyleft Games]] || align=left | Research how Sugar Labs might leverage the work of copyleftgames.org and CGG might leverage the work of Sugar Labs. || 20 || || outreach/research || activity | ||