<br><br><div class="gmail_quote">2008/7/14 Chani <<a href="mailto:chanika@gmail.com">chanika@gmail.com</a>>:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div class="Wj3C7c">
<br>
</div></div>I'm not sure... what exactly would such plugins do? what sort of integration<br>
do you mean?</blockquote><div><br>I mean, where the plasmoid itself is programmed to use a generic class, and then each media player has a class that inherits from the generic class used. That way, all that has to be done to add support for a media player is to write a single class library. <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>
<br>
I'd imagine that, if it were done the Plasma Way, there would be a dataengine<br>
for each media player (or maybe just one for those that have that standard<br>
dbus interface I vaguely remember hearding of?), and then either one or<br>
several applets providing the UI... could you use essentially the same UI for<br>
any media player, or would they all have to be different?</blockquote><div><br>That is my intention (to use the same, or at least a very similar UI for all media players), but I'm not familiar with dataengines...<br>
<br>As for what XML has to do with this, one idea I had was to use a single XML file for each "media player driver", and then follow the instructions there to properly communicate with the media player chosen... <br>
</div></div>