You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now this package can only work with the Mesh type as defined in GeometryBasics. Which, given how poorly this type is documented, makes it quite unuseable.
Instead of forcing the user to use these classes, the Julian way is to work with interfaces, not with types. As an example, one could look at this wonderful little package called AbstractTrees.jl: this manages to offer a number of useful algorithms for general tree types without forcing the user to use any explicit type (and not even forcing them to derive from a given abstract type).
This would be even more adapted to this package given that the interface used is really simple:
extract vertices and triangles from a mesh,
compute the normal for each face of the mesh (this can have a default method),
build a mesh from vertices and triangles.
The text was updated successfully, but these errors were encountered:
Right now this package can only work with the
Mesh
type as defined inGeometryBasics
. Which, given how poorly this type is documented, makes it quite unuseable.Instead of forcing the user to use these classes, the Julian way is to work with interfaces, not with types. As an example, one could look at this wonderful little package called
AbstractTrees.jl
: this manages to offer a number of useful algorithms for general tree types without forcing the user to use any explicit type (and not even forcing them to derive from a given abstract type).This would be even more adapted to this package given that the interface used is really simple:
The text was updated successfully, but these errors were encountered: