[Bf-committers] Pipeline Changes Proposal

[Aaron Moore]

Hi Ton,

Sorry about the lack of clarity with the diagram, I wrote it using
only the code itself as a reference and not the current diagram.

I decided that in order to best show the changes from the previous
system, I'd simply mark-up the current diagram. Honestly, the
embedding of the callbacks in the pipeline will not change the code
that much. Code will be moved in callbacks in a separate file, but the
structure will remain almost exactly the same.

New diagram:
http://wiki.blender.org/index.php/Render_API#Pipeline_Flow

The translating of the current code so that it uses the render API
will be somewhat more complicated, but that is certainly not suited to
diagramming. That's why I am going to, for development, leave the
current system exactly as it is and build the render API
implementation in parallel to it, so that I can flip back and forth
for testing. Once the two systems work identically, I can simply
remove the old system.

Is this good? Does the diagram explain my intentions well enough, or
should I do more?

- Aaron

On 7/23/07, Ton Roosendaal <ton at blender.org> wrote:
> Hi,
>
> I don't understand how you get from the current diagram to yours...
>
> I.e. this is the current state:
> http://wiki.blender.org/index.php/Image:Render_pipeline_flow2.png
>
> -Ton-
>
> On 23 Jul, 2007, at 10:20, Aaron Moore wrote:
>
> > Hi,
> >
> > I've proposed changes to the render pipeline. If you wish to comment,
> > please do so soon, as I need to have this implemented by Wednesday. I
> > will start coding it tomorrow, but I will continue to incorporate any
> > important suggestions that people might have.
> >
> > The diagrams, brief explanation of them:
> > http://wiki.blender.org/index.php/Render_API#Pipeline_Changes
> >
> > Summary:
> > Render structure contains both render results (for all render engines)
> > and the render database (for blender internal only). These must be
> > separated. Pipeline.c will be reserved for code that ALL renderers
> > use. A new file will be created for the blender internal specific code
> > in Pipeline.c, this will also be the only place where the blender
> > internal database will be accessible.
> >
> > Comments are welcome.
> >
> > mosani
> > _______________________________________________
> > Bf-committers mailing list
> > Bf-committers at blender.org
> > http://lists.blender.org/mailman/listinfo/bf-committers
> >
> >
> ------------------------------------------------------------------------
> --
> Ton Roosendaal  Blender Foundation ton at blender.org
> http://www.blender.org
>
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>