First Impressions

#1 Well I just got started with it, it seems really good. So far I am still in the tutorials, but just have one left to do and then i am going to try to make my own little game and go from there.
The interface and layout is really user friendly and everything seems to function really well.
I did notice that the debuggin is a bit hard to read/ figure out, but i was refered to get Torsion, and I am just about to start to use that now.

#2 I just started using the trial version two days ago and I am going through the tutorials (on the second one right now). I was actually getting started on TGE but was intrigued by TGB. I am hooked! I will continue to develop models and games with TGE but I think I will be using TGB while I am becoming more proficient with TorqueScript. Great job with this one guys!!

#3 It be nice if there were some syntax checking, or something like "compiler errors" to let me know when I make a mistake. I got stuck a few time in the tutorials because I typed "$this" instead of "%this", for example.

Another nice feature would be to add a script editor directly within the engine so restarting wouldn't be nescessary so often, or perhaps add a button to quickly reload (or at the very least, automatically restart after quitting) to update changes from script files.

#4 Typing $this instead of %this isn't going to be shown as a compile error. For example, %this is a local variable, however $this is a global variable. Two valid and seperate variables there. ;)

Syntax checking is caught and logged in the Console in TGB, and also written to console.log when you exit TGB.

Hope that helps,
- Tom.

#5 @Nebu: the engine automatically ignores .dso's and recompiles your code everytime the level is ran...so you don't need to restart your engine.

#6 Thanks for the tip on the console. I'll start checking there whenever my scripts start performing strangely.

This might just be a personal preference thing, but I like languages where you have to declare a variable before using it for exactly the reasons mentioned above. I know VB lets you toggle mandatory declarations on and off with OPTION EXPLICIT. Any chance a similar feature could get put into TorqueScript?

#7 If you have the source, and the knowledge, I'm sure you could do it. ;)
I have no idea if it is in there already, never looked how to do it, never wanted to. :)

#8 I love TGB. It is very quick to get up to speed. Especially with the great docs and examples. I'm having a ball when I find time to mess around with it.

#9

Quote:
I know VB lets you toggle mandatory declarations on and off with OPTION EXPLICIT. Any chance a similar feature could get put into TorqueScript?

It's a preference you can set (thanks to Labrat for reminding us all!):

$Con::warnUndefinedVariables = True;

#10 I went ahead and bought it, since it is a major step up from GameMaker (www.gamemaker.nl) and is more powerful out the box.

The only thing that bugs me right now is that it's not full screen when you are working.

#11 @Lamont: do you mean the application itself, or the "working area".

You can use alt-enter, or Select the Edit->Preferences menu to have the application go full screen.

#12 I saw that, but it's not "Windows" full screen. It flickers my monitor when I go from TGB to Photoshop/Lightwave/Other Apps. Maybe the option to offer the "full screen" resolutions in windowed mode?

#13 So what you want is a "maximize" so that it takes up all screen space, but still is windowed, if I read you properly.

The maximize capability was taken out at the last minute do to some functional inconsistencies, and as far as I am aware will be worked on in the future.

#14 Cool. So I am not going crazy ^_^!!