-
Notifications
You must be signed in to change notification settings - Fork 11
mesh_t based ruby bindings #50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Also expanding `s.files` entry to be all ruby in lib/**/*.rb
This is mainly to make the ruby helper deallocator trivial.
Undecided on if I want to keep the STLObject exported for write, or not. The C-API sort-of favors C, and making a mesh would probs entangle the existing BSPNode with the ruby GC :(
As this stands, there's not an output that won't require a conversion to STL before write unless this gets re-written to use On the bright side, I don't think the ruby API actually needs to change at all. |
Gonna remap the ruby wrapper to universally use |
this required moving the bsp_mesh_t into a new header so that it wouldn't be circular bsp.h<->mesh.h
mesh_to_bsp now calls mesh->to_bsp
Right now, it basically asserts that you pass "STL" but the intent is to remove any surprise from what arrives on the disk after a call to write rather than just having a convention of knowledge about the underlying type's prototype
lib/csg.rb
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# Assign
This PR will update the ruby bindings for the
csg
gem to be based on the newmesh_t
type from #49This will also bump the gem version to
0.1.0
because of the API shuffling I'm doing.Tasks
mesh_t
intoCSG::Native
mesh_read_file
to return aCSG::Native
CSG::Solid
to bemesh_t
backed instead ofstl_object
to_bsp
to themesh_t
prototype returning a new BSP treemesh_t->to_bsp
bsp_to_mesh
helper to not deal with CPP generated calls from rubybsp_to_mesh
Maybe this also?
stl_object
from being exported to ruby?