commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gilles (JIRA)" <>
Subject [jira] [Commented] (GEOMETRY-14) AffineTransform?D Classes
Date Sat, 06 Oct 2018 23:17:00 GMT


Gilles commented on GEOMETRY-14:

{quote}A.transform(B).transform(C) would logically perform A, then B, then C.
With [UnaryOperator|],
this would be expressed either as
or as
Using it will bring all the advantages of a standard API.
{quote}{{t.apply(p1.vectorTo(p2)).normalize()}} is more difficult to read.
Maybe, but caution still applies for anything that goes into the public API. The fluent API
is nice but we should explore the alternatives.
{quote}I do not have the private fields set as final so that I can do things like copying
This is a can of worms, as it will prevent any simple implementation of multi-threaded processing.

> AffineTransform?D Classes
> -------------------------
>                 Key: GEOMETRY-14
>                 URL:
>             Project: Apache Commons Geometry
>          Issue Type: New Feature
>            Reporter: Matt Juntunen
>            Priority: Major
>              Labels: pull-request-available
> We should create AffineTransform?D classes that implement matrix-based affine transforms.
They should have simple methods for creating translations, rotations, and scaling and calculating
the inverse.
> Pull Request #1:

This message was sent by Atlassian JIRA

View raw message