Why was polygon coloring functionality for addons disabled/removed?

I’m just asking, I usually agree with what Campbell does in Blender development, but some devs. working on render exporters were annoyed when the functionality that allowed objects/polygons to be colored when setting materials for external renderers like when using BI was removed as a new restriction for RNA saying it’s bad practice (which is not writing to RNA) and weren’t given an alternate method.

Apparently for Luxblend25 at least that means a new scene using Luxrender would now have all objects be the same color and you have to click on them to know what color they are, why is this restriction in place if it removes the ability to have some of the same feedback for which materials are which in object mode as in BI?

So what is the reasoning, why is it considered bad practice, and why weren’t the devs. of external rendering interfaces notified? This is not bashing the devs. as they have been doing a good job working on 2.5, but this seemed to me like a ‘yank the rug out from under them’ moment as it seems to involve removing functionality rather than adding it.

Apparently stability and correctness trump convenience.

And, as we all know, the renderer api is ‘experimental’ (in fact ton wanted to rip it out until it could be implemented ‘correctly’) so stuff like this is to be expected.

There are other (hacky) ways to work around this until a proper system – most likely involving the event system – is implemented.

At least Doug Hammond has taken it to the mailing list so Campbell will be aware
http://lists.blender.org/pipermail/bf-committers/2010-December/029637.html
http://lists.blender.org/pipermail/bf-committers/2010-December/029638.html

Now he raises an issue with another commit (despite the possible benefits it would bring to python coders)
http://lists.blender.org/pipermail/bf-committers/2010-December/029636.html

At least it will spark some useful discussion of what to do in such cases to keep render exporters running, the exporters right now are the reason some people are even using Blender 2.5. :slight_smile: