[Bf-committers] Meeting notes, 19 sept 2010

Ton Roosendaal ton at blender.org
Tue Sep 21 17:48:08 CEST 2010


This I meant:

> - don't rna wrap C code which is work in progress?
> - don't port unfinished C code to python?

But modifiying existing code is fine, provided no functionality gets  
lost, and preferably provided things then fucntion better for end- 
users even!

A good example is the render api, this is not well designed yet, and  
hasn't been used optimally inside Blender either. It's for me still a  
Same goes for most of the Window Manager WM calls.


Ton Roosendaal  Blender Foundation   ton at blender.org    www.blender.org
Blender Institute   Entrepotdok 57A  1018AD Amsterdam   The Netherlands

On 20 Sep, 2010, at 4:36, Campbell Barton wrote:

>> - Campbell reports we need to work still on how Python operators work
>> within or without context ('data' context). The meeting discussed  
>> some
>> cases, but no clear answers popped up yet. Ton mentioned to at least
>> not try to Pytonify the C code when that's not fully finished or  
>> frozen.
> Can you clarify what you mean by "Pytonify the C code"
> - don't rna wrap C code which is work in progress?
> - don't modify behavior of C code to work better with python?
> - don't port unfinished C code to python?
> Is this something which has happened before you want to prevent? or is
> this more a general concern.
> Realize this sounds pedantic but if I'm to be sure not to do it I want
> to be clear on what you say :)
> - Campbell
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers

More information about the Bf-committers mailing list