Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

E4/Menus

< E4
Revision as of 10:18, 14 October 2010 by Unnamed Poltroon (Talk) (New page: = Menu and Toolbar Rendering = We need to work through the many scenarios we have for menus and toolbars, and make sure that we cover off all of them (or decide against them) to support b...)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Menu and Toolbar Rendering

We need to work through the many scenarios we have for menus and toolbars, and make sure that we cover off all of them (or decide against them) to support both our e4 menus story and the compatibility menus/actions story.

e4 RCP Menus

In e4 Menus, they can be defined in 3 places in the model, and have contributions added to them.  MMenu supports 4 types, MHandledMenuItem, MDirectMenuItem, MMenuSeparator, and sub MMenus.

  1. An MMenu can be defined on an MWindow.  This will be rendered as an SWT Menu bar.
  2. An MMenu with tag "ViewMenu" can be added to an MPart.  This is rendered as an SWT Menu and needs to be shown when the view dropdown menu is provided.  We also tag it with ContributionsAnalyzer.MC_MENU when in a CompatibilityView
  3. an MPopupMenu can be added to an MPart.  This is rendered as an SWT Menu.  The EMenuService allows it to be associated with a Control

We then support MMenuContributions.  They were processed and added to the model on SWT.Show events, and then removed in an asyncExec(*) after the SWT.Hide.

We also support MRenderedMenu where we stick a MenuManager into the model as a transient object.


Back to the top