I'm copying this email on user and developpers list so peoples can be informed
of what is going on
with GO-1 development (from legacy StyledMapPane and j2d-renderer).
The 'legacy' and 'migrate' modules have been removed from SVN (both 2.3 trunk
and 2.2 branch).
However the code still available on a separated 'legacy' branch, until GO-1
development will be
finished.
Олег Ефимов a écrit :
> So, I've finally defeated my organizational problems and Maven (it's a tough
> one) :)
>
> Ext/go is compiling, I'm ready for further instructions!
Nice! I suggest that you also performs the following checkout:
svn checkout http://svn.geotools.org/geotools/branches/legacy/
and mount the 'legacy/src' and 'migrate/src' sub-directories into Netbeans. You
can ignore
'legacy/src' (it is only needed for compiling). The interresting directory is
'migrate/src'.
The general rule is: as soon as a method has been ported from J2D-Renderer to
GO-1, we deprecate the
corresponding method in J2D-renderer with a "@deprecated Replaced by [EMAIL
PROTECTED] ...}" javadoc tag. When
we finished to port all methods from a class, only then we deprecate the old
legacy class. It allow
us to generate a javadoc as a kind of "how to migrate from J2D-renderer to
GO-1". Most of the time,
there is a one-to-one relationship.
The work is monitored there: http://jira.codehaus.org/browse/GEOT-415
Steps to do
-----------------------------------------------
Our first step is to implement the following GeoAPI interface:
http://geoapi.sourceforge.net/snapshot/javadoc/org/opengis/spatialschema/geometry/geometry/PointArray.html
It is implemented in the org.geotools.geometry.array package. PointArray2D is
the abstract base
class tuned for GO-1 renderer needs. Try to become familiar with this class and
its
geotools-specific extensions, since it is at the hearth of GO-1 renderer.
Important additional
methods (compared to the GeoAPI interfaces) are:
- getBounds2D
- iterator
- toFloatArray
- subarray
For PointArray2D and subclasses, performance matter. Some method make
assumption for performance
reasons. We should be generous on usage of "assert" statements in such methods.
We need to port all remaining classes from the legacy
org.geotools.renderer.array package. Ignore
all classes already marked as @deprecated (either they are already ported, or
we choosed to not port
them).
I suggest that you begin with DefaultArray (probably to be renamed
DefaultArray2D, unless someone
has a better name to suggest). Try to retrofit 'getFirstPoint' and
'getLastPoint' implementations
into the 'get' method, if applicable. Note that the 'count()' method has been
renamed as 'length()'.
Maybe some other methods were renamed too, I don't remember - we need to be
carefull about method
names same some of them override methods in super-class. Javadoc need to be
translated from French
to English - I will take care of this part, unless you can read French :).
We need an extensive test suite, as JUnit tests. We should port the JUnit tests
from the
'legacy/migrate/test' directory (only the tests related to DefaultArray for
now). If there is no
tests for DefaultArray, it would be nice if you could write somes (it would
also be a way to dig in
DefaultArray working). If some tests already exist, feel free to add more tests.
Thanks,
Martin.
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
