It's good that all the code is there and open source. Having different
tools for different tasks is great. It's the Unix way.
Dan
On 2/12/10 3:20 PM, Jelle Feringa wrote:
You're right., I don't know wether or not the gcode generation has to
be a feature of pythonOCC.
There is no place for g-code generation in "core" pythonOCC.
But as a project I do think it is an _awesome_ idea.
Look, the debate on whether to include these things into pythonOCC is
a non-issue.
PythonOCC is well defined in scope, and projects such as these are
extremely welcome, but pythonOCC is just a dependency to them, not the
other way around.
I'm really impressed by projects like Sebastien's occray:
http://code.google.com/p/occray/
* its does as advertised
* its on SVN
* bring added value to pythonOCC
* in an elegant API
* fun to see a quick render emerge using 8 cores ;')
I hope to see more projects like that!
By the way, what's your thought on StepNC?
Seems the future to milling ( perhaps not so practical yet? )
In brief, we're completely open to your efforts/contributions and
ready to help you as far as we can.
Absolutely ;')
_______________________________________________
Pythonocc-users mailing list
Pythonocc-users@gna.org
https://mail.gna.org/listinfo/pythonocc-users
_______________________________________________
Pythonocc-users mailing list
Pythonocc-users@gna.org
https://mail.gna.org/listinfo/pythonocc-users
