| <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML> |
| <HEAD> |
| |
| <meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." > |
| |
| <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1"> |
| <META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css"> |
| |
| <LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css"> |
| <TITLE> |
| Defining a rich client application |
| </TITLE> |
| |
| <link rel="stylesheet" type="text/css" HREF="../book.css"> |
| </HEAD> |
| <BODY BGCOLOR="#ffffff"> |
| <H2> |
| Defining a rich client application</H2> |
| <p> |
| The definition of a rich client application plug-in starts out similarly to the other plug-ins we've been |
| studying. The only difference in the first part of the markup is that the list of required plug-ins is much |
| smaller than we've been used to!</p> |
| <pre> |
| <?xml version="1.0" encoding="UTF-8"?> |
| <?eclipse version="3.0"?> |
| <plugin |
| id="org.eclipse.ui.examples.rcp.browser" |
| name="%pluginName" |
| version="3.0.0" |
| provider-name="%providerName"> |
| |
| <runtime> |
| <library name="browser.jar"> |
| </library> |
| </runtime> |
| <requires> |
| <import plugin="org.eclipse.core.runtime"/> |
| <import plugin="org.eclipse.ui"/> |
| </requires> |
| </pre> |
| <P> |
| Up to now, we've contributed function to the platform workbench by declaring extensions that |
| add elements to the workbench. In all of the <tt>plugin.xml</tt> content that we've reviewed so far, |
| we've only looked at individual contributions to a workbench that is assumed to be there. On the rich |
| client platform, there is no application already defined. Your rich client plug-in is the one |
| responsible for specifying the class that should be executed when the platform is started. This |
| is done in the <a href="../reference/extension-points/org_eclipse_core_runtime_applications.html"><b>org.eclipse.core.runtime.applications</b></a> |
| extension.</p> |
| <pre> <extension |
| point="org.eclipse.core.runtime.applications" |
| id="app" |
| name="%appName"> |
| <application> |
| <run |
| class="org.eclipse.ui.examples.rcp.browser.BrowserApp"> |
| </run> |
| </application> |
| </extension> |
| </pre> |
| <p>In this extension, we specify the class that should be run when the platform is first started. |
| This class must implement <b><a href="../reference/api/org/eclipse/core/runtime/IPlatformRunnable.html">IPlatformRunnable</a></b>, |
| which simply means that it must implement a <b>run</b> method. The run method is responsible for creating the SWT display and |
| starting up a workbench. The class <b><a href="../reference/api/org/eclipse/ui/PlatformUI.html">PlatformUI</a></b> |
| implements convenience methods for performing these tasks.</p> |
| <pre> public Object run(Object args) throws Exception { |
| Display display = PlatformUI.createDisplay(); |
| try { |
| int code = PlatformUI.createAndRunWorkbench(display, |
| <b>new BrowserAdvisor()</b>); |
| // exit the application with an appropriate return code |
| return code == PlatformUI.RETURN_RESTART |
| ? EXIT_RESTART |
| : EXIT_OK; |
| } finally { |
| if (display != null) |
| display.dispose(); |
| } |
| } |
| </pre> |
| <p>The call to <b>createAndRunWorkbench</b> will not return until the workbench is closed. The SWT event loop and other |
| low-level logistics are handled inside this method. At this stage, it's not so important |
| that you understand the underlying mechanics in running an SWT application. This code can be copied to your rich client |
| application with minimal changes. In fact, the hook for you to add your own functionality is the <b>WorkbenchAdvisor</b> |
| that is passed as an argument when the workbench is created. Let's take a closer look.</p> |
| |
| </BODY> |
| </HTML> |
