Summary: | Make configuration extensionizable | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Francisco <franciscoadriansanchez> |
Component: | UI | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | enhancement | CC: | cno, heiko.tietze, jmadero.dev, libcub, thomas.lendo, vsfoote |
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
See Also: |
https://bugs.documentfoundation.org/show_bug.cgi?id=52387 https://bugs.documentfoundation.org/show_bug.cgi?id=64439 |
||
Whiteboard: | |||
Crash report or crash signature: | Regression By: | ||
Bug Depends on: | |||
Bug Blocks: | 107636 |
Description
Francisco
2013-01-17 00:42:37 UTC
Indeed, and a good idea (although perhaps quite difficult to implement). Thank you for reporting this enhancement request! I can confirm that this is a valid enhancement request on: Version: 4.3.0.0.alpha0+Build ID: daa57a101a20e0b37db7090796ad002b8d192b9b Date: Sun Dec 15 23:07:57 2013 +0100 Platform: Ubuntu Linux 13.10 x64 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + As I've been able to confirm the enhancement request I am marking as: New (confirmed) Enhancement Low - there is a workaround to just keep your entire profile, this would just allow maintaining specific configurations vs. an entire profile. Useful, but not impossible to currently keep configurations. Also, implementing may be difficult. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material *** Bug 120160 has been marked as a duplicate of this bug. *** 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.) We should reduce the scope of this bug to the second issue (kind of repository of profile sharing - a privacy issue?) and the export and import issezcsn be handled in bug 52387. Adding needsUXEval. I love the idea of an extension for this. We could add Export.../Import... and have it together with Reset in a menu button. Export should list top level items to allow unchecking personal information. Something like Export configuration data: [x] General [x] User Data <danger icon> [x] General [x] View [x] Print [x] Path <danger icon> etc. [/] Load Save [x] General [ ] VBA Properties ... with an icon to indicate sensitive information. The import function needs to match capabilities. If the binary doesn't support a language which was previously saved it must not crash. And last but not least I would prefer XML output to allow modification to the exported data. There is no use case to share (parts) of the user configuration. If you want to save all, just copy the file. Sharing with other is a security/privacy topic and unclear when needed. So WF'ing the duplicate ticket. *** This bug has been marked as a duplicate of bug 52387 *** *** This bug has been marked as a duplicate of bug 120719 *** |