Justin Deoliveira wrote:
Jesse,
I am trying to create the decorator api. I figure the best way is to
create an abstract class (Decorator) that implements Renderer and
just have extenders fill in the bits. However I am not sure if this
is line with the current workflow. Does each renderer get its own
raster? If so my design may not be the best solution since
dectorators wouldn't need their own raster.
Hi Justin,
I kind of thought RenderContext was simply a facade on the various
services available to someone writing a renderer. But it does seem to
have acquired additional functionality somewhere on route (namely
managing a bufferedImage for you). I have no idea how that will work
with respect to printing.
I am pretty sure we are flip flopping on the idea of who is
responsible for "owning" the raster for each layer. ie Managing the
buffered image for a Layer is a good idea. We just need a way for a
mathematically generated layer like north arrow to indicate "Don't
buffer me, I am super fast" so that raster( Graphics2d ) gets called.
Q: Should we just throw a flag into the Renderer interface for now?
