Planning for 2.0

[reuben firmin]

The ability to reliably switch soundcards. Currently if I swap out my
asoundrc to point to a new default, Amarok will successfully play a few
songs, but xine will then crash (unable to initialize sound device). Perhaps
the KDE4 sound system will make this work transparently, but it would be
neat if Amarok can be toughened up to cope.

On 2/17/07, Dan Meltzer <dwm2 at alfred.edu> wrote:
>
> Now that 2.0 runs It seems like a good time to start setting up plans for
> what and how things will be done.
>
>
> From What i've heard, the following things are/were planned:
>
> 1) Refactoring collectiondb
> 2) UI Redesign
> 3) Making amarok OS independant.
>
> I'm sure there are other things, but i don't recall what off the top of my
> head.
>
> My suggestion would be to do the first two in a branch (probably separate
> branches).  This allows trunk to be something we know works and a place to
> do 3) in as well as other fixes.  Are there other plans for 2.0?
>
>
> TO DEVELOPERS: Are there people who are planning on working in anything
> specific?
>
> TO USERS: What features do you think 2.0 should have that 1.4.5doesn't?  This is probably the best opportunity to add features, as
> everything is changing anyways.  What do you think Amarok needs to continue
> to be the best media player availible?  Making suggestions is no guarantee
> they will be implemented, but its more likely than not making suggestions.
>
> _______________________________________________
> 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/20070218/d4f5e5fe/attachment.html>