Bug 4341

Description Kai-Uwe Maetzel 2001-10-10 23:10:05 EDT

From EC:

I assume that you talk about the breakpoints view contributed
by the "org.eclipse.debug.ui" plugin. The mechanisms how the vertical
ruler and the breakpoints view look up icons differ. The breakpoints
view has specific knowledge about markers representing breakpoints,
whereas the vertical ruler does not assume a specific marker type.

If you create a marker which should be rendered independently of
its state, the following is recommended: You specify a particular icon
for a particular marker type in your plugin.xml file, e.g.:
<extension point="org.eclipse.ui.markerImageProviders">
    <imageprovider  id="myplugin.myMarkerProvider"
        markertype="myplugin.mymarker"
        icon="myiconlocation/mymarkericon.gif">
    </imageprovider>
</extension>

Your definition is picked up by all editors relying on the provided
default implementation.

If  you create a marker that should be rendered depending on
its state, you have to provide an Annotation which masters the
required rendering. In addition, you have to make sure that for
your marker your custom annotation is created. If you deal with
your own IAnnotationModel, it depends on your implementation
how your annotation is created and added to the  model. If you
use, e.g., the ResourceAnnotationModel, you can create a subclass
of MarkerAnnotation, say MyMarkerAnnotation, and subclass
ResourceAnnotationModel overriding createMarkerAnnotation(IMarker)
to return MyMarkerAnnotation. Thus, when building an editor, you have
to configure it with document providers which return your custom
ResourceAnnotationModel. As example look at JDT. They provide their
own JavaMarkerAnnotation, annotation model, etc.
We are looking into simplifying this for the future.

NOTES: