Changes

no edit summary
Line 11: Line 11:  
{{TOCright}}
 
{{TOCright}}
   −
=== Turtle Art Nutrition ===
+
=== Turtle Art nutrition ===
    
Working with the maintainer of [[Activities/TurtleArt|Turtle Blocks]] to further develop the prototype [[Activities/TurtleArt#Nutrition|Turtle Nutrition plug-in]] into a stand-alone activity. In its current state, Turtle Nutrition is a plug-in to the Turtle Blocks application. The plug-in aims to raise awareness of nutritional values through visual programming elements.
 
Working with the maintainer of [[Activities/TurtleArt|Turtle Blocks]] to further develop the prototype [[Activities/TurtleArt#Nutrition|Turtle Nutrition plug-in]] into a stand-alone activity. In its current state, Turtle Nutrition is a plug-in to the Turtle Blocks application. The plug-in aims to raise awareness of nutritional values through visual programming elements.
Line 21: Line 21:  
''Contact'': [[User:Walter]]
 
''Contact'': [[User:Walter]]
   −
=== Portfolio Videos ===
+
=== Portfolio videos ===
    
Working with the maintainer of [[Activities/Portfolio|Portfolio]] to add a mechanism for exporting .ogv (voice over still images) of a portfolio presentation. This is a request that has come from deployments: they'd like to be able to post videos of student work, which is currently available as a slide show with audio voice-over.
 
Working with the maintainer of [[Activities/Portfolio|Portfolio]] to add a mechanism for exporting .ogv (voice over still images) of a portfolio presentation. This is a request that has come from deployments: they'd like to be able to post videos of student work, which is currently available as a slide show with audio voice-over.
Line 31: Line 31:  
''Contact'': [[User:Walter]]
 
''Contact'': [[User:Walter]]
   −
=== Unified Journal View ===
+
=== Unified journal view ===
    
Rather than viewing the details of a Journal entry on a separate page, the idea is to make the details appear in an expandabe in-line format on the main Journal view. The look and feel would be more like Google+ or Facebook. Performance will be a major challenge.
 
Rather than viewing the details of a Journal entry on a separate page, the idea is to make the details appear in an expandabe in-line format on the main Journal view. The look and feel would be more like Google+ or Facebook. Performance will be a major challenge.
Line 47: Line 47:  
''Contact'': [[User:Jelkner]]
 
''Contact'': [[User:Jelkner]]
   −
=== Background Image on Home View ===
+
=== Background image on Home View ===
    
Since we are replacing Hippo, it is relatively trivial to add a background image to the Home View. The image could be set from the Sugar control panel.
 
Since we are replacing Hippo, it is relatively trivial to add a background image to the Home View. The image could be set from the Sugar control panel.
Line 67: Line 67:  
''Contact'': [[User:Walter]]
 
''Contact'': [[User:Walter]]
   −
=== Plugin Support ===
+
=== Plugin support ===
    
A number of activities, notably [[Activities/TurtleArt#Plugins|Turtle Art]], are supporting plugins -- the ability to extend features by downloading additional modules. However, [[Activities/TurtleArt#How_to_install_a_plugin|the mechanism for installing plugins]] is anything but friendly. It would be nice to design a uniform plugin bundle type and modify the activity installer to recognize this new type. Caveats include dependencies -- presumably the plugin would take care of that -- and version control -- plugins are often incumbent upon a specific version of an activity. [http://activities.sugarlabs.org ASLO hosting]] should also be considered.
 
A number of activities, notably [[Activities/TurtleArt#Plugins|Turtle Art]], are supporting plugins -- the ability to extend features by downloading additional modules. However, [[Activities/TurtleArt#How_to_install_a_plugin|the mechanism for installing plugins]] is anything but friendly. It would be nice to design a uniform plugin bundle type and modify the activity installer to recognize this new type. Caveats include dependencies -- presumably the plugin would take care of that -- and version control -- plugins are often incumbent upon a specific version of an activity. [http://activities.sugarlabs.org ASLO hosting]] should also be considered.
Line 75: Line 75:  
''Contact'': [[User:Walter]]
 
''Contact'': [[User:Walter]]
   −
=== End-user Modifications of Sugar Source ===
+
=== End-user modifications of Sugar source ===
    
We have an existing mechanism for duplicating and modifying Sugar activities: a copy of the bundle can be creaed in ~/Activities, where it can be modified by the end user. We also have a mechanism for viewing the Sugar toolkit source, but no such convenient way for making changes without risking messing up the system. While it should be easy enough to make a duplicate copy in the user's home directory, and to change the Python paths to use the modified code, we need some mechanism -- presumably at boot -- to choose which version to run: the installed version or the modified version.
 
We have an existing mechanism for duplicating and modifying Sugar activities: a copy of the bundle can be creaed in ~/Activities, where it can be modified by the end user. We also have a mechanism for viewing the Sugar toolkit source, but no such convenient way for making changes without risking messing up the system. While it should be easy enough to make a duplicate copy in the user's home directory, and to change the Python paths to use the modified code, we need some mechanism -- presumably at boot -- to choose which version to run: the installed version or the modified version.
Line 83: Line 83:  
''Contact'': [[User:Walter]]
 
''Contact'': [[User:Walter]]
   −
=== Project Sharing Website ===
+
=== Project sharing website ===
 
Create a Project Hosting Site similar to the Scratch website where kids can share the projects they have created using various Sugar Activities.  The site should foster collaboration and sharing of projects.  The Web Site should be built using a free web framework so that it can be installed at deployment sites.  Some features include:
 
Create a Project Hosting Site similar to the Scratch website where kids can share the projects they have created using various Sugar Activities.  The site should foster collaboration and sharing of projects.  The Web Site should be built using a free web framework so that it can be installed at deployment sites.  Some features include:
   Line 99: Line 99:  
''Co-mentor'': [[User:dogi]]
 
''Co-mentor'': [[User:dogi]]
   −
=== Sugar as a Service Website ===
+
=== Sugar as a Service website ===
 
Create a Site for managing multiple "Sugar in a Browser" sessions like [https://one.treehouse.su/gar treehouse] or [http://cscott.net/junk/ta-broadway.png broadway gnome]
 
Create a Site for managing multiple "Sugar in a Browser" sessions like [https://one.treehouse.su/gar treehouse] or [http://cscott.net/junk/ta-broadway.png broadway gnome]
 
Some features include:
 
Some features include:
Line 108: Line 108:  
''Contact'': [[User:dogi]]
 
''Contact'': [[User:dogi]]
   −
=== Learn to program -- in Turtle Art ===
+
=== Learn to program in Turtle Art ===
    
In much the same way that [http://www.codecademy.com/courses/programming-intro/0#!/exercises/0] walks newbies through the basics of programming in Javascript, it would be nice to walk newbies through the basics of Turtle Art. There is already a provision within Turtle Art for programatically creating and moving blocks and executing program stacks. So it would be a matter of developing the exercises.
 
In much the same way that [http://www.codecademy.com/courses/programming-intro/0#!/exercises/0] walks newbies through the basics of programming in Javascript, it would be nice to walk newbies through the basics of Turtle Art. There is already a provision within Turtle Art for programatically creating and moving blocks and executing program stacks. So it would be a matter of developing the exercises.
Line 154: Line 154:  
''Contact'': [[User:Walter]]
 
''Contact'': [[User:Walter]]
   −
===Tam Tam For SoaS===
+
===Tam Tam for Sugar on a Stick ===
    
Develop a cross-platform version of Tam Tam Mini that will work with SoaS on most, if not all, PCs and Intel Macs.  Start with Tam Tam Mini to solve the problems (mostly sound) and add the other three Tam Tam Activities if time permits.
 
Develop a cross-platform version of Tam Tam Mini that will work with SoaS on most, if not all, PCs and Intel Macs.  Start with Tam Tam Mini to solve the problems (mostly sound) and add the other three Tam Tam Activities if time permits.