Re: [Tracker] Status of unimplemented dbus interfaces

["Mikkel Kamstrup Erlandsen" <mikkel kamstrup gmail com>]

2006/11/3, Jamie McCracken <jamiemcc blueyonder co uk>:

Julien wrote:
> Hello,
> these days, I am playing with python-fuse and tracker. I am currently
> trying to code a little demonstration of a fuse FS to browse 'Music'
> Services (by Album and Artist). In order to finish to code this, I need
> a few additions to the dbus interface.
>
> By chance Jamie McCracken already announced he will code the functions I
> need:
> * GetArtists - returns unique list of all artists (includes stats for no
> of tracks per artist)
> * GetAlbums - returns unique list of all album names (includes stats for
> no of tracks per album)
> * GetTracks - returns list of all music tracks
> * GetAlbumsByArtists - returns unique list of all albums for a specified
> artist (includes stats for no of tracks per album)
> * GetTracksByArtists - returns unique list of all tracks for a specified
> artist (includes stats for no of tracks per artist)
> * GetTracksByAlbum - returns unique list of all tracks for a specified
> album
>
> http://jamiemcc.livejournal.com/1657.html
>
>
> Is there any news about the status of such code?
>

these were postponed until LiveQuery support is implemented

We will be doing this stuff over the next month or so along with a new
improved metadata store. Some of it might change too as I suspect Music
Album is a separate first class object wrt music tracks so this needs
all glueing together.

The music interface will also be governed by what Rythmbox needs too as
its likely to be our biggest customer...

This might be a silly question (or simply answered somewhere I didn't look)... Why is this api needed anyway? Is it not possible with the current dbus api to get all items from the audio service with the metadata property audio.artist?

In case this is not possible, I'd rather suggest adding this more general api.

Cheers,
Mikkel