[Bf-committers] Armatures for beyond Release 2.4

[Thomas H. Hendrick]

So, I've been wondering -- what is really necessary to define a Bone 
inside Blender?  From the user Perspective, as well as the Python API, a 
Bone is defined as { Name, Parent Bone, Head Point, Tail Point, Roll }.

Is there a technical / mathematical reason a Bone could not be defined 
using { Name, Parent Bone, Bone Length, Quaternion from Parent, 
Translation from Parent }?  At least from the standpoint of the Python 
API, this would give the user much more control over rest position of 
the bone.

I was perhaps thinking the Python API for Editbone could be augmented to 
include (quick-example):
setLength( float len )
setRestLocation( Vector trans )
setRestQuaternion( Quaternion q )

Just a thought.  Thanks for all the hard work put in on the 2.4 release!

--Tom.

-- 
------------------------------------------------------------------------
Tom Hendrick<thomas.hendrick at vistagy.com>                Technical Staff
[W] 1-(781)-290-0506 x252   [M] 1-(617) 448-2585    [H] 1-(978)-244-1149
Vistagy, Inc.                                    http://www.vistagy.com/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: thomas.hendrick.vcf
Type: text/x-vcard
Size: 312 bytes
Desc: not available
Url : http://projects.blender.org/pipermail/bf-committers/attachments/20051223/7ff44969/thomas.hendrick.vcf