Just a clarification, I think the API the student had in mind was more along the lines of some sort of REST interface that online services could implement to make their content available to other sites and 3rd party programs. Not that such an API, if widely accepted, would not make defining a general service plugin a hell of a lot easier... :-)
<br><br>I am at work now, but will look through your <br><br><div><span class="gmail_quote">On 3/11/07, <b class="gmail_sendername">Jeff Mitchell</b> <<a href="mailto:kde-dev@emailgoeshere.com">kde-dev@emailgoeshere.com
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hey guys,<br><br>Today I had this odd feeling about SoC and checked the page to find out when
<br>signups are. Turns out it's due tomorrow. So I filled out the application<br>for us. I was very politic, played up our strengths, etc.<br><br>I just saw Nikolaj's email (coincidentally, seriously) and it sounds like the
<br>student might be interested in helping define the API and implement a Store<br>Plugin. I've done a (bit) of work on defining an API...I'll send out an<br>email with a very rough first draft (Umbrello doc) and explain a few things
<br>about it.<br><br>--Jeff<br>_______________________________________________<br>Amarok-devel mailing list<br><a href="mailto:Amarok-devel@kde.org">Amarok-devel@kde.org</a><br><a href="https://mail.kde.org/mailman/listinfo/amarok-devel">
https://mail.kde.org/mailman/listinfo/amarok-devel</a><br></blockquote></div><br>