[maemo-developers] Integration with hildon desktop

From: Jeffrey Barish jeff_barish at earthlink.net
Date: Tue Oct 7 03:49:31 EEST 2008
Eero Tamminen wrote:

> Hi,
> 
> ext Jeffrey Barish wrote:
>> Thanks to everyone for the excellent suggestions.  I tried them all, but
>> nothing worked.
>> 
>> Here's a report on my latest effort.  I started with a known
>> working .desktop file and replaced the name of the other application with
>> the name of my application everywhere except the fields related to the
>> icon.  When I ran my program, I got the logo for the other application in
>> the menu but the default logo in the navigation bar.  I conclude that
>> there
>> must be something wrong in my program.  Maybe I did not Hildonize it
>> correctly, though I don't see anything wrong.  I'm thinking that I will
>> just run the application in full-screen mode so that no one can see that
>> the icon is wrong.
> 
> To see which WM_CLASS your application uses (i.e. does it correspond
> to what you've specified in the .desktop file), install "x-debug-tools"
> package[1], do "xprop|grep WM_CLASS" from SSH console and click your
> application window.
> 
> Or if you have your application running in Scratchbox, you can use
> the xprop tool from your Linux desktop[2], just tell it to use your
> Xephyr display.
> 
> By default Gtk sets the WM_CLASS to the name of the binary (not script
> calling it...).
> 
> 
> - Eero
> 
> [1] See: http://maemo.org/development/tools/
> [2] Depending on your distribution and its version, the package
>      name for that differs, it could be xbase-clients, x11-utils...

I don't specify the WM_CLASS in the .desktop file because the application
whose .desktop I stole doesn't specify it.  I tried previously putting
StartupWMClass in the .desktop file, but it had no effect.  In any case,
xprop reports that the WM_CLASS is the main Python module (not binary) in
my package.

FYI, I do not use Scratchbox.
-- 
Jeffrey Barish


More information about the maemo-developers mailing list