git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Using Git for OpenSCAD and 3D Printing

From
MKMr. Sandor Kunyik <sandor@kane-il.us>
Date
Jan 5, 2021, 09:57 UTC
Message-ID
<cee9debaf32b69d793d0b8a3e8d4b2c6@kane-il.us>
Greetings,

If you were to design a new workflow, what key observations would you make in regards to OpenSCAD scripts?

As a quick illustration: I have a model with cavities to hold hex bolts and nuts. I fine-tuned the model to print on PrinterA, using FilamentA, SettingsA. Once in "production" I need to "freeze" all relevant scripts, especially when using multi-file structure. If the modules receive parameters I need to "remember" those parameters (such as the radius for the hex, and the dept of the cavity), and if they use hard-coded values I must remember not to change them. Otherwise I cannot repeatedly print the same model.

Now imagine this for the entire standard set of hex bolts - each of these were fine-tuned, test-printed and verified. The rationale behind this to guarantee that the models trying to conform to a standard (such as ASME B18.3) stay put, while models receiving non-standardized sizes such as Nylon 6/6/ (which have bigger hex heads) stay separated, and tweaked to work with each supplier.

My question is, should I just "hardcode" everything, set up forks or branches for all past scenarios? So far I only have a few dozen models and I'm already having a hard time finding models I printed and used in the past, to print again. How do I structure all this?

I am a mechanical engineer not a coder, new to all these. Maybe git or revision control is not the correct tool for this job?

-- 
Thanks for your time reading,
Sandor
Next: Philip Oakley
Message 1 of 4 in “Using Git for OpenSCAD and 3D Printing”
  1. Mr. Sandor KunyikJan 5, 2021
  2. Philip OakleyJan 11, 2021
  3. Mr. Sandor KunyikJan 18, 2021
  4. Philip OakleyJan 18, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.