<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 15:06:35 Alessandro Diaferia wrote:<br>
> That's great! Do we want to keep the "API" on the DataEngine's query side<br>
> or do we want to provide a set of inherited DataEngines such as for<br>
> example Plasma::MediaContentsDataEngine ? But probably that's too much.<br>
<br>
</div>On the one hand, it would make sense to share some common code, on the other hand,<br>
having an abstract mediacontent engine might not be what we want (since DataEngine is<br>
already abstract enough and should work fine). I suspect that this is something we'll<br>
find out as we have code for more than one or two engines. That should give us a<br>
better feeling for how much abstraction makes sense here.<br></blockquote><div><br>+1 :)<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>
Cheers,<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><br clear="all"><br>-- <br>Alessandro Diaferia<br>KDE Developer<br>