Description: I juggle LibreOffice between a horizontal and vertical monitor, as well as trackpoint, trackpad, and mouse. Despite always wanting to search for “the best interface”, I feel discouraged from experimenting with notebookbars. The menu bar, sidebar, toolbars, and status bar can all be toggled on and off independently, but choosing a notebookbar is only possible through “View -> User Interface...”. Unfortunately, hat dialog box changes all parts of the UI. I would really appreciate a “View -> Notebookbar” menu option. View -> Notebookbar could allow me to swap between Tabbed, Tabbed Compact, Groupedbar Compact, Contextual Single, and None without moving my toolbars around. Some notebookbars require the menu bar to appear, but otherwise View -> Notebookbar should have no effect on the other “-bars” in LibreOffice. Steps to Reproduce: 1. Arrange LibreOffice's toolbars as you see fit. 2. Decide that you want to change your NotebookBar, for example, let's say you no longer need the Tabbed NotebookBar because you found toolbars to do everything you needed. 3. Go to the menubar option "View" and look for an appropriate toggle. Actual Results: The only option that can change the notebookbar is the "User Interface..." dialog box. Unfortunately, choosing a different UI variant will remove all the toolbars you have open. Expected Results: Alongside the Menu Bar, Sidebar, Status Bar, and Toolbars options in the View dropdown, a new option named "Notebookbars" should be available. Similar to the way the "View -> Toolbars" dropdown lets you turn toolbars on and off, "View -> Notebookbars" should allow you to directly switch between the different types of NotebookBars. Reproducible: Always User Profile Reset: No Additional Info: I am NOT proposing the ability to turn on multiple notebookbars simultaneously; that's currently not possible and it might create extra programming (and usability) headaches. I would prefer a dropdown menu to a dialog box. "View -> User Interfaces..." is a dialog box because it provides context for users to make a big decision about their whole UI layout. A notebookbar is arguably just a really fancy premade toolbar; it should be turned on and off like a toolbar. Some notebookbars share the name of their associated User Interface. For example, activating the Tabbed UI will activate the Tabbed Notebookbar. If this enhancement is approved, then the names will need to change eventually. I haven't thought of any names to suggest, honestly.
UX team, what do you think of having the ability to toggle the notebookbar on and off just like toolbars, independently of what UI is used? To me, that sounds very niche and messy, and I'd rather see bug 148121 implemented as a "close-enough" alternative.
As a MUFFIN proposal, this has merit. We already can interactively toggle view of 'Main menu', any toolbar, the 'Sidebar'--why not implement a "visible" toggle for the 'Notebook bar' MUFFIN mode elements? And allow user to mix-and-match their UI. State would need to be recorded to user profile, per module for persistence between sessions. And of course provide means to reset to reasonable defaults. Additional "nice-to-do" enhancement would also track the per display layout--think an install on a laptop when connected to external monitor(s). Keep UI layout for use on main display only, and set(s) for when using external monitors.
Wouldn't invest any effort in a switch on/off function for the UI layout. And it's possible out of the box: enable the Tabbed UI, switch on the menubar at the View context menu, and show the toolbars you like. Minor issue: the toolbars are not remembered, at least not for Formatting and Standard.
We discussed the topic in the design meeting. While I thought the request is to enhance the UI selection dialog it's actually the lack of persistence what users configure. In fact we remember whether the menubar is on/off but not any of the other toolbars or sidebars (which can be enabled easily). Storing user settings is desired. Given that most users will use the Notebookbar without classic elements, the issue is of low priority.