Marble/MarbleDBus: Difference between revisions
No edit summary |
No edit summary |
||
Line 8: | Line 8: | ||
marble_pid="$(pidof marble)" | marble_pid="$(pidof marble)" | ||
</code> | </code> | ||
Then you can pass this PID to the actual qdbus call | Then you can pass this PID to the actual qdbus call | ||
Line 14: | Line 15: | ||
qdbus org.kde.marble-$marble_pid /MarbleWidget | qdbus org.kde.marble-$marble_pid /MarbleWidget | ||
</code> | </code> | ||
This call returns a list of all the methods that MarbleWidget supports. | This call returns a list of all the methods that MarbleWidget supports. | ||
Line 21: | Line 23: | ||
qdbus org.kde.marble-$marble_pid /MarbleWidget org.kde.MarbleWidget.zoomIn | qdbus org.kde.marble-$marble_pid /MarbleWidget org.kde.MarbleWidget.zoomIn | ||
</code> | </code> | ||
to zoom into the map. Note that for function calls you shouldn't pass the brackets "()". | to zoom into the map. Note that for function calls you shouldn't pass the brackets "()". |
Revision as of 16:39, 11 February 2009
Scripting Marble from the shell using D-BUS
MarbleWidget and MarbleMap provide their full amount of methods as a D-BUS Interface. Therefore you can easily create a shell-script to control Marble using the qdbus command line tool.
Before you start you need to find out the PID of the Marble process: In your script you can do it like this.
marble_pid="$(pidof marble)"
Then you can pass this PID to the actual qdbus call
qdbus org.kde.marble-$marble_pid /MarbleWidget
This call returns a list of all the methods that MarbleWidget supports.
From this list you can choose the one that you'd like to call, e.g.
qdbus org.kde.marble-$marble_pid /MarbleWidget org.kde.MarbleWidget.zoomIn
to zoom into the map. Note that for function calls you shouldn't pass the brackets "()".
As a convenient tool you can use qdbusviewer to get a graphical list of the interfaces and methods that get provided through D-BUS.
This article is a stub, please extend it.