The CompareEditorInput supports the comparison of an arbitrary file/folder structure which can be displayed in an editor, dialog or view. @@ -118,7 +116,7 @@
The ApplyPatchOperation provides the ability to launch the Apply Patch wizard programmatically. The pages shown by the wizard are determined using the inputs to the operation. diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/compare_contentviewer.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/compare_contentviewer.htm index 293fe194837..45636744477 100644 --- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/compare_contentviewer.htm +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/compare_contentviewer.htm @@ -1,12 +1,10 @@ - +
- - - - + +For text based inputs, clients should subclass the StructureCreator class. This will enable the use of a shared document between multiple editors open on the same file. diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/console_shell.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/console_shell.htm index 09ce616dd0b..bb93a856f66 100644 --- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/console_shell.htm +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/console_shell.htm @@ -1,12 +1,10 @@ - +
- - - - + +When using the Equinox console standalone on the command line, the exit command can be used to terminate Equinox and return to the system command prompt.
- For both Telnet and SSH sessions, the session can be closed without terminating Equinox with +For both Telnet and SSH sessions, the session can be closed without terminating Equinox with the disconnect command.
+
So where is our new view? We can see all of the views that have been contributed by plug-ins using the Window > Show View menu.
-
+
This menu shows us what views are available for the current perspective. You can see all of the views that are contributed to the platform (regardless of perspective) by selecting Other.... This will display a list of view categories and the views available under each category.
@@ -61,7 +58,7 @@
+
There we are! The view called "Hello View" has been added to the Show View window underneath our category "Hello Category." The labels for our category and view were obtained from the extension point configuration markup in the plugin.xml.
@@ -77,7 +74,7 @@
+
There it is, our first plug-in! We'll cover more specifics about UI classes and extension points later on.
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_view.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_view.htm index e9884ad0509..ac472b12d4b 100644 --- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_view.htm +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_view.htm @@ -1,12 +1,10 @@ - + - - - - + +When using forms in a non-trivial way, it is important to share +
When using forms in a non-trivial way, it is important to share as much as possible to conserve resources. For this reason, color management should be separated from the toolkit when there are more than one form to handle.
-Of course, it is possible to create one toolkit per form, but +
Of course, it is possible to create one toolkit per form, but that is too wasteful if there are many forms. Instead:
Create one toolkit for all the forms that have the same life +
Create one toolkit for all the forms that have the same life cycle. For example, if creating a multi-page editor, create one toolkit per editor and dispose it when editor is disposed. All the pages in the editor should share this toolkit.
Create one color manager (FormColors) per
+
Create one color manager (FormColors) per
plug-in. When creating the toolkit, pass the color manager to the toolkit.
The toolkit will know that the colors are shared and will not dispose them.
Use platform support for fonts and if possible, use Use platform support for fonts and if possible, use
+
JFaceResources predefined fonts. Between default, 'banner' and
'header' fonts, you can accomplish a lot. Using many fonts is very confusing
for the user, and if you do manage your own, you must ensure alternatives
across platforms. The JFace fonts are guaranteed to work on all the
platforms Eclipse ships on.
Dispose the color manager on plug-in shutdown (don't assume +
Dispose the color manager on plug-in shutdown (don't assume that plug-in shutdown also means platform shutdown - Eclipse runtime can uninstall your plug-in dynamically while the platform is still running).
Use form color manager to allocate all the colors needed by +
Use form color manager to allocate all the colors needed by the forms.
ExpandableComposite acts similar to Group control
with the ability to collapse a portion of a page a toggle control:
ExpandableComposite ec = toolkit.createExpandableComposite(form.getBody(), ExpandableComposite.TREE_NODE| ExpandableComposite.CLIENT_INDENT); diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/forms_controls_text.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/forms_controls_text.htm index f94fea30d88..29304d57e75 100644 --- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/forms_controls_text.htm +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/forms_controls_text.htm @@ -1,12 +1,10 @@ - + - - - - + +FormText control @@ -15,33 +13,33 @@FormText control
-It is possible to achieve highly polished results using images, +
It is possible to achieve highly polished results using images, hyperlinks and text snippets mixed together in a form. However, when the mix of these elements is needed as part of one integral text, it is very hard to do. To remedy the problem, UI Forms offer a rudimentary text control that can do the following:
Render plain wrapped text
Render plain wrapped text
Render plain text but convert any segment that starts with +
Render plain text but convert any segment that starts with http:// into a hyperlink on the fly
Render text with XML tags
Render text with XML tags
In all the modes, FormText control is capable of
+
In all the modes, FormText control is capable of
rendering either a string or an input stream.
FormText rtext = toolkit.createFormText(form.getBody(), true); String data = "Here is some plain text for the text to render."; rtext.setText(data, false, false);
Second argument set to false means that we will
+
Second argument set to false means that we will
treat input text as-is, and the third that we will not try to expand URLs if
found.
It is possible to still handle the text as normal but automatically convert segments with http:// protocol into hyperlinks:
@@ -49,7 +47,7 @@Similar to the Similar to the Hyperlink control,
+ Hyperlink control,
FormText accepts listeners that implement HyperlinkListener.
These listeners will be notified about events related to the hyperlink
segments within the control.
The most powerful use of the FormText control is
+
The most powerful use of the FormText control is
when formatting tags are added to the text. The expected root tag is form.
It can have one or more children that can either be <p> or <li>.
Either of these can have normal text, text between <b> or
<span> tags, images, links and SWT controls. Images are
declared using <img href="image key"/> (no content), while
links are expressed using <a href="href">text</a>.
Some of the tags mentioned above have additional attributes. Tag +
Some of the tags mentioned above have additional attributes. Tag
<a> can accept nowrap="true" to block the link from
being wrapped into the new line. Tag <p> can have attribute
vspace="false" (true by default) that adds additional space
between paragraphs. Tag <li> has more attributes:
style - can be text, bullet
+
style - can be text, bullet
and image (default is bullet)
value - not used for bullet; if style is
+
value - not used for bullet; if style is
text, the value will be rendered instead in place of a bullet;
if style is image, value represents a key in the image table of
an image to be rendered in place of a bullet
vspace - the same as for the 'p' tag.
vspace - the same as for the 'p' tag.
indent - the number of pixels to indent text
indent - the number of pixels to indent text
bindent - the number of pixels to indent the bullet +
bindent - the number of pixels to indent the bullet (this number is independent from 'indent' - be careful not to overlap them)
UI Forms provide a basic support for multi-page editors you can +
UI Forms provide a basic support for multi-page editors you can build on.
-You should start building a UI Forms multi-page editor by +
You should start building a UI Forms multi-page editor by
extending FormEditor:
public class SimpleFormEditor extends FormEditor { @@ -63,13 +61,13 @@
In addition to form pages, you can add one or more text editors as a raw source alternative to the GUI pages. For this, you should call '
-addPage(IEditorPart, IEditorInput input)' method in the superclass.Recommended Practices for Eclipse Forms Multi-page Editors
-There are many ways you can go about writing a form-based +
Recommended Practices for Eclipse Forms Multi-page Editors
+There are many ways you can go about writing a form-based multi-page editor. It mostly depends on the type of content you are editing and proficiency of your users. There are two ways you can approach it:
-
- -
If the typical users are using the editor infrequently, raw +
If the typical users are using the editor infrequently, raw source is hard to edit by hand or complex, your users are not very technical etc., you should make COMPLETE pages that are fully capable of editing every aspect of the content without the need to turn to the raw source. In this @@ -77,7 +75,7 @@
Recommended Practices for Eclipse Forms Multi-page Editors
for regular work. In that respect, you can get away with a basic text editor. PDE extension point schema editor falls into this group.- -
If your users are more technical, have no problem editing +
If your users are more technical, have no problem editing the file by hand but would appreciate some help from time to time, consider providing a mixed experience - make a good source editor with all the add-ons like incremental outline, context assist, syntax highlighting etc. @@ -87,7 +85,7 @@
Recommended Practices for Eclipse Forms Multi-page Editors
marginal or debatable. However, functionality that was only available in GUI pages and was very high-quality was used readily.Creating a high quality multi-page editor with mixed GUI and +
Creating a high quality multi-page editor with mixed GUI and source pages has its challenges. Accepting that users will switch pages frequently requires a good model of the underlying content. The model should be directly tied to the underlying document(s) so that it is in sync both when diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/forms_layouts.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/forms_layouts.htm index 4657e69e83c..5257ed714c1 100644 --- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/forms_layouts.htm +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/forms_layouts.htm @@ -1,12 +1,10 @@ - +
- - - - + +UI Forms Layouts @@ -15,7 +13,7 @@UI Forms Layouts
-UI Forms offer two new layouts over those provided by SWT. These +
UI Forms offer two new layouts over those provided by SWT. These layouts implement the common interface and can be used on any UI SWT composite, but are typically used in conjunction with UI Forms. The purpose of these layouts is to manage form layout in a way that is similar to Web browsers. diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/forms_layouts_column.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/forms_layouts_column.htm index 1920c1030eb..234d174f96c 100644 --- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/forms_layouts_column.htm +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/forms_layouts_column.htm @@ -1,12 +1,10 @@ - +
- - - - + +ColumnLayout diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/forms_layouts_table.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/forms_layouts_table.htm index 1e101c01413..54ebdd8bccd 100644 --- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/forms_layouts_table.htm +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/forms_layouts_table.htm @@ -1,12 +1,10 @@ - + - - - - + +TableWrapLayout @@ -15,20 +13,20 @@TableWrapLayout
-TableWrapLayout is a grid-based layout very similar to SWT's versatile +
TableWrapLayout is a grid-based layout very similar to SWT's versatile GridLayout. It differs from GridLayout in that it uses a layout algorithm that works more like HTML tables. It tries to respect the provided client area width and grows vertically to compensate.
-There are many similarities between GridLayout and +
There are many similarities between GridLayout and TableWrapLayout. Both organize children in grids. Both have layout data that instructs the layout how to treat each control. Both can accept hints on which control should grab excess space, etc.
-However, they fundamentally differ in the approach to the +
However, they fundamentally differ in the approach to the layout.
-TableWrapLayoutstarts with columns. It computes minimal, preferred and maximum widths of each column and uses this information to assign excess space. It also tries to be fair when dividing space across columns so that there is no excess wrapping of some controls.It is possible to mix
GridLayoutand+It is possible to mix
- - - - + +GridLayoutandTableWrapLayoutbut the branch whereGridLayoutis used is the one where wrapping stops. This is quite acceptable if you don't want it to wrap (if the composite contains controls that cannot wrap anyway, like text, diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/forms_managed.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/forms_managed.htm index a9c3e050f80..0a373b45ce6 100644 --- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/forms_managed.htm +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/forms_managed.htm @@ -1,12 +1,10 @@ - +Managed forms @@ -15,16 +13,16 @@Managed forms
-Managed forms are wrappers that add life cycle management and +
Managed forms are wrappers that add life cycle management and notification to form members. Managed form is not a form by itself. It has a form and accepts registration of
-IFormPartelement. For eachIFormPart, it manages events like dirty state, saving, commit, focus, selection changes etc. In order to reach to the wrapped form widget, call the 'getForm()'method.There is a similarity between managed forms and JFace viewers - +
There is a similarity between managed forms and JFace viewers - the relationship between a form and a managed form is similar to the one between a
-Tablewidget andTableViewerin JFace, for example.Not every control on the form needs to be a form part. It is +
Not every control on the form needs to be a form part. It is better to group a number of controls and implement
- - - - + +IFormPartinterface for the group. Section is a natural group and Eclipse Form providesSectionPartimplementation. It implements the interface and diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/forms_master_details.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/forms_master_details.htm index 7d9070abfe1..665d8cd5052 100644 --- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/forms_master_details.htm +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/forms_master_details.htm @@ -1,12 +1,10 @@ - +Master/Details block @@ -15,36 +13,36 @@Master/Details block
-Master/Details is a pattern used throughout the UI world. It +
Master/Details is a pattern used throughout the UI world. It consists of a list or a tree ('master') and a set of properties ('details') driven by the selection in the master. Eclipse Forms provide the implementation of the pattern as a useful building block with the following properties:
-
- -
While details part is created, master part factory method is +
While details part is created, master part factory method is abstract and must be implemented by the subclass
- -
Master and details parts are children of the sash form and +
Master and details parts are children of the sash form and the ratio of the form space allocated for each can be changed by moving the sash.
- -
Through the nature of the sash form, master and details +
Through the nature of the sash form, master and details parts can be organized horizontally or vertically in the form.
The idea of master/details block is to create a tree or a table +
The idea of master/details block is to create a tree or a table section that fires the selection notification via the managed form. If the details part can handle the selected object, it should switch to the page for it and display properties. When building on top of the provided master/details block, subclasses should:
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/httpservice.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/httpservice.htm index 13caa2c1a07..5e02d577ed8 100644 --- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/httpservice.htm +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/httpservice.htm @@ -1,12 +1,10 @@ - + - - - - + +
- -
Create the master part (the one that drives the details)
+Create the master part (the one that drives the details)
- -
Contribute actions to the form tool bar (consumes +
Contribute actions to the form tool bar (consumes upper-right portion of the form in the title area)
- -
Register details pages, one for each distinct input that can +
Register details pages, one for each distinct input that can arrive from the master part
Http Service and JSP support diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/int.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/int.htm index 76c747f6eb0..3d376cdb7f9 100644 --- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/int.htm +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/int.htm @@ -1,12 +1,10 @@ - + - - - - + +Welcome to Eclipse diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/int_eclipse.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/int_eclipse.htm index dbf47de8127..dc9680cee99 100644 --- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/int_eclipse.htm +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/int_eclipse.htm @@ -1,17 +1,20 @@ - + - - - - +What is Eclipse? +@@ -67,77 +70,77 @@
The figure below depicts a simplified view.
-
+
The plug-ins that make up a subsystem define extension points for adding behavior to the platform. The following table describes the major runtime components of the platform that are implemented as one or more plug-ins.
-+
@@ -149,7 +152,7 @@
- + - Platform runtime
Defines the extension point and plug-in model. It dynamically + Defines the extension point and plug-in model. It dynamically discovers plug-ins and maintains information about the plug-ins and their extension points in a platform registry. Plug-ins are started up when required according to user operation of the platform. The runtime is implemented using the OSGi framework. - + - Resource management (workspace)
Defines API for creating and managing resources (projects, + Defines API for creating and managing resources (projects, files, and folders) that are produced by tools and kept in the file system. - + - Workbench UI
Implements the user cockpit for navigating the platform. It defines extension points for adding UI components such as views or menu actions. + Implements the user cockpit for navigating the platform. It defines extension points for adding UI components such as views or menu actions. It supplies additional toolkits (JFace and SWT) for building user interfaces. The UI services are structured so that a subset of the UI plug-ins can be used to build rich client applications that are independent of the resource management and workspace model. IDE-centric plug-ins define additional functionality for navigating and manipulating resources. - + - Help system
Defines extension points for plug-ins to provide help or + Defines extension points for plug-ins to provide help or other documentation as browsable books. - + - Team support
Defines a team programming model for managing and versioning resources. +Defines a team programming model for managing and versioning resources. - + - Debug Support
Defines a language independent debug model and UI classes + Defines a language independent debug model and UI classes for building debuggers and launchers. - + - Other Utilities
Other utility plug-ins supply functionality such as searching and comparing resources, performing builds using XML configuration files, + Other utility plug-ins supply functionality such as searching and comparing resources, performing builds using XML configuration files, and dynamically updating the platform from a server.
Out of the box - or off the web - the basic platform is an integrated development environment (IDE) for anything (and nothing in particular).
-
+
It's the plug-ins that determine the ultimate functionality of the platform. That's why the Eclipse SDK ships with additional plug-ins to enhance the diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/int_goal.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/int_goal.htm index 11d35caa157..44535bcdf8c 100644 --- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/int_goal.htm +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/int_goal.htm @@ -1,12 +1,10 @@ - +
- - - - + +The holy grail diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/int_who.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/int_who.htm index 5e5147f273a..5f5ee4bc416 100644 --- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/int_who.htm +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/int_who.htm @@ -1,12 +1,10 @@ - + - - - - + +Who needs a platform? diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/java_web_start.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/java_web_start.htm index de936f64c94..141bb5e4f4e 100644 --- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/java_web_start.htm +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/java_web_start.htm @@ -1,13 +1,10 @@ - + - - - - - + +Deploying eclipse based application with Java Web Start @@ -34,12 +31,12 @@Deploying Eclipse Based Application With Java Web Start
Step 1, Creating a Wrapper Feature
- Create a feature including all the features that are listed in your product definition;
-- Ensure that the org.eclipse.equinox.launcher plug-in is in the feature or in one of the included feature;
+- Ensure that the
org.eclipse.equinox.launcherplug-in is in the feature or in one of the included feature;Step 2, Exporting the Wrapper Feature
Note. Before proceeding with this step make sure to have a key store available. Eclipse does not provide any -facility to create key stores. You can use the keytool application that +facility to create key stores. You can use thekeytoolapplication that comes with the JDK. In addition, ensure that the eclipse you are developing with is running on a Java SDK instead of a JRE. If this constraint is not satisfied, the jar signing will fail. @@ -76,7 +73,7 @@Step 2, Exporting the Wrapper Feature
Step 3, Creating the Main JNLP File
-A Java Web Start application is described by JNLP files. They replace the eclipse.exe and the config.ini +
A Java Web Start application is described by JNLP files. They replace the
eclipse.exeand theconfig.inifiles by some equivalent mechanism. For example, JNLP has its own mechanism to control splash screen, ways to pass parameters and define what constitutes the application.@@ -150,7 +147,7 @@
Step 3, Creating the Main JNLP File
</jnlp>Tip: once you have created this file, you can store it in the wrapper feature in a folder such that on every export you will get the complete structure. -This folder needs to be referenced from the root property of the build.properties (e.g: root=<folderContainingMainJNLPFile>/). +This folder needs to be referenced from the
rootproperty of the build.properties (e.g:root=<folderContainingMainJNLPFile>/).Plug-ins Based Application
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/jface.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/jface.htm index edeb81c125a..30b702378fb 100644 --- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/jface.htm +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/jface.htm @@ -1,12 +1,10 @@ - + - - - - + +The JFace UI framework diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/jface_actions.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/jface_actions.htm index e34a3a96373..64f0976b7e1 100644 --- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/jface_actions.htm +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/jface_actions.htm @@ -1,12 +1,10 @@ - + - - - - + +Actions and contributions diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/jface_fieldassist.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/jface_fieldassist.htm index 8c641422114..586cbac52d4 100644 --- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/jface_fieldassist.htm +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/jface_fieldassist.htm @@ -1,12 +1,10 @@ - + - - - - + +Field assist diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/jface_operations.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/jface_operations.htm index eee960d429a..e1c038c9259 100644 --- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/jface_operations.htm +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/jface_operations.htm @@ -1,18 +1,14 @@ - + - - - +Long-running operations - +Long-running Operations
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/jface_resources.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/jface_resources.htm index d3439094b73..22fdad1ec42 100644 --- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/jface_resources.htm +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/jface_resources.htm @@ -1,12 +1,9 @@ - +
- - - - +User interface resources @@ -88,7 +85,7 @@
Images that are added to or retrieved from the registry must not be disposed by any client. The registry is responsible for disposing of the image since the images are shared by multiple clients. The registry will dispose of the images when the platform GUI system shuts down. Disposing images that late in the lifetime of an application may be a disadvantage.
- + Plug-in patterns for using images
diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/jface_viewers.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/jface_viewers.htm index 0fe97674ae0..7a6f9817fbf 100644 --- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/jface_viewers.htm +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/jface_viewers.htm @@ -1,12 +1,9 @@ - + - - - - +
Viewers @@ -44,7 +41,7 @@
Each viewer has an associated SWT widget. This widget can be created implicitly by supplying the parent Composite in a convenience viewer constructor, or explicitly by creating it first and supplying it to the viewer in its constructor.
-List-oriented Viewers
+List-oriented Viewers
Lists, trees, and tables share many common capabilities from a user's point of view, such as population with objects, selection, sorting, and filtering.
These viewers keep a list of domain objects (called elements) and display them in their diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/network.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/network.htm index 4b831ba9535..1a8f3155604 100644 --- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/network.htm +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/network.htm @@ -1,12 +1,10 @@ - +
- - - - + +Network support diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt.htm index 19d65b38645..72bdca71c21 100644 --- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt.htm +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt.htm @@ -1,12 +1,10 @@ - + - - - - + +Standard Widget Toolkit diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_error.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_error.htm index 78d1b0da118..f1faac5c451 100644 --- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_error.htm +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_error.htm @@ -1,12 +1,10 @@ - + - - - - + +Error handling diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_examples.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_examples.htm index 1c4a707c177..619ff5435ef 100644 --- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_examples.htm +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_examples.htm @@ -1,12 +1,10 @@ - + - - - - + +SWT Examples diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_graphics.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_graphics.htm index dd2e7d1f589..86f92897ae5 100644 --- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_graphics.htm +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_graphics.htm @@ -1,12 +1,10 @@ - + - - - - + +Graphics @@ -202,7 +200,7 @@Disposal
}); -Non-disposed Resource Handler
+Non-disposed Resource Handler
If a resource is detected to not have been disposed then
- - - - +Resource.setNonDisposeHandlerdiff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_layouts.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_layouts.htm index beb77a93169..20cc9939fb2 100644 --- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_layouts.htm +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_layouts.htm @@ -1,15 +1,18 @@ - +Layouts + @@ -86,10 +89,10 @@Layouts
The following table summarizes the standard layouts provided by SWT.
-+
- - + + diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_layouts_custom.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_layouts_custom.htm index 3c730df5c40..633123eca12 100644 --- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_layouts_custom.htm +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_layouts_custom.htm @@ -1,12 +1,10 @@ - + - - - - + + LayoutCustom Layouts diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_threading.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_threading.htm index 35c9341e735..d3c4180ecef 100644 --- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_threading.htm +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_threading.htm @@ -1,12 +1,10 @@ - + - - - - + +Threading issues @@ -91,7 +89,7 @@SWT UI thread
from a background thread. -Executing code from a non-UI thread
+Executing code from a non-UI thread
Applications that wish to call UI code from a non-UI thread must provide a Runnable that calls the UI code. The methods @@ -142,7 +140,7 @@
Executing code from a non-UI thread
executes. -The workbench and threads
+The workbench and threads
The threading rules are very clear when you are implementing an SWT application from the ground up since you control the creation of the event diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets.htm index b528c451b19..5dbb1f2f9f1 100644 --- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets.htm +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets.htm @@ -1,12 +1,10 @@ - +
- - - - + +Widgets diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets_controls.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets_controls.htm index 4adedab1ac9..8e6dcca466f 100644 --- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets_controls.htm +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets_controls.htm @@ -1,15 +1,18 @@ - + - - - - +Controls + @@ -25,10 +28,10 @@Controls
the concrete types of controls provided in this package. -+
- - + + diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets_custom.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets_custom.htm index 3db14e154f9..5183e41eb69 100644 --- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets_custom.htm +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets_custom.htm @@ -1,15 +1,18 @@ - + - - - - + WidgetCustom widgets + @@ -20,10 +23,10 @@Custom Widgets
which contains custom controls that are not in the core set of SWT controls but are needed to implement the platform workbench. -+
- - + + diff --git a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets_events.htm b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets_events.htm index d40a1228d2e..3e47c7a447b 100644 --- a/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets_events.htm +++ b/eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets_events.htm @@ -1,15 +1,18 @@ - + - - - - + ControlEvents + @@ -58,10 +61,10 @@Events
High Level Events
-+
- - + + @@ -213,10 +216,10 @@ Event Type
High Level Events
Low Level Events
-+
- - + + Event Type