Hello Stefan,
I think this is probably a good idea but I'd be interested to hear
what others think who have been involved with the library, and it's
various attempts at GUI modules, for much longer than I have.
One of the reasons for my caution is that one could imagine JMapPane's
various bits being formalized into a number of interfaces. The old
swing-widgets module had a DeformableViewer interface and a ZoomPane
abstract class, neither of which I've used in JMapPane (nor did Ian
whose JMapPane code was the starting point for the current class).
There is also the rule that we've set ourselves (sensibly I think) to
keep the swing module simple and modest in scope. I wonder if defining
interfaces might be seen by some as akin to setting standards -
something that it could be argued the swing module isn't there to do.
Michael
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.
http://p.sf.net/sfu/bobj-july_______________________________________________
Geotools-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
