Behavior readability - associate with objects

[GoogleCodeExporter]

Currently the Move and Rotate commands are listed under Translators and 
Rotators.

While this may nicely represent the programming structure required, it isn't 
intuitive for a 3D artist who is used to seeing a transform as something 
applied to an object.

For consideration: put the Move and Rotate, setAccel, setPos, basically any 
commands which are meant to in the end affect an object listed as sub-items 
under that object.

This would require extensive access to the object structure such that the 
correct part in a complex hierarchy could be selected and affected.

Original issue reported on code.google.com by scott.kr...@gmail.com on 20 Aug 2011 at 12:37

[GoogleCodeExporter]

This needs review to see if it is still valid for Kuda2. These need to be 
retested and opened as needed. On hold for now until that happens. Commend as 
needed.

Original comment by jpywt...@gmail.com on 1 Mar 2012 at 10:40

• Changed state: Hold
• Added labels: Type-Other

[GoogleCodeExporter]

In Kuda2 all transforms can turn (rotate), move (translate), and scale. 
Behavior actions can be any of those and they can trigger as well.

Original comment by jpywt...@gmail.com on 1 Mar 2012 at 11:19

• Changed state: Fixed
• Added labels: Milestone-Release2.0.1

[GoogleCodeExporter]

Original comment by jpywt...@gmail.com on 17 Apr 2012 at 10:26

• Changed state: Verified