Bug 123769 - some ui changes/ advancements
Summary: some ui changes/ advancements
Status: RESOLVED NOT A BUG
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR wishlist
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
: 123770 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-03-17 08:47 UTC by Hristo Ivanov
Modified: 2006-06-11 12:32 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hristo Ivanov 2006-03-17 08:47:10 UTC
Version:           any (using KDE KDE 3.5.1)
Installed from:    Fedora RPMs
Compiler:          g++ 4.0.2 fedora-custom-made g++
OS:                Linux

Well, i'll just start.
**) some words for the panels
1) The statistics page
  It is confusing the way that statistics are handled in the new 1.4 betas. ALSO, i think that it is somewhat confusing in the earlier versions, too. (The statistics page i mean, the other statistics are fine). Why:
  First of all, it is not customizable. I want, for example, to display not the LAST 5 items, but to be able to tell amarok how much songs to display AND (which is done in the betas in some cryptic combo) to be able to tell what "recent" means (3 days for example). 
  Second: In the betas the statistics are split (bad) and much of the functionality is made in some strange tree-like interface (ugly, unfriendly and somewhat harder). It has fixed things in it, no customization at all (like the previous version). Note that when muich of the functionality is made its way into tabs, etc. people tend to NOT use the main menu for anything else than preferences. The statistics thing should be back (in my personal oppenion), but it should be a tab like the file browser, the collection browser, etc. Customizable, of course. I'm of the people who tend not to know exactly what "fast", "recent", etc. things mean.. For me, these are useless. Prefer "last x things", "first x things", "x months ago", etc.
2) The queue manager needs some polish
  First: Users should be able to edit their queue on the fly, when they make changes to the queue they should become available right that way
  Second: The buttons need to be explained some way. Icons are not so generic solution for all things :)
  Third: Assuming (First:), The OK and Cancel buttons are pointless. There should be some undo/redo in their place
3) Suggestions should be in some frendlier way, not displayed in khtml mode (some inprovements on the dynamic mode). I mean, some more songs to be suggested with, if available something like "similarity", or "virtual dj", etc, that some (music match jukebox) have (site for that should be nice). or an assistent to that thing.
4) For a future version:
  It'd be nice if done, just sounds very nice: beat matching so the next song can mix with the previous (mixes, remixes, etc... dj things would be very, very nice). Think of a graph that compares the output of the current song with some other song and some volume adjusting tools to fade out manually the mixed songs.
**) Generic things
  It should be clear enough that from ANY place, dialog, etc. double click means "play" where "play" adds the selected thing to the playlist and plays it.. (or, if something is already playing, queue that thing, etc.) Under thing, understand: when clicking on an artist, add everything of that artist. when clicking on album, add all the songs of the album. When clicking somewhere in the queue manager/statistics page, also.
  Also, middle click may be used too (queue songs, etc.)
Comment 1 Mark Kretschmann 2006-03-17 09:01:50 UTC
*** Bug 123770 has been marked as a duplicate of this bug. ***
Comment 2 Mark Kretschmann 2006-03-17 09:03:49 UTC
Sorry, bug reports containing multiple items are not allowed.
Comment 3 Hristo Ivanov 2006-03-17 12:16:03 UTC
Strange, it told me there was a database error while processing so that's why i hit the button twice. Apologies
Comment 4 Seb Ruiz 2006-03-22 15:00:43 UTC
We mean that you need to file a separate bug report for each issue.

one for the statistics, one for the queue manager etc.

we can't manage stuff which is bundled in together like this