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
Here is a start of a discussion regarding the previous attempt to generate tree of operations from modeling,
I my mind this would enable different kinds of optimisations and other use-cases not possible with direct execution of modeling functions.
diff plus redo of only parts that changed (after param change)
executing on demand certain operations
referencing vtree by clicking on the model
referencing source from model or vtree
evaluating vtree in different preview/export/fidelity modes (fast preview for dev, full execution for export)
simpler usage of different boolean libraries for different purpose, or using some new faster one
This could allow designing modeling part of jscad to focus on expressing the ideas and separating the parts that actually produce meshes or do boolean out of it.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Here is a start of a discussion regarding the previous attempt to generate tree of operations from modeling,
I my mind this would enable different kinds of optimisations and other use-cases not possible with direct execution of modeling functions.
This could allow designing modeling part of jscad to focus on expressing the ideas and separating the parts that actually produce meshes or do boolean out of it.
Beta Was this translation helpful? Give feedback.
All reactions