A completely new dialog or a new tab in the 'Customize' dialog can be introduced where the user can save, load and set back to default the whole customization that was done in the UI for each application or for a file (see 'Scope' in Tools > Customize > Menus > Scope) or for entire LibO at once. Customization includes: * menu changes * toolbar changes (Notebookbar changes in the future) * context menu changes * keyboard shortcut changes * presentation of the sidebar (open/closed/collapsed, which tab is open, width and position of sidebar) * window size and position (fullscreen, maximized or left bound or centered on the screen or whatever) as well as * toolbar icon size (from Options > LibO > View) * sidebar icon size (from Options > LibO > View) * Notebookbar icon size (from Options > LibO > View) * icon style (from Options > LibO > View) * icons in menus (from Options > LibO > View) * shortcuts in context menus (from Options > LibO > View) * mouse positioning (from Options > LibO > View) * middle mouse button (from Options > LibO > View) * font list preview (from Options > LibO > View) * Theme (from Options > LibO > Personalization) * UI language (from Options > Language Settings > Languages) * extended tips (from Options > LibO > General) and maybe other visual settings. This feature could be used as a 'UI profile' and would make it easier for users to take UI customizations to another LibO installation or to share a profile. To avoid the problem of UI elements for non-existing commands (if an existing command changed or was deprecated) or that new commands would be overwritten and made invisible by importing an old profile, the most optimal way to save such UI profile is to save only the changed elements instead of the whole structure. (For example, if a user adds an command to a context menu, not the entire context menu structure should be saved in the profile but only the added command with information at which position it was inserted.)
*** This bug has been marked as a duplicate of bug 59493 ***
*** This bug has been marked as a duplicate of bug 52387 ***
*** This bug has been marked as a duplicate of bug 120719 ***