‹Addon›GearWorkbench

[iplayfast]

🔌 𝗥𝗲𝗽𝗼𝘀𝗶𝘁𝗼𝗿𝘆

https://github.com/iplayfast/GearWorkBench

📑 𝗡𝗼𝘁𝗲𝘀

A FreeCAD workbench for designing parametric gears. Every gear is fully parametric — change any value and the 3D model rebuilds automatically.

This is not a replacement for the fcgears, but instead a parametric version of the same with some additional components.

Because it is fully parametric some operations are slower than fcgears, but it is (I believe) more flexible.

[iplayfast]

release here.
https://github.com/iplayfast/GearWorkBench/releases/tag/1.0

[chennes]

It appears to be missing cycloidGearCreator and gearLog. I also strongly recommend switching to the newer, namespaced addon layout described here: https://freecad.github.io/Addon-Academy/Topics/Structuring/

[iplayfast]

I'll work on that.

[iplayfast]

Done https://github.com/iplayfast/GearWorkBench/releases/tag/1.1

[chennes]

Do you want the addon entry to be pinned to your release tag? It would mean you'd need a PR here to update the tag anytime you update, but prevents users from accidentally running your current work on your main branch (an alternative would be to make a "release" branch that you only update when you are ready to, or something along those lines).

[chennes]

A few more notes about the source itself:

1. It looks like cycloidFun.py might also be missing from the repo. It's imported, but I don't see it.
2. When you switched to the namespaced layout of the code, you didn't switch your imports, so I'd guess this doesn't actually load correctly in FreeCAD -- you should be using things like from freecad.GearWorkBench import gearMath instead of just import gearMath.
3. Your package.xml file date and version don't match your stated version and changed date
4. Your license SPDX isn't valid: it should be either LGPL-2.1-or-later or LGPL-2.1-only (depending on your preference)
5. Your README link in package.xml should be to raw markdown, not the rendered page
6. You have a gearMath.py.backup file committed.

[iplayfast]

I think this fixes all those problems (and a few warnings). Thanks for your help in this.

https://github.com/iplayfast/GearWorkBench/releases/tag/1.3

[iplayfast]

I'm standardizing on using release tags (now) so I think pinning to the release tag is the logical choice.