You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@directory.apache.org by pa...@apache.org on 2007/12/27 18:45:01 UTC
svn commit: r607099 [15/25] - in
/directory/studio/branches/studio-eclipse-3.3: dependencies/eclipse/3.3.1/
dependencies/eclipse/3.3.1/features/
dependencies/eclipse/3.3.1/features/org.eclipse.rcp_3.3.2.R33x_r20071022-8y8eE9CEV3FspP8HJrY1M2dS/
dependen...
Added: directory/studio/branches/studio-eclipse-3.3/dependencies/eclipse/3.3.1/plugins/org.eclipse.rcp.source_3.3.2.R33x_r20071022-8y8eE9CEV3FspP8HJrY1M2dS/src/org.eclipse.ui_3.3.1.M20070910-0800b/schema/menus.exsd
URL: http://svn.apache.org/viewvc/directory/studio/branches/studio-eclipse-3.3/dependencies/eclipse/3.3.1/plugins/org.eclipse.rcp.source_3.3.2.R33x_r20071022-8y8eE9CEV3FspP8HJrY1M2dS/src/org.eclipse.ui_3.3.1.M20070910-0800b/schema/menus.exsd?rev=607099&view=auto
==============================================================================
--- directory/studio/branches/studio-eclipse-3.3/dependencies/eclipse/3.3.1/plugins/org.eclipse.rcp.source_3.3.2.R33x_r20071022-8y8eE9CEV3FspP8HJrY1M2dS/src/org.eclipse.ui_3.3.1.M20070910-0800b/schema/menus.exsd (added)
+++ directory/studio/branches/studio-eclipse-3.3/dependencies/eclipse/3.3.1/plugins/org.eclipse.rcp.source_3.3.2.R33x_r20071022-8y8eE9CEV3FspP8HJrY1M2dS/src/org.eclipse.ui_3.3.1.M20070910-0800b/schema/menus.exsd Thu Dec 27 09:44:07 2007
@@ -0,0 +1,945 @@
+<?xml version='1.0' encoding='UTF-8'?>
+<!-- Schema file written by PDE -->
+<schema targetNamespace="org.eclipse.ui">
+<annotation>
+ <appInfo>
+ <meta.schema plugin="org.eclipse.ui" id="menus" name="Menus"/>
+ </appInfo>
+ <documentation>
+ <p>
+This extension point allows the plug-in developer to add (contribute) a variety of custom additions to the eclipse framework:
+<ul>
+ <li>Main Menu</li>
+ <li>Main Toolbars</li>
+ <li>View Menus/Toolbars:
+ <ul>
+ <li>View Dropdown Menu</li>
+ <li>View Toolbar</li>
+ <li>Context Menu(s)</li>
+ </ul>
+ </li>
+ <li>Trim</li>
+</ul>
+</p>
+<p>
+It provides a common implementation for and acts as a replacement of the following (legacy) eclipse extension points:
+<ul>
+<li>org.eclipse.ui.ActionSets</li>
+<li>org.eclipse.ui.EditorActions</li>
+<li>org.eclipse.ui.popupMenus (including 'objectContributions')</li>
+<li>org.eclipse.ui.viewActions</li>
+</ul>
+</p>
+<p>
+The general strategy for this mechanism is to separate the 'location' where the contributions should be inserted from the visibility and enablement state of the element. Each conribution first defines its insertion location through a Menu 'URI', a string (loosely) formatted according to the jave.net.URI format:
+</p><p>
+<b>"[Scheme]:[ID]?[ArgList]"</b>
+<ul>
+<li><b>Scheme</b> - The 'type' of the UI component into which the contributions will be added. It may be either "menu", "popup" or "toolbar". While 'popup' is indeed a form of menu it is provided to allow a distinction between a view's 'chevron' menu (for which we use the "menu" scheme) and its default context menu which, by convention, should be registered using the "popup" scheme.</li>
+<li><b>ID</b> - This is the id of menu or toolbar into which the contributions should be added. By convention views should use their view id as the id of the root of their chevron and default popup menu. Note that there is no explicit distinction between contributions supporting editors and 'normal' contributions into the Menu Menu or Toolbar; both global contributions and editor contributions would use the "org.eclipse.ui.main.menu" id or "org.eclipse.ui.main.toolbar". A special id used with popup:, "org.eclipse.ui.any.popup", is reserved to handle contributions which are candidates to appear on any (top level) context menu. Note that these contributions are expected to implement a 'visibleWhen' expression sufficient to limit their visibility to appropriate menus</li>
+<li><b>Query</b> - This field allows fine-grained definition of the specific location <i>within</i> a given menu. It has the form "[placement]=[id]" where placement is one of "before" or "after" and the id is expected to be the id of some IContributionItem in the menu.</li>
+</ul>
+<p>
+This will define the location at which the contributions will appear in the eclipse UI. Once the insertion point has been defined the rest of the contributions describe the UI elements that will be added at that location. Each element supports a 'visibleWhen' expression that determines at run time whether a particular item should appear in the menu based on the system's current state (selection, active view/editor, context...). See <code>org.eclipse.ui.ISources</code> for a list of currently
+supported variables.
+</p>
+ </documentation>
+ </annotation>
+
+ <include schemaLocation="schema://org.eclipse.core.expressions/schema/expressionLanguage.exsd"/>
+
+ <element name="extension">
+ <complexType>
+ <sequence>
+ <element ref="group" minOccurs="0" maxOccurs="unbounded"/>
+ <element ref="widget" minOccurs="0" maxOccurs="unbounded"/>
+ <element ref="menuContribution" minOccurs="0" maxOccurs="unbounded"/>
+ </sequence>
+ <attribute name="point" type="string" use="required">
+ <annotation>
+ <documentation>
+ org.eclipse.ui.menus
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="id" type="string">
+ <annotation>
+ <documentation>
+ An optional identifier of the extension instance.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="name" type="string">
+ <annotation>
+ <documentation>
+ An optional name of the extension instance.
+ </documentation>
+ <appInfo>
+ <meta.attribute translatable="true"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="group">
+ <annotation>
+ <appInfo>
+ <meta.element deprecated="true"/>
+ </appInfo>
+ <documentation>
+ <p>
+A logical group. It can either be visible (e.g., separators are drawn before and after, as appropriate) or invisible. By default, logicial groups are visible.
+</p>
+<p>
+A group can contain menus, items and other groups.
+</p>
+<p>
+This element is deprecated. Groups are now expressed as id'd 'separator' elements. The menu insertion URI can be used to define an insertion point either 'before' or 'after' <b>any</b> id'd element and placing it after the separator is the same as contibuting it to the group. </p>
+<p>
+See the documentation for the 'locationURI' attribute of 'menuAddition' for more details on how to define insertion points adn how they relate to the menu structure.
+</p>
+ </documentation>
+ </annotation>
+ <complexType>
+ <sequence>
+ <element ref="location" minOccurs="0" maxOccurs="unbounded"/>
+ </sequence>
+ <attribute name="id" type="string" use="required">
+ <annotation>
+ <documentation>
+ A unique identifier for this group. It is recommended that the identifier be prefixed by the plug-in name, to guarantee uniqueness. For example, a group contributed by <code>org.eclipse.ui</code> might be called <code>org.eclipse.ui.group1</code>.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="separatorsVisible" type="boolean" use="default" value="true">
+ <annotation>
+ <documentation>
+ Whether separators should be drawn around the group. The workbench will take care of deciding whether a separator needs to be drawn at the top or bottom -- accounting for the top and bottom of the menu and duplicate separators. By default, separators are visible.
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="widget">
+ <annotation>
+ <appInfo>
+ <meta.element deprecated="true"/>
+ </appInfo>
+ <documentation>
+ A menu or trim element that is given direct access to the widgets. For example, this can be used to render a combo box. <b>NOTE:</b> If a widget element becomes visible in the user interface, this will lead to plug-in loading. <strong>Use this element with caution, as it can cause performance problems.</strong>
+ When used as trim the widget will only cause the plug-in to load when it becomes visible in the UI.
+<p>
+<b>NOTE:</b> This element is deprecated. Clients should contribute a Toolbar to one of the trim areas and place a control contribution inside it. See the Trim Contribution example for details.
+</p>
+ </documentation>
+ </annotation>
+ <complexType>
+ <sequence>
+ <element ref="location" minOccurs="0" maxOccurs="unbounded"/>
+ <element ref="class" minOccurs="0" maxOccurs="1"/>
+ <element ref="visibleWhen" minOccurs="0" maxOccurs="1"/>
+ <element ref="layout" minOccurs="0" maxOccurs="1"/>
+ </sequence>
+ <attribute name="id" type="string" use="required">
+ <annotation>
+ <documentation>
+ A unique identifier for this widget. It is recommended that the identifier be prefixed by the plug-in name, to guarantee uniqueness. For example, a widget contributed by <code>org.eclipse.ui</code> might be called <code>org.eclipse.ui.widget1</code>.
+<p>
+If defined then it can be used as a reference in the Query part of the location defining whether the additions are to go before or after this element (or at the end of the logical group containing this element using the 'endof' value).
+</p>
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="class" type="string" use="required">
+ <annotation>
+ <documentation>
+ This class is loaded to fill the appropriate spot in the menu or trim when it shows. While, strictly speaking, this class must implement <code>IWorkbenchWidget</code> you should use the default implementation; <code>AbstractWorkbenchTrimWidget</code> as the base from which to derive your widget implementation. This implementation handles the 'init' method and caches the result for use through its <code>getWorkbenchWindow</code> method.
+ </documentation>
+ <appInfo>
+ <meta.attribute kind="java" basedOn="org.eclipse.ui.menus.IWorkbenchWidget"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="layout">
+ <annotation>
+ <appInfo>
+ <meta.element deprecated="true"/>
+ </appInfo>
+ <documentation>
+ This element can be used to specify various layout options for elements added into <code>trim</code> locations.
+ </documentation>
+ </annotation>
+ <complexType>
+ <attribute name="fillMajor" type="boolean">
+ <annotation>
+ <documentation>
+ The widget will stretch to use up any additional space available along its <b>major</b> dimension in the group's area (i.e. it will use the extra horizontal space for horizontally oriented trim areas). Default is <code>false</code>.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="fillMinor" type="boolean">
+ <annotation>
+ <documentation>
+ The widget will stretch to use up any additional space available along its <b>minor</b> dimension in the group's area (i.e. it will use the extra vertical space for horizontally oriented trim areas). Default is <code>false</code>.
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="location">
+ <annotation>
+ <appInfo>
+ <meta.element deprecated="true"/>
+ </appInfo>
+ <documentation>
+ A location in which a <code>menu</code>, <code>group</code>, <code>item</code> or <code>widget</code> can appear. This element is used to control location-specific information.
+<p>
+This element is deprecated. Users of this extension point should now define the location at which their contributions should appear using the 'locationURI' specification.
+</p>
+ </documentation>
+ </annotation>
+ <complexType>
+ <sequence>
+ <element ref="order" minOccurs="0" maxOccurs="1"/>
+ <choice>
+ <element ref="bar"/>
+ <element ref="part"/>
+ <element ref="popup"/>
+ </choice>
+ </sequence>
+ <attribute name="mnemonic" type="string">
+ <annotation>
+ <documentation>
+ The mnemonic that should be associated with this element in the given location. A mnemonic should be a single character.
+ </documentation>
+ <appInfo>
+ <meta.attribute translatable="true" deprecated="true"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ <attribute name="imageStyle" type="string">
+ <annotation>
+ <documentation>
+ The image style to associate with this location. It is possible for commands to have different styles of images associated with them. For example, a different icon could be selected for the tool bar and for the menu. This is especially important for developers using drop-down tool items in the tool bar, as they may wish to display an icon more appropriate for the drop-down.
+ </documentation>
+ <appInfo>
+ <meta.attribute deprecated="true"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="bar">
+ <annotation>
+ <appInfo>
+ <meta.element deprecated="true"/>
+ </appInfo>
+ <documentation>
+ A leaf element within a location. This can be the menu bar or the trim area. If unqualified, this indicates the top-level menu bar or trim. If this is qualified with a <code>part</code> element, then this indicates that part's menu or trim.
+ </documentation>
+ </annotation>
+ <complexType>
+ <attribute name="type" use="required">
+ <annotation>
+ <documentation>
+ <p>
+<b>NOTE:</b> This is not only deprecated but has no value in the current implementation (the only acceptable value is 'trim' which is the default. You may safely remove this from any declarations.
+</p>
+<p>
+What type of bar to contribute to. This can be <code>menu</code> or <code>trim</code>. If contributing to the menu, then the item will be parented to some widget structure. In general, this means using widget elements does not make much sense, and an icon for an item's command is not strictly necessary. The default value is <code>menu</code>.
+</p>
+<p>
+<p>If contributing to the <code>trim</code>, then the bar will generally not require a command or an icon, it should be filled with a widget that displays the trim information.
+<p>
+Within the trim, the workbench defines five general groups which correspond to various positions around the window:
+<ul>
+<li><b>command1</b> - This represents the (horizontal) trim area that the main toolbars are placed into.</li>
+<li><b>command2</b> - This represents the (horizontal) trim area that the Perspective Switcher is in by default.</li>
+<li><b>vertical1</b> - This represents the (vertical) trim area that is on the left side when the text direction is Left->Right and on the right side for Right->Left text.</li>
+<li><b>vertical2</b> - This represents the (vertical) trim area that is on the opposite side of the workbench from <code>vertical1</code>.</li>
+<li><b>status</b> - This represents the (horizontal) trim area along the bottom edge of the workbench.</li>
+</ul>
+By positioning the trim contribution within or with respect to these groups, the position is inferred by the workbench.
+</p>
+ </documentation>
+ <appInfo>
+ <meta.attribute deprecated="true"/>
+ </appInfo>
+ </annotation>
+ <simpleType>
+ <restriction base="string">
+ <enumeration value="menu">
+ </enumeration>
+ <enumeration value="trim">
+ </enumeration>
+ </restriction>
+ </simpleType>
+ </attribute>
+ <attribute name="path" type="string">
+ <annotation>
+ <documentation>
+ This represents the id of a group that the widget is to be placed into.
+ </documentation>
+ <appInfo>
+ <meta.attribute deprecated="true"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="class">
+ <annotation>
+ <documentation>
+ A class element supporting the executable extension parsing syntax for both <code>widget</code> and <code>dynamic</code> elements.
+ </documentation>
+ </annotation>
+ <complexType>
+ <sequence>
+ <element ref="parameter" minOccurs="0" maxOccurs="unbounded"/>
+ </sequence>
+ <attribute name="class" type="string" use="required">
+ <annotation>
+ <documentation>
+ The class to load as an <code>IExecutableExtension</code>.
+ </documentation>
+ <appInfo>
+ <meta.attribute kind="java"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="visibleWhen">
+ <annotation>
+ <documentation>
+ A core Expression that ontrols the visibility of the given element.
+ </documentation>
+ </annotation>
+ <complexType>
+ <choice minOccurs="0" maxOccurs="1">
+ <element ref="not"/>
+ <element ref="or"/>
+ <element ref="and"/>
+ <element ref="instanceof"/>
+ <element ref="test"/>
+ <element ref="systemTest"/>
+ <element ref="equals"/>
+ <element ref="count"/>
+ <element ref="with"/>
+ <element ref="resolve"/>
+ <element ref="adapt"/>
+ <element ref="iterate"/>
+ <element ref="reference"/>
+ </choice>
+ <attribute name="checkEnabled" type="boolean" use="default" value="false">
+ <annotation>
+ <documentation>
+ If this attribute is set to <code>true</code>, then there should be no sub-elements. This just checks the enabled state of the command, and makes the corresponding element visible if the command is enabled.
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="part">
+ <annotation>
+ <appInfo>
+ <meta.element deprecated="true"/>
+ </appInfo>
+ <documentation>
+ <p>
+An element within a location. This qualifies the location to refer to a particular workbench part. This can be either a view or an editor. The qualification can use either the class name of the part (including inheritance), or it can refer to the identifier for the view or editor.
+</p>
+<p>
+Only one of <code>id</code> and <code>class</code> can be specified.
+</p>
+<p>
+<b>NOTE:</b> This element is deprecated. It had been used for a previous technique for adding trim elements. Instead, clients should contribute a Toolbar to one of the trim areas and place a control contribution inside it. See the Trim Contribution example for details.
+</p>
+ </documentation>
+ </annotation>
+ <complexType>
+ <choice>
+ <element ref="popup"/>
+ <element ref="bar"/>
+ </choice>
+ <attribute name="id" type="string">
+ <annotation>
+ <documentation>
+ The identifier of the view or editor.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="class" type="string">
+ <annotation>
+ <documentation>
+ The class of the part. This can be a superclass, interface or superinterface of the part, and it will still match.
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="parameter">
+ <annotation>
+ <documentation>
+ A parameter to either an executable extension or a command -- depending on where it appears in the extension.
+ </documentation>
+ </annotation>
+ <complexType>
+ <attribute name="name" type="string" use="required">
+ <annotation>
+ <documentation>
+ The name is either the name of the parameter to pass to the executable extension, or the identifier of the parameter for the command.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="value" type="string" use="required">
+ <annotation>
+ <documentation>
+ The value to pass for this parameter.
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="order">
+ <annotation>
+ <appInfo>
+ <meta.element deprecated="true"/>
+ </appInfo>
+ <documentation>
+ <b>NOTE:</b> This element is deprecated in favor of using the 'locationURI' to specify the location at which contributions should be placed.
+<p>
+Controls the position of a widget within a particular group.
+</p>
+ </documentation>
+ </annotation>
+ <complexType>
+ <attribute name="position" use="required">
+ <annotation>
+ <documentation>
+ <p>
+This attribute accepts the following values: <code>start</code> (put the element at the beginning of the container); <code>end</code> (put the element at the end of its container); <code>after</code> (put the element after the sibling element whose id matches <code>ref</code>); and, <code>before</code> (put the element before the sibling element whose id matches <code>ref</code>). Relative ordering can be applied to any type of menu element.
+</p>
+<p>
+In the event of conflicts, Eclipse will chose an arbitrary order. The only guarantee is that, in the event of a conflict, the order will remain the same as long as the following holds:
+</p>
+<ul>
+<li>The Eclipse version is the same.</li>
+<li>The list of elements is the same (i.e., no dynamic elements, no plug-ins added or removed).</li>
+</ul>
+ </documentation>
+ </annotation>
+ <simpleType>
+ <restriction base="string">
+ <enumeration value="start">
+ </enumeration>
+ <enumeration value="end">
+ </enumeration>
+ <enumeration value="before">
+ </enumeration>
+ <enumeration value="after">
+ </enumeration>
+ </restriction>
+ </simpleType>
+ </attribute>
+ <attribute name="relativeTo" type="string">
+ <annotation>
+ <documentation>
+ The identifier of the element to which this position is relative. This value is required if the <code>position</code> is <code>before</code> or <code>after</code>.
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="popup">
+ <annotation>
+ <appInfo>
+ <meta.element deprecated="true"/>
+ </appInfo>
+ <documentation>
+ Part of a location. It indicates that the menu, group, item or widget should appear in the popup menu.
+<p>
+<p>
+<b>NOTE:</b> This element is deprecated. It had been used for a previous technique for adding trim elements. Instead, clients should contribute a Toolbar to one of the trim areas and place a control contribution inside it. See the Trim Contribution example for details.
+</p>
+ </documentation>
+ </annotation>
+ <complexType>
+ <attribute name="id" type="string">
+ <annotation>
+ <documentation>
+ The identifier of the popup menu. If none is specified, then it will appear in all popup menus.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="path" type="string">
+ <annotation>
+ <documentation>
+ The path within the popup menu to place the element. If not specified, then this is added to the "additions" group.
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="menuContribution">
+ <annotation>
+ <documentation>
+ <p>Defines an ordered set of additions to the command UI structure. The defined elements will be added into the command UI structure at the location specified by the <code>locationURI</code> element.
+</p><p>
+This should be the starting point for <i>all</i> contributions into menus, toolbars or trim, wherever they occur in the UI.
+</p>
+ </documentation>
+ </annotation>
+ <complexType>
+ <sequence>
+ <element ref="menu" minOccurs="0" maxOccurs="unbounded"/>
+ <element ref="command" minOccurs="0" maxOccurs="unbounded"/>
+ <element ref="separator" minOccurs="0" maxOccurs="unbounded"/>
+ <element ref="dynamic" minOccurs="0" maxOccurs="unbounded"/>
+ <element ref="toolbar" minOccurs="0" maxOccurs="unbounded"/>
+ <element ref="control" minOccurs="0" maxOccurs="unbounded"/>
+ </sequence>
+ <attribute name="locationURI" type="string" use="required">
+ <annotation>
+ <documentation>
+ A <code>URI</code> specification that defines the insertion point at which the contained additions will be added.
+
+The format for the URI is comprised of three basic parts:
+
+Scheme: One of "menu", "popup" or "toolbar. Indicates the type of the manager used to handle the contributions
+Id: This is either the id of an existing menu, a view id or the id of the editor 'type'
+Query: The query format is &lt;placement&gt;=&lt;id&gt; where:
+ &lt;placement&gt; is either "before" or "after" and
+ &lt;id&gt; is the id of an existing menu item
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="menu">
+ <annotation>
+ <appInfo>
+ <meta.element labelAttribute="label" icon="icon"/>
+ </appInfo>
+ <documentation>
+ Defines a new menu contribution at the given insertion point.
+ </documentation>
+ </annotation>
+ <complexType>
+ <sequence minOccurs="0" maxOccurs="1">
+ <element ref="visibleWhen" minOccurs="0" maxOccurs="1"/>
+ <choice minOccurs="0" maxOccurs="unbounded">
+ <element ref="menu" minOccurs="0" maxOccurs="1"/>
+ <element ref="command" minOccurs="0" maxOccurs="1"/>
+ <element ref="separator" minOccurs="0" maxOccurs="1"/>
+ <element ref="dynamic" minOccurs="0" maxOccurs="1"/>
+ </choice>
+ </sequence>
+ <attribute name="id" type="string">
+ <annotation>
+ <documentation>
+ The 'id' of this menu contribution. If defined then it can be extended through other 'menuAddition' elements or the id can be used as a reference in the Query part of the location defining whether the additions are to go before or after this element.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="mnemonic" type="string">
+ <annotation>
+ <documentation>
+ The character of the Label that should be given the mnemonic affordance. This is to allow the menu system to re-define the value during translation without having to understand the various platforms' conventions for menu label definition (i.e. using the '&amp;' character...).
+ </documentation>
+ <appInfo>
+ <meta.attribute translatable="true"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ <attribute name="icon" type="string">
+ <annotation>
+ <documentation>
+ A plugin relative path to the image to be used as the icon for this menu in either a menu or a toolbar.
+ </documentation>
+ <appInfo>
+ <meta.attribute kind="resource"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ <attribute name="tooltip" type="string">
+ <annotation>
+ <documentation>
+ The tooltip to be displayed for this element when it is placed in a toolbar. This value should be translatable.
+ </documentation>
+ <appInfo>
+ <meta.attribute translatable="true"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ <attribute name="label" type="string" use="required">
+ <annotation>
+ <documentation>
+ The label to be displayed for this element when it is placed in either a menu or a toolbar. This value should be translatable.
+ </documentation>
+ <appInfo>
+ <meta.attribute translatable="true"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="command">
+ <annotation>
+ <appInfo>
+ <meta.element labelAttribute="label" icon="icon"/>
+ </appInfo>
+ <documentation>
+ Defines a new Command Contribution at the defined insertion point.
+ </documentation>
+ </annotation>
+ <complexType>
+ <sequence>
+ <element ref="visibleWhen" minOccurs="0" maxOccurs="1"/>
+ <element ref="parameter" minOccurs="0" maxOccurs="unbounded"/>
+ </sequence>
+ <attribute name="commandId" type="string" use="required">
+ <annotation>
+ <documentation>
+ 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.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="id" type="string">
+ <annotation>
+ <documentation>
+ The 'id' of this contribution. If defined then it can be used as a reference in the Query part of the location defining whether the additions are to go before or after this element.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="mnemonic" type="string">
+ <annotation>
+ <documentation>
+ The character of the Label that should be given the mnemonic affordance. This is to allow the menu system to re-define the value during translation without having to understand the various platforms' conventions for menu label definition (i.e. using the '&amp;' character...).
+ </documentation>
+ <appInfo>
+ <meta.attribute translatable="true"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ <attribute name="icon" type="string">
+ <annotation>
+ <documentation>
+ a relative path of an icon used to visually represent the action in its context.
+If omitted and the action appears in the toolbar, the Workbench will use a placeholder icon. The path is relative to the location of the plugin.xml file of the contributing plug-in.
+ </documentation>
+ <appInfo>
+ <meta.attribute kind="resource"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ <attribute name="disabledIcon" type="string">
+ <annotation>
+ <documentation>
+ a relative path of an icon used to visually represent the action in its context when the action is disabled. If omitted, the normal icon will simply appear greyed out. The path is relative to the location of the plugin.xml file of the contributing plug-in. The disabled icon will appear in toolbars but not in menus. Icons for disabled actions in menus will be supplied by the OS.
+ </documentation>
+ <appInfo>
+ <meta.attribute kind="resource"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ <attribute name="hoverIcon" type="string">
+ <annotation>
+ <documentation>
+ a relative path of an icon used to visually represent the action in its context when the mouse pointer is over the action. If omitted, the normal icon will be used. The path is relative to the location of the plugin.xml file of the contributing plug-in.
+ </documentation>
+ <appInfo>
+ <meta.attribute kind="resource"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ <attribute name="label" type="string">
+ <annotation>
+ <documentation>
+ The label to be displayed for this element when it is placed in either a menu. This value should be translatable.
+ </documentation>
+ <appInfo>
+ <meta.attribute translatable="true"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ <attribute name="tooltip" type="string">
+ <annotation>
+ <documentation>
+ The tooltip to be displayed for this element when it is placed in a toolbar. This value should be translatable.
+ </documentation>
+ <appInfo>
+ <meta.attribute translatable="true"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ <attribute name="helpContextId" type="string">
+ <annotation>
+ <documentation>
+ a unique identifier indicating the help context for this action. If the action appears as a menu item, then pressing F1 while the menu item is highlighted will display help.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="style" use="default" value="push">
+ <annotation>
+ <documentation>
+ an attribute to define the user interface style type for the action. If omitted, then it is <samp>push</samp> by default. The attribute value will be one of the following:
+ <table border="0" width="80%">
+ <tr>
+ <td valign="top" width="25"></td>
+ <td valign="top" nowrap><b>push</b></td>
+ <td valign="top">- as a regular menu item or tool item.</td>
+ </tr>
+ <tr>
+ <td valign="top" width="25"></td>
+ <td valign="top" nowrap><b>radio</b></td>
+ <td valign="top">- as a radio style menu item or tool item. Actions with the radio style within the same menu or toolbar group behave as a radio set. The initial value is specified by the <samp>state</samp> attribute.</td>
+ </tr>
+ <tr>
+ <td valign="top" width="25"></td>
+ <td valign="top" nowrap><b>toggle</b></td>
+ <td valign="top">- as a checked style menu item or as a toggle tool item. The initial value is specified by the <samp>state</samp> attribute.</td>
+ </tr>
+ <tr>
+ <td valign="top" width="25"></td>
+ <td valign="top" nowrap><b>pulldown</b></td>
+ <td valign="top">- (ToolBar only) Creates a ToolItem with the <code>SWT.DROP_DOWN</code> affordance. The URI of the menu is "menu:" + this item's ID.</td>
+ </tr>
+ </table>
+ </documentation>
+ </annotation>
+ <simpleType>
+ <restriction base="string">
+ <enumeration value="push">
+ </enumeration>
+ <enumeration value="radio">
+ </enumeration>
+ <enumeration value="toggle">
+ </enumeration>
+ <enumeration value="pulldown">
+ </enumeration>
+ </restriction>
+ </simpleType>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="separator">
+ <annotation>
+ <appInfo>
+ <meta.element labelAttribute="name"/>
+ </appInfo>
+ <documentation>
+ Inserts a separator at the current insertion point.
+ </documentation>
+ </annotation>
+ <complexType>
+ <attribute name="name" type="string" use="required">
+ <annotation>
+ <documentation>
+ The 'id' of this contribution. If defined then it can be used as a reference in the Query part of the location defining whether the additions are to go before or after this element (or at the end of the logical group containing this element using the 'endOf' value).
+<p>
+Separator contributions that have an id define the start of a logical group so the result of using the 'endof' value for placement is to search forward in the current menu to locate the next id'd separator and to place the inserted elements before that element. If no trailing separator is found then the items are placed at the end of the menu.
+</p>
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="visible" type="boolean">
+ <annotation>
+ <documentation>
+ Indicates whether or not the separator should be visible in the UI. <code>false</code> by default.
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="toolbar">
+ <annotation>
+ <appInfo>
+ <meta.element labelAttribute="id"/>
+ </appInfo>
+ <documentation>
+ Contributes a new ToolBar at the current insertion point.
+ </documentation>
+ </annotation>
+ <complexType>
+ <sequence minOccurs="0" maxOccurs="1">
+ <element ref="visibleWhen" minOccurs="0" maxOccurs="1"/>
+ <choice minOccurs="0" maxOccurs="unbounded">
+ <element ref="command" minOccurs="0" maxOccurs="1"/>
+ <element ref="separator" minOccurs="0" maxOccurs="1"/>
+ <element ref="dynamic" minOccurs="0" maxOccurs="1"/>
+ <element ref="control" minOccurs="0" maxOccurs="1"/>
+ </choice>
+ </sequence>
+ <attribute name="id" type="string" use="required">
+ <annotation>
+ <documentation>
+ The 'id' of this toolbar contribution. If defined then it can be extended through other 'menuAddition' elements or the id can be used as a reference in the Query part of the location defining whether the additions are to go before or after this element.
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="control">
+ <annotation>
+ <documentation>
+ Used to contribute controls to ToolBars in the workbench. The 'class' attribute must be a derivative of the
+WorkbenchWindowControlContribution base class.
+<p>
+<b>NOTE:</b> Due to platform restruictions ontrol contributions are only supported for toolbars; Attempts to contribute controls into a menu or popup will be treated as a NO-OP.
+</p>
+ </documentation>
+ </annotation>
+ <complexType>
+ <attribute name="id" type="string">
+ <annotation>
+ <documentation>
+ The 'id' of this menu contribution. If defined then it can be used as a reference in the Query part of the location defining whether the additions are to go before or after this element.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="class" type="string" use="required">
+ <annotation>
+ <documentation>
+ The class which will be used to create the control that is to be hosted in a ToolBar. This must be a subclass of
+WorkbenchWindowControlContribution which provides information as to the control's location (i.e. which workbench window it's being hosted in and the side of the window that it is currently being displayed on.
+ </documentation>
+ <appInfo>
+ <meta.attribute kind="java" basedOn="org.eclipse.ui.menus.WorkbenchWindowControlContribution"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="dynamic">
+ <annotation>
+ <documentation>
+ The element provides a mechanism that will call back into the defined class to fill a list with the IContributionItems to be shown when the menu or toolbar is built. The defined class must be a derivative of the org.eclipse.ui.actions.CompoundContributionItem base class that provides an implementation for the abstract <code>getContributionItems</code> method.
+ </documentation>
+ </annotation>
+ <complexType>
+ <sequence>
+ <element ref="class" minOccurs="0" maxOccurs="1"/>
+ <element ref="visibleWhen" minOccurs="0" maxOccurs="1"/>
+ </sequence>
+ <attribute name="id" type="string" use="required">
+ <annotation>
+ <documentation>
+ A unique identifier for this contribution. It is recommended that the identifier be prefixed by the plug-in name, to guarantee uniqueness. For example, a widget contributed by <code>org.eclipse.ui</code> might be called <code>org.eclipse.ui.widget1</code>.
+<p>
+If defined then it can be used as a reference in the Query part of the location defining whether the additions are to go before or after this element (or at the end of the logical group containing this element using the 'endof' value).
+</p>
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="class" type="string" use="required">
+ <annotation>
+ <documentation>
+ This class is expected to be a subclass of CompoundContributionItem. When an addition of this type is encountered the specified class is instantiated and used to retrieve a list of the IContributionItems to be placed into the menu. The resulting list may be empty if there are no appropriate items to be shown in the current context.
+ </documentation>
+ <appInfo>
+ <meta.attribute kind="java" basedOn="org.eclipse.ui.actions.CompoundContributionItem"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="since"/>
+ </appInfo>
+ <documentation>
+ 3.3
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="examples"/>
+ </appInfo>
+ <documentation>
+ <p>
+A basic extension looks like this.
+</p>
+<pre>
+ <extension
+ id="add.item"
+ point="org.eclipse.ui.menus">
+ <menuContribution
+ locationURI="menu:someorg.somemenu.id?after=additions">
+ <command
+ commandId="someorg.someid.someCommand"
+ icon="icons/anything.gif"
+ id="someorg.someid.BasicCmdItem"
+ label="Simple Item"
+ mnemonic="S">
+ </command>
+ </menuContribution>
+ </extension>
+</pre>
+<p>
+This is the simplest example; adding a command contribution after an existing menu's additions group.
+</p>
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="apiInfo"/>
+ </appInfo>
+ <documentation>
+ <p>
+It is preferred that menu contributions be added in the <code>plugin.xml</code>. Plugins can
+programmatically add their own menu contributions using <code>org.eclipse.ui.menus.IMenuService</code> and <code>org.eclipse.ui.menus.AbstractContributionFactory</code>, but should be sure to remove them if the plugin is unloaded. The <code>IMenuService</code> can be retrieved through any of the <code>IServiceLocators</code>, the workbench, the workbench window, or the part site.
+</p>
+<p>
+See <a href="org_eclipse_ui_commands.html">org.eclipse.ui.commands</a> to define a command and <a href="org_eclipse_ui_handlers.html">org.eclipse.ui.handlers</a> to define an implementation for the command.
+</p>
+<p>To register a context menu, use the <code>IWorkbenchPartSite.registerContextMenu</code> methods.</p>
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="implementation"/>
+ </appInfo>
+ <documentation>
+
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="copyright"/>
+ </appInfo>
+ <documentation>
+ Copyright (c) 2005,2007 IBM Corporation and others.<br>
+All rights reserved. This program and the accompanying materials are made
+available under the terms of the Eclipse Public License v1.0 which accompanies
+this distribution, and is available at <a
+href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>
+ </documentation>
+ </annotation>
+
+</schema>
Added: directory/studio/branches/studio-eclipse-3.3/dependencies/eclipse/3.3.1/plugins/org.eclipse.rcp.source_3.3.2.R33x_r20071022-8y8eE9CEV3FspP8HJrY1M2dS/src/org.eclipse.ui_3.3.1.M20070910-0800b/schema/newWizards.exsd
URL: http://svn.apache.org/viewvc/directory/studio/branches/studio-eclipse-3.3/dependencies/eclipse/3.3.1/plugins/org.eclipse.rcp.source_3.3.2.R33x_r20071022-8y8eE9CEV3FspP8HJrY1M2dS/src/org.eclipse.ui_3.3.1.M20070910-0800b/schema/newWizards.exsd?rev=607099&view=auto
==============================================================================
--- directory/studio/branches/studio-eclipse-3.3/dependencies/eclipse/3.3.1/plugins/org.eclipse.rcp.source_3.3.2.R33x_r20071022-8y8eE9CEV3FspP8HJrY1M2dS/src/org.eclipse.ui_3.3.1.M20070910-0800b/schema/newWizards.exsd (added)
+++ directory/studio/branches/studio-eclipse-3.3/dependencies/eclipse/3.3.1/plugins/org.eclipse.rcp.source_3.3.2.R33x_r20071022-8y8eE9CEV3FspP8HJrY1M2dS/src/org.eclipse.ui_3.3.1.M20070910-0800b/schema/newWizards.exsd Thu Dec 27 09:44:07 2007
@@ -0,0 +1,336 @@
+<?xml version='1.0' encoding='UTF-8'?>
+<!-- Schema file written by PDE -->
+<schema targetNamespace="org.eclipse.ui">
+<annotation>
+ <appInfo>
+ <meta.schema plugin="org.eclipse.ui" id="newWizards" name="Creation Wizards"/>
+ </appInfo>
+ <documentation>
+ This extension point is used to register resource creation wizard extensions. Creation wizards appear as choices within the "New Dialog", and are typically used to create folders and files.
+<p>
+In the "New Dialog", wizards are organized into categories which usually reflect a particular problem domain. For instance, a Java oriented plugin may define a category called "Java" which is appropriate for "Class" or "Package" creation wizards. The categories defined by one plug-in can be referenced by other plug-ins using the category attribute. Uncategorized wizards, as well as wizards with invalid category paths, will end up in an "Other" category.
+</p>
+
+<p>
+Wizards may optionally specify a description subelement whose body should contain short text about the wizard.
+</p>
+ </documentation>
+ </annotation>
+
+ <element name="extension">
+ <complexType>
+ <choice minOccurs="0" maxOccurs="unbounded">
+ <element ref="category"/>
+ <element ref="wizard"/>
+ <element ref="primaryWizard"/>
+ </choice>
+ <attribute name="point" type="string" use="required">
+ <annotation>
+ <documentation>
+ a fully qualified identifier of the target extension point
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="id" type="string">
+ <annotation>
+ <documentation>
+ an optional identifier of the extension instance
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="name" type="string">
+ <annotation>
+ <documentation>
+ an optional name of the extension instance
+ </documentation>
+ <appInfo>
+ <meta.attribute translatable="true"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="category">
+ <annotation>
+ <appInfo>
+ <meta.element labelAttribute="name"/>
+ </appInfo>
+ </annotation>
+ <complexType>
+ <attribute name="id" type="string" use="required">
+ <annotation>
+ <documentation>
+ a unique name that can be used to identify this category
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="name" type="string" use="required">
+ <annotation>
+ <documentation>
+ a translatable name of the category that will be used in the dialog box
+ </documentation>
+ <appInfo>
+ <meta.attribute translatable="true"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ <attribute name="parentCategory" type="string">
+ <annotation>
+ <documentation>
+ a path to another category if this category should be added as a child
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="wizard">
+ <annotation>
+ <appInfo>
+ <meta.element labelAttribute="name" icon="icon"/>
+ </appInfo>
+ </annotation>
+ <complexType>
+ <sequence>
+ <element ref="description" minOccurs="0" maxOccurs="1"/>
+ <element ref="selection" minOccurs="0" maxOccurs="unbounded"/>
+ </sequence>
+ <attribute name="id" type="string" use="required">
+ <annotation>
+ <documentation>
+ a unique name that can be used to identify this wizard
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="name" type="string" use="required">
+ <annotation>
+ <documentation>
+ a translatable name of the wizard that will be used in the dialog box
+ </documentation>
+ <appInfo>
+ <meta.attribute translatable="true"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ <attribute name="icon" type="string">
+ <annotation>
+ <documentation>
+ a relative path of an icon that will be used together with the name to represent the wizard
+as one of the choices in the creation dialog box.
+ </documentation>
+ <appInfo>
+ <meta.attribute kind="resource"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ <attribute name="category" type="string">
+ <annotation>
+ <documentation>
+ a slash-delimited path ('/') of category IDs. Each token in the
+path must represent a valid category ID previously defined
+by this or some other plug-in. If omitted, the wizard will be
+added to the "Other" category.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="class" type="string" use="required">
+ <annotation>
+ <documentation>
+ a fully qualified name of the Java class implementing <samp>org.eclipse.ui.INewWizard</samp>.
+ </documentation>
+ <appInfo>
+ <meta.attribute kind="java" basedOn="org.eclipse.jface.wizard.Wizard:org.eclipse.ui.INewWizard"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ <attribute name="project" type="boolean">
+ <annotation>
+ <documentation>
+ an optional attribute indicating the wizard will create an IProject resource.
+Also causes the wizard to appear as a choice within the "New Project Dialog".
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="finalPerspective" type="string">
+ <annotation>
+ <documentation>
+ an optional attribute which identifies a perspective to activate when IProject resource creation is finished.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="preferredPerspectives" type="string">
+ <annotation>
+ <documentation>
+ an optional attribute specifying a comma-separated list of perspective IDs. If the current perspective is in this list, then no perspective activation occurs when IProject resource creation is finished.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="helpHref" type="string">
+ <annotation>
+ <documentation>
+ a help url that can describe this wizard in detail.
+<p>
+Since 3.0
+</p>
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="descriptionImage" type="string">
+ <annotation>
+ <documentation>
+ a larger image that can help describe this wizard.
+<p>
+Since 3.0
+</p>
+ </documentation>
+ <appInfo>
+ <meta.attribute kind="resource"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ <attribute name="canFinishEarly" type="boolean">
+ <annotation>
+ <documentation>
+ whether the wizard is capable of finishing without ever showing pages to the user.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="hasPages" type="boolean">
+ <annotation>
+ <documentation>
+ whether the wizard provides any pages.
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="description" type="string">
+ <annotation>
+ <appInfo>
+ <meta.element translatable="true"/>
+ </appInfo>
+ <documentation>
+ an optional subelement whose body contains a short text describing what the wizard will do when started
+ </documentation>
+ </annotation>
+ </element>
+
+ <element name="selection">
+ <complexType>
+ <attribute name="class" type="string" use="required">
+ <annotation>
+ <documentation>
+ a fully qualified class name. If each object in the workbench selection implements this interface the selection will be passed to the wizard. Otherwise, an empty selection is passed
+ </documentation>
+ <appInfo>
+ <meta.attribute kind="java"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ <attribute name="name" type="string">
+ <annotation>
+ <documentation>
+ an optional name filter. Each object in the workbench selection must match the name filter to be passed to the wizard
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="primaryWizard">
+ <annotation>
+ <documentation>
+ a means of declaring that a wizard is "primary" in the UI. A primary wizard is emphasized in the new wizard dialog. Please note that this element is not intended to be used by plug in developers! This element exists so that product managers may emphasize a set of wizards for their products.
+ </documentation>
+ </annotation>
+ <complexType>
+ <attribute name="id" type="string" use="required">
+ <annotation>
+ <documentation>
+ the id of a wizard that should be made primary.
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="examples"/>
+ </appInfo>
+ <documentation>
+ Following is an example of creation wizard configuration:
+<p>
+<pre>
+ <extension point="org.eclipse.ui.newWizards">
+ <category
+ id="com.xyz.XYZ"
+ name="XYZ Wizards">
+ </category>
+ <category
+ id="com.xyz.XYZ.Web"
+ name="Web Wizards"
+ parentCategory="com.xyz.XYZ">
+ </category>
+ <wizard
+ id="com.xyz.wizard1"
+ name="XYZ artifact"
+ category="com.xyz.XYZ/com.xyz.XYZ.Web"
+ icon="./icons/XYZwizard1.gif"
+ class="com.xyz.XYZWizard1">
+ <description>
+ Create a simple XYZ artifact and set initial content
+ </description>
+ <selection class="org.eclipse.core.resources.IResource"/>
+ </wizard>
+ </extension>
+</pre>
+</p>
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="apiInfo"/>
+ </appInfo>
+ <documentation>
+ The value of the class attribute must represent a class
+that implements <samp>org.eclipse.ui.INewWizard</samp>.
+If the wizard is created from within the
+New Wizard it will be inserted into the existing wizard.
+If the wizard is launched as a shortcut
+(from the File New menu or a toolbar button) it will
+appear standalone as a separate dialog box.
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="implementation"/>
+ </appInfo>
+ <documentation>
+ The workbench comes with wizards for creating empty
+resources of the following types:
+project, folder and file. These wizards are registered
+using the same mechanism as described above.
+Additional wizards may also appear, subject to
+particular platform installation.
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="copyright"/>
+ </appInfo>
+ <documentation>
+ Copyright (c) 2002, 2005 IBM Corporation and others.<br>
+All rights reserved. This program and the accompanying materials are made
+available under the terms of the Eclipse Public License v1.0 which accompanies
+this distribution, and is available at <a
+href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>
+ </documentation>
+ </annotation>
+
+</schema>
Added: directory/studio/branches/studio-eclipse-3.3/dependencies/eclipse/3.3.1/plugins/org.eclipse.rcp.source_3.3.2.R33x_r20071022-8y8eE9CEV3FspP8HJrY1M2dS/src/org.eclipse.ui_3.3.1.M20070910-0800b/schema/perspectiveExtensions.exsd
URL: http://svn.apache.org/viewvc/directory/studio/branches/studio-eclipse-3.3/dependencies/eclipse/3.3.1/plugins/org.eclipse.rcp.source_3.3.2.R33x_r20071022-8y8eE9CEV3FspP8HJrY1M2dS/src/org.eclipse.ui_3.3.1.M20070910-0800b/schema/perspectiveExtensions.exsd?rev=607099&view=auto
==============================================================================
--- directory/studio/branches/studio-eclipse-3.3/dependencies/eclipse/3.3.1/plugins/org.eclipse.rcp.source_3.3.2.R33x_r20071022-8y8eE9CEV3FspP8HJrY1M2dS/src/org.eclipse.ui_3.3.1.M20070910-0800b/schema/perspectiveExtensions.exsd (added)
+++ directory/studio/branches/studio-eclipse-3.3/dependencies/eclipse/3.3.1/plugins/org.eclipse.rcp.source_3.3.2.R33x_r20071022-8y8eE9CEV3FspP8HJrY1M2dS/src/org.eclipse.ui_3.3.1.M20070910-0800b/schema/perspectiveExtensions.exsd Thu Dec 27 09:44:07 2007
@@ -0,0 +1,310 @@
+<?xml version='1.0' encoding='UTF-8'?>
+<!-- Schema file written by PDE -->
+<schema targetNamespace="org.eclipse.ui">
+<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
+the initial contents of the window action bars
+(menu and toolbar) and the initial set of views
+and their layout within a workbench page.
+Other plug-ins may contribute actions or views to
+the perspective which appear when the perspective
+is selected. Optional additions by other plug-ins
+are appended to the initial definition.
+ </documentation>
+ </annotation>
+
+ <element name="extension">
+ <complexType>
+ <sequence>
+ <element ref="perspectiveExtension" minOccurs="0" maxOccurs="unbounded"/>
+ </sequence>
+ <attribute name="point" type="string" use="required">
+ <annotation>
+ <documentation>
+ a fully qualified identifier of the target extension point
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="id" type="string">
+ <annotation>
+ <documentation>
+ an optional identifier of the extension instance
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="name" type="string">
+ <annotation>
+ <documentation>
+ an optional name of the extension instance
+ </documentation>
+ <appInfo>
+ <meta.attribute translatable="true"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="perspectiveExtension">
+ <annotation>
+ <appInfo>
+ <meta.element labelAttribute="targetID"/>
+ </appInfo>
+ </annotation>
+ <complexType>
+ <choice minOccurs="0" maxOccurs="unbounded">
+ <element ref="actionSet"/>
+ <element ref="viewShortcut"/>
+ <element ref="perspectiveShortcut"/>
+ <element ref="newWizardShortcut"/>
+ <element ref="view"/>
+ <element ref="showInPart"/>
+ </choice>
+ <attribute name="targetID" type="string" use="required">
+ <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 "*" the extension is applied to all perspectives.
+
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="actionSet">
+ <complexType>
+ <attribute name="id" type="string" use="required">
+ <annotation>
+ <documentation>
+ the unique identifier of the action set which will be added to the perspective.
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="viewShortcut">
+ <complexType>
+ <attribute name="id" type="string" use="required">
+ <annotation>
+ <documentation>
+ the unique identifier of the view which will be added to the perspective's "Show View" submenu of the "Window" menu.
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="perspectiveShortcut">
+ <complexType>
+ <attribute name="id" type="string" use="required">
+ <annotation>
+ <documentation>
+ the unique identifier of the perspective which will be added to the perspective's "Open Perspective" submenu of the "Window" menu.
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="newWizardShortcut">
+ <complexType>
+ <attribute name="id" type="string" use="required">
+ <annotation>
+ <documentation>
+ the unique identifier of the new wizard which will be added to the perspective's "New" submenu of the "File" menu.
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="showInPart">
+ <complexType>
+ <attribute name="id" type="string">
+ <annotation>
+ <documentation>
+ the unique identifier of the view which will be added to the perspective's "Show In..." prompter in the Navigate menu.
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="view">
+ <complexType>
+ <attribute name="id" type="string" use="required">
+ <annotation>
+ <documentation>
+ the unique identifier of the view which will be added to the perspective layout.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="relative" type="string">
+ <annotation>
+ <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 <samp>relationship</samp>. Ignored if relationship is "fast".
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="relationship" use="required">
+ <annotation>
+ <documentation>
+ specifies the relationship between <samp>id</samp> and
+<samp>relative</samp>.
+The following values are supported:
+<ul>
+<b>fast</b> - the view extension will be created as a fast view.
+<br><b>stack</b> - the view extension will be stacked with the relative
+view in a folder.
+<br><b>left, right, top, bottom</b> - the view extension will be placed
+beside the relative view. In this case a <samp>ratio</samp> must also
+be defined.</ul>
+ </documentation>
+ </annotation>
+ <simpleType>
+ <restriction base="string">
+ <enumeration value="stack">
+ </enumeration>
+ <enumeration value="left">
+ </enumeration>
+ <enumeration value="right">
+ </enumeration>
+ <enumeration value="top">
+ </enumeration>
+ <enumeration value="bottom">
+ </enumeration>
+ <enumeration value="fast">
+ </enumeration>
+ </restriction>
+ </simpleType>
+ </attribute>
+ <attribute name="ratio" type="string">
+ <annotation>
+ <documentation>
+ the percentage of area within the relative view which will be donated to the view extension. If the view extension is a fast view, the ratio is the percentage of the workbench the fast view will cover when active. This must be defined as a floating point value and lie between 0.05 and 0.95.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="visible" type="boolean">
+ <annotation>
+ <documentation>
+ whether the view is initially visible when the perspective is opened. This attribute should have a value of "true" or "false" if used.
+If this attribute is not used, the view will be initially visible by default.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="closeable" type="boolean">
+ <annotation>
+ <documentation>
+ whether the view is closeable in the target perspective. This attribute should have a value of "true" or "false" if used. If this attribute is not used, the view will be closeable, unless the perspective itself is marked as fixed.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="moveable" type="boolean">
+ <annotation>
+ <documentation>
+ whether the view is moveable. A non-moveable view cannot be moved either within the same folder, or moved between folders in the perspective. This attribute should have a value of "true" or "false" if used.
+If this attribute is not used, the view will be moveable, unless the perspective itself is marked as fixed.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="standalone" type="boolean">
+ <annotation>
+ <documentation>
+ whether the view is a standalone view. A standalone view cannot be docked together with others in the same folder. This attribute should have a value of "true" or "false" if used. This attribute is ignored if the relationship attribute is "fast" or "stacked". If this attribute is not used, the view will be a regular view, not a standalone view (default is "false").
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="showTitle" type="boolean">
+ <annotation>
+ <documentation>
+ whether the view's title is shown. This attribute should have a value of "true" or "false" if used. This attribute only applies to standalone views. If this attribute is not used, the view's title will be shown (default is "true").
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="minimized" type="boolean" use="default" value="false">
+ <annotation>
+ <documentation>
+ If the perspective extension will result in a new view stack being created (i.e. the 'relationship' attribute is one of left, right, top or bottom) this field determines the new stack's initial display state.
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </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):
+<p>
+<pre>
+ <extension point="org.eclipse.ui.perspectiveExtensions">
+ <perspectiveExtension
+ targetID="org.eclipse.ui.resourcePerspective">
+ <actionSet id="org.eclipse.jdt.ui.JavaActionSet"/>
+ <viewShortcut id="org.eclipse.jdt.ui.PackageExplorer"/>
+ <newWizardShortcut id="org.eclipse.jdt.ui.wizards.NewProjectCreationWizard"/>
+ <perspectiveShortcut id="org.eclipse.jdt.ui.JavaPerspective"/>
+ <view id="org.eclipse.jdt.ui.PackageExplorer"
+ relative="org.eclipse.ui.views.ResourceNavigator"
+ relationship="stack"/>
+ <view id="org.eclipse.jdt.ui.TypeHierarchy"
+ relative="org.eclipse.ui.views.ResourceNavigator"
+ relationship="left"
+ ratio="0.50"/>
+ </perspectiveExtension>
+ </extension>
+</pre>
+</p>
+<p>
+In the example above, an action set, view shortcut,
+new wizard shortcut, and perspective shortcut are
+contributed to the initial contents of the
+Resource Perspective. In addition, the
+Package Explorer view is stacked on the
+Resource Navigator and the Type Hierarchy View is
+added beside the Resource Navigator.
+</p>
+ </documentation>
+ </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>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="implementation"/>
+ </appInfo>
+ <documentation>
+
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="copyright"/>
+ </appInfo>
+ <documentation>
+ Copyright (c) 2002, 2007 IBM Corporation and others.<br>
+All rights reserved. This program and the accompanying materials are made
+available under the terms of the Eclipse Public License v1.0 which accompanies
+this distribution, and is available at <a
+href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>
+ </documentation>
+ </annotation>
+
+</schema>
Added: directory/studio/branches/studio-eclipse-3.3/dependencies/eclipse/3.3.1/plugins/org.eclipse.rcp.source_3.3.2.R33x_r20071022-8y8eE9CEV3FspP8HJrY1M2dS/src/org.eclipse.ui_3.3.1.M20070910-0800b/schema/perspectives.exsd
URL: http://svn.apache.org/viewvc/directory/studio/branches/studio-eclipse-3.3/dependencies/eclipse/3.3.1/plugins/org.eclipse.rcp.source_3.3.2.R33x_r20071022-8y8eE9CEV3FspP8HJrY1M2dS/src/org.eclipse.ui_3.3.1.M20070910-0800b/schema/perspectives.exsd?rev=607099&view=auto
==============================================================================
--- directory/studio/branches/studio-eclipse-3.3/dependencies/eclipse/3.3.1/plugins/org.eclipse.rcp.source_3.3.2.R33x_r20071022-8y8eE9CEV3FspP8HJrY1M2dS/src/org.eclipse.ui_3.3.1.M20070910-0800b/schema/perspectives.exsd (added)
+++ directory/studio/branches/studio-eclipse-3.3/dependencies/eclipse/3.3.1/plugins/org.eclipse.rcp.source_3.3.2.R33x_r20071022-8y8eE9CEV3FspP8HJrY1M2dS/src/org.eclipse.ui_3.3.1.M20070910-0800b/schema/perspectives.exsd Thu Dec 27 09:44:07 2007
@@ -0,0 +1,180 @@
+<?xml version='1.0' encoding='UTF-8'?>
+<!-- Schema file written by PDE -->
+<schema targetNamespace="org.eclipse.ui">
+<annotation>
+ <appInfo>
+ <meta.schema plugin="org.eclipse.ui" id="perspective" name="Perspectives"/>
+ </appInfo>
+ <documentation>
+ This extension point is used to add perspective factories to the workbench. A perspective factory is used to define the initial layout and visible action sets for a perspective. The user can select a perspective by invoking the "Open Perspective" submenu of the "Window" menu.
+ </documentation>
+ </annotation>
+
+ <element name="extension">
+ <complexType>
+ <sequence>
+ <element ref="perspective" minOccurs="0" maxOccurs="unbounded"/>
+ </sequence>
+ <attribute name="point" type="string" use="required">
+ <annotation>
+ <documentation>
+ a fully qualified identifier of the target extension point
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="id" type="string">
+ <annotation>
+ <documentation>
+ an optional identifier of the extension instance
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="name" type="string">
+ <annotation>
+ <documentation>
+ an optional name of the extension instance
+ </documentation>
+ <appInfo>
+ <meta.attribute translatable="true"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="perspective">
+ <annotation>
+ <appInfo>
+ <meta.element labelAttribute="name" icon="icon"/>
+ </appInfo>
+ </annotation>
+ <complexType>
+ <sequence>
+ <element ref="description" minOccurs="0" maxOccurs="1"/>
+ </sequence>
+ <attribute name="id" type="string" use="required">
+ <annotation>
+ <documentation>
+ a unique name that will be used to identify this perspective.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="name" type="string" use="required">
+ <annotation>
+ <documentation>
+ a translatable name that will be used in the workbench window menu bar to represent this perspective.
+ </documentation>
+ <appInfo>
+ <meta.attribute translatable="true"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ <attribute name="class" type="string" use="required">
+ <annotation>
+ <documentation>
+ a fully qualified name of the class that implements
+<samp>org.eclipse.ui.IPerspectiveFactory</samp> interface.
+ </documentation>
+ <appInfo>
+ <meta.attribute kind="java" basedOn="org.eclipse.ui.IPerspectiveFactory"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ <attribute name="icon" type="string">
+ <annotation>
+ <documentation>
+ a relative name of the icon that will be associated
+with this perspective.
+ </documentation>
+ <appInfo>
+ <meta.attribute kind="resource"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ <attribute name="fixed" type="boolean">
+ <annotation>
+ <documentation>
+ indicates whether the layout of the perspective is fixed. If true, then views created by the perspective factory are not closeable, and cannot be moved. The default is false.
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="description" type="string">
+ <annotation>
+ <appInfo>
+ <meta.element translatable="true"/>
+ </appInfo>
+ <documentation>
+ an optional subelement whose body should contain text providing a short description of the perspective.
+ </documentation>
+ </annotation>
+ </element>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="examples"/>
+ </appInfo>
+ <documentation>
+ The following is an example of a perspective extension:
+<p>
+<pre>
+ <extension
+ point="org.eclipse.ui.perspectives">
+ <perspective
+ id="org.eclipse.ui.resourcePerspective"
+ name="Resource"
+ class="org.eclipse.ui.internal.ResourcePerspective"
+ icon="icons/MyIcon.gif">
+ </perspective>
+ </extension>
+</pre>
+</p>
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="apiInfo"/>
+ </appInfo>
+ <documentation>
+ The value of the <samp>class</samp> attribute must be the
+fully qualified name of a class that implements
+<samp>org.eclipse.ui.IPerspectiveFactory</samp>.
+The class must supply the initial layout for a
+perspective when asked by the workbench.
+<p>
+The <samp>plugin_customization.ini</samp> file is used to define the default perspective. The <i>default perspective</i> is the first perspective which appears when the product is launched after install. It is also used when the user opens a page or window with no specified perspective. The default perspective is defined as a property within the plugin_customization.ini, as shown below. The user may also override this perspective from the workbench perspectives preference page.
+<pre>
+ defaultPerspectiveId = org.eclipse.ui.resourcePerspective
+</pre>
+The perspectives which appear in the "Open Perspective" menu are shortcuts for perspective selection. This set is defined by the active perspective itself, and extensions made through the perspectiveExtensions extension point.
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="implementation"/>
+ </appInfo>
+ <documentation>
+ The workbench provides a "Resource Perspective".
+Additional perspectives may be added by plug-ins.
+They are selected using the "Open Perspective" submenu of the "Window" menu.
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="copyright"/>
+ </appInfo>
+ <documentation>
+ Copyright (c) 2002, 2005 IBM Corporation and others.<br>
+All rights reserved. This program and the accompanying materials are made
+available under the terms of the Eclipse Public License v1.0 which accompanies
+this distribution, and is available at <a
+href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>
+ </documentation>
+ </annotation>
+
+</schema>