[Bf-committers] Python!

[Ton Roosendaal]

Hi,

> The more I think about this, however, the more it feels like what we're
> talking about here is duplicating the current class structure into a
> second blender memory tree, one that only acts as a middle man and
> doesn't effect the data of either python or the internal blender
> workings on its own.  Is this a correct notion?  If so, is this really
> necessary?  Or are we just wrapping current class abstraction methods
> (getvar, setvar) with the "mailbox" functions?
>
> Heh, maybe I'm overthinking this.  It's 946a and I haven't had my tea.
>

Yes, we have to be careful not to go into 'style over substance' again.  
The sad fact of Python in Blender was not a lack of engineering skills,  
but just lack of a motivated group of artists/coders who are interested  
in making something that works for the users.

I don't care how you do it, with mailboxes or with a bomb-proof  
interface or with a wee timerous beasty... (Nice definition of Blender,  
though! :-)

-Ton-

"Netjes is voor watjes!"
------------------------------------------------------------------------ 
--
Ton Roosendaal  Blender Foundation ton@blender.org