Editing PyMaemo/HildonDesktop

Warning: You are not logged in. Your IP address will be recorded in this page's edit history.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 1: Line 1:
-
= Python bindings for libhildondesktop =
+
== Python bindings for libhildondesktop ==
These bindings allow to create the so called Hildon Home and Status Menu applets (or widgets, in Maemo 5). It consists of two binary packages:
These bindings allow to create the so called Hildon Home and Status Menu applets (or widgets, in Maemo 5). It consists of two binary packages:
Line 6: Line 6:
* hildon-desktop-python-loader: this is a Hildon Desktop loader for Python plugins.
* hildon-desktop-python-loader: this is a Hildon Desktop loader for Python plugins.
-
== Migrating old Widgets to Maemo 5 ==
+
=== Migrating old Widgets to Maemo 5 ===
The libhildondesktop version in Maemo 5 contains some API changes that also reflect on the Python bindings. Namely, you should pay attention to the following differences when migrating Home/Status Widgets from older Maemo releases to Fremantle:
The libhildondesktop version in Maemo 5 contains some API changes that also reflect on the Python bindings. Namely, you should pay attention to the following differences when migrating Home/Status Widgets from older Maemo releases to Fremantle:
Line 19: Line 19:
* Remove the "hd_plugin_get_object" function and instead add a "hd_plugin_type" variable that points to the plugin main class.
* Remove the "hd_plugin_get_object" function and instead add a "hd_plugin_type" variable that points to the plugin main class.
-
== Example - Home widgets (Fremantle only) ==
+
=== Example - Home widgets (Fremantle only) ===
 +
 
 +
The code below was based on the C example that can be found on the maemo-examples package sources [https://garage.maemo.org/svn/maemoexamples/branches/fremantle-sdk-testing/maemo-examples/hello-world-home.c].
<pre>
<pre>
import gtk
import gtk
import hildondesktop
import hildondesktop
 +
 +
class HelloWorldButton(gtk.Button):
 +
    def __init__(self, padding):
 +
        gtk.Button.__init__(self)
 +
        icon_theme = gtk.icon_theme_get_default()
 +
        icon = icon_theme.load_icon("hello", 40, 0)
 +
        if icon is None:
 +
            icon = icon_theme.load_icon("qgn_list_gene_default_app", 40, 0)
 +
        icon_image = gtk.Image()
 +
        icon_image.set_from_pixbuf(icon)
 +
        icon_image.set_padding(padding, padding)
 +
        self.add(icon_image)
 +
        self.show_all()
class HelloWorldDialog(gtk.Dialog):
class HelloWorldDialog(gtk.Dialog):
Line 41: Line 56:
     def __init__(self):
     def __init__(self):
         hildondesktop.HomePluginItem.__init__(self)
         hildondesktop.HomePluginItem.__init__(self)
-
         button = gtk.Button("Hello")
+
         button = HelloWorldButton(10)
         button.connect("clicked", hello_world_dialog_show)
         button.connect("clicked", hello_world_dialog_show)
         button.show_all()
         button.show_all()
Line 66: Line 81:
</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, plus the ".py" extension.
+
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>:
-
 
+
-
Next, save the following text as /usr/share/applications/hildon-home/hello_world_home.desktop:
+
<pre>
<pre>
Line 78: Line 91:
</pre>
</pre>
-
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]]
+
Make sure the hildon desktop and hildon-home are running. For that, you can use the following commands:
 +
 
 +
<pre>
 +
[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-home.launch &
 +
</pre>
-
Now you need to add the newly installed home widget to the desktop. Follow these instructions to add it using the Hildon Desktop interface:
+
Now you need to add the newly installed home widget to the desktop. For that you can either manually add it to the <b>~/.config/hildon-desktop/home.plugins</b> file, or follow these instructions to add it using the Hildon Desktop interface:
# Click anywhere on the Maemo desktop background.
# Click anywhere on the Maemo desktop background.
Line 97: Line 116:
[[Image:Hello_world_home_python2.png]]
[[Image:Hello_world_home_python2.png]]
-
== Example - Status menu widgets (Fremantle only) ==
+
=== Example - Status menu widgets (Fremantle only) ===
The code below was based on the C example that can be found on the Maemo 5 Developer Guide [http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Application_Development/Writing_Desktop_Widgets#Status_Menu_widgets].
The code below was based on the C example that can be found on the Maemo 5 Developer Guide [http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Application_Development/Writing_Desktop_Widgets#Status_Menu_widgets].
<pre>
<pre>
 +
import gobject
import gtk
import gtk
import hildondesktop
import hildondesktop
class ExampleStatusPlugin(hildondesktop.StatusMenuItem):
class ExampleStatusPlugin(hildondesktop.StatusMenuItem):
 +
    __gtype_name__ = 'ExampleStatusPlugin'
 +
     def __init__(self):
     def __init__(self):
         hildondesktop.StatusMenuItem.__init__(self)
         hildondesktop.StatusMenuItem.__init__(self)
-
 
+
       
 +
        STATUS_AREA_EXAMPLE_ICON_SIZE = 22
         icon_theme = gtk.icon_theme_get_default()
         icon_theme = gtk.icon_theme_get_default()
-
         pixbuf = icon_theme.load_icon("general_email", 22, gtk.ICON_LOOKUP_NO_SVG)
+
         pixbuf = icon_theme.load_icon("general_email", STATUS_AREA_EXAMPLE_ICON_SIZE, gtk.ICON_LOOKUP_NO_SVG)
         self.set_status_area_icon(pixbuf)
         self.set_status_area_icon(pixbuf)
-
 
+
       
         label = gtk.Label("Example message")
         label = gtk.Label("Example message")
         self.add(label)
         self.add(label)
         self.show_all()
         self.show_all()
-
hd_plugin_type = ExampleStatusPlugin
+
def hd_plugin_get_object():
 +
    return gobject.new(ExampleStatusPlugin, plugin_id="example_status_plugin")
 +
 
 +
if __name__ == "__main__":
 +
    obj = hd_plugin_get_object()
 +
    obj.show_all()
 +
    gtk.main()
</pre>
</pre>
Line 131: Line 160:
</pre>
</pre>
-
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]]
+
Make sure the hildon desktop and hildon-status-menu are running. For that, you can use the following commands:
-
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.
+
<pre>
 +
[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:
Line 142: Line 177:
[[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>
 
-
 
-
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:
 
-
<source lang="python">
 
-
import sys
 
-
f=open('/tmp/mylog.log', 'at', buffering=1)
 
-
sys.stdout=f
 
-
sys.stderr=f
 
-
</source>
 
-
 
-
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</code> and will only grow in size.
 
-
 
-
[[Category:Python]]
 

Learn more about Contributing to the wiki.


Please note that all contributions to maemo.org wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see maemo.org wiki:Copyrights for details). Do not submit copyrighted work without permission!


Cancel | Editing help (opens in new window)