Hi Markus,
thank you for the detailed explanation.
Yes this will work. The back-end should be also doable.
Your solution fits nicely to your drop target idea. I like the idea,
that the drop target pane can contain a list of playlists
or a track table.
The other good idea, is Joan original desig
> By the way Markus the condensed library looks interesting, with this it
> will be possible to have multiple right panes showing at the same time or
> only one right pane and different CondensedLibraries?
For me the right pane and the CondensedLibraries are Function-Wise the
same. Each one of
Hi,
as it is the design now, when the user tries to drag a song to a playlist
when it selects the song the let pane will change and it won't allow to
drag the song to the desired playlist. My idea was to allow the user to
drag the song(s) directly to the button bar, so when the user does this
autom
Hi Daniel,
> We have discussed such a model earlier, but it was difficult to
> generalize is in the back-end.
Hm, I don't really get that point.
Each library Feature would need
* a 'default' widget, if no child element of it is selected (Playlists
would display all Playlists there),
* a wi
Hi Markus,
thank you for you second library model.
We have discussed such a model earlier, but it was difficult to
generalize is in the back-end.
The current model has a nice generalized object model.
See the exploded drawing on:
http://www.mixxx.org/wiki/doku.php/library_layout_redesign
For my
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
*
>
> 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
> Ide
Thanks for addressing the library redesign!
> 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
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 unha
