[EMAIL PROTECTED] a écrit :
I'd like to make the changes so I can continue improving and documenting
the TextSymbolizer.
I'd like to make the changes on 2.1.x and trunk.
I'm SE Asia, so I've been unable to attend the meetings (they are at
about 3:00am for me). If anyone has any problems if I do this, let me
know NOW.
The only people who should be concerned are the j2d renderer people (I
saw a reference to "AbsoluteLineDisplacement" in it). That module is
in legacy, so I imagine its not a problem if I break it.
Actually, the module is in "migrate" (which is different from legacy).
But since it is in "migrate" for a while, we should not stop geotools
development because of that.
I suggest to go ahead with the change. If the change appears to break
the j2d renderer, lets create a temporary copy of TextSymbolizer in a
'legacy' package, to be put in the legacy module. The j2d renderer would
use this legacy class until its upgrate.
Martin.
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
