[Bf-committers] Blender 2.5 api proposal.

[Chris Want]

My feeling is that if you are going to the trouble of
starting from scratch, you should focus on writing a
decent C library/API, then use Python to shadow the calls
in that API (with some python bookkeeping added). That way
people aren't bound to Python, and this would open
the door to wrapping other languages too. This would
also have great potential for integrating the plugin API and
the scripting API, and for people being able to use Blender
functionality outside of Blender (using Blender as a GUI-less
general purpose graphics library).

Maybe these issues are addressed in the RNA system already
(sadly, I must admit that I am finding it hard to find the time
to follow everything going on in Blender development these days),
but this was my main concern reading your proposal.

Chris

Campbell Barton wrote:
> Here's is my proposal for the Blender 2.5 api.
> http://wiki.blender.org/index.php/BlenderDev/Blender2.5/PythonAPI_Ideasman
> 
> I'm interested to know what people think of possibly moving to a new
> api (especially active Blender/Python scripters).
> 
> This page was started more to get an idea of what people wanted, its
> still useful for discussion.
> http://wiki.blender.org/index.php/BlenderDev/Blender2.5/PythonAPI
> 
> Last meeting we discussed weather to use python 3.0, and it seems a hot topic :)
> PyRNA runs with Python 2.3 - 3.0rc3, in anticipation for a possible
> switch, can we keep these issues separate since its has almost no
> baring on a new API.
> 
> Even though this is a blender-2.5 topic, most of the people this
> affects are not on that list.
>