Tge 1.4
by Firas · in Torque Game Engine · 03/10/2005 (2:56 am) · 5 replies
What new features TGE 1.4 will provide?
About the author
#3
Improve vehicle collision handling.
is this the only changes?
03/11/2005 (8:39 am)
So is the main changes between TGE 1.3 and TGE 1.4 is: Improve vehicle collision handling.
is this the only changes?
#4
I'm not involved in the specifics of the 1.4 release, so all of this information is from what has been gathered in the forums. Please do not quote me on anything. With that disclaimer, here goes:
One of the major aspects of 1.4 (and the follow on, 1.5) is the component system for code organization. In a nutshell, what this means is that instead of having to derive functionality from a parent class, TGE will be re-organized around the concept of including components that provide specific functionality for your class. In other words, if you want to have an object "tickable", you'd include the component that handles tick processing. If you want a class to have networkablilty, you'd include the pack/unpack functionality component. It's a very nice implementation of composition basically, and will make code structure, and especially creation of new classes a lot easier for developers that may want to change fundamental aspects of how TGE is (currently, at 1.3) organized.
There is also a lot of minor, but important tweaks and bug fixes. Ben I know has been building a "todo" list for a lot of things, and some of the things that did make it into the RTS-SK pack are going to be in 1.4 as well--like I said minor, but things like removing hard coded values and replacing them with #define parameters. An example of this: To change the max number of players allowed to connect to a game in 1.3, you'd have to touch dozens of lines of code in a lot of areas. In the RTS-SK (and my understanding is in 1.4 as well), you change 2 #defines. Basically, refactoring of code that may not have been up to 100% standards.
It is possible that Ben's refactoring of the console functionality, or at least part of it, will be in 1.4 as well. Again, this is simply a suspicion on my part, so please do not try to hold Ben or GG to my guesstimate!
03/11/2005 (10:23 am)
No, hehe.I'm not involved in the specifics of the 1.4 release, so all of this information is from what has been gathered in the forums. Please do not quote me on anything. With that disclaimer, here goes:
One of the major aspects of 1.4 (and the follow on, 1.5) is the component system for code organization. In a nutshell, what this means is that instead of having to derive functionality from a parent class, TGE will be re-organized around the concept of including components that provide specific functionality for your class. In other words, if you want to have an object "tickable", you'd include the component that handles tick processing. If you want a class to have networkablilty, you'd include the pack/unpack functionality component. It's a very nice implementation of composition basically, and will make code structure, and especially creation of new classes a lot easier for developers that may want to change fundamental aspects of how TGE is (currently, at 1.3) organized.
There is also a lot of minor, but important tweaks and bug fixes. Ben I know has been building a "todo" list for a lot of things, and some of the things that did make it into the RTS-SK pack are going to be in 1.4 as well--like I said minor, but things like removing hard coded values and replacing them with #define parameters. An example of this: To change the max number of players allowed to connect to a game in 1.3, you'd have to touch dozens of lines of code in a lot of areas. In the RTS-SK (and my understanding is in 1.4 as well), you change 2 #defines. Basically, refactoring of code that may not have been up to 100% standards.
It is possible that Ben's refactoring of the console functionality, or at least part of it, will be in 1.4 as well. Again, this is simply a suspicion on my part, so please do not try to hold Ben or GG to my guesstimate!
#5
03/11/2005 (5:46 pm)
Those sound nice. I'm looking forward to seeing this. 
Torque Owner Pauliver