There many different rendering primitives (for images, text, graphics)
as well as rendering surfaces configurations for both offscreen surfaces
and device (framebuffer) surfaces, and printer graphics devices.
When combined with platform differences and application differences
this leads to a huge combination of potential rendering paths.
This makes it difficult to debug problems and identify performance
bottlenecks.
Possibilities in this feature include
  - expanding the existing facilities for tracing the lowest-level
    loop invocations, and making them more Java Logging API friendly
  - providing a journalling facility so that Graphics calls can
    be logged in a way that allow them to be replayed from a metafile.
    This could allow debugging and tuning independently of the context
    of customer apps which may have require too much configuration.


======================================================================