Sorry to be slow of brain, but I'm getting a bit lost now... Perhaps
> if I just explain what JMapPane currently does (plus the branch code
> updates) someone can help me to understand how this does, or doesn't,
> fit with the ideas being discussed.
The ideas being discussed seem to be going okay; I am probably confusing the
issue as I am asking how *you* are handling rotate in JMapPane. 
> There are two bounding rectangles: map and display. When zoomed in
> these can be the same, but at full extent the display bounds can be
> larger than the map bounds due to slack space.
Got it. 
> The map pane maintains its worldToScreen and screenToWorld
> AffineTransforms. There is currently no setter method. The transforms
> are used for mouse coords etc as well as being passed to the
> renderer's paint method (although the renderer does not honour the
> transform for grid coverages which is a long-standing issue that would
> be great to sort out).
> 
> In the branch code, where rotation has been implemented, it is handled
> as an extra, concatenated transform (so that it is easy to undo).
Okay; that is what I was trying to ask.

We can compare notes with what GeoServer does for angle; if the two approaches 
are similar
then we could fold the "angle" functionality into MapViewport and simplify both 
codebases.

Q: How does angle effect your worldToScreen and screenToWorld transforms? Do 
you need to
make the extra concatenated transform available for tools to work etc?
> An item on my swing todo list is the ability to link map panes. An
> example use case is a small navigation pane showing a map at full
> extent linked to a larger, zoomed in pane. In this case a single
> viewport would not work. I guess one pane could clone the other's
> MapContent but then there are sync issues to handle if layers are
> added, removed etc. I don't bring this up as an objection to anything
> currently being discussed, but just as a use case I'd like to be able
> to support.
MapContent is designed to be shared between map panes; that is why MapViewport
is a separate class. In the original MapContext they were part of one class and 
thus
always the same.

It is my hope if you wanted "an overview" you could make a MapViewport
that wrapped the original (adjusting the by a scale factor). Or you could use 
listeners
and update the second MapViewport for a slightly more complicated solution.

So the general theme is that work is proceeding apace (Andrea reviewed your 
patch, I added StyledLayer, and
we can adjust MapViewport and MapContent to try and make coding easier and 
reduce duplication).

Jody 
------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to