Hi RJ,
> Interesting -- do Library Track Tables need a title now? In Mixxx 2.0 we
> know what playlist is selected based on the highlight in the sidebar tree,
> but this may be harder to tell in particular because the focus highlight is
> somewhat subtle. Maybe we could clear up the need for keep
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 06 Jun 2016 20:22:08 -0100 "RJ Ryan"
wrote:
>Or, for the specific case of two playlists showing at the same
>time -- each
>library track table could be styled with a particular color (e.g.
>a rim
>around it or a background color / alternate r
On Mon, Jun 6, 2016 at 1:50 PM, Joan Marcè i Igual
wrote:
> Hi RJ,
> thank you for your thoughts
>
>
>> I see -- thanks for the explanation. Sorry to nit-pick but could I push
>> for more salient names for these? I think it's already causing confusion
>> :). Skin designers will probably also be c
Hi RJ,
thank you for your thoughts
> I see -- thanks for the explanation. Sorry to nit-pick but could I push
> for more salient names for these? I think it's already causing confusion
> :). Skin designers will probably also be confused.
> We already have and XML nodes.
> What about for the but
On Fri, Jun 3, 2016 at 7:43 AM, Joan Marcè i Igual
wrote:
>
> I'd like to push back on this a little bit just to see whether it can be
>> made more general.
>>
>> Why hard-code any orientations into this? And why 2 panes instead of N?
>>
> Yes it will be N panes (maybe it's not well explained) bu
Hi,
Thinking about it the drop target needs to be shown somewhere in the
layout, Ferran's idea seems better to me. Also, there's the option to
convert the Library drop target into a feature itself with only a right
pane. This will mix both Ferran's and Markus' idea. The user can select
this featur
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
>
> The second way is the "Copy to Context menu". Unfortunately the menu
> vanishes after the copy. Conclusion: Not easy.
>
Why is this "not easy"?
> 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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Speaking of playlists, is there going to be a playlist button? I
don't see it anywhere in the docs. Crates button, but no Playlist
button?
~RAWRR
On Sat, 04 Jun 2016 11:51:18 + "Daniel Schürmann"
wrote:
>Good point.
>
>We have actually only tho
Good point.
We have actually only thought about building a new Playlist by dropping to
the second pane.
Sorting library tracks to different crates is also a very common task. We
schould make very easy.
What are good solutions?
Currently it can be done like that.
Select a track in the source pan
1) Will users be able to configure the library to look exactly like it does
now? I mean, single list with the complete tree on the left.
My concern is: As far as I can understand, the only way to drag a song to a
playlist will be with two opened panes, because the playlist tree will only
be shown
> I'd like to push back on this a little bit just to see whether it can be
> made more general.
>
> Why hard-code any orientations into this? And why 2 panes instead of N?
>
Yes it will be N panes (maybe it's not well explained) but for simplicity I
only created the examples with 2 pane. There will
On Thu, Jun 2, 2016 at 9:57 AM, RJ Ryan wrote:
> I think your design doc could use a section on how MIDI / HID control will
>>> control the library once it goes split pane.
>>>
>> Added, it is related to this PR (
>> https://github.com/mixxxdj/mixxx/pull/953)
>>
>
> Ah, I missed Daniel's comment
On Thu, Jun 2, 2016 at 9:14 AM, Joan Marcè i Igual
wrote:
> Hi RJ,
>
> thank you for your explanation. I was mistaken with the LibraryViewManager
> because
> the Library class is already doing most of the functions I was going to
> code in the
> LibraryViewManager. So, I've changed the wiki to fi
Oh great idea I'll take in account and if there's enough time I'll add it
On Thu, 2 Jun 2016 18:15 Be, wrote:
> I like your ideas and I'm excited to play with the new interface. :) I
> have a suggestion for a feature: a new search box for the left pane. As
> the interface is now, this wouldn't m
Hi RJ,
thank you for your explanation. I was mistaken with the LibraryViewManager
because
the Library class is already doing most of the functions I was going to
code in the
LibraryViewManager. So, I've changed the wiki to fix the things that were
not right in
the previous design.
> I would like
I like your ideas and I'm excited to play with the new interface. :) I
have a suggestion for a feature: a new search box for the left pane. As
the interface is now, this wouldn't make much sense because all the
features are lumped together into the sidebar. After your redesign, it
would be help
Oh! Also you will probably need a section describing how skin XML will
describe / configure a library.
On Wed, Jun 1, 2016, 10:04 AM RJ Ryan wrote:
> Nice work Joan!
>
> I would like to point out one key design detail of the library. There is a
> "frontend" (GUI components -- WLibrary, WLibraryS
Nice work Joan!
I would like to point out one key design detail of the library. There is a
"frontend" (GUI components -- WLibrary, WLibrarySidebar, DlgRecording,
DlgAnalysis, etc.) and a "backend" (non-GUI components -- Library,
LibraryFeature, BasePlaylistFeature, CrateFeature, etc.).
There are
Hi everyone,
I have been working with the design of the new Library Layout and I have
created
a new page in the wiki (
http://www.mixxx.org/wiki/doku.php/library_layout_redesign )
showing all the ideas.
With this new design the user will be able to show two library features at
once
(it can be dec
28 matches
Mail list logo
