D-BUS service names for maemo
 

Hi folks,

do you think it would be a good thing to consolidate all the d-bus service names that are available for us to use in Maemo.
Can we either use this thread as a sticky or create a wiki page for the same.

I dont have much info about the different services available but ive seen many useful ones being discussed in threads.
for example
for MCE services ==> here

Im sure there are more like bme , ive seen another for the mapper.

Can we all consolidate them here ?

and please restrict discussion to only listing the services and what they are for so we can keep it as a good reference.

If there is already such a place ( I did my search ;) ) , please redirect me to that thread and this can be ignored.

Im sure this would help a lot of developers including me to come up with more useful apps.
Feel free to correct me if Im not thinking right.

Re: D-BUS service names for maemo
 

I did find this, seems to also have a long list of DBUS stuff listed.

http://wiki.maemo.org/Phone_control

also the user Jebba also had a big list which just got moved.

http://wiki.maemo.org/User:Jebba/DBUS

im not sure if this is the exact stuff you are after though.

Re: D-BUS service names for maemo
 

thanks RipTorn
yes exactly the kind of stuff I would have liked to consolidate.
Ive seen more of them around, was wondering if we could get all those and list it here in one place.

Re: D-BUS service names for maemo
 

the wiki is part of the .maemo.org website so any extra stuff could go on there I would imagine. Not sure if there would be much point having a sticky post, but that up to the community I guess.

The wiki also has python examples as well that makes it easy for beginners,
(people like me :p)

Cheers
Rip

Re: D-BUS service names for maemo
 

Just added this to the wiki: http://wiki.maemo.org/Documentation/..._in_Freemantle. Hope it helps. I will add more when i have the time.

Re: D-BUS service names for maemo
 

Developing for Maemo 5 is much, much, much easier, 'cause of the existence of docs, api refs and wiki, 'cause of OS2008 developing experience. And I just miss the point again and again... Please, use search... Or use fantasy... Do you know 'bout 'dbus-inspector'? Now you do ;) Use it ;)
P.S. Nothing personal, just a long New Year holidays :)

Re: D-BUS service names for maemo
 

URL is bad, could you please correct it?

--denis

Re: D-BUS service names for maemo
 

From looking at Recent Changes, I guess he means: http://wiki.maemo.org/Documentation/..._in_Freemantle

I know it looks the same, but it clicks different!

Re: D-BUS service names for maemo
 

I was looking for the very same thing the other day. It's really annoying that the closed osso apps don't accept command-line parameters and also don't have a published dbus reference.

Anyway, here's information on opening a PDF with osso_pdfviewer. If anyone knows how to specify an initial magnification or fullscreen mode, please share.

http://talk.maemo.org/showthread.php?p=431990

Re: D-BUS service names for maemo
 

some useful stuff here, not to the point, but helps to attain d-bus enlightenment. ==> HERE

thanks to 412b for hinting dbus-inspector.

Re: D-BUS service names for maemo
 

this is what i had found out yesterday
its the list of dbus service interfaces , but im yet to find the services published by these different dbus daemons that are handled by these interaces.

You can find them on your N900 the list of interfaces used by the various dbus daemons.
just goto
/etc/dbus-1/system.d

if Ive missed to see something please report.

Re: D-BUS service names for maemo
 

just installed dbus-inspector on my N900.
Ran it , there were some errors :confused: and it shows nothing. just an empty window, doesnt list the interfaces or services.
is there some config I need to do ?

if this works this will definitely make up for the lack of documentation of interaces/services.
I also read that the services will show on the dbus-inspector only if the introspection has been implemented by the respective daemons. Dont know how that holds for maemo . ?

Re: D-BUS service names for maemo
 

No config is needed. Did you run it in XTerm? If you did, post the output. And one more thing to be told: it takes much time to introspect (partly because of the timeouts and slow CPU).

Introspection is partly supported in Maemo unfortunately, so still docs reading to be done.

Re: D-BUS service names for maemo
 

I ran it using ssh to get the error log. Its attached
The screenshot is also attached.

btw just another thing the refresh and quit buttons were working to touch.

Re: D-BUS service names for maemo
 

Well, you can patch a bit sources of dbus-inspector, according to last error in log dbus-inspector fails with None instead of String.

Re: D-BUS service names for maemo
 

Thanks, that didnt take me this post to figure out :rolleyes:
Im no expert in python, but ill try to patch it if I can in case nobody fixes it before.

Re: D-BUS service names for maemo
 

;)
It's quite easy, but having a device is a nice speed-up in fixing. Perhaps, a bit later I'll post patched version.

Re: D-BUS service names for maemo
 

Try this quick-patched version

Re: D-BUS service names for maemo
 

didnt work again :( . attached the error.
sorry ,i hadnt realized you didnt have a device to test it, would it not work on the ARMEL target in the SDK env (i mean just to test it ? )

anyways, if you would be working on it, you could send me the patched version to test anytime. ill try to have a look too myself when I can.

cheers

Re: D-BUS service names for maemo
 

In fact, there are no critical errors. Moreover, how much time did you let it to work? According to log introspection wasn't finished.

Just for testing purposes it can be run in the SDK, but only for testing. Python is target independent, so no difference should be there.

Re: D-BUS service names for maemo
 

kept it running for abt 18 minutes.
this time longer. same reponse, nothing on screen, and several errors just like in the attachment

Re: D-BUS service names for maemo
 

Hmm... There are 2 variants at the moment: someone with device can patch it
or wait until I have enough free time to find out the reasons... It seems to need a deeper dive into.