Le 01/08/2017 à 16:34, Sisinda Dinusha a écrit :
> Did you mean the android.graphics.Matrix class? The reason I didn't
> use the Matrix class is because it uses float instead of double and I
> was not sure float would be sufficient for our task.
>
Indeed it seems to be that class.
We do not need to port AffineTransform to Android since actually, it
does not provide any new functionality. The default implementations in
org.apache.sis.referencing.transform already do all the work needed. The
AffineTransform class in Apache SIS is used mostly for inter-operability
with Java2D - this goal obviously doesn't apply to the Android platform.
Rather than porting parts of Java2D, I think we should use the classes
provided by the Android platform. Indeed their precision are lower, but
if we need double precision we can use the other Apache SIS classes.
I recommend to define AffineTransform is a wrapper around the Android
Affine class for now. As a next step, we may reduce (but not eliminate)
usage of that class in the rest of Apache SIS for avoiding the precision
problem. We would keep that class for cases where we need
inter-operability with the Android graphic package.
Martin
