<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:verdana, helvetica, sans-serif;font-size:12pt"><div>Hello,</div><div><br></div><div>My first post! I totally agree that there should be some cleaning up of old features that have been replaced with more flexible ones, however I would prefer to keep:</div><div>'Do Composite' and while the render window placement could be turned into a user preference, I still think it is relevant too.</div><div><br></div><div>'Do Composite' is quick and easy to turn on/off the compositor when doing test renders. I often use the compositor for vector motion blur and like to turn that off when I am doing tests and I like to turn it off in the same panel that I am changing other render settings for tests and I can do that while in any screen layout. Two of the three methods for turning off Do Composite require the nodes panel to be visible. Also, changing noodles just
to turn it off would be bothersome and I would not consider it a legitimate workflow technique.</div><div><br></div><div>As for render window placement I am a bit confused about 2.5's current behavior. 2.5 currently chooses a panel to turn into an image viewer, which is a pain since I have to change it back to whatever it was before after a render. I prefer using the separate render window because it does not change the layout I am using. 2.5 at this point does not seem to look for an existing Image Viewer to place the rendered output either so even if there is a viewer open, it will change my nodes view or 3D view into a viewer. I am assuming this behavior will be tweaked or there is a preference I have missed. Since the renderer in 2.5 is threaded I see why having it render to a panel is a better idea than a new window blocking the UI, but please don't remove this functionality completely. Another thought is to have an option to render to a viewer or
render to a new window. This could be in the render menu and a simple checkbox in the Scene panel.</div><div><br></div><div>Just my $.02,</div><div><br></div><div>Best Regards,</div><div><br></div><div>Scott Meador</div><div style="font-family:verdana, helvetica, sans-serif;font-size:12pt"><br><div style="font-family:Courier New, monaco, monospace, sans-serif;font-size:10pt"><font size="2" face="Tahoma"><hr size="1"></font><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Sat, 9 May 2009 08:48:16 +0200<br>From: William Reynish <<a ymailto="mailto:william@reynish.com" href="mailto:william@reynish.com">william@reynish.com</a>><br>Subject: [Bf-taskforce25] Blender spring cleaning<br>To: "The Blender 2.5 TaskForce" <<a ymailto="mailto:bf-taskforce25@blender.org" href="mailto:bf-taskforce25@blender.org">bf-taskforce25@blender.org</a>><br>Message-ID: <<a
ymailto="mailto:A659966D-3B45-48B4-B155-761F840A0C23@reynish.com" href="mailto:A659966D-3B45-48B4-B155-761F840A0C23@reynish.com">A659966D-3B45-48B4-B155-761F840A0C23@reynish.com</a>><br>Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes<br><br>Hi All,<br><br>Now that spring time is upon us, it's a nice opportunity to do some <br>cleaning up in Blenders functionality. Over the years, some features <br>have been superseded by others 2.5 is a good release to make some <br>clean cuts, now that forward compatibility is out of the window.<br><br>Certain features have been replaced by better alternatives, but until <br>now the older implementations haven't been removed yet. We have things <br>like 'Old Track' and 'CurveFollow' controls which have been replaced <br>by more flexible constraints instead. Keeping these old features is <br>really just adding bloat, and confusing to the end user.<br><br>The reason they've been kept
until now has been to ensure a transition <br>period, but really these features have been redundant since what, <br>2003? It's about time we have the guts to just go ahead and remove <br>them. Yes, in the short term it's annoying to have features disappear, <br>but in the long run we'll have a better, cleaner Blender.<br><br>When talking about outdated features, I'm specifically thinking about <br>these for now:<br><br>Curve animation (superseded by the Follow Path constraint)<br>Old Track (superseded by the Track To constraint)<br>Render windows placement controls (useless really, and irrelevant as <br>Blender renders using the image editor by default)<br>'Do Composite' (There are at least three ways of turning on and off <br>the compositor. There's the 'Use Nodes' button in the compositor <br>itself, you can make a direct link from the RenderLayer to the <br>Composite node, and you can use the 'Do Composite' button. There's too
<br>much redundancy here.)<br><br>These are the ones I could think of off the top of my head, but I'm <br>sure there are probably more? Anyone else have suggestions for <br>features in need of a little cleaning out?<br><br>It's a nice time to fight back against bloat and feature creep.<br><br>Cheers,<br><br>-William<br><br><br>------------------------------<br><br>_______________________________________________<br>Bf-taskforce25 mailing list<br><a ymailto="mailto:Bf-taskforce25@blender.org" href="mailto:Bf-taskforce25@blender.org">Bf-taskforce25@blender.org</a><br><a href="http://lists.blender.org/mailman/listinfo/bf-taskforce25" target="_blank">http://lists.blender.org/mailman/listinfo/bf-taskforce25</a><br><br><br>End of Bf-taskforce25 Digest, Vol 9, Issue 11<br>*********************************************<br></div></div><div style="position:fixed"></div></div><br>
</body></html>