<div dir="ltr"><br><br><div class="gmail_quote">On Mon, Jul 14, 2008 at 2:26 PM, Alex Merry <<a href="mailto:huntedhacker@tiscali.co.uk">huntedhacker@tiscali.co.uk</a>> 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's the point of the nowplaying data engine. It should abstract away media<br>
players. I'm thinking of separating out the actual media player interaction<br>
into a library (it shouldn't be too difficult to do, since I've designed it<br>
with that in mind from the start). Then new media players could be<br>
implemented as plugins, and this could be shared with the now listening plugin<br>
in Kopete, for example.<br>
<br>
Alex<font color="#888888"><br></font></blockquote></div><br>Actually, that's exactly what I was thinking (except I didn't know about Plasma::DataEngine before). The current NowPlaying plasmoid appears to be a subset of what I was going to do, so I'll work with it and submit my patches back here to avoid duplication of effort.<br>
<br>BTW, am I completely out of it here, or would it be a better idea to create an abstract DataEngine (say, NowPlayingDataEngine), and then create subclasses that implement different media players, but show the same interface, thus hiding most of the differences between data engines? I'm not sure how often DataEngines are created in memory during execution, so I'm trying to think about possible enhancements to speed here...<br>
</div>