Pierre Amadio opened a bug about this issue already way back:
https://bugs.maemo.org/show_bug.cgi?id=1475
(The bug is still set at "NEW").
Fred Pacquier wrote:
> Eero Tamminen a écrit :
>> So you've now verified that Exec part works, whether it's in
>> .desktop or .service file. What about the s
Eero Tamminen a écrit :
>
> So you've now verified that Exec part works, whether it's in
> .desktop or .service file. What about the service name,
> Does the service name in .desktop match the .service file?
> I don't really know D-BUS, but when looking at the maemoblocks
> stuff on the device:
>
Kimmo Hämäläinen a écrit :
> On Thu, 2007-11-29 at 15:20 -0800, ext Mike Morrison wrote:
>> On Nov 29, 2007 2:33 PM, Thomas D. Waelti <[EMAIL PROTECTED]> wrote:
>>> Something else: make sure your service name is something like
>>> com.nokia.yourapp, and NOT com.yourdomainname.yourapp or so...
>>>
Hi,
ext Fred Pacquier wrote:
> Thomas D. Waelti wrote :
>>> However, I have been unable to adapt the mClock example for the
>>> service file successfully. As soon as I reference the X-Osso-
>>> Service value in the desktop file, I get a lengthy "Loading..."
>>> banner and nothing else, even though
On Thu, 2007-11-29 at 15:20 -0800, ext Mike Morrison wrote:
> On Nov 29, 2007 2:33 PM, Thomas D. Waelti <[EMAIL PROTECTED]> wrote:
> > Something else: make sure your service name is something like
> > com.nokia.yourapp, and NOT com.yourdomainname.yourapp or so...
> > And in the osso context, only
On Fri 30 Nov 2007 00:33, "Thomas D. Waelti" <[EMAIL PROTECTED]> writes:
>
>> Thomas D. Waelti wrote :
However, I have been unable to adapt the mClock example for the
service file successfully. As soon as I reference the X-Osso-
Service value in the desktop file, I get a lengthy "Lo
On Nov 29, 2007 2:33 PM, Thomas D. Waelti <[EMAIL PROTECTED]> wrote:
> Something else: make sure your service name is something like
> com.nokia.yourapp, and NOT com.yourdomainname.yourapp or so...
> And in the osso context, only connect to the yourapp part of the service, not
> the full service
Exactly my feelings. Compared to development on Palm or Windows Mobile, this is
hell :-)
I spent 2-3 evenings on mClock, and at least a dozen on the packaging etc.
Something else: make sure your service name is something like
com.nokia.yourapp, and NOT com.yourdomainname.yourapp or so...
And in
Thomas D. Waelti wrote :
>> However, I have been unable to adapt the mClock example for the
>> service file successfully. As soon as I reference the X-Osso-
>> Service value in the desktop file, I get a lengthy "Loading..."
>> banner and nothing else, even though I call osso.Context() early in
>> m
> However, I have been unable to adapt the mClock example for the
> service file successfully. As soon as I reference the X-Osso-
> Service value in the desktop file, I get a lengthy "Loading..."
> banner and nothing else, even though I call osso.Context() early in
> my code. I must be missing some
Jesse, Levi, Eero, Thomas : thanks to all of you for your answers, hints
and links !
All were informative and useful. I hadn't realized till now that
pyGame/SDL apps were treated so specifically, and I'd been looking in
all the wrong places...
So, the trick with StartupWMClass in the desktop f
Please check my article in the wiki:
http://maemo.org/community/wiki/packagebuildingwithoutlinuxusingpypackager/
Hope it helps (even if you don't use pypackager)
Best regards
-Tom
>> By "well-behaved" I mean an app which appears as an icon in the
>> taskbar like a proper Hildon app.
>>
>> I hav
Hi,
ext Fred Pacquier wrote:
> By "well-behaved" I mean an app which appears as an icon in the taskbar
> like a proper Hildon app.
>
> I have copied and modified .desktop and .service files of such apps made
> with PyGTK, but pyGame seems different. If the .desktop doesn't
> reference an osso
> By "well-behaved" I mean an app which appears as an icon in the taskbar
> like a proper Hildon app.
>
> I have copied and modified .desktop and .service files of such apps made
> with PyGTK, but pyGame seems different. If the .desktop doesn't
> reference an osso service, the app starts from the m
By "well-behaved" I mean an app which appears as an icon in the taskbar
like a proper Hildon app.
I have copied and modified .desktop and .service files of such apps made
with PyGTK, but pyGame seems different. If the .desktop doesn't
reference an osso service, the app starts from the menu, but
15 matches
Mail list logo
