I made an in source build, and it worked perfectly.
However i could not figure out how to use it. I guess it is a bit early in development.
It would be very nice if someone could do a demo of the code at this stage.
There are several important scripts that get copied to Mod/Path/PathScripts during installation. If these aren't found, you'll still be able to launch the Path WB but many things may not work.
Here's a quick run through with some screenshots. It'll give you a sense of where the workbench is going but be warned that it is still very early and not ready to merge to Master. So there are many bugs and some things may change a lot before merging.
Below, I've created a sketch and padded it. Then selected the top face and created a profile path. The path is generated automatically stepping down 1mm at a time. There are lots of properties on the data tab that can be adjusted. The path itself will be updated in real time. It's also still parametric, so if the sketch is changed, the path will adapt. The profile is the first of the 'Path Python Features' In the future, there will be more for pocketing, drilling, surfacing, etc. As the name suggests, these are written in Python so it will be a great place for the community to contribute.
I've added a sketch to the face and made a pocket. Then created a "path pocket" from it. This is all using OCC offsetting and is looking pretty good. The path pocket is incomplete. You can't set step-down, step-over or many other properties you'd expect.
You can create a Path Project and add individual Paths to it. The project will control the sequence of operations and also hold properties that are global.
Double clicking the path project opens up the Task view. Here you can resequence the path operations and also edit the tool table. The tool table editor will allow importing and existing tool table and will read HeeksCNC tool tables directly.
Select either an individual path or a project and export it. The list of exporters now includes Gcode. Selecting it will bring up a second dialog where you can choose the post-processor to use. Post processors are in python and customization will be done there. The post selector will look in the directory referenced above as well as the user's Macro directory. as long as the name is <name>_post.py, it will be found.
There are a lot more features already and more planned. I can do more posts and screen shots if there's interest.