[Bf-taskforce25] Blender spring cleaning

[Campbell Barton]

from reading williams post +1 in general though there are some
spesific I'm not sure of, no opinion on render window.

one extra thing that would be nice to change for 2.5
Disallow empty strings for names everywhere.
currently this is allowed for vgroup names, datablock names etc, I
think most places you can type in a name allow this.
If you use names like this your likely to hit problems so better disallow it.

Other things I have mentioned before but not in 1 list :)
- remove IFDEF's for BeOS and AMIGA in the code
- remove Amiga and HamX image formats
- remove videoscape format support
- remove C coded dxf, vrml support
- drop current radiosity code (talked to ton and he's ok not to port it over)
- remove sumo (solid) from the BGE
- remove ODE, QHull which bullet physics wont use
- Personally Id advocate dropping Irix support too since its been 'End
of life' for quite some years now but others probably want to keep
maintaining it.

On Tue, May 12, 2009 at 2:46 AM, JimmyVolatile <spam at useful.no> wrote:
> Small suggestion:
> Just make the render window remember its placement each time.
>
> After a render is done, you drag simply the window to where you think it's
> better fit and it will keep re-appearing at that position for each render
> (i.e. Blender stores the position of the window's top left corner).
> In case the the render is larger than the available space, the window's top
> left corner is offset from the desired position to make sure all of it
> appears within the edges of the screen.
> If the window/render is larger than the screen resolution, the window is
> offset, as before (appears maximized) and content is scaled down to fit
> within the window borders.
>
> This way, the window configuration works transparently to the user,
> utilizing the actions s/he would make use of anyway :)
> /Jimmy Volatile
>
> On Tue, May 12, 2009 at 9:28 AM, joe <joeedh at gmail.com> wrote:
>
>>
>> Ah I use the render window placement all the time, I'd be sad to see
>> it go.  I do agree about the composite buttons though. . .I think we
>> should either make Do Composite be an alias to the node editor's
>> button, or (my preference) remove the node editor button alltogether.
>> Joe
>> On Sat, May 9, 2009 at 12:48 AM, William Reynish <william at reynish.com>
>> wrote:
>> > Hi All,
>> >
>> > Now that spring time is upon us, it's a nice opportunity to do some
>> > cleaning up in Blenders functionality. Over the years, some features
>> > have been superseded by others 2.5 is a good release to make some
>> > clean cuts, now that forward compatibility is out of the window.
>> >
>> > Certain features have been replaced by better alternatives, but until
>> > now the older implementations haven't been removed yet. We have things
>> > like 'Old Track' and 'CurveFollow' controls which have been replaced
>> > by more flexible constraints instead. Keeping these old features is
>> > really just adding bloat, and confusing to the end user.
>> >
>> > The reason they've been kept until now has been to ensure a transition
>> > period, but really these features have been redundant since what,
>> > 2003? It's about time we have the guts to just go ahead and remove
>> > them. Yes, in the short term it's annoying to have features disappear,
>> > but in the long run we'll have a better, cleaner Blender.
>> >
>> > When talking about outdated features, I'm specifically thinking about
>> > these for now:
>> >
>> > Curve animation (superseded by the Follow Path constraint)
>> > Old Track (superseded by the Track To constraint)
>> > Render windows placement controls (useless really, and irrelevant as
>> > Blender renders using the image editor by default)
>> > 'Do Composite' (There are at least three ways of turning on and off
>> > the compositor. There's the 'Use Nodes' button in the compositor
>> > itself, you can make a direct link from the RenderLayer to the
>> > Composite node, and you can use the 'Do Composite' button. There's too
>> > much redundancy here.)
>> >
>> > These are the ones I could think of off the top of my head, but I'm
>> > sure there are probably more? Anyone else have suggestions for
>> > features in need of a little cleaning out?
>> >
>> > It's a nice time to fight back against bloat and feature creep.
>> >
>> > Cheers,
>> >
>> > -William
>> > _______________________________________________
>> > Bf-taskforce25 mailing list
>> > Bf-taskforce25 at blender.org
>> > http://lists.blender.org/mailman/listinfo/bf-taskforce25
>> >
>> _______________________________________________
>> Bf-taskforce25 mailing list
>> Bf-taskforce25 at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-taskforce25