Sugar Grane - Revision history

Edsiper: /* About your project */

2009-04-12T15:01:14Z

About your project

← Older revision		Revision as of 11:01, 12 April 2009
Line 81:		Line 81:
	launch a UI sugar_grane UI dialog asking to the user if he wants to switch to the session found.		launch a UI sugar_grane UI dialog asking to the user if he wants to switch to the session found.

	How to create a sugar-grande session in a mass storage device ?, add a '~~Portable~~' item in the main sugar menu with options to export, import, recover, etc.		How to create a sugar-grande session in a mass storage device ?, add a 'Mobile' or 'Grane' menu item in the main sugar menu with options
			such as export, import, recover, info, etc.

	* What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.		* What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.

Edsiper: /* About your project */

2009-04-12T14:58:58Z

About your project

← Older revision		Revision as of 10:58, 12 April 2009
Line 77:		Line 77:
	*--> Preferences/ -- User session preferences as colors, name, picture, list of friends, etc		*--> Preferences/ -- User session preferences as colors, name, picture, list of friends, etc

	using the proposed structure defined above, when a mass storage device is plugged, Journal will mount the device per default behavior and then we try to detect if exists a sugar-grane_unique_user_id directory, after validate the session.info file information and if everything is ok, we launch a UI sugar_grane UI dialog asking to the user if he wants to switch to the session found.		using the proposed structure defined above, when a mass storage device is plugged, Journal will mount the device per default behavior and then
			we try to detect if exists a sugar-grane_unique_user_id directory, after validate the session.info file information and if everything is ok, we
			launch a UI sugar_grane UI dialog asking to the user if he wants to switch to the session found.

			How to create a sugar-grande session in a mass storage device ?, add a 'Portable' item in the main sugar menu with options to export, import, recover, etc.

	* What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.		* What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.

Edsiper: /* About your project */

2009-04-12T14:55:30Z

About your project

← Older revision		Revision as of 10:55, 12 April 2009
Line 70:		Line 70:
	Also, is necessary to define a directory structure in the storage device in order to let sugar recognize that a sugar-grane is present, eg:		Also, is necessary to define a directory structure in the storage device in order to let sugar recognize that a sugar-grane is present, eg:

	sugar-grane_unique_user_id		sugar-grane_unique_user_id/
	\|		\|
	*--> session.info -- Information about the sugar-grane session as id, creation date, last updated, etc		*--> session.info -- Information about the sugar-grane session as id, creation date, last updated, etc
	*--> Activities/ -- Full activities		*--> Activities/ -- Full activities
	*--> Journal/ -- Journal information		*--> Journal/ -- Journal information
	*--> Preferences/ -- User session preferences as colors, name, picture, etc		*--> Preferences/ -- User session preferences as colors, name, picture, list of friends, etc


			using the proposed structure defined above, when a mass storage device is plugged, Journal will mount the device per default behavior and then we try to detect if exists a sugar-grane_unique_user_id directory, after validate the session.info file information and if everything is ok, we launch a UI sugar_grane UI dialog asking to the user if he wants to switch to the session found.

	* What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.		* What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.

Edsiper: /* About your project */

2009-04-12T14:45:36Z

About your project

← Older revision		Revision as of 10:45, 12 April 2009
Line 67:		Line 67:
	- Load journal information using given path		- Load journal information using given path
	- Set user information		- Set user information

	Also, is necessary to define a directory structure in the storage device in order to let sugar recognize that a sugar-grane is present, eg:		Also, is necessary to define a directory structure in the storage device in order to let sugar recognize that a sugar-grane is present, eg:

Edsiper: /* About your project */

2009-04-12T14:44:36Z

About your project

← Older revision		Revision as of 10:44, 12 April 2009
Line 63:		Line 63:
	* How it should work		* How it should work
	The main design of this project involves to patch the Sugar Core, adding the availability to reload different phases of the startup process as requested:		The main design of this project involves to patch the Sugar Core, adding the availability to reload different phases of the startup process as requested:

	- Read activities lists from given path		- Read activities lists from given path
	- Load journal information using given path		- Load journal information using given path
	- Set ~~current~~ user information		- Set user information

			Also, is necessary to define a directory structure in the storage device in order to let sugar recognize that a sugar-grane is present, eg:

	- Activities~~: Sugar read two main directories to get the~~ activities ~~list and then it build on fly the launcher for each one~~,		sugar-grane_unique_user_id
			\|
			*--> session.info -- Information about the sugar-grane session as id, creation date, last updated, etc
			*--> Activities/ -- Full activities
			*--> Journal/ -- Journal information
			*--> Preferences/ -- User session preferences as colors, name, picture, etc

Edsiper: /* About your project */

2009-04-12T14:38:07Z

About your project

← Older revision		Revision as of 10:38, 12 April 2009
Line 61:		Line 61:
	kid session to another Sugar environment if desired.		kid session to another Sugar environment if desired.

			* How it should work
			The main design of this project involves to patch the Sugar Core, adding the availability to reload different phases of the startup process as requested:
			- Read activities lists from given path
			- Load journal information using given path
			- Set current user information



			- Activities: Sugar read two main directories to get the activities list and then it build on fly the launcher for each one,



	* What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.		* What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.

Dfarning: fix camelcase links

2009-04-03T21:48:35Z

fix camelcase links

← Older revision		Revision as of 17:48, 3 April 2009
Line 98:		Line 98:
	[[Image:New-developer-challenge.png\|thumb\|right\|An example of the kind of screenshot of your first modification to your development environment which you should include in your application. Note that the drop-down menu text has Mel's email address in place of the word "Restart" - your screenshot should contain your email instead.]]		[[Image:New-developer-challenge.png\|thumb\|right\|An example of the kind of screenshot of your first modification to your development environment which you should include in your application. Note that the drop-down menu text has Mel's email address in place of the word "Restart" - your screenshot should contain your email instead.]]

	# We want to make sure that you can set up a [[~~DevelopmentTeam~~#Development_systems\|development environment]] before the summer starts. Please send us a link to a screenshot of your Sugar development environment with the following modification: when you hover over the XO-person icon in the middle of Home view, the drop-down text should have your email in place of "Restart." See the image on the right for an example. It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.		# We want to make sure that you can set up a [[Development Team#Development_systems\|development environment]] before the summer starts. Please send us a link to a screenshot of your Sugar development environment with the following modification: when you hover over the XO-person icon in the middle of Home view, the drop-down text should have your email in place of "Restart." See the image on the right for an example. It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.

	[http://www.olpcnews.com/images/olpc-chile.jpg http://www.olpcnews.com/images/olpc-chile.jpg] :D		[http://www.olpcnews.com/images/olpc-chile.jpg http://www.olpcnews.com/images/olpc-chile.jpg] :D

Edsiper: /* About your project */

2009-04-03T18:37:07Z

About your project

← Older revision		Revision as of 14:37, 3 April 2009
Line 57:		Line 57:
	and with grane we avoid that, both have different goals.		and with grane we avoid that, both have different goals.

	Grane will over Sugar and Sugar over a very customized OS environment for the running hardware. It will be designed to fast-switching between session around different		Grane will work over Sugar and Sugar over a very customized OS environment for the running hardware. It will be designed to fast-switching between session around different
	computers, computer just contain the Sugar environment and sugar-Grane do the dirty tasks. Also it will helps to do a hard copy from one		computers, computer just contain the Sugar environment and sugar-Grane do the dirty tasks. Also it will helps to do a hard copy from one
	kid session to another Sugar environment if desired.		kid session to another Sugar environment if desired.

Edsiper: /* About your project */

2009-04-03T18:33:56Z

About your project

← Older revision		Revision as of 14:33, 3 April 2009
Line 55:		Line 55:

	The big difference with Sugar_on_a_Stick, is that we don't keep the OS in the storage device, sugar_on_a_stick uses an OS very generic		The big difference with Sugar_on_a_Stick, is that we don't keep the OS in the storage device, sugar_on_a_stick uses an OS very generic
	and with ~~grain~~ we avoid that~~. Grane will over Sugar and Sugar over a very customized OS environment for the running hardware~~.		and with grane we avoid that, both have different goals.

	It will be designed to fast-switching between session around different computers, computer just contain the Sugar environment and sugar-Grane do		Grane will over Sugar and Sugar over a very customized OS environment for the running hardware. It will be designed to fast-switching between session around different
	the dirty tasks. Also it will helps to do a hard copy from one kid session to another Sugar environment if desired.		computers, computer just contain the Sugar environment and sugar-Grane do the dirty tasks. Also it will helps to do a hard copy from one
			kid session to another Sugar environment if desired.

Edsiper: /* About your project */

2009-04-03T18:32:12Z

About your project

← Older revision		Revision as of 14:32, 3 April 2009
Line 53:		Line 53:

	This implementation need to be done in the core of Sugar and integrated with Journal for data sync.		This implementation need to be done in the core of Sugar and integrated with Journal for data sync.

			The big difference with Sugar_on_a_Stick, is that we don't keep the OS in the storage device, sugar_on_a_stick uses an OS very generic
			and with grain we avoid that. Grane will over Sugar and Sugar over a very customized OS environment for the running hardware.

			It will be designed to fast-switching between session around different computers, computer just contain the Sugar environment and sugar-Grane do
			the dirty tasks. Also it will helps to do a hard copy from one kid session to another Sugar environment if desired.


	* What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.		* What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.