Bug Hunting Session
Bug 59493 - Allow exporting configuration files easily and make some kind Configuration repository
Summary: Allow exporting configuration files easily and make some kind Configuration r...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: low enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: needsUXEval
: 120160 (view as bug list)
Depends on:
Blocks: User-Profile
  Show dependency treegraph
 
Reported: 2013-01-17 00:42 UTC by Francisco
Modified: 2019-08-27 06:38 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Francisco 2013-01-17 00:42:37 UTC
If I remember right, one of the thoughts about a new UI for OpenOffice back in Renaissance project was that OOo was already good, but the defaults were the problem.

I my case it _is_ a problem, and I'm always changin many configurations  from position and coontent of toolbars, to linestyles, gradients andcolor palette. This happens when, for some reason, my profile gets corrupt and I need to reset, or I have a new installation and dont have any copy of my profile... or whatever.

The way a tray to conserve my configurations is copying my entire profile from one installation to another. I understand that I'm copying maybe a lot files unnecesary since I know that where are some of the configurations stores. For example, I know that my default color palette is in config/standard.soc. For there are many other configurations that are stored in different places, or even in "registrymodifications.xcu". 

My "idea" embraces 2 things: allow exporting personalizations easily, without the need of going to the profile and copying folder, but having a button that exports literally all configs to a simple file (maybe some kind of ZIP?), which can be loaded as extensions. The main reasoning behind this is just make it easier export and import configurations, and avoiding the necessity of knowing where configs are for a simple user.

The second point is sharing: I cannot ensure but I think that, like me, there are other people that dislike some defaults configuration in LibO. So a way of easily share confugurations, like some kind of repository could be good. It could be integrated to the extensions/templates webpage, and also, having a way to vote which set of configurations results in a favourite could help LibO to set better defaults.

It's an idea.
Comment 1 Joel Madero 2013-12-28 17:55:38 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
Comment 2 Thomas Lendo 2018-10-17 19:50:26 UTC
*** Bug 120160 has been marked as a duplicate of this bug. ***
Comment 3 Thomas Lendo 2018-10-17 19:51:09 UTC
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.)
Comment 4 Thomas Lendo 2019-08-27 06:38:00 UTC
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.