Affine transforms - matrix algebra
martin.desruisseaux at geomatys.fr
Thu Jul 19 14:16:05 PDT 2012
Le 19/07/12 22:39, Pavel Safrata a écrit :
> Or we could simply keep the J2D terminology prefixed with something,
> perhaps "apply".
On my side, I liked the method names that specify in which space the
translation or scale apply, no matter if the methods use
"source"/"target" or "prepend"/"append" or something else. I admit that
there is different opinions of what "append" means. My view is strongly
influenced by ISO-19111 and by the wording of Java2D
AffineTransform.concatenate(...) javadoc, but I understand that other
peoples will view the mathematical notation instead.
It seems to me that the choices depend on the "pedagogic" approach
chosen for telling to the users what the methods do. I see the following
choices (not trying to be exhaustive; I just list what - in my current
understanding - seem the most frequent/debated points of views):
1) The "operation chain" point of view (ISO-19111 and
AffineTransform.concatenate(...) javadoc wording).
2) The mathematical (especially matrix) notation point of view.
I have a preference for 1 given that, in my past experience with an open
source project, I realized that many Java developers seem to be a bit
scared by mathematics. However I think I will be fine with whatever you
More information about the openjfx-dev