kdeconnect-kde/plugins/mpriscontrol
Albert Vaca 517c02451b Merge branch '0.9'
# Conflicts:
#	kdeconnect.appdata.xml
#	plugins/mprisremote/kdeconnect_mprisremote.json
#	plugins/ping/kdeconnect_ping.json
#	plugins/remotecontrol/kdeconnect_remotecontrol.json
2016-01-02 12:51:30 -08:00
..
CMakeLists.txt Remove unneeded dependency link 2015-04-10 18:03:49 +02:00
kdeconnect_mpriscontrol.json Merge branch '0.9' 2016-01-02 12:51:30 -08:00
mpriscontrolplugin.cpp Reordered lines 2015-11-11 11:03:00 -08:00
mpriscontrolplugin.h Watch all serivies with the watcher 2015-09-11 11:27:35 +02:00
mprisdbusinterface.xml Move the plugins into a different top-ĺevel directory 2014-06-14 16:34:11 +02:00
propertiesInterface.xml First approach to a KF5 port of KDE Connect 2014-06-16 20:02:07 +02:00
README Move the plugins into a different top-ĺevel directory 2014-06-14 16:34:11 +02:00

This plugin controls the playback of mpris-enabled applications in this device,
commanded by its counterpart in the other device that acts as a remote control.
That means both plugins are not symmetrical.

This plugins receives and sends packages with type kdeconnect.mpris.

It keeps a list of detected players it can control via MPRIS. When it receives
a package that contains the boolean "requestPlayerList" set to true, it will
send back the list of players in an array named "playerList". If a new player is
detected or a known one dissappears, it should also send this list. Note that
players are identified only by its name (its MPRIS Identity), so there can not
be two players with the same display name.

This plugins also reports the current song, extracted from MPRIS Metadata. It
should send it when it changes or when receiving a package containing a boolean
"requestNowPlaying" set to true.

The remote devices can send packages with commands to one of the players. Those
packages will contain a string "player" with the name of the player they want to
command and a string "action" with the name of an MPRIS call (like "Play",
"Next"...).

This plugin can also control the system volume. The peer device can send a
package with "requestVolume" set to true to ask for the current volume, or send
a package with "setVolume" set to an integer in the range [0,100] to change it.