Development Team/Sugargame - Revision history

Quozl at 07:06, 12 July 2017

2017-07-12T07:06:04Z

← Older revision		Revision as of 03:06, 12 July 2017
Line 13:		Line 13:
	Get it from:		Get it from:

	http://~~git~~.sugarlabs~~.org/projects~~/sugargame		http://github.com/sugarlabs/sugargame

	And place it within your activity source. It is not part of Sugar. Remember to check back for updates when you are continuing development of your activity.		And place it within your activity source. It is not part of Sugar. Remember to check back for updates when you are continuing development of your activity.

Quozl: /* Sugargame */

2013-09-30T21:36:35Z

Sugargame

← Older revision		Revision as of 17:36, 30 September 2013
Line 4:		Line 4:
	programs to run well under Sugar.		programs to run well under Sugar.
	It is a fork of olcpgames, which is no longer maintained.		It is a fork of olcpgames, which is no longer maintained.

			What it does:

			* Wraps a Sugar activity around an existing Pygame program with few changes
			* Allows Sugar toolbars and other widgets to be added to the activity UI
			* Provides hooks for saving to and restoring from the Journal

	Get it from:		Get it from:
Line 9:		Line 15:
	http://git.sugarlabs.org/projects/sugargame		http://git.sugarlabs.org/projects/sugargame

	~~What~~ it ~~does:~~		And place it within your activity source. It is not part of Sugar. Remember to check back for updates when you are continuing development of your activity.

	* Wraps a Sugar activity around an existing Pygame program with few changes		You can find it in some activities already. It is so small that the duplication is unimportant.
	* Allows Sugar toolbars and other widgets to be added to the ~~activity UI~~
	* Provides hooks for saving to and restoring from the Journal

	== Using Sugargame ==		== Using Sugargame ==

Quozl: correct name is Pygame not PyGame

2013-09-30T21:33:21Z

correct name is Pygame not PyGame

← Older revision		Revision as of 17:33, 30 September 2013
Line 1:		Line 1:
	== Sugargame ==		== Sugargame ==

	Sugargame is a Python package which allows [http://www.pygame.org/ ~~PyGame~~]		Sugargame is a Python package which allows [http://www.pygame.org/ Pygame]
	programs to run well under Sugar.		programs to run well under Sugar.
	It is a fork of olcpgames, which is no longer maintained.		It is a fork of olcpgames, which is no longer maintained.
Line 11:		Line 11:
	What it does:		What it does:

	* Wraps a Sugar activity around an existing ~~PyGame~~ program with few changes		* Wraps a Sugar activity around an existing Pygame program with few changes
	* Allows Sugar toolbars and other widgets to be added to the activity UI		* Allows Sugar toolbars and other widgets to be added to the activity UI
	* Provides hooks for saving to and restoring from the Journal		* Provides hooks for saving to and restoring from the Journal
Line 19:		Line 19:
	See also [[Development Team/Sugargame/Examples]].		See also [[Development Team/Sugargame/Examples]].

	==== Wrapping a ~~PyGame~~ program ====		==== Wrapping a Pygame program ====

	To use Sugargame to Sugarize a ~~PyGame~~ program, set up an activity directory and copy the Sugargame package into it. For an example, see the directory named test, inside the Sugargame repository. It is in fact a Sugargame activity.		To use Sugargame to Sugarize a Pygame program, set up an activity directory and copy the Sugargame package into it. For an example, see the directory named test, inside the Sugargame repository. It is in fact a Sugargame activity.

	The activity directory should look something like this:		The activity directory should look something like this:

Manuq: /* Wrapping a Pygame program */

2013-09-30T15:52:15Z

Wrapping a Pygame program

← Older revision		Revision as of 11:52, 30 September 2013
Line 19:		Line 19:
	See also [[Development Team/Sugargame/Examples]].		See also [[Development Team/Sugargame/Examples]].

	==== Wrapping a ~~Pygame~~ program ====		==== Wrapping a PyGame program ====

	To use Sugargame to Sugarize a ~~Pygame~~ program, set up an activity directory and copy the Sugargame package to it.		To use Sugargame to Sugarize a PyGame program, set up an activity directory and copy the Sugargame package into it. For an example, see the directory named test, inside the Sugargame repository. It is in fact a Sugargame activity.

	The activity directory should look something like this:		The activity directory should look something like this:

Manuq: /* Sugargame */

2013-09-30T15:47:47Z

Sugargame

← Older revision		Revision as of 11:47, 30 September 2013
Line 1:		Line 1:
	== Sugargame ==		== Sugargame ==

	Sugargame is a Python package which allows [http://www.pygame.org/ ~~Pygame~~]		Sugargame is a Python package which allows [http://www.pygame.org/ PyGame]
	programs to run well under Sugar.		programs to run well under Sugar.
	It is fork of ~~the~~ olcpgames ~~framework~~, which is no longer as maintained.		It is a fork of olcpgames, which is no longer maintained.

			Get it from:

	http://git.sugarlabs.org/projects/sugargame		http://git.sugarlabs.org/projects/sugargame
Line 9:		Line 11:
	What it does:		What it does:

	* Wraps a Sugar activity around an existing ~~Pygame~~ program with few changes		* Wraps a Sugar activity around an existing PyGame program with few changes
	* Allows Sugar toolbars and other widgets to be added to the activity UI		* Allows Sugar toolbars and other widgets to be added to the activity UI
	* Provides hooks for saving to and restoring from the Journal		* Provides hooks for saving to and restoring from the Journal

Quozl: some parts of olpcgames have been maintained in some activities, so reduce the strength of the no maintenance assertion.

2012-04-11T00:47:39Z

some parts of olpcgames have been maintained in some activities, so reduce the strength of the no maintenance assertion.

← Older revision		Revision as of 20:47, 10 April 2012
Line 3:		Line 3:
	Sugargame is a Python package which allows [http://www.pygame.org/ Pygame]		Sugargame is a Python package which allows [http://www.pygame.org/ Pygame]
	programs to run well under Sugar.		programs to run well under Sugar.
	It is fork of the olcpgames framework, which is no longer maintained.		It is fork of the olcpgames framework, which is no longer as maintained.

	http://git.sugarlabs.org/projects/sugargame		http://git.sugarlabs.org/projects/sugargame

Quozl: move ancient history to end of page

2011-01-19T04:54:18Z

move ancient history to end of page

@@ Line 12: / Line 12: @@
 * Allows Sugar toolbars and other widgets to be added to the activity UI
 * Provides hooks for saving to and restoring from the Journal
 == Using Sugargame ==
@@ Line 128: / Line 105: @@
 the One Laptop per Child project.
-=== Changelog ===
+== Changelog ==
-====v1.1====
+===v1.1===
 * Fix bugs in event handling.  (Pablo Moleri)
 * Remove reference to gtk.Socket.get_window() method, which is missing in older versions of PyGTK.
-====v1.0====
+===v1.0===
 * Initial version of Sugargame

Quozl: add fix for keyboard focus to generate pygame keypress events

2011-01-19T04:52:02Z

add fix for keyboard focus to generate pygame keypress events

← Older revision		Revision as of 00:52, 19 January 2011
Line 42:		Line 42:
	==== Wrapping a Pygame program ====		==== Wrapping a Pygame program ====

	To use Sugargame to Sugarize a Pygame program, set up an activity directory and		To use Sugargame to Sugarize a Pygame program, set up an activity directory and copy the Sugargame package to it.
	copy the Sugargame package to it.

	The activity directory should look something like this:		The activity directory should look something like this:
Line 53:		Line 52:
	setup.py - Install script		setup.py - Install script

	To make the Activity class, start with test/TestActivity.py from the Sugargame		To make the Activity class, start with test/TestActivity.py from the Sugargame distribution.
	distribution.

	~~The activity should create a single PygameCanvas widget and call run_pygame on it.~~
	~~Pass the main loop function of the Pygame program~~.

			The activity must create a single PygameCanvas widget:
	self._canvas = sugargame.canvas.PygameCanvas(self)		self._canvas = sugargame.canvas.PygameCanvas(self)
	self.set_canvas(self._canvas)		self.set_canvas(self._canvas)

			The activity may assign keyboard focus to the PygameCanvas widget, so that keyboard events generate pygame events:
			self._canvas.grab_focus()

			The activity must call the run_pygame method of the PygameCanvas widget, passing the main loop function of the Pygame program.
	# Start the game running.		# Start the game running.
	self._canvas.run_pygame(self.game.run)		self._canvas.run_pygame(self.game.run)

	In your Pygame main loop, pump the GTK ~~message~~ loop:		In your Pygame main loop, you must pump the GTK event loop:

	while gtk.events_pending():		while gtk.events_pending():

Quozl: /* Support */

2011-01-19T04:46:03Z

Support

← Older revision		Revision as of 00:46, 19 January 2011
Line 126:		Line 126:

	It is loosely based on the source code to the olpcgames framework, developed by		It is loosely based on the source code to the olpcgames framework, developed by
	the One Laptop ~~Per~~ Child project.		the One Laptop per Child project.

	=== Changelog ===		=== Changelog ===

Wade: /* Adding Pygame to a PyGTK activity */

2010-06-27T17:34:08Z

Adding Pygame to a PyGTK activity

← Older revision		Revision as of 13:34, 27 June 2010
Line 102:		Line 102:
	pygame.display.set_mode(event.size, pygame.RESIZABLE)		pygame.display.set_mode(event.size, pygame.RESIZABLE)

			# Check the mouse position
			x, y = pygame.mouse.get_pos()

	# Clear Display		# Clear Display
	screen.fill((255,255,255)) #255 for white		screen.fill((255,255,255)) #255 for white