View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0001346 | MMW v4 | Main Panel/Toolbars/Menus | public | 2004-05-12 13:05 | 2007-04-26 21:28 |
Reporter | rusty | Assigned To | |||
Priority | high | Severity | feature | Reproducibility | always |
Status | feedback | Resolution | open | ||
Summary | 0001346: Tree is crowded and nodes are sometimes inaccessible | ||||
Description | Users have made several complaints about the current tree organization: 1) If expanded, it's hard to access some nodes (e.g. if the library is expanded, a device node can only be accessed by first collapsing the tree) 2) It's 'crowded' / overloaded This can be solved in one of 3 ways: a) Make the root nodes non-hierarchical (hierarchy would appear in the tracklist). This is similar to iTunes/WMP. The downside of this approach is that unless we add an extra tree control in the tracklist, drag and drop operations would be impossible. b) Continue with the current approach of using the Tree + Shortcuts, but -ensure that shortcuts are included for all root nodes (Collapse, Now Playing, Library, Playlists, Podcasts, <CD/DVD Devices>, <Portable Devices>, My Computer, Radio, Web) -switch to outlook style shortcuts (vertical orientation), so that all shorcuts can fit This would have the benefit of retaining the benefit of the tree, with the only compromises being: -Some vertical space would be taken up by the shortcuts -Because all nodes of the tree are always displayed, the tree would still appear 'crowded'. c) Take the approach defined in b), but in addition, limit the portion of the tree that is shown when any shortcut is selected to the portion associated with the shortcut. e.g. if the user clicks 'Device' shortcut, then only the device and related nodes appear. This will make the tree narrower (since root node doesn't have to be displayed) and appear less crowded. This needs to be specced further though, to define which node appear e.g. when the user clicks Device shortcut. | ||||
Additional Information | http://www.songs-db.com/forum/viewtopic.php?t=1280 | ||||
Tags | No tags attached. | ||||
Fixed in build | |||||
|
I don't know, although the ideas here have some advantages, they also have some advantages. From my point of view, some of the problems described in this issue were resolved by the Vista-like toolbar - it lets user to quickly navigate in the tree, even in cases the tree is too complex. So, I'd propose to defer this issue, at least past MM 3.0. |
|
I also have requested a) as an option in the library. Subnodes are ok (Artist, Album) but not sub-subnodes (with the name of the artist, album etc.) Although this function relies heavily on a smart and intuitive searching-engine, I think it will be great to have that selection. I also think that the tree should be more customizable in general so that the user can decide what nodes he/she wants to see. |
|
The Vista-like toolbar is helpful, but doesn't resolve the 'congestion' in the tree, and only _partially_ resolves the issue of better access to root nodes: e.g. to see playlists requires at least 3 clicks vs clicking an Outlook-Style Playlists button would open up all playlists right away (one click). e.g. to play a CD requires -one click to the dropdown -one click to My Computer -one click to the next dropdown -one click to CD -double-click tracks vs. the alternative solution would be 2 clicks -click CD Device button -double-click tracks Note: the click count would only differ by 1 if 0001618 was fixed Summary: I still think that a simplified tree is needed, but that if it's too much work, we can defer it. |