-
-
Notifications
You must be signed in to change notification settings - Fork 34
Extract out BuildVolume #188
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
|
Visit the preview URL for this PR (updated for commit 3bb4e69): https://gcode-preview--pr188-extract-build-volume-ytlmsfbj.web.app (expires Mon, 11 Nov 2024 03:30:54 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 59bd114ae4847b32c2bba0b68620b9069a3e3531 |
|
I think it's fine for now, separating it out as a util. Eventually we'd want to move to a scheme where we add/remove objects like a build plate to the scene. Also it might be better to separate the axes from the build plate, eventually that is. |
|
Agreed, they could all be separated. In a way, I find it elegant to have the build volume in a single object but with different methods to represent it on the scene. They all use the same x,y and z values. |
# Conflicts: # src/webgl-preview.ts
0d1558f to
3bb4e69
Compare
|
@sophiedeziel this LGTM. Agree to merge? |
|
Yes! |
As explored in #169, I've extracted out the build volume to encapsulate the attributes and geometry building.