[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[libreoffice-projects] Minutes from the UX/design meeting 2020-Mar-18


Present: Muhammet, Cor, Heiko
Comments from: MikeK, Regina

Tickets/Topic

* Branding for 7.0
+ https://bugs.documentfoundation.org/show_bug.cgi?id=130778
+ see also https://wiki.documentfoundation.org/Marketing/Branding/Ideas
+ will be on this list until it's solved
+ CfP1 https://listarchives.libreoffice.org/global/design/msg09227.html
+ CfP2 https://listarchives.libreoffice.org/global/design/msg09272.html
+ NEXT STEPS?
=> put the ideas into the program and wait for comments

* Overwriting Writer styles does not overwrite changes to Marginalia paragraph style
+ https://bugs.documentfoundation.org/show_bug.cgi?id=130719
+ define _all_ internal styles in template Style > Default?
+ MikeK:
1) all the styles in shipped templates (maintenance burden, possible implementation problem)
2) Load Styles to always load full set of standard styles (would break current workflow / possible disallow the opposite need)
optionally, "[x] Overwrite standard styles absent in the template with defaults")
3) NOTABUG/WONTFIX (maybe with reanming the function "Load Styles from Template")
* "Load styles" should not import content
+ https://bugs.documentfoundation.org/show_bug.cgi?id=131347
+ rename "Load Style" to "Load Template" and rename/reorganize the checkboxes?
+ NAB (MikeK)
=> preference to NAB (renaming/documentation) (Muhammet)

* Make font installation optional
+ https://bugs.documentfoundation.org/show_bug.cgi?id=91886
+ big +1, ideally as extension (Heiko)
+ good idea (Muhammet)
+ disable font installation in the wizard might be unintentionally and cannot be reverted later (Muhammet)
=> summary "Make fonts extensionizable", hardware/platform -> All, Block -> clean

* Gallery updates
+ https://bugs.documentfoundation.org/show_bug.cgi?id=131319 gallery: update Symbol gallery
+ looks good and could hold also what's now planned for bullets
+ https://bugs.documentfoundation.org/show_bug.cgi?id=131318 gallery: add Widget gallery
+ too many items, not so relevant though named as a use case some times
https://design.blog.documentfoundation.org/2016/04/01/the-many-faced-god-part-2-how-libreoffice-draw-is-expected-to-evolve/
+ https://bugs.documentfoundation.org/show_bug.cgi?id=131308 Gallery: update Computer gallery
+ don't see any need for symbols under "Computer"
+ maybe replace COmputer by Widgets
+ any improvement is good (Cor)
=> go ahead
+ another idea for a gallery would be music notes

* PRINTING: Option to print grid in Draw
+ https://bugs.documentfoundation.org/show_bug.cgi?id=68662
+ could be done per extension (moved), implemented to printing options (new),
or realized as a layer (wfm)
+ sounds reasonable, sometimes you want to print the grid (Cor)
+ grids are helper functions and can be complex (thickness, size, strightness, color etc. might need to be configurable)
+ see also https://bugs.documentfoundation.org/show_bug.cgi?id=130995
+ ship (a couple of) templates with grids to a) solve the actual problem and b) illustrate how its done
+ can also be shared as extension
=> do it


--
To unsubscribe e-mail to: projects+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/projects/
Privacy Policy: https://www.documentfoundation.org/privacy

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.