https://bugs.documentfoundation.org/show_bug.cgi?id=91781
--- Comment #14 from Yousuf (Jay) Philips <philipz85@hotmail.com> ---
Created attachment 116249
--> https://bugs.documentfoundation.org/attachment.cgi?id=116249&action=edit
Writer's tools menu stats
(In reply to Joel Madero from comment #12)
In that response I didn't really see any proof - can you raise this at your
next design call?
What type of proof are you looking for? I have been analyzing the OOo user
stats and have spreadsheets per application, similar to what can be seen in the
attachment of Writer's tools menu. These spreadsheets are not fully complete
yet, but i plan to publish them.
I had discussed this issue previously in a design call with Kendy after going
through numerous bug reports with Cor, Andy and the gang about other menu bar
submenus and context menus (bug 85945, bug 86048, bug 86048, etc). I will bring
up the issue again today at the design call.
I had assumed that design team was
discussing these changes but with the comments here, it seems like that is
not the case.
The design team are discussing these changes, which is why i opened this bug
report. They wouldnt be able to fully evaluate these changes if it wasnt
available in a daily master build and them taking the new menus for a spin.
--
You are receiving this mail because:
You are on the CC list for the bug.
Context
- [Libreoffice-ux-advise] [Bug 91781] Reorganization of the menu bar for Writer · 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.