https://bugs.documentfoundation.org/show_bug.cgi?id=118402
Heiko Tietze <tietze.heiko@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
CC|libreoffice-ux-advise@lists |mentoring@documentfoundatio
|.freedesktop.org |n.org,
| |tietze.heiko@gmail.com
Summary|Needs ellipses: "Manage |Needs ellipsis: "New >
|Templates" menu item and |Templates"
|window |
Status|UNCONFIRMED |NEW
Keywords|needsUXEval |difficultyBeginner,
| |easyHack, skillDesign,
| |topicDesign
--- Comment #5 from Heiko Tietze <tietze.heiko@gmail.com> ---
(In reply to Explorer09 from comment #1)
I make a correction here. Adding ellipsis on File->Templates->"Manage
Templates" might not look sensible (as it does not _require_ input on
managing Impress templates). But a similar menu item,
File->New->"Templates", may need ellipsis, so it becomes
File->New->"Templates..."
That would have been my reply for Manage Templates. We shouldn't overdo
ellipsis, otherwise the information becomes pointless - and that's why it makes
sense in New because we indicate the difference to the other items.
This is a very simple easyhack (how to find the code pointer:
https://design.blog.documentfoundation.org/2018/02/28/easyhacking-all-about-terminology/)
--
You are receiving this mail because:
You are on the CC list for the bug.
Context
- [Libreoffice-ux-advise] [Bug 118402] Needs ellipsis: "New > Templates" · bugzilla-daemon
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.