[Tracker] using the dbus interface

["Dan Kuester" <dkuester colorado edu>]

Hi,

I'm looking into using tracker as the center of a heavily
metadata-oriented music playback application written in python (1).  I
chose tracker because I appreciate it as a user - especially for its
minimal resource consumption and strong support for interesting music
metadata.

Can anyone suggest the best way to embed search calls in python?  From
the code I've read in svn, dbus looks like the (only?) way.  While I
am all for dbus-foo, it has become clear that at tracker's
/org/freedesktop/tracker interfaces have not stabilized (2); this
combined with the lack of external documentation that I can find makes
me unsure about which methods are intended to be more stable.

Can anyone describe (or point me a the document which describes) which
dbus interfaces are meant to be deprecated or are unmaintained, and
which are more stable?  Am I far off base, and there is there a better
way for me to be making tracker calls?

Thanks everybody, and keep up the good work! :)
Dan Kuester

(1) Anybody who wants to bring up reactions to my desire to write yet
another music player is welcome to bring it up with me separately, but
I'm not interested in discussing this in this thread.

(2)  As an example, tracker_dbus_method_search_metadata seems
effectively disabled in src/trackerd/traker-search-search.c:

//      res = tracker_db_search_metadata (db_con, service, field,
text, offset, limit);
        res = NULL;

Further, the implementation comments (the only documentation?) seems
to be missing  to the dbus call.  Is this meant to be deprecated?