The LibreOffice gallery sidebar is a really great option to handle often used shapes or predefined shapes. The issue is that the existing preinstalled galleries are maybe examples how to use the gallery but ordinary very unflexible to use cause: - you can't remove and ADD gallery items (cause the gallery is stored in the install folder) - the svg, png, ... image files are not themable you can't change the colors, shapes, ... dictionaries are also extensions. If the user use extensions from the extension page, the user can use the galleries how were needed BPMN, Flowchart, ... whatever. And extension can be also preinstalled (like LibO did with dictionaries).
An link to the extension page from the gallery sidebar next to the New Template can be usefull.
+1 from me
Why not installing the Galleries at the user space? Likely the same as shipping it as extension.
Please try with a nightly build.
The header was "Gallery elements only available as extension" that it's not possible to modify an preinstalled gallery is only an side effect. Or at least offer the top 10 items from the design survey 2015 (and the rest as extension) https://design.blog.documentfoundation.org/2015/04/02/libreoffice-design-session-shapes/ It's not good to make surveys and don't respect the results from the survey.
All galleries as extension leads to no gallery when build is done without it. And that might feel as broken app. If we store the shipped extensions at the user space it has the same effect but circumvents the extension management. Let's see if we get more opinions on that.
Cloph, what do you think about installing Galleries in the (writable) user space.
it's an unfortunate situation when Delete or Rename, for example, do nothing on shipped Gallery items because the user has no write permission. Either we block all functions or, better, install Gallery items in the user space.
*** Bug 158248 has been marked as a duplicate of this bug. ***
How about using something symbolic links?
Dear andreas_k, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug