Jump to content
Clovis Ramsay

Reclaim Screen Space: How to gut the UI?

Recommended Posts

The biggest problem with what the OP was suggesting was there's a LOT of the UI that can be folded away and hidden until you need it that takes up FAR more screen real estate than what he was suggesting losing, plus the things he suggested cutting out are kind of important for actually making the program work. If you remove the scrollbars, for example, how do you navigate around your project? A lot of the menus that he was suggesting should be cut out are project specific rather than global menus, so it'd force you to remember a bunch of key commands, and you'd have no visual indicator that something was active or not (anyone who uses Ripple Edit a lot will know what a good day it was when we got the indicator icon). You lose core functionality to save a tiny amount of space.

This isn't Cakewalk bias, as much as we're obviously here because this is our DAW of choice and are comfortable with the workflow, there's some very logical reasons that some of this stuff is actually in there and can't be removed. Like I said, you could get rid of 30 or 40 pixels worth of borders, scrollbars and menus... or... you could fold away great chunks of the UI and get far more screen real estate back just by taking advantage of how Skylight is designed.

Example: 

Here's my full layout:

Full.thumb.png.6b69b32eaf710e0f3f85c0536d63e9ff.png

Versus my compact layout for a single, low res panel:

Compact.thumb.png.4e0d5dbc3ef2360a9fb83322d8282416.png

I'm saving FAR more space folding away the panels I don't use than I would do by hiding a few menu and scroll bars,

 

Edited by Lord Tim

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×
×
  • Create New...