Hi Ferran,
thank you for your ideas.
The second way is the "Copy to Context menu". Unfortunately the
menu vanishes after the copy. Conclusion: Not easy.
Why is this "not easy"?
This IS easy for a single track, but not for many, lets say new tracks.
I am afraid, this menu becomes unhandy if we have crates hierarchies.
Maybe we can replace it with something cool that fixes the other issue
as well.
How about adding a root node to the Crates and Playlist Feature
that displays the All tracks? That would allow dragging any track
to any Crate /Playlist.
1) This doesn't allow users to add tracks from playlist to crates.
Yes, a solution would be to combine the crates an playlists feature.
However a separate feature may allows us to add cool new things to the
left pane individual.
2) Maybe the user is looking at the auto-dj queue and thinks "this
track is totally hot, I should add it to the Hits crate". He can't
because from the auto-dj pane he can't access the playlist tree. For
me this is not a solution.
The main task for the autodj's left pane is to define the transitions.
The user can already use the context menu or open a second pane, but
this might be not straight forward enough.
once we have a Crate hierarchies, it could be as hard to drop to
one from 100 crates. This cam be solved ba a Bookmark feature that
contains only a few relevant Crates.
What do you think? Any other idea?
Keep showing the whole tree of features in every pane: Show the tree
corresponding to the current pane. Add an additional node, collapsed
by default that shows the whole tree. Something like this:
-Crate 1
-Crate 2
---Sub Crate 2.1
-Crate 3
-Full Tree
---...
Isn't this a simple but effective solution?
IMHO we should careful consider what is the most required contend on the
feature's left pane. Sorting tracks to different crates / playlists is
only one aspect. It should not clutter the left pane one one hand, but
there is a valid demand to have always an easy access to crates and
playlist as drop targets.
You idea, goes to the right direction.
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.
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.
The most difficult case, seams to be the single feature view: ButtonBar
+ AutoDJ left pane + AutoDJ track list.
Form this view, the user can drag a track from the AutoDJ track list,
hover to the Full Tree button on the button bar.
this will enable the drop target tree on the left pane keeping the
AutoDJ track list in the right pane.
Now he can sort all tracks as desired.
@JOAN, will this fit to your Backend model? Will it replace the single
cates and playlist features?
Do we still need to copy to context menu?
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?
Kind regards,
Daniel
------------------------------------------------------------------------------
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
