|
|
I think that c) would make the most sense. Below the Sorting area, there could be a section with a dropdown and three buttons: Save Preset, Load Preset, and Delete Preset. To save a preset, the user can type the name into the dropdown and hit Save; To load/delete a preset, the user can click the right item in the dropdown and hit Load/Delete. I don't think that Delete Preset should require a prompt, because it's not something that really causes any data loss. I can code up a prototype if you'd like. |
|
|
c) ok, might be useful, so let's try if you have time d) I have just added addon for sharing the columns settings and visibility It is in .../sampleScripts/sharedColumns Assigned to Draki to upload the addon to our addon's repository? Maybe after some brief testing? Also attached the addon here: https://www.mediamonkey.com/forum/viewtopic.php?p=478724#p478724 for the user to test. EDIT: This initial version of the addon isn't perfect, as by sharing the columns it removes '#' column from playlists / playing node. Workaround is to edit the shared columns within playlist node. |
|
|
Note that sorting is affected in a similar manner to columns (i.e. it gets lost and isn't easy to recover / copy). Not sure if it belongs here or in a separate bug, but I wanted to note it so we don't lose track (it was originally mentioned at #12243 which is fixed). |
|
|
Wouldn't it be a whole lot better to start by working on the Custom Views facility (aka manage Views) to make it more universal. From what I see a Custom View, designed in the Main panel, can be used most places, with just a few exceptions: * Location sub-node, and Folders node * Playlist node * and in the global Search facility Couldn't there be an under-the-covers transaction facility to overcome those exceptions. That way users could design their views, which would have global applicability, by a background process stripping off the mode-specific View Elements, or whatever the issues are. I never did like the MM4 the "Sharing" collection facility . Too atomic. Too easy to get muddled up. Hard to get an overview. MM5 Custom Views is an improvement IMO, but it is not fully implemented yet IMO. Adding presets to the Custom Views facility sounds an ugly complicating hack to me (if I understand the proposal correctly). |
|
|
A review of most of the feedback sees to indicate that the most common complaint/requirements are: - Users shouldn't have to re-configure columns & column sequence / column widths for each node-view. - Given that List, Simplified list, and List (by Album) views are different, it should be possible to apply the settings for all Collections OR Collection subnodes that use each view (e.g. to _all_ Collections and their subnodes, or to just CollectionName and it's subnodes) - The approach should be able to accomodate 'special' nodes like Playlist and Playing - The approach should accomodate the fact that Sort requirements and View Element requirements are likely different for different nodes (and especially for 'Playing' and 'Playlist' nodes). Possible approaches: 1) A global setting similar to the 'SharedColumns' addon, that wouldh share columns & column sequence / column widths. across all groups of Collection/Node-views, but with greater granularity. e.g. Column settings: (o) Unique to each Collection / Node ( ) Shared across nodes within a Collection ( ) Shared across all nodes in all Collections Downsides to this approach: - Settings for Playing/Playlists/Global Search would probably have to be configured independently (i.e. more work for users) - There's no obvious portion in the UI for such a setting - This approach doesn't mesh well with the current UI in the sense that it's completely disconnected from the 'Configure Views' functionality. 2) Similar to what was described by Barry/Drakinite (assuming I understood correctly), on each Configure View screen, add a set of checkboxes to determine which Collections/Nodes the view is applied to. e.g. Name: List View type: List Collections: Music, Kids Music > Genres [⋮] (clicking the ellipsis could show a tree hierarchy of Collections allowing the user to select all Collections, any set of collections, or a set of Collections nodes) Nodes: Playing, Playlists [⋮] (clicking the ellipsis would display non-Collection nodes that are configurable e.g. Playing, Playlists, Folders, Search) This approach fits well with the Configure Views functionality, BUT, it doesn't allow sorting or view elements to be maintained independently per Collection/Node (e.g. the UI implies that changes to the columns/sort would apply to all associated nodes). A way around this would be to remove 'Sort' from the 'Configure view' dialogs. 3) Retaining independence of Views-Nodes, but allowing the user to apply changes to other Views-Nodes when making changes. e.g. upon making a column change: Save (View): 'List' [ ] All Collections [ ] Collection: 'Music' (i.e. the current Collection) [x] Music > Genres) (i.e. the current node) [ ] Playing [ ] Playlists [ ] Folders [ ] Search . . . . . . . [Save] [Cancel] This approach is quite flexible, and allows column configuration to be applied without sorts (without making changes to View Configuration' functionality), but is onerous in that it would require that every time the user edits a View (whether through 'Configure view', 'Choose columns/sort'), or by adding/resizing a column, the user would have to confirm which views to apply the changes to. Thoughts? I think Option 2 might be best, but I suspect that Option 3 could probably be implemented much more quickly and doesn't even require any new strings. |
|
|
I think 3) would work fine.. |
|
|
I started with implementation of 3), but it was quite cumbersome and problematic to implement so I finally implemented this using solution 1) as follows: image.png (61,987 bytes) |
- Anonymous
