Skip to main content
summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorChris Goldthorpe2007-09-19 16:32:51 +0000
committerChris Goldthorpe2007-09-19 16:32:51 +0000
commit08b39951f81cce2f8b8a269973938e7c83c22c26 (patch)
tree3662ef0dd799e8f93df8681660289ff1fec8e188
parentd2339e3b10d791c8f55c35c02b9517b3c5aa80da (diff)
downloadeclipse.platform.ua-08b39951f81cce2f8b8a269973938e7c83c22c26.tar.gz
eclipse.platform.ua-08b39951f81cce2f8b8a269973938e7c83c22c26.tar.xz
eclipse.platform.ua-08b39951f81cce2f8b8a269973938e7c83c22c26.zip
Regenerate using latest PDE to fix CHKPII errors.v20070919
-rw-r--r--org.eclipse.ui.cheatsheets/schema/cheatSheetContentFileSpec.html66
-rw-r--r--org.eclipse.ui.cheatsheets/schema/compositeContentFile.html24
-rw-r--r--org.eclipse.ui.intro/schema/introContentFileSpec.html62
3 files changed, 76 insertions, 76 deletions
diff --git a/org.eclipse.ui.cheatsheets/schema/cheatSheetContentFileSpec.html b/org.eclipse.ui.cheatsheets/schema/cheatSheetContentFileSpec.html
index 8d542cc72..607627524 100644
--- a/org.eclipse.ui.cheatsheets/schema/cheatSheetContentFileSpec.html
+++ b/org.eclipse.ui.cheatsheets/schema/cheatSheetContentFileSpec.html
@@ -24,22 +24,22 @@ DTD fragments (<a href="cheatSheetContentFileSpec.exsd">machine readable XML sch
<p></p>
<p class="ConfigMarkupElementDesc">
The root element of a cheatsheet.</p>
-<br/>
+<br>
<ul class="ConfigMarkupAttlistDesc">
<li><b>title</b> - The title of this cheat sheet. The title will be displayed at the head of the cheat sheet view when the cheat sheet is opened.</li>
</ul>
-<br/><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.intro">intro</a> (<a href="#e.description">description</a>)&gt;</p>
+<br><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.intro">intro</a> (<a href="#e.description">description</a>)&gt;</p>
<p class="code SchemaDtd">&lt;!ATTLIST intro</p>
<p class="code SchemaDtdAttlist">contextId&nbsp;CDATA #IMPLIED<p class="code SchemaDtdAttlist">href&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED&gt;</p>
<p></p>
<p class="ConfigMarkupElementDesc">
The &lt;intro&gt; element is used to define the introductory text to be displayed when the cheat sheet is opened.</p>
-<br/>
+<br>
<ul class="ConfigMarkupAttlistDesc">
<li><b>contextId</b> - The optional help context id of the documentation for this cheat sheet. If supplied, context help for the given fully-qualified context id is shown to the user (typically in a small pop-up window) when they clicks the introduction's help link. If this attribute is supplied, the <b>href</b> attribute should not be supplied (<b>href</b> will be ignored if both are present).</li>
<li><b>href</b> - The optional help document describing this cheat sheet. If supplied, this help document is shown to the user (typically in a help browser shown in a separate window) when they clicks the introduction's help link. If this attribute is supplied, the <b>contextId</b> attribute should not be supplied (<b>href</b> will be ignored if both are present).</li>
</ul>
-<br/><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.description">description</a> (#PCDATA)&gt;</p>
+<br><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.description">description</a> (#PCDATA)&gt;</p>
<p></p>
<p class="ConfigMarkupElementDesc">
The &lt;description&gt; element holds the description of a cheat sheet or of
@@ -57,12 +57,12 @@ separator; adjacent spaces and line breaks are treated as single unit and
rendered as a single space or a line break. Whitespace immediately after the
&lt;<b>description</b>&gt; and &lt;<b>br/</b>&gt; tags is ignored, as is
whitespace immediately before the &lt;<b>/description</b>&gt; tag.</p>
-<br/><br/>
+<br><br>
<p class="code SchemaDtd">&lt;!ELEMENT <a name="e.item">item</a> (<a href="#e.description">description</a> , (<a href="#e.action">action</a> | <a href="#e.command">command</a> | <a href="#e.perform-when">perform-when</a> | (<a href="#e.subitem">subitem</a> | <a href="#e.conditional-subitem">conditional-subitem</a> | <a href="#e.repeated-subitem">repeated-subitem</a>)*) , <a href="#e.onCompletion">onCompletion</a>?)&gt;</p>
<p class="code SchemaDtd">&lt;!ATTLIST item</p>
<p class="code SchemaDtdAttlist">title&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED<p class="code SchemaDtdAttlist">dialog&nbsp;&nbsp;&nbsp;&nbsp;(true | false) "false"<p class="code SchemaDtdAttlist">skip&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(true | false) "false"<p class="code SchemaDtdAttlist">contextId&nbsp;CDATA #IMPLIED<p class="code SchemaDtdAttlist">href&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED&gt;</p>
<p></p>
-<p class="ConfigMarkupElementDesc">
+<div class="ConfigMarkupElementDesc">
<p>Each &lt;item&gt; element describes one top-level step in a cheat sheet. An
&lt;item&gt; may contain &lt;subitem&gt; elements.
@@ -86,8 +86,8 @@ represented as sub-items.)</p>
presentation of a sub-step based on cheat sheet variables whose values are
acquired in earlier steps. A &lt;repeated-subitem&gt; subelement allows a step
to include a set of similar sub-steps. Again, the exact set of sub-steps may be
-based on cheat sheet variables whose value are acquired in earlier steps.</p></p>
-<br/>
+based on cheat sheet variables whose value are acquired in earlier steps.</p></div>
+<br>
<ul class="ConfigMarkupAttlistDesc">
<li><b>title</b> - The title of this step.</li>
<li><b>dialog</b> - if &quot;true&quot; means this step involves opening a modal dialog. This is a hint to the system that it should allow the user to continue using the cheat sheet while in the modal dialog. This attribute will only affect dialogs launched from a command or action.</li>
@@ -95,11 +95,11 @@ based on cheat sheet variables whose value are acquired in earlier steps.</p></p
<li><b>contextId</b> - The optional help context id of the documentation for this cheat sheet step. If supplied, context help for the given&nbsp; fully-qualified context id is shown to the user (typically in a small pop-up window) when they clicks the step's help link. If this attribute is supplied, the <b>href</b> attribute should not be supplied (<b>href</b> will be ignored if both are present).</li>
<li><b>href</b> - The optional help document describing this cheat sheet step. If supplied, this help document is shown to the user (typically in a help browser shown in a separate window) when they clicks the step's help link. If this attribute is supplied, the <b>contextId</b> attribute should not be supplied (<b>href</b> will be ignored if both are present).</li>
</ul>
-<br/><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.subitem">subitem</a> (<a href="#e.action">action</a> | <a href="#e.command">command</a> | <a href="#e.perform-when">perform-when</a>)?&gt;</p>
+<br><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.subitem">subitem</a> (<a href="#e.action">action</a> | <a href="#e.command">command</a> | <a href="#e.perform-when">perform-when</a>)?&gt;</p>
<p class="code SchemaDtd">&lt;!ATTLIST subitem</p>
<p class="code SchemaDtdAttlist">label&nbsp;CDATA #REQUIRED<p class="code SchemaDtdAttlist">skip&nbsp;&nbsp;(true | false) "false"<p class="code SchemaDtdAttlist">when&nbsp;&nbsp;CDATA #IMPLIED&gt;</p>
<p></p>
-<p class="ConfigMarkupElementDesc">
+<div class="ConfigMarkupElementDesc">
<p>Each &lt;subitem&gt; element describes a sub-step in a cheat sheet. A &lt;subitem&gt;
carries a simple text label, but has neither a lengthy description nor further
sub-items.
@@ -114,8 +114,8 @@ that they have successfully completed the step.</p>
given item can be performed in any order. All sub-items within an item have to
be completed or skipped before progressing to the next item. (Which means
actions that must be performed in a required sequence should not be represented
-as sub-items.)</p></p>
-<br/>
+as sub-items.)</p></div>
+<br>
<ul class="ConfigMarkupAttlistDesc">
<li><b>label</b> - The title of the cheat sheet sub-item. If the string
contains substring occurrences of the form &quot;${<i>var</i>}&quot;, they
@@ -133,11 +133,11 @@ as sub-items.)</p></p>
element matches this string value. This attribute is ignored if the &lt;subitem&gt;
element is not a child of&nbsp; a &lt;conditional-subitem&gt; element.</li>
</ul>
-<br/><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.conditional-subitem">conditional-subitem</a> (<a href="#e.subitem">subitem</a>+)&gt;</p>
+<br><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.conditional-subitem">conditional-subitem</a> (<a href="#e.subitem">subitem</a>+)&gt;</p>
<p class="code SchemaDtd">&lt;!ATTLIST conditional-subitem</p>
<p class="code SchemaDtdAttlist">condition&nbsp;CDATA #REQUIRED&gt;</p>
<p></p>
-<p class="ConfigMarkupElementDesc">
+<div class="ConfigMarkupElementDesc">
<p>Each &lt;conditional-subitem&gt; element describes a single sub-step whose
form can differ based on a condition known at the time the item is expanded.
<p>The <b>condition</b> attribute on the &lt;conditional-subitem&gt; element
@@ -159,8 +159,8 @@ then the second sub-item is selected and the item expands to something
equivalent to
<pre class="Example"><span class="code SchemaTag">&lt;item ...&gt;
&lt;subitem label=</span><span class="code SchemaCstring">&quot;Step for B.&quot;</span><span class="code SchemaTag">/&gt;
-&lt;/item&gt;</span></pre></p>
-<br/>
+&lt;/item&gt;</span></pre></div>
+<br>
<ul class="ConfigMarkupAttlistDesc">
<li><b>condition</b> - Arbitrary string value used to select which child &lt;subitem&gt;
will be used. If the attribute string has the form &quot;${<i>var</i>}&quot;,
@@ -169,11 +169,11 @@ equivalent to
the start of execution of the containing &lt;item&gt; element (or the empty
string if the variable is unbound at that time).</li>
</ul>
-<br/><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.repeated-subitem">repeated-subitem</a> (<a href="#e.subitem">subitem</a>)&gt;</p>
+<br><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.repeated-subitem">repeated-subitem</a> (<a href="#e.subitem">subitem</a>)&gt;</p>
<p class="code SchemaDtd">&lt;!ATTLIST repeated-subitem</p>
<p class="code SchemaDtdAttlist">values&nbsp;CDATA #REQUIRED&gt;</p>
<p></p>
-<p class="ConfigMarkupElementDesc">
+<div class="ConfigMarkupElementDesc">
<p>Each &lt;repeated-subitem&gt; element describes a sub-item that expands into
0, 1, or more similar sub-steps.
@@ -202,8 +202,8 @@ then the item expands to something equivalent to:
&lt;subitem label=</span><span class="code SchemaCstring">&quot;Step three.&quot;</span><span class="code SchemaTag">&gt;
&lt;action class=</span><span class="code SchemaCstring">&quot;com.xyz.myaction&quot;</span><span class="code SchemaTag"> pluginId=</span><span class="code SchemaCstring">&quot;com.xyz&quot;</span><span class="code SchemaTag"> param1=</span><span class="code SchemaCstring">&quot;three&quot;</span><span class="code SchemaTag">/&gt;
&lt;/subitem&gt;
-&lt;/item&gt;</span></pre></p>
-<br/>
+&lt;/item&gt;</span></pre></div>
+<br>
<ul class="ConfigMarkupAttlistDesc">
<li><b>values</b> - A string containing a comma-separated list of values. If
the attribute string has the form &quot;${<i>var</i>}&quot;, it is
@@ -212,13 +212,13 @@ then the item expands to something equivalent to:
start of execution of the containing &lt;item&gt; element (or the empty
string if the variable is unbound at that time).</li>
</ul>
-<br/><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.action">action</a> EMPTY&gt;</p>
+<br><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.action">action</a> EMPTY&gt;</p>
<p class="code SchemaDtd">&lt;!ATTLIST action</p>
<p class="code SchemaDtdAttlist">class&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED<p class="code SchemaDtdAttlist">pluginId&nbsp;&nbsp;CDATA #REQUIRED<p class="code SchemaDtdAttlist">paramN&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class="code SchemaDtdAttlist">confirm&nbsp;&nbsp;&nbsp;(true | false) "false"<p class="code SchemaDtdAttlist">when&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class="code SchemaDtdAttlist">required&nbsp;&nbsp;(true | false) "true"<p class="code SchemaDtdAttlist">translate&nbsp;CDATA #IMPLIED&gt;</p>
<p></p>
<p class="ConfigMarkupElementDesc">
Each &lt;action&gt; element describes an action in a cheat sheet.</p>
-<br/>
+<br>
<ul class="ConfigMarkupAttlistDesc">
<li><b>class</b> - The fully-qualified name of the Java class implementing <code>org.eclipse.jface.action.IAction</code>.
If this action also implements <code>org.eclipse.ui.cheatsheets.ICheatSheetAction</code>
@@ -256,11 +256,11 @@ Examples:
<br>
<code>translate = ""</code> means do not translate any parameters for this action.</li>
</ul>
-<br/><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.command">command</a> EMPTY&gt;</p>
+<br><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.command">command</a> EMPTY&gt;</p>
<p class="code SchemaDtd">&lt;!ATTLIST command</p>
<p class="code SchemaDtdAttlist">serialization&nbsp;CDATA #REQUIRED<p class="code SchemaDtdAttlist">returns&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class="code SchemaDtdAttlist">confirm&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(true | false) "false"<p class="code SchemaDtdAttlist">when&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class="code SchemaDtdAttlist">required&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(true | false) "true"<p class="code SchemaDtdAttlist">translate&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED&gt;</p>
<p></p>
-<p class="ConfigMarkupElementDesc">
+<div class="ConfigMarkupElementDesc">
<p>Each &lt;command&gt; element describes an command in a cheat sheet.
<p>Below is an example of an item with a command which opens a dialog box and
stores the result in the cheat sheet variable &quot;result&quot;.</p>
@@ -269,8 +269,8 @@ stores the result in the cheat sheet variable &quot;result&quot;.</p>
&lt;command returns = </span><span class="code SchemaCstring">&quot;result&quot;</span><span class="code SchemaTag">
serialization=</span><span class="code SchemaCstring">&quot;org.eclipse.ui.dialogs.openMessageDialog(title=Select View,buttonLabel0=Package Explorer,message=Select a view ,buttonLabel1=Search View)&quot;</span><span class="code SchemaTag">/&gt;
&lt;onCompletion&gt; Selected the ${result}. &lt;/onCompletion&gt;
-&lt;/item&gt;</span></pre></p>
-<br/>
+&lt;/item&gt;</span></pre></div>
+<br>
<ul class="ConfigMarkupAttlistDesc">
<li><b>serialization</b> - A serialized
<a href="../api/org/eclipse/core/commands/ParameterizedCommand.html">
@@ -297,7 +297,7 @@ Examples:
<br>
<code>translate = ""</code> means do not translate any parameters for this command.</li>
</ul>
-<br/><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.onCompletion">onCompletion</a> (#PCDATA)&gt;</p>
+<br><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.onCompletion">onCompletion</a> (#PCDATA)&gt;</p>
<p></p>
<p class="ConfigMarkupElementDesc">
Contains text which will be displayed when
@@ -306,12 +306,12 @@ sheet to acknowledge completion of the entire task. The description consists of
&lt;onCompletion&gt; elements may also contain references to cheat sheet variables of
the form&nbsp; &quot;${<i>var</i>}&quot;, which will be expanded using the actual value of
the cheat sheet variable <i>var</i> at the time this step was completed.</p>
-<br/><br/>
+<br><br>
<p class="code SchemaDtd">&lt;!ELEMENT <a name="e.perform-when">perform-when</a> (<a href="#e.action">action</a> | <a href="#e.command">command</a>)+&gt;</p>
<p class="code SchemaDtd">&lt;!ATTLIST perform-when</p>
<p class="code SchemaDtdAttlist">condition&nbsp;CDATA #REQUIRED&gt;</p>
<p></p>
-<p class="ConfigMarkupElementDesc">
+<div class="ConfigMarkupElementDesc">
<p>Each &lt;perform-when&gt; element describes an action in a cheat sheet.
<p>The <b>condition</b> attribute on the &lt;conditional-subitem&gt; element
provides a string value (invariably this value comes from a cheat sheet
@@ -339,8 +339,8 @@ to
&lt;action class=</span><span class="code SchemaCstring">&quot;com.xyz.action2&quot;</span><span class="code SchemaTag"> pluginId=</span><span class="code SchemaCstring">&quot;com.xyz&quot;</span><span class="code SchemaTag"> /&gt;
&lt;/subitem&gt;
&lt;/item&gt;
-</span></pre></p>
-<br/>
+</span></pre></div>
+<br>
<ul class="ConfigMarkupAttlistDesc">
<li><b>condition</b> - Arbitrary string value used to select which child
&lt;action&gt; or &lt;command&gt; will be performed. If the attribute string has the form
@@ -350,7 +350,7 @@ to
&lt;item&gt; element (or the empty string if the variable is unbound at that
time).</li>
</ul>
-<br/><h6 class="CaptionFigColumn SchemaHeader">Examples: </h6><p>The following is an example of a simple cheat sheet content file which
+<br><h6 class="CaptionFigColumn SchemaHeader">Examples: </h6><p>The following is an example of a simple cheat sheet content file which
demonstrates the use of commands, perform-when and conditional subitems.</p>
<pre class="Example"><span class="code SchemaTag">
@@ -409,7 +409,7 @@ demonstrates the use of commands, perform-when and conditional subitems.</p>
</span></pre>
<p></p>
-<br/>
+<br>
<p class="note SchemaCopyright">
Copyright (c) 2004, 2007 IBM Corporation and others.<br>
All rights reserved. This program and the accompanying materials are made
diff --git a/org.eclipse.ui.cheatsheets/schema/compositeContentFile.html b/org.eclipse.ui.cheatsheets/schema/compositeContentFile.html
index 6962736fb..606dd027a 100644
--- a/org.eclipse.ui.cheatsheets/schema/compositeContentFile.html
+++ b/org.eclipse.ui.cheatsheets/schema/compositeContentFile.html
@@ -23,11 +23,11 @@
<p></p>
<p class="ConfigMarkupElementDesc">
The root element of a composite cheatsheet</p>
-<br/>
+<br>
<ul class="ConfigMarkupAttlistDesc">
<li><b>name</b> - The name of the composite cheat sheet which will be displayed in large font when the composite cheat sheet is opened.</li>
</ul>
-<br/><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.taskGroup">taskGroup</a> ((<a href="#e.task">task</a> | <a href="#e.taskGroup">taskGroup</a>)+ , <a href="#e.intro">intro</a>? , <a href="#e.onCompletion">onCompletion</a>? , <a href="#e.dependency">dependency</a>*)&gt;</p>
+<br><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.taskGroup">taskGroup</a> ((<a href="#e.task">task</a> | <a href="#e.taskGroup">taskGroup</a>)+ , <a href="#e.intro">intro</a>? , <a href="#e.onCompletion">onCompletion</a>? , <a href="#e.dependency">dependency</a>*)&gt;</p>
<p class="code SchemaDtd">&lt;!ATTLIST taskGroup</p>
<p class="code SchemaDtdAttlist">kind&nbsp;(set|sequence|choice) "set"<p class="code SchemaDtdAttlist">name&nbsp;CDATA #REQUIRED<p class="code SchemaDtdAttlist">id&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class="code SchemaDtdAttlist">skip&nbsp;(true | false) "false"&gt;</p>
<p></p>
@@ -35,14 +35,14 @@ The root element of a composite cheatsheet</p>
A task group represents a collection of related tasks. If the kind is "choice" only one of the child tasks need to be completed. If the kind is "set" or "sequence" all children must be completed.
Note that the child elements &lt;task&gt;, &lt;taskGroup&gt;, &lt;intro&gt;, &lt;onCompletion&gt; and &lt;dependency&gt; may occur in any order. The order of the &lt;task&gt; and &lt;taskGroup&gt; elements determines the order in which they will be displayed and in the case of a sequence the order in which they must be performed.</p>
-<br/>
+<br>
<ul class="ConfigMarkupAttlistDesc">
<li><b>kind</b> - The kind of this task group which can be "set", "sequence" or "choice". If the kind is set or sequence this task group is complete when all of its child tasks/task groups have been completed. In addition the subtasks of a sequence must be completed in order. A choice is complete when any of its subtasks has been completed.</li>
<li><b>name</b> - The name of this task group which will be displayed in the task explorer.</li>
<li><b>id</b> - An id for this task group which is required if this task group is referenced by a dependency element.</li>
<li><b>skip</b> - If true this group of tasks may be skipped.</li>
</ul>
-<br/><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.task">task</a> (<a href="#e.intro">intro</a>? , <a href="#e.onCompletion">onCompletion</a>? , <a href="#e.param">param</a>* , <a href="#e.dependency">dependency</a>*)&gt;</p>
+<br><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.task">task</a> (<a href="#e.intro">intro</a>? , <a href="#e.onCompletion">onCompletion</a>? , <a href="#e.param">param</a>* , <a href="#e.dependency">dependency</a>*)&gt;</p>
<p class="code SchemaDtd">&lt;!ATTLIST task</p>
<p class="code SchemaDtdAttlist">kind&nbsp;CDATA "set"<p class="code SchemaDtdAttlist">name&nbsp;CDATA #REQUIRED<p class="code SchemaDtdAttlist">id&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class="code SchemaDtdAttlist">skip&nbsp;(true | false) "false"&gt;</p>
<p></p>
@@ -50,20 +50,20 @@ Note that the child elements &lt;task&gt;, &lt;taskGroup&gt;, &lt;intro&gt;, &lt
A leaf task within a composite cheat sheet. A task does not have children, but it does have a task editor which shows in the lower/right hand pane of the cheat sheet view. The task kind determines which task editor will be opened, a task kind of "cheatsheet" represents a simple cheatsheet. Other task kinds may be contributed.
Note that the child elements &lt;intro&gt;, &lt;onCompletion&gt;, &lt;param&gt; and &lt;dependency&gt; may occur in any order.</p>
-<br/>
+<br>
<ul class="ConfigMarkupAttlistDesc">
<li><b>kind</b> - The task kind. A task kind of "cheatsheet" represents a simple cheatsheet, other task kinds can be contributed using the extension point org.eclipse.ui.cheatsheets.cheatSheetContent.</li>
<li><b>name</b> - The name of this task which will be displayed in the task explorer.</li>
<li><b>id</b> - An id for this task group which is required if this task group is referenced by a dependency element.</li>
<li><b>skip</b> - If true this task may be skipped.</li>
</ul>
-<br/><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.param">param</a> EMPTY&gt;</p>
+<br><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.param">param</a> EMPTY&gt;</p>
<p class="code SchemaDtd">&lt;!ATTLIST param</p>
<p class="code SchemaDtdAttlist">name&nbsp;&nbsp;CDATA #REQUIRED<p class="code SchemaDtdAttlist">value&nbsp;CDATA #REQUIRED&gt;</p>
<p></p>
<p class="ConfigMarkupElementDesc">
A parameter to a task within a composite cheatsheet. Each parameter has a name and value, both of which are strings. A task may have any number of parameters, two parameters for a single task may not share the same name.</p>
-<br/>
+<br>
<ul class="ConfigMarkupAttlistDesc">
<li><b>name</b> - The name of this parameter. A task of kind="cheatsheet" can have the following parameters:
@@ -74,29 +74,29 @@ A parameter to a task within a composite cheatsheet. Each parameter has a name a
<p>showIntro: A boolean parameter with default value of true. If "false" the cheat sheet when started will initially show the first step rather than the introduction.</p></li>
<li><b>value</b> - The value of this parameter.</li>
</ul>
-<br/><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.intro">intro</a> (#PCDATA)&gt;</p>
+<br><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.intro">intro</a> (#PCDATA)&gt;</p>
<p></p>
<p class="ConfigMarkupElementDesc">
Contains the text which will be displayed before this task has been started. May contain
<a href="../../../org.eclipse.platform.doc.isv/guide/forms_controls_text_markup.htm">form text markup</a>.</p>
-<br/><br/>
+<br><br>
<p class="code SchemaDtd">&lt;!ELEMENT <a name="e.onCompletion">onCompletion</a> (#PCDATA)&gt;</p>
<p></p>
<p class="ConfigMarkupElementDesc">
Contains the text which will be displayed in the completion panel for this task. May contain
<a href="../../../org.eclipse.platform.doc.isv/guide/forms_controls_text_markup.htm">form text markup</a>.</p>
-<br/><br/>
+<br><br>
<p class="code SchemaDtd">&lt;!ELEMENT <a name="e.dependency">dependency</a> EMPTY&gt;</p>
<p class="code SchemaDtd">&lt;!ATTLIST dependency</p>
<p class="code SchemaDtdAttlist">task&nbsp;CDATA #REQUIRED&gt;</p>
<p></p>
<p class="ConfigMarkupElementDesc">
Creates a dependency between two tasks or subtasks.</p>
-<br/>
+<br>
<ul class="ConfigMarkupAttlistDesc">
<li><b>task</b> - The id of the task or task group which must be completed before this task can be started.</li>
</ul>
-<br/><br/>
+<br><br>
<p class="note SchemaCopyright">
Copyright (c) 2006, 2007 IBM Corporation and others.<br>
All rights reserved. This program and the accompanying materials are made
diff --git a/org.eclipse.ui.intro/schema/introContentFileSpec.html b/org.eclipse.ui.intro/schema/introContentFileSpec.html
index 7fb897808..e584aa1f4 100644
--- a/org.eclipse.ui.intro/schema/introContentFileSpec.html
+++ b/org.eclipse.ui.intro/schema/introContentFileSpec.html
@@ -16,12 +16,12 @@
<p></p>
<p class="ConfigMarkupElementDesc">
The introContent element defines the body of the intro content file. The content file is made up of pages, shared groups that can be included in multiple pages, extensions to anchor points defined in other configurations, or replacements of existing elements.</p>
-<br/><br/>
+<br><br>
<p class="code SchemaDtd">&lt;!ELEMENT <a name="e.page">page</a> (<a href="#e.group">group</a> | <a href="#e.link">link</a> | <a href="#e.text">text</a> | <a href="#e.head">head</a> | <a href="#e.img">img</a> | <a href="#e.include">include</a> | <a href="#e.html">html</a> | <a href="#e.title">title</a> | <a href="#e.anchor">anchor</a> | <a href="#e.contentProvider">contentProvider</a>)+&gt;</p>
<p class="code SchemaDtd">&lt;!ATTLIST page</p>
<p class="code SchemaDtdAttlist">id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED<p class="code SchemaDtdAttlist">url&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class="code SchemaDtdAttlist">style&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class="code SchemaDtdAttlist">alt-style&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class="code SchemaDtdAttlist">filteredFrom&nbsp;(swt|html) <p class="code SchemaDtdAttlist">content&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class="code SchemaDtdAttlist">style-id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class="code SchemaDtdAttlist">shared-style&nbsp;(true | false) <p class="code SchemaDtdAttlist">bgImage&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED&gt;</p>
<p></p>
-<p class="ConfigMarkupElementDesc">
+<div class="ConfigMarkupElementDesc">
<p>
This element is used to describe a page to be displayed. The intro can display both dynamic and static pages. Content for dynamic pages is generated from the subelements of the page, described below. The style or alt-style will be applied depending on the presentation. The styles can be further enhanced by referencing the id or class-id.
</p>
@@ -33,8 +33,8 @@ The home page, whose id is specified in the presentation element of the intro co
</p>
<p>
The subelements used in a dynamic page are as follows: A <b>group</b> subelement is used to group related content and apply style across the grouped content. A <b>link</b> subelement defines a link which can be used to link to a static or dynamic page and run an intro action/command. A link is normally defined at the page level to navigate between main pages versus links within a page. A <b>text</b> subelement defines textual content at the page level. A <b>head</b> subelement is only applicable for the Web based presentation and allows for additional html to be added to the HTML <b>head</b> section. This is useful for adding java scripts or extra style sheets. An <b>img</b> subelement defines image content for the page level. An <b>include</b> subelement allows for reuse of any element other than a page. An <b>html</b> subelement is only applicable for the Web based presentation and allows for the embedding or inclusion of html into the page's content. Embedding allows for a fully defined html file to be embeded within an HTML <b>object</b> by referencing the html file. Inclusion allows for including an html snippet directly from an html file. A <b>title</b> subelement defines the title of the page. An <b>anchor</b> subelement defines a point where external contributions can be made by an &lt;extensionContent&gt; element.
-</p></p>
-<br/>
+</p></div>
+<br>
<ul class="ConfigMarkupAttlistDesc">
<li><b>id</b> - A unique name that can be used to identify this page.</li>
<li><b>url</b> - The optional relative path to an HTML file. When using the Web based presentation, this HTML file will be displayed instead of any content defined for this page. This attribute is only applicable to the home page, which is identified in the presentation element of the intro config extension point. It is ignored for all other pages.</li>
@@ -52,13 +52,13 @@ Since 3.1, if the content of the external file is XHTML 1.0, then the page is re
<li><b>shared-style</b> - a boolean flag that controls the addition of the shared style into this page's list of styles. If <code>true</code> (the default), the shared style is added to this page's styles. If <code>false</code>, the shared style defined in the Intro configuration will not be injected into the styles of this page.</li>
<li><b>bgImage</b> - an optional URL of the image to use as a background for this group</li>
</ul>
-<br/><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.group">group</a> (<a href="#e.group">group</a> | <a href="#e.link">link</a> | <a href="#e.text">text</a> | <a href="#e.img">img</a> | <a href="#e.include">include</a> | <a href="#e.html">html</a> | <a href="#e.anchor">anchor</a> | <a href="#e.contentProvider">contentProvider</a>)*&gt;</p>
+<br><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.group">group</a> (<a href="#e.group">group</a> | <a href="#e.link">link</a> | <a href="#e.text">text</a> | <a href="#e.img">img</a> | <a href="#e.include">include</a> | <a href="#e.html">html</a> | <a href="#e.anchor">anchor</a> | <a href="#e.contentProvider">contentProvider</a>)*&gt;</p>
<p class="code SchemaDtd">&lt;!ATTLIST group</p>
<p class="code SchemaDtdAttlist">id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED<p class="code SchemaDtdAttlist">label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class="code SchemaDtdAttlist">style-id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class="code SchemaDtdAttlist">filteredFrom&nbsp;(swt|html) <p class="code SchemaDtdAttlist">computed&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(true | false) "false"<p class="code SchemaDtdAttlist">bgImage&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class="code SchemaDtdAttlist">expandable&nbsp;&nbsp;&nbsp;(true | false) "false"<p class="code SchemaDtdAttlist">expanded&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(true | false) "false"&gt;</p>
<p></p>
<p class="ConfigMarkupElementDesc">
Used to group related content, content that should have similar style applied, or content that will be included together in other pages.</p>
-<br/>
+<br>
<ul class="ConfigMarkupAttlistDesc">
<li><b>id</b> - unique identifier of the group</li>
<li><b>label</b> - a label or heading for this group</li>
@@ -69,37 +69,37 @@ Used to group related content, content that should have similar style applied, o
<li><b>expandable</b> - specifies whether or not the group can be expanded and collapsed. Defaults to false if not specified. If true, the expanded attribute will be consulted to determine whether or not the group should be expanded by default or not.</li>
<li><b>expanded</b> - specifies whether the expandable group should be expanded by default or not. Defaults to false (collapsed) if not specified. This only applies to expandable groups (where expandable was set to true). Has no effect otherwise.</li>
</ul>
-<br/><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.head">head</a> EMPTY&gt;</p>
+<br><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.head">head</a> EMPTY&gt;</p>
<p class="code SchemaDtd">&lt;!ATTLIST head</p>
<p class="code SchemaDtdAttlist">src&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED<p class="code SchemaDtdAttlist">encoding&nbsp;CDATA #IMPLIED&gt;</p>
<p></p>
<p class="ConfigMarkupElementDesc">
Direct HTML to include in a page'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. If the content contains substitution segments of the form $plugin:plugin_id$ then they will be replaced with the absolute path to the plugin with id plugin_id.
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).</p>
-<br/>
+<br>
<ul class="ConfigMarkupAttlistDesc">
<li><b>src</b> - relative or absolute URL to a file containing HTML to include directly into the HTML head section. If the content contains substitution segments of the form $plugin:plugin_id$ then they will be replaced with the absolute path to the plugin with id plugin_id.</li>
<li><b>encoding</b> - an optional attribute to specify the encoding of the inlined file containing the head snippet. Default is UTF-8. Since 3.0.1</li>
</ul>
-<br/><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.title">title</a> EMPTY&gt;</p>
+<br><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.title">title</a> EMPTY&gt;</p>
<p class="code SchemaDtd">&lt;!ATTLIST title</p>
<p class="code SchemaDtdAttlist">id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class="code SchemaDtdAttlist">style-id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class="code SchemaDtdAttlist">filteredFrom&nbsp;(swt|html) &gt;</p>
<p></p>
<p class="ConfigMarkupElementDesc">
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.</p>
-<br/>
+<br>
<ul class="ConfigMarkupAttlistDesc">
<li><b>id</b> - unique identifier of this title.</li>
<li><b>style-id</b> - A means to classifiy this element into a given category so that a common style may be applied</li>
<li><b>filteredFrom</b> - 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.</li>
</ul>
-<br/><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.link">link</a> (<a href="#e.text">text</a>? , <a href="#e.img">img</a>?)&gt;</p>
+<br><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.link">link</a> (<a href="#e.text">text</a>? , <a href="#e.img">img</a>?)&gt;</p>
<p class="code SchemaDtd">&lt;!ATTLIST link</p>
<p class="code SchemaDtdAttlist">url&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED<p class="code SchemaDtdAttlist">id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class="code SchemaDtdAttlist">label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class="code SchemaDtdAttlist">style-id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class="code SchemaDtdAttlist">filteredFrom&nbsp;(swt|html) &gt;</p>
<p></p>
<p class="ConfigMarkupElementDesc">
Can link to a static HTML file, an external web site, or can run an Intro URL action.</p>
-<br/>
+<br>
<ul class="ConfigMarkupAttlistDesc">
<li><b>url</b> - A valid URL to an external web site, a static html file, or an Intro URL that represents an Intro action. All intro URLs have the following form: http://org.eclipse.ui.intro/&lt;action name&gt;?param1=value1&amp;param2=value2 and will be processed by the intro framework.<br>
The predefined actions will be described using this format:<br>
@@ -188,26 +188,26 @@ will process the message parameter as "This is a message".<br>
<li><b>style-id</b> - A means to classifiy this link into a given category so that a common style may be applied.</li>
<li><b>filteredFrom</b> - 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.</li>
</ul>
-<br/><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.text">text</a> EMPTY&gt;</p>
+<br><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.text">text</a> EMPTY&gt;</p>
<p class="code SchemaDtd">&lt;!ATTLIST text</p>
<p class="code SchemaDtdAttlist">id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class="code SchemaDtdAttlist">style-id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class="code SchemaDtdAttlist">filteredFrom&nbsp;(swt|html) &gt;</p>
<p></p>
<p class="ConfigMarkupElementDesc">
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.</p>
-<br/>
+<br>
<ul class="ConfigMarkupAttlistDesc">
<li><b>id</b> - unique identifier of this text.</li>
<li><b>style-id</b> - A means to classify this element into a given category so that a common style may be applied</li>
<li><b>filteredFrom</b> - 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.</li>
</ul>
-<br/><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.img">img</a> EMPTY&gt;</p>
+<br><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.img">img</a> EMPTY&gt;</p>
<p class="code SchemaDtd">&lt;!ATTLIST img</p>
<p class="code SchemaDtdAttlist">src&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED<p class="code SchemaDtdAttlist">id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class="code SchemaDtdAttlist">alt&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class="code SchemaDtdAttlist">style-id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class="code SchemaDtdAttlist">filteredFrom&nbsp;(swt|html) &gt;</p>
<p></p>
<p class="ConfigMarkupElementDesc">
An image that represents intro content and not presentation (as opposed to decoration images defined in styles).</p>
-<br/>
+<br>
<ul class="ConfigMarkupAttlistDesc">
<li><b>src</b> - the file to load the image from</li>
<li><b>id</b> - unique identifier of this image</li>
@@ -215,7 +215,7 @@ An image that represents intro content and not presentation (as opposed to decor
<li><b>style-id</b> - A means to classifiy this image into a given category so that a common style may be applied.</li>
<li><b>filteredFrom</b> - 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.</li>
</ul>
-<br/><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.html">html</a> (<a href="#e.img">img</a> | <a href="#e.text">text</a>)&gt;</p>
+<br><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.html">html</a> (<a href="#e.img">img</a> | <a href="#e.text">text</a>)&gt;</p>
<p class="code SchemaDtd">&lt;!ATTLIST html</p>
<p class="code SchemaDtdAttlist">id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED<p class="code SchemaDtdAttlist">src&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED<p class="code SchemaDtdAttlist">type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(inline|embed) <p class="code SchemaDtdAttlist">style-id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class="code SchemaDtdAttlist">filteredFrom&nbsp;(swt|html) <p class="code SchemaDtdAttlist">encoding&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED&gt;</p>
<p></p>
@@ -225,7 +225,7 @@ direct HTML to include in the page either by embedding the entire document, or i
Embedding allows for a fully defined html file to be embedded within the dynamic page's content. An HTML <b>object</b> element is created that references the html file.
<br>
Inclusion allows for including an html snippet directly from a file into the dynamic html page.</p>
-<br/>
+<br>
<ul class="ConfigMarkupAttlistDesc">
<li><b>id</b> - unique identifier of this HTML element</li>
<li><b>src</b> - relative or absolute URL to a file containing HTML. If the content contains substitution segments of the form $plugin:plugin_id$ then they will be replaced with the absolute path to the plugin with id plugin_id.</li>
@@ -234,35 +234,35 @@ Inclusion allows for including an html snippet directly from a file into the dyn
<li><b>filteredFrom</b> - 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.</li>
<li><b>encoding</b> - an optional attribute to specify the encoding of the inlined file (in the case where type=inline is specified). If not specified, the default is UTF-8. Since 3.0.1</li>
</ul>
-<br/><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.include">include</a> EMPTY&gt;</p>
+<br><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.include">include</a> EMPTY&gt;</p>
<p class="code SchemaDtd">&lt;!ATTLIST include</p>
<p class="code SchemaDtdAttlist">path&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED<p class="code SchemaDtdAttlist">configId&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class="code SchemaDtdAttlist">merge-style&nbsp;(true | false) &gt;</p>
<p></p>
<p class="ConfigMarkupElementDesc">
expands an element targeted by the given path and optional configId attributes. Path should uniquely address an element within the specified configuration. It could point to a shared group defined at the configuration level, or any element in a page.</p>
-<br/>
+<br>
<ul class="ConfigMarkupAttlistDesc">
<li><b>path</b> - the path that uniquely represents the target element within the configuration (e.g. page/group1/group2). It may be a group element, or any element that may be contained in a group. You can not include a page.</li>
<li><b>configId</b> - identifier of a configuration where the included element is defined. If specified, it is assumed that the element to be included is specified in another configuration, and not the enclosing configuration. In this case, that external config is loaded and the element is resolved from that new config. If not specified, enclosing (parent) configuration of this include is assumed.</li>
<li><b>merge-style</b> - if <code>true</code>, style belonging to the page that owns the included element will be added to list of styles of the including page. If <code>false</code> (the default), the including page is responsible for controlling properties of the included element.</li>
</ul>
-<br/><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.anchor">anchor</a> EMPTY&gt;</p>
+<br><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.anchor">anchor</a> EMPTY&gt;</p>
<p class="code SchemaDtd">&lt;!ATTLIST anchor</p>
<p class="code SchemaDtdAttlist">id&nbsp;CDATA #REQUIRED&gt;</p>
<p></p>
<p class="ConfigMarkupElementDesc">
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</p>
-<br/>
+<br>
<ul class="ConfigMarkupAttlistDesc">
<li><b>id</b> - unique id to identify this anchor.</li>
</ul>
-<br/><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.extensionContent">extensionContent</a> (<a href="#e.text">text</a> | <a href="#e.group">group</a> | <a href="#e.link">link</a> | <a href="#e.html">html</a> | <a href="#e.include">include</a>)+&gt;</p>
+<br><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.extensionContent">extensionContent</a> (<a href="#e.text">text</a> | <a href="#e.group">group</a> | <a href="#e.link">link</a> | <a href="#e.html">html</a> | <a href="#e.include">include</a>)+&gt;</p>
<p class="code SchemaDtd">&lt;!ATTLIST extensionContent</p>
<p class="code SchemaDtdAttlist">path&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED<p class="code SchemaDtdAttlist">style&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class="code SchemaDtdAttlist">alt-style&nbsp;CDATA #IMPLIED<p class="code SchemaDtdAttlist">content&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class="code SchemaDtdAttlist">id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class="code SchemaDtdAttlist">name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED&gt;</p>
<p></p>
<p class="ConfigMarkupElementDesc">
The content to be added to the target anchor. Only one <code>extensionContent</code> or <code>replacementContent</code> is allowed in a given configExtension because if this extension could not be resolved (if the config could not be found, or the target anchor could not be found) then the pages and/or groups in the extension need to be ingnored.</p>
-<br/>
+<br>
<ul class="ConfigMarkupAttlistDesc">
<li><b>path</b> - the path that uniquely represents the path to an anchor. (e.g. page/group1/group2/anchorId) within the target configuration to be extended. It can only be an anchor which can be in any page or group, including shared groups at configuration level.</li>
<li><b>style</b> - A relative path to a CSS file which is applied to the page only when using the Web based presentation. The path is relative to the location of this xml content file. <br>
@@ -275,13 +275,13 @@ Since 3.1, styles can also be a comma separated list of styles. These styles wil
<li><b>id</b> - (since 3.2) a unique identifier of this extension required when used in conjunction with intro configurer.</li>
<li><b>name</b> - (since 3.2) a translatable name of this extension required when used in conjunction with intro configurer</li>
</ul>
-<br/><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.replacementContent">replacementContent</a> (<a href="#e.text">text</a> | <a href="#e.group">group</a> | <a href="#e.link">link</a> | <a href="#e.html">html</a> | <a href="#e.include">include</a>)+&gt;</p>
+<br><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.replacementContent">replacementContent</a> (<a href="#e.text">text</a> | <a href="#e.group">group</a> | <a href="#e.link">link</a> | <a href="#e.html">html</a> | <a href="#e.include">include</a>)+&gt;</p>
<p class="code SchemaDtd">&lt;!ATTLIST replacementContent</p>
<p class="code SchemaDtdAttlist">path&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED<p class="code SchemaDtdAttlist">style&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class="code SchemaDtdAttlist">alt-style&nbsp;CDATA #IMPLIED<p class="code SchemaDtdAttlist">content&nbsp;&nbsp;&nbsp;CDATA #IMPLIED&gt;</p>
<p></p>
<p class="ConfigMarkupElementDesc">
(since 3.3) The content to replace the target element. Only one <code>extensionContent</code> or <code>replacementContent</code> is allowed in a given configExtension because if this extension could not be resolved (if the config could not be found, or the target element could not be found) then the pages and/or groups in the extension need to be ignored.</p>
-<br/>
+<br>
<ul class="ConfigMarkupAttlistDesc">
<li><b>path</b> - the path that uniquely represents the path to the element to be replaced. (e.g. page/group1/group2/elementId) within the target configuration to be extended. To replace content contributed from an <code>extensionContent</code>, you may use a path of the form <code>pageId/@extension_id/path_in_extension</code> and it will be resolved to the specified extension.</li>
<li><b>style</b> - A relative path to a CSS file which is applied to the page only when using the Web based presentation. The path is relative to the location of this xml content file. <br>
@@ -292,7 +292,7 @@ Since 3.1, styles can also be a comma separated list of styles. These styles wil
Since 3.1, styles can also be a comma separated list of styles. These styles will be used when creating the SWT presentation of the welcome page.</li>
<li><b>content</b> - if content is defined, it is assumed that the extension content is defined in an external XHTML file. In that case the resource pointed to by this content attribute is loaded and the path attribute is now resolved in this external file. since 3.1</li>
</ul>
-<br/><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.contentProvider">contentProvider</a> (<a href="#e.text">text</a>?)&gt;</p>
+<br><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.contentProvider">contentProvider</a> (<a href="#e.text">text</a>?)&gt;</p>
<p class="code SchemaDtd">&lt;!ATTLIST contentProvider</p>
<p class="code SchemaDtdAttlist">id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED<p class="code SchemaDtdAttlist">class&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED<p class="code SchemaDtdAttlist">pluginId&nbsp;CDATA #IMPLIED&gt;</p>
<p></p>
@@ -300,25 +300,25 @@ Since 3.1, styles can also be a comma separated list of styles. These styles wil
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. Since 3.0.1</p>
-<br/>
+<br>
<ul class="ConfigMarkupAttlistDesc">
<li><b>id</b> - unique identifier of this content provider element. It is a required attribute because having a unique id is what prevents the intro framework from reinstantiating this content provider class and recreating its content.</li>
<li><b>class</b> - A class that implements the IContentProvider interface</li>
<li><b>pluginId</b> - 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't come from the same plugin that defined the markup.</li>
</ul>
-<br/><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.hr">hr</a> EMPTY&gt;</p>
+<br><p class="code SchemaDtd">&lt;!ELEMENT <a name="e.hr">hr</a> EMPTY&gt;</p>
<p class="code SchemaDtd">&lt;!ATTLIST hr</p>
<p class="code SchemaDtdAttlist">id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class="code SchemaDtdAttlist">style-id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED<p class="code SchemaDtdAttlist">filteredFrom&nbsp;(swt|html) &gt;</p>
<p></p>
<p class="ConfigMarkupElementDesc">
a horizontal rule.</p>
-<br/>
+<br>
<ul class="ConfigMarkupAttlistDesc">
<li><b>id</b> - unique identifier of this hr</li>
<li><b>style-id</b> - A means to classify this element into a given category so that a common style may be applied</li>
<li><b>filteredFrom</b> - 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.</li>
</ul>
-<br/><br/>
+<br><br>
<p class="note SchemaCopyright">
Copyright (c) 2004, 2006 IBM Corporation and others.<br>
All rights reserved. This program and the accompanying materials are made

Back to the top