Open nebhale opened 7 years ago
Interesting @nebhale . I'm even thinking that we extend our auto-hiding from 3.4.0 to include ALL of the UI chrome.
I can see a situation where you've just got a window open in your browser and you'd want the top bar to exist at all times but for wallboards at the very least, it seems like being able to hide even that is useful.
But moving your mouse being enough to show it all again, would probably be enough in that case as well.
Any update?
@goody80 its still an interesting idea but I don't think we'll have a chance to pick up this story in the near future 😓
@jama22 Yeah, I know, So we have to use iframe only for this.
Let's see further :)
Thanks for your feedback!
I think the HIGH-DENSITY mode ( http://your_concourse_url/hd) is what you are looking for.
High-density mode doesn't solve for this request as it only applies to the main landing-page dashboard. If you review the mockups above, you'll see that they're trying to show the team-level pipelines (fully expanded) but without the nav-bar at the top. It has been 6 years since I opened the issue, but I'm pretty sure there's still no way to hide that top bar in any view including the High-density view.
Currently, when viewing a pipeline there is no way to hide all of the UI chrome. Hiding the chrome of the UI can be useful in cases where the display of the pipeline display is static (e.g. a wallboard) and therefore the version of Concourse, the legend, and the pipeline group aren't necessary as they aren't dynamic. This is doubly useful in cases where a collection of pipelines are displayed in a single page. For example, the Cloud Foundry Java Experience team uses a wallboard that is more or less:
On load, it's pretty crowded, with mostly redundant and static information:
With the new legend hiding feature in 3.4.0, it's a bit better but there's still a bunch of information that changes rarely (if ever) and isn't important to display all the time:
Ideally there would be a way to disable all of the UI chrome (and bonus points for allowing the pipelines to occupy all the recovered space):
My modest proposal would be that any URI would have an optional query parameter (e.g
?chrome=false
) that could be used to indicate that the UI chrome elements should not be added when the page is rendered. This would allow the previousiframe
based example to remove the UI chrome simply by adjusting the URI that is requested.