<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><BR><DIV><DIV>On Feb 7, 2007, at 1:53 PM, James Heaver wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite">On 07/02/07, <B class="gmail_sendername">Marcel Urech</B> <<A href="mailto:stokedfish@gmail.com">stokedfish@gmail.com</A>> wrote:<DIV><SPAN class="gmail_quote"></SPAN><BLOCKQUOTE class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> On Wednesday 07 February 2007 12:00:31 <A href="mailto:amarok-request@kde.org">amarok-request@kde.org</A> wrote:<BR><BR>> ok, I agree but this feature should be in "extension" not in amarok-core. I<BR>> would use it 3-4 times a year than ;] <BR>><BR>> In Amarok 2.0 there are going to be extensions like in Firefox so it is<BR>> good place for that sort of features.<BR><BR>What does it matter whether you call it plugin or extension?<BR>It would still be external and you'd still be ignoring your user's demand... </BLOCKQUOTE><DIV><BR><BR>Perhaps we approach this in a different way. <BR><BR>For me scripts seem a bit of a dark art. I've not invested the time to discover what scripts are out there which I might find useful, so for me any functionality that is provided by scripts is essentially non-existant. Maybe this is what needs to be tackled. Make the availability and discoverability of extensions much better. <BR></DIV></DIV></BLOCKQUOTE><DIV><BR class="khtml-block-placeholder"></DIV><DIV>++</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>I totally agree, I don't want to spend time figuring out how to deal with scripts. But on the other hand if extensions were implemented in the same way as Firefox it would be a no brainer. Select plugins from a list, click install, boom and you are all set. Doing it in this way also keeps some code out of "amarok core".</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><BR class="khtml-block-placeholder"></DIV>Niklas</DIV><DIV><BR><BLOCKQUOTE type="cite"><DIV><DIV><BR>Rather than making the features of this script, or that extension part of the core perhaps we should make extensions as a whole a part of the core amarok experience. <BR>When you first install Amarok you set up your media library, plug in your <A href="http://last.fm">last.fm</A> details etc etc AND go download your chosen extensions. Make it a matter of course and a central part of Amarok.<BR><BR><BR>James<BR></DIV><BR></DIV><BR><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">_______________________________________________</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Amarok mailing list</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A href="mailto:Amarok@kde.org">Amarok@kde.org</A></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A href="https://mail.kde.org/mailman/listinfo/amarok">https://mail.kde.org/mailman/listinfo/amarok</A></DIV> </BLOCKQUOTE></DIV><BR></BODY></HTML>