Attachment #90013 for bug #181515

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.




<?xml version='1.0' encoding='UTF-8'?>
<!-- Schema file written by PDE -->
<schema targetNamespace="org.eclipse.ui" xmlns="http://www.w3.org/2001/XMLSchema">
<annotation>
      <appinfo>
         <meta.schema plugin="org.eclipse.ui" id="perspectiveExtensions" name="Perspective Extensions"/>
      </appinfo>
      <documentation>
         This extension point is used to extend perspectives 
registered by other plug-ins. A perspective defines 

               <documentation>
                  an optional name of the extension instance
               </documentation>
               <appinfo>
                  <meta.attribute translatable="true"/>
               </appinfo>
            </annotation>
         </attribute>
      </complexType>


   <element name="perspectiveExtension">
      <annotation>
         <appinfo>
            <meta.element labelAttribute="targetID"/>
         </appinfo>
      </annotation>
      <complexType>
         <choice minOccurs="0" maxOccurs="unbounded">

            <annotation>
               <documentation>
                  the unique identifier of the perspective (as specified in the registry) into which the contribution is made. If the value is set to &quot;*&quot; the extension is applied to all perspectives.

               </documentation>
               <appinfo>
                  <meta.attribute kind="identifier" basedOn="org.eclipse.ui.perspectives/perspective/@id"/>
               </appinfo>
            </annotation>
         </attribute>
      </complexType>

               <documentation>
                  the unique identifier of the action set which will be added to the perspective.
               </documentation>
               <appinfo>
                  <meta.attribute kind="identifier" basedOn="org.eclipse.ui.actionSets/actionSet/@id"/>
               </appinfo>
            </annotation>
         </attribute>
      </complexType>

               <documentation>
                  the unique identifier of the view which will be added to the perspective&apos;s &quot;Show View&quot; submenu of the &quot;Window&quot; menu.
               </documentation>
               <appinfo>
                  <meta.attribute kind="identifier" basedOn="org.eclipse.ui.views/view/@id"/>
               </appinfo>
            </annotation>
         </attribute>
      </complexType>

               <documentation>
                  the unique identifier of the perspective which will be added to the perspective&apos;s &quot;Open Perspective&quot; submenu of the &quot;Window&quot; menu.
               </documentation>
               <appinfo>
                  <meta.attribute kind="identifier" basedOn="org.eclipse.ui.perspectives/perspective/@id"/>
               </appinfo>
            </annotation>
         </attribute>
      </complexType>

               <documentation>
                  the unique identifier of the new wizard which will be added to the perspective&apos;s &quot;New&quot; submenu of the &quot;File&quot; menu.
               </documentation>
               <appinfo>
                  <meta.attribute kind="identifier" basedOn="org.eclipse.ui.newWizards/wizard/@id"/>
               </appinfo>
            </annotation>
         </attribute>
      </complexType>

               <documentation>
                  the unique identifier of the view which will be added to the perspective&apos;s &quot;Show In...&quot; prompter in the Navigate menu.
               </documentation>
               <appinfo>
                  <meta.attribute kind="identifier" basedOn="org.eclipse.ui.views/view/@id"/>
               </appinfo>
            </annotation>
         </attribute>
      </complexType>

               <documentation>
                  the unique identifier of the view which will be added to the perspective layout.
               </documentation>
               <appinfo>
                  <meta.attribute kind="identifier" basedOn="org.eclipse.ui.views/view/@id"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="relative" type="string">

               <documentation>
                  the unique identifier of a view which already exists in the perspective.  This will be used as a reference point for placement of the view.  The relationship between these two views is defined by &lt;samp&gt;relationship&lt;/samp&gt;.  Ignored if relationship is &quot;fast&quot;.
               </documentation>
               <appinfo>
                  <meta.attribute kind="identifier" basedOn="org.eclipse.ui.views/view/@id"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="relationship" use="required">

   </element>

   <annotation>
      <appinfo>
         <meta.section type="examples"/>
      </appinfo>
      <documentation>
         The following is an example of a perspective extension (note the subelements and the way attributes are used):
&lt;p&gt;

   </annotation>

   <annotation>
      <appinfo>
         <meta.section type="apiInfo"/>
      </appinfo>
      <documentation>
         The items defined within the perspective extension are contributed to the initial contents of the target perspective.  Following this, the user may remove any contribution or add others to a perspective from within the workbench user interface.
      </documentation>
   </annotation>



         <meta.section type="implementation"/>
      </appInfo>
      <documentation>
         
      </documentation>
   </annotation>

   <annotation>
      <appinfo>
         <meta.section type="copyright"/>
      </appinfo>
      <documentation>
         Copyright (c) 2002, 2007 IBM Corporation and others.&lt;br&gt;
All rights reserved. This program and the accompanying materials are made




<?xml version='1.0' encoding='UTF-8'?>
<!-- Schema file written by PDE -->
<schema targetNamespace="org.eclipse.ui" xmlns="http://www.w3.org/2001/XMLSchema">
<annotation>
      <appinfo>
         <meta.schema plugin="org.eclipse.ui" id="commands" name="Commands"/>
      </appinfo>
      <documentation>
         &lt;p&gt;
The &lt;code&gt;org.eclipse.ui.commands&lt;/code&gt; extension point is used to declare commands and command categories, using the &lt;code&gt;command&lt;/code&gt; and &lt;code&gt;category&lt;/code&gt; elements. A command is an abstract representation of some semantic behaviour, but not it&apos;s actual implementation.  This allows different developers to contribute specific behaviour for their individual parts.  For example, there might be a &quot;paste&quot; command with one implementation in an editor and a different implementation in an explorer widget.  These implementations are called handlers.  Commands can also be viewed as declarative function pointers, or signal handlers.

               <documentation>
                  An optional name of the extension instance.
               </documentation>
               <appinfo>
                  <meta.attribute translatable="true"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="point" type="string" use="required">

               <documentation>
                  Please use &lt;code&gt;categoryId&lt;/code&gt; instead.
               </documentation>
               <appinfo>
                  <meta.attribute deprecated="true"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="description" type="string">

               <documentation>
                  A translatable short description of this command for display in the UI.
               </documentation>
               <appinfo>
                  <meta.attribute translatable="true"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="id" type="string" use="required">

               <documentation>
                  The translatable name of this command for display in the UI. Commands are typically named in the form of an imperative verb.
               </documentation>
               <appinfo>
                  <meta.attribute translatable="true"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="categoryId" type="string">

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Since: 3.0&lt;/em&gt;&lt;/p&gt;
               </documentation>
               <appinfo>
                  <meta.attribute kind="identifier" basedOn="org.eclipse.ui.commands/category/@id"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="defaultHandler" type="string">

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Since: 3.1&lt;/em&gt;&lt;/p&gt;
               </documentation>
               <appinfo>
                  <meta.attribute kind="java" basedOn="org.eclipse.core.commands.IHandler"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="returnTypeId" type="string">

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Since: 3.2&lt;/em&gt;&lt;/p&gt;
               </documentation>
               <appinfo>
                  <meta.attribute kind="identifier" basedOn="org.eclipse.ui.commands/commandParameterType/@id"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="helpContextId" type="string">

               <documentation>
                  A translatable short description of this category for display in the UI.
               </documentation>
               <appinfo>
                  <meta.attribute translatable="true"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="id" type="string" use="required">

               <documentation>
                  The translatable name of this category for display in the UI.
               </documentation>
               <appinfo>
                  <meta.attribute translatable="true"/>
               </appinfo>
            </annotation>
         </attribute>
      </complexType>


   <element name="commandParameter">
      <annotation>
         <appinfo>
            <meta.element labelAttribute="id"/>
         </appinfo>
         <documentation>
            &lt;p&gt;
Defines a parameter that a command should understand.  A parameter is a way to provide more information to a handler at execution time.  For example, a &quot;show view&quot; command might take a view as a parameter.  Handlers should be able to understand these parameters, so they should be treated like API.

               <documentation>
                  The name for the parameter.  This is the name as it will be displayed to an end-user.  As such, it should be translatable.  The name should be short -- preferrably one word.
               </documentation>
               <appinfo>
                  <meta.attribute translatable="true"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="values" type="string">

               <documentation>
                  The class providing a list of parameter values for the user to select.  This class should implement &lt;code&gt;org.eclipse.core.commands.IParameterValues&lt;/code&gt;.  If this class is not specified, you must specify the more verbose &lt;code&gt;values&lt;/code&gt; element.  Please see &lt;code&gt;org.eclipse.core.runtime.IExecutableExtension&lt;/code&gt;.
               </documentation>
               <appinfo>
                  <meta.attribute kind="java" basedOn="org.eclipse.core.commands.IParameterValues"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="typeId" type="string">

               <documentation>
                  The id of a commandParameterType for this commandParameter.  Specifying a typeId allows handlers of a command to convert string parameter values to objects in a consistent way and it allows potential callers of a command to look for commands that take objects of various types for their parameters.
               </documentation>
               <appinfo>
                  <meta.attribute kind="identifier" basedOn="org.eclipse.ui.commands/commandParameterType/@id"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="optional" type="boolean" use="default" value="true">

               <documentation>
                  The fully qualified name of a Java class or interface to use as the type of this command parameter.  This attribute is optional, however if omitted, &lt;code&gt;java.lang.Object&lt;/code&gt; will be used as the parameter type.
               </documentation>
               <appinfo>
                  <meta.attribute kind="java"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="converter" type="string">

               <documentation>
                  The class for converting between objects and string representations of objects for command parameter values.  This class should extend &lt;code&gt;org.eclipse.core.commands.AbstractParameterValueConverter&lt;/code&gt;. The converter should produce and consume objects of the type indicated in the &lt;code&gt;type&lt;/code&gt; attribute. If this class is not specified, this facility to convert between string and object values for this parameter type will not be available (the &lt;code&gt;getValueConverter()&lt;/code&gt; on class &lt;code&gt;ParameterType&lt;/code&gt; will return &lt;code&gt;null&lt;/code&gt;).
               </documentation>
               <appinfo>
                  <meta.attribute kind="java" basedOn="org.eclipse.core.commands.AbstractParameterValueConverter"/>
               </appinfo>
            </annotation>
         </attribute>
      </complexType>


   <element name="values">
      <annotation>
         <appinfo>
            <meta.element labelAttribute="class"/>
         </appinfo>
         <documentation>
            &lt;p&gt;
The more verbose version of the &lt;code&gt;values&lt;/code&gt; attribute on the &lt;code&gt;commandParameter&lt;/code&gt;.

               <documentation>
                  The class providing a list of parameter values for the user to select.  This class should implement &lt;code&gt;org.eclipse.core.commands.IParameterValues&lt;/code&gt;.  If this class is not specified, you must specify the more verbose &lt;code&gt;values&lt;/code&gt; element.  Please see &lt;code&gt;org.eclipse.core.runtime.IExecutableExtension&lt;/code&gt;.
               </documentation>
               <appinfo>
                  <meta.attribute kind="java" basedOn="org.eclipse.core.commands.IParameterValues"/>
               </appinfo>
            </annotation>
         </attribute>
      </complexType>


   <element name="parameter">
      <annotation>
         <appinfo>
            <meta.element labelAttribute="name"/>
         </appinfo>
         <documentation>
            &lt;p&gt;
A possible value for a parameter.


   <element name="defaultHandler">
      <annotation>
         <appinfo>
            <meta.element labelAttribute="class"/>
         </appinfo>
         <documentation>
            &lt;p&gt;
The default handler for this command.  If no other handler is active, this handler will be active.  This handler will conflict with other handler definitions that specify no &lt;code&gt;activeWhen&lt;/code&gt; conditions.  If you are not creating an &lt;code&gt;IExecutableExtension&lt;/code&gt;, you can use the &lt;code&gt;defaultHandler&lt;/code&gt; attribute instead.

               <documentation>
                  The class which implements &lt;code&gt;org.eclipse.core.commands.IHandler&lt;/code&gt;.
               </documentation>
               <appinfo>
                  <meta.attribute kind="java" basedOn="org.eclipse.core.commands.IHandler"/>
               </appinfo>
            </annotation>
         </attribute>
      </complexType>


   <element name="state">
      <annotation>
         <appinfo>
            <meta.element labelAttribute="class"/>
         </appinfo>
         <documentation>
            &lt;p&gt;
State information shared between all handlers, and potentially persisted between sessions.The state is simply a class that is loaded to look after the state.  See the API Information for more details.  This is not used for UI attributes like a menu contribution check box state or label.

               <documentation>
                  The class that can be loaded to store the state of this command.  State is shared amongst handlers, and can be persisted between sessions.  This class must implement &lt;code&gt;org.eclipse.core.commands.State&lt;/code&gt;.  Please see API Information.
               </documentation>
               <appinfo>
                  <meta.attribute kind="java"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="id" type="string" use="required">


   <element name="class">
      <annotation>
         <appinfo>
            <meta.element labelAttribute="class"/>
         </appinfo>
         <documentation>
            &lt;p&gt;
The class that can be loaded to store the state of this command.  This element is used if you wish to pass multiple parameters to an &lt;code&gt;org.eclipse.core.runtime.IExecutableExtension&lt;/code&gt;.

               <documentation>
                  The class that can be loaded to store the state of this command.  State is shared amongst handlers, and can be persisted between sessions.  This class must implement &lt;code&gt;org.eclipse.core.commands.State&lt;/code&gt;.  Please see API Information.
               </documentation>
               <appinfo>
                  <meta.attribute kind="java"/>
               </appinfo>
            </annotation>
         </attribute>
      </complexType>


   <element name="keyConfiguration">
      <annotation>
         <appinfo>
            <meta.element deprecated="true"/>
         </appinfo>
         <documentation>
            This element is used to define key configurations. If more than one of these elements exist with the same &lt;code&gt;id&lt;/code&gt; attribute, only the last declared element (in order of reading the plugin registry) is considered valid.  Please use the &quot;org.eclipse.ui.bindings&quot; extension point instead.
         </documentation>

               <documentation>
                  A translatable short description of this key configuration for display in the UI.
               </documentation>
               <appinfo>
                  <meta.attribute translatable="true" deprecated="true"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="id" type="string" use="required">

               <documentation>
                  The unique identifier of this key configuration.
               </documentation>
               <appinfo>
                  <meta.attribute deprecated="true"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="name" type="string" use="required">

               <documentation>
                  The translatable name of this key configuration for display in the UI. If this key configuration has a parent, it is not necessary to add &quot;(extends ...)&quot; to the name. This will be automatically added by the UI where necessary.
               </documentation>
               <appinfo>
                  <meta.attribute translatable="true" deprecated="true"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="parent" type="string">

                  The unique id of the parent key configuration. If this key configuration has a parent, it will borrow all key bindings from its parent, in addition to the key bindings defined in its own key configuration.
@deprecated Please use parentId instead.
               </documentation>
               <appinfo>
                  <meta.attribute deprecated="true"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="parentId" type="string">

               <documentation>
                  The unique id of the parent key configuration. If this key configuration has a parent, it will borrow all key bindings from its parent, in addition to the key bindings defined in its own key configuration.
               </documentation>
               <appinfo>
                  <meta.attribute deprecated="true"/>
               </appinfo>
            </annotation>
         </attribute>
      </complexType>


   <element name="context">
      <annotation>
         <appinfo>
            <meta.element deprecated="true"/>
         </appinfo>
         <documentation>
            This element is used to define contexts. If more than one of these elements exist with the same &lt;code&gt;id&lt;/code&gt; attribute, only the last declared element (in order of reading the plugin registry) is considered valid.  Please use the &lt;a href=&quot;org_eclipse_ui_contexts.html&quot;&gt;org.eclipse.ui.contexts&lt;/a&gt; extension point instead.
         </documentation>

               <documentation>
                  A translatable short description of this context for display in the UI.
               </documentation>
               <appinfo>
                  <meta.attribute translatable="true" deprecated="true"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="id" type="string" use="required">

               <documentation>
                  The unique identifier of this context.
               </documentation>
               <appinfo>
                  <meta.attribute deprecated="true"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="name" type="string" use="required">

               <documentation>
                  The translatable name of this context for display in the UI. If this context has a parent, it is not necessary to add &quot;(extends parent)&quot; to the name. This will be automatically added by the UI where necessary.
               </documentation>
               <appinfo>
                  <meta.attribute translatable="true" deprecated="true"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="parent" type="string">

                  The unique id of the parent context. If this context has a parent, it will borrow all key bindings from its parent, in addition to the key bindings defined in its own context.
@deprecated Please use &quot;parentId&quot; instead.
               </documentation>
               <appinfo>
                  <meta.attribute deprecated="true"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="parentId" type="string">

               <documentation>
                  The unique id of the parent context. If this context has a parent, it will borrow all key bindings from its parent, in addition to the key bindings defined in its own context.
               </documentation>
               <appinfo>
                  <meta.attribute deprecated="true"/>
               </appinfo>
            </annotation>
         </attribute>
      </complexType>


   <element name="scope">
      <annotation>
         <appinfo>
            <meta.element labelAttribute="id" deprecated="true"/>
         </appinfo>
         <documentation>
            This element is used to define scopes. If more than one of these elements exist with the same &lt;code&gt;id&lt;/code&gt; attribute, only the last declared element (in order of reading the plugin registry) is considered valid.
@deprecated Please use the &quot;org.eclipse.ui.contexts&quot; extension point instead.


@deprecated Please use the &quot;org.eclipse.ui.contexts&quot; extension point instead.
               </documentation>
               <appinfo>
                  <meta.attribute translatable="true" deprecated="true"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="id" type="string" use="required">


@deprecated Please use the &quot;org.eclipse.ui.contexts&quot; extension point instead.
               </documentation>
               <appinfo>
                  <meta.attribute deprecated="true"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="name" type="string" use="required">


@deprecated Please use the &quot;org.eclipse.ui.contexts&quot; extension point instead.
               </documentation>
               <appinfo>
                  <meta.attribute translatable="true" deprecated="true"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="parent" type="string">


@deprecated Please use the &quot;org.eclipse.ui.contexts&quot; extension point instead.
               </documentation>
               <appinfo>
                  <meta.attribute deprecated="true"/>
               </appinfo>
            </annotation>
         </attribute>
      </complexType>


   <element name="activeKeyConfiguration">
      <annotation>
         <appinfo>
            <meta.element deprecated="true"/>
         </appinfo>
         <documentation>
            &lt;p&gt;
This element is used to define the initial active key configuration for Eclipse. If more than one of these elements exist, only the last declared element (in order of reading the plugin registry) is considered valid.

               <documentation>
                  The unique id (&lt;code&gt;id&lt;/code&gt; attribute) of the keyConfiguration element one wishes to be initially active.
               </documentation>
               <appinfo>
                  <meta.attribute deprecated="true"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="keyConfigurationId" type="string">

               <documentation>
                  The unique id (&lt;code&gt;id&lt;/code&gt; attribute) of the keyConfiguration element one wishes to be initially active.
               </documentation>
               <appinfo>
                  <meta.attribute deprecated="true"/>
               </appinfo>
            </annotation>
         </attribute>
      </complexType>


   <element name="keyBinding">
      <annotation>
         <appinfo>
            <meta.element deprecated="true"/>
         </appinfo>
         <documentation>
            This element allows one to assign key sequences to commands.  Please use the &lt;code&gt;key&lt;/code&gt; element in the &quot;org.eclipse.ui.bindings&quot; extension point instead.
         </documentation>

                  The unique id of the key configuration of this key binding.
@deprecated Please use keyConfigurationId instead.
               </documentation>
               <appinfo>
                  <meta.attribute deprecated="true"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="command" type="string">

                  The unique identifier of the command to which the key sequence specified by this key binding is assigned. If the value of this attribute is an empty string, the key sequence is assigned to an internal &apos;no operation&apos; command. This is useful for &apos;undefining&apos; key bindings in specific key configurations and contexts which may have been borrowed from their parents.
@deprecated Please use &quot;commandId&quot; instead.
               </documentation>
               <appinfo>
                  <meta.attribute deprecated="true"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="locale" type="string">

               <documentation>
                  An optional attribute indicating that this key binding is only defined for the specified locale. Locales are specified according to the format declared in &lt;code&gt;java.util.Locale&lt;/code&gt;.
               </documentation>
               <appinfo>
                  <meta.attribute deprecated="true"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="platform" type="string">

               <documentation>
                  An optional attribute indicating that this key binding is only defined for the specified platform. The possible values of the &lt;code&gt;platform&lt;/code&gt; attribute are the set of the possible values returned by &lt;code&gt;org.eclipse.swt.SWT.getPlatform()&lt;/code&gt;.
               </documentation>
               <appinfo>
                  <meta.attribute deprecated="true"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="contextId" type="string">

               <documentation>
                  The unique id of the context of this key binding.
               </documentation>
               <appinfo>
                  <meta.attribute deprecated="true"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="string" type="string">

                  The key sequence to assign to the command. Key sequences consist of one or more key strokes, where a key stroke consists of a key on the keyboard, optionally pressed in combination with one or more of the following modifiers: Ctrl, Alt, Shift, and Command. Key strokes are separated by spaces, and modifiers are separated by &apos;+&apos; characters.
@deprecated Please use &quot;keySequence&quot; instead.
               </documentation>
               <appinfo>
                  <meta.attribute deprecated="true"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="scope" type="string">

                  The unique id of the context of this key binding.
@deprecated Please use &quot;contextId&quot; instead.  The old default scope, &quot;org.eclipse.ui.globalScope&quot;, has been changed to &quot;org.eclipse.ui.contexts.window&quot;.  The old name is still supported, but it is deprecated.
               </documentation>
               <appinfo>
                  <meta.attribute deprecated="true"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="keyConfigurationId" type="string">

                  The unique id of the key configuration of this key binding.
@deprecated Please use the &lt;code&gt;schemeId&lt;/code&gt; attribute on the &lt;code&gt;key&lt;/code&gt; element in the new &quot;org.eclipse.ui.bindings&quot; extension point.
               </documentation>
               <appinfo>
                  <meta.attribute deprecated="true"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="commandId" type="string">

               <documentation>
                  The unique identifier of the command to which the key sequence specified by this key binding is assigned. If the value of this attribute is an empty string, the key sequence is assigned to an internal &apos;no operation&apos; command. This is useful for &apos;undefining&apos; key bindings in specific key configurations and contexts which may have been borrowed from their parents.
               </documentation>
               <appinfo>
                  <meta.attribute deprecated="true"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="keySequence" type="string">

&lt;p&gt;The modifier keys can also be expressed in a platform-independent way.  On MacOS X, for example, &quot;Command&quot; is almost always used in place of &quot;Ctrl&quot;.  So, we provide &quot;M1&quot; which will map to either &quot;Ctrl&quot; or &quot;Command&quot;, as appropriate.  Similarly, &quot;M2&quot; is &quot;Shift&quot;; &quot;M3&quot; is &quot;Alt&quot;; and &quot;M4&quot; is &quot;Ctrl&quot; (MacOS X).  If more platforms are added, then you can count on these aliases being mapped to good platform defaults.&lt;/p&gt;
&lt;p&gt;The syntax for this string is defined in &lt;code&gt;org.eclipse.ui.internal.keys&lt;/code&gt;.  Briefly, the string is case insensitive -- though all capitals is preferred stylistically.  If the key is a letter, then simply append the letter.  If the key is a special key (i.e., non-ASCII), then use one of the following: ARROW_DOWN, ARROW_LEFT, ARROW_RIGHT, ARROW_UP, BREAK, CAPS_LOCK, END, F1, F2, F3, F4, F5, F6, F7, F8, F9, F10, F11, F12, F13, F14, F15, HOME, INSERT, NUM_LOCK, NUMPAD_0, NUMPAD_1, NUMPAD_2, NUMPAD_3, NUMPAD_4, NUMPAD_5, NUMPAD_6, NUMPAD_7, NUMPAD_8, NUMPAD_9, NUMPAD_ADD, NUMPAD_DECIMAL, NUMPAD_DIVIDE, NUMPAD_ENTER, NUMPAD_EQUAL, NUMPAD_MULTIPLY, NUMPAD_SUBTRACT, PAGE_UP, PAGE_DOWN, PAUSE, PRINT_SCREEN, or SCROLL_LOCK.  If the key is a non-printable ASCII key, then use one of the following: BS, CR, DEL, ESC, FF, LF, NUL, SPACE, TAB, or VT.  Note that the main keyboard enter/return key is CR.&lt;/p&gt;
               </documentation>
               <appinfo>
                  <meta.attribute deprecated="true"/>
               </appinfo>
            </annotation>
         </attribute>
      </complexType>
   </element>

   <annotation>
      <appinfo>
         <meta.section type="since"/>
      </appinfo>
      <documentation>
         &lt;p&gt;
2.1

   </annotation>

   <annotation>
      <appinfo>
         <meta.section type="examples"/>
      </appinfo>
      <documentation>
         &lt;p&gt;
The &lt;code&gt;plugin.xml&lt;/code&gt; file in the &lt;code&gt;org.eclipse.ui&lt;/code&gt; plugin makes extensive use of the &lt;code&gt;org.eclipse.ui.commands&lt;/code&gt; extension point.

   </annotation>

   <annotation>
      <appinfo>
         <meta.section type="apiInfo"/>
      </appinfo>
      <documentation>
         &lt;p&gt;
Handlers can be registered with commands using the &lt;code&gt;org.eclipse.ui.handlers.IHandlerService&lt;/code&gt;.  This can be retrieved from various workbench components (e.g., workbench, workbench window, part site, etc.) by calling &lt;code&gt;getService(IHandlerService.class)&lt;/code&gt;.

      </documentation>
   </annotation>


      <appInfo>
         <meta.section type="implementation"/>
      </appInfo>
      <documentation>
         
      </documentation>
   </annotation>

   <annotation>
      <appinfo>
         <meta.section type="copyright"/>
      </appinfo>
      <documentation>
         Copyright (c) 2000, 2007 IBM Corporation and others.&lt;br&gt;
All rights reserved. This program and the accompanying materials are made




<?xml version='1.0' encoding='UTF-8'?>
<!-- Schema file written by PDE -->
<schema targetNamespace="org.eclipse.ui" xmlns="http://www.w3.org/2001/XMLSchema">
<annotation>
      <appinfo>
         <meta.schema plugin="org.eclipse.ui" id="bindings" name="Bindings"/>
      </appinfo>
      <documentation>
         &lt;p&gt;
The &lt;code&gt;org.eclipse.ui.bindings&lt;/code&gt; extension point is used to declare bindings and schemes.  Schemes are sets of one or more bindings.  A binding is a mapping between a certain group of conditions, some user input and a triggered command.

               <documentation>
                  
               </documentation>
               <appinfo>
                  <meta.attribute translatable="true"/>
               </appinfo>
            </annotation>
         </attribute>
      </complexType>


   <element name="scheme">
      <annotation>
         <appinfo>
            <meta.element labelAttribute="name"/>
         </appinfo>
         <documentation>
            &lt;p&gt;
A scheme is a grouping of bindings that an end user can chose to use.

               <documentation>
                  The name for this scheme, as it should be displayed to an end-user.  This value should be translated.
               </documentation>
               <appinfo>
                  <meta.attribute translatable="true"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="description" type="string">

               <documentation>
                  The description for this scheme, as it would be displayed to an end user.  This value should be translated.
               </documentation>
               <appinfo>
                  <meta.attribute translatable="true"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="parentId" type="string">

               <documentation>
                  The identifier for the parent of this scheme.  If there is no parent, then do not specify this attribute.
               </documentation>
               <appinfo>
                  <meta.attribute kind="identifier" basedOn="org.eclipse.ui.bindings/scheme/@id"/>
               </appinfo>
            </annotation>
         </attribute>
      </complexType>


   <element name="key">
      <annotation>
         <appinfo>
            <meta.element labelAttribute="commandId"/>
         </appinfo>
         <documentation>
            &lt;p&gt;A binding between some keyboard input and the triggering of a command.&lt;/p&gt;
         </documentation>

               <documentation>
                  The identifier of the scheme in which this key binding is active.
               </documentation>
               <appinfo>
                  <meta.attribute kind="identifier" basedOn="org.eclipse.ui.bindings/scheme/@id"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="contextId" type="string" use="default" value="org.eclipse.ui.contexts.window">

               <documentation>
                  The identifier of the context in which this key binding is active.  Please see the &lt;code&gt;org.eclipse.ui.contexts&lt;/code&gt; extension point.  If this is not specified, then it defaults to &lt;code&gt;org.eclipse.ui.contexts.window&lt;/code&gt;.
               </documentation>
               <appinfo>
                  <meta.attribute kind="identifier" basedOn="org.eclipse.ui.contexts/context/@id"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="commandId" type="string">

If no command identifier is specified, this is a deletion marker.  This means that any binding in the same context with the same sequence, platform and locale will become inactive when this binding becomes active.  If the platform or locale on a deletion is not specified, then it matches any platform or locale.
&lt;/p&gt;
               </documentation>
               <appinfo>
                  <meta.attribute kind="identifier" basedOn="org.eclipse.ui.commands/command/@id"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="platform" type="string">


   <element name="parameter">
      <annotation>
         <appinfo>
            <meta.element labelAttribute="id"/>
         </appinfo>
         <documentation>
            A parameter name and value that should be passed to the command when it is executed.  This allows for the command to be qualified in some way.  For example, a &quot;Show View&quot; command might accept the view id as a parameter.
         </documentation>

               <documentation>
                  The parameter name as understood by the command.  This is not a translatable name, but the key to name-value map.
               </documentation>
               <appinfo>
                  <meta.attribute kind="identifier" basedOn="org.eclipse.ui.commands/command/commandParameter/@id"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="value" type="string">

   </element>

   <annotation>
      <appinfo>
         <meta.section type="since"/>
      </appinfo>
      <documentation>
         3.1
      </documentation>
   </annotation>

   <annotation>
      <appinfo>
         <meta.section type="examples"/>
      </appinfo>
      <documentation>
         &lt;pre&gt;
&lt;extension

   </annotation>

   <annotation>
      <appinfo>
         <meta.section type="apiInfo"/>
      </appinfo>
      <documentation>
         &lt;p&gt;
There is no public API for defining bindings.  To try to achieve stability for the user, bindings are only defined through the extension points.  If you are an RCP application, you should be able to override this behaviour in the &lt;code&gt;WorkbenchAdvisor&lt;/code&gt;.

   </annotation>



   <annotation>
      <appinfo>
         <meta.section type="copyright"/>
      </appinfo>
      <documentation>
         Copyright (c) 2005,2007 IBM Corporation and others.&lt;br&gt;
All rights reserved. This program and the accompanying materials are made




<?xml version='1.0' encoding='UTF-8'?>
<!-- Schema file written by PDE -->
<schema targetNamespace="org.eclipse.ui" xmlns="http://www.w3.org/2001/XMLSchema">
<annotation>
      <appinfo>
         <meta.schema plugin="org.eclipse.ui" id="contexts" name="Contexts"/>
      </appinfo>
      <documentation>
         &lt;p&gt;
The &lt;code&gt;org.eclipse.ui.contexts&lt;/code&gt; extension point is used to declare contexts and associated elements.

               <documentation>
                  An optional name of the extension instance.
               </documentation>
               <appinfo>
                  <meta.attribute translatable="true"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="point" type="string" use="required">

               <documentation>
                  A translatable short description of this context for display in the UI.
               </documentation>
               <appinfo>
                  <meta.attribute translatable="true"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="id" type="string" use="required">

               <documentation>
                  The translatable name of this context for display in the UI.
               </documentation>
               <appinfo>
                  <meta.attribute translatable="true"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="parentId" type="string">

               <documentation>
                  The unique identifier of the parent of this context.
               </documentation>
               <appinfo>
                  <meta.attribute kind="identifier" basedOn="org.eclipse.ui.contexts/context/@id"/>
               </appinfo>
            </annotation>
         </attribute>
      </complexType>
   </element>

   <annotation>
      <appinfo>
         <meta.section type="since"/>
      </appinfo>
      <documentation>
         &lt;p&gt;
3.0

   </annotation>

   <annotation>
      <appinfo>
         <meta.section type="examples"/>
      </appinfo>
      <documentation>
         &lt;p&gt;
The &lt;code&gt;plugin.xml&lt;/code&gt; file in the &lt;code&gt;org.eclipse.ui&lt;/code&gt; plugin makes use of the &lt;code&gt;org.eclipse.ui.contexts&lt;/code&gt; extension point.

   </annotation>

   <annotation>
      <appinfo>
         <meta.section type="apiInfo"/>
      </appinfo>
      <documentation>
         &lt;p&gt;
In general, it is preferrably to declare all contexts statically (in &lt;code&gt;plugin.xml&lt;/code&gt;).  This is so that users can use them in key bindings.  However, it is possible to declare contexts at run-time.  To do this, retrieve the &lt;code&gt;org.eclipse.ui.commands.IContextService&lt;/code&gt; from a workbench component, call &lt;code&gt;getContext(contextId)&lt;/code&gt; and then call &lt;code&gt;Context#define(...)&lt;/code&gt;.

      </documentation>
   </annotation>


      <appInfo>
         <meta.section type="implementation"/>
      </appInfo>
      <documentation>
         
      </documentation>
   </annotation>

   <annotation>
      <appinfo>
         <meta.section type="copyright"/>
      </appinfo>
      <documentation>
         Copyright (c) 2000, 2007 IBM Corporation and others.&lt;br&gt;
All rights reserved. This program and the accompanying materials are made




<?xml version='1.0' encoding='UTF-8'?>
<!-- Schema file written by PDE -->
<schema targetNamespace="org.eclipse.ui" xmlns="http://www.w3.org/2001/XMLSchema">
<annotation>
      <appinfo>
         <meta.schema plugin="org.eclipse.ui" id="commandImages" name="Command Images"/>
      </appinfo>
      <documentation>
         &lt;p&gt;
The images extension point provides a way of linking different types of images and icons to a particular command.  These images can be used, as appropriate, wherever the command appears in the user interface.  To accommodate some boundary cases (e.g., tool bar drop-down items), it is possible to group the images for a particular commands into &quot;styles&quot;.  These styles can then be specifically requested when a command is to be displayed.

               <documentation>
                  
               </documentation>
               <appinfo>
                  <meta.attribute translatable="true"/>
               </appinfo>
            </annotation>
         </attribute>
      </complexType>


   <element name="image">
      <annotation>
         <appinfo>
            <meta.element labelAttribute="commandId"/>
         </appinfo>
         <documentation>
            The images to associate with a particular command.
         </documentation>

               <documentation>
                  The identifier of the command with which the images should be associated.
               </documentation>
               <appinfo>
                  <meta.attribute kind="identifier" basedOn="org.eclipse.ui.commands/command/@id"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="icon" type="string" use="required">

               <documentation>
                  The path to the icon which should be used in the default case.  This will appear when the icon is enabled and mouse is not hovering over it.  It will also be used in any situation where such a more specific icon is not available.
               </documentation>
               <appinfo>
                  <meta.attribute kind="resource"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="disabledIcon" type="string">

               <documentation>
                  The icon to display when the command is disabled.
               </documentation>
               <appinfo>
                  <meta.attribute kind="resource"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="hoverIcon" type="string">

               <documentation>
                  The icon to display when the user is hovering over the command.
               </documentation>
               <appinfo>
                  <meta.attribute kind="resource"/>
               </appinfo>
            </annotation>
         </attribute>
         <attribute name="style" type="string">

   </element>

   <annotation>
      <appinfo>
         <meta.section type="since"/>
      </appinfo>
      <documentation>
         3.2
      </documentation>
   </annotation>

   <annotation>
      <appinfo>
         <meta.section type="examples"/>
      </appinfo>
      <documentation>
         &lt;pre&gt;
&lt;extension

   </annotation>

   <annotation>
      <appinfo>
         <meta.section type="apiInfo"/>
      </appinfo>
      <documentation>
         &lt;p&gt;
Within the workbench, it is possible to get images for commands using the &lt;code&gt;org.eclipse.ui.commands.ICommandImageService&lt;/code&gt; interface.  This interface can be retrieved from supporting workbench objects, such as &lt;code&gt;IWorkbench&lt;/code&gt; itself, the &lt;code&gt;IWorkbenchWindow&lt;/code&gt;, or the &lt;code&gt;IWorkbenchPartSite&lt;/code&gt;.  To retrieve the service, you would make a call like &lt;code&gt;workbench.getService(ICommandImageService.class)&lt;/code&gt;.

   </annotation>



   <annotation>
      <appinfo>
         <meta.section type="copyright"/>
      </appinfo>
      <documentation>
         Copyright (c) 2005,2007 IBM Corporation and others.&lt;br&gt;
All rights reserved. This program and the accompanying materials are made

Lines 401-406 Link Here

(-)schema/menus.exsd (+6 lines)
401	<documentation>	401	<documentation>
402	The name is either the name of the parameter to pass to the executable extension, or the identifier of the parameter for the command.	402	The name is either the name of the parameter to pass to the executable extension, or the identifier of the parameter for the command.
403	</documentation>	403	</documentation>
		404	<appinfo>
		405	<meta.attribute kind="identifier" basedOn="org.eclipse.ui.commands/command/commandParameter/@id"/>
		406	</appinfo>
404	</annotation>	407	</annotation>
405	</attribute>	408	</attribute>
406	<attribute name="value" type="string" use="required">	409	<attribute name="value" type="string" use="required">
Lines 619-624 Link Here
619	<documentation>	622	<documentation>
620	This is the id of the Command that is to be bound to this element. This is the hook into the Commands/Handlers/Key binding services that actually do the work should this item be selected. In many cases this command will have been defined in a previous extension declaration.	623	This is the id of the Command that is to be bound to this element. This is the hook into the Commands/Handlers/Key binding services that actually do the work should this item be selected. In many cases this command will have been defined in a previous extension declaration.
621	</documentation>	624	</documentation>
		625	<appinfo>
		626	<meta.attribute kind="identifier" basedOn="org.eclipse.ui.commands/command/@id"/>
		627	</appinfo>
622	</annotation>	628	</annotation>
623	</attribute>	629	</attribute>
624	<attribute name="id" type="string">	630	<attribute name="id" type="string">

Lines 1-10 Link Here

(-)schema/handlers.exsd (-23 / +19 lines)
1	<?xml version='1.0' encoding='UTF-8'?>	1	<?xml version='1.0' encoding='UTF-8'?>
2	<!-- Schema file written by PDE -->	2	<!-- Schema file written by PDE -->
3	<schema targetNamespace="org.eclipse.ui">	3	<schema targetNamespace="org.eclipse.ui" xmlns="http://www.w3.org/2001/XMLSchema">
4	<annotation>	4	<annotation>
5	<appInfo>	5	<appinfo>
6	<meta.schema plugin="org.eclipse.ui" id="handlers" name="Handlers"/>	6	<meta.schema plugin="org.eclipse.ui" id="handlers" name="Handlers"/>
7	</appInfo>	7	</appinfo>
8	<documentation>	8	<documentation>
9	<p>	9	<p>
10	The handlers extension point is an elaboration of the experimental <code>handlerSubmission</code> element defined in Eclipse 3.0. A handler is the behaviour of a command at a particular point in time. A command can have zero or more handlers associated with it. At any one point in time, however, a command will either have no active handler or one active handler. The active handler is the one which is currently responsible for carrying out the behaviour of the command. This is very similar to the concept of an action handler and a retargettable action.	10	The handlers extension point is an elaboration of the experimental <code>handlerSubmission</code> element defined in Eclipse 3.0. A handler is the behaviour of a command at a particular point in time. A command can have zero or more handlers associated with it. At any one point in time, however, a command will either have no active handler or one active handler. The active handler is the one which is currently responsible for carrying out the behaviour of the command. This is very similar to the concept of an action handler and a retargettable action.
Lines 75-80 Link Here
75	<documentation>	75	<documentation>
76	<p>The id of the command to associate with this handler implementation.</p>	76	<p>The id of the command to associate with this handler implementation.</p>
77	</documentation>	77	</documentation>
		78	<appinfo>
		79	<meta.attribute kind="identifier" basedOn="org.eclipse.ui.commands/command/@id"/>
		80	</appinfo>
78	</annotation>	81	</annotation>
79	</attribute>	82	</attribute>
80	<attribute name="class" type="string">	83	<attribute name="class" type="string">
Lines 82-90 Link Here
82	<documentation>	85	<documentation>
83	<p>The handler class that imlements <code>org.eclipse.core.commands.IHandler</code> or extends <code>org.eclipse.core.commands.AbstractHandler</code>.</p>	86	<p>The handler class that imlements <code>org.eclipse.core.commands.IHandler</code> or extends <code>org.eclipse.core.commands.AbstractHandler</code>.</p>
84	</documentation>	87	</documentation>
85	<appInfo>	88	<appinfo>
86	<meta.attribute kind="java" basedOn="org.eclipse.core.commands.IHandler"/>	89	<meta.attribute kind="java" basedOn="org.eclipse.core.commands.IHandler"/>
87	</appInfo>	90	</appinfo>
88	</annotation>	91	</annotation>
89	</attribute>	92	</attribute>
90	<attribute name="helpContextId" type="string">	93	<attribute name="helpContextId" type="string">
Lines 165-173 Link Here
165	<documentation>	168	<documentation>
166	<p>The handler class that imlements <code>org.eclipse.core.commands.IHandler</code> or extends <code>org.eclipse.core.commands.AbstractHandler</code>.</p>	169	<p>The handler class that imlements <code>org.eclipse.core.commands.IHandler</code> or extends <code>org.eclipse.core.commands.AbstractHandler</code>.</p>
167	</documentation>	170	</documentation>
168	<appInfo>	171	<appinfo>
169	<meta.attribute kind="java" basedOn="org.eclipse.core.commands.IHandler"/>	172	<meta.attribute kind="java" basedOn="org.eclipse.core.commands.IHandler"/>
170	</appInfo>	173	</appinfo>
171	</annotation>	174	</annotation>
172	</attribute>	175	</attribute>
173	</complexType>	176	</complexType>
Lines 198-215 Link Here
198	</element>	201	</element>
199		202
200	<annotation>	203	<annotation>
201	<appInfo>	204	<appinfo>
202	<meta.section type="since"/>	205	<meta.section type="since"/>
203	</appInfo>	206	</appinfo>
204	<documentation>	207	<documentation>
205	3.1	208	3.1
206	</documentation>	209	</documentation>
207	</annotation>	210	</annotation>
208		211
209	<annotation>	212	<annotation>
210	<appInfo>	213	<appinfo>
211	<meta.section type="examples"/>	214	<meta.section type="examples"/>
212	</appInfo>	215	</appinfo>
213	<documentation>	216	<documentation>
214	<p>	217	<p>
215	Variables that are valid in activeWhen and enabledWhen expressions can be found in <code>org.eclipse.ui.ISources</code>. The types of the variables are determined by the <code>org.eclipse.ui.ISourceProvider</code> that provides them.	218	Variables that are valid in activeWhen and enabledWhen expressions can be found in <code>org.eclipse.ui.ISources</code>. The types of the variables are determined by the <code>org.eclipse.ui.ISourceProvider</code> that provides them.
Lines 263-271 Link Here
263	</annotation>	266	</annotation>
264		267
265	<annotation>	268	<annotation>
266	<appInfo>	269	<appinfo>
267	<meta.section type="apiInfo"/>	270	<meta.section type="apiInfo"/>
268	</appInfo>	271	</appinfo>
269	<documentation>	272	<documentation>
270	<p>	273	<p>
271	All handlers implement <code>org.eclipse.core.commands.IHandler</code>, and can use <code>org.eclipse.core.commands.AbstractHandler</code> as a base class. Within the workbench, it is possible to activate and deactivate handlers using the <code>org.eclipse.ui.handlers.IHandlerService</code> interface. This interface can be retrieved from supporting workbench objects, such as <code>IWorkbench</code> itself, a workbench window, or a part site. To retrieve the service, you would make a call like <code>IWorkbench.getService(IHandlerService.class)</code>.	274	All handlers implement <code>org.eclipse.core.commands.IHandler</code>, and can use <code>org.eclipse.core.commands.AbstractHandler</code> as a base class. Within the workbench, it is possible to activate and deactivate handlers using the <code>org.eclipse.ui.handlers.IHandlerService</code> interface. This interface can be retrieved from supporting workbench objects, such as <code>IWorkbench</code> itself, a workbench window, or a part site. To retrieve the service, you would make a call like <code>IWorkbench.getService(IHandlerService.class)</code>.
Lines 284-302 Link Here
284	</documentation>	287	</documentation>
285	</annotation>	288	</annotation>
286		289
287	<annotation>	290
288	<appInfo>
289	<meta.section type="implementation"/>
290	</appInfo>
291	<documentation>
292
293	</documentation>
294	</annotation>
295		291
296	<annotation>	292	<annotation>
297	<appInfo>	293	<appinfo>
298	<meta.section type="copyright"/>	294	<meta.section type="copyright"/>
299	</appInfo>	295	</appinfo>
300	<documentation>	296	<documentation>
301	Copyright (c) 2005, 2007 IBM Corporation and others.<br>	297	Copyright (c) 2005, 2007 IBM Corporation and others.<br>
302	All rights reserved. This program and the accompanying materials are made	298	All rights reserved. This program and the accompanying materials are made

Return to bug 181515

Lines 1-10 Link Here

(-)schema/perspectiveExtensions.exsd (-22 / +39 lines)
1	<?xml version='1.0' encoding='UTF-8'?>	1	<?xml version='1.0' encoding='UTF-8'?>
2	<!-- Schema file written by PDE -->	2	<!-- Schema file written by PDE -->
3	<schema targetNamespace="org.eclipse.ui">	3	<schema targetNamespace="org.eclipse.ui" xmlns="http://www.w3.org/2001/XMLSchema">
4	<annotation>	4	<annotation>
5	<appInfo>	5	<appinfo>
6	<meta.schema plugin="org.eclipse.ui" id="perspectiveExtensions" name="Perspective Extensions"/>	6	<meta.schema plugin="org.eclipse.ui" id="perspectiveExtensions" name="Perspective Extensions"/>
7	</appInfo>	7	</appinfo>
8	<documentation>	8	<documentation>
9	This extension point is used to extend perspectives	9	This extension point is used to extend perspectives
10	registered by other plug-ins. A perspective defines	10	registered by other plug-ins. A perspective defines
Lines 42-50 Link Here
42	<documentation>	42	<documentation>
43	an optional name of the extension instance	43	an optional name of the extension instance
44	</documentation>	44	</documentation>
45	<appInfo>	45	<appinfo>
46	<meta.attribute translatable="true"/>	46	<meta.attribute translatable="true"/>
47	</appInfo>	47	</appinfo>
48	</annotation>	48	</annotation>
49	</attribute>	49	</attribute>
50	</complexType>	50	</complexType>
Lines 52-60 Link Here
52		52
53	<element name="perspectiveExtension">	53	<element name="perspectiveExtension">
54	<annotation>	54	<annotation>
55	<appInfo>	55	<appinfo>
56	<meta.element labelAttribute="targetID"/>	56	<meta.element labelAttribute="targetID"/>
57	</appInfo>	57	</appinfo>
58	</annotation>	58	</annotation>
59	<complexType>	59	<complexType>
60	<choice minOccurs="0" maxOccurs="unbounded">	60	<choice minOccurs="0" maxOccurs="unbounded">
Lines 69-76 Link Here
69	<annotation>	69	<annotation>
70	<documentation>	70	<documentation>
71	the unique identifier of the perspective (as specified in the registry) into which the contribution is made. If the value is set to "*" the extension is applied to all perspectives.	71	the unique identifier of the perspective (as specified in the registry) into which the contribution is made. If the value is set to "*" the extension is applied to all perspectives.
72
73	</documentation>	72	</documentation>
		73	<appinfo>
		74	<meta.attribute kind="identifier" basedOn="org.eclipse.ui.perspectives/perspective/@id"/>
		75	</appinfo>
74	</annotation>	76	</annotation>
75	</attribute>	77	</attribute>
76	</complexType>	78	</complexType>
Lines 83-88 Link Here
83	<documentation>	85	<documentation>
84	the unique identifier of the action set which will be added to the perspective.	86	the unique identifier of the action set which will be added to the perspective.
85	</documentation>	87	</documentation>
		88	<appinfo>
		89	<meta.attribute kind="identifier" basedOn="org.eclipse.ui.actionSets/actionSet/@id"/>
		90	</appinfo>
86	</annotation>	91	</annotation>
87	</attribute>	92	</attribute>
88	</complexType>	93	</complexType>
Lines 95-100 Link Here
95	<documentation>	100	<documentation>
96	the unique identifier of the view which will be added to the perspective's "Show View" submenu of the "Window" menu.	101	the unique identifier of the view which will be added to the perspective's "Show View" submenu of the "Window" menu.
97	</documentation>	102	</documentation>
		103	<appinfo>
		104	<meta.attribute kind="identifier" basedOn="org.eclipse.ui.views/view/@id"/>
		105	</appinfo>
98	</annotation>	106	</annotation>
99	</attribute>	107	</attribute>
100	</complexType>	108	</complexType>
Lines 107-112 Link Here
107	<documentation>	115	<documentation>
108	the unique identifier of the perspective which will be added to the perspective's "Open Perspective" submenu of the "Window" menu.	116	the unique identifier of the perspective which will be added to the perspective's "Open Perspective" submenu of the "Window" menu.
109	</documentation>	117	</documentation>
		118	<appinfo>
		119	<meta.attribute kind="identifier" basedOn="org.eclipse.ui.perspectives/perspective/@id"/>
		120	</appinfo>
110	</annotation>	121	</annotation>
111	</attribute>	122	</attribute>
112	</complexType>	123	</complexType>
Lines 119-124 Link Here
119	<documentation>	130	<documentation>
120	the unique identifier of the new wizard which will be added to the perspective's "New" submenu of the "File" menu.	131	the unique identifier of the new wizard which will be added to the perspective's "New" submenu of the "File" menu.
121	</documentation>	132	</documentation>
		133	<appinfo>
		134	<meta.attribute kind="identifier" basedOn="org.eclipse.ui.newWizards/wizard/@id"/>
		135	</appinfo>
122	</annotation>	136	</annotation>
123	</attribute>	137	</attribute>
124	</complexType>	138	</complexType>
Lines 131-136 Link Here
131	<documentation>	145	<documentation>
132	the unique identifier of the view which will be added to the perspective's "Show In..." prompter in the Navigate menu.	146	the unique identifier of the view which will be added to the perspective's "Show In..." prompter in the Navigate menu.
133	</documentation>	147	</documentation>
		148	<appinfo>
		149	<meta.attribute kind="identifier" basedOn="org.eclipse.ui.views/view/@id"/>
		150	</appinfo>
134	</annotation>	151	</annotation>
135	</attribute>	152	</attribute>
136	</complexType>	153	</complexType>
Lines 143-148 Link Here
143	<documentation>	160	<documentation>
144	the unique identifier of the view which will be added to the perspective layout.	161	the unique identifier of the view which will be added to the perspective layout.
145	</documentation>	162	</documentation>
		163	<appinfo>
		164	<meta.attribute kind="identifier" basedOn="org.eclipse.ui.views/view/@id"/>
		165	</appinfo>
146	</annotation>	166	</annotation>
147	</attribute>	167	</attribute>
148	<attribute name="relative" type="string">	168	<attribute name="relative" type="string">
Lines 150-155 Link Here
150	<documentation>	170	<documentation>
151	the unique identifier of a view which already exists in the perspective. This will be used as a reference point for placement of the view. The relationship between these two views is defined by <samp>relationship</samp>. Ignored if relationship is "fast".	171	the unique identifier of a view which already exists in the perspective. This will be used as a reference point for placement of the view. The relationship between these two views is defined by <samp>relationship</samp>. Ignored if relationship is "fast".
152	</documentation>	172	</documentation>
		173	<appinfo>
		174	<meta.attribute kind="identifier" basedOn="org.eclipse.ui.views/view/@id"/>
		175	</appinfo>
153	</annotation>	176	</annotation>
154	</attribute>	177	</attribute>
155	<attribute name="relationship" use="required">	178	<attribute name="relationship" use="required">
Lines 239-247 Link Here
239	</element>	262	</element>
240		263
241	<annotation>	264	<annotation>
242	<appInfo>	265	<appinfo>
243	<meta.section type="examples"/>	266	<meta.section type="examples"/>
244	</appInfo>	267	</appinfo>
245	<documentation>	268	<documentation>
246	The following is an example of a perspective extension (note the subelements and the way attributes are used):	269	The following is an example of a perspective extension (note the subelements and the way attributes are used):
247	<p>	270	<p>
Lines 277-303 Link Here
277	</annotation>	300	</annotation>
278		301
279	<annotation>	302	<annotation>
280	<appInfo>	303	<appinfo>
281	<meta.section type="apiInfo"/>	304	<meta.section type="apiInfo"/>
282	</appInfo>	305	</appinfo>
283	<documentation>	306	<documentation>
284	The items defined within the perspective extension are contributed to the initial contents of the target perspective. Following this, the user may remove any contribution or add others to a perspective from within the workbench user interface.	307	The items defined within the perspective extension are contributed to the initial contents of the target perspective. Following this, the user may remove any contribution or add others to a perspective from within the workbench user interface.
285	</documentation>	308	</documentation>
286	</annotation>	309	</annotation>
287		310
288	<annotation>	311
289	<appInfo>	312
290	<meta.section type="implementation"/>
291	</appInfo>
292	<documentation>
293
294	</documentation>
295	</annotation>
296		313
297	<annotation>	314	<annotation>
298	<appInfo>	315	<appinfo>
299	<meta.section type="copyright"/>	316	<meta.section type="copyright"/>
300	</appInfo>	317	</appinfo>
301	<documentation>	318	<documentation>
302	Copyright (c) 2002, 2007 IBM Corporation and others.<br>	319	Copyright (c) 2002, 2007 IBM Corporation and others.<br>
303	All rights reserved. This program and the accompanying materials are made	320	All rights reserved. This program and the accompanying materials are made

Lines 1-10 Link Here

(-)schema/bindings.exsd (-23 / +39 lines)
1	<?xml version='1.0' encoding='UTF-8'?>	1	<?xml version='1.0' encoding='UTF-8'?>
2	<!-- Schema file written by PDE -->	2	<!-- Schema file written by PDE -->
3	<schema targetNamespace="org.eclipse.ui">	3	<schema targetNamespace="org.eclipse.ui" xmlns="http://www.w3.org/2001/XMLSchema">
4	<annotation>	4	<annotation>
5	<appInfo>	5	<appinfo>
6	<meta.schema plugin="org.eclipse.ui" id="bindings" name="Bindings"/>	6	<meta.schema plugin="org.eclipse.ui" id="bindings" name="Bindings"/>
7	</appInfo>	7	</appinfo>
8	<documentation>	8	<documentation>
9	<p>	9	<p>
10	The <code>org.eclipse.ui.bindings</code> extension point is used to declare bindings and schemes. Schemes are sets of one or more bindings. A binding is a mapping between a certain group of conditions, some user input and a triggered command.	10	The <code>org.eclipse.ui.bindings</code> extension point is used to declare bindings and schemes. Schemes are sets of one or more bindings. A binding is a mapping between a certain group of conditions, some user input and a triggered command.
Lines 49-57 Link Here
49	<documentation>	49	<documentation>
50		50
51	</documentation>	51	</documentation>
52	<appInfo>	52	<appinfo>
53	<meta.attribute translatable="true"/>	53	<meta.attribute translatable="true"/>
54	</appInfo>	54	</appinfo>
55	</annotation>	55	</annotation>
56	</attribute>	56	</attribute>
57	</complexType>	57	</complexType>
Lines 59-67 Link Here
59		59
60	<element name="scheme">	60	<element name="scheme">
61	<annotation>	61	<annotation>
62	<appInfo>	62	<appinfo>
63	<meta.element labelAttribute="name"/>	63	<meta.element labelAttribute="name"/>
64	</appInfo>	64	</appinfo>
65	<documentation>	65	<documentation>
66	<p>	66	<p>
67	A scheme is a grouping of bindings that an end user can chose to use.	67	A scheme is a grouping of bindings that an end user can chose to use.
Lines 84-92 Link Here
84	<documentation>	84	<documentation>
85	The name for this scheme, as it should be displayed to an end-user. This value should be translated.	85	The name for this scheme, as it should be displayed to an end-user. This value should be translated.
86	</documentation>	86	</documentation>
87	<appInfo>	87	<appinfo>
88	<meta.attribute translatable="true"/>	88	<meta.attribute translatable="true"/>
89	</appInfo>	89	</appinfo>
90	</annotation>	90	</annotation>
91	</attribute>	91	</attribute>
92	<attribute name="description" type="string">	92	<attribute name="description" type="string">
Lines 94-102 Link Here
94	<documentation>	94	<documentation>
95	The description for this scheme, as it would be displayed to an end user. This value should be translated.	95	The description for this scheme, as it would be displayed to an end user. This value should be translated.
96	</documentation>	96	</documentation>
97	<appInfo>	97	<appinfo>
98	<meta.attribute translatable="true"/>	98	<meta.attribute translatable="true"/>
99	</appInfo>	99	</appinfo>
100	</annotation>	100	</annotation>
101	</attribute>	101	</attribute>
102	<attribute name="parentId" type="string">	102	<attribute name="parentId" type="string">
Lines 104-109 Link Here
104	<documentation>	104	<documentation>
105	The identifier for the parent of this scheme. If there is no parent, then do not specify this attribute.	105	The identifier for the parent of this scheme. If there is no parent, then do not specify this attribute.
106	</documentation>	106	</documentation>
		107	<appinfo>
		108	<meta.attribute kind="identifier" basedOn="org.eclipse.ui.bindings/scheme/@id"/>
		109	</appinfo>
107	</annotation>	110	</annotation>
108	</attribute>	111	</attribute>
109	</complexType>	112	</complexType>
Lines 111-119 Link Here
111		114
112	<element name="key">	115	<element name="key">
113	<annotation>	116	<annotation>
114	<appInfo>	117	<appinfo>
115	<meta.element labelAttribute="commandId"/>	118	<meta.element labelAttribute="commandId"/>
116	</appInfo>	119	</appinfo>
117	<documentation>	120	<documentation>
118	<p>A binding between some keyboard input and the triggering of a command.</p>	121	<p>A binding between some keyboard input and the triggering of a command.</p>
119	</documentation>	122	</documentation>
Lines 149-154 Link Here
149	<documentation>	152	<documentation>
150	The identifier of the scheme in which this key binding is active.	153	The identifier of the scheme in which this key binding is active.
151	</documentation>	154	</documentation>
		155	<appinfo>
		156	<meta.attribute kind="identifier" basedOn="org.eclipse.ui.bindings/scheme/@id"/>
		157	</appinfo>
152	</annotation>	158	</annotation>
153	</attribute>	159	</attribute>
154	<attribute name="contextId" type="string" use="default" value="org.eclipse.ui.contexts.window">	160	<attribute name="contextId" type="string" use="default" value="org.eclipse.ui.contexts.window">
Lines 156-161 Link Here
156	<documentation>	162	<documentation>
157	The identifier of the context in which this key binding is active. Please see the <code>org.eclipse.ui.contexts</code> extension point. If this is not specified, then it defaults to <code>org.eclipse.ui.contexts.window</code>.	163	The identifier of the context in which this key binding is active. Please see the <code>org.eclipse.ui.contexts</code> extension point. If this is not specified, then it defaults to <code>org.eclipse.ui.contexts.window</code>.
158	</documentation>	164	</documentation>
		165	<appinfo>
		166	<meta.attribute kind="identifier" basedOn="org.eclipse.ui.contexts/context/@id"/>
		167	</appinfo>
159	</annotation>	168	</annotation>
160	</attribute>	169	</attribute>
161	<attribute name="commandId" type="string">	170	<attribute name="commandId" type="string">
Lines 168-173 Link Here
168	If no command identifier is specified, this is a deletion marker. This means that any binding in the same context with the same sequence, platform and locale will become inactive when this binding becomes active. If the platform or locale on a deletion is not specified, then it matches any platform or locale.	177	If no command identifier is specified, this is a deletion marker. This means that any binding in the same context with the same sequence, platform and locale will become inactive when this binding becomes active. If the platform or locale on a deletion is not specified, then it matches any platform or locale.
169	</p>	178	</p>
170	</documentation>	179	</documentation>
		180	<appinfo>
		181	<meta.attribute kind="identifier" basedOn="org.eclipse.ui.commands/command/@id"/>
		182	</appinfo>
171	</annotation>	183	</annotation>
172	</attribute>	184	</attribute>
173	<attribute name="platform" type="string">	185	<attribute name="platform" type="string">
Lines 189-197 Link Here
189		201
190	<element name="parameter">	202	<element name="parameter">
191	<annotation>	203	<annotation>
192	<appInfo>	204	<appinfo>
193	<meta.element labelAttribute="id"/>	205	<meta.element labelAttribute="id"/>
194	</appInfo>	206	</appinfo>
195	<documentation>	207	<documentation>
196	A parameter name and value that should be passed to the command when it is executed. This allows for the command to be qualified in some way. For example, a "Show View" command might accept the view id as a parameter.	208	A parameter name and value that should be passed to the command when it is executed. This allows for the command to be qualified in some way. For example, a "Show View" command might accept the view id as a parameter.
197	</documentation>	209	</documentation>
Lines 202-207 Link Here
202	<documentation>	214	<documentation>
203	The parameter name as understood by the command. This is not a translatable name, but the key to name-value map.	215	The parameter name as understood by the command. This is not a translatable name, but the key to name-value map.
204	</documentation>	216	</documentation>
		217	<appinfo>
		218	<meta.attribute kind="identifier" basedOn="org.eclipse.ui.commands/command/commandParameter/@id"/>
		219	</appinfo>
205	</annotation>	220	</annotation>
206	</attribute>	221	</attribute>
207	<attribute name="value" type="string">	222	<attribute name="value" type="string">
Lines 215-232 Link Here
215	</element>	230	</element>
216		231
217	<annotation>	232	<annotation>
218	<appInfo>	233	<appinfo>
219	<meta.section type="since"/>	234	<meta.section type="since"/>
220	</appInfo>	235	</appinfo>
221	<documentation>	236	<documentation>
222	3.1	237	3.1
223	</documentation>	238	</documentation>
224	</annotation>	239	</annotation>
225		240
226	<annotation>	241	<annotation>
227	<appInfo>	242	<appinfo>
228	<meta.section type="examples"/>	243	<meta.section type="examples"/>
229	</appInfo>	244	</appinfo>
230	<documentation>	245	<documentation>
231	<pre>	246	<pre>
232	<extension	247	<extension
Lines 251-259 Link Here
251	</annotation>	266	</annotation>
252		267
253	<annotation>	268	<annotation>
254	<appInfo>	269	<appinfo>
255	<meta.section type="apiInfo"/>	270	<meta.section type="apiInfo"/>
256	</appInfo>	271	</appinfo>
257	<documentation>	272	<documentation>
258	<p>	273	<p>
259	There is no public API for defining bindings. To try to achieve stability for the user, bindings are only defined through the extension points. If you are an RCP application, you should be able to override this behaviour in the <code>WorkbenchAdvisor</code>.	274	There is no public API for defining bindings. To try to achieve stability for the user, bindings are only defined through the extension points. If you are an RCP application, you should be able to override this behaviour in the <code>WorkbenchAdvisor</code>.
Lines 265-274 Link Here
265	</annotation>	280	</annotation>
266		281
267		282
		283
268	<annotation>	284	<annotation>
269	<appInfo>	285	<appinfo>
270	<meta.section type="copyright"/>	286	<meta.section type="copyright"/>
271	</appInfo>	287	</appinfo>
272	<documentation>	288	<documentation>
273	Copyright (c) 2005,2007 IBM Corporation and others.<br>	289	Copyright (c) 2005,2007 IBM Corporation and others.<br>
274	All rights reserved. This program and the accompanying materials are made	290	All rights reserved. This program and the accompanying materials are made

Lines 1-10 Link Here

(-)schema/contexts.exsd (-25 / +21 lines)
1	<?xml version='1.0' encoding='UTF-8'?>	1	<?xml version='1.0' encoding='UTF-8'?>
2	<!-- Schema file written by PDE -->	2	<!-- Schema file written by PDE -->
3	<schema targetNamespace="org.eclipse.ui">	3	<schema targetNamespace="org.eclipse.ui" xmlns="http://www.w3.org/2001/XMLSchema">
4	<annotation>	4	<annotation>
5	<appInfo>	5	<appinfo>
6	<meta.schema plugin="org.eclipse.ui" id="contexts" name="Contexts"/>	6	<meta.schema plugin="org.eclipse.ui" id="contexts" name="Contexts"/>
7	</appInfo>	7	</appinfo>
8	<documentation>	8	<documentation>
9	<p>	9	<p>
10	The <code>org.eclipse.ui.contexts</code> extension point is used to declare contexts and associated elements.	10	The <code>org.eclipse.ui.contexts</code> extension point is used to declare contexts and associated elements.
Lines 29-37 Link Here
29	<documentation>	29	<documentation>
30	An optional name of the extension instance.	30	An optional name of the extension instance.
31	</documentation>	31	</documentation>
32	<appInfo>	32	<appinfo>
33	<meta.attribute translatable="true"/>	33	<meta.attribute translatable="true"/>
34	</appInfo>	34	</appinfo>
35	</annotation>	35	</annotation>
36	</attribute>	36	</attribute>
37	<attribute name="point" type="string" use="required">	37	<attribute name="point" type="string" use="required">
Lines 56-64 Link Here
56	<documentation>	56	<documentation>
57	A translatable short description of this context for display in the UI.	57	A translatable short description of this context for display in the UI.
58	</documentation>	58	</documentation>
59	<appInfo>	59	<appinfo>
60	<meta.attribute translatable="true"/>	60	<meta.attribute translatable="true"/>
61	</appInfo>	61	</appinfo>
62	</annotation>	62	</annotation>
63	</attribute>	63	</attribute>
64	<attribute name="id" type="string" use="required">	64	<attribute name="id" type="string" use="required">
Lines 73-81 Link Here
73	<documentation>	73	<documentation>
74	The translatable name of this context for display in the UI.	74	The translatable name of this context for display in the UI.
75	</documentation>	75	</documentation>
76	<appInfo>	76	<appinfo>
77	<meta.attribute translatable="true"/>	77	<meta.attribute translatable="true"/>
78	</appInfo>	78	</appinfo>
79	</annotation>	79	</annotation>
80	</attribute>	80	</attribute>
81	<attribute name="parentId" type="string">	81	<attribute name="parentId" type="string">
Lines 83-97 Link Here
83	<documentation>	83	<documentation>
84	The unique identifier of the parent of this context.	84	The unique identifier of the parent of this context.
85	</documentation>	85	</documentation>
		86	<appinfo>
		87	<meta.attribute kind="identifier" basedOn="org.eclipse.ui.contexts/context/@id"/>
		88	</appinfo>
86	</annotation>	89	</annotation>
87	</attribute>	90	</attribute>
88	</complexType>	91	</complexType>
89	</element>	92	</element>
90		93
91	<annotation>	94	<annotation>
92	<appInfo>	95	<appinfo>
93	<meta.section type="since"/>	96	<meta.section type="since"/>
94	</appInfo>	97	</appinfo>
95	<documentation>	98	<documentation>
96	<p>	99	<p>
97	3.0	100	3.0
Lines 100-108 Link Here
100	</annotation>	103	</annotation>
101		104
102	<annotation>	105	<annotation>
103	<appInfo>	106	<appinfo>
104	<meta.section type="examples"/>	107	<meta.section type="examples"/>
105	</appInfo>	108	</appinfo>
106	<documentation>	109	<documentation>
107	<p>	110	<p>
108	The <code>plugin.xml</code> file in the <code>org.eclipse.ui</code> plugin makes use of the <code>org.eclipse.ui.contexts</code> extension point.	111	The <code>plugin.xml</code> file in the <code>org.eclipse.ui</code> plugin makes use of the <code>org.eclipse.ui.contexts</code> extension point.
Lines 111-119 Link Here
111	</annotation>	114	</annotation>
112		115
113	<annotation>	116	<annotation>
114	<appInfo>	117	<appinfo>
115	<meta.section type="apiInfo"/>	118	<meta.section type="apiInfo"/>
116	</appInfo>	119	</appinfo>
117	<documentation>	120	<documentation>
118	<p>	121	<p>
119	In general, it is preferrably to declare all contexts statically (in <code>plugin.xml</code>). This is so that users can use them in key bindings. However, it is possible to declare contexts at run-time. To do this, retrieve the <code>org.eclipse.ui.commands.IContextService</code> from a workbench component, call <code>getContext(contextId)</code> and then call <code>Context#define(...)</code>.	122	In general, it is preferrably to declare all contexts statically (in <code>plugin.xml</code>). This is so that users can use them in key bindings. However, it is possible to declare contexts at run-time. To do this, retrieve the <code>org.eclipse.ui.commands.IContextService</code> from a workbench component, call <code>getContext(contextId)</code> and then call <code>Context#define(...)</code>.
Lines 122-140 Link Here
122	</documentation>	125	</documentation>
123	</annotation>	126	</annotation>
124		127
125	<annotation>	128
126	<appInfo>
127	<meta.section type="implementation"/>
128	</appInfo>
129	<documentation>
130
131	</documentation>
132	</annotation>
133		129
134	<annotation>	130	<annotation>
135	<appInfo>	131	<appinfo>
136	<meta.section type="copyright"/>	132	<meta.section type="copyright"/>
137	</appInfo>	133	</appinfo>
138	<documentation>	134	<documentation>
139	Copyright (c) 2000, 2007 IBM Corporation and others.<br>	135	Copyright (c) 2000, 2007 IBM Corporation and others.<br>
140	All rights reserved. This program and the accompanying materials are made	136	All rights reserved. This program and the accompanying materials are made

Lines 1-10 Link Here

(-)schema/commandImages.exsd (-21 / +25 lines)
1	<?xml version='1.0' encoding='UTF-8'?>	1	<?xml version='1.0' encoding='UTF-8'?>
2	<!-- Schema file written by PDE -->	2	<!-- Schema file written by PDE -->
3	<schema targetNamespace="org.eclipse.ui">	3	<schema targetNamespace="org.eclipse.ui" xmlns="http://www.w3.org/2001/XMLSchema">
4	<annotation>	4	<annotation>
5	<appInfo>	5	<appinfo>
6	<meta.schema plugin="org.eclipse.ui" id="commandImages" name="Command Images"/>	6	<meta.schema plugin="org.eclipse.ui" id="commandImages" name="Command Images"/>
7	</appInfo>	7	</appinfo>
8	<documentation>	8	<documentation>
9	<p>	9	<p>
10	The images extension point provides a way of linking different types of images and icons to a particular command. These images can be used, as appropriate, wherever the command appears in the user interface. To accommodate some boundary cases (e.g., tool bar drop-down items), it is possible to group the images for a particular commands into "styles". These styles can then be specifically requested when a command is to be displayed.	10	The images extension point provides a way of linking different types of images and icons to a particular command. These images can be used, as appropriate, wherever the command appears in the user interface. To accommodate some boundary cases (e.g., tool bar drop-down items), it is possible to group the images for a particular commands into "styles". These styles can then be specifically requested when a command is to be displayed.
Lines 39-47 Link Here
39	<documentation>	39	<documentation>
40		40
41	</documentation>	41	</documentation>
42	<appInfo>	42	<appinfo>
43	<meta.attribute translatable="true"/>	43	<meta.attribute translatable="true"/>
44	</appInfo>	44	</appinfo>
45	</annotation>	45	</annotation>
46	</attribute>	46	</attribute>
47	</complexType>	47	</complexType>
Lines 49-57 Link Here
49		49
50	<element name="image">	50	<element name="image">
51	<annotation>	51	<annotation>
52	<appInfo>	52	<appinfo>
53	<meta.element labelAttribute="commandId"/>	53	<meta.element labelAttribute="commandId"/>
54	</appInfo>	54	</appinfo>
55	<documentation>	55	<documentation>
56	The images to associate with a particular command.	56	The images to associate with a particular command.
57	</documentation>	57	</documentation>
Lines 62-67 Link Here
62	<documentation>	62	<documentation>
63	The identifier of the command with which the images should be associated.	63	The identifier of the command with which the images should be associated.
64	</documentation>	64	</documentation>
		65	<appinfo>
		66	<meta.attribute kind="identifier" basedOn="org.eclipse.ui.commands/command/@id"/>
		67	</appinfo>
65	</annotation>	68	</annotation>
66	</attribute>	69	</attribute>
67	<attribute name="icon" type="string" use="required">	70	<attribute name="icon" type="string" use="required">
Lines 69-77 Link Here
69	<documentation>	72	<documentation>
70	The path to the icon which should be used in the default case. This will appear when the icon is enabled and mouse is not hovering over it. It will also be used in any situation where such a more specific icon is not available.	73	The path to the icon which should be used in the default case. This will appear when the icon is enabled and mouse is not hovering over it. It will also be used in any situation where such a more specific icon is not available.
71	</documentation>	74	</documentation>
72	<appInfo>	75	<appinfo>
73	<meta.attribute kind="resource"/>	76	<meta.attribute kind="resource"/>
74	</appInfo>	77	</appinfo>
75	</annotation>	78	</annotation>
76	</attribute>	79	</attribute>
77	<attribute name="disabledIcon" type="string">	80	<attribute name="disabledIcon" type="string">
Lines 79-87 Link Here
79	<documentation>	82	<documentation>
80	The icon to display when the command is disabled.	83	The icon to display when the command is disabled.
81	</documentation>	84	</documentation>
82	<appInfo>	85	<appinfo>
83	<meta.attribute kind="resource"/>	86	<meta.attribute kind="resource"/>
84	</appInfo>	87	</appinfo>
85	</annotation>	88	</annotation>
86	</attribute>	89	</attribute>
87	<attribute name="hoverIcon" type="string">	90	<attribute name="hoverIcon" type="string">
Lines 89-97 Link Here
89	<documentation>	92	<documentation>
90	The icon to display when the user is hovering over the command.	93	The icon to display when the user is hovering over the command.
91	</documentation>	94	</documentation>
92	<appInfo>	95	<appinfo>
93	<meta.attribute kind="resource"/>	96	<meta.attribute kind="resource"/>
94	</appInfo>	97	</appinfo>
95	</annotation>	98	</annotation>
96	</attribute>	99	</attribute>
97	<attribute name="style" type="string">	100	<attribute name="style" type="string">
Lines 105-122 Link Here
105	</element>	108	</element>
106		109
107	<annotation>	110	<annotation>
108	<appInfo>	111	<appinfo>
109	<meta.section type="since"/>	112	<meta.section type="since"/>
110	</appInfo>	113	</appinfo>
111	<documentation>	114	<documentation>
112	3.2	115	3.2
113	</documentation>	116	</documentation>
114	</annotation>	117	</annotation>
115		118
116	<annotation>	119	<annotation>
117	<appInfo>	120	<appinfo>
118	<meta.section type="examples"/>	121	<meta.section type="examples"/>
119	</appInfo>	122	</appinfo>
120	<documentation>	123	<documentation>
121	<pre>	124	<pre>
122	<extension	125	<extension
Lines 138-146 Link Here
138	</annotation>	141	</annotation>
139		142
140	<annotation>	143	<annotation>
141	<appInfo>	144	<appinfo>
142	<meta.section type="apiInfo"/>	145	<meta.section type="apiInfo"/>
143	</appInfo>	146	</appinfo>
144	<documentation>	147	<documentation>
145	<p>	148	<p>
146	Within the workbench, it is possible to get images for commands using the <code>org.eclipse.ui.commands.ICommandImageService</code> interface. This interface can be retrieved from supporting workbench objects, such as <code>IWorkbench</code> itself, the <code>IWorkbenchWindow</code>, or the <code>IWorkbenchPartSite</code>. To retrieve the service, you would make a call like <code>workbench.getService(ICommandImageService.class)</code>.	149	Within the workbench, it is possible to get images for commands using the <code>org.eclipse.ui.commands.ICommandImageService</code> interface. This interface can be retrieved from supporting workbench objects, such as <code>IWorkbench</code> itself, the <code>IWorkbenchWindow</code>, or the <code>IWorkbenchPartSite</code>. To retrieve the service, you would make a call like <code>workbench.getService(ICommandImageService.class)</code>.
Lines 149-158 Link Here
149	</annotation>	152	</annotation>
150		153
151		154
		155
152	<annotation>	156	<annotation>
153	<appInfo>	157	<appinfo>
154	<meta.section type="copyright"/>	158	<meta.section type="copyright"/>
155	</appInfo>	159	</appinfo>
156	<documentation>	160	<documentation>
157	Copyright (c) 2005,2007 IBM Corporation and others.<br>	161	Copyright (c) 2005,2007 IBM Corporation and others.<br>
158	All rights reserved. This program and the accompanying materials are made	162	All rights reserved. This program and the accompanying materials are made