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 [17/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/statusHandlers.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/statusHandlers.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/statusHandlers.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/statusHandlers.exsd Thu Dec 27 09:44:07 2007
@@ -0,0 +1,267 @@
+<?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="statusHandlers" name="Status handlers"/>
+ </appInfo>
+ <documentation>
+ <p>
+This extension point is used to register implementations of status handlers in the workbench. A handler can be associated with a product and this association is also contributed via this extension point.
+</p>
+
+<p>
+Status handlers are part of the status handling facility. The facility is responsible for handling errors and other important issues in Eclipse based applications. The handlers are responsible for presenting this errors by logging or showing error dialogs.
+</p>
+
+<p>
+If there is no status handler associated with a product, the status handling facility uses the application handler defined in a workbench advisor.
+</p>
+ </documentation>
+ </annotation>
+
+ <element name="extension">
+ <complexType>
+ <sequence>
+ <element ref="statusHandler" minOccurs="0" maxOccurs="unbounded"/>
+ <element ref="statusHandlerProductBinding" minOccurs="0" maxOccurs="unbounded"/>
+ </sequence>
+ <attribute name="point" type="string" use="required">
+ <annotation>
+ <documentation>
+
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="id" type="string">
+ <annotation>
+ <documentation>
+
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="name" type="string">
+ <annotation>
+ <documentation>
+
+ </documentation>
+ <appInfo>
+ <meta.attribute translatable="true"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="statusHandler">
+ <annotation>
+ <documentation>
+ This element is used to define a status handler.
+ </documentation>
+ </annotation>
+ <complexType>
+ <sequence>
+ <element ref="parameter" minOccurs="0" maxOccurs="unbounded"/>
+ </sequence>
+ <attribute name="id" type="string" use="required">
+ <annotation>
+ <documentation>
+ <p>
+A unique identifier for this error handler. The id is used for setting default
+error handler in a product.
+If an error handler is to be the default one its id has to be set
+in a product preference file in org.eclipse.ui/ERROR_HANDLER_ID property.
+The name of the preference file is set in product extension
+"preferenceCustomization" property.
+</p>
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="class" type="string" use="required">
+ <annotation>
+ <documentation>
+ <p>
+A fully qualified name of a class which extends <code>org.eclipse.ui.errors.AbstractStatusHandler</code>.
+</p>
+ </documentation>
+ <appInfo>
+ <meta.attribute kind="java" basedOn="org.eclipse.ui.errors.AbstractStatusHandler"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="parameter">
+ <annotation>
+ <appInfo>
+ <meta.element labelAttribute="name"/>
+ </appInfo>
+ <documentation>
+ <p>
+This element defines parameters for instances of specified status handler class.
+Instances of specified status handler class should understand this parameter.
+</p>
+<p>
+Handling policies can use handler parameters. For example default policy
+use handlers "prefix" parameter. The default policy looks for the most specific
+handler for given status checking status pluginId against these prefixes.
+</p>
+ </documentation>
+ </annotation>
+ <complexType>
+ <attribute name="name" type="string" use="required">
+ <annotation>
+ <documentation>
+ The name of a parameter.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="value" type="string" use="required">
+ <annotation>
+ <documentation>
+ The value of a parameter.
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="statusHandlerProductBinding">
+ <annotation>
+ <documentation>
+ <p>
+Specifies a binding between a product and a status handler.
+These bindings determine which handler is appropriate for the current product (as defined by <code>org.eclipse.core.runtime.Platform.getProduct()</code>).
+</p>
+ </documentation>
+ </annotation>
+ <complexType>
+ <attribute name="productId" type="string" use="required">
+ <annotation>
+ <documentation>
+ The unique id of a product.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="handlerId" type="string" use="required">
+ <annotation>
+ <documentation>
+ The unique id of a status handler.
+ </documentation>
+ </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>
+The following is an example of the definition for handler with prefix parameter.
+</p>
+<p>
+<pre>
+<extension
+ point="org.eclipse.ui.statusHandlers">
+ <statusHandler
+ class="org.eclipse.ui.statushanders.SampleStatusHandler"
+ id="sampleStatusHandler">
+ <parameter
+ name="prefix"
+ value="org.eclipse.ui.ide">
+ </parameter>
+ </statusHandler>
+</extension>
+</pre>
+</p>
+<p>
+The following is an example of the definition for default (product) handler. The handler defined in the example will be default for product with id "productId".
+</p>
+<p>
+<pre>
+<extension
+ point="org.eclipse.ui.statusHandlers">
+ <statusHandler
+ class="org.eclipse.ui.statushandlers.SampleStatusHandler"
+ id="sampleStatusHandler">
+ </statusHandler>
+ <statusHandlerProductBinding
+ handlerId="sampleStatusHandler"
+ productId="productId">
+ </statusHandlerProductBinding>
+</extension>
+</pre>
+</p>
+<p>
+Of course we can define only the binding (for instance in a product plugin).
+The handler can be defined in other plugin.
+</p>
+<p>
+<pre>
+<extension
+ point="org.eclipse.ui.statusHandlers">
+ <statusHandlerProductBinding
+ handlerId="sampleStatusHandler"
+ productId="productId">
+ </statusHandlerProductBinding>
+</extension>
+</pre>
+</p>
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="apiInfo"/>
+ </appInfo>
+ <documentation>
+ </p>
+The value of the <code>class</code> attribute in <code>statusHandler</code> element must be the fully qualified name of a class that extends <code>org.eclipse.ui.statushandlers.AbstractStatusHandler</code>.
+</p>
+<p>
+The <code>parameter</code> elements in <code>statusHandler</code> element adds parameters which can be used during handling in the status handler defined in <code>class</code> attribute.
+</p>
+<p>
+The value of the <code>productId</code> attribute in <code>statusHandlerProductBinding</code> is full name of the product to which the handler with id defined in <code>handlerId</code> attribute in <code>statusHandlerProductBinding</code> will be associated.
+</p>
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="implementation"/>
+ </appInfo>
+ <documentation>
+ <p>
+The platform supplies basic implementation of <code>org.eclipse.ui.statushandlers.AbstractStatusHandler</code>.
+It is <code>org.eclipse.ui.statushandlers.WorkbenchErrorHandler</code> which is the default workbench status handler.
+</p>
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="copyright"/>
+ </appInfo>
+ <documentation>
+ Copyright (c) 2006, 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/systemSummarySections.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/systemSummarySections.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/systemSummarySections.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/systemSummarySections.exsd Thu Dec 27 09:44:07 2007
@@ -0,0 +1,142 @@
+<?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="systemSummarySections" name="System Summary Sections"/>
+ </appInfo>
+ <documentation>
+ The Eclipse UI provides an AboutDialog that can be branded and reused by client product plugins. This dialog includes a SystemSummary dialog that contains configuration details. By extending the org.eclipse.ui.systemSummarySections extension point clients are able to put their own information into the log.
+ </documentation>
+ </annotation>
+
+ <element name="extension">
+ <complexType>
+ <sequence>
+ <element ref="section" minOccurs="1" 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="section">
+ <complexType>
+ <attribute name="id" type="string">
+ <annotation>
+ <documentation>
+ an optional, unique name that will be used to identify this system summary section
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="sectionTitle" type="string" use="required">
+ <annotation>
+ <documentation>
+ a translatable name that will be displayed as the title of this section in the system summary
+ </documentation>
+ <appInfo>
+ <meta.attribute translatable="true"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ <attribute name="class" type="string" use="required">
+ <annotation>
+ <documentation>
+ The fully qualified name of a class the implements
+<code>org.eclipse.ui.about.ISystemSummarySection</code>. The class must provide a default constructor.
+ </documentation>
+ <appInfo>
+ <meta.attribute kind="java"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="since"/>
+ </appInfo>
+ <documentation>
+ 3.0
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="examples"/>
+ </appInfo>
+ <documentation>
+ Following is an example of a systemSummarySections extension:
+<pre>
+<extension
+ point="org.eclipse.ui.systemSummarySections">
+ <section
+ id="RCPBrowser.CookieDetails"
+ sectionTitle="Browser Cookies"
+ class="org.eclipse.ui.examples.rcp.browser.CookieConfigDetails"/>
+</extension>
+</pre>
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="apiInfo"/>
+ </appInfo>
+ <documentation>
+ The class specified in the section element must be a concrete subclass of <code>org.eclipse.ui.about.ISystemSummarySection</code>.
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="implementation"/>
+ </appInfo>
+ <documentation>
+ The Workbench uses this extension point to provide the following sections in the system summary dialog:
+<ul>
+<li>System properties: The properties returned by java.lang.System.getProperties().</li>
+<li>Features: The installed features.</li>
+<li>Plug-in Registry: The installed plug-ins and their status.</li>
+<li>User Preferences: The preferences that have been modified from their default values.</li>
+</ul>
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="copyright"/>
+ </appInfo>
+ <documentation>
+ Copyright (c) 2004, 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/themes.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/themes.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/themes.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/themes.exsd Thu Dec 27 09:44:07 2007
@@ -0,0 +1,679 @@
+<?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="themes" name="Themes"/>
+ </appInfo>
+ <documentation>
+ This extension point is used to customize the appearance of the UI. It allows definition of color and font entities as well as theme entities. Themes allow applications to selectively override default color and font specifications for particular uses.
+ </documentation>
+ </annotation>
+
+ <element name="extension">
+ <complexType>
+ <sequence>
+ <element ref="theme" minOccurs="0" maxOccurs="unbounded"/>
+ <element ref="colorDefinition" minOccurs="0" maxOccurs="unbounded"/>
+ <element ref="fontDefinition" minOccurs="0" maxOccurs="unbounded"/>
+ <element ref="themeElementCategory" minOccurs="0" maxOccurs="unbounded"/>
+ <element ref="data" minOccurs="0" maxOccurs="unbounded"/>
+ <element ref="categoryPresentationBinding" 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="theme">
+ <annotation>
+ <appInfo>
+ <meta.element labelAttribute="name" icon="icon"/>
+ </appInfo>
+ <documentation>
+ A collection of font, color and data overrides. Such a collection may be used to alter the appearance of the workbench. Many theme elements may exist with the same id. This allows component authors to contribute to existing themes.
+ </documentation>
+ </annotation>
+ <complexType>
+ <sequence>
+ <element ref="colorOverride" minOccurs="0" maxOccurs="unbounded"/>
+ <element ref="fontOverride" minOccurs="0" maxOccurs="unbounded"/>
+ <element ref="description" minOccurs="0" maxOccurs="1"/>
+ <element ref="data" minOccurs="0" maxOccurs="unbounded"/>
+ </sequence>
+ <attribute name="id" type="string" use="required">
+ <annotation>
+ <documentation>
+ a unique name that will be used to identify this theme
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="name" type="string">
+ <annotation>
+ <documentation>
+ a translatable name of the theme to be presented to the user. At least one theme definition with any given id should contain this attribute.
+ </documentation>
+ <appInfo>
+ <meta.attribute translatable="true"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="themeElementCategory">
+ <annotation>
+ <documentation>
+ A logical grouping of theme element definitions. This category may include colors and fonts.
+ </documentation>
+ </annotation>
+ <complexType>
+ <sequence>
+ <element ref="description" minOccurs="0" maxOccurs="1"/>
+ </sequence>
+ <attribute name="id" type="string" use="required">
+ <annotation>
+ <documentation>
+ the id for this category
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="parentId" type="string">
+ <annotation>
+ <documentation>
+ the id of the parent category, if any.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="class" type="string">
+ <annotation>
+ <documentation>
+ a class that implements <code>org.eclipse.ui.themes.IThemePreview</code>
+ </documentation>
+ <appInfo>
+ <meta.attribute kind="java" basedOn="org.eclipse.ui.IPresentationPreview"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ <attribute name="label" type="string">
+ <annotation>
+ <documentation>
+ a translatable name of the theme element category to be presented to the user
+ </documentation>
+ <appInfo>
+ <meta.attribute translatable="true"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="colorDefinition">
+ <annotation>
+ <documentation>
+ A symbolic color definition.
+ </documentation>
+ </annotation>
+ <complexType>
+ <sequence>
+ <element ref="colorFactory" minOccurs="0" maxOccurs="1"/>
+ <element ref="colorValue" minOccurs="0" maxOccurs="unbounded"/>
+ <element ref="description" minOccurs="0" maxOccurs="1"/>
+ </sequence>
+ <attribute name="id" type="string">
+ <annotation>
+ <documentation>
+ a unique id that can be used to identify this color definition.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="label" type="string" use="required">
+ <annotation>
+ <documentation>
+ a translatable name of the color to be presented to the user.
+ </documentation>
+ <appInfo>
+ <meta.attribute translatable="true"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ <attribute name="defaultsTo" type="string">
+ <annotation>
+ <documentation>
+ the id of another color definition that is the default setting for the receiver. When there is no preference for this color the color registry will have the value of defaultsTo set for it in the registry.
+
+Only one of <code>defaultsTo</code>, <code>value</code> or <code>colorFactory</code> may be defined.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="value" type="string">
+ <annotation>
+ <documentation>
+ The default value of this color. The value may be specified in the following ways:
+<ul>
+<li>a String containing comma separated integers in the form red,green,blue
+<li>a String that maps to an SWT color constant (ie: COLOR_RED).
+</ul>
+Only one of <code>defaultsTo</code>, <code>value</code> or <code>colorFactory</code> may be defined. If <code>value</code> is specified, additional value definitions may be specified on a per platform/windowing system basis via the <code>colorValue</code> element.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="categoryId" type="string">
+ <annotation>
+ <documentation>
+ the optional id of the <code>themeElementCategory</code> this color belongs to.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="colorFactory" type="string">
+ <annotation>
+ <documentation>
+ a class that implements <code>org.eclipse.ui.themes.IColorFactory</code>. This may be used instead of <code>value</code> to specify the default value of the color. Please be advised that this should be used with caution - usage of this attribute will cause plugin activation on workbench startup.
+ </documentation>
+ <appInfo>
+ <meta.attribute kind="java" basedOn="org.eclipse.ui.themes.IColorFactory"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ <attribute name="isEditable" type="boolean">
+ <annotation>
+ <documentation>
+ whether the user should be allowed to edit this color in the preference page. If this is <code>false</code> then the contribution is not shown to the user.
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="fontDefinition">
+ <annotation>
+ <documentation>
+ A symbolic font definition.
+ </documentation>
+ </annotation>
+ <complexType>
+ <sequence>
+ <element ref="fontValue" minOccurs="0" maxOccurs="unbounded"/>
+ <element ref="description" minOccurs="0" maxOccurs="1"/>
+ </sequence>
+ <attribute name="id" type="string" use="required">
+ <annotation>
+ <documentation>
+ a unique name that can be used to identify this font definition.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="label" type="string" use="required">
+ <annotation>
+ <documentation>
+ a translatable name of the font to be presented to the user.
+ </documentation>
+ <appInfo>
+ <meta.attribute translatable="true"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ <attribute name="value" type="string">
+ <annotation>
+ <documentation>
+ <p>the font value. This is in the form: <code>fontname-style-height</code> where <code>fontname</code> is the name of a font, <code>style</code> is a font style (one of <code>"regular"</code>, <code>"bold"</code>, <code>"italic"</code>, or <code>"bold italic"</code>) and <code>height</code> is an integer representing the font height.</p>
+<p>Example: <code>Times New Roman-bold-36</code>.</p>
+<p>Only one (or neither) of <code>value</code> or <code>defaultsTo</code> may be used.</p> If <code>value</code> is specified, additional value definitions may be specified on a per platform/windowing system basis via the <code>fontValue</code> element.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="categoryId" type="string">
+ <annotation>
+ <documentation>
+ the optional id of the <code>themeElementCategory</code> this font belongs to.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="defaultsTo" type="string">
+ <annotation>
+ <documentation>
+ the id of another font definition that is the default setting for the receiver. When there is no preference for this font the font registry will have the value of defaultsTo set for it in the registry.
+<p>
+Only one (or neither) of <code>value</code> or <code>defaultsTo</code> may be used.
+</p>
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="isEditable" type="boolean">
+ <annotation>
+ <documentation>
+ whether the user should be allowed to edit this color in the preference page. If this is <code>false</code> then the contribution is not shown to the user.
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="colorOverride">
+ <annotation>
+ <documentation>
+ Allows overriding of colors defined in <code>colorDefinition</code> elements. These colors will be applied when the theme is in use. The colors that are defined by workbench are:
+
+<ul>
+<li>org.eclipse.jface.preference.JFacePreference.ERROR_COLOR
+<li>org.eclipse.jface.preference.JFacePreference.HYPERLINK_COLOR
+<li>org.eclipse.jface.preference.JFacePreference.ACTIVE_HYPERLINK_COLOR
+</ul>
+ </documentation>
+ </annotation>
+ <complexType>
+ <sequence>
+ <element ref="colorFactory" minOccurs="0" maxOccurs="1"/>
+ <element ref="colorValue" minOccurs="0" maxOccurs="unbounded"/>
+ </sequence>
+ <attribute name="id" type="string" use="required">
+ <annotation>
+ <documentation>
+ a unique id that can be used to identify this color definition override. This should match an existing font identifier. Strictly speaking, you may override colors that do not exist in the base theme although this practice is not recommended. In effect, such overrides will have behavior similar to <code>colorDefinition</code>s that have <code>isEditable</code> set to <code>false</code>.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="value" type="string">
+ <annotation>
+ <documentation>
+ the overriding value of this color. The value may be specified in the following ways:
+<ul>
+<li>a String containing comma separated integers in the form red,green,blue
+<li>a String that maps to an SWT color constant (ie: COLOR_RED).
+</ul>
+Only one of <code>value</code> or <code>colorFactory</code> may be defined.
+Unlike a <code>colorDefinition</code>, you may not supply a <code>defaultsTo</code> for an override.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="colorFactory" type="string">
+ <annotation>
+ <documentation>
+ a class that implements <code>org.eclipse.ui.themes.IColorFactory</code>. This may be used instead of <code>value</code> to specify the default value of the color. Please be advised that this should be used with caution - usage of this attribute will cause plugin activation on workbench startup.
+ </documentation>
+ <appInfo>
+ <meta.attribute kind="java"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="fontOverride">
+ <annotation>
+ <documentation>
+ Allows overriding of fonts defined in <code>fontDefinition</code> elements. These fonts will be applied when the theme is in use. The fonts that are defined by workbench are:
+
+<ul>
+<li>org.eclipse.jface.resource.JFaceResources.BANNER_FONT
+<li>org.eclipse.jface.resource.JFaceResources.DIALOG_FONT
+<li>org.eclipse.jface.resource.JFaceResources.HEADER_FONT
+<li>org.eclipse.jface.resource.JFaceResources.TEXT_FONT
+</ul>
+ </documentation>
+ </annotation>
+ <complexType>
+ <sequence>
+ <element ref="fontValue" minOccurs="0" maxOccurs="unbounded"/>
+ </sequence>
+ <attribute name="id" type="string" use="required">
+ <annotation>
+ <documentation>
+ a unique id that can be used to identify this font definition override. This should match an existing font identifier. Strictly speaking, you may override fonts that do not exist in the base theme although this practice is not recommended. In effect, such overrides will have behavior similar to <code>fontDefinition</code>s that have <code>isEditable</code> set to <code>false</code>.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="value" type="string">
+ <annotation>
+ <documentation>
+ <p>the overriding value of this font. This is in the form: <code>fontname-style-height</code> where <code>fontname</code> is the name of a font, <code>style</code> is a font style (one of <code>"regular"</code>, <code>"bold"</code>, <code>"italic"</code>, or <code>"bold italic"</code>) and <code>height</code> is an integer representing the font height.</p>
+<p>Example: <code>Times New Roman-bold-36</code>.</p>
+<p><code>value</code> must be defined for a font override.
+Unlike a <code>fontDefinition</code>, you may not supply a <code>defaultsTo</code> for a <code>fontOverride</code>.</p>
+
+<p>If this value is not specified the default font will be used</p>
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="description" type="string">
+ <annotation>
+ <appInfo>
+ <meta.element translatable="true"/>
+ </appInfo>
+ <documentation>
+ A short description of the elements usage.
+ </documentation>
+ </annotation>
+ </element>
+
+ <element name="colorFactory">
+ <annotation>
+ <documentation>
+ The element version of the <code>colorFactory</code> attribute. This is used when the colorFactory implements <code>org.eclipse.core.runtime.IExecutableExtension</code> and there is parameterized data that you wish used in its initialization.
+ </documentation>
+ </annotation>
+ <complexType>
+ <sequence>
+ <element ref="parameter" minOccurs="0" maxOccurs="unbounded"/>
+ </sequence>
+ <attribute name="class" type="string" use="required">
+ <annotation>
+ <documentation>
+ a class that implements <code>org.eclipse.ui.themes.IColorFactory</code>. It may also implement <code>org.eclipse.core.runtime.IExecutableExtension</code>.
+ </documentation>
+ <appInfo>
+ <meta.attribute kind="java" basedOn="org.eclipse.ui.themes.IColorFactory"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ <attribute name="plugin" type="string">
+ <annotation>
+ <documentation>
+ the identifier of the plugin that contains the class
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="parameter">
+ <annotation>
+ <documentation>
+ A parameter element to be used within the colorFactory element. This will be passed as initialization data to the colorFactory class.
+ </documentation>
+ </annotation>
+ <complexType>
+ <attribute name="name" type="string" use="required">
+ <annotation>
+ <documentation>
+ the parameter name
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="value" type="string" use="required">
+ <annotation>
+ <documentation>
+ the parameter value
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="data">
+ <annotation>
+ <documentation>
+ <p>An element that allows arbitrary data to be associated with a theme or the default theme. This data may be gradient directions or percentages, labels, author information, etc.</p>
+<p>This element has behavior similar to definitions and overrides. If a key is present in both the default theme and an identified theme, then the identified themes value will be used when that theme is accessed. If the identified theme does not supply a value then the default is used.</p>
+ </documentation>
+ </annotation>
+ <complexType>
+ <attribute name="name" type="string" use="required">
+ <annotation>
+ <documentation>
+ the data name,
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="value" type="string" use="required">
+ <annotation>
+ <documentation>
+ the data value
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="colorValue">
+ <annotation>
+ <documentation>
+ This element allows specification of a color value on a per-platform basis.
+ </documentation>
+ </annotation>
+ <complexType>
+ <sequence>
+ <element ref="colorFactory" minOccurs="0" maxOccurs="1"/>
+ </sequence>
+ <attribute name="os" type="string">
+ <annotation>
+ <documentation>
+ an optional os string to enable choosing of color based on current OS. eg: win32,linux
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="ws" type="string">
+ <annotation>
+ <documentation>
+ an optional os string to enable choosing of color based on current WS. eg: win32,gtk
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="value" type="string">
+ <annotation>
+ <documentation>
+ The default value of this color. The value may be specified in the following ways:
+<ul>
+<li>a String containing comma separated integers in the form red,green,blue
+<li>a String that maps to an SWT color constant (ie: COLOR_RED).
+</ul>
+Only one of <code>value</code> or <code>colorFactory</code> may be defined.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="colorFactory" type="string">
+ <annotation>
+ <documentation>
+ a class that implements <code>org.eclipse.ui.themes.IColorFactory</code>. This may be used instead of <code>value</code> to specify the value of the color. Please be advised that this should be used with caution - usage of this attribute will cause plugin activation on workbench startup.
+ </documentation>
+ <appInfo>
+ <meta.attribute kind="java" basedOn="org.eclipse.ui.themes.IColorFactory"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="fontValue">
+ <annotation>
+ <documentation>
+ This element allows specification of a font value on a per-platform basis.
+ </documentation>
+ </annotation>
+ <complexType>
+ <attribute name="os" type="string">
+ <annotation>
+ <documentation>
+ an optional os string to enable choosing of font based on current OS. eg: win32,linux
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="ws" type="string">
+ <annotation>
+ <documentation>
+ an optional os string to enable choosing of font based on current WS. eg: win32,gtk
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="value" type="string" use="required">
+ <annotation>
+ <documentation>
+ <p>the font value. This is in the form: <code>fontname-style-height</code> where <code>fontname</code> is the name of a font, <code>style</code> is a font style (one of <code>"regular"</code>, <code>"bold"</code>, <code>"italic"</code>, or <code>"bold italic"</code>) and <code>height</code> is an integer representing the font height.</p>
+<p>Example: <code>Times New Roman-bold-36</code>.</p>
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="categoryPresentationBinding">
+ <annotation>
+ <documentation>
+ This element allows a category to be bound to a specific presentation as described by the <code>org.eclipse.ui.presentationFactory</code> extension point. If a category has any presentation bindings then it (and it's children) is only configurable by the user if it is bound to the active presentation. This is useful for removing unused items from user consideration.
+ </documentation>
+ </annotation>
+ <complexType>
+ <attribute name="categoryId" type="string" use="required">
+ <annotation>
+ <documentation>
+ the id of the category to bind
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="presentationId" type="string" use="required">
+ <annotation>
+ <documentation>
+ the id of the presentation to bind to
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="implementation"/>
+ </appInfo>
+ <documentation>
+ The workbench provides the font definitions for the text, dialog, banner, header and part title fonts. it also supplies color definitions for the hyperlink, active hyperlink, error, active part (background gradient parts and foreground) and the inactive part (background gradient parts and foreground). The workbench also provides data constants for the title gradient percentages (active and inactive) and the gradient directions (active and inactive). The workbench does not provide any named themes.
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="copyright"/>
+ </appInfo>
+ <documentation>
+ Copyright (c) 2003, 2006 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>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="apiInfo"/>
+ </appInfo>
+ <documentation>
+ The <code>org.eclipse.ui.IWorkbench.getThemeManager()</code> provides an instance of <code>org.eclipse.ui.themes.IThemeManager</code> that may be used to obtain a named theme (by id, including the default theme which has an id of <code>IThemeManager.DEFAULT_THEME</code>) or the current theme. From an <code>org.eclipse.ui.themes.ITheme</code> you may obtain a <code>org.eclipse.jface.resources.ColorRegistry</code>, an <code>org.eclipse.jface.resources.FontRegistry</code> and the arbitrary data associated with a theme.
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="since"/>
+ </appInfo>
+ <documentation>
+ 3.0
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="examples"/>
+ </appInfo>
+ <documentation>
+ The following is an example of several color and font definitions as well as a theme that overrides them.
+<p>
+<pre>
+ <extension point="org.eclipse.ui.themes">
+ <themeElementCategory
+ id="com.xyz.ThemeCategory"
+ class="com.xyz.XYZPreview"
+ label="XYZ Elements"/>
+ <colorDefinition
+ id="com.xyz.Forground"
+ categoryId="com.xyz.ThemeCategory"
+ label="XYZ Foreground Color"
+ value="COLOR_BLACK">
+ <!-- white should be used on GTK -->
+ <colorValue
+ value="COLOR_WHITE"
+ os="linux"
+ ws="gtk"/>
+ <description>
+ This color is used for the foreground color of the XYZ plugin editor.
+ </description>
+ </colorDefinition>
+ <colorDefinition
+ id="com.xyz.Background"
+ categoryId="com.xyz.ThemeCategory"
+ label="XYZ Background Color">
+ <colorFactory
+ class="org.eclipse.ui.themes.RGBBlendColorFactory"
+ plugin="org.eclipse.ui">
+ <parameter
+ name="color1"
+ value="COLOR_WHITE"/>
+ <parameter
+ name="color2"
+ value="COLOR_BLUE"/>
+ </colorFactory>
+ <!-- black should be used on GTK -->
+ <colorValue
+ value="COLOR_BLACK"
+ os="linux"
+ ws="gtk"/>
+ <description>
+ This color is used for the background color of the XYZ plugin editor.
+ </description>
+ </colorDefinition>
+ <fontDefinition
+ id="com.xyz.TextFont"
+ categoryId="com.xyz.ThemeCategory"
+ label="XYZ Editor Font"
+ defaultsTo="org.eclipse.jface.textfont">
+ <description>
+ This font is used by the XYY plugin editor.
+ </description>
+ </fontDefinition>
+ <data
+ name="com.xyz.EditorMarginWidth"
+ value="5"/>
+ <theme
+ id="com.xyz.HarshTheme"
+ label="Harsh Colors for XYZ">
+ <colorOverride
+ id="com.xyz.Forground"
+ value="COLOR_CYAN"/>
+ <colorOverride
+ id="com.xyz.Background"
+ value="COLOR_MAGENTA"/>
+ <data
+ name="com.xyz.EditorMarginWidth"
+ value="1"/>
+ </theme>
+ </extension>
+</pre>
+</p>
+ </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/viewActions.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/viewActions.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/viewActions.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/viewActions.exsd Thu Dec 27 09:44:07 2007
@@ -0,0 +1,471 @@
+<?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="viewActions" name="View Menus,Toolbars and Actions"/>
+ </appInfo>
+ <documentation>
+ <p>This extension point is used to add actions to the pulldown menu and toolbar for views registered by other plug-ins. Each view has a local pulldown menu normally activated
+by clicking on the top right triangle button. Other plug-ins can contribute submenus and actions to this menu. Plug-ins may also contribute actions to a view toolbar. View owners are first given a chance to populate these areas. Optional additions by other plug-ins are appended.</p>
+<p>
+You can now use <a href="org_eclipse_ui_menus.html">org.eclipse.ui.menus</a> to place commands in menus and toolbars as well.
+</p>
+
+ </documentation>
+ </annotation>
+
+ <include schemaLocation="commonAction.exsd"/>
+
+ <include schemaLocation="commonExpression.exsd"/>
+
+ <element name="extension">
+ <complexType>
+ <sequence>
+ <element ref="viewContribution" minOccurs="1" 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="viewContribution">
+ <annotation>
+ <documentation>
+ This element is used to define a group of view actions and/or menus.
+ </documentation>
+ </annotation>
+ <complexType>
+ <sequence>
+ <element ref="menu" minOccurs="0" maxOccurs="unbounded"/>
+ <element ref="action" minOccurs="0" maxOccurs="unbounded"/>
+ </sequence>
+ <attribute name="id" type="string" use="required">
+ <annotation>
+ <documentation>
+ a unique identifier used to reference this contribution.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="targetID" type="string" use="required">
+ <annotation>
+ <documentation>
+ a unique identifier of a registered view that is the target of this contribution.
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="action">
+ <annotation>
+ <appInfo>
+ <meta.element labelAttribute="label" icon="icon"/>
+ </appInfo>
+ <documentation>
+ This element defines an action that the user can invoke in the UI.
+ </documentation>
+ </annotation>
+ <complexType>
+ <sequence>
+ <choice>
+ <element ref="selection" minOccurs="0" maxOccurs="unbounded"/>
+ <element ref="enablement" minOccurs="0" maxOccurs="1"/>
+ </choice>
+ <element ref="class" minOccurs="0" maxOccurs="1"/>
+ </sequence>
+ <attribute name="id" type="string" use="required">
+ <annotation>
+ <documentation>
+ a unique identifier used as a reference for this action.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="label" type="string" use="required">
+ <annotation>
+ <documentation>
+ a translatable name used either as the menu item text or toolbar button label. The name can include mnenomic information.
+ </documentation>
+ <appInfo>
+ <meta.attribute translatable="true"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ <attribute name="menubarPath" type="string">
+ <annotation>
+ <documentation>
+ a slash-delimited path ('/') used to specify the location of this action in the pulldown menu. Each token in the path, except the last one, must represent a valid identifier of an existing menu in the hierarchy. The last token represents the named group into which this action will be added. If the path is omitted, this action will not appear in the pulldown menu.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="toolbarPath" type="string">
+ <annotation>
+ <documentation>
+ a named group within the local toolbar of the target view. If the group does not exist, it will be created. If omitted, the action will not appear in the local toolbar.
+ </documentation>
+ </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. The icon will appear in the toolbar but not in the pulldown menu.
+ </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 the toolbar but not in the pulldown menu.
+ </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="tooltip" type="string">
+ <annotation>
+ <documentation>
+ a translatable text representing the action's tool tip. Only used if the action appears in the toolbar.
+ </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. On some platforms, if the action appears as a menu item, then pressing the appropriate help key while the menu item is highlighted will display help. Not all platforms support this behaviour.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="style" use="default" value="push">
+ <annotation>
+ <documentation>
+ an optional attribute to define the user interface style type for the action. If defined, 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>
+ </table>
+ </documentation>
+ </annotation>
+ <simpleType>
+ <restriction base="string">
+ <enumeration value="push">
+ </enumeration>
+ <enumeration value="radio">
+ </enumeration>
+ <enumeration value="toggle">
+ </enumeration>
+ </restriction>
+ </simpleType>
+ </attribute>
+ <attribute name="state" type="boolean">
+ <annotation>
+ <documentation>
+ an optional attribute indicating the initial state (either <samp>true</samp> or <samp>false</samp>), used when the <samp>style</samp> attribute has the value <samp>radio</samp> or <samp>toggle</samp>.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="class" type="string" use="required">
+ <annotation>
+ <documentation>
+ name of the fully qualified class that implements <samp>org.eclipse.ui.IViewActionDelegate</samp>.
+ </documentation>
+ <appInfo>
+ <meta.attribute kind="java" basedOn="org.eclipse.ui.IViewActionDelegate"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ <attribute name="enablesFor" type="string">
+ <annotation>
+ <documentation>
+ a value indicating the selection count which must be met to enable the action.
+If this attribute is specified and the condition is met, the action is enabled.
+If the condition is not met, the action is disabled.
+If no attribute is specified, the action is enabled for any number of items selected.
+The following attribute formats are supported:
+ <table border="0" width="80%">
+ <tr>
+ <td valign="top" width="25"></td>
+ <td valign="top" nowrap><b>!</b></td>
+ <td valign="top">- 0 items selected</td>
+ </tr>
+ <tr>
+ <td valign="top" width="25"></td>
+ <td valign="top" nowrap><b>?</b></td>
+ <td valign="top">- 0 or 1 items selected</td>
+ </tr>
+ <tr>
+ <td valign="top" width="25"></td>
+ <td valign="top" nowrap><b>+</b></td>
+ <td valign="top">- 1 or more items selected</td>
+ </tr>
+ <tr>
+ <td valign="top" width="25"></td>
+ <td valign="top" nowrap><b>multiple, 2+</b></td>
+ <td valign="top">- 2 or more items selected</td>
+ </tr>
+ <tr>
+ <td valign="top" width="25"></td>
+ <td valign="top" nowrap><b>n</b></td>
+ <td valign="top">- a precise number of items selected.a precise number of items selected.&nbsp;
+ For example: enablesFor=&quot; 4&quot; enables the action only when 4
+ items are selected</td>
+ </tr>
+ <tr>
+ <td valign="top" width="25"></td>
+ <td valign="top" nowrap><b>*</b></td>
+ <td valign="top">- any number of items selected</td>
+ </tr>
+ </table>
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="parameter">
+ <annotation>
+ <documentation>
+ A parameter element to be used within an IExecutableExtension element. This will be passed as initialization data to the instantiated class.
+ </documentation>
+ </annotation>
+ <complexType>
+ <attribute name="name" type="string" use="required">
+ <annotation>
+ <documentation>
+ the parameter name
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="value" type="string" use="required">
+ <annotation>
+ <documentation>
+ the parameter value
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="class">
+ <annotation>
+ <documentation>
+ The element version of the <code>class</code> attribute. This is used when the class implements <code>org.eclipse.core.runtime.IExecutableExtension</code> and there is parameterized data that you wish used in its initialization.
+ </documentation>
+ </annotation>
+ <complexType>
+ <sequence>
+ <element ref="parameter" minOccurs="0" maxOccurs="unbounded"/>
+ </sequence>
+ <attribute name="class" type="string">
+ <annotation>
+ <documentation>
+ A class that implements <code>org.eclipse.ui.IViewActionDelegate</code>. It may also implement <code>org.eclipse.core.runtime.IExecutableExtension</code>.
+ </documentation>
+ <appInfo>
+ <meta.attribute kind="java"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="examples"/>
+ </appInfo>
+ <documentation>
+ The following is an example of a view action extension:
+<p>
+<pre>
+ <extension point="org.eclipse.ui.viewActions">
+ <viewContribution
+ id="com.xyz.xyzViewC1"
+ targetID="org.eclipse.ui.views.navigator.ResourceNavigator">
+ <menu
+ id="com.xyz.xyzMenu"
+ label="XYZ Menu"
+ path="additions">
+ <separator name="group1"/>
+ </menu>
+ <action
+ id="com.xyz.runXYZ"
+ label="&amp;Run XYZ Tool"
+ menubarPath="com.xyz.xyzMenu/group1"
+ toolbarPath="Normal/additions"
+ style="toggle"
+ state="true"
+ icon="icons/runXYZ.gif"
+ tooltip="Run XYZ Tool"
+ helpContextId="com.xyz.run_action_context"
+ class="com.xyz.actions.RunXYZ">
+ <selection class="org.eclipse.core.resources.IFile" name="*.java"/>
+ </action>
+ </viewContribution>
+ </extension>
+</pre>
+</p>
+<p>
+In the example above, the specified action will only enable for a single selection (<samp>enablesFor</samp> attribute). In addition, the object in the selection must be a Java file resource.
+</p>
+<p>
+The following is an other example of a view action extension:
+</p>
+<p>
+<pre>
+ <extension point="org.eclipse.ui.viewActions">
+ <viewContribution
+ id="com.xyz.xyzViewC1"
+ targetID="org.eclipse.ui.views.navigator.ResourceNavigator">
+ <menu
+ id="com.xyz.xyzMenu"
+ label="XYZ Menu"
+ path="additions">
+ <separator name="group1"/>
+ </menu>
+ <action
+ id="com.xyz.runXYZ2"
+ label="&amp;Run XYZ2 Tool"
+ menubarPath="com.xyz.xyzMenu/group1"
+ style="push"
+ icon="icons/runXYZ2.gif"
+ tooltip="Run XYZ2 Tool"
+ helpContextId="com.xyz.run_action_context2"
+ class="com.xyz.actions.RunXYZ2">
+ <enablement>
+ <and>
+ <objectClass name="org.eclipse.core.resources.IFile"/>
+ <not>
+ <objectState name="extension" value="java"/>
+ </not>
+ </and>
+ </enablement>
+ </action>
+ </viewContribution>
+ </extension>
+</pre>
+</p>
+<p>
+In the example above, the specified action will appear as a menu item. The action is enabled if the selection contains no Java file resources.
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="apiInfo"/>
+ </appInfo>
+ <documentation>
+ The value of the <samp>class</samp> attribute must be a fully qualified name of a Java class that implements <samp>org.eclipse.ui.IViewActionDelegate</samp>. This class is loaded as late as possible to avoid loading the entire plug-in before it is really needed.
+<p>
+The interface <samp>org.eclipse.ui.IViewActionDelegate</samp> extends <samp>org.eclipse.ui.IActionDelegate</samp> and adds an additional method that allows the
+delegate to initialize with the view instance it is contributing into.
+</p>
+<p>
+This extension point can be used to contribute actions into menus previously created by the target view. Omitting the menu path attribute will result in adding the new menu or action at the end of the pulldown menu.
+</p>
+<p>
+The enablement criteria for an action extension is initially defined by <samp>enablesFor</samp>, and also either <samp>selection</samp> or <samp>enablement</samp>. However, once the action delegate has been instantiated, it may control the action enable state directly within its <samp>selectionChanged</samp> method.
+</p>
+<p>
+Action and menu labels may contain special characters that encode mnemonics using the following rules:
+<ol>
+<li>
+Mnemonics are specified using the ampersand ('&amp;') character in front
+of a selected character in the translated text. Since ampersand is not
+allowed in XML strings, use <samp>&amp;amp;</samp> character entity.</li>
+</ol>
+If two or more actions are contributed to a menu or toolbar by a single extension the actions will appear in the reverse order of how they are listed in the plugin.xml file. This behavior is admittedly unintuitive. However, it was discovered after the Eclipse Platform API was frozen. Changing the behavior now would break every plug-in which relies upon the existing behavior.
+<p>
+The <samp>selection</samp> and <samp>enablement</samp> elements are mutually exclusive. The <samp>enablement</samp> element can replace the <samp>selection</samp> element using the sub-elements <samp>objectClass</samp> and <samp>objectState</samp>. For example, the following:
+<pre>
+ <selection
+ class="org.eclipse.core.resources.IFile"
+ name="*.java">
+ </selection>
+</pre>
+can be expressed using:
+<pre>
+ <enablement>
+ <and>
+ <objectClass name="org.eclipse.core.resources.IFile"/>
+ <objectState name="extension" value="java"/>
+ </and>
+ </enablement>
+</pre>
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="implementation"/>
+ </appInfo>
+ <documentation>
+ Each view normally comes with a number of standard items on the pulldown menu and local toolbar. Additions from other plug-ins will be appended to the standard complement.
+ </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/views.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/views.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/views.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/views.exsd Thu Dec 27 09:44:07 2007
@@ -0,0 +1,300 @@
+<?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="views" name="Views"/>
+ </appInfo>
+ <documentation>
+ This extension point is used to define additional views
+for the workbench. A view is a visual component
+within a workbench page. It is typically used to
+navigate a hierarchy of information (like the workspace),
+open an editor, or display properties for
+the active editor. The user can make a view
+visible from the Window > Show View menu or close it from the
+view local title bar.
+<p>
+In order to reduce the visual clutter in the Show View Dialog, views should be grouped using categories.
+ </documentation>
+ </annotation>
+
+ <element name="extension">
+ <complexType>
+ <choice minOccurs="0" maxOccurs="unbounded">
+ <element ref="category"/>
+ <element ref="view"/>
+ <element ref="stickyView"/>
+ </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 will be used to identify this category
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="name" type="string" use="required">
+ <annotation>
+ <documentation>
+ a translatable name that will be used in the UI for this category
+ </documentation>
+ <appInfo>
+ <meta.attribute translatable="true"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ <attribute name="parentCategory" type="string">
+ <annotation>
+ <documentation>
+ an optional path composed of category IDs separated by '/'. This
+allows the creation of a hierarchy of categories.
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="view">
+ <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 view
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="name" type="string" use="required">
+ <annotation>
+ <documentation>
+ a translatable name that will be used in the UI for this view
+ </documentation>
+ <appInfo>
+ <meta.attribute translatable="true"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ <attribute name="category" type="string">
+ <annotation>
+ <documentation>
+ an optional attribute that is composed of the category IDs separated
+by '/'. Each referenced category must be declared in a corresponding category element.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="class" type="string" use="required">
+ <annotation>
+ <documentation>
+ a fully qualified name of the class that implements
+<samp>org.eclipse.ui.IViewPart</samp>. A common practice
+is to subclass <samp>org.eclipse.ui.part.ViewPart</samp>
+in order to inherit the default functionality.
+ </documentation>
+ <appInfo>
+ <meta.attribute kind="java" basedOn="org.eclipse.ui.part.ViewPart"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ <attribute name="icon" type="string">
+ <annotation>
+ <documentation>
+ a relative name of the icon that will
+be associated with the view.
+ </documentation>
+ <appInfo>
+ <meta.attribute kind="resource"/>
+ </appInfo>
+ </annotation>
+ </attribute>
+ <attribute name="fastViewWidthRatio" type="string">
+ <annotation>
+ <documentation>
+ the percentage of the width of the workbench that the view will take up as an active fast view.
+This must be defined as a floating point value and lie between 0.05 and 0.95.
+If no value is supplied, a default ratio will be used.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="allowMultiple" type="boolean">
+ <annotation>
+ <documentation>
+ flag indicating whether this view allows multiple instances to be created using IWorkbenchPage.showView(String id, String secondaryId). 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 view.
+ </documentation>
+ </annotation>
+ </element>
+
+ <element name="stickyView">
+ <annotation>
+ <documentation>
+ A sticky view is a view that will appear by default across all perspectives in a window once it is opened. Its initial placement is governemed by the location attribute, but nothing prevents it from being moved or closed by the user. Use of this element will only cause a placeholder for the view to be created, it will not show the view. Please note that usage of this element should be done with great care and should only be applied to views that truely have a need to live across perspectives.
+
+Since 3.0
+ </documentation>
+ </annotation>
+ <complexType>
+ <attribute name="id" type="string" use="required">
+ <annotation>
+ <documentation>
+ the id of the view to be made sticky.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="location">
+ <annotation>
+ <documentation>
+ optional attribute that specifies the location of the sticky view relative to the editor area. If absent, the view will be docked to the right of the editor area.
+ </documentation>
+ </annotation>
+ <simpleType>
+ <restriction base="string">
+ <enumeration value="RIGHT">
+ </enumeration>
+ <enumeration value="LEFT">
+ </enumeration>
+ <enumeration value="TOP">
+ </enumeration>
+ <enumeration value="BOTTOM">
+ </enumeration>
+ </restriction>
+ </simpleType>
+ </attribute>
+ <attribute name="closeable" type="boolean">
+ <annotation>
+ <documentation>
+ optional attribute that specifies wether the view should be closeable. If absent it will be closeable.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="moveable" type="boolean">
+ <annotation>
+ <documentation>
+ optional attribute that specifies wether the view should be moveable. If absent it will be moveable.
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="examples"/>
+ </appInfo>
+ <documentation>
+ The following is an example of the extension point:
+<p>
+<pre>
+ <extension point="org.eclipse.ui.views">
+ <category
+ id="com.xyz.views.XYZviews"
+ name="XYZ"/>
+ <view
+ id="com.xyz.views.XYZView"
+ name="XYZ View"
+ category="com.xyz.views.XYZviews"
+ class="com.xyz.views.XYZView"
+ icon="icons/XYZ.gif"/>
+ </extension>
+</pre>
+</p>
+The following is an example of a sticky view declaration:
+<p>
+<pre>
+ <extension point="org.eclipse.ui.views">
+ <stickyView
+ id="com.xyz.views.XYZView" />
+ </extension>
+</pre>
+</p>
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="apiInfo"/>
+ </appInfo>
+ <documentation>
+ The value of the <samp>class</samp> attribute must be a
+fully qualified name of the class that implements
+<samp>org.eclipse.ui.IViewPart</samp>. It is common
+practice to subclass <samp>org.eclipse.ui.part.ViewPart</samp>
+ when developing a new view.
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="implementation"/>
+ </appInfo>
+ <documentation>
+ The Eclipse Platform provides a number of standard views including Navigator, Properties, Outline and Tasks. From the user point of view, these views are no different from any other view provided by the plug-ins. All the views can be shown from the "Show View" submenu of the "Window" menu. The position of a view is persistent: it is saved when the view is closed and restored when the view is reopened in a single session. The position is also persisted between workbench sessions.
+ </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>