No subject

primarily isn't controlling the media player. Some examples:
* VoIP application that wants to automatically stop playback when there
is an incomming call
* IRC client script that announces current track
* "enqueue in mediaplayer" in contextmenu in filebrowser
* some alarm clock app that starts music playback with a specific track
5 minutes before the real alarm goes on.
* dock/panel-app for showing current song.
* script that automatically stops music when your bluetooth phone goes
out of range.
* headphone saver (like screensaver, but that shuts off music instead)
* whatever, if the functionality is provided unexpected uses tend to pop up.

With a common interface this kind of apps doesn't have to know about
different media players, they just fire off some dbus messages to a
standard place.

To serve its purpose it must be very easy for the application to
interface with the mediaplayer. Therefore the interface has to be as
simple as possible, containing only the basic stuff, no capabilities
negotiation should be needed.

 anders

-- 
This is the vlc-devel mailing-list, see http://www.videolan.org/vlc/
To unsubscribe, please read http://developers.videolan.org/lists.html