commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Juntunen (JIRA)" <>
Subject [jira] [Commented] (GEOMETRY-32) BSPTree Updates
Date Thu, 07 Mar 2019 04:55:00 GMT


Matt Juntunen commented on GEOMETRY-32:

{quote}Would it be possible at this point to draft a user guide with usage examples?
I think it's still a little too early for a user guide, unfortunately. Once this issue, GEOMETRY-29,
GEOMETRY-33, and GEOMTRY-34 are closed the API should be stable enough to write a pretty thorough
{quote}Even better would be to accompany it with a "commons-geometry-examples" module.
I like this idea a lot. This would be a great place to put some of the code we currently have
only in tests, like OBJWriter and PLYParser.

> BSPTree Updates
> ---------------
>                 Key: GEOMETRY-32
>                 URL:
>             Project: Apache Commons Geometry
>          Issue Type: Improvement
>          Components: core
>            Reporter: Matt Juntunen
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
> The following updates should be made to the BSPTree class:
> - add an {{isLeaf()}} method to replace all of the {{node.getCut() == null}} expressions
> - add unit tests
> _Edit [2019-02-17]:_
> Additional goals:
> - Refactor the API to split the idea of a general BSPTree and a BSPTree used for defining
in/out regions. This could result in a BSPTree interface and a RegionBSPTree interface. The
goal here is to allow end-users to create their own extensions of these classes and specialize
them for their own applications (for example, to implement spatial sorting or other algorithms).
This will be one of the only planned extension points in the library.
> - Make the API easier to use and extend and reduce the necessity of casting (especially
unchecked casting) as much as possible.
> - Add the idea of convex subhyperplanes to allow for more efficient tree construction.

This message was sent by Atlassian JIRA

View raw message