new feature idea: GUI/skin paging
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mixxx |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
The skins are getting as full of controls as we can make them; with the new FX array added to the samplers, and now the option of four decks, there is less and less leeway. especially for smaller screens and especially for aesthetics. Elegance becomes difficult when the screen is just a mass of widgets practically touching each other.
What I propose is "slide out" pages that emerge when the mouse stays at the edge of the screen for a configurable amount of time. This is a common feature of Android and various web applications. I believe Tumblr uses it and the Lightning browser for Android uses it, though the idea goes as far back as taskbar hiding in various desktop environments/
The one hitch I foresee is what to do when Mixxx isn't in fullscreen mode, but a clickable tab should suffice. It would also be nice to allow the cursor to sense the edge of the window so that if reaching that vertice from the inside, it could trigger the drawer/panel even without that vertice being flush with the monitor edge.
Should I submit this as a blueprint, or is this adequate?
Changed in mixxx: | |
status: | New → Confirmed |
importance: | Undecided → Wishlist |
tags: |
added: skin removed: feature wishlist |
It is OK for me to track the idea here.
Am 24.03.2016 9:55 nachm. schrieb "RAWRR" <email address hidden>:
> Public bug reported: shells. /bugs.launchpad .net/bugs/ 1561730 shells. /bugs.launchpad .net/mixxx/ +bug/1561730/ +subscriptions
>
> The skins are getting as full of controls as we can make them; with the
> new FX array added to the samplers, and now the option of four decks,
> there is less and less leeway. especially for smaller screens and
> especially for aesthetics. Elegance becomes difficult when the screen is
> just a mass of widgets practically touching each other.
>
> What I propose is "slide out" pages that emerge when the mouse stays at
> the edge of the screen for a configurable amount of time. This is a
> common feature of Android and various web applications. I believe Tumblr
> uses it and the Lightning browser for Android uses it, though the idea
> goes as far back as taskbar hiding in various desktop
> environments/
>
> The one hitch I foresee is what to do when Mixxx isn't in fullscreen
> mode, but a clickable tab should suffice. It would also be nice to allow
> the cursor to sense the edge of the window so that if reaching that
> vertice from the inside, it could trigger the drawer/panel even without
> that vertice being flush with the monitor edge.
>
> Should I submit this as a blueprint, or is this adequate?
>
> ** Affects: mixxx
> Importance: Undecided
> Status: New
>
>
> ** Tags: feature gui wishlist
>
> --
> You received this bug notification because you are a member of Mixxx
> Development Team, which is subscribed to Mixxx.
> https:/
>
> Title:
> new feature idea: GUI/skin paging
>
> Status in Mixxx:
> New
>
> Bug description:
> The skins are getting as full of controls as we can make them; with
> the new FX array added to the samplers, and now the option of four
> decks, there is less and less leeway. especially for smaller screens
> and especially for aesthetics. Elegance becomes difficult when the
> screen is just a mass of widgets practically touching each other.
>
> What I propose is "slide out" pages that emerge when the mouse stays
> at the edge of the screen for a configurable amount of time. This is a
> common feature of Android and various web applications. I believe
> Tumblr uses it and the Lightning browser for Android uses it, though
> the idea goes as far back as taskbar hiding in various desktop
> environments/
>
> The one hitch I foresee is what to do when Mixxx isn't in fullscreen
> mode, but a clickable tab should suffice. It would also be nice to
> allow the cursor to sense the edge of the window so that if reaching
> that vertice from the inside, it could trigger the drawer/panel even
> without that vertice being flush with the monitor edge.
>
> Should I submit this as a blueprint, or is this adequate?
>
> To manage notifications about this bug go to:
> https:/
>