Summer of Code/2012 - Revision history

FGrose: application rejection notice

2012-04-24T16:00:24Z

application rejection notice

← Older revision		Revision as of 12:00, 24 April 2012
Line 1:		Line 1:
			{{Note/important\|Sorry\|Our application was rejected [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg13412.html] (item 2), so no project this year.}}

	Our application page is [http://www.google-melange.com/gsoc/org/application/google/gsoc2012/7284202].		Our application page is [http://www.google-melange.com/gsoc/org/application/google/gsoc2012/7284202].

Line 9:		Line 11:
	'''Note:''' Potential students, more project ideas can be found on our [[Features]] page.		'''Note:''' Potential students, more project ideas can be found on our [[Features]] page.

	~~{{TOCright}}~~		__TOC__

	=== Turtle Art nutrition ===		=== Turtle Art nutrition ===

Ritafreudenberg at 14:55, 16 March 2012

2012-03-16T14:55:18Z

← Older revision		Revision as of 10:55, 16 March 2012
Line 173:		Line 173:

	''Contact'': [[User:Ritafreudenberg]]		''Contact'': [[User:Ritafreudenberg]]

			===Finish Physical Etoys port to Sugar ===
			Level (Beginner, Intermediate, Advanced): Intermediate
			Possible mentor: Ricardo Moran
			Possible second mentor: ...

			Physical Etoys is an extension to Etoys that allows the user to communicate with robots as if they were virtual objects in the computer. With Physical Etoys, it becomes posible to program real world objects (such as robots) to perform any task you want, or sense the world and use that information to control virtual objects (such as drawings on the screen).
			The hardware platforms currently supported by Physical Etoys include: Arduino, Lego Mindstorms Nxt, Nintendo Wiimote, Microsoft Kinect, and others.
			Making Physical Etoys work in Sugar would bring a platform for teaching robotics to all Sugar users, letting each kid that owns a XO transform his laptop into a robot. The port is currently half finished, but it lacks some details that need to be taken care about in order to finally publish it.

			Technical Details:
			All Physical Etoys modules should work well in Linux and specifically in the XO laptop, this can involve porting some libraries and generally dealing with platform-specific issues. Finally, Physical Etoys will have to be wrapped as an Activity bundle for the XO.

			Benefits to the Student:
			The student will learn about the inside of Physical Etoys and its communication model with the outside world, making it work seamlessly in different platforms.

			Benefits to the Community:
			The Sugar community would gain a visual programming tool for teaching robotics that is based on a currently popular platform, as it is Etoys.

			''Contact'': [[User:Ritafreudenberg]]


	== Proposals Template ==		== Proposals Template ==

Godiard: /* Port GBrainy to Python */

2012-03-10T02:01:08Z

Port GBrainy to Python

← Older revision		Revision as of 22:01, 9 March 2012
Line 140:		Line 140:
	GBrainy have many good logic games, but is programed in Mono. We can put Mono inside a activity but is not ideal.		GBrainy have many good logic games, but is programed in Mono. We can put Mono inside a activity but is not ideal.
	The games are defined in xml files, and the UI is GTK and cairo, should be not very dificult to port it to python.		The games are defined in xml files, and the UI is GTK and cairo, should be not very dificult to port it to python.

			More info [https://live.gnome.org/gbrainy/Extending]

	''Contact'': [[User:Godiard]]		''Contact'': [[User:Godiard]]

Godiard: /* Implement a presentation mode in Fototoon */

2012-03-10T02:00:10Z

Implement a presentation mode in Fototoon

← Older revision		Revision as of 22:00, 9 March 2012
Line 136:		Line 136:
	''Contact'': [[User:Godiard]]		''Contact'': [[User:Godiard]]

			=== Port GBrainy to Python ===

			GBrainy have many good logic games, but is programed in Mono. We can put Mono inside a activity but is not ideal.
			The games are defined in xml files, and the UI is GTK and cairo, should be not very dificult to port it to python.

			''Contact'': [[User:Godiard]]

	=== Implement a robotics plugin for Turtle Art ===		=== Implement a robotics plugin for Turtle Art ===

Ritafreudenberg at 16:10, 9 March 2012

2012-03-09T16:10:56Z

← Older revision		Revision as of 12:10, 9 March 2012
Line 159:		Line 159:

	''Contact'': [[User:GrannieB]]		''Contact'': [[User:GrannieB]]

			===Collaboration in Etoys ===

			Develop a robust collaboration method in Etoys. Improving collaboration so that kids can easily share and control objects they created directly between computers.

			''Contact'': [[User:Ritafreudenberg]]

	== Proposals Template ==		== Proposals Template ==

Cjl: typo

2012-03-02T20:06:16Z

typo

← Older revision		Revision as of 16:06, 2 March 2012
Line 150:		Line 150:
	=== Implement help mechanism for activities using Mallard ===		=== Implement help mechanism for activities using Mallard ===

	[http://projectmallard.org/ 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, accessed through a mechanism similar to the view source mechanism. We need to sort through two issues: integration into Sugar and intergration into ~~out~~ i18n system.		[http://projectmallard.org/ 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, accessed through a mechanism similar to the view source mechanism. We need to sort through two issues: integration into Sugar and intergration into our i18n / L10n system.

	''Contact'': [[User:Walter]]		''Contact'': [[User:Walter]]

Walter at 18:28, 2 March 2012

2012-03-02T18:28:15Z

← Older revision		Revision as of 14:28, 2 March 2012
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.

CBigenho at 18:24, 2 March 2012

2012-03-02T18:24:48Z

← Older revision		Revision as of 14:24, 2 March 2012
Line 153:		Line 153:

	''Contact'': [[User:Walter]]		''Contact'': [[User:Walter]]

			===Tam Tam For SoaS===

			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.

			''Contact'': [[User:GrannieB]]

	== Proposals Template ==		== Proposals Template ==

Dogi: /* Project Sharing Website */

2012-03-02T17:53:36Z

Project Sharing Website

← Older revision		Revision as of 13:53, 2 March 2012
Line 95:		Line 95:
	* Multi-language support		* Multi-language support

	''Contact'': [[User:MrSteve]] [[User:dogi]]		''Contact'': [[User:MrSteve]]

			''Co-mentor'': [[User:dogi]]

	=== Sugar as a Service Website ===		=== Sugar as a Service Website ===

Tonyforster: /* Learn to program -- in Turtle Art */

2012-03-02T17:47:32Z

Learn to program -- in Turtle Art

← Older revision		Revision as of 13:47, 2 March 2012
Line 113:		Line 113:

	''Contact'': [[User:Walter]]		''Contact'': [[User:Walter]]

	''Co-mentor'': [[User:tonyforster]]		''Co-mentor'': [[User:tonyforster]]