<br><br><div class="gmail_quote">2009/9/14 Sebastian Kügler <span dir="ltr"><<a href="mailto:sebas@kde.org">sebas@kde.org</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Saturday 12 September 2009 16:49:01 Alessandro Diaferia wrote:<br>
> I've had a look at the code and I feel it can be merged into<br>
> MediaCenterComponents since I plan to provide models to navigate through<br>
> webservices like picasa, youtube and so on. As from what i've achieved<br>
> with mediacenter there's already a good api to start writing a model for<br>
> both the youtube engine and this one.<br>
><br>
> Any objection? Suggestions from the kde-silk team?<br>
<br>
</div>It would be a good idea to make the "API" (names of sources, returned data) generic<br>
for image webservices, so it's easier to just exchange the dataengine in the<br>
background to use a different image webservice.<br></blockquote><div>+1<br>What do you think about a generic "API" for media sources in general, and then defining something more specific for each type (e.g. music, video, pictures..).<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;">
<br>
Otherwise, great, I'd say :)<br>
<font color="#888888">--<br>
sebas<br>
<br>
<a href="http://www.kde.org" target="_blank">http://www.kde.org</a> | <a href="http://vizZzion.org" target="_blank">http://vizZzion.org</a> | GPG Key ID: 9119 0EF9<br>
</font><br>_______________________________________________<br>
Plasma-devel mailing list<br>
<a href="mailto:Plasma-devel@kde.org">Plasma-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/plasma-devel" target="_blank">https://mail.kde.org/mailman/listinfo/plasma-devel</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Alessandro Diaferia<br>KDE Developer<br>