[Bf-committers] Render API: Framework and Scene Break-Down

Shaul Kedem shaul.kedem at gmail.com
Wed Jun 6 14:10:40 CEST 2007

Both of you have excellent points, but I think it all boils down to
performance; python is nice for plugins, not as a glue, the overhead of
going back and forth to the VM and the memory management will take it's

I vote for a C API - this is the native to blender, it concerns the required
part and so on.

I also don't see the wider angle you are talking about, if python wrapper is
needed, wrap the code, but don't use it in the process itself.

Also, am reading the wiki (haven't finished) but wanted to ask if this API
will be able to change the information before the render, and if so, will it
go back to the scene or be part of the rendering only?

my 0.000001 cent

On 6/6/07, Aaron Moore <two.a.ron at gmail.com> wrote:
> A last few things to your reply, Jonathan, as I think about it.
> Whenever the blender internals are reworked, depending if it were
> relevant to the rendering, both the Pythong API and the Render API
> would have to be updated. This is bad. Bad for maintenance and bad for
> debugging.
> But keeping them separate ensures that they won't break each other.
> If they were to be integrated with each other, it would have to be
> done VERY well. Planning for this would lengthen my design process,
> tie more developers into my project (the Python API people, assuming
> they're not already involved), and make everything much more
> complicated.
> When you look at things from the point of view of the current source,
> simply reimplementing the current convertblender.c as a render API
> makes a lot of sense, because you only see the localized improvement
> in development ease.
> But looking from a wider more theoretical angle, you're point is a
> definite concern.
> ... it is a problem!
> ... which I don't know how to solve.
> If, with further thought and input from others this makes sense, and
> if someone comes up with a brilliant idea that would solve the
> practicality problem, I would be willing to go for it. But those
> blocks stand in the way right now.
> Ah, also, here's one significant difference between the APIs. The
> Render API is intended for both internal use (the internal render will
> use it) and external. Just one way in which the goals and requirements
> of the systems differ.
> Aaron
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.blender.org/pipermail/bf-committers/attachments/20070606/625774ab/attachment.htm 

More information about the Bf-committers mailing list