https://bugs.documentfoundation.org/show_bug.cgi?id=169214
--- Comment #7 from Eyal Rozenberg <[email protected]> --- (In reply to Telesto from comment #6) > > Actually - no, that's not the behavior of File > New ; it opens a submenu, > > and that's it. > > I can Left Click "New" in the main drop down, with navigating the submenu to > open a new Writer document (assuming using Writer). At least on macOS Are you sure you're not just releasing the mouse and letting the first submenu item be selected? ... Well, maybe it's MacOS-specific behavior. On Linux (and Windows IIANM), it doesn't work that way. But if MacOS really has this kind of widget, maybe it's less preposterous to also have it on other platforms. Still, let this stay WONTFIX unless more people start clamoring for this. > (In reply to Eyal Rozenberg from comment #5) > The resource allocation is implicitly assessed in any enhancement request, > IMHO. Well, it's not assessed by the people making the request; and it's not assessed - for the most part - in design meetings discussing enhancement requests. So these requests definitely become NEW with nobody committing any resources, or assessing resource availability, for those enhancements. > Not consistently, though. The list of possible enhancements is in > principle endless. Maybe even as expert setting, if we want to be geeky. You > need some demarcation criterium. Well, one demarcation criterion is the willingness to request the enhancement. That already prevents totally-frivolous ones. And the next criterion is convincing a QA person, or barring that the design meeting participants, that it serves a relevant use case and does not better fit in an extension. > Is it useful having a bug/enhancement > idea's floating around as nice to have but realistically not gonna happen in > lets say next 50 years. I don't know about LO, about in Mozilla, there are _critical_ enhancement requests that have been waiting around for nearly 30 years now. So, the fact that something might not happen for several decades does not mean it should not be on file. Moreover - it's almost impossible to tell whether an enhancement request deemed useful would be picked up by someone or not. These things surprise you. > At which point it might be superfluous after all. > Everything might be done by AI or different UI design because everybody > using VR. 40 years ago you already had a mostly-similar desktop environment to what we have today, if we focus on the basics. > There is already 'lack' of direction regarding user interface styles. Semi-agreed, but - that does not mean we should prune and avoid ideas at the bug tracker level; rather, that should happen through the policy-making mechanisms and resource-allocation-coordination mechanisms. We lack those, unfortunately: The ESC has formally stated it does not actually steer the project; and the TDF board of directors... well, let's say it has its problems. > * complexity; having multiple UI's requires a lot more documentation, > testing, maintaining etc Unfortunately, that hasn't happened... someone just gave the green light to us shipping with 7 UI modes. The documentation still assumes menus+toolbars IIANM. > * impurity's in design. So a flaw in Tabbed UI being presented as non-issue > (trivial) because other UI elements cover this aspect (sidebar/menubar). That's very interesting! And quite sad. But we're really getting off topic here... I want to encourage you to maybe write something up, either to send on the design mailing list, or to present at a conference, or even just to propose a discussion in one of the design meetings, about these matters. -- You are receiving this mail because: You are the assignee for the bug.
