Considering to get iTgb

#1 You can complete a game, but I strongly recommend learning Obj-C. You don't want to be stuck without a feature because you can't implement it quickly in CocoaTouch ;)

Take a few hours to learn Obj-C. If you know C, there is very little to learn. The majority of the new stuff is really Apple's CocoaTouch API, which is mostly well-documented. There are also books on the subject (and a good one covering 3.0 coming from Pragmatic Press after 3.0 is released).

Coming to an Apple platform, you should learn the local language. That's just the way they work ;)

#2 I'm not a fan of Obj-C, but Ronny has a point to an extent. I had to learn the language to help work on the engine, but I will probably never use it for game play. If you want an iPhone specific feature that has not been implemented yet, such as accessing the camera, you will need to learn Obj-C. If you want to create a shooting behavior or some other game functionality, you will not need to learn it.

Most of my game play code was written in TorqueScript and C++. The behaviors are in C, and the really basic stuff is in TorqueScript.

#3 @Ronny, Thanks. At some point I do think I'll need to learn it. I have a lot of Torque scripts that I have written over the years and would really speed things up so I do want to use that as an advantage for my first game on the iDevices.

@Micheal, regarding the loading time and memory consumptions what are your takes on that.

Thanks !

#4 @Aun - Right now it's borderline depending on what kind of game you are making. Most users who have found their game taking too long to load have customized the engine by ripping out certain parts they do not need, or further optimizing their assets (switching to PVR, powers of 2, MP3s, etc).

The base example for the engine, BehaviorShooter, loads in about 10 seconds depending on which device you are using. This could easily be increased or decreased depending on what assets you use and how you load objects.

As far as memory consumption is concerned, so far the engine is holding up well. In the upcoming releases we are integrating some memory reduction code that will drop about 40% - 50%.

#5 Thanks for the clarification Michael, 10 seconds isn't that bad :)

I guess going with iTgb should be a reasonable option for me. Now my last question is when can we expect the next release of iTgb ?

Thanks again :D

#6 Friday is supposed to be 1.2.1 day, with a heap of bugfixes.

Is the plan to set milestones for versions and release whatever is ready then?