Bug 13445 - Context Menu Design Issues
: Context Menu Design Issues
Status: NEW
Product: SqueezePlay
Classification: Unclassified
Component: UI
: unspecified
: PC Windows XP
: -- enhancement (vote)
: Future
Assigned To: Unassigned bug - please assign me!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-08-18 00:38 UTC by Philip Meyer
Modified: 2011-11-06 23:25 UTC (History)
2 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philip Meyer 2009-08-18 00:38:15 UTC
I'm finding the context menu very disappointing.  It looks a bit naff, and the UI is actually faulty.  Some observations:

- the text overflows the context menu window.

- the bump effect when you reach top/bottom is even worse than the normal scroll bump - really slow, because I think it is bumping the context menu AND the screen underneath it.

- the context menu doesn't feel integrated, in that there isn't a back button top-left, but a close button top-right.

- screensaver can kick in taking me to NP, and when I click back, it takes me back into the context menu "window", but if I R-L swipe to get to NP, a back doesn't take me back to context menu.

- scrolling the list of options is not very responsive.

- the title "more" is not very useful.  Better would be to report the item that was clicked on.


I think the effort being expended to make it look like a pop-up window  wasteful.  Just make it act like a normal UI page.  i.e. scroll on right-to-left and use the whole screen.  The title could be the item clicked on, or something like "Actions for <item>".  Add the page to the standard menu stack, so navigations such as "back", screensaver and NP work consistently.

I feel that right-arrow.hold on the IR remote would make a lot more sense than abusing the Add button.  After all, touch = right-arrow, long-touch = right-arrow.hold.  Especially seeing that you intend not to change Classic players (so Add will still function as add on old players).


Why is Album Volume Adjustment in the context menu?  It's not a context action - it's information about the album, which frankly I would be surprised if anyone cared about anyway.  But if this piece of album information is here, then why not other album info, such as Artist(s), Band(s), Conductor(s), Composer(s), Album Artist, Year (all of which should be navigateable items), and information such as date added, artwork, etc.  Context actions should be listed, plus a link to "Show Album Information" for navigation.
Comment 1 Pat Ransil 2009-08-28 10:55:26 UTC
I am adding the TinySC keyword. If this is not right, pls change.
Comment 2 Ben Klaas 2009-08-28 11:00:28 UTC
No, this is not TinySC specific
Comment 3 Ben Klaas 2009-10-02 15:18:55 UTC
There's a few things that are obvious to do here (removing the title 'more' on fab4 CMs, which is not to spec anyway), but mostly this is a UI design complaint bug, so passing to Weldon for review.
Comment 4 Philip Meyer 2009-10-02 15:28:17 UTC
Another point: How do you play the whole album for a song that comes up in a random song mix?

eg. in SB3 interface, within song info you can sit on an item and do actions on it.  eg. for a song, select an artist, album, year, genre, etc, and press right to navigate into it, or press play or add to perform those actions.  Press play.hold to get to mixers, etc.  Now, the context menu lists those things, but you can't directly perform actions on them.  i.e. you can't hold your finger down on an item in the context menu to bring up a context menu for that item.  All you can do is touch the item to navigate into it.
Comment 5 Weldon Matt 2009-10-02 15:37:37 UTC
(In reply to comment #4)
> Another point: How do you play the whole album for a song that comes up in a
> random song mix?

Press+hold the song.  In the context menu, scroll down to "album: [album name]" and select it.  Then press the first song in the album to start playing it.

Am I missing something? 

> eg. in SB3 interface, within song info you can sit on an item and do actions on
> it.  eg. for a song, select an artist, album, year, genre, etc, and press right
> to navigate into it, or press play or add to perform those actions.  Press
> play.hold to get to mixers, etc.  Now, the context menu lists those things, but
> you can't directly perform actions on them.  i.e. you can't hold your finger
> down on an item in the context menu to bring up a context menu for that item. 
> All you can do is touch the item to navigate into it.

You lost me at the end.  You want context menus for things inside context menus?
Comment 6 Philip Meyer 2009-10-02 16:27:39 UTC
(In reply to comment #5)
> Press+hold the song.  In the context menu, scroll down to "album: [album name]"
> and select it.  Then press the first song in the album to start playing it.
> 
> Am I missing something? 
> 
This only works if the "play other songs in album" option is enabled (not with "play only selected song").  There's no way to easily navigate around like the classic interface.

> You lost me at the end.  You want context menus for things inside context
> menus?
Effectively Song Info menu page has been replaced with a context menu.  Song Info used to allow actions on items, but now context menu only allows navigation to items.

In all other parts of the interface, album, artist, genre and year items can be long-touched to display info and actions for that item.  A context menu can also contain these items, but the context menu cannot be displayed for them.
Comment 7 Weldon Matt 2009-10-04 17:49:52 UTC
There is some redundancy here with other bugs I think, will review soon
Comment 8 Philip Meyer 2009-11-01 04:25:33 UTC
Another thing to consider:

Instead of a long list of actions and info, how about displaying large icons for Play, Add, Add Next, Add to Favorites, and Mixers (perhaps some other common action items, such as "Remove from Playlist" if the item is in the current playlist).

i.e. touch and hold an item and context menu pops up.  In that pop-up, permanently display the common action buttons, and under that have a scrollable list of extra less-common stuff.
Comment 9 Chris Owens 2010-02-02 15:11:30 UTC
Moving Matt Weldon bugs
Comment 10 Alan Young 2011-11-06 23:25:04 UTC
Unassigned bugs cannot have a priority.