public
/
til.jpace121
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

More editing.

This commit is contained in:
James Pace 2024-02-07 02:11:50 +00:00
parent 6531f3d2f0
commit eb2e1b6852
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
posts/cadquery-direct-api.qmd
View File

@ -52,10 +52,9 @@ but definitely the suggested workflow.
Regardless, the actions in each of the lines is extremely dependent on state hidden in the workplane Regardless, the actions in each of the lines is extremely dependent on state hidden in the workplane
that is basically impossible to tease out. that is basically impossible to tease out.
What I've found more challenging is it is really hard to organize things in a way that allows for code It is also really hard to organize things in a way that allows for code reuse.
reuse.
Specifically, I've worked on two projects where I've wanted to reuse sketches in multiple places, Specifically, I've worked on two projects where I've wanted to reuse sketches in multiple places,
and in neither case could I really find a nice way to do that while using the Fluid API. and in neither case could I really find a nice way to do that while using the Fluent API.
I've found the Direct API to make this much easier. I've found the Direct API to make this much easier.
The Direct API is much closer to "normal" OOP programming, where objects are made by calling The Direct API is much closer to "normal" OOP programming, where objects are made by calling