PyPackager
(→mClock.py) |
(Reviewed article, added info about py2deb/extras repo, removed Midgard tag) |
||
| Line 1: | Line 1: | ||
| - | + | For developers without a Linux-background and supporting hardware, getting into development on Maemo is most easily achieved by using [http://pymaemo.garage.maemo.org/ PyMaemo], the Python port for Maemo. Check the website for more information on how to program - this wiki page only explains how to package your final program for redistribution. | |
| - | + | Once you have an application, one remaining hurdle is the proper packaging of your app. This needs to be a Debian package, a *.deb file. As it is impossible to build such a package on Windows-based systems (different concept of permissions, no tools), you need to build it either on a Linux system - or you can directly do it on your Internet Tablet using the handy [http://khertan.net/softwares/pypackager.php PyPackager tool from Benoît Hervier, aka Khertan]. With it, you can simply select a source directory that then gets packaged into the final DEB file suitable for distribution over maemo.org downloads or your homepage (PS: If you plan to distribute your application using the integrated application manager and the extras repository, you must use another build process. Check the [[py2deb]] documentation for this). | |
| - | + | However, you need to properly structure your source directory to achieve maximum Maemo/Hildon desktop integration. This document shall explain this, using the [http://maemo.org/downloads/product/OS2008/mclock/ mClock] build process as an example. | |
| - | |||
== Prerequisites == | == Prerequisites == | ||
Revision as of 19:06, 7 October 2008
For developers without a Linux-background and supporting hardware, getting into development on Maemo is most easily achieved by using PyMaemo, the Python port for Maemo. Check the website for more information on how to program - this wiki page only explains how to package your final program for redistribution.
Once you have an application, one remaining hurdle is the proper packaging of your app. This needs to be a Debian package, a *.deb file. As it is impossible to build such a package on Windows-based systems (different concept of permissions, no tools), you need to build it either on a Linux system - or you can directly do it on your Internet Tablet using the handy PyPackager tool from Benoît Hervier, aka Khertan. With it, you can simply select a source directory that then gets packaged into the final DEB file suitable for distribution over maemo.org downloads or your homepage (PS: If you plan to distribute your application using the integrated application manager and the extras repository, you must use another build process. Check the py2deb documentation for this).
However, you need to properly structure your source directory to achieve maximum Maemo/Hildon desktop integration. This document shall explain this, using the mClock build process as an example.
Contents |
Prerequisites
- OpenSSH server installed on the device
- Using a SFTP client on the Windows computer (e.g. Bitvise Tunnelier)
Process in general
- Login as root
- Upload your source directory to wherever you want (I suggest MyDocs)
- Change the permissions on files that later need to be executable to 755
- Open Pypackager, add the necessary information, select a source folder, save the settings. Tap the wheel icon to build your package.
- Use the Maemo File Manager to open the resulting .deb filename. It should automatically launch the Programs Manager and start to install your app.
- Debug - Rinse - Repeat
The folder structure
MyDocs or whatever root
- mClock.png
- A 26x26 alpha transparency PNG with the icon that shall be included in the build as the package icon (as seen in the Programs Manager)
- mclock-pypackager
- The saved config file from PyPackager
- mclock-src
- the folder containing the source code; the structure of the subfolders must match the structure of how the app will be deployed on the system (read an intro to debain packaging such as the one reffered on the PyPackager homepage)
- usr
- the main subfolder, matches /usr
- bin
- folder containing the main executable, a mClock file with 755 permission, containing a link to the mClock.py file inside the lib/maemo subfolder
- lib
- folder with mClock subfolder containing all *.py files of the application
- share
- folder containing all elements responsible for Hildon integration
- applications/hildon subfolder
- contains a mClock.desktop file that defines how the mClock app appears in the Hildon menu system (Name, Subtitle when in Finger mode, Icon, Exec path, StartupWMClass to link running app to Task Navigator icon, corresponding service (only needed when doing communications over OSSO).
- dbus-1/services subfolder
- contains a mclock.service file that links the service name to the executable
- icons/hicolor subfolder
- contains PNG icons in two sizes, used by the Menu System (small one when in pen mode under 26x26\hildon; large one for finger mode under scalable/hildon, in a size of 48x48)
- mClock subfolder
- containing all resources used by the application that are NOT executables, such as images.
- pixmaps subfolder
- dontaining the 48x48 icon once again for other uses by the system (TODO: anybody knows what for exactly?)
That's it. Quite simple once you have set it up properly. One thing: try to use a lowercase-only application name. Unix is case-sensitive, and choosing a name such as mClock was stupid from me. Don't do it. I did run into all sorts of troubles....
The files
Information about the *.desktop and *.service files plus some tips about needed stuff inside your python app.
mClock.desktop file
[Desktop Entry] Version=1.0.0 Version of this file, NOT of the app. Keep it at 1.0.0 Encoding=UTF-8 Name=mClock Name of the app as seen in Menu Comment=Clock & day/night map Description of the app as seen as subtitle in Menu in Finger mode Exec=/usr/bin/mClock Link to the app Icon=mclock Name of our icon file, without the trailing .png part X-Icon-path=/usr/share/icons Path to the icon X-Window-Icon=mclock Name of our icon file, without the trailing .png part (again?!) Type=Application X-Osso-Service=com.nokia.mclock UST begin with com.nokia. due to a bug, anything else WONT work X-Osso-Type=application/x-executable StartupWMClass=mClock Only needed because it's a PyGame app (would be automatic with GTK)
mclock.service
All lower case just to be sure. Very simple content:
[D-BUS Service] Name=com.nokia.mclock MUST begin with com.nokia. due to a bug, anything else WONT work Exec=/usr/bin/mClock Link to the app
mClock.py
Some important snippets from my code...
The first one is to be set as early as wanted, it will make sure that the "Loading..." banner disappers. Only needed because this is a pure pygame app right now, wouldn't be needed when using GTK!
import os os.environ["SDL_VIDEO_X11_WMCLASS"]="mClock"
Later on, we need to connect to our osso service or the service daemon will kill our application!
osso_c = osso.Context("mclock", "0.2.1", False)
(However, don't ask me IF that version string has ANY relevance, I don't know)