@dan rathbun said:
@jessejames said:
It is really a disservice to all of us that Python is not included in SketchUp. Some will argue...
@unknownuser said:Well the dev team does not have time to support another language
Thats true, just give us the hooks we need and we will write and maintain the Python API and Python API docs, no need to lift a finger!Good News for Jesse ! It's already been DONE. It's called SuPy, and the current version is 1.6, written by a guy named Greg Ewing in New Zealand. Here's the link:
http://www.cosc.canterbury.ac.nz/greg.ewing/SuPy/Since YOU are our resident expert in Python... we appoint you to test it out and give us a report:
(1) Is it faster? (ie: SU Ruby scripts vs SU Python scripts)
(2) And can SU Python scripts be compiled?Anyone think of anymore evaluation questions?
Hello Dan,
Yes i already knew about SuPy because my begging, nagging, and borderline stalking to everyone on planet earth including GvR himself help to bring attention to the Python community of Python's role in SketchUp. I am forever in the service of Greg Ewing for his wonderful work on this module.
However, this is a Ruby module and not a REAL Python API. Basically Python calls Ruby code, then Ruby calls SketchUp, very inefficient! Therefore it suffers from extreme slow speeds and has to work around the differences between Python and Ruby languages. The intention of this module was to shed light on Python's abilities in the hope Google would then give us the hooks we need for a REAL Python API. I would love for all scripters to have a choice between Python and Ruby, and constantly improve both API's. This would foster even better plugins in the future, sadly though so many of the Ruby guys are so rabidly against it none of the noobs are brave enough to try it.