[Bf-python] Proposed BPyAPI Additions.

[Campbell Barton]

Yep, should be documented, until recently it was undecieded so Id not 
written the docs.
At some point I proposed "Empty" - as a string, and others (Ken?) wanted 
to use constants.

In many cases I prefer strings to constants, they just end up being less 
typing and doc searching to use.

Ken Hughes wrote:
> Willian Padovani Germano wrote:
>>> BTW, as per last week's conversation I've removed "None" as an 
>>> argument for .new() and added string checking, for "Empty" right 
>>> now.  Should I go ahead and commit that?
>>
>> I'm for it, too.
>
> OK, I'll wait to see if Cam and Stephen are on-board also then commit.
>
>> BTW, next step after that (can be after release) is to support 
>> primitives: .add(CUBE), etc. We just need to see how to pass the 
>> needed parameters, like number of segments and rings for an UVSPHERE.
>>
>> I prefer the actual arg names: .add(UVSPHERE, segments = 32, rings = 
>> 32), instead of something less readable like .add(UVSPHERE, options = 
>> [32, 32]).
>
> And speaking of constants and such, after the release I want to dredge 
> up the bitfield/constants proposals I did months ago:
>
> http://mediawiki.blender.org/index.php/BlenderDev/Bitfields
>
> Ken
> _______________________________________________
> Bf-python mailing list
> Bf-python at projects.blender.org
> http://projects.blender.org/mailman/listinfo/bf-python
>


-- 
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