[Bf-committers] Transform Whitepaper

[Chris Want]

They are just looking at cleaning up the code
that is executed when you press g,s,r, etc (the
dreaded transform() function) -- nothing as
ambitious as what you have presented. So by
'transformer' they mean things like handles
you can grab to move or rotate or scale, and
not a stack of things.

Chris

Douglas Bischoff wrote:
> On Mar 11, 2004, at 12:36, Ton Roosendaal wrote:
> 
>> To look at is:
>> - where does 'transformer' data reside, in a Blender SpaceWindow, in a 
>> scene?
>> - what if 2 transformers operate simulteneously (could work!)
> 
> 
> Are you suggesting that one might be able to have a "stack" of 
> transformers each doing their thing to the underlying object? Something 
> that would leave the original object unaltered but process the object 
> through the stack prior to display and/or rendering?
> 
> That'd give you the ability to turn some transformers on or off 
> temporarily to see the effects (playing around with different options, 
> for example, or disabling processor-intensive ones for quick editing), 
> or re-order items on the stack to change when they take place relative 
> to each other...
> 
> ....or am I taking this waaaay farther than you were originally 
> suggesting? :-)
> 
> -Bish
> 
> _______________________________________________
> Bf-committers mailing list
> Bf-committers@blender.org
> http://www.blender.org/mailman/listinfo/bf-committers