Bug 6086 - Rhapsody: Adding a track/album to library
: Rhapsody: Adding a track/album to library
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Rhapsody Direct
: unspecified
: PC Windows XP
: P3 minor (vote)
: ---
Assigned To: Andy Grundman
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-11-07 19:34 UTC by ndijulio
Modified: 2009-09-08 09:19 UTC (History)
3 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ndijulio 2007-11-07 19:34:36 UTC
Currently when you click on a track/album in the Now Playing Screen it takes you into another menu screen with info about the artist, etc.  The action items are located at the bottom:

Add album to library
Add track to library

These choices should be at the top of the menu.  In addition, we could reinforce the ADD icon here instead of text.  Once you select the item or press "Add," the confirmation would be better communicated by using the toast popup from the bottom similar to adding a playlist.  Currently, you go into another screen that is confusing on whether the addition has taken place.
Comment 1 Blackketter Dean 2007-11-07 19:59:38 UTC
Noah:  I have no idea what this is.  Is this in the web interface, the player interface or the Jive interface?  Can you give a little more info?
Comment 2 ndijulio 2007-11-07 20:11:28 UTC
The comment was made while using the Jive interface [under Rhapsody] navigating through Now Playing list of artist from a playlist.
Comment 3 Blackketter Dean 2007-11-08 09:30:22 UTC
Brian: can you review this as you look at the Jive UI?
Comment 4 Brian Dils 2007-11-26 19:14:19 UTC
I had kind of a hard time replicating this because of getting Rhapsody up and running, but I agree, the action items should be at the top and more prominent.  I think we discussed a similar such problem on the SC UI a few weeks back and came up with a similar solution.  If we can use the same layout that would be great.
Comment 5 Andy Grundman 2007-11-27 12:24:45 UTC
Please note that the same menu structure is used everywhere (player, web, Jive), you can't just change it for Jive.
Comment 6 Blackketter Dean 2007-12-26 13:55:10 UTC
Moving these items up closer to the top seems reasonable to me and reasonable to do for all UIs.  Is the logic for this ordering centralized, Andy?
Comment 7 Andy Grundman 2007-12-26 14:18:38 UTC
It's easy to move them, but are you sure you want to do that?  I find I hardly ever use add/remove and more often use the menu to find out more info about the track, and I'd hate having to always scroll past add or remove items.
Comment 8 Blackketter Dean 2007-12-27 08:28:57 UTC
The real question is: 

Do action items always bubble to the top?  

I think that the answer is yes.

This would include, when appropriate:

Play
Add
Play All
Add All
Add Album To Library
Remove Album From Library
Add Track To Library
Remove Track From Library

etc...

Brian: do you agree?
Comment 9 Brian Dils 2008-01-07 16:32:12 UTC
I'd have to see it in action, but I think I would agree
Comment 10 Andy Grundman 2008-01-08 12:52:53 UTC
Done, I've moved all the add/remove Rhapsody items to the top.
Comment 11 y360 2008-01-21 02:19:32 UTC
Right clicking a Rhapsody playlist in production SN loads the tracklist and shows the first track which is what one might expect.

In SN beta however, same action shows a metadata of the playlist with "tracks" as the fourth item and "remove playlist from library" as the first menu item.

This is counter-intuitive. When I click through into a playlist I expect to play it or browse its tracks, not delete it.
Removing a playlist using SB3 is much less common than wanting to get into the playlist

Also, it is all too easy to remove a playlist by mistake the way it is set up now in SN beta

Rhapsody playlists can take a long time to build one track a time, and removing them by mistake is not a recoverable operation.

Thus I would propose hiding the option to delete a playlist, and enabling playing/browsing the playlist as the default top menu action

Comment 12 Andy Grundman 2008-01-21 05:11:23 UTC
Brian, Dean, what do you think?
Comment 13 Blackketter Dean 2008-01-21 07:27:45 UTC
Remove should definitely not be at the top of the list.    People click through inadvertantly all the time.   Playing the playlist should be the first item, like Play All in the Music Library.



Comment 14 Andy Grundman 2008-01-21 07:43:01 UTC
OK, I will move the "Tracks (NN)" menu item to the top, this is the list of tracks and you can hit play to play all.

I will move the 'Remove' items back to the bottom... Do you want 'Add playlist to library' as the second item?
Comment 15 ndijulio 2008-01-21 09:34:46 UTC
We have discussed this idea in the past, however, when deleting anything from SC or Jive a confirmation pop-up would solve this issue no?  It is easy to select an option by mistake.  For actions that are difficult to recover a simple confirmation screen or pop-up would allow the user to have an "undo."
Comment 16 y360 2008-01-22 10:40:22 UTC
The major use case here is playing or browsing into the list, not deleting it and certainly not while in SB3.
IMHO this whole additional menu level is of questionable value.

# Action: Remove playlist from library
# Text: Playlist: XXX
# Text: Playlist Length: 12:22:41
# Play: Tracks (198)
# Text: Created: 2007-03-26 08:53:08
# Text: Last Modified: 2008-01-21 14:14:08  
Comment 17 Andy Grundman 2008-01-22 11:03:00 UTC
I like that menu, and it's certainly valuable.  If you don't want to use it, just hit Play on the playlist title on the parent level.
Comment 18 Andy Grundman 2008-01-23 10:01:01 UTC
Fixed.  I moved the 'remove' items to the bottom and added 'Play' items to the top of album menu, channel menu, and playlist menu.
Comment 19 Chris Owens 2008-03-07 09:03:22 UTC
This bug is being closed since it was resolved for a version which is now released!  Please download the new version of SqueezeCenter (formerly SlimServer) at http://www.slimdevices.com/su_downloads.html

If you are still seeing this bug, please re-open it and we will consider it for a future release.