[Bf-committers] Node property panel enhancement

[j.bakker at atmind.nl]

Hi!

Patch is in the patchtracker. I currently only added the colorbalance as an
example. Will do other nodes as I go along the UI of the compositor.

http://projects.blender.org/tracker/index.php?func=detail&aid=27809&group_id
=9&atid=127

Jeroen

Original Message:
-----------------
From: Matt Ebb matt at mke3.net
Date: Tue, 28 Jun 2011 07:41:51 +1000
To: bf-committers at blender.org
Subject: Re: [Bf-committers] Node property panel enhancement


+1. it can be nice to have controls on the nodes for a few select things,
but should be a minimal amount or none at all.

The current situation has a few problems:
1) lack of space on nodes is a deterrent to adding further options that
might be very useful
2) lack of space on nodes causes options that do get added to be crammed in
very tight, or with giant nodes
3) with a network full of giant nodes, that number of nodes that you can see
and interact with at any given time decreases, since less nodes fit in the
view at a zoom level that's usable

Splitting this up would help a lot.

matt


On Tue, Jun 28, 2011 at 4:42 AM, Lukas T�nne
<lukas.toenne at googlemail.com>wrote:

> +1
>
> In my own nodes stuff (particles-2010 branch) i even have this
> already. This was primarily intended to avoid cluttering the node
> options with very advanced and rarely used special settings, though it
> may be debatable whether it is a good idea to hide such settings at
> all (can't even remember what node i used this for right now). It uses
> the default ui callback if no "special" draw function is defined.
>
> On Mon, Jun 27, 2011 at 8:30 PM, Troy Sobotka <troy.sobotka at gmail.com>
> wrote:
> > On Mon, Jun 27, 2011 at 11:12 AM, pete larabell <xgl.asyliax at gmail.com>
> wrote:
> >> +1 on this.
> >
> > I'll second this.
> >
> > I find that both Nuke's panel approach and Blender's
> > "within-the-node-itself" approach have some advantages in certain
> > contexts.
> >
> > Having, if I understand you correctly, a fluid layout for the node UI
> > elements would be a huge asset.
> >
> > On a side note, with regards to viewers (and apologies for hijacking
> > this thread potentially):
> >
> > 1) Will multiple viewers be available for look test LUTs?
> >
> > 2) Have you thought about how display characterization is going to fit
> > into this pipeline? As I understand it OCIO will handle the transform
> > to a known space, but that space must still be reconciled against the
> > display's characterization.
> >
> > With respect,
> > TJS
> > _______________________________________________
> > Bf-committers mailing list
> > Bf-committers at blender.org
> > http://lists.blender.org/mailman/listinfo/bf-committers
> >
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>
_______________________________________________
Bf-committers mailing list
Bf-committers at blender.org
http://lists.blender.org/mailman/listinfo/bf-committers

--------------------------------------------------------------------
mail2web LIVE – Free email based on Microsoft® Exchange technology -
http://link.mail2web.com/LIVE