Archive:D-Bus Server - Revision history

Karellen at 21:42, 2 August 2020

2020-08-02T21:42:34Z

← Older revision		Revision as of 21:42, 2 August 2020
Line 1:		Line 1:
	~~{{mininav\|[[Development]]}}~~

	{{Incomplete}}		{{Incomplete}}
Line 6:		Line 5:
	XBMC can receive and send commands through our internally embedded D-Bus Server and its API.		XBMC can receive and send commands through our internally embedded D-Bus Server and its API.

	The D-Bus Server in Kodi is currently "limited" but it supports [http://wiki.xmms2.xmms.se/wiki/Media_Player_Interfaces MPRIS (Media Player Remote Interfacing Specification)] which is somewhat standardized. The D-Bus Server in Kodi can do more or less same as the [[EventServer]] but the D-Bus interface is standard on most Linux distribution so a program that can control i.e. VLC through its D-Bus interface could quite easily control Kodi as well without modification. Note that in the context of this page, interface refers to interface in the sense of an API, not an interface through which a user interacts with a program.		The D-Bus Server in Kodi is currently "limited" but it supports [http://wiki.xmms2.xmms.se/wiki/Media_Player_Interfaces MPRIS (Media Player Remote Interfacing Specification)] which is somewhat standardized. The D-Bus Server in Kodi can do more or less same as the EventServer but the D-Bus interface is standard on most Linux distribution so a program that can control i.e. VLC through its D-Bus interface could quite easily control Kodi as well without modification. Note that in the context of this page, interface refers to interface in the sense of an API, not an interface through which a user interacts with a program.

	== Introduction ==		== Introduction ==
Line 21:		Line 20:
	XBMC can receive and send commands through our internally embedded D-Bus Server and its API.		XBMC can receive and send commands through our internally embedded D-Bus Server and its API.

	The D-Bus Server in Kodi is currently "limited" but it supports [http://wiki.xmms2.xmms.se/wiki/Media_Player_Interfaces MPRIS (Media Player Remote Interfacing Specification)] which is somewhat standardized. The D-Bus Server in Kodi can do more or less same as the [[EventServer]] but the D-Bus interface is standard on most Linux distribution so a program that can control i.e. VLC through its D-Bus interface could quite easily control Kodi as well without modification.		The D-Bus Server in Kodi is currently "limited" but it supports [http://wiki.xmms2.xmms.se/wiki/Media_Player_Interfaces MPRIS (Media Player Remote Interfacing Specification)] which is somewhat standardized. The D-Bus Server in Kodi can do more or less same as the EventServer but the D-Bus interface is standard on most Linux distribution so a program that can control i.e. VLC through its D-Bus interface could quite easily control Kodi as well without modification.

	==== Pros and Cons with D-Bus ====		==== Pros and Cons with D-Bus ====
	The D-Bus Server in Kodi is currently "limited" but it supports [http://wiki.xmms2.xmms.se/wiki/Media_Player_Interfaces MPRIS (Media Player Remote Interfacing Specification)] which is somewhat standardized. The D-Bus Server in Kodi can do more or less same as the [[EventServer]] but the D-Bus interface is standard on most Linux distribution so a program that can control i.e. VLC through its D-Bus interface could quite easily control Kodi as well without modification.		The D-Bus Server in Kodi is currently "limited" but it supports [http://wiki.xmms2.xmms.se/wiki/Media_Player_Interfaces MPRIS (Media Player Remote Interfacing Specification)] which is somewhat standardized. The D-Bus Server in Kodi can do more or less same as the EventServer but the D-Bus interface is standard on most Linux distribution so a program that can control i.e. VLC through its D-Bus interface could quite easily control Kodi as well without modification.

	==== Known caveats ====		==== Known caveats ====
Line 62:		Line 61:
	dbus-send --print-reply --session --dest="org.mpris.xbmc" /Player org.freedesktop.MediaPlayer.Stop		dbus-send --print-reply --session --dest="org.mpris.xbmc" /Player org.freedesktop.MediaPlayer.Stop

	~~[[Category:Manual]]~~		[[Category:Development-Archived]]
	[[Category:Development]]
	~~[[Category:Add~~-~~ons~~]]

Karellen: Karellen moved page D-Bus Server to Archive:D-Bus Server without leaving a redirect: Outdated

2020-08-02T21:41:45Z

Karellen moved page D-Bus Server to Archive:D-Bus Server without leaving a redirect: Outdated

← Older revision	Revision as of 21:41, 2 August 2020
(No difference)

NedBot: web link corrections for xbmc -> kodi

2015-05-13T00:40:29Z

web link corrections for xbmc -> kodi

← Older revision		Revision as of 00:40, 13 May 2015
Line 30:		Line 30:

	= Development of the D-Bus Server API and D-Bus Clients for Kodi =		= Development of the D-Bus Server API and D-Bus Clients for Kodi =
	http://trac.~~xbmc~~.~~org~~/ticket/6076 here is the ticket for the server, it shows the functionality.		http://trac.kodi.tv/ticket/6076 here is the ticket for the server, it shows the functionality.

	== Example demos of DBus usage (open source code) ==		== Example demos of DBus usage (open source code) ==

NedBot: Bot: Automated text replacement (- XBMC + Kodi )

2015-05-04T08:28:46Z

Bot: Automated text replacement (- XBMC + Kodi )

← Older revision		Revision as of 08:28, 4 May 2015
Line 6:		Line 6:
	XBMC can receive and send commands through our internally embedded D-Bus Server and its API.		XBMC can receive and send commands through our internally embedded D-Bus Server and its API.

	The D-Bus Server in ~~XBMC~~ is currently "limited" but it supports [http://wiki.xmms2.xmms.se/wiki/Media_Player_Interfaces MPRIS (Media Player Remote Interfacing Specification)] which is somewhat standardized. The D-Bus Server in ~~XBMC~~ can do more or less same as the [[EventServer]] but the D-Bus interface is standard on most Linux distribution so a program that can control i.e. VLC through its D-Bus interface could quite easily control ~~XBMC~~ as well without modification. Note that in the context of this page, interface refers to interface in the sense of an API, not an interface through which a user interacts with a program.		The D-Bus Server in Kodi is currently "limited" but it supports [http://wiki.xmms2.xmms.se/wiki/Media_Player_Interfaces MPRIS (Media Player Remote Interfacing Specification)] which is somewhat standardized. The D-Bus Server in Kodi can do more or less same as the [[EventServer]] but the D-Bus interface is standard on most Linux distribution so a program that can control i.e. VLC through its D-Bus interface could quite easily control Kodi as well without modification. Note that in the context of this page, interface refers to interface in the sense of an API, not an interface through which a user interacts with a program.

	== Introduction ==		== Introduction ==
Line 18:		Line 18:


	==== Why the D-Bus Server and its API is needed in ~~XBMC~~ ====		==== Why the D-Bus Server and its API is needed in Kodi ====
	XBMC can receive and send commands through our internally embedded D-Bus Server and its API.		XBMC can receive and send commands through our internally embedded D-Bus Server and its API.

	The D-Bus Server in ~~XBMC~~ is currently "limited" but it supports [http://wiki.xmms2.xmms.se/wiki/Media_Player_Interfaces MPRIS (Media Player Remote Interfacing Specification)] which is somewhat standardized. The D-Bus Server in ~~XBMC~~ can do more or less same as the [[EventServer]] but the D-Bus interface is standard on most Linux distribution so a program that can control i.e. VLC through its D-Bus interface could quite easily control ~~XBMC~~ as well without modification.		The D-Bus Server in Kodi is currently "limited" but it supports [http://wiki.xmms2.xmms.se/wiki/Media_Player_Interfaces MPRIS (Media Player Remote Interfacing Specification)] which is somewhat standardized. The D-Bus Server in Kodi can do more or less same as the [[EventServer]] but the D-Bus interface is standard on most Linux distribution so a program that can control i.e. VLC through its D-Bus interface could quite easily control Kodi as well without modification.

	==== Pros and Cons with D-Bus ====		==== Pros and Cons with D-Bus ====
	The D-Bus Server in ~~XBMC~~ is currently "limited" but it supports [http://wiki.xmms2.xmms.se/wiki/Media_Player_Interfaces MPRIS (Media Player Remote Interfacing Specification)] which is somewhat standardized. The D-Bus Server in ~~XBMC~~ can do more or less same as the [[EventServer]] but the D-Bus interface is standard on most Linux distribution so a program that can control i.e. VLC through its D-Bus interface could quite easily control ~~XBMC~~ as well without modification.		The D-Bus Server in Kodi is currently "limited" but it supports [http://wiki.xmms2.xmms.se/wiki/Media_Player_Interfaces MPRIS (Media Player Remote Interfacing Specification)] which is somewhat standardized. The D-Bus Server in Kodi can do more or less same as the [[EventServer]] but the D-Bus interface is standard on most Linux distribution so a program that can control i.e. VLC through its D-Bus interface could quite easily control Kodi as well without modification.

	==== Known caveats ====		==== Known caveats ====
	The D-Bus Server in ~~XBMC~~ is currently "limited".		The D-Bus Server in Kodi is currently "limited".

	= Development of the D-Bus Server API and D-Bus Clients for ~~XBMC~~ =		= Development of the D-Bus Server API and D-Bus Clients for Kodi =
	http://trac.xbmc.org/ticket/6076 here is the ticket for the server, it shows the functionality.		http://trac.xbmc.org/ticket/6076 here is the ticket for the server, it shows the functionality.

NedBot: Robot: Changing Category:XBMC Manual to Category:Manual

2014-11-17T21:19:28Z

Robot: Changing Category:XBMC Manual to Category:Manual

← Older revision		Revision as of 21:19, 17 November 2014
Line 62:		Line 62:
	dbus-send --print-reply --session --dest="org.mpris.xbmc" /Player org.freedesktop.MediaPlayer.Stop		dbus-send --print-reply --session --dest="org.mpris.xbmc" /Player org.freedesktop.MediaPlayer.Stop

	[[Category:~~XBMC~~ Manual]]		[[Category:Manual]]
	[[Category:Development]]		[[Category:Development]]
	[[Category:Add-ons]]		[[Category:Add-ons]]

NedBot: Robot: Substituting template: Name

2014-06-05T20:17:26Z

Robot: Substituting template: Name

← Older revision		Revision as of 20:17, 5 June 2014
Line 6:		Line 6:
	XBMC can receive and send commands through our internally embedded D-Bus Server and its API.		XBMC can receive and send commands through our internally embedded D-Bus Server and its API.

	The D-Bus Server in ~~{{name}}~~ is currently "limited" but it supports [http://wiki.xmms2.xmms.se/wiki/Media_Player_Interfaces MPRIS (Media Player Remote Interfacing Specification)] which is somewhat standardized. The D-Bus Server in ~~{{name}}~~ can do more or less same as the [[EventServer]] but the D-Bus interface is standard on most Linux distribution so a program that can control i.e. VLC through its D-Bus interface could quite easily control ~~{{name}}~~ as well without modification. Note that in the context of this page, interface refers to interface in the sense of an API, not an interface through which a user interacts with a program.		The D-Bus Server in XBMC is currently "limited" but it supports [http://wiki.xmms2.xmms.se/wiki/Media_Player_Interfaces MPRIS (Media Player Remote Interfacing Specification)] which is somewhat standardized. The D-Bus Server in XBMC can do more or less same as the [[EventServer]] but the D-Bus interface is standard on most Linux distribution so a program that can control i.e. VLC through its D-Bus interface could quite easily control XBMC as well without modification. Note that in the context of this page, interface refers to interface in the sense of an API, not an interface through which a user interacts with a program.

	== Introduction ==		== Introduction ==
Line 18:		Line 18:


	==== Why the D-Bus Server and its API is needed in ~~{{name}}~~ ====		==== Why the D-Bus Server and its API is needed in XBMC ====
	XBMC can receive and send commands through our internally embedded D-Bus Server and its API.		XBMC can receive and send commands through our internally embedded D-Bus Server and its API.

	The D-Bus Server in ~~{{name}}~~ is currently "limited" but it supports [http://wiki.xmms2.xmms.se/wiki/Media_Player_Interfaces MPRIS (Media Player Remote Interfacing Specification)] which is somewhat standardized. The D-Bus Server in ~~{{name}}~~ can do more or less same as the [[EventServer]] but the D-Bus interface is standard on most Linux distribution so a program that can control i.e. VLC through its D-Bus interface could quite easily control ~~{{name}}~~ as well without modification.		The D-Bus Server in XBMC is currently "limited" but it supports [http://wiki.xmms2.xmms.se/wiki/Media_Player_Interfaces MPRIS (Media Player Remote Interfacing Specification)] which is somewhat standardized. The D-Bus Server in XBMC can do more or less same as the [[EventServer]] but the D-Bus interface is standard on most Linux distribution so a program that can control i.e. VLC through its D-Bus interface could quite easily control XBMC as well without modification.

	==== Pros and Cons with D-Bus ====		==== Pros and Cons with D-Bus ====
	The D-Bus Server in ~~{{name}}~~ is currently "limited" but it supports [http://wiki.xmms2.xmms.se/wiki/Media_Player_Interfaces MPRIS (Media Player Remote Interfacing Specification)] which is somewhat standardized. The D-Bus Server in ~~{{name}}~~ can do more or less same as the [[EventServer]] but the D-Bus interface is standard on most Linux distribution so a program that can control i.e. VLC through its D-Bus interface could quite easily control ~~{{name}}~~ as well without modification.		The D-Bus Server in XBMC is currently "limited" but it supports [http://wiki.xmms2.xmms.se/wiki/Media_Player_Interfaces MPRIS (Media Player Remote Interfacing Specification)] which is somewhat standardized. The D-Bus Server in XBMC can do more or less same as the [[EventServer]] but the D-Bus interface is standard on most Linux distribution so a program that can control i.e. VLC through its D-Bus interface could quite easily control XBMC as well without modification.

	==== Known caveats ====		==== Known caveats ====
	The D-Bus Server in ~~{{name}}~~ is currently "limited".		The D-Bus Server in XBMC is currently "limited".

	= Development of the D-Bus Server API and D-Bus Clients for ~~{{name}}~~ =		= Development of the D-Bus Server API and D-Bus Clients for XBMC =
	http://trac.xbmc.org/ticket/6076 here is the ticket for the server, it shows the functionality.		http://trac.xbmc.org/ticket/6076 here is the ticket for the server, it shows the functionality.

NedBot: Bot: Automated text replacement (- XBMC + {{name}} )

2014-06-05T01:01:48Z

Bot: Automated text replacement (- XBMC + {{name}} )

← Older revision		Revision as of 01:01, 5 June 2014
Line 6:		Line 6:
	XBMC can receive and send commands through our internally embedded D-Bus Server and its API.		XBMC can receive and send commands through our internally embedded D-Bus Server and its API.

	The D-Bus Server in ~~XBMC~~ is currently "limited" but it supports [http://wiki.xmms2.xmms.se/wiki/Media_Player_Interfaces MPRIS (Media Player Remote Interfacing Specification)] which is somewhat standardized. The D-Bus Server in ~~XBMC~~ can do more or less same as the [[EventServer]] but the D-Bus interface is standard on most Linux distribution so a program that can control i.e. VLC through its D-Bus interface could quite easily control ~~XBMC~~ as well without modification. Note that in the context of this page, interface refers to interface in the sense of an API, not an interface through which a user interacts with a program.		The D-Bus Server in {{name}} is currently "limited" but it supports [http://wiki.xmms2.xmms.se/wiki/Media_Player_Interfaces MPRIS (Media Player Remote Interfacing Specification)] which is somewhat standardized. The D-Bus Server in {{name}} can do more or less same as the [[EventServer]] but the D-Bus interface is standard on most Linux distribution so a program that can control i.e. VLC through its D-Bus interface could quite easily control {{name}} as well without modification. Note that in the context of this page, interface refers to interface in the sense of an API, not an interface through which a user interacts with a program.

	== Introduction ==		== Introduction ==
Line 18:		Line 18:


	==== Why the D-Bus Server and its API is needed in ~~XBMC~~ ====		==== Why the D-Bus Server and its API is needed in {{name}} ====
	XBMC can receive and send commands through our internally embedded D-Bus Server and its API.		XBMC can receive and send commands through our internally embedded D-Bus Server and its API.

	The D-Bus Server in ~~XBMC~~ is currently "limited" but it supports [http://wiki.xmms2.xmms.se/wiki/Media_Player_Interfaces MPRIS (Media Player Remote Interfacing Specification)] which is somewhat standardized. The D-Bus Server in ~~XBMC~~ can do more or less same as the [[EventServer]] but the D-Bus interface is standard on most Linux distribution so a program that can control i.e. VLC through its D-Bus interface could quite easily control ~~XBMC~~ as well without modification.		The D-Bus Server in {{name}} is currently "limited" but it supports [http://wiki.xmms2.xmms.se/wiki/Media_Player_Interfaces MPRIS (Media Player Remote Interfacing Specification)] which is somewhat standardized. The D-Bus Server in {{name}} can do more or less same as the [[EventServer]] but the D-Bus interface is standard on most Linux distribution so a program that can control i.e. VLC through its D-Bus interface could quite easily control {{name}} as well without modification.

	==== Pros and Cons with D-Bus ====		==== Pros and Cons with D-Bus ====
	The D-Bus Server in ~~XBMC~~ is currently "limited" but it supports [http://wiki.xmms2.xmms.se/wiki/Media_Player_Interfaces MPRIS (Media Player Remote Interfacing Specification)] which is somewhat standardized. The D-Bus Server in ~~XBMC~~ can do more or less same as the [[EventServer]] but the D-Bus interface is standard on most Linux distribution so a program that can control i.e. VLC through its D-Bus interface could quite easily control ~~XBMC~~ as well without modification.		The D-Bus Server in {{name}} is currently "limited" but it supports [http://wiki.xmms2.xmms.se/wiki/Media_Player_Interfaces MPRIS (Media Player Remote Interfacing Specification)] which is somewhat standardized. The D-Bus Server in {{name}} can do more or less same as the [[EventServer]] but the D-Bus interface is standard on most Linux distribution so a program that can control i.e. VLC through its D-Bus interface could quite easily control {{name}} as well without modification.

	==== Known caveats ====		==== Known caveats ====
	The D-Bus Server in ~~XBMC~~ is currently "limited".		The D-Bus Server in {{name}} is currently "limited".

	= Development of the D-Bus Server API and D-Bus Clients for ~~XBMC~~ =		= Development of the D-Bus Server API and D-Bus Clients for {{name}} =
	http://trac.xbmc.org/ticket/6076 here is the ticket for the server, it shows the functionality.		http://trac.xbmc.org/ticket/6076 here is the ticket for the server, it shows the functionality.

Martijn at 21:00, 31 August 2013

2013-08-31T21:00:37Z

← Older revision		Revision as of 21:00, 31 August 2013
Line 1:		Line 1:
			{{mininav\|[[Development]]}}

	{{Incomplete}}		{{Incomplete}}
	__TOC__		__TOC__

Ned Scott: /* Example demos of DBus usage (open source code) */

2013-06-28T04:54:54Z

Example demos of DBus usage (open source code)

← Older revision		Revision as of 04:54, 28 June 2013
Line 63:		Line 63:
	[[Category:Development]]		[[Category:Development]]
	[[Category:Add-ons]]		[[Category:Add-ons]]
	~~[[Category:To-Do]]~~

>NedBot: Robot: Cosmetic changes

2013-05-06T20:22:51Z

Robot: Cosmetic changes

← Older revision		Revision as of 20:22, 6 May 2013
Line 1:		Line 1:
	{{Incomplete}}		{{Incomplete}}
	~~[[Category:XBMC Manual]]~~
	__TOC__		__TOC__

Line 61:		Line 60:
	dbus-send --print-reply --session --dest="org.mpris.xbmc" /Player org.freedesktop.MediaPlayer.Stop		dbus-send --print-reply --session --dest="org.mpris.xbmc" /Player org.freedesktop.MediaPlayer.Stop

			[[Category:XBMC Manual]]
	[[Category:Development]]		[[Category:Development]]
	[[Category:Add-ons]]		[[Category:Add-ons]]
	[[Category:To-Do]]		[[Category:To-Do]]