Skip to main content
aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMazen Faraj2004-08-30 22:25:05 +0000
committerMazen Faraj2004-08-30 22:25:05 +0000
commit266616041676a2aba376dcc353f909cd789ca039 (patch)
tree2adfd0c1f11e690b970eda801bd03b1c6b98f2d4 /org.eclipse.ui.intro/schema/IntroContent.exsd
parenta87d8603698ae22b879ee84933ec9f89a85455bb (diff)
downloadeclipse.platform.ua-266616041676a2aba376dcc353f909cd789ca039.tar.gz
eclipse.platform.ua-266616041676a2aba376dcc353f909cd789ca039.tar.xz
eclipse.platform.ua-266616041676a2aba376dcc353f909cd789ca039.zip
Merging 3.0.1 changes
Diffstat (limited to 'org.eclipse.ui.intro/schema/IntroContent.exsd')
-rw-r--r--org.eclipse.ui.intro/schema/IntroContent.exsd252
1 files changed, 145 insertions, 107 deletions
diff --git a/org.eclipse.ui.intro/schema/IntroContent.exsd b/org.eclipse.ui.intro/schema/IntroContent.exsd
index fc0cadc57..593efd7dd 100644
--- a/org.eclipse.ui.intro/schema/IntroContent.exsd
+++ b/org.eclipse.ui.intro/schema/IntroContent.exsd
@@ -53,6 +53,7 @@ The subelements used in a dynamic page are as follows: A <b>group</b&gt
<element ref="html" minOccurs="0" maxOccurs="unbounded"/>
<element ref="title" minOccurs="0" maxOccurs="1"/>
<element ref="anchor" minOccurs="0" maxOccurs="unbounded"/>
+ <element ref="contentProvider" minOccurs="0" maxOccurs="unbounded"/>
</choice>
<attribute name="url" type="string">
<annotation>
@@ -130,6 +131,7 @@ This seperation of pages can be used when performance is an issue, as the conten
<element ref="include" minOccurs="0" maxOccurs="unbounded"/>
<element ref="html" minOccurs="0" maxOccurs="unbounded"/>
<element ref="anchor" minOccurs="0" maxOccurs="unbounded"/>
+ <element ref="contentProvider" minOccurs="0" maxOccurs="unbounded"/>
</choice>
<attribute name="id" type="string" use="required">
<annotation>
@@ -170,6 +172,63 @@ This seperation of pages can be used when performance is an issue, as the conten
</complexType>
</element>
+ <element name="head">
+ <annotation>
+ <documentation>
+ Direct HTML to include in a page&apos;s HEAD content area. It allows for additional html to be added to the HTML HEAD section. This is useful for adding java srcipts or extra styles sheets.
+This markup is only to be used with an HTML based intro part implementation. It is simply ignored in the case of a UI Forms implementation. A page can have more than one head element. An implementation can have one and only one head element (since it is a shared across all pages).
+ </documentation>
+ </annotation>
+ <complexType>
+ <attribute name="src" type="string" use="required">
+ <annotation>
+ <documentation>
+ relative or absolute URL to a file containing HTML to include directly into the HTML head section.
+ </documentation>
+ </annotation>
+ </attribute>
+ </complexType>
+ </element>
+
+ <element name="title">
+ <annotation>
+ <documentation>
+ a snippet of text that can optionally contain escaped HTML tags. It is only used as a Page Title, and so a given page can have a maximum of one title element.
+ </documentation>
+ </annotation>
+ <complexType>
+ <attribute name="id" type="string">
+ <annotation>
+ <documentation>
+ unique identifier of this title.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="style-id" type="string">
+ <annotation>
+ <documentation>
+ A means to classifiy this element into a given category so that a common style may be applied
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="filteredFrom">
+ <annotation>
+ <documentation>
+ an optional attribute that allows for filtering a given element out of a specific implementation. For example, if a group has filteredFrom = swt, it means that this group will not appear as content in the swt implementation.
+ </documentation>
+ </annotation>
+ <simpleType>
+ <restriction base="string">
+ <enumeration value="swt">
+ </enumeration>
+ <enumeration value="html">
+ </enumeration>
+ </restriction>
+ </simpleType>
+ </attribute>
+ </complexType>
+ </element>
+
<element name="link">
<annotation>
<documentation>
@@ -288,54 +347,25 @@ no parameters required&lt;br&gt;
</complexType>
</element>
- <element name="html">
+ <element name="text">
<annotation>
<documentation>
- direct HTML to include in the page either by embedding the entire document, or inlining a snippet of HTML in-place. A fallback image or text must be defined for alternative swt presentation rendering.
-&lt;br&gt;
-Embedding allows for a fully defined html file to be embedded within the dynamic page&apos;s content. An HTML &lt;b&gt;object&lt;/b&gt; element is created that references the html file.
-&lt;br&gt;
-Inclusion allows for including an html snippet directly from a file into the dynamic html page.
+ a snippet of text that can optionally contain escaped HTML tags. It can include b and li tags. It can also contain anchors for urls.
+If multiple paragraphs are needed, then the text can be divided into multiple sections each begining and ending with the p tag.
</documentation>
</annotation>
<complexType>
- <choice>
- <element ref="img"/>
- <element ref="text"/>
- </choice>
- <attribute name="id" type="string" use="required">
- <annotation>
- <documentation>
- unique identifier of this HTML element
- </documentation>
- </annotation>
- </attribute>
- <attribute name="src" type="string" use="required">
- <annotation>
- <documentation>
- relative or absolute URL to a file containing HTML
- </documentation>
- </annotation>
- </attribute>
- <attribute name="type" use="required">
+ <attribute name="id" type="string">
<annotation>
<documentation>
- if &apos;embed&apos;, a valid (full) HTML document will be embedded using HTML &apos;OBJECT&apos; tag. If &apos;inline&apos;, value of &apos;src&apos; will be treated as a snippet of HTML to emit &apos;in-place&apos;. (if type is not specified, this html object is ignored by the intro configuration).
+ unique identifier of this text.
</documentation>
</annotation>
- <simpleType>
- <restriction base="string">
- <enumeration value="inline">
- </enumeration>
- <enumeration value="embed">
- </enumeration>
- </restriction>
- </simpleType>
</attribute>
<attribute name="style-id" type="string">
<annotation>
<documentation>
- A means to classifiy this HTML element into a given category so that a common style may be applied.
+ A means to classifiy this element into a given category so that a common style may be applied
</documentation>
</annotation>
</attribute>
@@ -357,24 +387,38 @@ Inclusion allows for including an html snippet directly from a file into the dyn
</complexType>
</element>
- <element name="title">
+ <element name="img">
<annotation>
<documentation>
- a snippet of text that can optionally contain escaped HTML tags. It is only used as a Page Title, and so a given page can have a maximum of one title element.
+ An image that represents intro content and not presentation (as opposed to decoration images defined in styles).
</documentation>
</annotation>
<complexType>
- <attribute name="id" type="string">
+ <attribute name="id" type="string" use="required">
<annotation>
<documentation>
- unique identifier of this title.
+ unique identifier of this image
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="src" type="string" use="required">
+ <annotation>
+ <documentation>
+ the file to load the image from
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="alt" type="string">
+ <annotation>
+ <documentation>
+ the alternative text to use when the image can not be loaded and as tooltip text for the image.
</documentation>
</annotation>
</attribute>
<attribute name="style-id" type="string">
<annotation>
<documentation>
- A means to classifiy this element into a given category so that a common style may be applied
+ A means to classifiy this image into a given category so that a common style may be applied.
</documentation>
</annotation>
</attribute>
@@ -396,25 +440,54 @@ Inclusion allows for including an html snippet directly from a file into the dyn
</complexType>
</element>
- <element name="text">
+ <element name="html">
<annotation>
<documentation>
- a snippet of text that can optionally contain escaped HTML tags. It can include b and li tags. It can also contain anchors for urls.
-If multiple paragraphs are needed, then the text can be divided into multiple sections each begining and ending with the p tag.
+ direct HTML to include in the page either by embedding the entire document, or inlining a snippet of HTML in-place. A fallback image or text must be defined for alternative swt presentation rendering.
+&lt;br&gt;
+Embedding allows for a fully defined html file to be embedded within the dynamic page&apos;s content. An HTML &lt;b&gt;object&lt;/b&gt; element is created that references the html file.
+&lt;br&gt;
+Inclusion allows for including an html snippet directly from a file into the dynamic html page.
</documentation>
</annotation>
<complexType>
- <attribute name="id" type="string">
+ <choice>
+ <element ref="img"/>
+ <element ref="text"/>
+ </choice>
+ <attribute name="id" type="string" use="required">
<annotation>
<documentation>
- unique identifier of this text.
+ unique identifier of this HTML element
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="src" type="string" use="required">
+ <annotation>
+ <documentation>
+ relative or absolute URL to a file containing HTML
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="type" use="required">
+ <annotation>
+ <documentation>
+ if &apos;embed&apos;, a valid (full) HTML document will be embedded using HTML &apos;OBJECT&apos; tag. If &apos;inline&apos;, value of &apos;src&apos; will be treated as a snippet of HTML to emit &apos;in-place&apos;. (if type is not specified, this html object is ignored by the intro configuration).
</documentation>
</annotation>
+ <simpleType>
+ <restriction base="string">
+ <enumeration value="inline">
+ </enumeration>
+ <enumeration value="embed">
+ </enumeration>
+ </restriction>
+ </simpleType>
</attribute>
<attribute name="style-id" type="string">
<annotation>
<documentation>
- A means to classifiy this element into a given category so that a common style may be applied
+ A means to classifiy this HTML element into a given category so that a common style may be applied.
</documentation>
</annotation>
</attribute>
@@ -467,73 +540,19 @@ If multiple paragraphs are needed, then the text can be divided into multiple se
</complexType>
</element>
- <element name="head">
- <annotation>
- <documentation>
- Direct HTML to include in a page&apos;s HEAD content area. It allows for additional html to be added to the HTML HEAD section. This is useful for adding java srcipts or extra styles sheets.
-This markup is only to be used with an HTML based intro part implementation. It is simply ignored in the case of a UI Forms implementation. A page can have more than one head element. An implementation can have one and only one head element (since it is a shared across all pages).
- </documentation>
- </annotation>
- <complexType>
- <attribute name="src" type="string" use="required">
- <annotation>
- <documentation>
- relative or absolute URL to a file containing HTML to include directly into the HTML head section.
- </documentation>
- </annotation>
- </attribute>
- </complexType>
- </element>
-
- <element name="img">
+ <element name="anchor">
<annotation>
<documentation>
- An image that represents intro content and not presentation (as opposed to decoration images defined in styles).
+ an anchor is the element used to declare extensibility. It is a location in the configurtaion that allows for external contributions. Only anchors are valid target values for the path attribute in an extensionContent
</documentation>
</annotation>
<complexType>
<attribute name="id" type="string" use="required">
<annotation>
<documentation>
- unique identifier of this image
- </documentation>
- </annotation>
- </attribute>
- <attribute name="src" type="string" use="required">
- <annotation>
- <documentation>
- the file to load the image from
- </documentation>
- </annotation>
- </attribute>
- <attribute name="alt" type="string">
- <annotation>
- <documentation>
- the alternative text to use when the image can not be loaded and as tooltip text for the image.
- </documentation>
- </annotation>
- </attribute>
- <attribute name="style-id" type="string">
- <annotation>
- <documentation>
- A means to classifiy this image into a given category so that a common style may be applied.
- </documentation>
- </annotation>
- </attribute>
- <attribute name="filteredFrom">
- <annotation>
- <documentation>
- an optional attribute that allows for filtering a given element out of a specific implementation. For example, if a group has filteredFrom = swt, it means that this group will not appear as content in the swt implementation.
+ unique id to identify this anchor.
</documentation>
</annotation>
- <simpleType>
- <restriction base="string">
- <enumeration value="swt">
- </enumeration>
- <enumeration value="html">
- </enumeration>
- </restriction>
- </simpleType>
</attribute>
</complexType>
</element>
@@ -576,17 +595,36 @@ This markup is only to be used with an HTML based intro part implementation. It
</complexType>
</element>
- <element name="anchor">
+ <element name="contentProvider">
<annotation>
<documentation>
- an anchor is the element used to declare extensibility. It is a location in the configurtaion that allows for external contributions. Only anchors are valid target values for the path attribute in an extensionContent
+ A proxy for an intro content provider, which allows an intro page to dynamically pull data from various sources (e.g., the web, eclipse, etc) and provide content at runtime based on this dynamic data. If the IIntroContentProvider class that is specified in the class attribute can not be loaded, then the contents of the text element will be rendered instead.
+This is a dynamic version of the html intro tag. While the html tag allows for embedding or inlining a static html content into the generated html intro page, the contentProvider tag allows for dynamic creation of that content at runtime.
+Another difference between the tags is that the html tag is only supported for the HTML presentation, while this contentProvider tag is supported for both the HTML and SWT presentations.
</documentation>
</annotation>
<complexType>
- <attribute name="id" type="string">
+ <all>
+ <element ref="text" minOccurs="0" maxOccurs="1"/>
+ </all>
+ <attribute name="id" type="string" use="required">
<annotation>
<documentation>
- unique id to identify this anchor.
+ unique identifier of this HTML element
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="pluginId" type="string">
+ <annotation>
+ <documentation>
+ The id of the plugin that contains the IContentProvider class specified by the class attribute. This is an optional attribute that should be used if the class doesn&apos;t come from the same plugin that defined the markup.
+ </documentation>
+ </annotation>
+ </attribute>
+ <attribute name="class" type="string" use="required">
+ <annotation>
+ <documentation>
+ A class that implements the IContentProvider interface
</documentation>
</annotation>
</attribute>

Back to the top