Fullscreen-Interface and Amarok 2.0

[James Heaver]

Disclaimer - I'm still using 144 atm, and the last time I used the script
dialogue may have been before that.  If its changed since - fantastic!

But I can't stand the script dialogue.  It is nowhere near the ease of use
of firefox extensions.  I would be for having a web based interface which
can be, for example, accessed via the context browser.

Something along the lines of Firefox's extensions or even Linspire's CNR.

Out of the software I have installed extensions for, (which is limited)
firefox's is the only approach I have ever been happy with that I can
recall.

Especially in the music player world winamp and foobar are horrible.

I think this is yet another area that amarok should excel at and define what
is expected of a music player.


James

On 09/02/07, Jeff Mitchell <kde-dev at emailgoeshere.com> wrote:
>
> Quoting Niklas Nylund <ninylund at abo.fi>:
> > 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".
>
> You mean, exactly how it's done in Amarok 1.4?  Open Script Manager,
> click Get New Scripts, and you get a nice dialog that lets you select
> them, complete with descriptions and ratings.  Click one more button,
> the script is installed for you.
>
> Granted, things will change in A2 (how is still not yet determined)
> but seriously, how much easier do you want it?
>
> --Jeff
>
> _______________________________________________
> Amarok mailing list
> Amarok at kde.org
> https://mail.kde.org/mailman/listinfo/amarok
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/amarok/attachments/20070209/2a502851/attachment.html>