Projects/Marble/MarbleDBus - Revision history

Neverendingo: Text replace - "" to ""

2011-06-29T20:57:33Z

Text replace - "</code>" to "</syntaxhighlight>"

Neverendingo: Text replace - "`" to ""`


2011-06-29T20:49:05Z
Text replace - "<code>" to "<syntaxhighlight lang="text">"

				
				
				
				
			
			← Older revision
			Revision as of 20:49, 29 June 2011
			
Line 5:
Line 5:
  Before you start you need to find out the PID of the Marble process: In your script you can do it like this.   Before you start you need to find out the PID of the Marble process: In your script you can do it like this.
    
− <code> + <syntaxhighlight lang="text">
  marble_pid="$(pidof marble)"   marble_pid="$(pidof marble)"
  </code>   </code>
Line 12:
Line 12:
  Then you can pass this PID to the actual qdbus call   Then you can pass this PID to the actual qdbus call
    
− <code> + <syntaxhighlight lang="text">
  qdbus org.kde.marble-$marble_pid /MarbleWidget   qdbus org.kde.marble-$marble_pid /MarbleWidget
  </code>   </code>
Line 20:
Line 20:
  From this list you can choose the one that you'd like to call, e.g.   From this list you can choose the one that you'd like to call, e.g.
    
− <code> + <syntaxhighlight lang="text">
  qdbus org.kde.marble-$marble_pid /MarbleWidget org.kde.MarbleWidget.zoomIn   qdbus org.kde.marble-$marble_pid /MarbleWidget org.kde.MarbleWidget.zoomIn
  </code>   </code>
Line 33:
Line 33:
    
  To shorten the following dbus calls, we use   To shorten the following dbus calls, we use
− <code> + <syntaxhighlight lang="text">
  marble_pid="$(pidof marble)"   marble_pid="$(pidof marble)"
  alias MCALL='qdbus org.kde.marble-${marble_pid} /MarbleWidget'   alias MCALL='qdbus org.kde.marble-${marble_pid} /MarbleWidget'
Line 39:
Line 39:
    
  Changing map themes can be done via   Changing map themes can be done via
− <code> + <syntaxhighlight lang="text">
  MCALL org.kde.MarbleWidget.setMapThemeId "earth/srtm/srtm.dgml"   MCALL org.kde.MarbleWidget.setMapThemeId "earth/srtm/srtm.dgml"
  MCALL org.kde.MarbleWidget.setMapThemeId "earth/openstreetmap/openstreetmap.dgml"   MCALL org.kde.MarbleWidget.setMapThemeId "earth/openstreetmap/openstreetmap.dgml"
Line 45:
Line 45:
    
  Move to a place, specified by longitude and latitude   Move to a place, specified by longitude and latitude
− <code> + <syntaxhighlight lang="text">
  MCALL org.kde.MarbleWidget.centerOn 8.8 53.2   MCALL org.kde.MarbleWidget.centerOn 8.8 53.2
  </code>   </code>
    
  Set the zoom   Set the zoom
− <code> + <syntaxhighlight lang="text">
  MCALL org.kde.MarbleWidget.zoomView 2000   MCALL org.kde.MarbleWidget.zoomView 2000
  </code>   </code>
Line 60:
Line 60:
    
  It is also possible to retrieve parameters from marble, e.g.   It is also possible to retrieve parameters from marble, e.g.
− <code> + <syntaxhighlight lang="text">
  MCALL org.freedesktop.DBus.Properties.Get org.kde.MarbleWidget latitude   MCALL org.freedesktop.DBus.Properties.Get org.kde.MarbleWidget latitude
  MCALL org.freedesktop.DBus.Properties.Get org.kde.MarbleWidget longitude   MCALL org.freedesktop.DBus.Properties.Get org.kde.MarbleWidget longitude
Line 74:
Line 74:
    
  Opening a gpx file should work via   Opening a gpx file should work via
− <code> + <syntaxhighlight lang="text">
  MCALL org.kde.MarbleWidget.openGpxFile /tmp/test.gpx   MCALL org.kde.MarbleWidget.openGpxFile /tmp/test.gpx
  </code>   </code>
Line 86:
Line 86:
  ===No MarbleWidget or MarbleMap===   ===No MarbleWidget or MarbleMap===
  <b>Problem:</b> Neither the MarbleMap nor the MarbleWidget interfaces are available in my installation, and qdbus complains:   <b>Problem:</b> Neither the MarbleMap nor the MarbleWidget interfaces are available in my installation, and qdbus complains:
− <code> + <syntaxhighlight lang="text">
  org.freedesktop.DBus.Error.UnknownObject (No such object path '/MarbleWidget')   org.freedesktop.DBus.Error.UnknownObject (No such object path '/MarbleWidget')
  </code>   </code>
Line 92:
Line 92:
  <b>Solution:</b> The D-BUS interface is only available in Marble trunk (and eventually in Marble >= 0.8). Additionally you need to make sure that the "BUILD_WITH_DBUS" cmake flag is set to "ON" once you are building Marble from the source code:   <b>Solution:</b> The D-BUS interface is only available in Marble trunk (and eventually in Marble >= 0.8). Additionally you need to make sure that the "BUILD_WITH_DBUS" cmake flag is set to "ON" once you are building Marble from the source code:
    
− <code> + <syntaxhighlight lang="text">
  cmake -DBUILD_WITH_DBUS=ON ../marble   cmake -DBUILD_WITH_DBUS=ON ../marble
  </code>   </code>



Arnd at 19:17, 8 March 2009
2009-03-08T19:17:45Z


				
				
				
				
			
			← Older revision
			Revision as of 19:17, 8 March 2009
			
Line 51:
Line 51:
  Set the zoom   Set the zoom
  <code>   <code>
− CALL org.kde.MarbleWidget.zoomView 2000 + MCALL org.kde.MarbleWidget.zoomView 2000
  </code>   </code>
    
Line 61:
Line 61:
  It is also possible to retrieve parameters from marble, e.g.   It is also possible to retrieve parameters from marble, e.g.
  <code>   <code>
− CALL org.freedesktop.DBus.Properties.Get org.kde.MarbleWidget latitude + MCALL org.freedesktop.DBus.Properties.Get org.kde.MarbleWidget latitude
− CALL org.freedesktop.DBus.Properties.Get org.kde.MarbleWidget longitude + MCALL org.freedesktop.DBus.Properties.Get org.kde.MarbleWidget longitude
− CALL org.freedesktop.DBus.Properties.Get org.kde.MarbleWidget zoom + MCALL org.freedesktop.DBus.Properties.Get org.kde.MarbleWidget zoom
  </code>   </code>
  to get the current latitude, longitude or zoom.   to get the current latitude, longitude or zoom.
Line 75:
Line 75:
  Opening a gpx file should work via   Opening a gpx file should work via
  <code>   <code>
−   CALL org.kde.MarbleWidget.openGpxFile /tmp/test.gpx + MCALL org.kde.MarbleWidget.openGpxFile /tmp/test.gpx
  </code>   </code>
  but gives: "Invalid number of parameters".   but gives: "Invalid number of parameters".





Arnd at 19:16, 8 March 2009
2009-03-08T19:16:33Z


				
				
				
				
			
			← Older revision
			Revision as of 19:16, 8 March 2009
			
Line 64:
Line 64:
  CALL org.freedesktop.DBus.Properties.Get org.kde.MarbleWidget longitude   CALL org.freedesktop.DBus.Properties.Get org.kde.MarbleWidget longitude
  CALL org.freedesktop.DBus.Properties.Get org.kde.MarbleWidget zoom   CALL org.freedesktop.DBus.Properties.Get org.kde.MarbleWidget zoom
− </code + </code>
  to get the current latitude, longitude or zoom.   to get the current latitude, longitude or zoom.
    



Arnd: Further qdbus examples; retrieving parameters from marble
2009-03-08T19:15:23Z
Further qdbus examples; retrieving parameters from marble

				
				
				
				
			
			← Older revision
			Revision as of 19:15, 8 March 2009
			
Line 29:
Line 29:
  As a convenient tool you can use <b>qdbusviewer</b> to get a graphical list of the interfaces and methods that get provided through D-BUS.   As a convenient tool you can use <b>qdbusviewer</b> to get a graphical list of the interfaces and methods that get provided through D-BUS.
    
  + 
  + === Further examples ===
  + 
  + To shorten the following dbus calls, we use
  + <code>
  + marble_pid="$(pidof marble)"
  + alias MCALL='qdbus org.kde.marble-${marble_pid} /MarbleWidget'
  + </code>
  + 
  + Changing map themes can be done via
  + <code>
  + MCALL org.kde.MarbleWidget.setMapThemeId "earth/srtm/srtm.dgml"
  + MCALL org.kde.MarbleWidget.setMapThemeId "earth/openstreetmap/openstreetmap.dgml"
  + </code>
  + 
  + Move to a place, specified by longitude and latitude
  + <code>
  + MCALL org.kde.MarbleWidget.centerOn 8.8 53.2
  + </code>
  + 
  + Set the zoom
  + <code>
  + CALL org.kde.MarbleWidget.zoomView 2000
  + </code>
  + 
  + Note that the range of values passed to zoomView
  + is defined  in the .dgml files, eg for
  + marble/data/maps/earth/openstreetmap/openstreetmap.dgml
  + the range is from 900 to 4000, while for bluemarble it is from 900 to 2400.
  + 
  + It is also possible to retrieve parameters from marble, e.g.
  + <code>
  + CALL org.freedesktop.DBus.Properties.Get org.kde.MarbleWidget latitude
  + CALL org.freedesktop.DBus.Properties.Get org.kde.MarbleWidget longitude
  + CALL org.freedesktop.DBus.Properties.Get org.kde.MarbleWidget zoom
  + </code
  + to get the current latitude, longitude or zoom.
  + 
  + Note that one has to go through org.freedesktop.DBus.Properties.Get
  + as latitude is not a method, but a property.
  + 
  +                
  + === Things which (currently) don't work ===
  + 
  + Opening a gpx file should work via
  + <code>
  +   CALL org.kde.MarbleWidget.openGpxFile /tmp/test.gpx
  + </code>
  + but gives: "Invalid number of parameters".
  + This might be a bug on  the qdbus side.
    
  ----------------   ----------------



Tampakrap at 10:59, 6 March 2009
2009-03-06T10:59:28Z


				
				
				
				
			
			← Older revision
			Revision as of 10:59, 6 March 2009
			
Line 40:
Line 40:
  </code>   </code>
    
− <b>Solution:</b> The D-BUS interface is only available in Marble trunk (and eventually in Marble >= 0.8). Additionally you need to make sure that the "BUILD_WITH_DBUS" cmake flag is set to "ON": + <b>Solution:</b> The D-BUS interface is only available in Marble trunk (and eventually in Marble >= 0.8). Additionally you need to make sure that the "BUILD_WITH_DBUS" cmake flag is set to "ON" once you are building Marble from the source code:
    
  <code>   <code>
  cmake -DBUILD_WITH_DBUS=ON ../marble   cmake -DBUILD_WITH_DBUS=ON ../marble
  </code>   </code>



Tampakrap at 10:58, 6 March 2009
2009-03-06T10:58:37Z


				
				
				
				
			
			← Older revision
			Revision as of 10:58, 6 March 2009
			
Line 35:
Line 35:
  ==Trouble shooting==   ==Trouble shooting==
  ===No MarbleWidget or MarbleMap===   ===No MarbleWidget or MarbleMap===
− <b>Problem:</b> Neither the MarbleMap nor the MarbleWidget interfaces are available in my installation (Debian lenny), and qdbus complains: + <b>Problem:</b> Neither the MarbleMap nor the MarbleWidget interfaces are available in my installation, and qdbus complains:
  <code>   <code>
  org.freedesktop.DBus.Error.UnknownObject (No such object path '/MarbleWidget')   org.freedesktop.DBus.Error.UnknownObject (No such object path '/MarbleWidget')





Tampakrap at 10:57, 6 March 2009
2009-03-06T10:57:38Z


				
				
				
				
			
			← Older revision
			Revision as of 10:57, 6 March 2009
			
Line 40:
Line 40:
  </code>   </code>
    
− <b>Solution:</b> ??? + <b>Solution:</b> The D-BUS interface is only available in Marble trunk (and eventually in Marble >= 0.8). Additionally you need to make sure that the "BUILD_WITH_DBUS" cmake flag is set to "ON":
  +  
  + <code>
  + cmake -DBUILD_WITH_DBUS=ON ../marble
  + </code>





Tampakrap at 06:49, 6 March 2009
2009-03-06T06:49:00Z


				
				
				
				
			
			← Older revision
			Revision as of 06:49, 6 March 2009
			
Line 30:
Line 30:
    
    
  + ----------------
  + ----------------
    
− This article is a stub, please extend it. + ==Trouble shooting==
  + ===No MarbleWidget or MarbleMap===
  + <b>Problem:</b> Neither the MarbleMap nor the MarbleWidget interfaces are available in my installation (Debian lenny), and qdbus complains:
  + <code>
  + org.freedesktop.DBus.Error.UnknownObject (No such object path '/MarbleWidget')
  + </code>
  +  
  + <b>Solution:</b> ???





Tackat at 16:39, 11 February 2009
2009-02-11T16:39:59Z


				
				
				
				
			
			← Older revision
			Revision as of 16:39, 11 February 2009
			
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 "()".

← Older revision		Revision as of 19:15, 8 March 2009
Line 29:		Line 29:
	As a convenient tool you can use <b>qdbusviewer</b> to get a graphical list of the interfaces and methods that get provided through D-BUS.		As a convenient tool you can use <b>qdbusviewer</b> to get a graphical list of the interfaces and methods that get provided through D-BUS.

		+
		+	=== Further examples ===
		+
		+	To shorten the following dbus calls, we use
		+	<code>
		+	marble_pid="$(pidof marble)"
		+	alias MCALL='qdbus org.kde.marble-${marble_pid} /MarbleWidget'
		+	</code>
		+
		+	Changing map themes can be done via
		+	<code>
		+	MCALL org.kde.MarbleWidget.setMapThemeId "earth/srtm/srtm.dgml"
		+	MCALL org.kde.MarbleWidget.setMapThemeId "earth/openstreetmap/openstreetmap.dgml"
		+	</code>
		+
		+	Move to a place, specified by longitude and latitude
		+	<code>
		+	MCALL org.kde.MarbleWidget.centerOn 8.8 53.2
		+	</code>
		+
		+	Set the zoom
		+	<code>
		+	CALL org.kde.MarbleWidget.zoomView 2000
		+	</code>
		+
		+	Note that the range of values passed to zoomView
		+	is defined in the .dgml files, eg for
		+	marble/data/maps/earth/openstreetmap/openstreetmap.dgml
		+	the range is from 900 to 4000, while for bluemarble it is from 900 to 2400.
		+
		+	It is also possible to retrieve parameters from marble, e.g.
		+	<code>
		+	CALL org.freedesktop.DBus.Properties.Get org.kde.MarbleWidget latitude
		+	CALL org.freedesktop.DBus.Properties.Get org.kde.MarbleWidget longitude
		+	CALL org.freedesktop.DBus.Properties.Get org.kde.MarbleWidget zoom
		+	</code
		+	to get the current latitude, longitude or zoom.
		+
		+	Note that one has to go through org.freedesktop.DBus.Properties.Get
		+	as latitude is not a method, but a property.
		+
		+
		+	=== Things which (currently) don't work ===
		+
		+	Opening a gpx file should work via
		+	<code>
		+	CALL org.kde.MarbleWidget.openGpxFile /tmp/test.gpx
		+	</code>
		+	but gives: "Invalid number of parameters".
		+	This might be a bug on the qdbus side.

	----------------		----------------

← Older revision		Revision as of 10:57, 6 March 2009
Line 40:		Line 40:
	</code>		</code>

−	<b>Solution:</b> ~~???~~	+	<b>Solution:</b> The D-BUS interface is only available in Marble trunk (and eventually in Marble >= 0.8). Additionally you need to make sure that the "BUILD_WITH_DBUS" cmake flag is set to "ON":
		+
		+	<code>
		+	cmake -DBUILD_WITH_DBUS=ON ../marble
		+	</code>

← Older revision		Revision as of 06:49, 6 March 2009
Line 30:		Line 30:


		+	----------------
		+	----------------

−	~~This article is a stub~~, ~~please extend it~~.	+	==Trouble shooting==
		+	===No MarbleWidget or MarbleMap===
		+	<b>Problem:</b> Neither the MarbleMap nor the MarbleWidget interfaces are available in my installation (Debian lenny), and qdbus complains:
		+	<code>
		+	org.freedesktop.DBus.Error.UnknownObject (No such object path '/MarbleWidget')
		+	</code>
		+
		+	<b>Solution:</b> ???