Planning for the gt-swing module; Micheal has been working on consolidating what we have with a view to promoting swing to supported land...

Reference:

Quality Assurance

1. Going through all of the current classes and doing general tidying refactoring, adding unit tests, culling unused or duplicate code, and updating javadocs. This is what I'm working on at the moment.

2. Tackle the current open jiras, particularly:

2 and 3 might not be done in that order - more likely my usual random
mix unless external constraints demand otherwise.

Document

Docs minimal:

Docs recommended:

The existing docs have this covered:

RnD Target

Recent Developments:

Interesting RnD topics:

JLayeredMapPane

JLayeredMapPane - class about 1/2 written. This is the idea of having multiple MapContent in a single JPannel and allow "background" rendering into backing images. Get back to JLayeredMapPane and bring it up to being able to do an animation example.

This will also involve some discussion about handling DirectLayers outside the renderer. With Andrea's assistance I added support for DirectLayers to StreamingRenderer a while ago but you won't want to go through the renderer for non-static graphics, especially if a high frame-rate is required.

JList Emulation

The ability to treat a map display as a normal JList

Printing

It would be good to package this up (this docs do cover it)

Shared Interfaces with SWT

Feedback from 2010

Feedback collected on gt-swing:

http://docs.geotools.org/latest/userguide/unsupported/swing/jmappane.html

Trvial feedback (raised as issues in the issue tracker) the following issues were identified that made coding more verbose than needed:

This was actually amsuing as we would call JComponent.repaint() and get the same map generated as the component draws into a back buffer).

Options (these are alternaitves):