Community
Participate
Working Groups
I noticed 2 ways in which the menubars shown on the editor page (File, Edit, View, etc) do not behave like menubars in other windowing systems**: I) Orion's menubars open on a "click" event, i.e. you have to release the mouse button in order to see the menu contents. Other windowing systems show the menu on mousedown. This feels snappier. 2) You cannot quickly scan through several menus by opening one and then hovering over the others with the mouse cursor -- you must click each menu individually. These are minor issues, but they contribute to a perception of slowness/clunkiness in the UI. ** Tested Windows, OS X, and Google Docs
OK, so the first step here is to gather up all the menu processing / rendering into a simpler structure. We need to replace the current hard-coded calls to 'addCommandGroup' and 'registerCommandContribution' with fixed structures. Ultimately there should be *one* structure that completely defines the 'main menu' and augment the '_render' to produce everything including the menu 'bar'...
Ive captured the initial work into a branch "MenuStructs". This is phase 1... It tackles the Editor page and currently has replacements for the main menu bar's dropdowns (File / Edit / View / Tools) as well as both the nav and editor context menus. This is currently under a darklaunch with the test being: var useStructs = "true" === localStorage.getItem("useMenuStruct")
We've decided to capture the rest of this work on a more specific defect; bug 496678
Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see: https://dev.eclipse.org/mhonarc/lists/orion-dev/msg04002.html
