[
https://issues.apache.org/jira/browse/GEOMETRY-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17248621#comment-17248621
]
Gilles Sadowski commented on GEOMETRY-108:
------------------------------------------
bq. long-standing naming convention
Yes, I know; I didn't express myself clearly: It just looks strange, when
similar classes are to be added, that the same part of the name refers to
different things (the dimension in one case, the geometry in the other).
But maybe we already had that discussion about "namespaces" (so that the same
class name could be used whatever the geometry)... ;-)
> BoundaryList Implementations
> ----------------------------
>
> Key: GEOMETRY-108
> URL: https://issues.apache.org/jira/browse/GEOMETRY-108
> Project: Apache Commons Geometry
> Issue Type: New Feature
> Reporter: Matt Juntunen
> Priority: Major
>
> We need a {{BoundarySource}} implementation that simply contains an arbitrary
> list of hyperplane convex subsets. I propose creating the following classes:
> - {{o.a.c.geometry.core.partitioning.BoundaryList}}
> - {{o.a.c.geometry.euclidean.oned.BoundaryList1D}}
> - {{o.a.c.geometry.euclidean.twod.BoundaryList2D}}
> - {{o.a.c.geometry.euclidean.threed.BoundaryList3D}}
> - {{o.a.c.geometry.spherical.oned.BoundaryList1S}}
> - {{o.a.c.geometry.spherical.twod.BoundaryList2S}}
> This is required for GEOMETRY-101 since the output from reading some model
> file formats is a simple list of facets.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
