[Bf-python] Thought about IRC meeting and beyond

[Campbell Barton]

Just comment on 1 point.
I think we should make users to think in terms of the current scene 
defining the context.
All blender tools use the current scenes data.
Object.Get() - should only ever be used in rare cases, since mostly you 
want the objects in the scene.
could we encourage python'ers to use scene.getChildren()?

Also. python coders need to be aware of the active object and how do 
deal with it. Some documentation on this would be good to write.

Not totaly clear on the object access, but am interested it what this is 
about. ob.data seems a nice way to go?
Whats suggested..
was
ob.link(data) # Could be replaced by.
thinking ob.data = data

- Cam


> A related issue is what Campbell has pointed a few times: Object.Get() 
> returns all objects in Blender, not just the ones in the current 
> scene. This is bad for exporters, for example. We might simplify 
> things, since getting from current scene is a more common request, and 
> make that the default: .Get(fromAllScenes = False) or something like 
> that.
>
> PS: it was agreed yesterday that we should use the wiki for our new 
> api discussions. Personally I think it's better (faster, cleaner) to 
> use this list for the chatting stages, like this reply, but ok, wiki 
> pages are better to organize all discussions and conclusions.
>
> Stephen: please explain to us your idea about this project's wiki 
> "layout": where we discuss (single page, per topic), etc.
>
> http://mediawiki.blender.org/index.php/BPy_API_Cleanup_-_2006
>
> -- 
> Willian
> _______________________________________________
> 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