Community
Participate
Working Groups
When using Orion on a small-screen device, I really start to notice how much vertical space is taken up by the Orion banner. In keeping with "giving the pixels to the content", I'd like to hide the Orion banner so I have more room for the editor/compare view/etc.
are you thinking a way to dismiss it (and remember that it should stay closed?) A longer term solution is custom layouts (CSS3 media queries) where we could style the page for different devices. But I assume you mean do something now/soon...
I'd like to close the bottom banner too if I could. The one that starts with "this is a build of Orion..."
> are you thinking a way to dismiss it (and remember that it should stay closed?) Yes: for now, being able to collapse it like the outline view would be enough. > I'd like to close the bottom banner too if I could. +1
Collapsing the header would lose the breadcrumb though. Since trees are really useless on a small device I found myself using the breadcrumb all the time to move around. Also there is no equivalent to the (Navigator | Sites | Plugins | Repositories) links across the top if the banner is closed. Wouldn't you just zoom the screen slightly when you want to focus on the content?
(In reply to comment #4) > Collapsing the header would lose the breadcrumb though. Since trees are really > useless on a small device I found myself using the breadcrumb all the time to > move around. Also there is no equivalent to the (Navigator | Sites | Plugins | > Repositories) links across the top if the banner is closed. I don't rely on either of those very often, so I wouldn't mind seeing them hidden inside a "nav" icon or similar when space is limited. (My current workflow is to open all the files I need to edit in separate tabs and leave them open. In those tabs I'd like to see as much code as possible. I have a separate tab I use for bouncing between Plugins/Repositories/Sites.) > Wouldn't you just zoom the screen slightly when you want to focus on the content? In my case I was using a small notebook, not a tablet, so my browser's zoom feature doesn't pan the banner out of view, it just makes everything appear larger...
So you wouldn't want a global setting that applies to all tabs, but just be able to close the header/footer on any given page...
I opened bug 359875 as a more future looking bug to capture ideas for alternate layouts on small devices. I thought the point about the breadcrumbs is a good one...on a small device we may want to separate the breadcrumb from the banner (ie, an alternate banner which is only a breadcrumb), or even the breadcrumb appearing in some other navigation menu. Then this bug can focus on the "what can we do right now" to make things manageable on different devices, such as collapsing the header and footer (In reply to comment #6) > So you wouldn't want a global setting that applies to all tabs, but just be > able to close the header/footer on any given page... And in this case storing the preference in a non-user scope makes sense because the user would have a different preference when working on a different device.
i'll try something quick and dirty for M1, probably just a keybinding. We can worry about a general affordance when we look at visual design/layout in M2.
(In reply to comment #8) > i'll try something quick and dirty for M1, probably just a keybinding. We can > worry about a general affordance when we look at visual design/layout in M2. Did the quick and dirty binding, ctrl+shift+m will toggle the banner/footer. Made a note in bug 349634 about having an affordance and possibly an alternate layout that includes some elements (breadcrumb). There is also the issue of whether we should cache state (but then you have to think about how to get the elements back when you've toggled everything off). So for now the state is not captured and reload will get everything back. I'm sure people will want smarter behavior but that will require some visuals. (ctrl+O uses a cookie to remember outline state but you always have the split affordance for getting it back.)
This is great :)
