Skip to main content
aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--org.eclipse.ui.cheatsheets/schema/cheatSheetContent.exsd (renamed from org.eclipse.ui.cheatsheets/schema/org.eclipse.ui.cheatsheets.cheatSheetContent.exsd)362
-rw-r--r--org.eclipse.ui.cheatsheets/schema/cheatSheetItemExtension.exsd (renamed from org.eclipse.ui.cheatsheets/schema/org.eclipse.ui.cheatsheets.cheatSheetItemExtension.exsd)290
-rw-r--r--org.eclipse.ui.intro/schema/config.exsd (renamed from org.eclipse.ui.intro/schema/org.eclipse.ui.intro.config.exsd)472
-rw-r--r--org.eclipse.ui.intro/schema/configExtension.exsd (renamed from org.eclipse.ui.intro/schema/org.eclipse.ui.intro.configExtension.exsd)402
4 files changed, 763 insertions, 763 deletions
diff --git a/org.eclipse.ui.cheatsheets/schema/org.eclipse.ui.cheatsheets.cheatSheetContent.exsd b/org.eclipse.ui.cheatsheets/schema/cheatSheetContent.exsd
index 2f4f168cf..db35f0dc1 100644
--- a/org.eclipse.ui.cheatsheets/schema/org.eclipse.ui.cheatsheets.cheatSheetContent.exsd
+++ b/org.eclipse.ui.cheatsheets/schema/cheatSheetContent.exsd
@@ -1,166 +1,166 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<!-- Schema file written by PDE -->
-<schema targetNamespace="org.eclipse.ui.cheatsheets">
-<annotation>
- <appInfo>
- <meta.schema plugin="org.eclipse.ui.cheatsheets" id="cheatSheetContent" name="Cheat Sheet Content"/>
- </appInfo>
- <documentation>
+<?xml version='1.0' encoding='UTF-8'?>
+<!-- Schema file written by PDE -->
+<schema targetNamespace="org.eclipse.ui.cheatsheets">
+<annotation>
+ <appInfo>
+ <meta.schema plugin="org.eclipse.ui.cheatsheets" id="cheatSheetContent" name="Cheat Sheet Content"/>
+ </appInfo>
+ <documentation>
This extension point is used to register cheat sheet content contributions. Cheat sheets appear as choices from the &quot;Help&quot; menu or from within the cheat sheet view, and are typically used to aid a user through a series of comlex tasks to accomplish an overall goal.
&lt;p&gt;
The cheat sheets are organized into categories which usually reflect a particular problem domain. For instance, a Java oriented plug-in may define a category called &quot;Java&quot; which is appropriate for cheat sheets that would aid a user with any of the Java tools. The categories defined by one plug-in can be referenced by other plug-ins using the category attribute of a cheatsheet element. Uncategorized cheat sheets, as well as cheat sheets with invalid category paths, will end up in an &quot;Other&quot; category.
&lt;p&gt;
-Cheat sheets may optionally specify a description subelement whose body should contain short text about the cheat sheet.
- </documentation>
- </annotation>
-
- <element name="extension">
- <complexType>
- <choice minOccurs="0" maxOccurs="unbounded">
- <element ref="category"/>
- <element ref="cheatsheet"/>
- </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>
- </annotation>
- </attribute>
- </complexType>
- </element>
-
- <element name="category">
- <annotation>
- <appInfo>
- <meta.element labelAttribute="name"/>
- </appInfo>
- <documentation>
+Cheat sheets may optionally specify a description subelement whose body should contain short text about the cheat sheet.
+ </documentation>
+ </annotation>
+
+ <element name="extension">
+ <complexType>
+ <choice minOccurs="0" maxOccurs="unbounded">
+ <element ref="category"/>
+ <element ref="cheatsheet"/>
+ </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>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="category">
+ <annotation>
+ <appInfo>
+ <meta.element labelAttribute="name"/>
+ </appInfo>
+ <documentation>
A category element in the cheatsheetContent extension point creates a new category in the cheat sheet menu.
The cheat sheet menu is available from the help menu in the workbench.
If a new category is specified, cheat sheets may be targeted to that category and will appear under it in the
-cheat sheet selection dialog.
- </documentation>
- </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>
- </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="cheatsheet">
- <annotation>
- <appInfo>
- <meta.element labelAttribute="name"/>
- </appInfo>
- <documentation>
+cheat sheet selection dialog.
+ </documentation>
+ </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>
+ </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="cheatsheet">
+ <annotation>
+ <appInfo>
+ <meta.element labelAttribute="name"/>
+ </appInfo>
+ <documentation>
A cheatsheet element is put into the cheatsheetContent extension point if there is a cheat sheet to be contributed to the
workbench. A cheat sheet element must specify an id, a translatable name to appear in the selection options, a category id
to specify which category this cheat sheet will be included in, and a content file.
-The cheat sheet content file is an XML file that describes the steps and actions that the cheat sheet has.
- </documentation>
- </annotation>
- <complexType>
- <sequence>
- <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 cheat sheet
- </documentation>
- </annotation>
- </attribute>
- <attribute name="name" type="string" use="required">
- <annotation>
- <documentation>
- a translatable name of the cheat sheet that will be used in the help menu and the selection dialog box
- </documentation>
- </annotation>
- </attribute>
- <attribute name="category" type="string">
- <annotation>
- <documentation>
+The cheat sheet content file is an XML file that describes the steps and actions that the cheat sheet has.
+ </documentation>
+ </annotation>
+ <complexType>
+ <sequence>
+ <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 cheat sheet
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="name" type="string" use="required">
+ <annotation>
+ <documentation>
+ a translatable name of the cheat sheet that will be used in the help menu and the selection dialog box
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="category" type="string">
+ <annotation>
+ <documentation>
a slash-delimited path (&apos;/&apos;) 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 &quot;Other&quot; category.
- </documentation>
- </annotation>
- </attribute>
- <attribute name="contentFile" type="string">
- <annotation>
- <documentation>
+added to the &quot;Other&quot; category.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="contentFile" type="string">
+ <annotation>
+ <documentation>
the path of a cheat sheet content file. The content file is an XML file that contains the specifics of the cheat sheet (&lt;a href=&quot;cheatSheetContentFileSpec.html&quot;&gt;cheat sheet content file format specification)&lt;/a&gt;.
-The content file is parsed at run time by the cheat sheet framework. Based on the settings in this file, a certain number of steps, actions, descriptions, and help links are shown to the user when the cheat sheet is opened. The path is interpreted as relative to the plug-in that declares the extension; the path may include special variables. In particular, use &quot;$nl$&quot; as the first segment of the path to indicate that there are locale-specific translations of the content file in subdirectories below &quot;nl/&quot;. For more detail about the specail variables, you can read the Java API document for &lt;a href=&quot;../api/org/eclipse/core/runtime/Platform.html#find&quot;&gt;Platform.find&lt;/a&gt;.
- </documentation>
- </annotation>
- </attribute>
- <attribute name="listener" type="string">
- <annotation>
- <documentation>
- listener is a fully qualified name of a Java class which must subclass &lt;code&gt;org.eclipse.ui.cheatsheets.CheatSheetListener&lt;/code&gt;.
- </documentation>
- </annotation>
- </attribute>
- </complexType>
- </element>
-
- <element name="description" type="string">
- <annotation>
- <documentation>
- a short description of the cheat sheet
- </documentation>
- </annotation>
- </element>
-
- <annotation>
- <appInfo>
- <meta.section type="since"/>
- </appInfo>
- <documentation>
- 3.0
- </documentation>
- </annotation>
-
- <annotation>
- <appInfo>
- <meta.section type="examples"/>
- </appInfo>
- <documentation>
+The content file is parsed at run time by the cheat sheet framework. Based on the settings in this file, a certain number of steps, actions, descriptions, and help links are shown to the user when the cheat sheet is opened. The path is interpreted as relative to the plug-in that declares the extension; the path may include special variables. In particular, use &quot;$nl$&quot; as the first segment of the path to indicate that there are locale-specific translations of the content file in subdirectories below &quot;nl/&quot;. For more detail about the specail variables, you can read the Java API document for &lt;a href=&quot;../api/org/eclipse/core/runtime/Platform.html#find&quot;&gt;Platform.find&lt;/a&gt;.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="listener" type="string">
+ <annotation>
+ <documentation>
+ listener is a fully qualified name of a Java class which must subclass &lt;code&gt;org.eclipse.ui.cheatsheets.CheatSheetListener&lt;/code&gt;.
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="description" type="string">
+ <annotation>
+ <documentation>
+ a short description of the cheat sheet
+ </documentation>
+ </annotation>
+ </element>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="since"/>
+ </appInfo>
+ <documentation>
+ 3.0
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="examples"/>
+ </appInfo>
+ <documentation>
Here is a sample usage of the cheatSheetContent extension point:
&lt;p&gt;
&lt;pre&gt;
@@ -180,36 +180,36 @@ The content file is parsed at run time by the cheat sheet framework. Based on th
&lt;/cheatsheet&gt;
&lt;/extension&gt;
&lt;/pre&gt;
-&lt;/p&gt;
- </documentation>
- </annotation>
-
- <annotation>
- <appInfo>
- <meta.section type="apiInfo"/>
- </appInfo>
- <documentation>
- For further details see the spec for the org.eclipse.ui.cheatsheets API package.
- </documentation>
- </annotation>
-
- <annotation>
- <appInfo>
- <meta.section type="implementation"/>
- </appInfo>
- <documentation>
- There are no built-in cheat sheets.
- </documentation>
- </annotation>
-
- <annotation>
- <appInfo>
- <meta.section type="copyright"/>
- </appInfo>
- <documentation>
+&lt;/p&gt;
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="apiInfo"/>
+ </appInfo>
+ <documentation>
+ For further details see the spec for the org.eclipse.ui.cheatsheets API package.
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="implementation"/>
+ </appInfo>
+ <documentation>
+ There are no built-in cheat sheets.
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="copyright"/>
+ </appInfo>
+ <documentation>
Copyright (c) 2004 IBM Corporation and others.
-All rights reserved. This program and the accompanying materials are made available under the terms of the Common Public License v1.0 which accompanies this distribution, and is available at &lt;a href=&quot;http://www.eclipse.org/legal/cpl-v10.html&quot;&gt;http://www.eclipse.org/legal/cpl-v10.html&lt;/a&gt;
- </documentation>
- </annotation>
-
-</schema>
+All rights reserved. This program and the accompanying materials are made available under the terms of the Common Public License v1.0 which accompanies this distribution, and is available at &lt;a href=&quot;http://www.eclipse.org/legal/cpl-v10.html&quot;&gt;http://www.eclipse.org/legal/cpl-v10.html&lt;/a&gt;
+ </documentation>
+ </annotation>
+
+</schema>
diff --git a/org.eclipse.ui.cheatsheets/schema/org.eclipse.ui.cheatsheets.cheatSheetItemExtension.exsd b/org.eclipse.ui.cheatsheets/schema/cheatSheetItemExtension.exsd
index 9f5333e0c..8773bb9db 100644
--- a/org.eclipse.ui.cheatsheets/schema/org.eclipse.ui.cheatsheets.cheatSheetItemExtension.exsd
+++ b/org.eclipse.ui.cheatsheets/schema/cheatSheetItemExtension.exsd
@@ -1,145 +1,145 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<!-- Schema file written by PDE -->
-<schema targetNamespace="org.eclipse.ui.cheatsheets">
-<annotation>
- <appInfo>
- <meta.schema plugin="org.eclipse.ui.cheatsheets" id="cheatSheetItemExtension" name="Cheat Sheet Item Extension"/>
- </appInfo>
- <documentation>
- This extension point should be used when an extra button needs to be added to a step in the cheat sheet.
-You can put a new attribute into the &quot;item&quot; tag in the cheat sheet content file, and when that value is read by the cheat sheet framework,
-it will check to see if there is a class registered through this extension point that will handle this attribute. The attribute name found in the
-cheat sheet content file is matched against all of the values found in the &quot;itemAttribute&quot; attribute of all of the registered cheatsheetItemExtension point implementations. If there is a match, the class specified to handle this item attribute is loaded by the cheat sheet framework and is called to handle the attribute specified in the cheat sheet content file.
-
-After having parsed the value of the item attribute, the class remains available to the cheat sheets framework. When the item is rendered for the cheat sheets view, the class is once again called to handle the addition of components to a Composite. The items that are added to this composite are displayed in the cheat sheet step (currently, beside the help icon). It is displayed only for the step that is described by the &quot;item&quot; tag that the attribute appeared in the cheat sheet content file.
-
-The suggested use of this extension point is adding a small (16x16) button with a graphic that opens a dialog box when pressed.
- </documentation>
- </annotation>
-
- <element name="extension">
- <complexType>
- <choice minOccurs="0" maxOccurs="unbounded">
- <element ref="itemExtension"/>
- </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>
- </annotation>
- </attribute>
- </complexType>
- </element>
-
- <element name="itemExtension">
- <annotation>
- <appInfo>
- <meta.element labelAttribute="name"/>
- </appInfo>
- <documentation>
- Use this item extension to add elements to cheat sheet steps. You can use this extension point to add icons and buttons (currently, beside the
-help icon) for a step in the cheat sheet.
-You specify the name of an attribute that you will put into the cheat sheet item tag. You also specify a class that will handle the parsing of the attribute value from the cheat sheet content file when the cheat sheet is loaded. The attribute valuemust be a string. The specified class must subclass &lt;code&gt;org.eclipse.ui.cheatsheets.AbstractItemExtensionElement&lt;/code&gt;. After the cheat sheet content file is parsed and loaded, the class specified in the extension point is called again through the interface to add graphics or buttons to the step in the cheat sheet (currently, next to the help button).
- </documentation>
- </annotation>
- <complexType>
- <attribute name="itemAttribute" type="string" use="required">
- <annotation>
- <documentation>
- This attribute value must be the string value of an attribute name that is put into an item tag in the cheat sheet content file. If this attribute string matches an attribute parsed from the item tag in the cheat sheet content file, the class specified will be loaded and will be called to parse the full value of the attribute using the w3 DOM specification. It will later be called to add controls to a Composite, and the added components (usually graphics or buttons) will appear in the step of the cheat sheet for the item specified (currently, beside the help icon for that step).
- </documentation>
- </annotation>
- </attribute>
- <attribute name="class" type="string" use="required">
- <annotation>
- <documentation>
- The fully qualified class name of the class that subclasses &lt;code&gt;org.eclipse.ui.cheatsheet.AbstractItemExtensionElement&lt;/code&gt; to handle unknown attributes in the cheat sheet content file and extend the steps in the cheat sheet. The class must be public, and have a public 1-argument constructor that accepts the attribute name
-(a &lt;code&gt;String&lt;/code&gt;).
- </documentation>
- </annotation>
- </attribute>
- </complexType>
- </element>
-
- <annotation>
- <appInfo>
- <meta.section type="since"/>
- </appInfo>
- <documentation>
- 3.0
- </documentation>
- </annotation>
-
- <annotation>
- <appInfo>
- <meta.section type="examples"/>
- </appInfo>
- <documentation>
- Here is an example implementation of this extension point:
-&lt;p&gt;
-&lt;pre&gt;
-&lt;extension point=&quot;org.eclipse.ui.cheatsheets.cheatSheetItemExtension&quot;&gt;
- &lt;itemExtension
- itemAttribute=&quot;xyzButton&quot;
- class=&quot;com.example.HandleParsingAndAddButton&quot;&gt;
- &lt;/itemExtension&gt;
-&lt;/extension&gt;
-&lt;/pre&gt;
-&lt;/p&gt;
-And here is the item attribute for that extension:
-&lt;p&gt;
-&lt;pre&gt;
-&lt;item title=&quot;XYZ Title&quot; xyzButton=&quot;/icon/button.gif&quot;&gt;
-&lt;/pre&gt;
-&lt;/p&gt;
-Note that the value of the attribute in the item tag can be ANYTHING. It can be anything because
-the class that parses that attribute is the class HandleParsingAndAddButton, which in this example parses
-a string /icon/button.gif from the attribute. It later will use that info to load the gif and use it as the icon
-for a new button.
- </documentation>
- </annotation>
-
- <annotation>
- <appInfo>
- <meta.section type="apiInfo"/>
- </appInfo>
- <documentation>
- See the Javadoc information for org.eclipse.ui.cheatsheets.AbstractItemExtensionElement for API details.
- </documentation>
- </annotation>
-
- <annotation>
- <appInfo>
- <meta.section type="implementation"/>
- </appInfo>
- <documentation>
- There is no supplied implementation at this time.
- </documentation>
- </annotation>
-
- <annotation>
- <appInfo>
- <meta.section type="copyright"/>
- </appInfo>
- <documentation>
- Copyright (c) 2004 IBM Corporation and others.
-All rights reserved. This program and the accompanying materials are made available under the terms of the Common Public License v1.0 which accompanies this distribution, and is available at &lt;a href=&quot;http://www.eclipse.org/legal/cpl-v10.html&quot;&gt;http://www.eclipse.org/legal/cpl-v10.html&lt;/a&gt;
- </documentation>
- </annotation>
-
-</schema>
+<?xml version='1.0' encoding='UTF-8'?>
+<!-- Schema file written by PDE -->
+<schema targetNamespace="org.eclipse.ui.cheatsheets">
+<annotation>
+ <appInfo>
+ <meta.schema plugin="org.eclipse.ui.cheatsheets" id="cheatSheetItemExtension" name="Cheat Sheet Item Extension"/>
+ </appInfo>
+ <documentation>
+ This extension point should be used when an extra button needs to be added to a step in the cheat sheet.
+You can put a new attribute into the &quot;item&quot; tag in the cheat sheet content file, and when that value is read by the cheat sheet framework,
+it will check to see if there is a class registered through this extension point that will handle this attribute. The attribute name found in the
+cheat sheet content file is matched against all of the values found in the &quot;itemAttribute&quot; attribute of all of the registered cheatsheetItemExtension point implementations. If there is a match, the class specified to handle this item attribute is loaded by the cheat sheet framework and is called to handle the attribute specified in the cheat sheet content file.
+
+After having parsed the value of the item attribute, the class remains available to the cheat sheets framework. When the item is rendered for the cheat sheets view, the class is once again called to handle the addition of components to a Composite. The items that are added to this composite are displayed in the cheat sheet step (currently, beside the help icon). It is displayed only for the step that is described by the &quot;item&quot; tag that the attribute appeared in the cheat sheet content file.
+
+The suggested use of this extension point is adding a small (16x16) button with a graphic that opens a dialog box when pressed.
+ </documentation>
+ </annotation>
+
+ <element name="extension">
+ <complexType>
+ <choice minOccurs="0" maxOccurs="unbounded">
+ <element ref="itemExtension"/>
+ </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>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="itemExtension">
+ <annotation>
+ <appInfo>
+ <meta.element labelAttribute="name"/>
+ </appInfo>
+ <documentation>
+ Use this item extension to add elements to cheat sheet steps. You can use this extension point to add icons and buttons (currently, beside the
+help icon) for a step in the cheat sheet.
+You specify the name of an attribute that you will put into the cheat sheet item tag. You also specify a class that will handle the parsing of the attribute value from the cheat sheet content file when the cheat sheet is loaded. The attribute valuemust be a string. The specified class must subclass &lt;code&gt;org.eclipse.ui.cheatsheets.AbstractItemExtensionElement&lt;/code&gt;. After the cheat sheet content file is parsed and loaded, the class specified in the extension point is called again through the interface to add graphics or buttons to the step in the cheat sheet (currently, next to the help button).
+ </documentation>
+ </annotation>
+ <complexType>
+ <attribute name="itemAttribute" type="string" use="required">
+ <annotation>
+ <documentation>
+ This attribute value must be the string value of an attribute name that is put into an item tag in the cheat sheet content file. If this attribute string matches an attribute parsed from the item tag in the cheat sheet content file, the class specified will be loaded and will be called to parse the full value of the attribute using the w3 DOM specification. It will later be called to add controls to a Composite, and the added components (usually graphics or buttons) will appear in the step of the cheat sheet for the item specified (currently, beside the help icon for that step).
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="class" type="string" use="required">
+ <annotation>
+ <documentation>
+ The fully qualified class name of the class that subclasses &lt;code&gt;org.eclipse.ui.cheatsheet.AbstractItemExtensionElement&lt;/code&gt; to handle unknown attributes in the cheat sheet content file and extend the steps in the cheat sheet. The class must be public, and have a public 1-argument constructor that accepts the attribute name
+(a &lt;code&gt;String&lt;/code&gt;).
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="since"/>
+ </appInfo>
+ <documentation>
+ 3.0
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="examples"/>
+ </appInfo>
+ <documentation>
+ Here is an example implementation of this extension point:
+&lt;p&gt;
+&lt;pre&gt;
+&lt;extension point=&quot;org.eclipse.ui.cheatsheets.cheatSheetItemExtension&quot;&gt;
+ &lt;itemExtension
+ itemAttribute=&quot;xyzButton&quot;
+ class=&quot;com.example.HandleParsingAndAddButton&quot;&gt;
+ &lt;/itemExtension&gt;
+&lt;/extension&gt;
+&lt;/pre&gt;
+&lt;/p&gt;
+And here is the item attribute for that extension:
+&lt;p&gt;
+&lt;pre&gt;
+&lt;item title=&quot;XYZ Title&quot; xyzButton=&quot;/icon/button.gif&quot;&gt;
+&lt;/pre&gt;
+&lt;/p&gt;
+Note that the value of the attribute in the item tag can be ANYTHING. It can be anything because
+the class that parses that attribute is the class HandleParsingAndAddButton, which in this example parses
+a string /icon/button.gif from the attribute. It later will use that info to load the gif and use it as the icon
+for a new button.
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="apiInfo"/>
+ </appInfo>
+ <documentation>
+ See the Javadoc information for org.eclipse.ui.cheatsheets.AbstractItemExtensionElement for API details.
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="implementation"/>
+ </appInfo>
+ <documentation>
+ There is no supplied implementation at this time.
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="copyright"/>
+ </appInfo>
+ <documentation>
+ Copyright (c) 2004 IBM Corporation and others.
+All rights reserved. This program and the accompanying materials are made available under the terms of the Common Public License v1.0 which accompanies this distribution, and is available at &lt;a href=&quot;http://www.eclipse.org/legal/cpl-v10.html&quot;&gt;http://www.eclipse.org/legal/cpl-v10.html&lt;/a&gt;
+ </documentation>
+ </annotation>
+
+</schema>
diff --git a/org.eclipse.ui.intro/schema/org.eclipse.ui.intro.config.exsd b/org.eclipse.ui.intro/schema/config.exsd
index 387dd8364..61a0cd59a 100644
--- a/org.eclipse.ui.intro/schema/org.eclipse.ui.intro.config.exsd
+++ b/org.eclipse.ui.intro/schema/config.exsd
@@ -1,236 +1,236 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<!-- Schema file written by PDE -->
-<schema targetNamespace="org.eclipse.ui.intro">
-<annotation>
- <appInfo>
- <meta.schema plugin="org.eclipse.ui.intro" id="config" name="Intro Part Configuration"/>
- </appInfo>
- <documentation>
- This extension point is used to register an intro configuration. This configuration provides presentation implementations and content for a given intro contribution. An intro appears when the workbench is first launched and as a choice from the &quot;Help&quot; menu. The intro is typically used to introduce a user to a product built on Eclipse.
-&lt;p&gt;
-The intros are organized into pages which usually reflect a particular category of introductory material. For instance, a What&apos;s New page may introduce new concepts or functionality since previous versions. The content defined by one intro configuration can be referenced and extended from other plug-ins using the &lt;a href=&quot;org.eclipse.ui.intro.configExtension.exsd&quot;&gt;org.eclipse.ui.intro.configExtension&lt;/a&gt; extension point.
-&lt;p&gt;
-todo - add other APIs here such as IStandbyPart
- </documentation>
- </annotation>
-
- <include schemaLocation="IntroContent.exsd"/>
-
- <element name="extension">
- <complexType>
- <sequence>
- <element ref="config" 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>
- </annotation>
- </attribute>
- </complexType>
- </element>
-
- <element name="config">
- <annotation>
- <documentation>
- A config element can be used to configure a customizable Intro Part. A config element must specify an id, an introId, and a content file.
-The intro content file is an XML file that describes the pages, groups and links that the intro has.
- </documentation>
- </annotation>
- <complexType>
- <sequence>
- <element ref="presentation"/>
- </sequence>
- <attribute name="introId" type="string" use="required">
- <annotation>
- <documentation>
- the id of an intro part contribution that this configuration will be associated with.
- </documentation>
- </annotation>
- </attribute>
- <attribute name="id" type="string" use="required">
- <annotation>
- <documentation>
- a unique name that can be used to identify this intro configuration
- </documentation>
- </annotation>
- </attribute>
- <attribute name="content" type="string" use="required">
- <annotation>
- <documentation>
- an intro content file. The content file is an XML file that contains the specifics of the intro (&lt;a href=&quot;introContentFileSpec.html&quot;&gt;intro content file format specification)&lt;/a&gt;.
-The content file is parsed at run time by the intro framework. Based on the settings in this file, a certain number of pages, groups, and links are shown to the user when the intro is opened.
- </documentation>
- </annotation>
- </attribute>
- </complexType>
- </element>
-
- <element name="presentation">
- <annotation>
- <documentation>
- Presentation element that defines all the possible implementations of an intro part&apos;s presentation. It can have one or more implementation defined in it. Only one implementation will be chosen at startup, based the os/ws attributes of the implementations. Otherwise, the first one with no os/ws attributes defined will be chosen.
- </documentation>
- </annotation>
- <complexType>
- <sequence>
- <element ref="implementation" minOccurs="1" maxOccurs="unbounded"/>
- </sequence>
- <attribute name="home-page-id" type="string" use="required">
- <annotation>
- <documentation>
- the id of the home (root) page.
- </documentation>
- </annotation>
- </attribute>
- <attribute name="standby-page-id" type="string">
- <annotation>
- <documentation>
- an optional attribute to define the id of the standby page. The standby page will be shown to the user when the Intro is set to standby.
- </documentation>
- </annotation>
- </attribute>
- </complexType>
- </element>
-
- <element name="implementation">
- <annotation>
- <documentation>
- The presentation of the Platform&apos;s out of the box experience has two implementations. One of them is SWT Browser based, while the other is UI Forms based. The customizable intro part can be configured to pick one of those two presentation based on the current OS and WS. The type of the implementation can be swt or html.
- </documentation>
- </annotation>
- <complexType>
- <sequence>
- <element ref="head" minOccurs="0" maxOccurs="1"/>
- </sequence>
- <attribute name="kind" use="required">
- <annotation>
- <documentation>
-
- </documentation>
- </annotation>
- <simpleType>
- <restriction base="string">
- <enumeration value="swt">
- </enumeration>
- <enumeration value="html">
- </enumeration>
- </restriction>
- </simpleType>
- </attribute>
- <attribute name="style" type="string">
- <annotation>
- <documentation>
- The shared style that will be applied to all pages presented by this intro presentation implementation.
- </documentation>
- </annotation>
- </attribute>
- <attribute name="os" type="string">
- <annotation>
- <documentation>
- os string used when choosing the presentation&apos;s implementation based on current OS. eg: win32,linux (todo - where are the valid OS strings used by Eclipse defined?)
- </documentation>
- </annotation>
- </attribute>
- <attribute name="ws" type="string">
- <annotation>
- <documentation>
- ws string used when choosing the presentation&apos;s implementation based on current WS. eg: win32,gtk (todo - where are the valid WS strings used by Eclipse defined? Should we expand WS to windowing system?)
- </documentation>
- </annotation>
- </attribute>
- </complexType>
- </element>
-
- <annotation>
- <appInfo>
- <meta.section type="since"/>
- </appInfo>
- <documentation>
- 3.0
- </documentation>
- </annotation>
-
- <annotation>
- <appInfo>
- <meta.section type="examples"/>
- </appInfo>
- <documentation>
- Here is a sample usage of the config extension point.
-
-&lt;extension id=&quot;intro&quot; point=&quot;org.eclipse.ui.intro.config&quot;&gt;
- &lt;config
- introId=&quot;com.org.xyz.intro&quot;
- id=&quot;com.org.xyz.introConfig&quot;
- content=&quot;introContent.xml&quot;&gt;
- &lt;presentation
- home-page-id=&quot;root&quot;
- title=&quot;%intro.title&quot;&gt;
- &lt;implementation
- ws=&quot;win32&quot;
- style=&quot;css/shared.css&quot;
- class=&quot;org.eclipse.ui.internal.intro.impl.presentations.BrowserIntroPartImplementation&quot;
- os=&quot;win32&quot;&gt;
- &lt;/implementation&gt;
- &lt;implementation
- style=&quot;css/shared_swt.properties&quot;
- class=&quot;org.eclipse.ui.internal.intro.impl.presentations.FormIntroPartImplementation&quot;&gt;
- &lt;/implementation&gt;
- &lt;/presentation&gt;
- &lt;/config&gt;
-&lt;/extension&gt;
- </documentation>
- </annotation>
-
- <annotation>
- <appInfo>
- <meta.section type="apiInfo"/>
- </appInfo>
- <documentation>
- [Enter API information here.]
- </documentation>
- </annotation>
-
- <annotation>
- <appInfo>
- <meta.section type="implementation"/>
- </appInfo>
- <documentation>
- The intro contributed by the org.eclipse.platform plugin is the only implementation within Eclipse.
- </documentation>
- </annotation>
-
- <annotation>
- <appInfo>
- <meta.section type="copyright"/>
- </appInfo>
- <documentation>
- /************************************************************************
- * Copyright (c) 2004 IBM Corporation and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Common Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/cpl-v10.html
- *
- * Contributors:
- * IBM Corporation - Initial API and implementation
- *************************************************************************/
- </documentation>
- </annotation>
-
-</schema>
+<?xml version='1.0' encoding='UTF-8'?>
+<!-- Schema file written by PDE -->
+<schema targetNamespace="org.eclipse.ui.intro">
+<annotation>
+ <appInfo>
+ <meta.schema plugin="org.eclipse.ui.intro" id="config" name="Intro Part Configuration"/>
+ </appInfo>
+ <documentation>
+ This extension point is used to register an intro configuration. This configuration provides presentation implementations and content for a given intro contribution. An intro appears when the workbench is first launched and as a choice from the &quot;Help&quot; menu. The intro is typically used to introduce a user to a product built on Eclipse.
+&lt;p&gt;
+The intros are organized into pages which usually reflect a particular category of introductory material. For instance, a What&apos;s New page may introduce new concepts or functionality since previous versions. The content defined by one intro configuration can be referenced and extended from other plug-ins using the &lt;a href=&quot;org.eclipse.ui.intro.configExtension.exsd&quot;&gt;org.eclipse.ui.intro.configExtension&lt;/a&gt; extension point.
+&lt;p&gt;
+todo - add other APIs here such as IStandbyPart
+ </documentation>
+ </annotation>
+
+ <include schemaLocation="IntroContent.exsd"/>
+
+ <element name="extension">
+ <complexType>
+ <sequence>
+ <element ref="config" 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>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="config">
+ <annotation>
+ <documentation>
+ A config element can be used to configure a customizable Intro Part. A config element must specify an id, an introId, and a content file.
+The intro content file is an XML file that describes the pages, groups and links that the intro has.
+ </documentation>
+ </annotation>
+ <complexType>
+ <sequence>
+ <element ref="presentation"/>
+ </sequence>
+ <attribute name="introId" type="string" use="required">
+ <annotation>
+ <documentation>
+ the id of an intro part contribution that this configuration will be associated with.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="id" type="string" use="required">
+ <annotation>
+ <documentation>
+ a unique name that can be used to identify this intro configuration
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="content" type="string" use="required">
+ <annotation>
+ <documentation>
+ an intro content file. The content file is an XML file that contains the specifics of the intro (&lt;a href=&quot;introContentFileSpec.html&quot;&gt;intro content file format specification)&lt;/a&gt;.
+The content file is parsed at run time by the intro framework. Based on the settings in this file, a certain number of pages, groups, and links are shown to the user when the intro is opened.
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="presentation">
+ <annotation>
+ <documentation>
+ Presentation element that defines all the possible implementations of an intro part&apos;s presentation. It can have one or more implementation defined in it. Only one implementation will be chosen at startup, based the os/ws attributes of the implementations. Otherwise, the first one with no os/ws attributes defined will be chosen.
+ </documentation>
+ </annotation>
+ <complexType>
+ <sequence>
+ <element ref="implementation" minOccurs="1" maxOccurs="unbounded"/>
+ </sequence>
+ <attribute name="home-page-id" type="string" use="required">
+ <annotation>
+ <documentation>
+ the id of the home (root) page.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="standby-page-id" type="string">
+ <annotation>
+ <documentation>
+ an optional attribute to define the id of the standby page. The standby page will be shown to the user when the Intro is set to standby.
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="implementation">
+ <annotation>
+ <documentation>
+ The presentation of the Platform&apos;s out of the box experience has two implementations. One of them is SWT Browser based, while the other is UI Forms based. The customizable intro part can be configured to pick one of those two presentation based on the current OS and WS. The type of the implementation can be swt or html.
+ </documentation>
+ </annotation>
+ <complexType>
+ <sequence>
+ <element ref="head" minOccurs="0" maxOccurs="1"/>
+ </sequence>
+ <attribute name="kind" use="required">
+ <annotation>
+ <documentation>
+
+ </documentation>
+ </annotation>
+ <simpleType>
+ <restriction base="string">
+ <enumeration value="swt">
+ </enumeration>
+ <enumeration value="html">
+ </enumeration>
+ </restriction>
+ </simpleType>
+ </attribute>
+ <attribute name="style" type="string">
+ <annotation>
+ <documentation>
+ The shared style that will be applied to all pages presented by this intro presentation implementation.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="os" type="string">
+ <annotation>
+ <documentation>
+ os string used when choosing the presentation&apos;s implementation based on current OS. eg: win32,linux (todo - where are the valid OS strings used by Eclipse defined?)
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="ws" type="string">
+ <annotation>
+ <documentation>
+ ws string used when choosing the presentation&apos;s implementation based on current WS. eg: win32,gtk (todo - where are the valid WS strings used by Eclipse defined? Should we expand WS to windowing system?)
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="since"/>
+ </appInfo>
+ <documentation>
+ 3.0
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="examples"/>
+ </appInfo>
+ <documentation>
+ Here is a sample usage of the config extension point.
+
+&lt;extension id=&quot;intro&quot; point=&quot;org.eclipse.ui.intro.config&quot;&gt;
+ &lt;config
+ introId=&quot;com.org.xyz.intro&quot;
+ id=&quot;com.org.xyz.introConfig&quot;
+ content=&quot;introContent.xml&quot;&gt;
+ &lt;presentation
+ home-page-id=&quot;root&quot;
+ title=&quot;%intro.title&quot;&gt;
+ &lt;implementation
+ ws=&quot;win32&quot;
+ style=&quot;css/shared.css&quot;
+ class=&quot;org.eclipse.ui.internal.intro.impl.presentations.BrowserIntroPartImplementation&quot;
+ os=&quot;win32&quot;&gt;
+ &lt;/implementation&gt;
+ &lt;implementation
+ style=&quot;css/shared_swt.properties&quot;
+ class=&quot;org.eclipse.ui.internal.intro.impl.presentations.FormIntroPartImplementation&quot;&gt;
+ &lt;/implementation&gt;
+ &lt;/presentation&gt;
+ &lt;/config&gt;
+&lt;/extension&gt;
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="apiInfo"/>
+ </appInfo>
+ <documentation>
+ [Enter API information here.]
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="implementation"/>
+ </appInfo>
+ <documentation>
+ The intro contributed by the org.eclipse.platform plugin is the only implementation within Eclipse.
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="copyright"/>
+ </appInfo>
+ <documentation>
+ /************************************************************************
+ * Copyright (c) 2004 IBM Corporation and others.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Common Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/cpl-v10.html
+ *
+ * Contributors:
+ * IBM Corporation - Initial API and implementation
+ *************************************************************************/
+ </documentation>
+ </annotation>
+
+</schema>
diff --git a/org.eclipse.ui.intro/schema/org.eclipse.ui.intro.configExtension.exsd b/org.eclipse.ui.intro/schema/configExtension.exsd
index c3b40c01b..c7135728c 100644
--- a/org.eclipse.ui.intro/schema/org.eclipse.ui.intro.configExtension.exsd
+++ b/org.eclipse.ui.intro/schema/configExtension.exsd
@@ -1,201 +1,201 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<!-- Schema file written by PDE -->
-<schema targetNamespace="org.eclipse.ui.intro">
-<annotation>
- <appInfo>
- <meta.schema plugin="org.eclipse.ui.intro" id="configExtension" name="Intro Part Configuration Extension"/>
- </appInfo>
- <documentation>
- This extension point is used to extend an existing intro configuration by providing more content, additional StandbyContentParts or additional IntroUrl actions.
- </documentation>
- </annotation>
-
- <element name="extension">
- <complexType>
- <sequence>
- <element ref="configExtension" minOccurs="1" maxOccurs="unbounded"/>
- <element ref="standbyContentPart" minOccurs="0" maxOccurs="unbounded"/>
- <element ref="action" 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>
- </annotation>
- </attribute>
- </complexType>
- </element>
-
- <element name="configExtension">
- <annotation>
- <documentation>
- Defines an extension to an intro configuration. Any page or div in an intro part configuration can be extended, if that page has declared extensability through defining place holders.
- </documentation>
- </annotation>
- <complexType>
- <attribute name="configId" type="string" use="required">
- <annotation>
- <documentation>
- the id of an intro contribution that will be extended
- </documentation>
- </annotation>
- </attribute>
- <attribute name="content" type="string" use="required">
- <annotation>
- <documentation>
- an intro content file. The content file is an XML file that contains the specifics of the intro (&lt;a href=&quot;introContentFileSpec.html&quot;&gt;intro content file format specification)&lt;/a&gt;.
-The content file is parsed at run time by the intro framework. Based on the settings in this file, a certain number of pages, groups, and links are shown to the user when the intro is opened.
- </documentation>
- </annotation>
- </attribute>
- </complexType>
- </element>
-
- <element name="standbyContentPart">
- <annotation>
- <documentation>
- standby content part registration. Once registered, standby parts can be launched through an introURL action of the following format:
-&lt;pre&gt;
-http://org.eclipse.ui.intro/showStandby?partId=org.eclipse.ui.intro.config.contextHelp
-&lt;/pre&gt;
- </documentation>
- </annotation>
- <complexType>
- <attribute name="id" type="string" use="required">
- <annotation>
- <documentation>
- a unique id that identifies this standbyPart.
- </documentation>
- </annotation>
- </attribute>
- <attribute name="pluginId" type="string">
- <annotation>
- <documentation>
- The name of the plugin that holds the class defined in the &quot;class&quot; attribute. (todo - is this needed? shouldn&apos;t the class be in the declaring plugin already.)
- </documentation>
- </annotation>
- </attribute>
- <attribute name="class" type="string" use="required">
- <annotation>
- <documentation>
- The fully qualified class name of the class that implements &lt;code&gt;org.eclipse.ui.intro.config.IStandbyContentPart&lt;/code&gt; to handle displaying alternative standby content, such as a cheat sheet.
- </documentation>
- </annotation>
- </attribute>
- </complexType>
- </element>
-
- <element name="action">
- <annotation>
- <documentation>
- Custom Intro URL action registration. This can be used to create new Intro URL actions. It can be used to create a shortCut action or create custom actions.
-For example:
-a short cut command is:
-
-a custom command is:
- </documentation>
- </annotation>
- <complexType>
- <attribute name="name" type="string" use="required">
- <annotation>
- <documentation>
-
- </documentation>
- </annotation>
- </attribute>
- <attribute name="replaces" type="string" use="required">
- <annotation>
- <documentation>
-
- </documentation>
- </annotation>
- </attribute>
- </complexType>
- </element>
-
- <annotation>
- <appInfo>
- <meta.section type="since"/>
- </appInfo>
- <documentation>
- 3.0
- </documentation>
- </annotation>
-
- <annotation>
- <appInfo>
- <meta.section type="examples"/>
- </appInfo>
- <documentation>
- Here is an example implementation of this extension point:
-
-&lt;extension point=&quot;org.eclipse.ui.intro.configExtension&quot;&gt;
- &lt;configExtension
- configId=&quot;com.org.xyz.introConfig&quot;
- content=&quot;extensionContent.xml&quot;/&gt;
-
- &lt;standbyPart
- id=&quot;com.org.xyz.myStandbyPart&quot;
- class=&quot;com.org.xyz.internal.MyStandbyContent&quot;
- pluginId=&quot;org.eclipse.platform&quot;/&gt; (todo - remove the pluginId?)
-&lt;/extension&gt;
- </documentation>
- </annotation>
-
- <annotation>
- <appInfo>
- <meta.section type="apiInfo"/>
- </appInfo>
- <documentation>
- [Enter API information here.]
- </documentation>
- </annotation>
-
- <annotation>
- <appInfo>
- <meta.section type="implementation"/>
- </appInfo>
- <documentation>
- There are three supplied implementations:
-&lt;ul&gt;
-&lt;li&gt;org.eclipse.jdt, makes use of configExtension&lt;/li&gt;
-&lt;li&gt;org.eclipse.pde, makes use of configExtension&lt;/li&gt;
-&lt;li&gt;org.eclipse.platform, makes use of standbyPoint&lt;/li&gt;
-&lt;/ul&gt;
- </documentation>
- </annotation>
-
- <annotation>
- <appInfo>
- <meta.section type="copyright"/>
- </appInfo>
- <documentation>
- /************************************************************************
- * Copyright (c) 2004 IBM Corporation and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Common Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/cpl-v10.html
- *
- * Contributors:
- * IBM Corporation - Initial API and implementation
- *************************************************************************/
- </documentation>
- </annotation>
-
-</schema>
+<?xml version='1.0' encoding='UTF-8'?>
+<!-- Schema file written by PDE -->
+<schema targetNamespace="org.eclipse.ui.intro">
+<annotation>
+ <appInfo>
+ <meta.schema plugin="org.eclipse.ui.intro" id="configExtension" name="Intro Part Configuration Extension"/>
+ </appInfo>
+ <documentation>
+ This extension point is used to extend an existing intro configuration by providing more content, additional StandbyContentParts or additional IntroUrl actions.
+ </documentation>
+ </annotation>
+
+ <element name="extension">
+ <complexType>
+ <sequence>
+ <element ref="configExtension" minOccurs="1" maxOccurs="unbounded"/>
+ <element ref="standbyContentPart" minOccurs="0" maxOccurs="unbounded"/>
+ <element ref="action" 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>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="configExtension">
+ <annotation>
+ <documentation>
+ Defines an extension to an intro configuration. Any page or div in an intro part configuration can be extended, if that page has declared extensability through defining place holders.
+ </documentation>
+ </annotation>
+ <complexType>
+ <attribute name="configId" type="string" use="required">
+ <annotation>
+ <documentation>
+ the id of an intro contribution that will be extended
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="content" type="string" use="required">
+ <annotation>
+ <documentation>
+ an intro content file. The content file is an XML file that contains the specifics of the intro (&lt;a href=&quot;introContentFileSpec.html&quot;&gt;intro content file format specification)&lt;/a&gt;.
+The content file is parsed at run time by the intro framework. Based on the settings in this file, a certain number of pages, groups, and links are shown to the user when the intro is opened.
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="standbyContentPart">
+ <annotation>
+ <documentation>
+ standby content part registration. Once registered, standby parts can be launched through an introURL action of the following format:
+&lt;pre&gt;
+http://org.eclipse.ui.intro/showStandby?partId=org.eclipse.ui.intro.config.contextHelp
+&lt;/pre&gt;
+ </documentation>
+ </annotation>
+ <complexType>
+ <attribute name="id" type="string" use="required">
+ <annotation>
+ <documentation>
+ a unique id that identifies this standbyPart.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="pluginId" type="string">
+ <annotation>
+ <documentation>
+ The name of the plugin that holds the class defined in the &quot;class&quot; attribute. (todo - is this needed? shouldn&apos;t the class be in the declaring plugin already.)
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="class" type="string" use="required">
+ <annotation>
+ <documentation>
+ The fully qualified class name of the class that implements &lt;code&gt;org.eclipse.ui.intro.config.IStandbyContentPart&lt;/code&gt; to handle displaying alternative standby content, such as a cheat sheet.
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="action">
+ <annotation>
+ <documentation>
+ Custom Intro URL action registration. This can be used to create new Intro URL actions. It can be used to create a shortCut action or create custom actions.
+For example:
+a short cut command is:
+
+a custom command is:
+ </documentation>
+ </annotation>
+ <complexType>
+ <attribute name="name" type="string" use="required">
+ <annotation>
+ <documentation>
+
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="replaces" type="string" use="required">
+ <annotation>
+ <documentation>
+
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="since"/>
+ </appInfo>
+ <documentation>
+ 3.0
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="examples"/>
+ </appInfo>
+ <documentation>
+ Here is an example implementation of this extension point:
+
+&lt;extension point=&quot;org.eclipse.ui.intro.configExtension&quot;&gt;
+ &lt;configExtension
+ configId=&quot;com.org.xyz.introConfig&quot;
+ content=&quot;extensionContent.xml&quot;/&gt;
+
+ &lt;standbyPart
+ id=&quot;com.org.xyz.myStandbyPart&quot;
+ class=&quot;com.org.xyz.internal.MyStandbyContent&quot;
+ pluginId=&quot;org.eclipse.platform&quot;/&gt; (todo - remove the pluginId?)
+&lt;/extension&gt;
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="apiInfo"/>
+ </appInfo>
+ <documentation>
+ [Enter API information here.]
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="implementation"/>
+ </appInfo>
+ <documentation>
+ There are three supplied implementations:
+&lt;ul&gt;
+&lt;li&gt;org.eclipse.jdt, makes use of configExtension&lt;/li&gt;
+&lt;li&gt;org.eclipse.pde, makes use of configExtension&lt;/li&gt;
+&lt;li&gt;org.eclipse.platform, makes use of standbyPoint&lt;/li&gt;
+&lt;/ul&gt;
+ </documentation>
+ </annotation>
+
+ <annotation>
+ <appInfo>
+ <meta.section type="copyright"/>
+ </appInfo>
+ <documentation>
+ /************************************************************************
+ * Copyright (c) 2004 IBM Corporation and others.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Common Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/cpl-v10.html
+ *
+ * Contributors:
+ * IBM Corporation - Initial API and implementation
+ *************************************************************************/
+ </documentation>
+ </annotation>
+
+</schema>

Back to the top