Skip to main content
aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorIvan Furnadjiev2013-06-04 10:46:43 +0000
committerIvan Furnadjiev2013-06-04 10:46:43 +0000
commitf549088fc40fc43df101ac800323b213f8dd0b75 (patch)
tree7bb1c47122ed6cbfcc85f0a95e7f608da7a1da9c /bundles/org.eclipse.rap.ui
parent2be3e656d893db24e70ed3c12040c0fc5668b546 (diff)
downloadorg.eclipse.rap-f549088fc40fc43df101ac800323b213f8dd0b75.tar.gz
org.eclipse.rap-f549088fc40fc43df101ac800323b213f8dd0b75.tar.xz
org.eclipse.rap-f549088fc40fc43df101ac800323b213f8dd0b75.zip
Update the documentation inside exsd files
Diffstat (limited to 'bundles/org.eclipse.rap.ui')
-rw-r--r--bundles/org.eclipse.rap.ui/schema/rap/branding.exsd29
-rw-r--r--bundles/org.eclipse.rap.ui/schema/rap/entrypoint.exsd10
-rw-r--r--bundles/org.eclipse.rap.ui/schema/rap/layouts.exsd66
-rw-r--r--bundles/org.eclipse.rap.ui/schema/rap/phaselistener.exsd20
-rw-r--r--bundles/org.eclipse.rap.ui/schema/rap/resources.exsd15
-rw-r--r--bundles/org.eclipse.rap.ui/schema/rap/serviceHandler.exsd29
-rw-r--r--bundles/org.eclipse.rap.ui/schema/rap/settingstores.exsd44
-rw-r--r--bundles/org.eclipse.rap.ui/schema/rap/stackPresentations.exsd30
-rw-r--r--bundles/org.eclipse.rap.ui/schema/rap/themeableWidgets.exsd28
-rw-r--r--bundles/org.eclipse.rap.ui/schema/rap/themes.exsd32
10 files changed, 146 insertions, 157 deletions
diff --git a/bundles/org.eclipse.rap.ui/schema/rap/branding.exsd b/bundles/org.eclipse.rap.ui/schema/rap/branding.exsd
index b019c1bf97..cfa8f802cd 100644
--- a/bundles/org.eclipse.rap.ui/schema/rap/branding.exsd
+++ b/bundles/org.eclipse.rap.ui/schema/rap/branding.exsd
@@ -6,7 +6,7 @@
<meta.schema plugin="org.eclipse.rap.ui" id="branding" name="Branding"/>
</appInfo>
<documentation>
- A branding adds customizations and styling to the UI of a RAP application. It can be used to set the title and icon displayed in the browser, or to apply a custom theme and styling. A branding is associated with a name and can be activated by using this name as the servlet name in the URL.
+ A branding adds customizations and styling to the UI of a RAP application. It can be used to set the title and icon displayed in the browser, or to apply a custom theme and styling. The branding is associated with &lt;code&gt;EntryPoint&lt;/code&gt; or &lt;code&gt;IApplication&lt;/code&gt; implementation.
&lt;p&gt;
Brandings can reside in a separate bundle, i.e. it is possible to brand applications without modifying their containing bundles.
&lt;/p&gt;
@@ -26,21 +26,21 @@ Brandings can reside in a separate bundle, i.e. it is possible to brand applicat
<attribute name="point" type="string" use="required">
<annotation>
<documentation>
-
+
</documentation>
</annotation>
</attribute>
<attribute name="id" type="string">
<annotation>
<documentation>
-
+
</documentation>
</annotation>
</attribute>
<attribute name="name" type="string">
<annotation>
<documentation>
-
+
</documentation>
<appInfo>
<meta.attribute translatable="true"/>
@@ -308,19 +308,16 @@ The icon should be in the .ico format for compatibility with all browsers.
<meta.section type="examples"/>
</appInfo>
<documentation>
- &lt;pre&gt;
+&lt;pre&gt;
&lt;extension
- point=&quot;org.eclipse.rap.ui.branding&quot;&gt;
- &lt;branding
- id=&quot;org.example.tea.teabranding&quot;
- servletName=&quot;tea&quot;
- defaultEntrypointId=&quot;org.example.tea.application&quot;
- themeId=&quot;org.example.tea.teatheme&quot;
- title=&quot;Tea Portal&quot;
- favicon=&quot;icons/favicon.ico&quot;
- body=&quot;body.html&quot;
- exitConfirmationClass=&quot;org.example.tea.ExitConfirmation&quot;&gt;
- &lt;/branding&gt;
+ point=&quot;org.eclipse.rap.ui.branding&quot;&gt;
+ &lt;branding
+ id=&quot;org.example.tea.teabranding&quot;
+ themeId=&quot;org.example.tea.teatheme&quot;
+ title=&quot;Tea Portal&quot;
+ favicon=&quot;icons/favicon.ico&quot;
+ body=&quot;body.html&quot;
+ &lt;/branding&gt;
&lt;/extension&gt;
&lt;/pre&gt;
</documentation>
diff --git a/bundles/org.eclipse.rap.ui/schema/rap/entrypoint.exsd b/bundles/org.eclipse.rap.ui/schema/rap/entrypoint.exsd
index 11acb038b0..fdb45bdb77 100644
--- a/bundles/org.eclipse.rap.ui/schema/rap/entrypoint.exsd
+++ b/bundles/org.eclipse.rap.ui/schema/rap/entrypoint.exsd
@@ -29,21 +29,21 @@ As an alternative to registering an entrypoint, Eclipse applications can also us
<attribute name="point" type="string" use="required">
<annotation>
<documentation>
-
+
</documentation>
</annotation>
</attribute>
<attribute name="id" type="string">
<annotation>
<documentation>
-
+
</documentation>
</annotation>
</attribute>
<attribute name="name" type="string">
<annotation>
<documentation>
-
+
</documentation>
<appInfo>
<meta.attribute translatable="true"/>
@@ -77,7 +77,7 @@ As an alternative to registering an entrypoint, Eclipse applications can also us
<attribute name="class" type="string">
<annotation>
<documentation>
- An implementation of &lt;code&gt;IEntryPoint&lt;/code&gt; which starts the application. Either this attribute or applicationId must be specified.
+ An implementation of &lt;code&gt;EntryPoint&lt;/code&gt; which starts the application. Either this attribute or applicationId must be specified.
</documentation>
<appInfo>
<meta.attribute kind="java" basedOn=":org.eclipse.rap.rwt.application.EntryPoint"/>
@@ -150,7 +150,7 @@ public class MyEntryPoint implements EntryPoint {
<meta.section type="examples"/>
</appInfo>
<documentation>
- &lt;pre&gt;
+&lt;pre&gt;
&lt;extension
id=&quot;org.eclipse.rap.demo.demoentrypoint&quot;
point=&quot;org.eclipse.rap.ui.entrypoint&quot;&gt;
diff --git a/bundles/org.eclipse.rap.ui/schema/rap/layouts.exsd b/bundles/org.eclipse.rap.ui/schema/rap/layouts.exsd
index 832139215b..0821b932ac 100644
--- a/bundles/org.eclipse.rap.ui/schema/rap/layouts.exsd
+++ b/bundles/org.eclipse.rap.ui/schema/rap/layouts.exsd
@@ -26,21 +26,21 @@ The default Layout can be defined by contributing to the &lt;code&gt;org.eclipse
<attribute name="point" type="string" use="required">
<annotation>
<documentation>
-
+
</documentation>
</annotation>
</attribute>
<attribute name="id" type="string">
<annotation>
<documentation>
-
+
</documentation>
</annotation>
</attribute>
<attribute name="name" type="string">
<annotation>
<documentation>
-
+
</documentation>
<appInfo>
<meta.attribute translatable="true"/>
@@ -97,14 +97,14 @@ The default Layout can be defined by contributing to the &lt;code&gt;org.eclipse
<attribute name="id" type="string" use="required">
<annotation>
<documentation>
-
+ The unique identifier for a Layout.
</documentation>
</annotation>
</attribute>
<attribute name="name" type="string">
<annotation>
<documentation>
-
+ This optional attribute is just to give the Layout a readable name.
</documentation>
</annotation>
</attribute>
@@ -125,36 +125,36 @@ The default Layout can be defined by contributing to the &lt;code&gt;org.eclipse
<meta.section type="examples"/>
</appInfo>
<documentation>
- The following is an example of a Layout with three LayoutSets:
-&lt;p&gt;
+ The following is an example of a Layout with three LayoutSets:
&lt;pre&gt;
&lt;extension
- id=&quot;org.eclipse.presentation.example.layout&quot;
- name=&quot;Example Layout&quot;
- point=&quot;org.eclipse.ui.presentations.Layouts&quot;&gt;
- &lt;LayoutSet
- class=&quot;org.eclipse.rap.ui.interactiondesign.example.layoutset.HeaderLayoutSet2&quot;
- id=&quot;header.layoutset&quot;
- name=&quot;Header2&quot;&gt;
- &lt;/LayoutSet&gt;
- &lt;LayoutSet
- class=&quot;org.eclipse.rap.ui.interactiondesign.example.layoutset.MacBarLayoutSet2&quot;
- id=&quot;macBar.layoutset&quot;
- name=&quot;MacBar 2&quot;&gt;
- &lt;/LayoutSet&gt;
- &lt;LayoutSet
- class=&quot;org.eclipse.rap.ui.interactiondesign.example.layoutset.FooterLayoutSet2&quot;
- id=&quot;footer.layoutset&quot;
- name=&quot;Footer&quot;&gt;
- &lt;/LayoutSet&gt;
- &lt;LayoutSet
- class=&quot;org.eclipse.rap.ui.interactiondesign.example.layoutset.NavigationPaneLayoutSet2&quot;
- id=&quot;navigationpane.layoutset&quot;
- name=&quot;NavigationPane&quot;&gt;
- &lt;/LayoutSet&gt;
- &lt;/extension&gt;
- &lt;/pre&gt;
- &lt;/p&gt;
+ point=&quot;org.eclipse.rap.ui.layouts&quot;&gt;
+ &lt;layout
+ id=&quot;org.eclipse.presentation.example.layout&quot;
+ name=&quot;Example Layout&quot;&gt;
+ &lt;layoutSet
+ class=&quot;org.eclipse.rap.ui.interactiondesign.example.layoutset.HeaderLayoutSet2&quot;
+ id=&quot;header.layoutset&quot;
+ name=&quot;Header2&quot;&gt;
+ &lt;/layoutSet&gt;
+ &lt;layoutSet
+ class=&quot;org.eclipse.rap.ui.interactiondesign.example.layoutset.MacBarLayoutSet2&quot;
+ id=&quot;macBar.layoutset&quot;
+ name=&quot;MacBar 2&quot;&gt;
+ &lt;/layoutSet&gt;
+ &lt;layoutSet
+ class=&quot;org.eclipse.rap.ui.interactiondesign.example.layoutset.FooterLayoutSet2&quot;
+ id=&quot;footer.layoutset&quot;
+ name=&quot;Footer&quot;&gt;
+ &lt;/layoutSet&gt;
+ &lt;layoutSet
+ class=&quot;org.eclipse.rap.ui.interactiondesign.example.layoutset.NavigationPaneLayoutSet2&quot;
+ id=&quot;navigationpane.layoutset&quot;
+ name=&quot;NavigationPane&quot;&gt;
+ &lt;/layoutSet&gt;
+ &lt;/layout&gt;
+&lt;/extension&gt;
+&lt;/pre&gt;
</documentation>
</annotation>
diff --git a/bundles/org.eclipse.rap.ui/schema/rap/phaselistener.exsd b/bundles/org.eclipse.rap.ui/schema/rap/phaselistener.exsd
index 806c49d027..37af416161 100644
--- a/bundles/org.eclipse.rap.ui/schema/rap/phaselistener.exsd
+++ b/bundles/org.eclipse.rap.ui/schema/rap/phaselistener.exsd
@@ -6,7 +6,7 @@
<meta.schema plugin="org.eclipse.rap.ui" id="phaselistener" name="PhaseListener"/>
</appInfo>
<documentation>
- The extension point is used to register a &lt;code&gt;PhaseListener&lt;/code&gt; implementation. PhaseListeners are objects that are registered to be notified at the beginning and ending of each phase of the request processing lifecycle (see &lt;code&gt;ILifeCycle&lt;/code&gt;). Extensions should provide a class that implements &lt;code&gt;org.eclipse.rap.rwt.lifecycle.PhaseListener&lt;/code&gt;.
+ The extension point is used to register a &lt;code&gt;PhaseListener&lt;/code&gt; implementation. PhaseListeners are objects that are registered to be notified at the beginning and ending of each phase of the request processing lifecycle (see &lt;code&gt;LifeCycle&lt;/code&gt;). Extensions should provide a class that implements &lt;code&gt;org.eclipse.rap.rwt.lifecycle.PhaseListener&lt;/code&gt;.
</documentation>
</annotation>
@@ -23,21 +23,21 @@
<attribute name="point" type="string" use="required">
<annotation>
<documentation>
-
+
</documentation>
</annotation>
</attribute>
<attribute name="id" type="string">
<annotation>
<documentation>
-
+
</documentation>
</annotation>
</attribute>
<attribute name="name" type="string">
<annotation>
<documentation>
-
+
</documentation>
<appInfo>
<meta.attribute translatable="true"/>
@@ -52,7 +52,7 @@
<attribute name="class" type="string" use="required">
<annotation>
<documentation>
-
+
</documentation>
<appInfo>
<meta.attribute kind="java" basedOn="org.eclipse.rap.rwt.lifecycle.PhaseListener"/>
@@ -76,14 +76,14 @@
<meta.section type="examples"/>
</appInfo>
<documentation>
- &lt;pre&gt;
+&lt;pre&gt;
&lt;extension
id=&quot;org.eclipse.rap.demo.phaselistenerextension&quot;
point=&quot;org.eclipse.rap.ui.phaselistener&quot;&gt;
&lt;entrypoint
- id=&quot;org.eclipse.rap.demo.phaselistener&quot;
- class=&quot;org.eclipse.rap.demo.DemoPhaseListener&quot; /&gt;
- &lt;/extension&gt;
+ id=&quot;org.eclipse.rap.demo.phaselistener&quot;
+ class=&quot;org.eclipse.rap.demo.DemoPhaseListener&quot; /&gt;
+&lt;/extension&gt;
&lt;/pre&gt;
</documentation>
</annotation>
@@ -101,7 +101,7 @@ import org.eclipse.rap.rwt.lifecycle.*;
public class DemoPhaseListener implements PhaseListener {
- public void beforePhase( final PhaseEvent event ) {
+ public void beforePhase( PhaseEvent event ) {
// ...
RWT.getLifeCycle().removePhaseListener( this );
}
diff --git a/bundles/org.eclipse.rap.ui/schema/rap/resources.exsd b/bundles/org.eclipse.rap.ui/schema/rap/resources.exsd
index 84044af17f..4e05fd6a01 100644
--- a/bundles/org.eclipse.rap.ui/schema/rap/resources.exsd
+++ b/bundles/org.eclipse.rap.ui/schema/rap/resources.exsd
@@ -23,21 +23,21 @@
<attribute name="point" type="string" use="required">
<annotation>
<documentation>
-
+
</documentation>
</annotation>
</attribute>
<attribute name="id" type="string">
<annotation>
<documentation>
-
+
</documentation>
</annotation>
</attribute>
<attribute name="name" type="string">
<annotation>
<documentation>
-
+
</documentation>
<appInfo>
<meta.attribute translatable="true"/>
@@ -106,14 +106,13 @@
<meta.section type="examples"/>
</appInfo>
<documentation>
- &lt;pre&gt;
+&lt;pre&gt;
&lt;extension
- id=&quot;example.customwidget.customjs&quot;
- point=&quot;org.eclipse.rap.ui.resources&quot;&gt;
- &lt;resource class=&quot;example.customwidget.CustomJavaScriptResource&quot;/&gt;
+ id=&quot;example.customwidget.customjs&quot;
+ point=&quot;org.eclipse.rap.ui.resources&quot;&gt;
+ &lt;resource class=&quot;example.customwidget.CustomJavaScriptResource&quot;/&gt;
&lt;/extension&gt;
&lt;/pre&gt;
-
</documentation>
</annotation>
diff --git a/bundles/org.eclipse.rap.ui/schema/rap/serviceHandler.exsd b/bundles/org.eclipse.rap.ui/schema/rap/serviceHandler.exsd
index 5c72041b12..92eebce7a5 100644
--- a/bundles/org.eclipse.rap.ui/schema/rap/serviceHandler.exsd
+++ b/bundles/org.eclipse.rap.ui/schema/rap/serviceHandler.exsd
@@ -26,21 +26,21 @@ A service handler can be accessed by a URL with a specific parameter. This URL c
<attribute name="point" type="string" use="required">
<annotation>
<documentation>
-
+
</documentation>
</annotation>
</attribute>
<attribute name="id" type="string">
<annotation>
<documentation>
-
+
</documentation>
</annotation>
</attribute>
<attribute name="name" type="string">
<annotation>
<documentation>
-
+
</documentation>
<appInfo>
<meta.attribute translatable="true"/>
@@ -55,7 +55,7 @@ A service handler can be accessed by a URL with a specific parameter. This URL c
<attribute name="id" type="string" use="required">
<annotation>
<documentation>
- A unique ID for this service manager. This ID is used to obtain the URL to access the service manager.
+ A unique ID for this service handler. This ID is used to obtain the URL to access the service handler.
</documentation>
</annotation>
</attribute>
@@ -88,18 +88,17 @@ A service handler can be accessed by a URL with a specific parameter. This URL c
<documentation>
Here&apos;s an example of an extension that registers two service handlers:
&lt;pre&gt;
- &lt;extension point=&quot;org.eclipse.rap.ui.serviceHandler&quot;&gt;
- &lt;serviceHandler
- class=&quot;org.eclipse.rap.ui.impl.ServiceHandler1&quot;
- id=&quot;myHandler1&quot;&gt;
- &lt;/serviceHandler&gt;
- &lt;serviceHandler
- class=&quot;org.eclipse.rap.ui.ServiceHandler2&quot;
- id=&quot;myHandler2&quot;&gt;
- &lt;/serviceHandler&gt;
- &lt;/extension&gt;
+&lt;extension point=&quot;org.eclipse.rap.ui.serviceHandler&quot;&gt;
+ &lt;serviceHandler
+ class=&quot;org.eclipse.rap.ui.impl.ServiceHandler1&quot;
+ id=&quot;myHandler1&quot;&gt;
+ &lt;/serviceHandler&gt;
+ &lt;serviceHandler
+ class=&quot;org.eclipse.rap.ui.ServiceHandler2&quot;
+ id=&quot;myHandler2&quot;&gt;
+ &lt;/serviceHandler&gt;
+&lt;/extension&gt;
&lt;/pre&gt;
-
</documentation>
</annotation>
diff --git a/bundles/org.eclipse.rap.ui/schema/rap/settingstores.exsd b/bundles/org.eclipse.rap.ui/schema/rap/settingstores.exsd
index c4e8beb7d4..d52866510c 100644
--- a/bundles/org.eclipse.rap.ui/schema/rap/settingstores.exsd
+++ b/bundles/org.eclipse.rap.ui/schema/rap/settingstores.exsd
@@ -6,13 +6,13 @@
<meta.schema plugin="org.eclipse.rap.ui" id="settingstores" name="Setting Stores"/>
</appInfo>
<documentation>
- This extension point allows developers to contribute additional &lt;code&gt;ISettingStore&lt;/code&gt; instances.
+ This extension point allows developers to contribute additional &lt;code&gt;SettingStore&lt;/code&gt; instances.
&lt;p&gt;
-An &lt;code&gt;ISettingStore&lt;/code&gt; provides persistent storage for settings (key value pairs of Strings), which are then available beyond the scope of a single session. An &lt;code&gt;ISettingStoreFactory&lt;/code&gt; is responsible for creating a particular kind of &lt;code&gt;ISettingStore&lt;/code&gt;.
+An &lt;code&gt;SettingStore&lt;/code&gt; provides persistent storage for settings (key value pairs of Strings), which are then available beyond the scope of a single session. An &lt;code&gt;SettingStoreFactory&lt;/code&gt; is responsible for creating a particular kind of &lt;code&gt;SettingStore&lt;/code&gt;.
&lt;p&gt;
Developers that want to implement their own setting store must provide a setting store factory and register it with the framework using this extension point.
&lt;p&gt;
-Note that at runtime only &lt;b&gt;one&lt;/b&gt; (out of all available) factories will be used to create new &lt;code&gt;ISettingStore&lt;/code&gt; instances. Which factory is used can be controlled in two ways:
+Note that at runtime only &lt;b&gt;one&lt;/b&gt; (out of all available) factories will be used to create new &lt;code&gt;SettingStore&lt;/code&gt; instances. Which factory is used can be controlled in two ways:
&lt;ul&gt;
&lt;li&gt;In a normal RAP deployment you can specify the factory to be used by placing the following property in the OSGi config.ini file: &lt;code&gt;org.eclipse.rap.rwt.settingStoreFactory=&lt;i&gt;id&lt;/i&gt;&lt;/code&gt; where &lt;i&gt;id&lt;/i&gt; identifies a particular factory element. Example:
&lt;pre&gt;
@@ -21,12 +21,12 @@ org.eclipse.rap.rwt.settingStoreFactory=file
&lt;/li&gt;
&lt;li&gt;In an RWT-only deployment you can specify the factory to be used by placing the following snippet in the web.xml file:&lt;br&gt;
&lt;pre&gt;
-&amp;lt;init-param&amp;gt;
- &amp;lt;param-name&amp;gt;org.eclipse.rap.rwt.settingStoreFactory&amp;lt;/param-name&amp;gt;
- &amp;lt;param-value&amp;gt;org.eclipse.rap.rwt.service.FileSettingStoreFactory&amp;lt;/param-value&amp;gt;
-&amp;lt;/init-param&amp;gt;
+&lt;init-param&gt;
+ &lt;param-name&gt;org.eclipse.rap.rwt.settingStoreFactory&lt;/param-name&gt;
+ &lt;param-value&gt;org.eclipse.rap.rwt.service.FileSettingStoreFactory&lt;/param-value&gt;
+&lt;/init-param&gt;
&lt;/pre&gt;
-&lt;li&gt;If nothing is specified, the class &lt;code&gt;WorkbenchFileSettingStoreFactory&lt;/code&gt; will be used in a regular RAP deployment. In an RWT only deployment the class &lt;code&gt;RWTFileSettingStoreFactory&lt;/code&gt; will be used instead.&lt;/li&gt;
+&lt;li&gt;If nothing is specified, the class &lt;code&gt;WorkbenchFileSettingStoreFactory&lt;/code&gt; will be used in a regular RAP deployment. In an RWT only deployment the class &lt;code&gt;FileSettingStoreFactory&lt;/code&gt; will be used instead.&lt;/li&gt;
&lt;/ul&gt;
</documentation>
</annotation>
@@ -112,18 +112,18 @@ org.eclipse.rap.rwt.settingStoreFactory=file
<meta.section type="examples"/>
</appInfo>
<documentation>
- &lt;pre&gt;
- &lt;extension
- point=&quot;org.eclipse.rap.ui.settingstores&quot;&gt;
- &lt;factory
- class=&quot;org.eclipse.rap.ui.internal.preferences.WorkbenchFileSettingStoreFactory&quot;
- id=&quot;file&quot;&gt;
- &lt;/factory&gt;
- &lt;factory
- class=&quot;org.eclipse.rap.rwt.service.FileSettingStoreFactory&quot;
- id=&quot;rwtfile&quot;&gt;
- &lt;/factory&gt;
- &lt;/extension&gt;
+&lt;pre&gt;
+&lt;extension
+ point=&quot;org.eclipse.rap.ui.settingstores&quot;&gt;
+ &lt;factory
+ class=&quot;org.eclipse.rap.ui.internal.preferences.WorkbenchFileSettingStoreFactory&quot;
+ id=&quot;file&quot;&gt;
+ &lt;/factory&gt;
+ &lt;factory
+ class=&quot;org.eclipse.rap.rwt.service.FileSettingStoreFactory&quot;
+ id=&quot;rwtfile&quot;&gt;
+ &lt;/factory&gt;
+&lt;/extension&gt;
&lt;/pre&gt;
</documentation>
</annotation>
@@ -135,7 +135,7 @@ org.eclipse.rap.rwt.settingStoreFactory=file
<documentation>
To obtain a setting store use &lt;code&gt;RWT.getSettingStore()&lt;/code&gt;. This will use the configured &lt;code&gt;org.eclipse.rap.rwt.service.SettingStoreFactory&lt;/code&gt; to generate and return an appropriate &lt;code&gt;org.eclipse.rap.rwt.service.SettingStore&lt;/code&gt; instance for this session.
&lt;p&gt;
-Developers wishing to provide their own setting store must implement &lt;code&gt;ISettingStore&lt;/code&gt; and &lt;code&gt;ISettingStoreFactory&lt;/code&gt; and contribute their factory using this extension point.
+Developers wishing to provide their own setting store must implement &lt;code&gt;SettingStore&lt;/code&gt; and &lt;code&gt;SettingStoreFactory&lt;/code&gt; and contribute their factory using this extension point.
</documentation>
</annotation>
@@ -146,7 +146,7 @@ Developers wishing to provide their own setting store must implement &lt;code&gt
<documentation>
RAP provides the following default implementations:
&lt;ul&gt;
-&lt;li&gt;&lt;code&gt;WorkbenchFileSettingStoreFactory&lt;/code&gt;, &lt;code&gt;RWTFileSettingStoreFactory&lt;/code&gt; and &lt;code&gt;FileSettingStore&lt;/code&gt;
+&lt;li&gt;&lt;code&gt;WorkbenchFileSettingStoreFactory&lt;/code&gt;, &lt;code&gt;FileSettingStoreFactory&lt;/code&gt; and &lt;code&gt;FileSettingStore&lt;/code&gt;
&lt;/li&gt;
&lt;/ul&gt;
</documentation>
diff --git a/bundles/org.eclipse.rap.ui/schema/rap/stackPresentations.exsd b/bundles/org.eclipse.rap.ui/schema/rap/stackPresentations.exsd
index 65ad143651..6439770a50 100644
--- a/bundles/org.eclipse.rap.ui/schema/rap/stackPresentations.exsd
+++ b/bundles/org.eclipse.rap.ui/schema/rap/stackPresentations.exsd
@@ -25,21 +25,21 @@ You can define default StackPresentations for a part using the &lt;code&gt;org.e
<attribute name="point" type="string" use="required">
<annotation>
<documentation>
-
+
</documentation>
</annotation>
</attribute>
<attribute name="id" type="string">
<annotation>
<documentation>
-
+
</documentation>
</annotation>
</attribute>
<attribute name="name" type="string">
<annotation>
<documentation>
-
+
</documentation>
<appinfo>
<meta.attribute translatable="true"/>
@@ -140,19 +140,19 @@ With this action you can implement configuration bahaviour e.g. this action can
<meta.section type="examples"/>
</appinfo>
<documentation>
- &lt;pre&gt;
+&lt;pre&gt;
&lt;extension
- point=&quot;org.eclipse.ui.presentations.StackPresentations&quot;&gt;
- &lt;stackPresentation
- actionClass=&quot;org.eclipse.rap.ui.interactiondesign.example.configaction.ExampleConfigAction&quot;
- actionIcon=&quot;icons/configure.png&quot;
- class=&quot;org.eclipse.rap.ui.interactiondesign.example.stacks.NavigationPaneStackPresentation&quot;
- id=&quot;org.eclipse.rap.ui.interactiondesign.navigationPaneStackPresentation&quot;
- menuIcon=&quot;icons/menuIcon.gif&quot;
- name=&quot;Navigation Pane&quot;
- type=&quot;view&quot;&gt;
- &lt;/stackPresentation&gt;
-&lt;/extension&gt;
+ point=&quot;org.eclipse.ui.presentations.StackPresentations&quot;&gt;
+ &lt;stackPresentation
+ actionClass=&quot;org.eclipse.rap.ui.interactiondesign.example.configaction.ExampleConfigAction&quot;
+ actionIcon=&quot;icons/configure.png&quot;
+ class=&quot;org.eclipse.rap.ui.interactiondesign.example.stacks.NavigationPaneStackPresentation&quot;
+ id=&quot;org.eclipse.rap.ui.interactiondesign.navigationPaneStackPresentation&quot;
+ menuIcon=&quot;icons/menuIcon.gif&quot;
+ name=&quot;Navigation Pane&quot;
+ type=&quot;view&quot;&gt;
+ &lt;/stackPresentation&gt;
+&lt;/extension&gt;
&lt;/pre&gt;
</documentation>
</annotation>
diff --git a/bundles/org.eclipse.rap.ui/schema/rap/themeableWidgets.exsd b/bundles/org.eclipse.rap.ui/schema/rap/themeableWidgets.exsd
index 09654d876b..35d73e3a28 100644
--- a/bundles/org.eclipse.rap.ui/schema/rap/themeableWidgets.exsd
+++ b/bundles/org.eclipse.rap.ui/schema/rap/themeableWidgets.exsd
@@ -29,21 +29,21 @@ None of these files are mandatory, files which are found are respected, but file
<attribute name="point" type="string" use="required">
<annotation>
<documentation>
-
+
</documentation>
</annotation>
</attribute>
<attribute name="id" type="string">
<annotation>
<documentation>
-
+
</documentation>
</annotation>
</attribute>
<attribute name="name" type="string">
<annotation>
<documentation>
-
+
</documentation>
<appInfo>
<meta.attribute translatable="true"/>
@@ -101,18 +101,16 @@ None of these files are mandatory, files which are found are respected, but file
<meta.section type="examples"/>
</appInfo>
<documentation>
- The following is an example of a themeable widget extension definition:
-&lt;p&gt;
+ The following is an example of a themeable widget extension definition:
&lt;pre&gt;
- &lt;extension
- point=&quot;org.eclipse.rap.ui.themeableWidgets&quot;&gt;
- &lt;widget
- id=&quot;my.custom.datepicker&quot;
- class=&quot;my.custom.controls.DatePicker&quot;&gt;
- &lt;/widget&gt;
- &lt;/extension&gt;
+&lt;extension
+ point=&quot;org.eclipse.rap.ui.themeableWidgets&quot;&gt;
+ &lt;widget
+ id=&quot;my.custom.datepicker&quot;
+ class=&quot;my.custom.controls.DatePicker&quot;&gt;
+ &lt;/widget&gt;
+&lt;/extension&gt;
&lt;/pre&gt;
-&lt;/p&gt;
</documentation>
</annotation>
@@ -121,7 +119,7 @@ None of these files are mandatory, files which are found are respected, but file
<meta.section type="apiInfo"/>
</appInfo>
<documentation>
-
+
</documentation>
</annotation>
@@ -130,7 +128,7 @@ None of these files are mandatory, files which are found are respected, but file
<meta.section type="implementation"/>
</appInfo>
<documentation>
-
+
</documentation>
</annotation>
diff --git a/bundles/org.eclipse.rap.ui/schema/rap/themes.exsd b/bundles/org.eclipse.rap.ui/schema/rap/themes.exsd
index b00817d23a..b3814f67b6 100644
--- a/bundles/org.eclipse.rap.ui/schema/rap/themes.exsd
+++ b/bundles/org.eclipse.rap.ui/schema/rap/themes.exsd
@@ -7,7 +7,7 @@
</appInfo>
<documentation>
This extension point is used to register custom RWT themes.
-An RWT theme is used to customize the look and feel of applications built with the Rich Ajax Platform. To create a custom theme, a CSS file must be provided. With this file the styling of one ore more widgets can be customized. A list of themeable widgets and properties can be found in the &quot;RAP Theming Reference&quot;.
+An RWT theme is used to customize the look and feel of applications built with the Remote Application Platform. To create a custom theme, a CSS file must be provided. With this file the styling of one ore more widgets can be customized. A list of themeable widgets and properties can be found in the &quot;RAP Theming Reference&quot;.
It is also possible to register contributions to existing RWT themes.
A theme contribution contains CSS rules that are appended to an existing theme. If more than one contributions are registered for the same theme, the order in which these contributions are appended is undefined. The user of this extension point must ensure that the rules specified in a theme contribution can not interfere with the rules in other theme contributions. Ideally, theme contributions contain only rules for custom variants.
@@ -138,28 +138,24 @@ A theme contribution contains CSS rules that are appended to an existing theme.
<meta.section type="examples"/>
</appInfo>
<documentation>
- The following is an example of a theme extension with a new theme:
-&lt;p&gt;
+ The following is an example of a theme extension with a new theme:
&lt;pre&gt;
- &lt;extension point=&quot;org.eclipse.rap.ui.themes&quot;&gt;
- &lt;theme
- id=&quot;my.application.aquablue&quot;
- name=&quot;Aqua Blue Theme&quot;
- file=&quot;aqua-blue.css&quot; /&gt;
- &lt;/extension&gt;
+&lt;extension point=&quot;org.eclipse.rap.ui.themes&quot;&gt;
+ &lt;theme
+ id=&quot;my.application.aquablue&quot;
+ name=&quot;Aqua Blue Theme&quot;
+ file=&quot;aqua-blue.css&quot; /&gt;
+&lt;/extension&gt;
&lt;/pre&gt;
-&lt;/p&gt;
The following is an example of a theme extension that defines a contribution to an existing theme:
-&lt;p&gt;
&lt;pre&gt;
- &lt;extension point=&quot;org.eclipse.rap.ui.themes&quot;&gt;
- &lt;themeContribution
- themeId=&quot;my.application.aquablue&quot;
- file=&quot;aqua-blue-additions.css&quot; /&gt;
- &lt;/extension&gt;
+&lt;extension point=&quot;org.eclipse.rap.ui.themes&quot;&gt;
+ &lt;themeContribution
+ themeId=&quot;my.application.aquablue&quot;
+ file=&quot;aqua-blue-additions.css&quot; /&gt;
+&lt;/extension&gt;
&lt;/pre&gt;
-&lt;/p&gt;
</documentation>
</annotation>
@@ -169,7 +165,7 @@ The following is an example of a theme extension that defines a contribution to
<meta.section type="implementation"/>
</appInfo>
<documentation>
- The RAP demo plugin &lt;code&gt;org.eclipse.rap.demo&lt;/code&gt; contains an example of a theme extension.
+ The RAP demo plugin &lt;code&gt;org.eclipse.rap.design.example&lt;/code&gt; contains an example of a theme extension.
</documentation>
</annotation>

Back to the top