Evaluating iTorque - Some questions first

Hi,

I'm currently evaluating iTorque for my upcoming iPad, iPod, and iPhone game. I'm currently prototyping it in cocos2d but am thinking something like iTorque may make the final development easier because of the toolchains it provides. With that said, I'm trying to determine the feasibility of iTorque for the game and have a few questions. Hopefully I can get some answers :)

First question - our game doesn't use your standard sprite sheets. Instead our characters are created from a bunch of different part sprites (appendages) that are put together at runtime. We basically have a hat, head, body, arms, and legs. These parts are combined at runtime to create our character sprite. We did it this way because the different parts for each class has a different look, and these parts can be mixed and matched. Creating every possible combination in a sprite just wasn't feasible. For some examples on how these look/are setup, you can check my photobucket: s93.photobucket.com/albums/l64/jaylach/Patchwork%20Battle/

As I said, these need to be combined at runtime to create a single character entity that can be animated both as a whole and the parts separately. Does Torque allow you to create a game object that contains child "sprites" that can be changed at runtime, dynamically?

Second question - because we're not using your standard sprites, our animations are not in your standard sprite sheets. Instead we are programmatically animating the characters and their parts. This is not as daunting as it sounds since our animation style is pretty simple. You can check out an early alpha of the animation style here: www.youtube.com/watch?v=w9jDdcahgvA

Does the Torque animation editor tool allow you animate game object properties (i.e: rotation, scale, opacity, etc) or is it used only for spritesheet animations?

Third question - the iOS game that is probably closest to the one we're working on is Battleheart. While the gameplay is different (our's is turn based), the number of things happening on the screen is about the same (8 character sprites, simple animations, limited particles, etc). How would a game like Battleheart perform if it was built in Torque? Is Torque performant enough to use to create a game like Battleheart or are the limitations on iOS too much to warrant using Torque?

Final question - I have become a pretty big fan of Objective-C (I know, shame on me). Is it possible to use Objective-C with iTorque or am I limited to just TorqueScript and C++?

Many thanks in advance!!!