[Bf-compositor] Wiki

[David McSween]

Sebastian that looks like a good plan. We must consider that there may be
crossover between categories when a feature might improve performance or
even usability. Will we be able to triage entries then redirect them to a
more appropriate category? I guess that may be up to a dev or perhaps the
list mailing group.
On 3 Nov 2013 20:56, "Sebastian König" <koenig.sebastian at gmx.net> wrote:

> Hey!
> I already sent out a mail to this list announcing the new wiki page (WIP).
> http://wiki.blender.org/index.php/Dev:Ref/Proposals/Compositor
>
> However, I wanted to have some feedback from you regarding the structure
> and order of that page.
>
> My idea would be to have 3 main sections:
> 1) Performance,
> 2) Usability
> 3) Features.
>
> So everything related to things like ram preview, faster nodetree updates
> etc  would go to 1, things like better roto workflow, node-shelf, new
> button layout etc. go to 2, and new nodes, new backdrop features etc could
> go to 3.
> On the top of the page we could have a hitlist of the most pressing issues
> and most wanted features.
> But that’s open for discussion.
>
> So, what do you guys think?
>
> Cheers,
>
> Seb
>
>
>
> _______________________________________________
> Bf-compositor mailing list
> Bf-compositor at blender.org
> http://lists.blender.org/mailman/listinfo/bf-compositor
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.blender.org/pipermail/bf-compositor/attachments/20131103/63e58948/attachment.htm