Description: Hi! I'd like to give you my mockup. There you go: https://drive.google.com/file/d/18WKZ3sqZqeUBe4C05K-J_ynTBJZhQfzL/view?usp=sharing Actual Results: - Expected Results: - Reproducible: Always User Profile Reset: No Additional Info: -
In general, changing the menus is not very much welcome at the users and the benefit should be very clear. Goal of this exercise is likely a) to save space and b) to better sort the content. And I definitely like it (also big thumbs up for the elaborated overview). Most of the text attributes are also accessible via toolbar/notebookbar and sidebar. So "hiding" them in a submenu seems to be okay. Andreas tried to make the context menus more consistent and placed the Properties... always at the bottom. Not sure if that makes sense here, just to mention. Component is Impress; shouldn't it rather be Writer? And ideally aligned with other modules.
(In reply to Heiko Tietze from comment #1) > In general, changing the menus is not very much welcome at the users and the > benefit should be very clear. The goal of this exercise is likely a) to save > space and b) to better sort the content. You right, Sir. Alternatively, we can make a notification/dialog introducing this new menubar, for example, "You're currently using the new menubar" with options: "Keep using it" and "Revert to the old menubar". > Andreas tried to make the context menus more consistent and placed the > Properties... always at the bottom. Not sure if that makes sense here, just > to mention. Could you send me Andreas' work, Sir? > Component is Impress; shouldn't it rather be Writer? And ideally aligned > with other modules. It's made to Impress, Sir. I didn't know if you all talked that the idea is supposed to Writer. Maybe I got you wrong
We discussed the proposal in the design meeting and appreciate the approach. However, it a) changes on the menu should be done carefully (or optionally, see bug 120132, and b) need a broad consensus as it affects the familiarity with the UI for all users. So please add other modules to the mockup (and share it on here as access to GDrive is not always possible/wanted).
Let's will not touch main menu -1 from me
(In reply to Roman Kuznetsov from comment #4) > Let's will not touch main menu > > -1 from me Would you mind to give some kind of explanation :-). I'm lacking telepathy skills. Ideally every element change should be discussed one by one. I'm do agree on a some of the suggestions. Others are more problematic. Like putting change case under a submenu (looks nicer, not sure how would be received). Putting crop settings together makes sense, IMHO. At some point we end up at the same discussion as the toolbar/tabbed interface. So different being able to set the 'old' menu configuration somewhere for enduser comp-ability reasons ;-) One of the arguments of NeoOffice using 4.4.7.2 as baseline was the menu structure. Not the best argument I have heard, but
(In reply to Heiko Tietze from comment #3) > So please add other modules to the mockup (and share it on here as access to GDrive is not always possible/wanted). No answer, resolving now.