When notebookbar mode is enabled, a number of implementations would like to disable decks of the sidebar, like for example the properties deck. So we would need to implement this feature and have it configurable in XML. officecfg/registry/data/org/openoffice/Office/UI/Notebookbar.xcu
(In reply to Yousuf Philips (jay) from comment #0) > ... a number of implementations would like to ... I do not really understand what you mean with this. Apart from that: the question how to handle notebookbar <> sidebar touches the issue of providing a clear switch to choose various interface types (basic / expert / ms-office-style / ... /...), not?
(In reply to Cor Nouws from comment #1) > I do not really understand what you mean with this. So lets say the tabbed notebookbar wants to define that the properties deck of the sidebar should be disabled when the notebookbar is enabled, we should have the option to do that.
(In reply to Yousuf Philips (jay) from comment #2) > So lets say the tabbed notebookbar wants to define that the properties deck > of the sidebar should be disabled when the notebookbar is enabled, we should > have the option to do that. Ah bon, compris! Merci,
I guess we can also add an option to completely hide sidebar decks in Notebookbar mode, when you move the cursor to there, they will appearing.
I would change the status to wantfix cause 1. you can activate/deactivate the sidebar within the NB (tabbedbar -> viewtab) 2. define specific decks that will be hiden in some specific NB implementation will confuse when you read a tutorial or you switch between different layouts (tabbed compact on laptop and groupedbar full on desktop) I don't see the benefit of deactivate specific sidebar decks. general NB tabbed don't need the sidebar but NB tabbed compact can need it. I would leave it as it is.
(In reply to andreas_k from comment #5) > I don't see the benefit of deactivate specific sidebar decks. general NB > tabbed don't need the sidebar but NB tabbed compact can need it. I would > leave it as it is. You mean: why limit the choice that users have to do as they prefer?
The idea is likely not to prevent users from a workflow. So what Jay had in mind was probably to collapse the content panel depending on the NB. An example is the inserting shapes - position/size is collapsed.
(In reply to Heiko Tietze from comment #7) > The idea is likely not to prevent users from a workflow. So what Jay had in > mind was probably to collapse the content panel depending on the NB. An > example is the inserting shapes - position/size is collapsed. Ah, then this issue should read "hide .. " and not "disable.." ?
(In reply to Heiko Tietze from comment #7) > The idea is likely not to prevent users from a workflow. So what Jay had in > mind was probably to collapse the content panel depending on the NB. An > example is the inserting shapes - position/size is collapsed. No not collapsing content panels, hiding the entire deck, including the icon in the NB button bar.
(In reply to Yousuf Philips (jay) (retired) from comment #9) > No not collapsing content panels, hiding the entire deck, including the icon > in the NB button bar. That looks to me as if that would limit users choice. I am in favor of offering a default mode - making sense for most users.
I don't see a big benefit in addition have an icon available don't be a difference between simple ui and complex one. Maybe you have a mockup what's the benefit.
(In reply to Cor Nouws from comment #10) > That looks to me as if that would limit users choice. > I am in favor of offering a default mode - making sense for most users. The default mode is what LO comes with, but UI layout designers should have the control to decide what is or isnt available to users in their designed layout. For example, heiko decided that the sidebar should be available to users who use his NB implementation (contextual groups), while I decided that the sidebar shouldnt be available to users who use my NB implementation (contextual single).
(In reply to Yousuf Philips (jay) (retired) from comment #13) > ... For example, heiko decided that the sidebar should be available to > users who use his NB implementation (contextual groups), while I decided > that the sidebar shouldnt be available to users who use my NB implementation > (contextual single). Now imagine that the default mode is: NB X with Side Bar not activated. And the users freedom: activate it. Just my idea, of course.
> Now imagine that the default mode is: NB X with Side Bar not activated. > And the users freedom: activate it. > Just my idea, of course. +1
(In reply to Cor Nouws from comment #14) > Now imagine that the default mode is: NB X with Side Bar not activated. > And the users freedom: activate it. > Just my idea, of course. Users will always have the option to activate the sidebar, toolbar, etc, but it would be hidden by default when switching to a view which defines it to be hidden.
can be usefull, but all the show/hide stuff (menubar, toolbars, sidebar, ...) make the configuration of LibO very complex so I would suggest to make it an wantfix to reduce the complexity.