Note however that in the target supplied with the Samples Manager we eliminated the “eclipse” folder in the Delta Pack and so, as shown in figure 3-4, the eclipse segment was not needed in this case.

public class Application implements IApplication {
	public Object start(IApplicationContext context) {
		Display display = PlatformUI.createDisplay();
		try {
			int returnCode = PlatformUI.createAndRunWorkbench(display, new ApplicationWorkbenchAdvisor());
			if (returnCode == PlatformUI.RETURN_RESTART) {
				return IApplication.EXIT_RESTART;
			}
			return IApplication.EXIT_OK;
		} finally {
			display.dispose();
		}
	}

	public void stop() {
		if (!PlatformUI.isWorkbenchRunning())
			return;
		final IWorkbench workbench = PlatformUI.getWorkbench();
		final Display display = workbench.getDisplay();
		display.syncExec(new Runnable() {
			public void run() {
				if (!display.isDisposed())
					workbench.close();
			}
		});
	}
}

Page 60 — In the description of how to get to the launch configurations (section 4.3.2) the menu path should be Run > Run Configurations… and Run > Debug Configurations….  Similarly, Figure 4-12 shows an outdated view of the Run menu.

Page 277 — In the BrowserView code snippet the “nextAction” variable declared at the beginning of createControlPart() should be named “forwardAction” to match its use in the last line of the snippet.

Page 125 — When you add translatable messages to the plugin.properties file you should ensure that the bundle’s MANIFEST.MF is updated to indicate where the translations are to be found. For example,

Bundle-Localization: plugin

Below is a quick summary of the changes in this new version:

• General clean up of glitches and errata reported by readers/reviewers
• New target platform that is smaller and more complete
• Chapter 14 code updated to better reflect the use of p2
• Chapter 9 product definition updated to export and produce the correct launcher on Mac
• Fixes to avoid NPEs and other problems when login to a chat server was not possible

Check out the new samples and be sure to let us know on the forums if there are problems.

Page 208 — The features to be included in the Hyperbola feature are part of the target platform. In Eclipse 3.5.x there is a PDE bug that prevents features from software sites from being added to the target platform. This has been resolved in 3.6. To work around this, we have manually added the required features to the HyperbolaTarget project’s misc/features directory.  Alternatively, you can use Eclipse 3.6 to do your development.

Note as well that the org.eclipse.equinox.p2.user.ui feature is listed as the Equinox p2 Provisioning feature in the Galileo repository and is not included in the Equinox p2 SDK feature.

Page 210 — To get a binding for %aboutText you need to tell OSGi where to find translations. Do this by adding the following header to the Hyperbola bundle manifest:

Bundle-Localization: plugin

Page 211 – To be able to run or test the new p2 function, you have to export Hyperbola and be running it as a normal application. You also need to have a repository to which you can point Hyperbola for updates or new function. You can do this with the following steps:

Note — The Help UI requires the UI forms bundle (org.eclipse.ui.forms).  This is not part of the standard RCP feature and so typically would not be part of your target platform. We have added it manually in the provided target definition in the misc folder as a convenience. As an alternative, you could add the Eclipse Platform SDK feature from the Galileo repository to your target.  This includes UI forms, in addition to many other things, some of which you may find useful.