| <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//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>Debug model presentation</TITLE> |
| |
| <link rel="stylesheet" type="text/css" HREF="../book.css"> |
| </HEAD> |
| <BODY BGCOLOR="#ffffff"> |
| <h3>Debug model presentation</h3> |
| <p>Since there is a generic, uniform model for debug elements in the platform, |
| it's possible to provide a starting point for implementing debugger UI |
| classes. The heart of the debugger UI support is the <b>debug model |
| presentation</b> (<a href="../reference/api/org/eclipse/debug/ui/IDebugModelPresentation.html"><b>IDebugModelPresentation</b></a>). |
| The debug model presentation is responsible for providing labels, images, and |
| editors associated with specific debug elements.</p> |
| <p>Plug-ins that define their own debug model typically provide a debug model |
| presentation for displaying debug elements in the model. This is |
| done using the <a href="../reference/extension-points/org_eclipse_debug_ui_debugModelPresentations.html"><b>org.eclipse.debug.ui.debugModelPresentations</b></a> |
| extension point. This extension point allows an implementation of <a href="../reference/api/org/eclipse/debug/ui/IDebugModelPresentation.html"><b>IDebugModelPresentation</b></a> |
| to be associated with the identifier of a particular debug model. </p> |
| <p>Recall that <a href="debug_model.htm">debug model elements</a> know the id of |
| their originating debug model. This means that given any debug element, |
| the debug platform can obtain the id of the debug model and then query the |
| plug-in registry for any corresponding debug model presentations.</p> |
| <p>The markup for adding a debug model presentation looks like this:</p> |
| <pre><font color="#4444CC"><extension point = "org.eclipse.debug.ui.debugModelPresentations"> |
| <debugModelPresentation |
| class = "org.eclipse.jdt.internal.debug.ui.JDIModelPresentation" |
| id = "org.eclipse.jdt.debug" |
| detailsViewerConfiguration = "org.eclipse.jdt.internal.debug.ui.display.DetailsViewerConfiguration"> |
| </debugModelPresentation> |
| </extension></font></pre> |
| <p>An optional <b>detailsViewerConfiguration</b> can be specified in addition to |
| the debug model presentation. The details viewer must extend the JFace <a href="../reference/api/org/eclipse/jface/text/source/SourceViewerConfiguration.html"><b>SourceViewerConfiguration</b></a> |
| class. The meaning of "details" is interpreted by the debug |
| model. The details are computed by the debug model presentation and passed |
| to the details viewer. For example, the Java debugger uses the details |
| viewer to show code assist in the variables view when expressions are evaluated.</p> |
| <p> </p> |
| <p><a href="../hglegal.htm"><img border="0" src="../ngibmcpy.gif" alt="Copyright IBM Corporation and others 2000, 2003." border="0" width="324" height="14"></a></p> |
| </BODY> |
| </HTML> |
