Jump to: navigation, search

Difference between revisions of "Table of WTP IDs"

(Introduction)
m (Introduction: Misc clean-up)
Line 4: Line 4:
 
It is important to document the usage of the ids, especially when they relate to menus, toolbars, commands, and popus as the org.eclipse.ui.menus extension point allows for other plugins to contribute to menus based off the ids that are published.  Commands are also referenced by id, and are implemented based on handlers.
 
It is important to document the usage of the ids, especially when they relate to menus, toolbars, commands, and popus as the org.eclipse.ui.menus extension point allows for other plugins to contribute to menus based off the ids that are published.  Commands are also referenced by id, and are implemented based on handlers.
  
Eclipse 3.3 introduced the org.eclipse.ui.menus extension point, this is to eventually replace the 4 contribution points that exist currently for creating menus.  A detailed mapping can be found at [[Menus_Extension_Mapping]].  Paul Webb has created a good overview of the new org.eclipse.ui.menus extension point in his [http://richclientplatform.blogspot.com/2007/07/new-menu-contribution-extension.html blog].
+
Eclipse 3.3 introduced the org.eclipse.ui.menus extension point, this is to eventually replace the 4 contribution points that exist currently for creating menus.  A detailed mapping can be found at [[Menus Extension Mapping]].  Paul Webster has created a good overview of the new org.eclipse.ui.menus extension point in his [http://richclientplatform.blogspot.com/2007/07/new-menu-contribution-extension.html blog].
  
The [[Platform_Command_Framework]] contains information on how to debug handlers and commands that aren't working.
+
The [[Platform Command Framework]] contains information on how to debug handlers and commands that aren't working.
  
 
==Menus==
 
==Menus==
The org.eclipse.ui.menus extension point allows for the definition of menus that other plugins can contribute too.  See [[Menu_Contributions]] and [http://help.eclipse.org/help33/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/workbench_cmd.htm Basic Workbench Extensions using Commands] for more information specifically for working with org.eclipse.ui.menus, org.eclipse.ui.commands, and org.eclipse.ui.handlers ([[Platform_Command_Framework]]).
+
The org.eclipse.ui.menus extension point allows for the definition of menus that other plugins can contribute too.  See [[Menu Contributions]] and [http://help.eclipse.org/help33/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/workbench_cmd.htm Basic Workbench Extensions using Commands] for more information specifically for working with org.eclipse.ui.menus, org.eclipse.ui.commands, and org.eclipse.ui.handlers ([[Platform Command Framework]]).
  
In addition, controlling when a menu or command is available can be implemented with [[Command_Core_Expressions]].
+
In addition, controlling when a menu or command is available can be implemented with [[Command Core Expressions]].
  
 
<table border="1">
 
<table border="1">
Line 26: Line 26:
 
   <td>SSE.ui/plugin.xml</td>
 
   <td>SSE.ui/plugin.xml</td>
 
   <td>Main Menu</td>
 
   <td>Main Menu</td>
   <td>A general source main menu that can be contributed to from other plugins.</td>
+
   <td>A general source main menu that can be contributed to from other plug-ins.</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
  
 
==Commands==
 
==Commands==
 
+
Commands are implemented and tied to menus using handlers.  They can also be tied to actionSets and have actionDelegates. If implemented using handlers, a command may have zero to many handlers, but only zero to one may be active at any given point in time.  Handlers can be specified using either the org.eclipse.ui.handlers extension point or programmatically.
Commands are implemented and tied to menus using handlers.  They can also be tied to actionSets and have action Delgates.   If implemented using handlers, a command may have zero to many handlers, but only zero to one may be active at any given point in time.  Handlers can be specified using either the org.eclipse.ui.handlers extension point or programtically.
+
  
 
<table border="1">
 
<table border="1">

Revision as of 23:16, 15 December 2007

Introduction

There are a vast number of ids that are used within the WTP. Every command, content-type, action, menu, etc has an id that is associated with it. This page will try to keep up to date with the various ids, where they can be found, and what they correspond too.

It is important to document the usage of the ids, especially when they relate to menus, toolbars, commands, and popus as the org.eclipse.ui.menus extension point allows for other plugins to contribute to menus based off the ids that are published. Commands are also referenced by id, and are implemented based on handlers.

Eclipse 3.3 introduced the org.eclipse.ui.menus extension point, this is to eventually replace the 4 contribution points that exist currently for creating menus. A detailed mapping can be found at Menus Extension Mapping. Paul Webster has created a good overview of the new org.eclipse.ui.menus extension point in his blog.

The Platform Command Framework contains information on how to debug handlers and commands that aren't working.

Menus

The org.eclipse.ui.menus extension point allows for the definition of menus that other plugins can contribute too. See Menu Contributions and Basic Workbench Extensions using Commands for more information specifically for working with org.eclipse.ui.menus, org.eclipse.ui.commands, and org.eclipse.ui.handlers (Platform Command Framework).

In addition, controlling when a menu or command is available can be implemented with Command Core Expressions.

Id Name Location Type Description
sourceMenuId Source SSE.ui/plugin.xml Main Menu A general source main menu that can be contributed to from other plug-ins.

Commands

Commands are implemented and tied to menus using handlers. They can also be tied to actionSets and have actionDelegates. If implemented using handlers, a command may have zero to many handlers, but only zero to one may be active at any given point in time. Handlers can be specified using either the org.eclipse.ui.handlers extension point or programmatically.

Id Category Id Menu/Toolbar Location Description
org.eclipse.wst.sse.ui.structure.select.enclosing org.eclipse.ui.category.edit Edit SSE.ui/plugin.xml Select Enclosing
org.eclipse.wst.sse.ui.structure.select.next org.eclipse.ui.category.edit Edit SSE.ui/plugin.xml Select Next
org.eclipse.wst.sse.ui.structure.select.previous org.eclipse.ui.category.edit Edit SSE.ui/plugin.xml Select Previous
org.eclipse.wst.sse.ui.structure.select.last org.eclipse.ui.category.edit Edit SSE.ui/plugin.xml Select Last
org.eclipse.wst.sse.ui.toggle.comment org.eclipse.ui.category.edit Source SSE.ui/plugin.xml Toggle Comment
org.eclipse.wst.sse.ui.add.block.comment org.eclipse.ui.category.edit Source SSE.ui/plugin.xml Add Block Comment
org.eclipse.wst.sse.ui.remove.block.comment org.eclipse.ui.category.edit Source SSE.ui/plugin.xml Remove Block Comment
org.eclipse.wst.sse.ui.cleanup.document org.eclipse.ui.category.edit Source SSE.ui/plugin.xml Cleanup Document
org.eclipse.wst.sse.ui.format.document org.eclipse.ui.category.edit Source SSE.ui/plugin.xml Format Document
org.eclipse.wst.sse.ui.format.active.elements org.eclipse.ui.category.edit Source SSE.ui/plugin.xml Format Active Elements
org.eclipse.wst.sse.ui.open.file.from.source org.eclipse.ui.category.edit Navigate SSE.ui/plugin.xml Open File From Source
org.eclipse.wst.sse.ui.search.find.occurrences org.eclipse.ui.category.edit Source SSE.ui/plugin.xml Find Occurrences