...
I would like to share some comments about the API from a user point-of-view. I hope that the comments will become more detailed, once I actually use it:
| Wiki Markup |
|---|
The use of double\[\] for Vectors and Shapes |
I don't think this is a good idea. While I appreciate that the description is in the javadoc, I strongly feel that it should be part of the API. For vectors, this might still be acceptable, while for shapes I find it absolutely necessary to have descriptive names. The mapping between index and name of the parameter is totally arbitrary and should therefore be avoided completely.
The API for the analysis should be as high-level as possible. I would therefore very much appreciate if classes for the vectors and shapes and track parameters could be added. No, they don't need Draw(), Rotate(), Pt() and Streamer components 
Status codes
The Java language was awarded such a nice enum class. Is there really a performance issue in using ints for status bits or types ?
...