[Bf-committers] Blender 2.5 api proposal.
earlye at gmail.com
Mon Dec 1 18:27:58 CET 2008
My primary concerns are:
1) ease of integration into external systems.
a) ability to load a blender file.
b) ability to print to the console (I assume 2.5 will still be a console
c) ability to read environment variables.
d) ability to unpack a file
d) ability to start a render (including setting up regions, resolution,
choosing cameras and scenes, etc.)
2) ability to get progress messages from lengthy Blender processes on the
console. See especially patch 6161 (thanks for prior feedback on that
Campbell!). I would ***really*** like to see this in the 2.5 series if it
won't make it in to the 2.4x series - if this is there, then I can start to
support daily builds of Blender as opposed to "just" the point releases, and
I can support builds much more quickly than currently (I only managed to get
2.48a support finished today).
-- Early Ehlinger, President, ResPower, Inc.
On Mon, Dec 1, 2008 at 12:05 AM, Campbell Barton <ideasman42 at gmail.com>wrote:
> Here's is my proposal for the Blender 2.5 api.
> I'm interested to know what people think of possibly moving to a new
> api (especially active Blender/Python scripters).
> This page was started more to get an idea of what people wanted, its
> still useful for discussion.
> Last meeting we discussed weather to use python 3.0, and it seems a hot
> topic :)
> PyRNA runs with Python 2.3 - 3.0rc3, in anticipation for a possible
> switch, can we keep these issues separate since its has almost no
> baring on a new API.
> Even though this is a blender-2.5 topic, most of the people this
> affects are not on that list.
> - Campbell
> Bf-committers mailing list
> Bf-committers at blender.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Bf-committers