Follow Techotopia on Twitter

On-line Guides
All Guides
eBook Store
iOS / Android
Linux for Beginners
Office Productivity
Linux Installation
Linux Security
Linux Utilities
Linux Virtualization
Linux Kernel
System/Network Admin
Scripting Languages
Development Tools
Web Development
GUI Toolkits/Desktop
Mail Systems
Eclipse Documentation

How To Guides
General System Admin
Linux Security
Linux Filesystems
Web Servers
Graphics & Desktop
PC Hardware
Problem Solutions
Privacy Policy




Eclipse Plug-in Developer Guide
Previous Page Home Next Page

Making UI contributions

So far, we've seen that the main difference between a rich client platform plug-in and an Eclipse SDK plug-in is that the rich client plug-in is responsible for specifying the class that should be run when the platform is started. This class creates and runs a workbench window that is configured appropriately. What else is different about a rich client application? Not much, actually.

Once the infrastructure for the application workbench is in place, the techniques for adding function to the workbench are the same as those we used when we were extending the platform SDK workbench. The workbench UI extension points are used to add views, editors, menus, and all of the other contributions we know and love. In the case of the browser example, we'll be adding extensions for a perspective and a couple of views.

We were introduced to these extensions in Plugging into the workbench. For completeness, we'll take a look at how the browser example uses these extensions, but we'll assume that we already have a working knowledge of these concepts.

  Published under the terms of the Eclipse Public License Version 1.0 ("EPL") Design by Interspire