It seems to me the old interface with
- Rotation3D which has a rotate function
- functions to create Rotation3Ds from various Euler angles
(including ZYZ, if it is not already there)
- possible caching of the rotation matrix in Rotation3D if that does
speed things up
covers everything that is needed without the addition of any of the
new classes and conflicting conventions. Is this right?
No. I tried building a Rotation 3D and using it and it didn't work
with project(). I can provide the details of what was failing, and
maybe somebody can find what I couldn't after fighting for some
weeks. It would be very helpful.