<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 Monday 14 September 2009 14:21:38 Alessandro Diaferia wrote:<br>
> I can propose a draft. I think I'll discuss about it today live together<br>
> with Francesco.. I'll post the draft here as soon as i get something<br>
> convincing :)<br>
<br>
</div>Cool, looking forward to seeing it.<br>
<br>
Keep in mind that we'll want to do the same for other content sources as well. In the<br>
end, we might write applets for a "type of dataengine" and make the dataengine<br>
implementation that is used configurable. That way, we get content provider plugins<br>
for specific services.<br>
<br>
And we could even write tests for it :D<br>
<font color="#888888">--<br>
</font><div><div></div><div class="h5">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>
</div></div><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>That's great! Do we want to keep the "API" on the DataEngine's query side or do we want to provide a set of inherited DataEngines such as for example Plasma::MediaContentsDataEngine ? But probably that's too much.<br clear="all">
<br>-- <br>Alessandro Diaferia<br>KDE Developer<br>