[Bf-python] Blender scripting API

Antti Siponen antti.siponen at iki.fi
Mon Apr 13 16:24:21 CEST 2009


Hi everybody!

I'm totally new here, so be gentle if you need to rip me to pieces...

I just had in mind an idea/voice that says:

"Why do we have the C/Python/C marshalling hardcoded into the API
functions?" (Or do we? At least it seemd so to me)

I was just thinking that it might make something more flexible if we
had the marshalling
separated from the actual API functions. That way it would later be
possible to code
scripts for Blender in some other language than Python too (not that
there would ever
be any real need for that ofcourse, but people like to do stupid
things and you can't help
it you know...).

For example if I wanted to try out some Fran modelling scripts with blender
I would have to compile Blender to kick a haskell intepreter instead
of the python one and do
some extra marshalling too. Many languages have ready thought-out
marshalling procedures
for interfacing with C, but not for example with Python.

So what I propose is that we could have the scripting API exposed as
C-calls and have a separate
marshalling parts for interfacing it with the scripting language (Even
with Python, even if we have a
Python interpreter inside)

If this isn't totally laughed at here, I might also give it a serious
look and come up with some less
"waving hands" versions of the idea.


Antti Siponen



More information about the Bf-python mailing list