Activity Team/FAQ - Revision history

Quozl at 02:11, 17 January 2018

2018-01-17T02:11:42Z

← Older revision		Revision as of 22:11, 16 January 2018
Line 34:		Line 34:

	==== How do I adopt an orphaned Activity, or become an Activity co-maintainer ====		==== How do I adopt an orphaned Activity, or become an Activity co-maintainer ====
	:If you want to take on a maintainer-ship role for an Activity, try making contact and emailing the current maintainer first, they may be busy with other projects, or genuinely ~~MIA~~. If you get no response, ask the Activity Team on the [http://lists.sugarlabs.org/listinfo/sugar-devel Sugar developers mail list], they will try to make a decision within seven days and make contact the Infrastructure Team to change ownership for resources like the [http://bugs.sugarlabs.org bug tracker], [http://git.sugarlabs.org git repository], [http://activities.sugarlabs.org ASLO].		:If you want to take on a maintainer-ship role for an Activity, try making contact and emailing the current maintainer first, they may be busy with other projects, or genuinely missing in action. If you get no response, ask the Activity Team on the [http://lists.sugarlabs.org/listinfo/sugar-devel Sugar developers mail list], they will try to make a decision within seven days and make contact the Infrastructure Team to change ownership for resources like the [http://bugs.sugarlabs.org bug tracker], [http://git.sugarlabs.org git repository], [http://activities.sugarlabs.org ASLO].

	~~==== Help! I suddenly can't push to Gitorious! ====~~
	:The [http://osuosl.org/ OSUOSL] which hosts Gitorious has an aggressive IP blacklist policy. If you once were able to push but now cannot, send an email to support@osuosl.org requesting that your IP be removed from the blacklist.

	==== Is there a Commits mailing list? ====		==== Is there a Commits mailing list? ====
	:Instead of a commits list, we use the RSS feed at http://git.sugarlabs.org/events.atom. This tracks the activity (commits, branches, comments, merge requests) of all projects hosted on Gitorious. Commits of PO files by Pootle are tracked on the [http://lists.sugarlabs.org/listinfo/pootle-commits pootle-commits] list.		:No.

	==== How do I get a trac component associated with my project? ====		==== How do I get a trac component associated with my project? ====
	:File a [http://bugs.sugarlabs.org ticket] with the request. Please assign the ticket to the trac component, mark it as a task and don't forget to mention the name of your project and the default owner for the tickets.		:File a [http://bugs.sugarlabs.org ticket] with the request. Please assign the ticket to the trac component, mark it as a task and don't forget to mention the name of your project and the default owner for the tickets.

			:Or use GitHub issues feature.

	==== How do I analyze my activity's memory usage? ====		==== How do I analyze my activity's memory usage? ====
	:Please refer to these pages for assistance in understanding the memory usage patterns of activities and the shell and for detecting leaks: http://wiki.laptop.org/go/MemoryUsageAnalysis and http://wiki.laptop.org/go/Memory_leak_testing		:Please refer to these pages for assistance in understanding the memory usage patterns of activities and the shell and for detecting leaks: http://wiki.laptop.org/go/MemoryUsageAnalysis and http://wiki.laptop.org/go/Memory_leak_testing

	==== How does one ~~package~~ an activity? ====		==== How does one bundle an activity? ====
	:Save the [http://git.sugarlabs.org/projects/hello-world/repos/mainline/blobs/master/setup.py setup.py] file in the top directory of your activity development tree. To make an activity bundle, run the following code:		:Save the [http://git.sugarlabs.org/projects/hello-world/repos/mainline/blobs/master/setup.py setup.py] file in the top directory of your activity development tree. To make an activity bundle, run the following code:
	:{{Code\|python setup.py dist_xo}}		:{{Code\|python setup.py dist_xo}}
Line 89:		Line 88:
	<pre>		<pre>
	def get_hardware():		def get_hardware():
	""" Determine whether we are using XO 1.0, 1.5, or "unknown" hardware """		""" Determine whether we are using XO-1, XO-1.5, or "unknown" hardware """
	if _get_dmi('product_name') != 'XO':		if _get_dmi('product_name') != 'XO':
	return 'unknown'		return 'unknown'
Line 109:		Line 108:
	</pre></li>		</pre></li>
	</ol>		</ol>

			:Some activities have a hw.py file that explains further and supports later models.

	==== How do I tell Sugar that my activity does not write any data to the Journal? ====		==== How do I tell Sugar that my activity does not write any data to the Journal? ====
Line 114:		Line 115:
	:One of my activities is a game that does not produce any document in the journal. How do I inform Sugar?		:One of my activities is a game that does not produce any document in the journal. How do I inform Sugar?

	:~~Pass~~ to ~~Activity.__init__ create_jobject=False~~		:You cannot do this; there was a way to do it, but it was removed.
	~~<ol style="list-style-type:none">~~
	~~<li>~~
	~~<pre>~~
	~~class MyActivity(activity.Activity):~~
	~~def __init__(self~~, ~~handle):~~
	~~activity~~.~~Activity.__init__(self, handle, create_jobject=False)~~
	~~</pre></li>~~
	~~</ol>~~

	==== How do I run Sugar in a way that matches the proportions of the OLPC XO? ====		==== How do I run Sugar in a way that matches the proportions of the OLPC XO? ====

Quozl: /* How do I get my activity in the hands of students? */

2018-01-17T02:05:40Z

How do I get my activity in the hands of students?

← Older revision		Revision as of 22:05, 16 January 2018
Line 29:		Line 29:

	==== How do I get my activity in the hands of students? ====		==== How do I get my activity in the hands of students? ====
	:The absolute best way to get your activity out into the world is to attend ~~an [OLPC:Deployment_meetings OLPC~~ deployment meeting] and suggest it to the deployment representatives. They can test your activity and offer feedback, and will ultimately decide whether it ships.		:The absolute best way to get your activity out into the world is to attend a deployment meeting and suggest it to the deployment representatives. They can test your activity and offer feedback, and will ultimately decide whether it ships within their deployment.

	:Another good way is to post and promote your activity on [http://activities.sugarlabs.org/ activities.sugarlabs.org]~~. This will get your activity into the hands of the G1G1 community and can be a stepping stone to getting included in the [[Sugar on a Stick]] distribution and in OLPC deployments~~.		:Another good way is to post and promote your activity on [http://activities.sugarlabs.org/ activities.sugarlabs.org].

	==== How do I adopt an orphaned Activity, or become an Activity co-maintainer ====		==== How do I adopt an orphaned Activity, or become an Activity co-maintainer ====

Quozl: /* How do I use the Gtk+ Inspector? */

2017-12-02T02:18:16Z

How do I use the Gtk+ Inspector?

← Older revision		Revision as of 22:18, 1 December 2017
Line 164:		Line 164:
	cd Activities/HelloWorld.activity		cd Activities/HelloWorld.activity
	GTK_DEBUG=interactive sugar-activity .		GTK_DEBUG=interactive sugar-activity .

			Or, request the feature from your activity, like this;

			self.canvas.get_toplevel().set_interactive_debugging(True)

	Because Sugar Gtk+ activities are full screen, use Alt+Tab or Alt+Shift+Tab to switch between the inspector and the activity.		Because Sugar Gtk+ activities are full screen, use Alt+Tab or Alt+Shift+Tab to switch between the inspector and the activity.

Quozl at 02:07, 2 December 2017

2017-12-02T02:07:25Z

← Older revision		Revision as of 22:07, 1 December 2017
Line 155:		Line 155:

	For Gtk+ 3.0 activities, an interactive inspector is available.		For Gtk+ 3.0 activities, an interactive inspector is available.

			On Debian or Ubuntu distributions, install the libgtk-3-dev package;

			sudo apt install libgtk-3-dev

	Set the GTK_DEBUG environment variable to ''interactive'' before running an activity, like this;		Set the GTK_DEBUG environment variable to ''interactive'' before running an activity, like this;

Quozl: /* How do I use the Gtk+ Inspector? */

2017-04-03T06:54:40Z

How do I use the Gtk+ Inspector?

← Older revision		Revision as of 02:54, 3 April 2017
Line 162:		Line 162:

	Because Sugar Gtk+ activities are full screen, use Alt+Tab or Alt+Shift+Tab to switch between the inspector and the activity.		Because Sugar Gtk+ activities are full screen, use Alt+Tab or Alt+Shift+Tab to switch between the inspector and the activity.

			It can help with debugging to set the ''name'' property of widgets using program-specific names, so that the widget tree shown by the inspector can be related to the widget tree in the source code.

	See also		See also
	* https://developer.gnome.org/gtk3/stable/gtk-running.html		* https://developer.gnome.org/gtk3/stable/gtk-running.html
	* https://wiki.gnome.org/Projects/GTK+/Inspector		* https://wiki.gnome.org/Projects/GTK+/Inspector

Quozl: /* How do I use the Gtk+ Inspector? */

2017-04-03T06:07:02Z

How do I use the Gtk+ Inspector?

← Older revision		Revision as of 02:07, 3 April 2017
Line 163:		Line 163:
	Because Sugar Gtk+ activities are full screen, use Alt+Tab or Alt+Shift+Tab to switch between the inspector and the activity.		Because Sugar Gtk+ activities are full screen, use Alt+Tab or Alt+Shift+Tab to switch between the inspector and the activity.

	See also https://wiki.gnome.org/Projects/GTK+/Inspector		See also
			* https://developer.gnome.org/gtk3/stable/gtk-running.html
			* https://wiki.gnome.org/Projects/GTK+/Inspector

Quozl: /* How do I use debugging output and how do I set the debug level? */

2017-04-03T05:50:26Z

How do I use debugging output and how do I set the debug level?

← Older revision		Revision as of 01:50, 3 April 2017
Line 151:		Line 151:

	export SUGAR_LOGGER_LEVEL=debug		export SUGAR_LOGGER_LEVEL=debug

			==== How do I use the Gtk+ Inspector? ====

			For Gtk+ 3.0 activities, an interactive inspector is available.

			Set the GTK_DEBUG environment variable to ''interactive'' before running an activity, like this;

			cd Activities/HelloWorld.activity
			GTK_DEBUG=interactive sugar-activity .

			Because Sugar Gtk+ activities are full screen, use Alt+Tab or Alt+Shift+Tab to switch between the inspector and the activity.

			See also https://wiki.gnome.org/Projects/GTK+/Inspector

SAMdroid: Remove closed, fixed bug notes

2014-04-06T09:00:27Z

Remove closed, fixed bug notes

← Older revision		Revision as of 05:00, 6 April 2014
Line 122:		Line 122:
	activity.Activity.__init__(self, handle, create_jobject=False)		activity.Activity.__init__(self, handle, create_jobject=False)
	</pre></li>		</pre></li>
	~~<li>(But keep in mind http://bugs.sugarlabs.org/ticket/1714)</li>~~
	</ol>		</ol>

FGrose: /* How do I run Sugar Runner/emulator in a way that matches the resolution of the OLPC XO? */

2014-02-06T01:30:35Z

How do I run Sugar Runner/emulator in a way that matches the resolution of the OLPC XO?

← Older revision		Revision as of 21:30, 5 February 2014
Line 125:		Line 125:
	</ol>		</ol>

	==== How do I run Sugar ~~Runner/emulator~~ in a way that matches the ~~resolution~~ of the OLPC XO? ====		==== How do I run Sugar in a way that matches the proportions of the OLPC XO? ====

	:Running the emulator with {{Code\|sugar-runner --resolution 832x624}} or, on older versions, {{Code\|sugar-emulator -i 832x624}} will give a close match to the XO screen proportions, i.e., the toolbar will be a close match.		:Running the emulator with {{Code\|sugar-runner --resolution 832x624}} or, on older versions, {{Code\|sugar-emulator -i 832x624}} will give a close match to the XO screen proportions, i.e., the toolbar will be a close match.

FGrose: /* How do I run the Sugar emulator in a way that matches the resolution of the OLPC XO? */

2014-02-06T01:27:51Z

How do I run the Sugar emulator in a way that matches the resolution of the OLPC XO?

← Older revision		Revision as of 21:27, 5 February 2014
Line 125:		Line 125:
	</ol>		</ol>

	==== How do I run ~~the~~ Sugar emulator in a way that matches the resolution of the OLPC XO? ====		==== How do I run Sugar Runner/emulator in a way that matches the resolution of the OLPC XO? ====

	:Running the emulator with ~~<code>~~sugar-emulator -i 832x624 ~~</code>~~ give a close match to the XO screen proportions (e.g., the toolbar will be a close match).		:Running the emulator with {{Code\|sugar-runner --resolution 832x624}} or, on older versions, {{Code\|sugar-emulator -i 832x624}} will give a close match to the XO screen proportions, i.e., the toolbar will be a close match.

	==== How do I use debugging output and how do I set the debug level? ====		==== How do I use debugging output and how do I set the debug level? ====