[Bf-python] More Proposed API changes.

[Campbell Barton]

At some point I suggested database for accessing blender objects and 
Theeth gave a very convincing argument as to why this wasnt logical 
Blender data dosnt match a database or some such arg.

db or DB are more likely to be variable names in existing python scripts 
too. - DB isnt blender spesific, "blend.objects" - reads as a blender 
object DB.* isnt obviously blender data, tho its not that strong an 
argument, Id also prefer to have the new API all lowercase, and 
camelCaps where 2 words are used...

Since the data under "blend.*" or "DB.*" may also have user preferences 
with blend.config I dont think blend should be limited to data access only,

My vote is to have "blend" - after thinking about it some. external data 
is a part of the blend file even if its stored elsewhere.



Stephen Swaney wrote:
> On Fri, Mar 09, 2007 at 11:48:04AM +1100, Campbell Barton wrote:
>> Agree that "blend" a little false since it imply's the data is in the 
>> current .blend file,
>>
>> However its the best of a bad lot ;)
>> the data is still IN the blend file, just as a reference.
> 
> Yeah, "blend" is definitely a little misleading.  The data is not
> in a .blend until it has been saved there once.
> 
> Since we are talking about Blender's database, maybe that is what we should
> call it.  DB is a nice short acronym for 'database'.
> 


-- 
See MetaVR Visuals Used at the Combat Studies Institute
http://www.metavr.com/casestudies/baghdadviews.html

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