I think the new model is a step backwards. It is totally unintuitive to me.
We'll have lots of users complaining either that they don't understand how it works or that it is broken. Users will have to learn how it works. The first time they'll open Mixxx, they will understand nothing. And every time they'll want to open a feature to an specific pane, they'll have to think how to do it. This is not a good idea with low light and drunken eyes ;) For me, the way to go to produce an easy interface that meets your goals is either: 1. Library right panes have tabs. A feature is always open in the current tab of the focused right pane. Tabs can be opened and closed like in a web browser, independently for each right pane. or: 2. Right panes can be blocked (or pinned). A blocked right pane can't get the focus so its feature can't change. This alone does not solve the use cases that worried you, but if you add a third pane that can be hidden/shown you can pin auto-dj there and you are good to go. 2. and 1. are very similar, I think 1. is more general and the best solution. For the left pane selection issue, I think tabs are also the best solution. Covers all use cases and is intuitive. All users are used to tabs. 2016-08-19 23:09 GMT+02:00 Daniel Schürmann <dasch...@mixxx.org>: > Hi Mixxx developers, > > Joan has just finished a new version of his "Library layout redesign" PR > https://github.com/mixxxdj/mixxx/pull/991 which contains the fixes for > the issues found in the first review and a prototype for an improved > focus and pane selection schema. > > While preparing it, we have tested some different options how to select > the pane for a selected feature. We have finally managed to meld the > ideas an requirements down to a few rules. > > "Last pane restore feature": > A feature opens, in the pane where is was last seen. (Feature hidden / > First click on the button bar). If a feature is already shown, it uses > the focused pane (Feature visible / First click on the button bar) > > This means: > If the focus has changed after the fist click on the button bar, the > second click opens a new track table in the focused pane. If the feature > allows only one pane like AutoDJ, the pane left and right panes are > swapped. > > This behaviour fits exactly for the two main use cases for a two track > table view: > > * AutoDJ supported DJing. > By default the AutoDJ track table is shown right. All other features are > shown left. Now you can switch features > as you like, without caring about the focused pane. AutoDJ sticks always > in sight in the right pane. No pane will move unless you enable an > enabled feature again. > > * Sorting tracks to Playlist / crates / AutoDJ from Library. > By default the library feature is enabled with a track table left. > The AutoDJ track table is on the right. > Focus the right pane; enable library feature again; Left and right panes > are swapped. > Now you can switch the desired drop target features as you like, without > caring about the focused pane. The Library table sticks in the right pane. > > > The current version of the "Library layout redesign" PR works almost > like that. We want to receive your feedback to know if it is worth to > clean ups the code to release quality and fix remaining issues. > > Does it work for your use cases as well? > Do we need additional controls or preference options to control the > behaviour? Pros and cons .... > > Thank you for your help! > > > Kind regards, > > Daniel > > > > > > > > > > > > Am 19.08.2016 um 22:20 schrieb Daniel Schürmann: > > Hi Ferran, > > > > Joan and me have discussed the model some time ago. But we have > > discarded the idea, because it somehow duplicates the button bar as > > Tabs. The tabs are somehow a button bar horizontal, but horizontal space > > it rar. > > > > But the underlying behaviour is interesting, treat the button bar as > > vertical tabs. > > This fits somehow to the schema, to control the panes content by the > > button bar and not vice versa. A left to right control flow. > > > > I will introduce our ideas it in a separate Mail. > > > > Kind regards, > > > > Daniel > > > > > > > > Am 19.08.2016 um 11:36 schrieb Ferran Pujol Camins: > >> What about tabs for the left pane? One tab for each distinct feature > >> open in a right pane. Similar to tabs in a web browser. Then, controls > >> to cycle through the different features' left pane would provide an easy > >> way to handle this from a controller. Plus it works well with n > 2 > >> right panes. > >> > >> 2016-08-15 22:50 GMT+02:00 Daniel Schürmann <dasch...@mixxx.org > >> <mailto:dasch...@mixxx.org>>: > >> > >> Yes, that's the other issue. Do you have an idea how to fix it? > >> An pin Icon for the tree view pane? > >> > >> > >> Am 15.08.2016 um 22:04 schrieb Be: > >> > We also have the related question of how to control which > >> feature's left > >> > pane appears. It seems there are two design goals: > >> > > >> > 1. Dragging a track from a right pane to a different feature's > >> left pane > >> > should be easy. The most prominent use case for this is sorting > >> many > >> > tracks into many crates. > >> > 2. Selecting the left pane for a feature with an open right pane > >> should > >> > be easy. An example use case is having Library and Auto DJ both > >> open > >> > with the Library tree on the left. It should be easy to access the > >> Auto > >> > DJ controls in Auto DJ's left pane from this situation. > >> > > >> > Currently, the most obvious way for a user to drag a track from a > >> right > >> > pane to a different feature's left pane (#1) is: > >> > * Click the feature icon corresponding to the right pane with the > >> > desired item to drag (for example, a track in Library). > >> > * Focus the other right pane. > >> > * Click the feature icon that has the left pane with desired drop > >> target > >> > (for example, a crate in the Crates tree). This has the side > >> effect of > >> > opening the feature's right pane as well. > >> > * Drag and drop easily between left & right. > >> > * When a different left pane is desired, click the corresponding > >> feature > >> > icon. > >> > > >> > This works well for design goal #1 but does not accomplish > >> design goal > >> > #2. The most intuitive way to accomplish design goal #2 would be > >> to open > >> > the left pane for a feature when its corresponding right pane is > >> > focused. Currently, users must click the feature icon for the > >> feature > >> > with the left pane they want to access. > >> > > >> > This creates a confusing situation because clicking the feature > >> icons > >> > has two different purposes: opening a left & right pane for a > >> feature > >> > that is not open, plus opening a left pane for a feature that > >> already > >> > has a right pane open. This is especially a problem for unstickied > >> > features (currently only Crates and Playlists) because the user > >> has to > >> > be careful to focus the right pane that already has that feature > >> open > >> > before clicking the feature icon. Otherwise, clicking the > >> feature icon > >> > will open the desired left pane but also open the undesired > >> right pane > >> > where the focus currently is, hiding a right feature pane the > >> user may > >> > have wanted to keep open. > >> > > >> > However, the obvious way for accomplishing design goal #2 > >> (opening the > >> > left pane for a feature when its right pane is focused) would > >> make the > >> > steps outlined above for design goal #1 impossible. There > >> already is > >> > another way to drag & drop many tracks between many crates (#1) > >> though: > >> > > >> > * Click the feature icon corresponding to the right pane with the > >> > desired item to drag (for example, a track in Library). > >> > * Drag a track from the right pane > >> > * Hover cursor over feature icon for the feature that has the left > >> pane > >> > with the desired drop target (for example, Crates list) > >> > * Desired left pane opens, mouse can be released onto drop target > >> > > >> > If the user clicks again on a new item in the right pane, the left > >> pane > >> > that opened by hovering the cursor for the first drag & drop > >> operation > >> > stays open. The focus has not shifted between the two right panes. > >> This > >> > makes it easy to do many more drag & drop operations without > >> having to > >> > hover over a feature icon every time. The problem is that this > >> is not > >> > easily discoverable. However, I doubt this is something that many > >> users > >> > will want to do live or even every day. So, I think it will be > >> okay as > >> > long as this way of dragging & dropping many tracks is documented > >> in the > >> > manual. > >> > > >> > On 08/15/2016 11:55 AM, Daniel Schürmann wrote: > >> >> Hi Mixxx developers > >> >> > >> >> During the review of the library redesign branch, we discovered a > >> design > >> >> issue about how to select where a track table of a feature is > >> shown. > >> >> https://github.com/mixxxdj/mixxx/pull/991 > >> <https://github.com/mixxxdj/mixxx/pull/991> > >> >> > >> >> Basically there are two valid requirements that at somehow > >> incompatible. > >> >> > >> >> 1. A feature track table should re-appear where it was before. It > >> turns > >> >> out in live test, that undesired panes swapping is annoying, > >> especially > >> >> late at night. > >> >> > >> >> 2. User expect, that a track table appears in the focused pane. > >> This > >> >> allows to intuitive arrange the desired panes side by side. It > >> is a > >> >> known paradigm from two panes file manager like Nemo. > >> >> > >> >> In the current implementation we have tried to predict what is > >> the best > >> >> behaviour. Unfortunately it suffers some pending issues. And > >> even if > >> >> they are solved, it will remain confusing that the same action > >> does > >> >> different things, depending on the context. > >> >> > >> >> What could be a solution? > >> >> > >> >> ------- > >> >> > >> >> The discussed Idea. > >> >> > >> >> For me it is important that the Auto DJ tracklist appears on the > >> right > >> >> pane after a single click on the library button. > >> >> The library view should always left. > >> >> > >> >> Other pane associations should be freely selectable. > >> >> > >> >> Let's add a pin button to the right pane (in fact to all n+1 > >> panes) > >> >> > >> >> This way, by default Mixxx works like known from other Apps (2.) > >> >> Following the focus. > >> >> > >> >> In my use case, I can open the Auto DJ in the right pane and > >> pin it. > >> >> >From now library panes ... will all appear left. If I need an > >> other > >> >> side by side view > >> >> I can release the pin. > >> >> > >> >> This does not fullfil pure (1.) but seams to be a good compromise > >> using > >> >> I known paradigm. > >> >> > >> >> What do you think? > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> > >> ------------------------------------------------------------ > ------------------ > >> > >> >> 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. http://sdm.link/zohodev2dev > >> >> > >> >> > >> >> > >> >> _______________________________________________ > >> >> Get Mixxx, the #1 Free MP3 DJ Mixing software Today > >> >> http://mixxx.org > >> >> > >> >> > >> >> Mixxx-devel mailing list > >> >> Mixxx-devel@lists.sourceforge.net > >> <mailto:Mixxx-devel@lists.sourceforge.net> > >> >> https://lists.sourceforge.net/lists/listinfo/mixxx-devel > >> <https://lists.sourceforge.net/lists/listinfo/mixxx-devel> > >> >> > >> > > >> > > >> > >> ------------------------------------------------------------ > ------------------ > >> > >> > 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. http://sdm.link/zohodev2dev > >> > _______________________________________________ > >> > Get Mixxx, the #1 Free MP3 DJ Mixing software Today > >> > http://mixxx.org > >> > > >> > > >> > Mixxx-devel mailing list > >> > Mixxx-devel@lists.sourceforge.net > >> <mailto:Mixxx-devel@lists.sourceforge.net> > >> > https://lists.sourceforge.net/lists/listinfo/mixxx-devel > >> <https://lists.sourceforge.net/lists/listinfo/mixxx-devel> > >> > > >> > >> > >> ------------------------------------------------------------ > ------------------ > >> > >> 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. http://sdm.link/zohodev2dev > >> _______________________________________________ > >> Get Mixxx, the #1 Free MP3 DJ Mixing software Today > >> http://mixxx.org > >> > >> > >> Mixxx-devel mailing list > >> Mixxx-devel@lists.sourceforge.net > >> <mailto:Mixxx-devel@lists.sourceforge.net> > >> https://lists.sourceforge.net/lists/listinfo/mixxx-devel > >> <https://lists.sourceforge.net/lists/listinfo/mixxx-devel> > >> > >> > > ------------------------------------------------------------ > ------------------ > _______________________________________________ > 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
------------------------------------------------------------------------------
_______________________________________________ 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
