FAQ How do I create an image registry for my plug-in?

If you&#146;re writing a plug-in with UI components, it should be a subclass
of AbstractUIPlugin. This superclass already provides you with
an empty image registry accessible by calling getImageRegistry.
When the registry is first accessed, the hook method initializeImageRegistry
will be called. You should override this method to populate your image registry
with the image descriptors you need. You don&#146;t have to use this registry if you
don&#146;t need it, and because it is created lazily on first access, there is no performance
overhead if you never use it. Here is an example of a plug-in that adds a
sample.gif image to its image registry:

Comments:

This FAQ seems misleading given the API comment on AbstractUIPlugin.getImageRegistry():

The image registry contains the images used by this plug-in that are very
frequently used and so need to be globally shared within the plug-in. Since
many OSs have a severe limit on the number of images that can be in memory at
any given time, a plug-in should only keep a small number of images in their
registry.