Hi Max<br><br><div class="gmail_quote">On 29 May 2010 18:31, Maximilian Kossick <span dir="ltr"><<a href="mailto:maximilian.kossick@googlemail.com">maximilian.kossick@googlemail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
That approach is used quite successfully in Amarok's D-Bus API. There<br>
is a D-BUS method that allows external applications to query Amarok's<br>
collections (all collections, unlike earlier versions which had to use<br>
SQL, and broke horribly when Amarok's SQL schema changed). Amarok<br>
takes a XML string, and returns a list of maps continaing track<br>
metadata.<br>
<br></blockquote><div><br>Can you point me to the part of the source where the Amarok D-bus API is implemented. I read the source of the XmlQueryReader and XmlQueryWriter classes. I would like to make a small test implementation by converting a query to XML. Hence, I would like to refer to some code that already uses these classes, to get a better idea. <br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Theoretically the XML format does already support queries for other<br>
entities than tracks, it's just that the current D-BUS API does not<br>
support this.<br></blockquote><div><br>What other entities? Do you mean album, genre etc.. ?<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I think I've got a draft for a XSD lying around on my harddrive<br>
somewhere. I'll try to dig it up.<br>
<br></blockquote><div><br>That would be helpful<br><br>--<br>Varrun<br></div></div>