From 8d359bf2452fca1144b40e60d1ca090137773642 Mon Sep 17 00:00:00 2001 From: Darin Swanson Date: Thu, 13 Sep 2001 15:38:04 +0000 Subject: 1GITH5J: ITPDUI:ALL - Fix HTML doc problems in 2.0 --- .../core/org/eclipse/debug/core/model/package.html | 8 +++--- .../core/org/eclipse/debug/core/package.html | 29 +++++++++++----------- org.eclipse.debug.ui/doc/hglegal.htm | 1 - org.eclipse.debug.ui/doc/org_eclipse_debug_ui.html | 4 +-- ...g_eclipse_debug_ui_debugModelPresentations.html | 26 +++++++++---------- .../ui/org/eclipse/debug/ui/package.html | 15 ++++++----- 6 files changed, 40 insertions(+), 43 deletions(-) diff --git a/org.eclipse.debug.core/core/org/eclipse/debug/core/model/package.html b/org.eclipse.debug.core/core/org/eclipse/debug/core/model/package.html index 59c1b7ba2..4b091a06d 100644 --- a/org.eclipse.debug.core/core/org/eclipse/debug/core/model/package.html +++ b/org.eclipse.debug.core/core/org/eclipse/debug/core/model/package.html @@ -1,8 +1,8 @@ +
-A language independent "debug model" is represented by the set of interfaces -defined in org.eclipse.debug.core.model. A client implements a debug +defined in org.eclipse.debug.core.model. A client implements a debug model by providing an implementation of these interfaces in a plug-in. (There is no explicit extension point that represents a debug model). Each debug architecture will have its own way of initiating a debug session. Generally, each debug model will provide one or @@ -42,8 +42,8 @@ responsibility.
Debug model elements and breakpoints are displayed in the workbench. To support -configurable and extensible presentation, the debug UI plug-in defines the debugModelPresentations extension point. Extensions of this kind +configurable and extensible presentation, the debug UI plug-in defines the +debugModelPresentations extension point. Extensions of this kind register for a specific debug model. It is intended that an implementation of a debug model will also provide an implementation of a debug model presentation. The presentation provides: diff --git a/org.eclipse.debug.core/core/org/eclipse/debug/core/package.html b/org.eclipse.debug.core/core/org/eclipse/debug/core/package.html index 81476871a..41340ca70 100644 --- a/org.eclipse.debug.core/core/org/eclipse/debug/core/package.html +++ b/org.eclipse.debug.core/core/org/eclipse/debug/core/package.html @@ -1,8 +1,8 @@ +
-The "debug model" is represented by the set of interfaces defined in org.eclipse.debug.core.model. A client implements a debug model by +
The "debug model" is represented by the set of interfaces defined in +org.eclipse.debug.core.model. A client implements a debug model by providing an implementation of these interfaces in a plug-in. (There is no explicit extension point that represents a debug model). Each debug architecture will have its own way of initiating a debug session. Generally, each debug model will provide one or more @@ -56,7 +56,7 @@ responsibility.
Debug model elements and breakpoints are displayed in the workbench. To support -configurable and extensible presentation, the debugModelPresentations +configurable and extensible presentation, the debugModelPresentations extension point is used. Extensions may be registered for a specific debug model. It is intended that an implementation of a debug model will also provide an implementation of a debug model presentation. The presentation provides: @@ -84,25 +84,24 @@ common line breakpoint marker, as well as the attributes for these markers. Brea creation is a client responsibility - that is, choosing which resource to associate a breakpoint with.
-The breakpoint definitions in plug-in org.eclipse.debug.core +
The breakpoint definitions in plug-in org.eclipse.debug.core are as follows:
- -<extension id="breakpoint"
+ <extension id="breakpoint"
point="org.eclipse.core.resources.markers">
<super type="org.eclipse.core.resources.marker"/>
<persisted value="true"/>
<extension id="lineBreakpoint"
+ <extension id="lineBreakpoint"
point="org.eclipse.core.resources.markers">
<super type="org.eclipse.debug.core.breakpoint"/>
<super type="org.eclipse.core.resources.textmarker"/>
<persisted value="true"/>
-</extension>
Breakpoints are persisted via the standard marker mechanism. Breakpoints defined with -the persisted attribute as false +the persisted attribute as false will not be persisted. Breakpoints are restored at workspace startup time by the breakpoint manager - that is, all persisted markers which are a subtype of the root breakpoint marker are added to the breakpoint manager. To allow for selective persistence @@ -150,7 +149,7 @@ with the breakpoint manager).
Removing a breakpoint from the breakpoint manager signals the end of the breakpoint -lifecycle. A breakpoint may be removed with the method org.eclipse.debug.core.IBreakpointManager.removeBreakpoint(IMarker), +lifecycle. A breakpoint may be removed with the method org.eclipse.debug.core.IBreakpointManager.removeBreakpoint(IMarker), or by deleting the underlying marker (in the later case, the breakpoint manager notices a breakpoint has been deleted, and automatically removes it).
@@ -165,12 +164,12 @@ model dependent.Debug targets are notified of breakpoints via the IBreakpointListener +
Debug targets are notified of breakpoints via the IBreakpointListener mechanism. The breakpoint manager only notifies debug targets of breakpoints added/changed/removed, after a target has been created. Since breakpoints are often in existence before a debug target is launched, a debug target is responsible for querying -the breakpoint manager for breakpoints in existence when it is created - see org.eclipse.debug.core.IBreakpointManager.getBreakpoints(String), +the breakpoint manager for breakpoints in existence when it is created - see +org.eclipse.debug.core.IBreakpointManager.getBreakpoints(String), which provides a list of active breakpoints for a specific debug model.
diff --git a/org.eclipse.debug.ui/doc/hglegal.htm b/org.eclipse.debug.ui/doc/hglegal.htm index b071dbdf4..d9e453f84 100644 --- a/org.eclipse.debug.ui/doc/hglegal.htm +++ b/org.eclipse.debug.ui/doc/hglegal.htm @@ -2,7 +2,6 @@ -This debug tools UI plug-in, org.eclipse.debug.ui, implements a +
This debug tools UI plug-in, org.eclipse.debug.ui, implements a
debug user-interface, allowing the user to view and manipulate debug targets, processes,
threads, stack frames, and variables. It provides standard debug functionality such as
stepping, setting breakpoints, etc.
diff --git a/org.eclipse.debug.ui/doc/org_eclipse_debug_ui_debugModelPresentations.html b/org.eclipse.debug.ui/doc/org_eclipse_debug_ui_debugModelPresentations.html
index c0fca96fc..5b1317eea 100644
--- a/org.eclipse.debug.ui/doc/org_eclipse_debug_ui_debugModelPresentations.html
+++ b/org.eclipse.debug.ui/doc/org_eclipse_debug_ui_debugModelPresentations.html
@@ -1,8 +1,8 @@
+
Configuration Markup:
<!ATTLIST sectionParser
- class CDATA #REQUIRED
- id CDATA #REQUIRED
+ class CDATA #REQUIRED
+
+ id CDATA #REQUIRED
The following is an example of a view filter extension point:
-<extension ++ </extension><extension point = "org.eclipse.debug.ui.debugModelPresentations"> <debugModelPresentation class = "com.example.JavaModelPresentation"> id = "com.example.JavaDebugModel" </debugLabelProvider - </extension>
In the example above, the class com.example.JavaModelPresentation will be used -to render and present debug elements originating from the debug model identified by com.example.JavaDebugModel.
+to render and present debug elements originating from the debug model identified by +com.example.JavaDebugModel.API Information: Value of the action attribute class must be a -fully qualified class name of a Java class that implements org.eclipse.debug.ui.IDebugModelPresentation.
+fully qualified class name of a Java class that implements +org.eclipse.debug.ui.IDebugModelPresentation. diff --git a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/package.html b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/package.html index 8f5023fa7..980386c8f 100644 --- a/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/package.html +++ b/org.eclipse.debug.ui/ui/org/eclipse/debug/ui/package.html @@ -1,8 +1,8 @@ + -Eclipse Debug Tools UI (debug UI plug-in) provides a set of classes and interfaces to support a debugger user interface. A generic debug perspective is provided with a common set of views. Clients are allowed to contribute actions to the debug views via the -standard workbench viewAction extension point, and can -contribute to popup menus in the debug views via the standard popupMenu +standard workbench viewAction extension point, and can +contribute to popup menus in the debug views via the standard popupMenu extension point.
The debug UI plug-in defines an extension (org.eclipse.debug.ui.debugModelPresentations) +
The debug UI plug-in defines an extension (org.eclipse.debug.ui.debugModelPresentations) point to allow implementations of debug models to provide custom rendering and presentation of its debug elements. Extensions are be registered for a specific debug model. It is intended that an implementation of a debug model will also provide an @@ -71,10 +71,9 @@ implementation of a debug model presentation. The presentation provides:
The debug UI plug-in defines an interface that launch wizards must implement - org.eclipse.debug.ui.ILaunchWizard. Launch wizards are defined -in launcher extensions (defined by org.eclipse.debug.core), and are instantiated by the debug UI +
The debug UI plug-in defines an interface that launch wizards must implement - +org.eclipse.debug.ui.ILaunchWizard. Launch wizards are defined +in launcher extensions (defined by org.eclipse.debug.core), and are instantiated by the debug UI plug-in.