1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
|
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="GENERATOR" content="Microsoft FrontPage 6.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<meta http-equiv="Content-Style-Type" content="text/css">
<!-- default platform documentation stylesheets -->
<style>@import url("../../book.css");</style>
<style>@import url("book.css");</style>
<!-- default schema documentation stylesheets -->
<style>@import url("schema.css");</style>
<style>@import url("../../schema.css");</style>
<title>Intro Content File XML Format</title>
</head>
<body>
<h1>Intro Content File XML Format</h1>
<p>Version 3.1.0</p>
<p>This document describes the intro content file structure as a series of
DTD fragments.</p>
<h2><code>introContent</code></h2>
<br><p class=code id=dtd><!ELEMENT <a name="e.introContent">introContent</a> (<a href="#e.page">page</a>+ , <a href="#e.group">group</a>* , <a href="#e.extensionContent">extensionContent</a>*)></p>
<p></p>
<p class=ConfigMarkup id=elementDesc>
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, and extensions to anchor points defined in other configurations.</p>
<br><br>
<h2><code>page</code></h2>
<br><p class=code id=dtd><!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.hr">hr</a>* | <a href="#e.title">title</a>? | <a href="#e.anchor">anchor</a>*
| <a href="#e.contentProvider">contentProvider</a>*)></p>
<p class=code id=dtd><!ATTLIST page</p>
<p class=code id=dtdAttlist>url CDATA #IMPLIED<p class=code id=dtdAttlist>id CDATA #REQUIRED<p class=code id=dtdAttlist>style CDATA #IMPLIED<p class=code id=dtdAttlist>alt-style CDATA #IMPLIED<p class=code id=dtdAttlist>filteredFrom (swt|html)<br>
bgImage CDATA #IMPLIED <p class=code id=dtdAttlist>content CDATA #IMPLIED<p class=code id=dtdAttlist>style-id CDATA #IMPLIED></p>
<p></p>
<p class=ConfigMarkup id=elementDesc>
This element is used to describe a page to be displayed. The intro can display both dynamic and static pages.<br>
<br>
Content for dynamic pages is generated from the sub elements 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.<br>
<br>
Static pages allow for the reuse of existing HTML documents within one's introduction, and can be linked to from any static or dynamic page. Static pages are not defined in a page element, they are simply html files that can be linked to by other pages.<br>
<br>
The home page, whose id is specified in the presentation element of the intro config extension point, can have a url indicating that it is a static page. If no url is specified then the home page is assumed to be dynamic. All other pages described using the page element are dynamic.
<br>
Also note that when the SWT presentation is used and a static page is to be displayed, an external
browser is launched and the current page remains visible.<br>
<br>
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 <extensionContent> element.</p>
<br>
<ul class=ConfigMarkup id=attlistDesc>
<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>
<li><b>id</b> - A unique name that can be used to identify this page.</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>
Since 3.1, styles can also be a comma separated list of styles.
These styles will be injected into the HTML HEAD element in the order in which they are listed in the style attribute.</li>
<li><b>alt-style</b> - A relative path to a SWT presentation properties file which is applied to the page only when using the SWT based presentation.
The path is relative to the location of this xml content file.<br>
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>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>content</b> - an optional attribute which can define the location of an introContent.xml file that represents the content of this page. When this attribute is defined, all children and attributes in this page element, except id, are ignored. This is because the content of this page is now assumed to reside in the xml file pointed to by the content file attribute. When resolving to the content of this file, the page with an id that matches the id defined in this page element is chosen.
This separation of pages can be used when performance is an issue, as the content of a page is now loaded more lazily.Since 3.1, if the content of the external file is XHTML 1.0, then the page is rendered as is.</li>
<li><b>style-id</b> - A means to classify the page into a given category so that a common style may be applied.</li>
<li><strong>shared-style </strong> - a boolean flag that controls the addition of the shared style into this page's list of styles. If true (the default), the shared style is added to this page's styles. If false , 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 background image to be used for this
page</li>
</ul>
<h2><code>group</code></h2>
<br><p class=code id=dtd><!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>*)></p>
<p class=code id=dtd><!ATTLIST group</p>
<p class=code id=dtdAttlist>id CDATA #REQUIRED<p class=code id=dtdAttlist>label CDATA #IMPLIED<p class=code id=dtdAttlist>style-id CDATA #IMPLIED<p class=code>
<p class=code id=dtdAttlist>computed CDATA (true|false) "false"<br>
bgImage CDATA #IMPLIED</p>
<p class=code id=dtdAttlist>filteredFrom (swt|html) ></p>
<p></p>
<p class=ConfigMarkup id=elementDesc>
Used to group related content, content that should have similar style applied, or content that will be included together in other pages.</p>
<br>
<ul class=ConfigMarkup id=attlistDesc>
<li><b>id</b> - unique identifier of the group</li>
<li><b>label</b> - a label or heading for this group</li>
<li><b>style-id</b> - A means to classify this group 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>
<li><b>computed</b> - if <code>true</code>, the children of this group will be
provided by the intro configurer at run time. It is advised not to define any
children statically in this case.</li>
<li><b>bgImage</b> - an optional URL of the background image to be used for this
group</li>
</ul>
<h2><code>link</code></h2>
<br><p class=code id=dtd><!ELEMENT <a name="e.link">link</a> (<a href="#e.text">text</a>? , <a href="#e.img">img</a>?)></p>
<p class=code id=dtd><!ATTLIST link</p>
<p class=code id=dtdAttlist>id CDATA #IMPLIED<p class=code id=dtdAttlist>label CDATA #IMPLIED<p class=code id=dtdAttlist>url CDATA #REQUIRED<p class=code id=dtdAttlist>style-id CDATA #IMPLIED<p class=code id=dtdAttlist>filteredFrom (swt|html) ></p>
<p></p>
<p class=ConfigMarkup id=elementDesc>
Can link to a static HTML file, an external web site, or can run an Intro URL action.</p>
<br>
<ul class=ConfigMarkup id=attlistDesc>
<li><b>id</b> - A unique id that can be used to identify this link</li>
<li><b>label</b> - The text name of this link</li>
<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/<action name>?param1=value1&param2=value2 and will be processed by the intro framework.
</ul>
<br><br>
The predefined actions will be described using this format:
<br>
<p style="margin-left:15px;">
<b>action name</b> - description of action<br>
<i>action parameter1</i> - description of parameter<br>
<i>action parameter2 (optional)</i> - description of parameter<br>
<i>action parameter3 (optional) = ("true" | "false") "false"</i> - description of parameter, choice of either true or false and "false" is the default<br>
</p>
<br>
The following predefined actions are included in the intro framework:
<p style="margin-left:15px;">
<b>close</b> - closes the intro part<br>
no parameters required<br>
<br>
<b>execute</b> - executes the specified command. See the <code>serialize()</code> method on <code>org.eclipse.core.command.ParameterizedCommand</code> for details of the command serialization format. Since 3.2.<br>
<i>command</i> - a serialized <code>ParameterizedCommand</code><br>
<i>standby (optional) = ("true" | "false") "false"</i> - indicate whether to set the intro into standby mode after executing the command<br>
<br>
<b>navigate</b> - navigate through the intro pages in a given direction or return to the home page<br>
<i>direction = ("backward" | "forward" | "home")</i> - specifies the direction to navigate<br>
<br>
<b>openBrowser</b> -
open the url in an external browser. Since 3.1, this action relies on the workbench Browser support. This means that any user preferences set for the browser will be honored.<br>
<i>url</i> - a valid URL to an external web site or a static HTML file<br>
<i>pluginId (optional)</i> - only required if a static HTML file is specified. This is the id of the plug-in containing the file.</p>
<p style="margin-left:15px;"><b>openURL</b> - open the url embedded in the Welcome page. In the case of SWT presentation, the url is displayed in an external browser (similar to the openBrowser action above).
since 3.1 <br>
<i>url</i> - a valid URL to an external web site or to a local HTML file<br>
<i>pluginId (optional)</i> - if the url is relative, then this specifies the id of the plug-in containing the file.<br>
<br>
<b>runAction</b> - runs the specified action<br>
<i>class</i> - the fully qualified class name of the class that implements one of <code>org.eclipse.ui.intro.config.IIntroAction</code>, <code>org.eclipse.jface.action.IAction</code>, or <code>org.eclipse.ui.IActionDelegate</code><br>
<i>pluginId</i> - The id of the plug-in which contains the class.<br>
<i>standby (optional) = ("true" | "false") "false"</i> - indicate whether to set the intro into standby mode after executing the action<br>
additional parameters - any additional parameters are passed to actions that implement <code>org.eclipse.ui.intro.config.IIntroAction</code><br>
<br>
<b>setStandbyMode</b> - sets the state of the intro part<br>
<i>standby = ("true" | "false")</i> - true to put the intro part in its partially visible
standby mode, and false to make it fully visible<br>
<br>
<b>showHelp</b> - Open the help system.<br>
no parameters required<br>
<br>
<b>showHelpTopic</b> - Open a help topic.<br>
<i>id</i> - the URL of the help resource. (See Javadoc for <code>org.eclipse.ui.help.WorkbenchHelp.displayHelpResource</code><br>
<i>embed </i><i>(optional) = ("true" | "false") "true"</i> - indicates that the help resource needs to be displayed embedded as part of the welcome pages. Default is false. This flag is simply ignored in the case of the SWT presentation. since 3.1<br>
<em>embedTarget (optional) </em> - the path to a div in the current Welcome page that will hold the content of the Help topic. If specified, then <em>embed </em> is true by default and the embedded URL is inserted inside the div with the specified path. The path is relative to the page and so it should not start with the page id. The children of the div are replaced by the content of the URL. Only one div per page can be used as an embed target. This flag is simply ignored in the case of the SWT presentation. It is also unsupported when using XHTML as intro content. since 3.1
<p style="margin-left:15px;"><br>
<b>showMessage</b> - Displays a message to the user using a standard information dialog.<br>
<i>message</i> - the message to show the user<br>
<br>
<b>showStandby</b> - Sets the intro part to standby mode and shows the standbyContentPart with the given input<br>
<i>partId</i> - the id of the standbyContentPart to show<br>
<i>input</i> - the input to set on the standbyContentPart<br>
<br>
<b>showPage</b> - show the intro page with the given id<br>
<i>id</i> - the id of the intro page to show<br>
<i>standby (optional) = ("true" | "false") "false"</i> - indicate whether to set the intro into standby mode after showing the page</p>
<p style="margin-left:15px;"> If any of the parameters passed to these actions have special characters (ie: characters that are illegal in a URL), then they should be encoded using UTF-8 url encoding. To recieve these parametrs in there decoded state a special parameter, <em>decode = ("true" "false") </em> can be used to force a decode of these parameters when the Intro framework processes them. <br>
For example, the following Intro url: <br>
<em>http://org.eclipse.ui.intro/showMessage?message=This+is+a+message </em><br>
will process the message parameter as "This+is+a+message" <br>
whereas <br>
<em>http://org.eclipse.ui.intro/showMessage?message=This+is+a+message&amp;decode=true </em><br>
will process the message parameter as "This is a message". <br>
</p>
<br></li>
<li><b>style-id</b> - A means to classify 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>
<h2><code>html</code></h2>
<br><p class=code id=dtd><!ELEMENT <a name="e.html">html</a> (<a href="#e.img">img</a> | <a href="#e.text">text</a>)></p>
<p class=code id=dtd><!ATTLIST html</p>
<p class=code id=dtdAttlist>id CDATA #REQUIRED<p class=code id=dtdAttlist>src CDATA #REQUIRED<p class=code id=dtdAttlist>type (inline|embed) <p class=code id=dtdAttlist>style-id CDATA #IMPLIED<p class=code id=dtdAttlist>filteredFrom (swt|html) ><p class=code id=dtdAttlist>encoding CDATA #IMPLIED</p>
<p></p>
<p class=ConfigMarkup id=elementDesc>
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. 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.
<br>
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>
<ul class=ConfigMarkup id=attlistDesc>
<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>
<li><b>type</b> - if 'embed', a valid (full) HTML document will be embedded using HTML 'OBJECT' tag. If 'inline', value of 'src' will be treated as a snippet of HTML to emit 'in-place'. (if type is not specified, this html object is ignored by the intro configuration).</li>
<li><b>style-id</b> - A means to classify this HTML 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>
<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>
<h2><code>hr</code></h2>
<br><p class=code id=dtd0><!ELEMENT <a name="e.hr">hr</a> EMPTY></p>
<p class=code id=dtd1><!ATTLIST hr</p>
<p class=code id=dtdAttlist0>id CDATA #IMPLIED<p class=code id=dtdAttlist1>style-id CDATA #IMPLIED<p class=code id=dtdAttlist2>filteredFrom (swt|html) ></p>
<p></p>
<p class=ConfigMarkup id=elementDesc0>
a horizontal rule.</p>
<br>
<ul class=ConfigMarkup id=attlistDesc0>
<li><b>id</b> - unique identifier of this rule.</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>
<h2><code>title</code></h2>
<br><p class=code id=dtd><!ELEMENT <a name="e.title">title</a> EMPTY></p>
<p class=code id=dtd><!ATTLIST title</p>
<p class=code id=dtdAttlist>id CDATA #IMPLIED<p class=code id=dtdAttlist>style-id CDATA #IMPLIED<p class=code id=dtdAttlist>filteredFrom (swt|html) ></p>
<p></p>
<p class=ConfigMarkup id=elementDesc>
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>
<ul class=ConfigMarkup id=attlistDesc>
<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>
<h2><code>text</code></h2>
<br><p class=code id=dtd><!ELEMENT <a name="e.text">text</a> EMPTY></p>
<p class=code id=dtd><!ATTLIST text</p>
<p class=code id=dtdAttlist>id CDATA #IMPLIED<p class=code id=dtdAttlist>style-id CDATA #IMPLIED<p class=code id=dtdAttlist>filteredFrom (swt|html) ></p>
<p></p>
<p class=ConfigMarkup id=elementDesc>
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
beginning and ending with the p tag.</p>
<br>
<ul class=ConfigMarkup id=attlistDesc>
<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>
<h2><code>include</code></h2>
<br><p class=code id=dtd><!ELEMENT <a name="e.include">include</a> EMPTY></p>
<p class=code id=dtd><!ATTLIST include</p>
<p class=code id=dtdAttlist>configId CDATA #IMPLIED<p class=code id=dtdAttlist>path CDATA #REQUIRED<p class=code id=dtdAttlist>merge-style (true | false) ></p>
<p></p>
<p class=ConfigMarkup id=elementDesc>
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>
<ul class=ConfigMarkup id=attlistDesc>
<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>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>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>
<h2><code>head</code></h2>
<br><p class=code id=dtd><!ELEMENT <a name="e.head">head</a> EMPTY></p>
<p class=code id=dtd><!ATTLIST head</p>
<p class=code id=dtdAttlist>src CDATA #REQUIRED><p class=code id=dtdAttlist>encoding CDATA #IMPLIED</p>
<p></p>
<p class=ConfigMarkup id=elementDesc>
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
scripts 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>
<ul class=ConfigMarkup id=attlistDesc>
<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>
<h2><code>img</code></h2>
<br><p class=code id=dtd><!ELEMENT <a name="e.img">img</a> EMPTY></p>
<p class=code id=dtd><!ATTLIST img</p>
<p class=code id=dtdAttlist>id CDATA #REQUIRED<p class=code id=dtdAttlist>src CDATA #REQUIRED<p class=code id=dtdAttlist>alt CDATA #IMPLIED<p class=code id=dtdAttlist>style-id CDATA #IMPLIED<p class=code id=dtdAttlist>filteredFrom (swt|html) ></p>
<p></p>
<p class=ConfigMarkup id=elementDesc>
An image that represents intro content and not presentation (as opposed to decoration images defined in styles).</p>
<br>
<ul class=ConfigMarkup id=attlistDesc>
<li><b>id</b> - unique identifier of this image</li>
<li><b>src</b> - the file to load the image from</li>
<li><b>alt</b> - the alternative text to use when the image can not be loaded and as tooltip text for the image.</li>
<li><b>style-id</b> - A means to classify 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>
<h2><code>extensionContent</code></h2>
<br><p class=code id=dtd><!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>)></p>
<p class=code id=dtd><!ATTLIST extensionContent</p>
<p class=code id=dtdAttlist>style CDATA #IMPLIED<p class=code id=dtdAttlist>alt-style CDATA #IMPLIED<br>
id CDATA #IMPLIED<p class=code>name
CDATA #IMPLIED<p class=code id=dtdAttlist>path CDATA #REQUIRED></p>
<p></p>
<p class=ConfigMarkup id=elementDesc>
The content to be added to the target anchor. Only one extensionContent 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 element could not be found) then the pages and/or groups in the extension need to be
ignored.</p>
<br>
<ul class=ConfigMarkup id=attlistDesc>
<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>
Since 3.1, styles can also be a comma separated list of styles. These styles will be injected into the HTML HEAD element in the order in which they are listed in the style attribute. </li>
<li><b>alt-style</b> -
A relative path to a SWT presentation properies file which is applied to the page only when using the SWT based presentation. The path is relative to the location of this xml content file. <br>
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>path</b> - the path that uniquely represents the path to an anchor. (e.g.
<b>page/group1/group2/anchorId</b>) 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.
Since 3.2, path can also use format 'page/@'. This format delegates path
resolution to the intro configurer.</li>
<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>
<li><strong>content </strong>- 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>
<p></p>
<h2><code>anchor</code></h2>
<br><p class=code id=dtd><!ELEMENT <a name="e.anchor">anchor</a> EMPTY></p>
<p class=code id=dtd><!ATTLIST anchor</p>
<p class=code id=dtdAttlist>id CDATA #REQUIRED></p>
<p></p>
<p class=ConfigMarkup id=elementDesc>
an anchor is the element used to declare extensibility. It is a location in the
configuration that allows for external contributions. Only anchors are valid target values for the path attribute in an extensionContent</p>
<br>
<ul class=ConfigMarkup id=attlistDesc>
<li><b>id</b> - unique id to identify this anchor.</li>
</ul>
<h2 id="dtd"><code>contentProvider</code></h2>
<p class="code" id="dtd"> </p>
<p class="code" id="dtd"><!ELEMENT <a name="e.contentProvider">contentProvider</a>
(<a href="#e.text">text</a>)></p>
<p class="code" id="dtd"><!ATTLIST contentProvider</p>
<p class="code" id="dtdAttlist">id CDATA #REQUIRED </p>
<p class="code" id="dtdAttlist">pluginId CDATA #IMPLIED </p>
<p class="code" id="dtdAttlist">class CDATA #REQUIRED></p>
<p> </p>
<p class="ConfigMarkup" id="elementDesc">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>
<p><br>
</p>
<ul class="ConfigMarkup" id="attlistDesc">
<li><b>id</b> - unique identifier of this content provider element. </li>
<li><b>pluginId</b> - The id of the plug-in 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 plug-in that defined
the markup. </li>
<li><b>class</b> - A class that implements the IContentProvider interface </li>
</ul>
<p>
<br><br>
</p>
<p class=note id=copyright>
</p>
<br>
<p class=note id=copyright>
Copyright (c) 2004, 2006 IBM Corporation and others.<br>
All rights reserved. This program and the accompanying materials are made
available under the terms of the Eclipse Public License v1.0 which accompanies
this distribution, and is available at
<a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>
</p>
</body>
</html>
|
