Skip to main content
Jump to: navigation, search

Menu Contributions

Revision as of 09:26, 24 October 2006 by Pwebster.ca.ibm.com (Talk | contribs) (Menus API)

Placement examples that try to describe the old to new way. Please contribute comments and suggestions in the discussion area or on Bug 154130 -KeyBindings- Finish re-work of commands and key bindings.


Add ProblemView menus

Add the Problems view menus. The problems view has one toolbar action and in the view menu, 3 actions and 2 dynamic submenus. It also has a dynamic menu and another bunch of actions in its context menu.

Commands

First define commands that are specific to the view. Since these are view commands, we can specify a default handler ... we're unlikely to replace it.

 <extension point="org.eclipse.ui.commands">
   <category id="org.eclipse.ui.views.problems"
             name="%ProblemView.category.name">
   </category>
   <command categoryId="org.eclipse.ui.views.problems"
            defaultHandler="org.eclipse.ui.views.markers.internal.TableSortHandler"
            description="%ProblemView.Sorting.description"
            id="org.eclipse.ui.views.problems.sorting"
            name="%ProblemView.Sorting.name">
   </command>
  <-- the view preference command would probably be defined once
      with the other preference contributions -->
  <command categoryId="org.eclipse.ui.views.problems"
           defaultHandler="org.eclipse.ui.preferences.ViewPreferencesHandler"
           description="%ViewPreferences.description"
           id="org.eclipse.ui.preferences.viewPreferences"
           name="%ViewPreferences.name">
     <commandParameter id="markerEnablementName"
                       name="%ViewPreferences.markerEnablementName.name"
                       optional="false" />
     <commandParameter id="markerLimitName"
                       name="ViewPreferences.markerLimitName.name"
                       optional="false" />
   </command>
   <command categoryId="org.eclipse.ui.views.problems"
            defaultHandler="org.eclipse.ui.views.markers.internal.FiltersHandler"
            description="%ProblemView.ConfigureFilters.description"
            id="org.eclipse.ui.views.problems.configureFilters"
            name="%ProblemView.ConfigureFilters.name">
   </command>
   <command categoryId="org.eclipse.ui.views.problems"
            defaultHandler="org.eclipse.ui.views.markers.internal.OpenMarkerHandler"
            description="%ProblemView.GoTo.description"
            id="org.eclipse.ui.views.problems.goTo"
            name="%ProblemView.GoTo.name" />
 </extension>

Handlers

We can also use a number of global commands, like copy, paste, delete, quick fix, and properties. For these, we just need to define our handlers. We need to add them with <activeWhen/> clauses to restrict them to being active when the view is active.

 <extension point="org.eclipse.ui.handlers">
   <handler commandId="org.eclipse.ui.edit.copy"
            class="org.eclipse.ui.views.markers.internal.CopyMarkerHandler">
     <enabledWhen>
       <not>
         <count value="0" />
       </not>
     </enabledWhen>
     <activeWhen>
       <with variable="activePartId">
         <equals value="org.eclipse.ui.views.ProblemView" />
       </with>
     </activeWhen>
   </handler>
   <handler commandId="org.eclipse.ui.edit.paste"
            class="org.eclipse.ui.views.markers.internal.PasteMarkerHandler">
     <enabledWhen>
       <not>
         <count value="0" />
       </not>
     </enabledWhen>
     <activeWhen>
       <with variable="activePartId">
         <equals value="org.eclipse.ui.views.ProblemView" />
       </with>
     </activeWhen>
   </handler>
   <handler commandId="org.eclipse.ui.edit.delete"
            class="org.eclipse.ui.views.markers.internal.RemoveMarkerHandler">
     <enabledWhen>
       <not>
         <count value="0" />
       </not>
     </enabledWhen>
     <activeWhen>
       <with variable="activePartId">
         <equals value="org.eclipse.ui.views.ProblemView" />
       </with>
     </activeWhen>
   </handler>
   <handler commandId="org.eclipse.ui.edit.selectAll"
            class="org.eclipse.ui.views.markers.internal.SelectAllMarkersHandler">
     <enabledWhen>
       <not>
         <count value="0" />
       </not>
     </enabledWhen>
     <activeWhen>
       <with variable="activePartId">
         <equals value="org.eclipse.ui.views.ProblemView" />
       </with>
     </activeWhen>
   </handler>
   <handler commandId="org.eclipse.jdt.ui.edit.text.java.correction.assist.proposals"
            class="org.eclipse.ui.views.markers.internal.ResolveMarkerHandler">
     <enabledWhen>
       <not>
         <count value="0" />
       </not>
     </enabledWhen>
     <activeWhen>
       <with variable="activePartId">
         <equals value="org.eclipse.ui.views.ProblemView" />
       </with>
     </activeWhen>
   </handler>
   <handler commandId="org.eclipse.ui.file.properties"
            class="org.eclipse.ui.views.markers.internal.ProblemPropertiesHandler">
     <enabledWhen>
       <not>
         <count value="0" />
       </not>
     </enabledWhen>
     <activeWhen>
       <with variable="activePartId">
         <equals value="org.eclipse.ui.views.ProblemView" />
       </with>
     </activeWhen>
   </handler>
 </extension>


Or we can programmatically activate them through the IHandlerService which we would retrieve from the ProblemView site.

IHandlerService handlerServ = (IHandlerService)getSite().getService(IHandlerService.class);
copy = new CopyMarkerHandler();
handlerServ.activateHandler("org.eclipse.ui.edit.copy", copy);

Using the ProblemView site to access the IHandlerService handles the <activeWhen/> clause for us, and our programmatic handler would manage its own enablement state.

Expression Sidebar

You can see that the <activeWhen/>, <enabledWhen/>, and probably the <visibleWhen/> are likely to be replicated over and over again. A possible option is some kind of expression template markup ... either in its own extension or supported by our UI extensions that can use core expressions.

Here's an example of using expression templates in its own extension point.

 <extension point="org.eclipse.core.expression.templates">
   <expression id="isPartActive">
     <parameter id="partId" />
     <with variable="activePartId">
       <equals value="$partId" />
     </with>
   </expression>
   <expression id="isActionSetActive">
     <parameter id="actionSetId" />
     <with variable="activeContexts">
       <iterator operator="or">
         <equals value="$actionSetId" />
       </iterator>
     </with>
   </expression>
   <expression id="isContextActive">
     <parameter id="contextId" />
     <with variable="activeContexts">
       <iterator operator="or">
         <equals value="$contextId" />
       </iterator>
     </with>
   </expression>
   <expression id="isSelectionAvailable">
     <not>
       <count value="0" />
     </not>
   </expression>
 </extension>


This could be used to simplify the handler definitions:

 <extension point="org.eclipse.ui.handlers">
   <handler commandId="org.eclipse.ui.edit.copy"
            class="org.eclipse.ui.views.markers.internal.CopyMarkerHandler">
     <enabledWhen>
       <evaluate ref="isSelectionAvailable" />
     </enabledWhen>
     <activeWhen>
       <evaluate ref="isPartActive">
         <parameter id="partId" value="org.eclipse.ui.views.ProblemView" />
       </evaluate>
     </activeWhen>
   </handler>
 </extension>


If we allow recursive template definitions, that would allow you to specify the concrete expression once and then reference it throughout your view.

 <extension point="org.eclipse.core.expression.templates">
   <expression id="isProblemViewActive">
     <evaluate ref="isPartActive">
       <parameter id="partId" value="org.eclipse.ui.views.ProblemView" />
     </evaluate>
   </expression>
 </extension>
 <extension point="org.eclipse.ui.handlers">
   <handler commandId="org.eclipse.ui.edit.copy"
            class="org.eclipse.ui.views.markers.internal.CopyMarkerHandler">
     <enabledWhen>
       <evaluate ref="isSelectionAvailable" />
     </enabledWhen>
     <activeWhen>
       <evaluate ref="isProblemViewActive" />
     </activeWhen>
   </handler>
 </extension>


This reduces the handler definition even more.

Menus

Then we would define the ProblemView menu structures. We are using 3 roots: the view menu, the view toolbar, and the view context menu. This is an example of an "in-place" menu definition. The XML hierarchy mirrors the menu hierarchy.


 <extension point="org.eclipse.ui.menus">
   <menuCollection location="menu://org.eclipse.ui.views.ProblemView">
     <item commandId="org.eclipse.ui.views.problems.sorting"
           mnemonic="%ProblemView.Sorting.mnemonic"
           tooltip="%ProblemView.Sorting.tooltip" />
     <menu id="org.eclipse.ui.views.problems.groupBy.menu"
           label="%ProblemView.GroupBy.label"
           mnemonic="%ProblemView.GroupBy.mnemonic">
       <dynamic class="org.eclipse.ui.views.markers.internal.GroupByMenu" />
     </menu>
     <separator id="group.filter" visible="true" />
     <menu id="org.eclipse.ui.views.problems.filters.menu"
           label="%ProblemView.Filters.label"
           mnemonic="%ProblemView.Filters.mnemonic">
       <dynamic class="org.eclipse.ui.views.markers.internal.FilterMenu" />
     </menu>
     <item commandId="org.eclipse.ui.views.problems.configureFilters"
           mnemonic="%ProblemView.ConfigureFilters.mnemonic"
           icon="$nl$/elcl16/filter_ps.gif"
           tooltip="%ProblemView.ConfigureFilters.tooltip" />
     <item commandId="org.eclipse.ui.preferences.viewPreferences"
           mnemonic="%ViewPreferences.mnemonic">
       <parameter id="markerEnablementName" value="LIMIT_PROBLEMS" />
       <parameter id="markerLimitName" value="PROBLEMS_LIMIT" />
     </item>
   </menuCollection>
   <menuCollection location="toolbar://org.eclipse.ui.views.ProblemView">
     <item commandId="org.eclipse.ui.views.problems.configureFilters"
           icon="$nl$/elcl16/filter_ps.gif"
           tooltip="%ProblemView.ConfigureFilters.tooltip" />
   </menuCollection>
   <menuCollection location="popup://org.eclipse.ui.views.ProblemView">
     <item commandId="org.eclipse.ui.views.problems.goTo"
           mnemonic="%ProblemView.GoTo.mnemonic"
           icon="$nl$/elcl16/gotoobj_tsk.gif"
           disabledIcon="$nl$/dlcl16/gotoobj_tsk.gif"
           tooltip="%ProblemView.GoTo.tooltip" />
     <separator id="group.showIn" visible="true" />
     <menu id="org.eclipse.ui.views.problems.showIn.menu"
           label="%ProblemView.ShowIn.label"
           mnemonic="%ProblemView.ShowIn.mnemonic">
       <dynamic class="org.eclipse.ui.actions.ShowInContributions" />
     </menu>
     <separator id="group.edit" visible="true" />
     <item commandId="org.eclipse.ui.edit.copy"
           mnemonic="%ProblemView.copy.mnemonic"
           icon="$nl$/icons/full/etool16/copy_edit.gif"
           disabledIcon="$nl$/icons/full/dtool16/copy_edit.gif" />
     <item commandId="org.eclipse.ui.edit.paste"
           mnemonic="%ProblemView.paste.mnemonic"
           icon="$nl$/icons/full/etool16/paste_edit.gif"
           disabledIcon="$nl$/icons/full/dtool16/paste_edit.gif" />
     <item commandId="org.eclipse.ui.edit.delete"
           mnemonic="%ProblemView.delete.mnemonic"
           icon="$nl$/icons/full/etool16/delete_edit.gif"
           disabledIcon="$nl$/icons/full/dtool16/delete_edit.gif">
       <visibleWhen>
         <not>
           <with variable="activePartId">
             <equals value="org.eclipse.ui.views.ProblemView" />
           </with>
         </not>
       </visibleWhen>
     </item>
     <item commandId="org.eclipse.ui.edit.selectAll"
           mnemonic="%ProblemView.selectAll.mnemonic" />
     <separator id="group.resolve" visible="true" />
     <item commandId="org.eclipse.jdt.ui.edit.text.java.correction.assist.proposals"
           mnemonic="%ProblemView.Resolve.mnemonic"
           icon="$nl$/icons/full/elcl16/smartmode_co.gif"
           disabledIcon="$nl$/icons/full/dlcl16/smartmode_co.gif" />
     <separator id="additions" visible="true" />
     <separator id="group.properties" visible="true" />
     <item commandId="org.eclipse.ui.file.properties"
           mnemonic="%ProblemView.Properties.mnemonic" />
   </menuCollection>
 </extension>


Some constraints on the system:

  1. Identifiers (id) for <menu/> and <item/> elements must be globally unique if they are specified.
  2. You can only reference a <menu/> or <item/> that has an id.
  3. If you are just placing your commands, you can leave them with only a command id. You don't have to specify an item id.
  4. <separator/> ids only have to be unique within that menu level.
  5. You can provide an <item/> label attribute. If none is provided, it will take the command name.
  6. In this design the item contains most of the same rendering information that <action/> did.
  7. <menu/> and <item/> can have <visibleWhen/> clauses. If a menu's <visibleWhen/> evaluates to false, we will never ask the items contained in that menu.
  8. All of the display-able attributes are translatable


Menu - JSR198

There is a JSR describing how IDEs can contribute menus. Below is a sample for 2 items:

  • org.eclipse.ui.views.problems.sorting.item from menu://org.eclipse.ui.views.ProblemView
  • org.eclipse.ui.views.problems.resolveMarker.item from popup://org.eclipse.ui.views.ProblemView
 <menu-hook>
   <actions>
     <action id="org.eclipse.ui.views.problems.sorting.item">
       <label>Sorting...</label>
       <mnemonic>S</mnemonic>
       <tooltip>Change the Sort order</tooltip>
       <invoke-class>org.eclipse.ui.views.problems.sorting</invoke-class>
     </action>
     <action id="org.eclipse.ui.views.problems.resolveMarker.item">
       <label>Quick Fix</label>
       <mnemonic>Q</mnemonic>
       <iconpath>$nl$/icons/full/elcl16/smartmode_co.gif</iconpath>
       <invoke-class>org.eclipse.jdt.ui.edit.text.java.correction.assist.proposals</invoke-class>
       <update-class>org.eclipse.jdt.ui.edit.text.java.correction.assist.proposals</update-class>
     </action>
   </actions>
   <menus>
     <menubar id="org.eclipse.ui.views.ProblemView">
       <menu id="org.eclipse.ui.views.ProblemView">
         <section id="problem.view.section">
           <item action-ref="org.eclipse.ui.views.problems.sorting.item" />
           <menu id="org.eclipse.ui.views.problems.groupBy.menu">
             <label>Group By</label>
             <mnemonic>G</mnemonic>
           </menu>
         </section>
       </menu>
     </menubar>
     <popup id="org.eclipse.ui.views.ProblemView">
       <section id="group.resolve">
         <item action-ref="org.eclipse.ui.views.problems.resolveMarker.item" />
       </section>
     </popup>
   </menus>
 </menu-hook>

Some thoughts:

  • the actions can only specify one icon
  • the actions can't *quite* link to our commands
  • the menus can't specify dynamic submenus

Menu - XUL

With Mozilla everywhere, there is the probability eclipse will include xulrunner. Menu definitions that are consistent with XUL look like:

 <keyset>
   <key id="paste-key" modifiers="accel" key="V" />
 </keyset>
 <menubar id="org.eclipse.ui.views.ProblemView">
   <menupopup id="org.eclipse.ui.views.ProblemView">
     <menuitem id="org.eclipse.ui.views.problems.sorting.item"
               accesskey="S"
               key="paste-key"
               label="Sorting..."
               oncommand="invokeCommand('org.eclipse.ui.views.problems.sorting')" />
     <menu id="org.eclipse.ui.views.problems.groupBy.menu"
           label="Group By"
           accesskey="G">
       <menupopup id="groupby.popup">
       </menupopup>
     </menu>
   </menupopup>
 </menubar>


XUL supports everything as a flavour of a DOM, and javascripting can drive your buttons to perform commands. I suspect the scripting would allow you to dynamically update menus (dynamic menus) on popup, depending on what events the DOM would report to you.

Menus API

We can contribute menu definitions through the IMenuService API.

The above example can be done for the view menus:

   public void createProblemsViewMenu() {
       IMenuService menuServ = (IMenuService) PlatformUI.getWorkbench()
               .getActiveWorkbenchWindow().getService(IMenuService.class);

       Collection menuCollection = new ArrayList();
       // add a menu item
       ItemDesc sort = new ItemDesc("org.eclipse.ui.views.problems.sorting");
       sort.setMnemonic("S");
       sort.setTooltip("Change the Sort order");
       menuCollection.add(sort);

       // add a dynamic submenu
       MenuDesc groupByMenu = new MenuDesc(
               "org.eclipse.ui.views.problems.groupBy.menu", "Group By");
       groupByMenu.setMnemonic("B");
       groupByMenu.setDynamicMenu(new GroupByDynamicMenu());
       menuCollection.add(groupByMenu);

       menuCollection.add(new SeparatorDesc("group.filter", true));

       // add a sub menu
       MenuDesc filtersMenu = new MenuDesc(
               "org.eclipse.ui.views.problems.filters.menu", "Filters");
       filtersMenu.setMnemonic("F");
       filtersMenu.setDynamicMenu(new FiltersDynamicMenu());
       menuCollection.add(filtersMenu);

       // add items to the sub menu
       ItemDesc fitem = new ItemDesc(
               "org.eclipse.ui.views.problems.configureFilters");
       fitem.setTooltip("Configure the filters to be applied to this view");
       fitem.setMnemonic("C");
       fitem.setImage(getSharedImage("elcl16/filter_ps.gif"));
       menuCollection.add(fitem);

       fitem = new ItemDesc(getProblemPreferencesCommand());
       fitem.setTooltip("Open the preferences");
       fitem.setMnemonic("P");
       menuCollection.add(fitem);

       // place the contribution back into the menu service.
       IMenuContribution viewMenu = menuServ.contribute(
               "menu://org.eclipse.ui.views.ProblemView", menuCollection);

       // and possibly much later
       menuServ.remove(viewMenu);
   }


You add your menus and menu items to an ordered collection, then contribute them to a location (like menu://org.eclipse.ui.views.ProblemView) and potentially a location modifier (after some id).

You can add Menus, Separators, Items, and Widgets to your collection. Once you've update your collection, contribute it back to the menu service.

If you need to reference an Item at some time you will need to create it with an id, which must be unique. For reuse you can create Items without ids, but then you will be unable to reference them.

Menus cannot be re-used in this manner, and so they have an intrinsic id value. Separators are unique within one menu level, so they also contain their id value.

Add Toggle Mark Occurrences to main toolbar

We can provide the Toggle Mark Occurrences toolbar button. It's normally contributed through an actionSet as a retargettable action, and the Java and Class File editors *EditorActionBarContributors provide the implementation ToggleMarkOccurrencesAction through IActionBars#setGlobalActionHandler(*).

Commands

First define the toggle mark occurrences command. Pretty straight forward, although it needs a "STYLE" state since it can be toggled. To allow handlers to update the label for the menu/toolbar items, we also add the "NAME" state.

 <extension point="org.eclipse.ui.commands">
   <command categoryId="org.eclipse.jdt.ui.category.source"
            description="%jdt.ui.ToggleMarkOccurrences.description"
            id="org.eclipse.jdt.ui.edit.text.java.toggleMarkOccurrences"
            name="%jdt.ui.ToggleMarkOccurrences.name">
     <state id="NAME" class="org.eclipse.jface.menus.TextState" />
     <state id="STYLE" class="org.eclipse.jface.commands.ToggleState:true" />
   </command>
 </extension>

Handlers

This command doesn't have a default handler, as it only applies to specific editors that are provided. So we would provide the handler for the java editor.

 <extension point="org.eclipse.ui.handlers">
   <handler commandId="org.eclipse.jdt.ui.edit.text.java.toggleMarkOccurrences"
            class="org.eclipse.jdt.internal.ui.javaeditor.ToggleMarkOccurrencesHandler">
     <activeWhen>
       <with variable="activePartId">
         <or>
           <equals value="org.eclipse.jdt.ui.CompilationUnitEditor" />
           <equals value="org.eclipse.jdt.ui.ClassFileEditor" />
         </or>
       </with>
     </activeWhen>
   </handler>
 </extension>

We're active for both the Java editor and the Class File editor. There is also the option to programmatically install the handler.

AndExpression expr = new AndExperssion();
expr.add(new ActivePartIdExpression("org.eclipse.jdt.ui.CompilationUnitEditor"));
expr.add(new ActivePartIdExpression("org.eclipse.jdt.ui.ClassFileEditor"));
IHandlerService handlerServ = (IHandlerService)getSite().getWorkbenchWindow().getService(IHandlerService.class);
toggleOccurrencesHandler = new ToggleMarkOccurrencesHandler();
handlerServ.activateHandler("org.eclipse.jdt.ui.edit.text.java.toggleMarkOccurrences", toggleOccurrencesHandler, expr);

Since the same handler is valid for both editors, we install it with a specific expression and don't tie the activation to the part site. But as written, the toggleOccurrencesHandler will exist as long as the workbench window exists.

Menus

 <extension point="org.eclipse.ui.menus">
   <menuCollection location="toolbar:org.eclipse.ui.edit.text.actionSet.presentation?after=Presentation">
     <item commandId="org.eclipse.jdt.ui.edit.text.java.toggleMarkOccurrences"
           tooltip="%jdt.ui.ToggleMarkOccurrences.tooltip"
           icon="$nl$/icons/full/etool16/mark_occurrences.gif"
           disabledIcon="$nl$/icons/full/dtool16/mark_occurrences.gif"
           helpContextId="toggle_mark_occurrences_action_context">
       <visibleWhen>
         <with variable="activeContexts">
           <iterator operator="or">
             <equals value="org.eclipse.jdt.ui.text.java.actionSet.presentation" />
           </iterator>
         </with>
       </visibleWhen>
     </item>
   </menuCollection>
 </extension>


Here we are adding ourselves to the workbench text presentation toolbar, which has already been contributed. This item is also tied to an actionSet.

Menus API

The above XML can be done using the menus API:

   public void createToggleMarkOccurrences() {
       IMenuService menuServ = (IMenuService) PlatformUI.getWorkbench()
               .getActiveWorkbenchWindow().getService(IMenuService.class);

       ItemDesc toggleItem = new ItemDesc(
               "org.eclipse.jdt.ui.edit.text.java.toggleMarkOccurrences");
       toggleItem
               .setImage(getSharedImage("icons/full/etool16/mark_occurrences.gif"));
       toggleItem
               .setDisabledImage(getSharedImage("icons/full/dtool16/mark_occurrences.gif"));
       toggleItem.setHelpContextId("toggle_mark_occurrences_action_context");
       toggleItem.setVisibleWhen(new ActiveContextExpression(
               "org.eclipse.jdt.ui.text.java.actionSet.presentation"));

       menuServ
               .contribute(
                       "toolbar:org.eclipse.ui.edit.text.actionSet.presentation?after=Presentation",
                       Collections.singletonList(toggleItem));
   }

This asks for a menu root in the org.eclipse.ui.edit.text.actionSet.presentation toolbar after the Presentation id.

It's contributed with a visibleWhen clause ActiveContextExpression(JAVA_PRESENTATION_ACTIONSET_ID), so it will be visible when the actionSet is active.

Possible Java Search Menu Example

The java search menu items are added through a Java Search action set. They have code that enables/disables the action set depending on the active editor.

ActionSet context

For something to go in an actionSet, then we would define the actionSet context.

 <extension point="org.eclipse.ui.contexts">
   <context description="%JavaSearchActionSet.description"
            id="org.eclipse.jdt.ui.SearchActionSet"
            name="%JavaSearchActionSet.label"
            parentId="org.eclipse.ui.contexts.actionSet">
   </context>
 </extension>

Commands

Also, a number of the items were retargetable actions that allow label updates. The current pattern would mean adding the NAME state to a lot of the commands.

 <extension point="org.eclipse.ui.commands">
   <command name="%ActionDefinition.readAccessInworkspace.name"
            description="%ActionDefinition.readAccessInWorkspace.description"
            categoryId="org.eclipse.search.ui.category.search"
            id="org.eclipse.jdt.ui.edit.text.java.search.read.access.in.workspace">
     <state id="NAME" class="org.eclipse.jface.menus.TextState" />
   </command>
   <command name="%ActionDefinition.readAccessInProject.name"
            description="%ActionDefinition.readAccessInProject.description"
            categoryId="org.eclipse.search.ui.category.search"
            id="org.eclipse.jdt.ui.edit.text.java.search.read.access.in.project">
     <state id="NAME" class="org.eclipse.jface.menus.TextState" />
   </command>
   <command name="%ActionDefinition.readAccessInHierarchy.name"
            description="%ActionDefinition.readAccessInHierarchy.description"
            categoryId="org.eclipse.search.ui.category.search"
            id="org.eclipse.jdt.ui.edit.text.java.search.read.access.in.hierarchy">
     <state id="NAME" class="org.eclipse.jface.menus.TextState" />
   </command>
   <command name="%ActionDefinition.readAccessInWorkingSet.name"
            description="%ActionDefinition.readAccessInWorkingSet.description"
            categoryId="org.eclipse.search.ui.category.search"
            id="org.eclipse.jdt.ui.edit.text.java.search.read.access.in.working.set">
     <state id="NAME" class="org.eclipse.jface.menus.TextState" />
   </command>
   <command name="%ActionDefinition.writeAccessInWorkspace.name"
            description="%ActionDefinition.writeAccessInWorkspace.description"
            categoryId="org.eclipse.search.ui.category.search"
            id="org.eclipse.jdt.ui.edit.text.java.search.write.access.in.workspace">
     <state id="NAME" class="org.eclipse.jface.menus.TextState" />
   </command>
   <command name="%ActionDefinition.writeAccessInProject.name"
            description="%ActionDefinition.writeAccessInProject.description"
            categoryId="org.eclipse.search.ui.category.search"
            id="org.eclipse.jdt.ui.edit.text.java.search.write.access.in.project">
     <state id="NAME" class="org.eclipse.jface.menus.TextState" />
   </command>
   <command name="%ActionDefinition.writeAccessInHierarchy.name"
            description="%ActionDefinition.writeAccessInHierarchy.description"
            categoryId="org.eclipse.search.ui.category.search"
            id="org.eclipse.jdt.ui.edit.text.java.search.write.access.in.hierarchy">
     <state id="NAME" class="org.eclipse.jface.menus.TextState" />
   </command>
   <command name="%ActionDefinition.writeAccessInWorkingSet.name"
            description="%ActionDefinition.writeAccessInWorkingSet.description"
            categoryId="org.eclipse.search.ui.category.search"
            id="org.eclipse.jdt.ui.edit.text.java.search.write.access.in.working.set">
     <state id="NAME" class="org.eclipse.jface.menus.TextState" />
   </command>
 </extension>

Menus

We'll assume that the Search menu is globally defined elsewhere by the org.eclipse.search plugin.

 <extension point="org.eclipse.ui.menus">
   <menuCollection location="menu://org.eclipse.ui.main.menu?after=navigate">
     <menu label="%searchMenu.label"
           mnemonic="%searchMenu.mnemonic"
           id="org.eclipse.search.menu">
       <separator name="internalDialogGroup" visible="false" />
       <separator name="dialogGroup" visible="false" />
       <separator name="fileSearchContextMenuActionsGroup" visible="true" />
       <separator name="contextMenuActionsGroup" visible="true" />
       <separator name="occurencesActionsGroup" visible="true" />
       <separator name="extraSearchGroup" visible="true" />
     </menu>
   </menuCollection>
 </extension>

Then the JDT plugin would contribute the menu items to search, where the menuRoot location specifies the starting point for adding the menus. For groups of actions like the Write Access or Read Access shown here, they can just be specified in order. The <visibleWhen/> clauses must be specified on the items contributed if they want to belong to the actionSet, but if the contribute items are contain in a contributed menu, it can just be specified on the <menu/> element. We also use the relative URI notation, since the menu id org.eclipse.search.menu must be unique.

 <extension point="org.eclipse.ui.menus">
   <menuCollection location="menu:org.eclipse.search.menu?after=dialogGroup">
     <item commandId="org.eclipse.jdt.internal.ui.search.openJavaSearchPage"
           label="%openJavaSearchPageAction.label"
           mnemonic="%openJavaSearchPageAction.mnemonic"
           icon="$nl$/icons/full/obj16/jsearch_obj.gif"
           helpContextId="java_search_action_context">
       <visibleWhen>
         <with variable="activeContexts">
           <iterator operator="or">
             <equals value="org.eclipse.jdt.ui.SearchActionSet" />
           </iterator>
         </with>
       </visibleWhen>
     </item>
   </menuCollection>
   <menuCollection location="menu:org.eclipse.search.menu?after=contextMenuActionsGroup">
     <menu id="readAccessSubMenu"
           label="%readAccessSubMenu.label"
           mnemonic="%readAccessSubMenu.mnemonic">
       <separator name="group1" visible="false" />
       <item commandId="org.eclipse.jdt.ui.edit.text.java.search.read.access.in.workspace"
             label="%InWorkspace.label"
             mnemonic="%InWorkspace.mnemonic">
       </item>
       <item commandId="org.eclipse.jdt.ui.edit.text.java.search.read.access.in.project"
             label="%InProject.label"
             mnemonic="%InProject.mnemonic">
       </item>
       <item commandId="org.eclipse.jdt.ui.edit.text.java.search.read.access.in.hierarchy"
             label="%InHierarchy.label"
             mnemonic="%InHierarchy.mnemonic">
       </item>
       <item commandId="org.eclipse.jdt.ui.edit.text.java.search.read.access.in.working.set"
             label="%InWorkingSet.label"
             mnemonic="%InWorkingSet.mnemonic">
       </item>
       <visibleWhen>
         <with variable="activeContexts">
           <iterator operator="or">
             <equals value="org.eclipse.jdt.ui.SearchActionSet" />
           </iterator>
         </with>
       </visibleWhen>
     </menu>
     <menu id="writeAccessSubMenu"
           label="%writeAccessSubMenu.label"
           mnemonic="%writeAccessSubMenu.mnemonic">
       <separator name="group1" visible="false" />
       <item commandId="org.eclipse.jdt.ui.edit.text.java.search.write.access.in.workspace"
             label="%InWorkspace.label"
             mnemonic="%InWorkspace.mnemonic">
       </item>
       <item commandId="org.eclipse.jdt.ui.edit.text.java.search.write.access.in.project"
             label="%InProject.label"
             mnemonic="%InProject.mnemonic">
       </item>
       <item commandId="org.eclipse.jdt.ui.edit.text.java.search.write.access.in.hierarchy"
             label="%InHierarchy.label"
             mnemonic="%InHierarchy.mnemonic">
       </item>
       <item commandId="org.eclipse.jdt.ui.edit.text.java.search.write.access.in.working.set"
             label="%InWorkingSet.label"
             mnemonic="%InWorkingSet.mnemonic">
       </item>
       <visibleWhen>
         <with variable="activeContexts">
           <iterator operator="or">
             <equals value="org.eclipse.jdt.ui.SearchActionSet" />
           </iterator>
         </with>
       </visibleWhen>
     </menu>
   </menuCollection>
   <menuCollection location="menu:org.eclipse.search.menu?after=occurencesActionsGroup">
     <item commandId="org.eclipse.jdt.ui.edit.text.java.search.occurrences.in.file.quickMenu"
           label="%occurrencesSubMenu.label">
       <dynamic class="org.eclipse.jdt.internal.ui.actions.OccurrencesSearchMenuAction" />
       <visibleWhen>
         <with variable="activeContexts">
           <iterator operator="or">
             <equals value="org.eclipse.jdt.ui.SearchActionSet" />
           </iterator>
         </with>
       </visibleWhen>
     </item>
   </menuCollection>
 </extension>

Currently, the java search menus are in the Java Search actionSet, that is dynamically enabled/disabled. This could also be done by specifying a visibleWhen like:

<visibleWhen>
  <with variable="activeEditorId">
    <or>
      <equals value="org.eclipse.jdt.ui.CompilationUnitEditor" />
      <equals value="org.eclipse.jdt.ui.ClassFileEditor" />
    </or>
  </with>
</visibleWhen>

This would make the visible if either the Java or Class File editor was the active editor, and they would disappear otherwise.

Menus API

The API can be used to contribute to the main menu bar:

   public void addSearchMenu() {
       IMenuService menuServ = (IMenuService) PlatformUI.getWorkbench()
               .getActiveWorkbenchWindow().getService(IMenuService.class);

       MenuDesc searchMenu = new MenuDesc("org.eclipse.search.menu", "Search");
       searchMenu.setMnemonic("a");

       searchMenu.add(new SeparatorDesc("internalDialogGroup", false));
       searchMenu.add(new SeparatorDesc("dialogGroup", false));
       searchMenu.add(new SeparatorDesc("fileSearchContextMenuActionsGroup",
               true));
       searchMenu.add(new SeparatorDesc("contextMenuActionsGroup", true));
       searchMenu.add(new SeparatorDesc("occurencesActionsGroup", true));
       searchMenu.add(new SeparatorDesc("extraSearchGroup", true));

       menuServ.contribute("menu://org.eclipse.ui.main.menu?after=navigate",
               Collections.singletonList(searchMenu));
   }

It's just a menu inserted at the menu root location.


Then another plugin can contribute to the search menu:

   public void addToSearchMenu() {
       IMenuService menuServ = (IMenuService) PlatformUI.getWorkbench()
               .getActiveWorkbenchWindow().getService(IMenuService.class);

       ItemDesc searchItem = new ItemDesc(
               "org.eclipse.jdt.internal.ui.search.openJavaSearchPage");
       searchItem.setMnemonic("J");
       searchItem.setImage(getSharedImage("icons/full/obj16/jsearch_obj.gif"));
       searchItem.setHelpContextId("java_search_action_context");
       ActiveContextExpression activeSearchActionSet = new ActiveContextExpression(
               "org.eclipse.jdt.ui.SearchActionSet");
       searchItem.setVisibleWhen(activeSearchActionSet);

       menuServ.contribute("menu:org.eclipse.search.menu?after=dialogGroup",
               Collections.singletonList(searchItem));

       Collection menuCollection = new ArrayList();

       MenuDesc readMenu = new MenuDesc("readAccessSubMenu", "Read Access");
       readMenu.setMnemonic("R");
       readMenu.setVisibleWhen(activeSearchActionSet);
       menuCollection.add(readMenu);

       readMenu.add(new SeparatorDesc("group1", false));

       ItemDesc item = new ItemDesc(
               "org.eclipse.jdt.ui.edit.text.java.search.read.access.in.workspace");
       item.setMnemonic("W");
       readMenu.add(item);
       item = new ItemDesc(
               "org.eclipse.jdt.ui.edit.text.java.search.read.access.in.project");
       item.setMnemonic("P");
       readMenu.add(item);
       item = new ItemDesc(
               "org.eclipse.jdt.ui.edit.text.java.search.read.access.in.hierarchy");
       item.setMnemonic("H");
       readMenu.add(item);
       item = new ItemDesc(
               "org.eclipse.jdt.ui.edit.text.java.search.read.access.in.working.set");
       item.setMnemonic("S");
       readMenu.add(item);

       MenuDesc writeMenu = new MenuDesc("readAccessSubMenu", "Read Access");
       writeMenu.setMnemonic("R");
       writeMenu.setVisibleWhen(activeSearchActionSet);
       menuCollection.add(writeMenu);

       writeMenu.add(new SeparatorDesc("group1", false));

       item = new ItemDesc(
               "org.eclipse.jdt.ui.edit.text.java.search.write.access.in.workspace");
       item.setMnemonic("W");
       writeMenu.add(item);
       item = new ItemDesc(
               "org.eclipse.jdt.ui.edit.text.java.search.write.access.in.project");
       item.setMnemonic("P");
       writeMenu.add(item);
       item = new ItemDesc(
               "org.eclipse.jdt.ui.edit.text.java.search.write.access.in.hierarchy");
       item.setMnemonic("H");
       writeMenu.add(item);
       item = new ItemDesc(
               "org.eclipse.jdt.ui.edit.text.java.search.write.access.in.working.set");
       item.setMnemonic("S");
       writeMenu.add(item);

       menuServ.contribute(
               "menu:org.eclipse.search.menu?after=contextMenuActionsGroup",
               menuCollection);
   }

When done, contribute the built menu back to the menu service.

IFile object contribution

We also have to provide object contributions (which in the past were scoped by objectClass).

Menus

There will be a reserved popup ID, "org.eclipse.ui.menus.popup.any" that will allow contributions to any popup menu.

 <extension point="org.eclipse.ui.menus">
   <menuCollection location="popup://org.eclipse.ui.menus.popup.any?after=additions">
     <item commandId="org.eclipse.ui.examples.wiki.post"
           mnemonic="%WikiExample.post.mnemonic"
           icon="$nl$/icons/full/elcl16/post_wiki.gif">
       <visibleWhen>
         <with variable="selection">
           <adapt type="org.eclipse.core.resources.IFile" />
         </with>
       </visibleWhen>
     </item>
     <item commandId="org.eclipse.ui.examples.wiki.load"
           mnemonic="%WikiExample.load.mnemonic"
           icon="$nl$/icons/full/elcl16/load_wiki.gif">
       <visibleWhen>
         <adapt type="org.eclipse.core.resources.IFile" />
       </visibleWhen>
     </item>
   </menuCollection>
 </extension>


It's probably that the default variable for core expression evaluations would be selection, so you wouldn't need the <with/> clause like in the second item above. There would probably also be a short-hand to tie the visibility to an active handler. Maybe <visibleWhen handler="true"/>

Menus API

So programmatically it is similar to all other menu contributions.

   public void addIFileContribution() {
       IMenuService menuServ = (IMenuService) PlatformUI.getWorkbench()
               .getActiveWorkbenchWindow().getService(IMenuService.class);
       Expression ifileExpression = new AdaptSelectionExpression(
               "org.eclipse.core.resources.IFile");
       Collection menuCollection = new ArrayList();
       ItemDesc wikiItem = new ItemDesc("org.eclipse.ui.examples.wiki.post");
       wikiItem.setMnemonic("P");
       wikiItem.setImage(getSharedImage("icons/full/elcl16/post_wiki.gif"));
       wikiItem.setVisibleWhen(ifileExpression);
       menuCollection.add(wikiItem);
       wikiItem = new ItemDesc("org.eclipse.ui.examples.wiki.load");
       wikiItem.setMnemonic("L");
       wikiItem.setImage(getSharedImage("icons/full/elcl16/load_wiki.gif"));
       wikiItem.setVisibleWhen(ifileExpression);
       menuCollection.add(wikiItem);
       menuServ.contribute(
               "popup://org.eclipse.ui.menus.popup.any?after=additions",
               menuCollection);
   }


The location of org.eclipse.ui.menus.popup.any specifies any context menu, and the expression ties it to a specific objectClass. Using the new expression syntax you can make your conditions more complex.

You can set your visibleWhen expression on each item as you create it.

Product removes the Project menu

An RCP product wishes to remove the Project menu. It should be possible to override the visibility of menu contributions.

   public void addOverride() {
       // the RCP app would already have its product key
       Object productKey = null;

       IMenuService menuServ = (IMenuService) PlatformUI.getWorkbench()
               .getActiveWorkbenchWindow().getService(IMenuService.class);
       menuServ.addOverride(productKey, "menu:project", new OverrideAdapter() { //$NON-NLS-1$
                   public Boolean getVisible() {
                       return Boolean.FALSE;
                   }
               });
   }


The idea is to provide this ability at the product level. For example, an RCP app should be able to hide any menu items that it doesn't want but picked up through the inclusion of a plugin.

That implies that it might not be part of the general IMenuService interface. Or (taking a page from the IExtensionRegistry) it might use a token that's available from the WorkbenchWindowAdvisor so that products can use the interface, or even expose the ability to their users.

If it returns null the next level of visibility is evaluated. The null case is to keep it consistent with other overrides.

File->Exit

Current RCP using ActionBarAdvisor

The ApplicationActionBarAdvisor should add the exit menu. The QuitAction is already coded and the exit command is already defined.

// create the file menu
MenuManager menu = new MenuManager(IDEWorkbenchMessages.Workbench_file, IWorkbenchActionConstants.M_FILE);
// ...
quitAction = ActionFactory.QUIT.create(window);
register(quitAction);
ActionContributionItem quitItem = new ActionContributionItem(quitAction);
quitItem.setVisible(!"carbon".equals(SWT.getPlatform())); //$NON-NLS-1$
menu.add(quitItem);

Current RCP or Eclipse plugin using an actionSet

Using an actionSet, you can also place the action in the main menu.

<extension
      point="org.eclipse.ui.actionSets">
   <actionSet
         id="org.eclipse.ui.file.exitActions"
         label="Exit Actions"
         visible="true">
      <action
            class="org.eclipse.ui.internal.QuitAction"
            id="quit"
            definitionId="org.eclipse.ui.file.exit"
            label="E&amp;xit"
            menubarPath="file/fileEnd"
            tooltip="Exit Eclipse">
      </action>
   </actionSet>
</extension>

Proposed new menu support

With the new structure, you would have to turn the action into a handler.


<extension
      point="org.eclipse.ui.handlers">
   <handler commandId="org.eclipse.ui.file.exit"
         class="org.eclipse.ui.internal.QuitHandler"/>
</extension>

Then you can place it in the menu:

<extension
      point="org.eclipse.ui.menus">
   <item
         commandId="org.eclipse.ui.file.exit"
         mnemonic="x"
         id="org.eclipse.ui.file.exit.menu">
      <location type="menu">
         <menu id="file"/>
         <order after="fileEnd"/>
      </location>
   </item>
</extension>

You can globally place your exit menu in the file menu, or tie it to an actionSet using the <visibleWhen/> clause.

Edit->Copy

Some Copy Stuff.

Global toolbar->Save

save

Global toolbar->Open Type

open type


Search->Registry Search

Provide a basic action set. You have 2 actions, Registry Find and Registry Replace, and you want to add them to the "dialog" section of the Search menu.


Proposed new menu support

Assume you have 2 commands defined, com.example.registry.search.find (Registry Find) and com.example.registry.search.replace (Registry Replace), and you want to add them to the main Search menu at org.eclipse.search.menu/dialogGroup. Your commands already have their images defined in the org.eclipse.ui.commandImages extension point.

Define the action set:

<context
      description="The collection of registry search actions"
      id="com.example.registry.search.actionSet"
      name="Registry Search Action Set"
      parentId="org.eclipse.ui.contexts.actionSet">
</context>

And here is a possible view of the menus extension point:

<extension
      point="org.eclipse.ui.menus">
   <item
         commandId="com.example.registry.search.find"
         mnemonic="d"
         id="com.example.registry.search.find.menu">
      <location type="menu">
         <menu id="org.eclipse.search.menu"/>
         <order after="dialogGroup"/>
      </location>
      <visibleWhen>
         <with variable="activeContexts">
            <iterator operator="or">
               <equals value="com.example.registry.search.actionSet"/>
            </iterator>
         </with>
      </visibleWhen>
   </item>
   <item
         commandId="com.example.registry.search.replace"
         mnemonic="p"
         id="com.example.registry.search.replace.menu">
      <location type="menu">
         <menu id="org.eclipse.search.menu"/>
         <order after="com.example.registry.search.find.menu"/>
      </location>
      <visibleWhen>
         <with variable="activeContexts">
            <iterator operator="or">
               <equals value="com.example.registry.search.actionSet"/>
            </iterator>
         </with>
      </visibleWhen>
   </item>
</extension>

Hmmmm, so to programmatically do this, you would have to go through the IMenuService.


ICommandService commandServ = (ICommandService) getSite().getWindow().getService(ICommandService.class);
IMenuService menuServ = (IMenuService) getSite().getWindow().getService(IMenuService.class);
 
Command findCmd = commandServ.getCommand("com.example.registry.search.find");
SLocation findLocation = new SLocation(SBar.MENU, "org.eclipse.search.menu");
findLocation.setOrder(new SOrder(SOrder.AFTER, "dialogGroup"));

SItem findItem = menuServ.getItem(new SLocation(SBar.MENU, "org.eclipse.search.menu/com.example.registry.search.find.menu"));
findItem.define(findCmd, findLocation, "d");
menuServ.contribute(findItem, new ActionSetExpression("com.example.registry.search.actionSet"));

Command replaceCmd = commandServ.getCommand("com.example.registry.search.replace");
SLocation replaceLocation = new SLocation(SBar.MENU, "org.eclipse.search.menu");
replaceLocation.setOrder(new SOrder(SOrder.AFTER, "com.example.registry.search.find.menu"));

SItem replaceItem = menuServ.getItem(new SLocation(SBar.MENU, "org.eclipse.search.menu/com.example.registry.search.replace.menu"));
replaceItem.define(replaceCmd, replaceLocation, "p");
menuServ.contribute(replaceItem, new ActionSetExpression("com.example.registry.search.actionSet"));

Widget in the main toolbar

You can use the extension point to contribute a control to the toolbar. You use the <widget/> element instead of the <item/> element.

<extension
      point="org.eclipse.ui.menus">
   <widget
         class="com.example.registry.search.SearchBar"
         id="com.example.registry.search.find.searchbar">
      <location type="toolbar">
         <menu id="org.eclipse.search.toolbar"/>
      </location>
      <visibleWhen>
         <with variable="activeContexts">
            <iterator operator="or">
               <equals value="com.example.registry.search.actionSet"/>
            </iterator>
         </with>
      </visibleWhen>
   </widget>
</extension>

The widget class must implement org.eclipse.ui.menus.IWorkbenchWidget, and provide fill(Composite parent) for a toolbar.

I'm not sure how far to go with IWorkbenchWidget. We already use this interface for adding controls to the trim, and there are open bug requests about adding arbitrary controls to the toolbars.

Will menus take arbitrary controls?

Edit->Undo relabel action

Like the Undo action, sometimes menu items would want to allow their label to be updated. This is currently handled through the Command objects and the handlers. IMenuStateIds and INamedHandleStateIds define some states that we currently support.

This can be used to update the menu item label:

<extension
      point="org.eclipse.ui.commands">
   <command
         description="Targetted Undo Command"
         id="org.eclipse.ui.commands.targettedUndo"
         name="Undo">
      <state
            class="org.eclipse.jface.menus.TextState"
            id="NAME"/>
   </command>
</extension>

It's placed in the menus just like any other command:

<extension
      point="org.eclipse.ui.menus">
   <item
         commandId="org.eclipse.ui.commands.targettedUndo"
         mnemonic="u"
         id="org.eclipse.ui.commands.undo">
      <location type="menu">
         <menu id="edit"/>
         <order after="edit.ext"/>
      </location>
   </item>
</extension>

As a handler becomes active and implement IObjectWithState (for example, derives from AbstractHandlerWithState) it is notified about any states that the handler's command contains. The states can be updated at that time.

class FileDeleteUndoHandler extends AbstractHandlerWithState {
    public final void handleStateChange(final State state, final Object oldValue) {
        if (INamedHandleStateIds.NAME.equals(state.getId()) && oldValue==null) {
            state.setValue("Undo File Delete");
        }
    }
    public final Object execute(final ExecutionEvent event) {
        // undo a file delete using EFS ... very cool
        return null;
    }
}

Search->Registry Search editor action

This should basically be the same as Search->Registry Search with a different visible when clause.

      <visibleWhen>
         <with variable="activeEditorId">
            <equals value="com.example.registry.RegistryEditor"/>
         </with>
      </visibleWhen>

So programmatically, that just translates into a different visible when expression:

menuServ.contribute(editorFindItem, new ActiveEditorIdExpression("com.example.registry.RegistryEditor"));

The menu items must be uniquely identified by their id. Since they only have one location, they can only have one activation in the service at a time.

Search->Registry Search programmatic editor action

Programmatically we have to take the editor action handlers into account.

One of the advantages of EditorActionBars is the lifecycle of the actions that are added. They're created when the first editor of that type is loaded and exist until the last editor of that type is closed.

Our service hierarchy has 2 levels, IWorkbenchWindow and IPartSite. Handlers registered with IWorkbenchWindow are active as long as the window is active, and are disposed when the window is disposed. Handlers registered with IPartSite are active and available as long as that specific part is active and available. When the part is closed, the handlers are disposed.

Two possibilities are:

1. Provide a service locator for the in-between case. Tied to a part type. The service locator expression makes the activation correct and the service locator disposes of them correctly. Basically, we would make IActionBars returned from each IPartSite a service locator as well.

2. Move these actions up to the IWorkbenchWindow level. With the correct expression the handler activation would be correct. But once created they would live as long as the workbench.

Add View submenu and item

View actions have to specify their menus as they are self contained.

<command id="z.ex.editor.commands.SampleViewAction"
    name="Sample View Action"
    description="Sample View Action command"/>
<extension
      point="org.eclipse.ui.commandImages">
   <image commandId="z.ex.editor.commands.SampleViewAction"
         icon="icons/sample.gif"/>
</extension>

Placing the action (which is specifically a menu or button linked to a command) can be accomplished with the org.eclipse.ui.menus extension point.

<extension
      point="org.eclipse.ui.menus">
   <menu
         id="z.ex.view.SampleViewMenu"
         mnemonic="M"
         label="Sample Menu">
      <location type="viewMenu">
         <part partId="z.ex.view.keybindings.views.SampleView"/>
      </location>
   </menu>
   <group
         groupId="z.ex.view.SampleViewGroup"
         separatorsVisible="false">
      <location type="viewMenu">
         <part partId="z.ex.view.keybindings.views.SampleView">
            <menu id="z.ex.view.SampleViewMenu"/>
         </part>
      </location>
   </group>
   <item
         commandId="z.ex.editor.commands.SampleViewAction"
         mnemonic="V"
         id="z.ex.view.SampleViewAction">
      <location type="viewMenu">
         <part partId="z.ex.view.keybindings.views.SampleView">
            <menu id="z.ex.view.SampleViewMenu"/>
         </part>
         <order after="z.ex.view.SampleViewGroup"/>
      </location>
   </item>
</extension>


Hmmmm, so to programmatically do this, you would have to go through the IMenuService.


ICommandService commandServ = (ICommandService) getSite().getWindow().getService(ICommandService.class);
IMenuService menuServ = (IMenuService) getSite().getWindow().getService(IMenuService.class);

SMenu viewMenu = menuServ.getMenu(new SLocation(SBar.VIEW_MENU, 
        "z.ex.view.keybindings.views.SampleView/z.ex.view.SampleViewMenu"));
viewMenu.define("Sample Menu", new SLocation(SBar.VIEW_MENU, 
        "z.ex.view.keybindings.views.SampleView"), "M");
SGroup viewGroup = menuServ.getGroup(new SLocation(SBar.VIEW_MENU, 
        "z.ex.view.keybindings.views.SampleView/z.ex.view.SampleViewMenu/z.ex.view.SampleViewGroup"));
viewGroup.define(new SLocation(SBar.VIEW_MENU, 
        "z.ex.view.keybindings.views.SampleView/z.ex.view.SampleViewMenu", false); 

Command viewCmd = commandServ.getCommand("z.ex.editor.commands.SampleViewAction");
SLocation viewLocation = new SLocation(SBar.VIEW_MENU, 
        "z.ex.view.keybindings.views.SampleView/z.ex.view.SampleViewMenu")
viewLocation.setOrder(new SOrder(SOrder.AFTER, "z.ex.view.SampleViewGroup"));
SItem viewItem = menuServ.getItem(new SLocation(SBar.VIEW_MENU, 
        "z.ex.view.keybindings.views.SampleView/z.ex.view.SampleViewMenu/z.ex.view.SampleViewAction.menu"));
viewItem.define(viewCmd, viewLocation, "V");
menuServ.contribute(viewItem);

Text editor popup action

Popups can be targetted at any registered context menu, or at all of them

<command id="z.ex.view.commands.SampleContributionAction"
    name="Sample Context Action"
    description="Sample Context Action command"/>
<extension
      point="org.eclipse.ui.commandImages">
   <image commandId="z.ex.view.commands.SampleContributionAction"
         icon="icons/sample.gif"/>
</extension>

Placing the action (which is specifically a menu or button linked to a command) can be accomplished with the org.eclipse.ui.menus extension point.

<extension
      point="org.eclipse.ui.menus">
   <item
         commandId="z.ex.view.commands.SampleContributionAction"
         mnemonic="C"
         id="z.ex.objectContribution.menu">
      <location type="contextMenu">
         <menu id="#EditorContext"/>
         <order after="z.ex.editor.contextGroup"/>
      </location>
   </item>
</extension>


Hmmmm, so to programmatically do this, you would have to go through the IMenuService.


Command contextCmd = commandServ.getCommand("z.ex.view.commands.SampleContributionAction");
SLocation contextLocation = new SLocation(SBar.CONTEXT_MENU, "#EditorContext");
contextLocation.setOrder(new SOrder(SOrder.AFTER, "z.ex.editor.contextGroup"));
SItem contextItem = menuServ.getItem(new SLocation(SBar.CONTEXT_MENU, "#EditorContext/z.ex.objectContribution.menu"));
contextItem.define(contextCmd, contextLocation, "C");
menuServ.contribute(contextItem);



Dynamic Previous Searches submenu

You want to add a dynamic "Previous Searches" submenu to the main Search menu.

<extension
      point="org.eclipse.ui.menus">
   <menu
         label="Previous Searches"
         mnemonic="c"
         id="com.example.registry.search.recent.menu">
      <dynamic class="com.example.registry.search.RecentMenu"/>
      <location type="menu">
         <menu id="org.eclipse.search.menu"/>
         <order after="additions"/>
      </location>
   </item>
</extension>

You can programmatically accomplish the same thing:

ICommandService commandServ = (ICommandService) getSite().getWindow().getService(ICommandService.class);
IMenuService menuServ = (IMenuService) getSite().getWindow().getService(IMenuService.class);

SMenu recentMenu = menuServ.getMenu(new SLocation(SBar.MENU, 
        "org.eclipse.search.menu/com.example.registry.search.recent.menu"));
SLocation menuLocation = new SLocation(SBar.MENU, 
        "org.eclipse.search.menu");
menuLocation.setOrder(new SOrder(SOrder.AFTER, "additions"));
recentMenu.define("Previous Searches", menuLocation, "c", new RecentMenu());

When your menu is about to show, you should get the callback:

public class RecentMenu implements IDynamicMenu {
    public void aboutToShow(IMenuCollection menu) {
        menu.clear();
        String[] searchIds = getSearchVew().getPreviousSearches();
        Command findCmd = commandServ.getCommand("com.example.registry.search.find");
        SLocation findLocation = new SLocation(SBar.MENU, "org.eclipse.search.menu/com.example.registry.search.recent.menu");
        for (int i=0; i<searchIds.length && i<4; i++) {
            SItem item = menuServ.getItem(new SLocation(SBar.MENU, 
                "org.eclipse.search.menu/com.example.registry.search.recent.menu/recentItem" + i));
            item.undefine();
            ParameterizedCommand parmFindCmd = ....; // findCmd + the searchId parameter
            item.define(parmFindCmd, findLocation);
            menu.add(item);
        }
    }
    public SearchViewPart getSearchView() {
        return ....;
    }
}

Dynamic Previous Searches editors group

You can have a group dynamically insert elements as a menu is shown.

<extension
      point="org.eclipse.ui.menus">
   <group
         groupId="com.example.registry.search.editors.menu"
         separatorsVisible="true">
      <dynamic class="com.example.registry.search.RecentSearchEditors"/>
      <location type="menu">
         <menu id="file"/>
         <order after="mru"/>
      </location>
   </group>
 </extension>

When the File menu is about to show, you will be called with your group IMenuCollection (not the entire File menu). But basically, it looks the same as the dynamic menu case.

public class RecentSearchEditors implements IDynamicMenu {
    public void aboutToShow(IMenuCollection menu) {
        menu.clear();
        String[] editorIds = getSearchVew().getPreviousOpenEditors();
        Command openCmd = commandServ.getCommand("com.example.registry.search.openEditor");
        SLocation fileLocation = new SLocation(SBar.MENU, "file");
        for (int i=0; i<editorIds.length && i<4; i++) {
            SItem item = menuServ.getItem(new SLocation(SBar.MENU, 
                "file/searchOpenEditor" + i));
            item.undefine();
            ParameterizedCommand parmOpenCmd = ....; // openCmd + the editorsId parameter
            item.define(parmOpenCmd, fileLocation);
            menu.add(item);
        }
    }
    public SearchViewPart getSearchView() {
        return ....;
    }
}

Added For Paul

<menu name="Window" id="window">
   <itemRef id="newWindow">
   <itemRef id="newEditor">
   <seperator id="seperator1">
   <menu name="Open Perspective" id="openPerspective"  class="generatePerspectivesMenu"/>
   <menu name="Show View" id="showView"/>
   <seperator id="seperator1">
   <itemRef id="customizePerspective">
   <itemRef id="savePerspective">
   <itemRef id="closePerspective">
   <itemRef id="closeAllPerspectives">
   <seperator id="seperator3">
   <menu name="Navigation" id="navigation">
   <seperator id="seperator4">
   </menu>
</menu>
<menu name="Working Sets" id="workingSets" after="window/navigation">
   <dynamic class="windowworkingsets"/>
   <itemRef id="editWorkingSets"/>
</menu>
<toolbar id="workingSet">
   <itemRef id="editWorkingSets"/>
</toolbar>
<itemRef id="hideToolbars" before="window/seperator1">


Example Matrix

Example Location visible when enabled when defined by placed by handled by comments
Add ProblemView menus view menu always always ViewPart & IActionBars ViewPart & IActionBars SampleViewAction
Add Toggle Mark Occurrences to main toolbar main menu always retarget action supplied org.eclipse.ui.actionSet & IActionBars org.eclipse.ui.actionSet & IActionBars ToggleMarkOccurrencesAction
File->Exit global menu always always ActionFactory WorkbenchActionBuilder QuitAction
Edit->Copy global menu always there is an enabled handler Workbench IDEApplication active part (what about Trim??) enablement determined by handler
Global toolbar->Save global toolbar always the active part needs saving Workbench IDEApplication Workbench
Global toolbar->Open Type global toolbar Java Navigation action set is enabled Java Navigation action set is enabled JDT UI JDT UI JDT UI
Global toolbar->Toggle Mark Occurrences global (editor) toolbar any Java editor is active any Java editor is active all Java Editors all Java Editors active Java Editor push button state is updated based on active editor
Search->Registry Search global menu Registry Search action set is enabled Registry Search action set is enabled plugin actionSet RegistrySearchAction
Widget in the main toolbar global toolbar Registry Search action set is enabled Registry Search action set is enabled plugin actionSet RegistrySearchAction
Edit->Undo relabel action global menu always always ActionFactory WorkbenchActionBuilder LabelRetargetAction
Search->Registry Search editor action global (editor) menu any registry editor is active any registry editor is active org.eclipse.ui.editorActions org.eclipse.ui.editorActions RegistrySearchAction
Search->Registry Search programmatic editor action global (editor) menu any registry editor is active any registry editor is active registry editor action bar contributor registry editor action bar contributor RegistrySearchAction
Add View submenu and item view menu always always org.eclipse.ui.viewActions org.eclipse.ui.viewActions SampleViewAction
Text editor popup action text editor context menu always always org.eclipse.ui.popupMenus org.eclipse.ui.popupMenus SampleContributionAction
IFile object contribution all context menus selection is an IFile always org.eclipse.ui.popupMenus org.eclipse.ui.popupMenus SampleContributionAction
Product removes Search Registry global menu never always ApplicationWorkbenchWindowAdvisor N/A menu service this cannot easily be done
Dynamic Previous Searches submenu global menu always always org.eclipse.ui.actionSets org.eclipse.ui.actionSets IMenuCreator
Dynamic Previous Searches editors group global menu always always N/A N/A IDynamicMenu

Back to the top