Hi Ferran and Markus,
thank you so much for your input.
What we have so far:
We need a tree as drop target to crates, playlist and AutoDJ.
This should be sensitive for drops from track tables, decks and file
system.
The open question is how and where to display it.
1: in the second pane
* good for small screens
2: on top of the left pane stack
* can be always visible
Feeling of 2 can be tested in Nemo file manager. It features two panes
and a switch to select the sidebar or the directory tree in the left pane.
Any addition thoughts? Pro and cons?
Am 05.06.2016 um 12:55 schrieb Ferran Pujol Camins:
Full Tree: I think we do not nee the legacy full tree, we need a
tree of all drop targets, right? The crates and playlist tree
should be sufficient.
Agree, but Autodj playlist is also a relevant drop target.
A full tree node, on every left pane breaks somehow the ButtoBar +
Fetaure Idea.
How can we combine both?
How about move this Full Tree node as button to the button bar.
This could be a special feature without a right pane.
I don't feel the button that makes the full tree appear should belong
to the button bar, because it is not a feature by itself. Creates,
playlists and autodj already have they own features. Maybe this button
could be placed at the bottom of the left pane (first picture). Then
if the button is pressed, the tree (playlists, crates and autodj list)
appears and stays there until the button is pressed again (second
picture). If the button is hovered while dragging tracks, the tree
appears but hides when the drop is done.
How do you feel about this?
I want to remark that is quite important to allow users to
configure the new library to look similar to current one (one
single pane + complete tree). Feature specific tree + collapsable
complete tree would also work for me.
I am not sure if I missed a point, why it is required to keep a
view that look similar to current one. Is there an other use case
we have missed?
Forget that, as long as you provide quick access to all relevant drop
targets and allow to only display one feature this would be ok for me.
Another thing you might want to think about is how this will affect
the drag and drop of tracks from OS file explorer. I'm not sure how
this works now, but you can add tracks to the library by dragging them
from outside Mixxx right? For every feature on the button bar, you
might want to think what will happen when an external track is dragged
with that feature open. What about when two features are open at the
same time?
Hope this helps you to improve the project definition :)
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org
Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel
