Summary: | new menu item: DOCUMENT, or a new sub-menu item FILES / Outline (enhancement, development) | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | peter josvai <jepe> |
Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | RESOLVED WONTFIX | ||
Severity: | enhancement | CC: | dgp-mail, d.libo, libreoffice-ux-advise, thomas.lendo |
Priority: | medium | Keywords: | needsUXEval |
Version: | Inherited From OOo | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Crash report or crash signature: | Regression By: | ||
Bug Depends on: | |||
Bug Blocks: | 85811 |
Description
peter josvai
2020-03-06 10:28:32 UTC
Would never search for export anywhere else but File. And I don't see another root item to improve anything, plus there are likely not enough items for this category. Other opinions? Difference between File and Document wouldn't be clear (at least it isn't clear for me). Could you please give a definition for File and Document that makes a clear distinction? => NEEDINFO In principle, a Document root menu item makes sense in Writer compared to Sheet in Calc. But there are not as many items as in Calc with Sheet to justify a new root menu item. As Dieter said, normal user will be confused with File / Document. The minimum information to discuss this is a list of menu items that should moved to it. Then we can see the benefit. Otherwise and because this is a huge change in Writer UI, we should try to avoid this. -1. This proposal does nothing to make the software easier to use or understand. Such a reorganization of the core menus would make the UI even more confusing for inexperienced users. Changings for changings -1 from me I’ll go ahead and mark this as WONTFIX for a reason I will state in a moment, and with this action I don’t mean to imply that we do not welcome UX suggestions — rather the opposite! But you should weigh the consequences of making any changes to menus, and those are an increasingly painful weight put on the shoulders of documentation writers and translators, all of whom are volunteers who gain nothing from the extra effort to update their content to reflect endless UI changes. Also, users themselves are affected in that they are forced to re-learn where things are in each release. In the past we had a contributor, J. P., who implemented many menu changes in a very rapid pace, without giving a real chance to others in the documentation and l10n teams to give input. Since he was met with little friction, he went on like this for a few releases. Now we have sizable problems in updating now-obsolete help strings (since he didn’t bother with it and discrepancies were only noticed individually by bug reporters afterwards), and translators (some of them like me, polyglots who work on several languages, and in many cases in charge only by themselves of the whole translation to their languages) had to deal with the fallout. I, personally, haven’t been able to again complete to 100% the help translations to Spanish and Asturian since then, and a few years have passed! Do you see the problem now? |