[Bf-python] API overhaul - irc meeting?
Campbell Barton
cbarton at metavr.com
Sat Jan 7 05:23:59 CET 2006
Hey All, Some comments before the meeting.
1) Documentation- I personaly like epydocs but having a way to document
things Once is ideal.
Couldent we jenerate the epydocs from docstrings in Blender? line
endings \n\ isnt that big a deal, a good text editor can swap them in as
a search replace anyhow- How bad is source files being bigger, a bit
more memory?
having duplicate docs for everything is a sizable time waister and needs
to be done away with. not only does it waist BPY API time, but it
increases the chance that one of the documentations will get out of date.
Gilbert, Joseph T. wrote:
> Here's my laundry list:
> 1) Eulers vs. Radians debate. Which do we go with for the mathutils
> module and throughout the api.
>
2) Not sure if this would be ideal but just thaught of it,
Could we have a rotation object type, like vector? - so euler/radians
etc are all accessable at once.
object.Rot.xr
object.Rot.yr
object.Rot.zr - Radians
object.Rot.xd
object.Rot.yd
object.Rot.zd - Degreese
object.Rot.xq
object.Rot.yq
object.Rot.zq
object.Rot.wq - Quat?
A wrapper rotation object could be used and accsessed in a few different
ways.
3) A colour wrapper.
at the moment NMesh has a colour object. Mesh also has added 1. There
are theme colours also (that just use tuples?).
Could we have a colour type object?
This would be similar to a vector except their range would be between 0
and 255.
We could then also have access to HSV(A) as well as RGB(A)... could add
other colour access also if we wanted.
>
> 7) Organize module hierarchy if needed. I'm thinking
> Blender.Object.Armature here, etc. NLA is in this category.
>
Not sure of this one, are we talking about a mesh with an armature
applied? or an armature object?
It this is to access an armature objects data then I prefer the current.
ob.data method.
--
Campbell J Barton
133 Hope Street
Geelong West, Victoria 3218 Australia
URL: http://www.metavr.com
e-mail: cbarton at metavr.com
phone: AU (03) 5229 0241
More information about the Bf-python
mailing list