[udig-devel] Re: UDIG Rendering docs

[Matthias Basler <Matthias.Basler@xxxxxxxxxxx>]

Zitat von Jesse Eichar <jeichar@xxxxxxxxxxxxxxx>:
> Hi I've started to update the documentation for Renderer.  I'm not done
> unfortunately but you can check it out.
> http://udig.refractions.net/confluence/display/DEV/Renderers

Thanks a lot!
This already gives a good impression of what classes are involved, what types of
Renderers exist and how this "determine the best renderer" works.

Questions (to be addressed in the documentation, as a suggestion):
- IViewportModel is not yet in the diagram. Is this intended?

- Some work flow diagram would be very helpful to see, who triggers whom when
rerendering is needed, and how each of the objects get their information.

- How dynamically is this network of classes? When exactly is it set up? When a
map is created or when the map canvas is set up or when the map canvas is
changed to view another map? Will the renderers to be used be determined again
each time the map context is changed (i.e. a layer added/deleted)?

- What are the RenderContext classes good for. (LiteRenderer obviously doesn't
need such a construct. It just takes a MapLayer.) I had a look at this class,
and it contains functions to
   - get the ILayer (this makes sense to me)
   - get the GeoResource (cannot this get accessed via the ILayer?)
   - some more convenience methods (getZorder, isVisible)
   - getImage() and other methods that return a BufferedImage.
     I am not sure what's that good for? Does this mean the renderers in uDig
     render onto the Graphics2D derived from these BufferedImages?
     Or for what else are these images used?
   - manage status messages (Which object(s) read them?)

Matthias Basler
c9bama@xxxxxxxxxxx

----------------------------------------------------------------
This mail was sent through http://webmail.uni-jena.de