Changes

Jump to navigation Jump to search
27 bytes added ,  10:43, 19 November 2012
Line 108: Line 108:  
! future || [[GoogleCodeIn2012/Sugar_on_Android|Sugar on Android]] || outreach/research || Research the issues involved with porting Sugar to Android.
 
! future || [[GoogleCodeIn2012/Sugar_on_Android|Sugar on Android]] || outreach/research || Research the issues involved with porting Sugar to Android.
 
|-
 
|-
! cgg || [[GoogleCodeIn2012/Sugar_and_CGG|Copyleft Games]] || outreach/research || Research how Sugar Labs might leverage the work of [copyleftgames.org CGG] and CGG might leverage the work of Sugar Labs.
+
! activity || [[GoogleCodeIn2012/Sugar_and_CGG|Copyleft Games]] || outreach/research || Research how Sugar Labs might leverage the work of [copyleftgames.org CGG] and CGG might leverage the work of Sugar Labs.
 
|-py3kPy
 
|-py3kPy
 
! future || [[GoogleCodeIn2012/Python3|Port to Python3]] || outreach/research || Research the issues we will encounter in [http://lwn.net/Articles/523465/ porting to Python 3]
 
! future || [[GoogleCodeIn2012/Python3|Port to Python3]] || outreach/research || Research the issues we will encounter in [http://lwn.net/Articles/523465/ porting to Python 3]
Line 124: Line 124:  
! i18n || [[GoogleCodeIn2012/Sugar_i18n_status|Sugar i18n]] || quality assurance || Do an analysis of which Sugar activities are lacking i18n support.
 
! i18n || [[GoogleCodeIn2012/Sugar_i18n_status|Sugar i18n]] || quality assurance || Do an analysis of which Sugar activities are lacking i18n support.
 
|-
 
|-
! ui || [[GoogleCodeIn2012/Special_needs|Special Needs]] || user interface || Analyze Sugar from the point of view of special needs and make recommendations for improvements.
+
! sugar || [[GoogleCodeIn2012/Special_needs|Special Needs]] || user interface || Analyze Sugar from the point of view of special needs and make recommendations for improvements.
 
|-
 
|-
! ui || [[GoogleCodeIn2012/Touch_UI|Touch UI]] || user interface || Help us design the Sugar affordances for Sugar on tablet computers (Sugar Touch).
+
! sugar || [[GoogleCodeIn2012/Touch_UI|Touch UI]] || user interface || Help us design the Sugar affordances for Sugar on tablet computers (Sugar Touch).
 
|-
 
|-
! ui || [[GoogleCodeIn2012/Maliit|On-screen Keyboard]] || user interface || Develop new Maliit keyboard files for additional languages(beyond those already developed by garycmartin).
+
! sugar || [[GoogleCodeIn2012/Maliit|On-screen Keyboard]] || user interface || Develop new Maliit keyboard files for additional languages(beyond those already developed by garycmartin).
 
|-
 
|-
! ui || [[GoogleCodeIn2012/Accelerometer|Accelerometer]] || user interface || Think of ways to further leverage the use of an accelerometer in Sugar (and other common sensors found in portable computing devices).
+
! sugar || [[GoogleCodeIn2012/Accelerometer|Accelerometer]] || user interface || Think of ways to further leverage the use of an accelerometer in Sugar (and other common sensors found in portable computing devices).
 
|-
 
|-
! ui || [[GoogleCodeIn2012/Assessment|Assessment]] || user interface || Assessing how Sugar is used by students. What is being learned? Survey students and teachers. How well does it deliver its goals?
+
! learning || [[GoogleCodeIn2012/Assessment|Assessment]] || user interface || Assessing how Sugar is used by students. What is being learned? Survey students and teachers. How well does it deliver its goals?
 
|-
 
|-
! ui || [[GoogleCodeIn2012/Feature_requests|New Features]] || user interface || Survey Sugar users to find out what UI features they want from Sugar in the future.
+
! future || [[GoogleCodeIn2012/Feature_requests|New Features]] || user interface || Survey Sugar users to find out what UI features they want from Sugar in the future.
 
|}
 
|}
  

Navigation menu