Module Structure + Licensing + Manifest

[PhoneDroid]

• Updated license file
• Added SPDX annotations
• Removed Python 2 annotation
• Restructured to module
• Added pyproject setup
• Added PySide wrapper
• Updated manifest
• Defined API

[PhoneDroid]

Not ready, the global variable isn't accessible.

[PhoneDroid]

@jmwright Had to define an API - which should
be done anyways - for it to access the content.

[jmwright]

@PhoneDroid If I try to install this addon from your branch in FreeCAD 1.0.2 (Flatpak) on Debian 13, I get the following error, which I remember from when I first updated this workbench. I think this may have been the cause of my weird installation method.

[PhoneDroid]

@jmwright Right, that likely comes from them not being on the allow list, I'll check if they can be added.

[jmwright]

@PhoneDroid I know it's a strange capitalization convention, but we have actually always used CadQuery rather than CADQuery as you have it in the license headers.

[PhoneDroid]

@jmwright I see, I'll update it later then.

[jmwright]

@PhoneDroid Would you like me to do the text replace and push it to your branch (assuming you allowed that when you opened the PR)?

[PhoneDroid]

@jmwright No thanks, I'll do that myself :3

Just gotta remember

[PhoneDroid]

@jmwright
I think I had created the PR with the wrong branch,
cherry picked stuff, I believe it should be fine now.

[jmwright]

@PhoneDroid Thanks!

I have looked this over and am ready to merge when you feel it is finished.

[PhoneDroid]

@jmwright Sure, go ahead.
Afterwards I'd recommend bumping the version / creating a new release.

Hopefully later on we can get your dependencies auto-installed as well~

[jmwright]

Thanks for the contribution @PhoneDroid !

[jmwright]

New release here: https://github.com/CadQuery/cadquery-freecad-workbench/releases/tag/v2.2.0

CadQuery is up to 2.6.2 now and uses cadquery-ocp 7.8.1.1, and CadQuery 2.7 is getting close-ish to release. At some point we will want to bump those versions up, but some testing will be required to make sure it does not break anything. I think I've had issues with the cadquery-ocp wheel messing with the FreeCAD environment before, but that might not be relevant anymore with the way FreeCAD 1.x handles environments.