| <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML> | |
| <HEAD> | |
| <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>Configuring PDE</title> | |
| </head> | |
| <BODY BGCOLOR="#ffffff"> | |
| <h1>Configuring PDE</h1> | |
| <p>Although PDE is part of the platform SDK, it may or may not be present in your | |
| particular installation. If it is not, it is easy to add by using the platform Update | |
| Manager. Once PDE is installed, it will configure itself with | |
| reasonable default values to be ready to use. However, some setup | |
| is recommended to create a clean working environment.</p> | |
| <h2>Run-time instance configuration</h2> | |
| <p>The most important variable you can set in PDE is the run-time workbench instance | |
| path. This is the path of the workbench installation that will be used to run and | |
| debug your plug-ins.</p> | |
| <p>The default choice of the run-time workbench is the host workbench i.e. the | |
| workbench you use for your development. | |
| This value is quite acceptable when you want to create plug-ins that will | |
| install into a platform configuration that is similar to your host | |
| setup. </p> | |
| <p>However, it is possible to use different workbench instances for development and | |
| run-time. For example, you might have a stable platform configuration that you use as a development tool, | |
| but wish to deploy your plug-ins in a different version. The run-time | |
| instance may be based on a new (and possibly less stable) technology, or may | |
| incorporate a different set of plug-ins than your host configuration. </p> | |
| <p>In both cases, it is important to use <b> different workspaces</b> for your host and | |
| run-time platform. Your host workspace location | |
| (where all your projects will go on your hard disk) is set when you launch your | |
| host development platform. | |
| To set up the location of your run-time workspace, choose the "Target | |
| Platform" page in the <b>Window>Preferences</b> dialog.</p> | |
| <p align="center"> | |
| <img border="0" src="images/preferences.gif" alt="PDE preferences - "Target Platform" page" width="607" height="541"></p> | |
| <p align="left">When you set the application location and press the <b>Reload</b> button, the | |
| list of plug-ins and fragments on the page will fill up with the discovered external plug-ins. By default, all these plug-ins will be | |
| invisible to PDE. You can make them visible by enabling them individually or | |
| pressing <b>Select All</b> button.</p> | |
| <p align="left">Note that workspace plug-ins and <b>enabled</b> external | |
| plug-ins will be used by PDE to resolve Java classes and plug-in dependencies. | |
| In the case where a workspace plug-in has the same id as an external plug-in, | |
| the workspace plug-in masks its external counterpart.</p> | |
| <i></i> | |
| <p> <br> | |
| <a href="../hglegal2003.htm"> | |
| <img src = "../images/ngibmcpy2003.gif" alt="Copyright IBM Corporation and others 2000, 2003" border="0" width="324" height="14"></a> | |
| </p> | |
| </body> | |
| </html> |