View Issue Details

IDProjectCategoryView StatusLast Update
0002825MMW v4Main Panel/Toolbars/Menuspublic2007-10-12 21:07
Reporterrusty Assigned To 
PriorityimmediateSeverityfeatureReproducibilityalways
Status closedResolutionfixed 
Fixed in Version3.0 
Summary0002825: Vista-style hierarchy browser
DescriptionWindows Vista added a nice new feature that gives users the ability to navigate to any portion of a tree without having to scroll through many intermediate nodes. This would be a nice addition to MediaMonkey.

1) It should be located in a horizontal space that contains other functions that affect the view:
   a) hierarchy browser
   b) view buttons
   c) search bar
   This implies that other toolbar commands should be on the same row as the Menu Bar.

2) It should be treated as a toolbar/function that can be enabled/disabled (enabled by default). It can be called the Tree Browser (or Tree Navigation Toolbar) if we decide to replace the existing navigational tool (see below).

3) This functionality largely replicates the functionality provided by the shortcuts that currently appear at the top of the tree, with the exception of the 'Collapse Tree' function. Therefore it would make sense to eliminate this toolbar altogether or to disable it by default.
The 'Collapse Tree' function, is valuable, though, and we need to figure out a means of retaining it.

4) This functionality overlaps somewhat with the functionality provided by the Album browser, however, the browser is still useful because it allows for non-hierarchical browsing (although we may find that links in tracks 0000481 may make this less important). As is already the case today, the display of tracks is based on the combination of the selected node and Album Browser. This same logic should apply to the QuickSearch bar ( 0000347 ).

5) In terms of hierarchy, at the top level there'd be:
   a) Audio, Video, Images
   b) Now Playing, Libraries (pre-defined and user-defined), Playlists, Podcasts, Search, My Computer, Net Radio, Web

   In addition, selection of a) level hierarchy should affect which nodes are displayed below, while Library selection should also affect what nodes are displayed for each library, however, this would probably be a future feature.

6) Functionality should be compatible with Magic Nodes (how to implement on a per library basis?)
TagsNo tags attached.
Fixed in build1084

Relationships

related to 0000102 closedpetr Improve Filter functionality usability 
related to 0002701 closedLudek Context toolbar + rationalize commands between menu and toolbar 

Activities

jiri

2007-03-07 10:28

administrator   ~0008734

Assigning to Petr. Note that some details related to this issue are written in issue 0000102 (Jiri's comment 8586).

petr

2007-03-13 15:37

developer   ~0008791

basic functionality is done ... so waiting for your feedback

rusty

2007-03-14 05:11

administrator   ~0008801

Looks great. The only things that need to change are:

7) It should use the toolbar background instead of looking like a separate control (i.e. get rid of the text box). Also the arrows that appear inside should appear the same as the arrows that appear elsewhere in the toolbar.

8) The default toolbar layout can change slightly:
-Move the view buttons to this level (right justified)
-Move the search bar to this level (far right justified)

9) We may need to adjust the hierarchy slightly, but I need to think about this further.

petr

2007-03-14 12:02

developer   ~0008803

7, 8 are done

rusty

2007-03-14 19:58

administrator   ~0008810

Last edited: 2007-03-14 21:32

9) I think that the current hierarchy implementation makes sense. The only change I would suggest is that the 'Home' button should just change to an icon of a speaker to represent 'Audio'.

Once we implement 0000102, the hiearchy would become:
Level 1: Audio
Level 2: Now Playing, Library, Playlists, Podcasts, (Search) depending on whether results exist, Devices, My Computer, Net Radio, Web
Level 3 (sub to Library): All, Contemporary, Classical, Audiobook, Podcasts

10) Would it be possible that clicking on a button that contains only subnodes (no tracks) should open the subnodes (e.g. Library, Locations, Playlists, My Computer, Net Radio, Web, etc.). Do you think that makes sense?

11) Clicking on an arrow causes subnodes to appear. Clicking on the arrow again should cause them to disappear. This is how Vista works.

12) Clicking on Home > Library > Location > ^
    --> HD:WINNT (c:), HD:DATA (F:), My Documents, Tragically Hip CD, HD:DATA (F:), My Documents, HD:DATA (F:), My Documents, HD:DATA (F:), My Documents, ... (the repetition continues on down the length of the entire screen. It only occurs sometimes--not sure why).

13) Clicking on Home > Library > Year > 1940 --> 1940 button and tracks don't appear

14) Some buttons don't appear when they should:
  i)Clicking on Home > Library > Classification --> Classification button doesn't appear

 ii)Clicking on Home > Library > Files to Edit > Unlevelled --> Unlevelled button doesn't appear

iii)Clicking on Home > Library > Files to Edit > Unorganized Tracks --> Unorganized Tracks button doesn't appear

15) Paths seem to change on their own sometimes:
   i)Clicking on Home > Library > Files to Edit > Unknown Title
    ---> Path changes to Home > Library > Title > Unknown

  ii)Clicking on Home > Library > Files to Edit > Unknown Rating
    ---> Path changes to Home > Library > Rating > Unknown

16) When a particular node is selected, it appears at the bottom of the tree instead of at the top (as it does when tree shortcuts are clicked).

17) Tree navigation toolbar should be disabled by default

petr

2007-03-15 00:42

developer   ~0008812

9) added "audio" icon
10) i think it makes sense. Please, specify all nodes which need to work like this
11) fixed
12) can't reproduce
13-17) fixed

jiri

2007-05-29 14:15

administrator   ~0009213

12) It is quite easily reproducable when you have scanning thread running.

10) Wouldn't it make sense for all nodes? I.e. if I click a node, I'd probably usually expect to see its children (if there are any).

petr

2007-06-12 22:40

developer   ~0009350

10 and 12 are fixed. Will be available in build 1040.

rusty

2007-06-13 03:58

administrator   ~0009351

Tested build 1040 and most everything seems to work correctly, however:

18) There's an entry for 'Library <Manage filters>' !

19) Terminology: Navigation --> Shortcuts
 and Tree Browser --> Navigation

17) My choice of words was misleading. I meant that the (old) Navigation toolbar should be disabled by default, but that the Tree browser (Now called Navigation toolbar) should be enabled.

20) would it make sense to place the Collapse button at the left of the (new) Navigation toolbar, and move the Backward / Forward buttons to this toolbar?

petr

2007-06-13 11:46

developer   ~0009353

done. Will be in 1041.

rusty

2007-06-14 22:13

administrator   ~0009398

I'm hoping we can get the toolbars looking a bit better by default. Sending screengrabs by email.

petr

2007-06-14 22:36

developer   ~0009399

Done. Will be in 1042.

jiri

2007-06-15 11:30

administrator   ~0009422

20) I think that it would make the Navigation bar too complicated.

21) One feature I miss it that when I select a tree node in Navigation bar, its children should probably be shown (i.e. the node would be expanded). What do you think?

22) When I have the tree somehow expanded and click some nodes in hierarchy below, it would probably make sense to collapse the tree hierarchy. For example, if I'm in Library>Artists>Metallica>One and click Artists button in Navigation bar, all artist nodes would collapse (i.e. 'One' album would be no longer visible). However, artists would still be visible (as described in 21)

23) Currently the first two buttons in Navigation bar have a little strange behaviour:
 a) 'Speaker' icon doesn't do anything. I'd expect it to collapse the whole tree and unselect selected tree node. (note: its dropdown arrow would retain its current functionality) (btw, after this fix we could get rid of Collapse tree button (with F7 shortcut, that should be re-assigned to this button).
 b) 'Library' button (or anything else that's 2nd in hierarchy, like Playlists) when clicked work like when their associated dropdown arrow is clicked, i.e. nothing happens, just a pop-up window appears. Instead, they should select the related node (Library, Playlists, ...) and possibly do the collapsing as described in 22. (note: the dropdown arrow would retain its current functionality)

Assigning to Rusty for a review.

jiri

2007-09-02 09:03

administrator   ~0010434

Raising priority in order to be reviewed asap.

rusty

2007-09-25 19:22

administrator   ~0010965

21) Yes--this would make sense

22) In addition If Library > Artist > U2
is selected and the user clicks Artist, then the Navigation bar should collapse back to Artist.

23) Agreed.

petr

2007-10-05 02:03

developer   ~0011195

Done. Will be in 1084.

rusty

2007-10-12 21:07

administrator   ~0011306

Verified 1087.