I'm currently in the process of choosing a transform tool and I've narrowed it down to three: GreenSock, Sencoluar, or Boceto. Some questions I have about the GreenSock tool:
1) How easy is it to make modifications, for example "skin" the controls appearance? I'd like to use a vector image for my resize/rotate handles rather than the generic blocks and I'd like to get rid of the rectangular box. I like that Senocular's controls are easy to derive a class from an individual control and just override the draw method. Is that easy to do with Greensock too? Are the methods that draw the controls exposed for overriding? I'd like to make transitions to future versions of the base code as easy as possible, but I foresee fairly heavy modification so I'm looking for something where I can use OOP principles to isolate the base functionality from my derived code.
2) Are their any integrations between the Transform tools and the Tweening/Timeline tools? I'd love to, for example, be able to "record" various transform states and save tweens between those positions to a timeline. Functions in the tweening tools that would let me add a transformitem derived control to a timeline and create a tween to it's current position (from the last recorded position) would be extremely useful, for example. If not currently available, is this a possibility for the future?
3) I notice that SVN access is mentioned for the tweeningtools but not the transform tools. Some form of version control would really make handling updates easier for me (especially if I end up having to modify the base classes). Is source control access available for easy upgrades?
4) Any other comparison or comments on features that differentiate these tools are appreciated. One pro for the Greensock tool that comes to mind is multiselect (and it appears to be very well supported
5) Are there public Roadmaps for the TransformTool anywhere?