Hi, yes its more like a STL slicer. In practice, though, I'm part of a "splinter group" of repstrap folks, who are using conventional 3-axis mills and a RepRap extruder to make a rapid proto machine.
In my case, I'm interested in creating G-code for the toolpaths, because I already have a 3-axis machine available that I'm converting to a "RepStrap" by adding an extruder in place of the spindle. I am happy to share my code-- I can believe anyone would do otherwise, whos using other people's OS code :) A RepStrap guy by the name of Enirque has built a python based slicer for STL, and my hope is to be able to integrate abililty to read step and STL by using pythonocc. His tool is fantastic-- but, it is (a) a bit slow, and (b) cannot handle bad STL, (c) cannot handle STEP, so I'm hoping to fix that... -----Original Message----- From: Jelle Feringa [mailto:[EMAIL PROTECTED] Sent: Friday, October 10, 2008 7:33 AM To: Cowdens Cc: minerva-pythonocc@gna.org Subject: Re: [Minerva-pythonocc] pythonOCC 0.96 and STEP import bug Dave, Let me thank you for sharing your code too, this is really a wonderful contribution to this list. I didnt get the notion of toolpath though, I thought you're builing something closer related to a Stereolithography model slicer, than NC / G-code generation for CNC milling? Btw., the RepRap project rules ;') -jelle _______________________________________________ Minerva-pythonocc mailing list Minerva-pythonocc@gna.org https://mail.gna.org/listinfo/minerva-pythonocc
