Present: Hossein, Cor, Heiko
Comments: Stuart, Stephane, Shu, Eyal, David
Tickets/Topics
* Removing "contextual groups" from the list of NB variants
+ Justin resolved some related tickets as WF/WFM
+ https://wiki.documentfoundation.org/Design/Guidelines/ToolBar
+
https://design.blog.documentfoundation.org/2016/12/21/evolving-past-the-restrictions-of-toolbars/.
+ pro removing: experimental state for long, some effort needed
+ con: would be a pity to just follow what others do
+ too many UI options anyway (Hossein)
+ unfortunately we do not have the manpower to improve these ideas
+ we have this ticket somewhere (Heiko)
* Add an "all pages" view mode to Draw to scroll through all pages
in canvas (without needing Page Pane)
+ https://bugs.documentfoundation.org/show_bug.cgi?id=156087
+ similar to Writer's multiple-page view; expected by many
users (Stephane, Shu)
+ Impress has the Slide Sorter in an extra view mode
+ Draw is not a PDF viewer, WF (Stuart)
+ missing function (Shu)
+ Draw is not meant to show multi-page documents,
dup of bug 141732 or invalid (Eyal)
=> resolve WF
* Rename "rotation object" to "solid of revolution"
+ https://bugs.documentfoundation.org/show_bug.cgi?id=156099
+ https://en.wikipedia.org/wiki/Solid_of_revolution (Tuomas)
+ ODF defines "a three-dimensional rotation shape based on the
given polygon"; the more convoluted "solid of revolution" while
lexically correct adds nothing to the UI or the UX (Stuart)
=> resolve NAB
* Support distinction rather than override of conflicting
subdocument styles
+ https://bugs.documentfoundation.org/show_bug.cgi?id=155740
+ unclear use case (David)
+ some confirmation per document (Shu)
+ if we better go with a global master switch (Heiko)
+ master documents are a special workflow aiming for style
consistency, WF (Mike, Hossein)
+ unclear use case (David)
+ copy/paste could solve alternative workflows (Shu)
=> resolve WF
* When setting the Heading/Outline Numbering for a level to "None",
still getting separators
+ https://bugs.documentfoundation.org/show_bug.cgi?id=156089
+ works like in MSO, WF (Justin)
+ no reason to block, WF (Heiko)
+ asking to _clear_ the separator fields in case of None (Eyal)
+ remembering "Chapter/:" is not a (good) solution since users may
change it for None into "-/>", or the like, making it very
difficult to follow
+ behavior existing for years shouldn't change without
good reasons (Hossein)
+ list style is something you shouldn't change multiple times
=> resolve WF
* Autocorrect replaces " - " with " – " instead of " — "
(en-dash instead of em-dash)
+ https://bugs.documentfoundation.org/show_bug.cgi?id=156046
+ maybe drop the conversion of single hyphen (Stuart)
+ typically two hyphen is an EN-dash, three EM (Heiko)
+ two dashes with / without spaces is kind of standard and
working like this in MSO (Hossein)
+ clearly described in
https://help.libreoffice.org/latest/en-US/text/shared/01/06040100.html
+ two dashes without spaces like 1--2 is not correctly
converted (Heiko)
=> bug; do not change the behavior as described in the help
--
To unsubscribe e-mail to: design+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/design/
Privacy Policy: https://www.documentfoundation.org/privacy
Context
- [libreoffice-design] Minutes from the UX/design meeting 2023-Jul-13 · Heiko Tietze
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.