Jeremy Wright

@KeithSloan ## Background/History When CQ 2.0 was in the earlier stages my plan was to update this workbench, and part of that was going to be using `toPythonOCC` and `fromPythonOCC`....

`toFreecad` is from CQ 1.0. There's no equivalent in CQ 2.0. I imagine that code would have to change to something like: ``` newFeature.Shape = Part.fromPythonOCC(cqObject.val().wrapped) ``` But that's just...

@infosisio I spent some time looking into it, but the main problem I ran into was that FreeCAD would not use an Anaconda environment, so it's very hard to experiment...

@grbd Thanks for pointing that out. This main branch needs more than just installing CQ 2.x, and so I have been pointing people to [this fork](https://github.com/jpmlt/freecad-cadquery2-workbench). Tagging @jpmlt to make...

This repo is only compatible with CadQuery 1.x and is not actively maintained anymore. However, there is a fork of this workbench (link in readme) that does support CadQuery 2.x....

The model generation in KiCAD is being updated to use CadQuery 2.x. My understanding is that the plan is to generate the models in GitLab's CI system at first and...

Ah, I see. You're wanting to test the parameter updates in your merge request. It sounds like you have the workbench working now, correct?

Big thanks to @easyw for fixing this. @scrouthtv Please re-open if there is an aspect of this issue that is not addressed by #156 @easyw Is this FreeCAD workbench still...

> is there an option to generate the models as it was in the original libraries? Not at this time, although you can call `.toCompound()` on the assembly to create...

> that is a big issue in generating the 3d library... do you think it could be implemented? @easyw I don't really understand what the problem is. Could you open...