Comment 2 for bug 796149
Revision history for this message
| reacocard (reacocard) wrote Re: dbus communication | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Query isn't really intended to be machine-parsable, its main reason for existence is to support the --query commandline option, which is intended to be human-readable and which should therefore be translated.
At present, using GetTrackAttr is the best way to get machine-suitable values. We've been discussing this in IRC a bit though and are considering adding some new method (GetTrackAttrs?) that would dump all the metadata about the current track to XML and return that over DBUS, which would both be faster (when using many tags, since you only need one round-trip) and would make it much easier for clients to support a greater variety of information and formattings. We could also then implement --query on the client side and deprecate the DBUS Query method, since it doesn't really make sense as part of the api exposed to other applications.