[Bf-python] new python development path

Joe Eagar joeedh at gmail.com
Sat Feb 11 01:00:21 CET 2006


Toni Alatalo wrote:
> On Thursday 09 February 2006 23:41, Gilbert, Joseph T. wrote:
>   
>> datablocks and not the other, I think the api become only more
>> confusing.
>>     
>
> this is certainly something to be wary about, but i think you missed something 
> here:
>
>   
>> Actions are basically floating datablocks like everything else. They are
>> created as part of an armature object and linked/unlinked to objects as
>> needed. If we have one type of access for Armature data and other for
>> Action data people will only get confused.
>>     
>
> i think ObData objects/datablocks, like MeshData and ArmatureData, are 
> different from independent datablocks such as Action and Text and Image etc.
>
> in Blender GUI, there is no way to create a new ArmatureData or MeshData. 
> apart from adding a new ArmatureObject or MeshObject to the scene, but to 
> create a new Action, you can just go to the action editor and click 'add 
> new'.
>
> ~Toni
Do, is the plan going to be that there will be no Object, (N)Mesh, 
Armature, Camera, etc. Blender.XXX modules?  Is everything going to go 
through the Scene module?  That makes sense to me.

joeedh




More information about the Bf-python mailing list