PyMaemo/HildonDesktop - Revision history

imported_>v13: Clarify that desktop activity manager usage is suggested for hildon-home widgets

2010-08-13T11:57:48Z

Clarify that desktop activity manager usage is suggested for hildon-home widgets

← Older revision		Revision as of 11:57, 13 August 2010
Line 163:		Line 163:
	</pre>		</pre>

	~~Note however that this~~ method may not ~~always~~ work ~~100%. The~~ old code may not be ~~always~~ unloaded. A ~~better~~ solution is to reload hildon-home using [http://maemo.org/downloads/product/Maemo5/actman/ Desktop Activity Manager]. Once you store the current desktop (e.g. with "activty new test; activity store test") you can re-load it using "activity load -f test". This will reload hildon-home and all its widgets.		This method may not work reliably for hildon-home widgets because the old code may not be fully unloaded. A solution is to reload hildon-home using [http://maemo.org/downloads/product/Maemo5/actman/ Desktop Activity Manager]. Once you store the current desktop (e.g. with "activty new test; activity store test") you can re-load it using "activity load -f test". This will reload hildon-home and all its widgets.

	Another way of debugging python widgets is to add this code at the beginning of the script:		Another way of debugging python widgets is to add this code at the beginning of the script:

imported_>v13: Add tip for reloading hildon-home using desktop activity manager

2010-08-13T11:52:49Z

Add tip for reloading hildon-home using desktop activity manager

← Older revision		Revision as of 11:52, 13 August 2010
Line 163:		Line 163:
	</pre>		</pre>

	Another way of debugging python widgets is to add this code at the ~~begining~~ of the script:		Note however that this method may not always work 100%. The old code may not be always unloaded. A better solution is to reload hildon-home using [http://maemo.org/downloads/product/Maemo5/actman/ Desktop Activity Manager]. Once you store the current desktop (e.g. with "activty new test; activity store test") you can re-load it using "activity load -f test". This will reload hildon-home and all its widgets.

			Another way of debugging python widgets is to add this code at the beginning of the script:
	<source lang="python">		<source lang="python">
	import sys		import sys

imported_>amigadave: /* Debugging tips */ fix typo

2010-08-12T14:05:38Z

Debugging tips: fix typo

← Older revision		Revision as of 14:05, 12 August 2010
Line 173:		Line 173:
	This will redirect stdout and stderr to <code>/tmp/mylog.log</code>. This means that all exceptions and all other output will be logged there. As a plus, the code can be given to testers and they will be able to report-back with the contents of the logfile.		This will redirect stdout and stderr to <code>/tmp/mylog.log</code>. This means that all exceptions and all other output will be logged there. As a plus, the code can be given to testers and they will be able to report-back with the contents of the logfile.

	However, '''do not''' use this by default in production systems. Use it '''only''' for debugging since the file will consume space in <code>/tmp</~~coe~~> and will only grow in size.		However, '''do not''' use this by default in production systems. Use it '''only''' for debugging since the file will consume space in <code>/tmp</code> and will only grow in size.

	[[Category:Python]]		[[Category:Python]]

imported_>amigadave: /* Debugging tips */ use

2010-08-12T14:05:09Z

Debugging tips: use <source>

← Older revision		Revision as of 14:05, 12 August 2010
Line 164:		Line 164:

	Another way of debugging python widgets is to add this code at the begining of the script:		Another way of debugging python widgets is to add this code at the begining of the script:
	<~~pre~~>		<source lang="python">
	import sys		import sys
	f=open('/tmp/mylog.log', 'at', buffering=1)		f=open('/tmp/mylog.log', 'at', buffering=1)
	sys.stdout=f		sys.stdout=f
	sys.stderr=f		sys.stderr=f
	</~~pre~~>		</source>

	This will redirect stdout and stderr to /tmp/mylog.log. This means that all exceptions and all other output will be logged there. As a plus, the code can be given to testers and they~~'ll~~ be able to report-back with the contents of the logfile.		This will redirect stdout and stderr to <code>/tmp/mylog.log</code>. This means that all exceptions and all other output will be logged there. As a plus, the code can be given to testers and they will be able to report-back with the contents of the logfile.

	However, ~~DON~~'T use this by default in production systems. Use it ~~ONLY~~ for debugging since the file will consume space in /tmp and will only grow in size.		However, '''do not''' use this by default in production systems. Use it '''only''' for debugging since the file will consume space in <code>/tmp</coe> and will only grow in size.

	[[Category:Python]]		[[Category:Python]]

imported_>v13: /* Debugging tips */

2010-08-12T13:05:04Z

Debugging tips

@@ Line 162: / Line 162: @@
 [sbox]> mv /tmp/hello_world_status_menu.desktop /usr/share/applications/hildon-status-menu/
 </pre>
 [[Category:Python]]

imported_>amigadave: Category:Python

2010-02-11T15:50:36Z

Category:Python

← Older revision		Revision as of 15:50, 11 February 2010
Line 162:		Line 162:
	[sbox]> mv /tmp/hello_world_status_menu.desktop /usr/share/applications/hildon-status-menu/		[sbox]> mv /tmp/hello_world_status_menu.desktop /usr/share/applications/hildon-status-menu/
	</pre>		</pre>

			[[Category:Python]]

imported_>lizardo: /* Testing the example */

2010-02-01T13:53:50Z

Testing the example

← Older revision		Revision as of 13:53, 1 February 2010
Line 66:		Line 66:
	</pre>		</pre>

	Save the example code shown above as /usr/lib/hildon-desktop/hello_world_home.py inside your FREMANTLE_X86 target. <b>Make sure the script has a valid Python module name, specially it should not have any dots or dashes on its name</b>. To be safe, use only alphanumeric characters and underscore.		Save the example code shown above as /usr/lib/hildon-desktop/hello_world_home.py inside your FREMANTLE_X86 target. <b>Make sure the script has a valid Python module name, specially it should not have any dots or dashes on its name</b>. To be safe, use only alphanumeric characters and underscore, plus the ".py" extension.

	Next, save the following text as /usr/share/applications/hildon-home/hello_world_home.desktop:		Next, save the following text as /usr/share/applications/hildon-home/hello_world_home.desktop:

imported_>lizardo: /* Testing the example */

2010-02-01T13:52:06Z

Testing the example

← Older revision		Revision as of 13:52, 1 February 2010
Line 66:		Line 66:
	</pre>		</pre>

	Save the example code shown above as ~~<b>~~/usr/lib/hildon-desktop/hello_world_home.py</b> ~~inside your FREMANTLE_X86 target~~. Next, save the following text as ~~<b>~~/usr/share/applications/hildon-home/hello_world_home.desktop~~</b>~~:		Save the example code shown above as /usr/lib/hildon-desktop/hello_world_home.py inside your FREMANTLE_X86 target. <b>Make sure the script has a valid Python module name, specially it should not have any dots or dashes on its name</b>. To be safe, use only alphanumeric characters and underscore.

			Next, save the following text as /usr/share/applications/hildon-home/hello_world_home.desktop:

	<pre>		<pre>

imported_>lizardo at 15:21, 12 November 2009

2009-11-12T15:21:09Z

← Older revision		Revision as of 15:21, 12 November 2009
Line 140:		Line 140:

	[[Image:Status-menu-2.png]]		[[Image:Status-menu-2.png]]

			== Debugging tips ==

			If a Python widget breaks for some reason, no error message will appear to the user. To debug the problem (in Scratchbox), you need to look at debug messages sent on the console where the UI was started.

			Debug messages for Home Widgets are shown by default. For Status Menu Widgets, you need to enable debug output by running these commands:

			<pre>
			[sbox]> pkill -f /usr/bin/hildon-status-menu
			[sbox]> DEBUG_OUTPUT=1 /usr/bin/hildon-status-menu &
			</pre>

			They will terminate the running hildon-status-menu process and start a new one with debug output enabled.

			To force reloading a plugin (so that you can get the error messages again), try moving the .desktop file out of the directory and adding it back, e.g.:

			<pre>
			[sbox]> mv /usr/share/applications/hildon-status-menu/hello_world_status_menu.desktop /tmp/
			[sbox]> mv /tmp/hello_world_status_menu.desktop /usr/share/applications/hildon-status-menu/
			</pre>

imported_>lizardo at 22:10, 18 October 2009

2009-10-18T22:10:28Z

← Older revision		Revision as of 22:10, 18 October 2009
Line 129:		Line 129:
	</pre>		</pre>

	~~Make sure~~ the ~~hildon desktop and hildon-status-menu are running~~. ~~For that, you can use~~ the ~~following commands:~~		Now start the SDK UI, if it is not already started. See the instructions on the [[Documentation/Maemo_5_Final_SDK_Installation#Starting.2FShutting_down_the_SDK_UI\|Maemo 5 SDK documentation page]]

	~~<pre>~~		The example status menu widget should appear as soon as the .desktop file is saved, as the plugin used in this example is of the permanent category. See the [[Documentation/Maemo_5_Developer_Guide/Application_Development/Writing_Desktop_Widgets#Status_Menu_widgets\|Maemo 5 Developer Guide]] for more information of status menu widgets categories.
	~~[sbox]> export DISPLAY=:2 # if you are using scratchbox + Xephyr~~
	~~[sbox]> af-sb-init.sh start~~
	~~[sbox]> run-standalone.sh maemo-summoner /usr/bin/hildon-status-menu.launch &~~
	~~</pre>~~

	The example status menu widget should appear as soon as ~~hildon-status-menu process~~ is ~~started~~, as the plugin used in this example is of the permanent category. See [~~http://wiki.maemo.org/~~Documentation/Maemo_5_Developer_Guide/Application_Development/Writing_Desktop_Widgets#Status_Menu_widgets] for more information of status menu widgets categories.

	This is a screenshot taken on Xephyr showing how the widget will look like:		This is a screenshot taken on Xephyr showing how the widget will look like: