From eb2e1b685258458ea9e50961ff437993c264fddd Mon Sep 17 00:00:00 2001 From: James Pace Date: Wed, 7 Feb 2024 02:11:50 +0000 Subject: [PATCH] More editing. --- posts/cadquery-direct-api.qmd | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/posts/cadquery-direct-api.qmd b/posts/cadquery-direct-api.qmd index 5e7f75d..ccf6a58 100644 --- a/posts/cadquery-direct-api.qmd +++ b/posts/cadquery-direct-api.qmd @@ -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 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 -reuse. +It is also really hard to organize things in a way that allows for code reuse. 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. The Direct API is much closer to "normal" OOP programming, where objects are made by calling