[Bf-committers] [Bf-blender-cvs] SVN commit: /data/svn/bf-blender [34914] trunk/blender/release/scripts/ui/ properties_material.py: Commit patch [#25939] material panel proposal by Ervin Weber (lusque).

ervin weber ervin.weber at gmail.com
Thu Feb 17 15:27:54 CET 2011


first of all, I'm sorry if I didn't publicized this enough.
After discussing in IRC, i have mailed bf-committers over 2 weeks ago:
The (few) replies where positive, so I raised the topic in the last 
sunday meeting. Nobody opposed and so it was committed.

I'm new here, so probably it was my fault for not knowing where this 
kind of topics are better discussed. If that was the case, again, I'm sorry.

Anyway, now that I have your attention, I'd like to propose a compromise 
solution: change the panels contents depending on whether the material 
uses a nodetree or not.

[simple material]:
maintain the 'old' panels as they were before

[node material]:
add the pipeline panel and move into it the relevant properties
(as the actual panels are)

I agree that the pipeline panel might be a burden when used with a 
simple material. But I think it is needed when dealing with 
node-materials, if only to show how the render engine actually works.

best regards,
Ervin Weber

On 17/02/2011 12.42, Brecht Van Lommel wrote:
> On Thu, Feb 17, 2011 at 12:06 PM, Matt Ebb<matt at mke3.net>  wrote:
>> On Thursday, February 17, 2011, Daniel Salazar - 3Developer.com
>> <zanqdo at gmail.com>  wrote:
>>>   It makes perfect sense if you know how it works
>> it doesn't make perfect sense and it never did in 2.4 either.
> We can disagree about what's
> more important, but I consciously made this design decision when
> adding the panels.

More information about the Bf-committers mailing list