Plan for Melv May

It's not a good way to start a plan by saying you can't say much but ..... I'm not going to say much in this plan! Josh Williams has just posted the second part to his excellent two-part discussion on T2D and when you've ready that, you're surely going to want to rest and not read what I've got to say about it, not that there's anything else to say!

Hopefully, after reading the plan, you'll start to get a good feeling for how much work has gone into it. I also hope that when/if you get T2D, you'll see how much work has gone into making it stable and user-friendly. I've tried hard to ensure that all function parameters are checked, all provide warning console output and all do this consistently. This is Early Adopter so sure, there'll be a few things that drift from this but nevertheless, this has been the goal throughout.

As usual, I've tried to write code like I'd write a book; there's plenty of comments for those who do care how it does what it does (some people would say too many comments) and there's a clear seperation between sub-systems so you can grasp each system in turn and how they interelate.

Of course, you can ignore all the code and just get right into the scripts as this is where the real power of T2D is. Don't start thinking that you need the code immediately. T2D is designed to be completely driven from the scripts. Almost everything you can do in C++ can be done in the scripts. Having the source-code though is a magical thing and not to be dismissed though.

Putting the huge volume of T3D, demo and editor script-code aside, T2Ds C++ code comes with 39 source code files totalling (27,477 lines) 908,446 bytes in size. Man, that's alot of typing I've done!

Well, there's not much more to say now that Josh has said everything so if you've not already read it then please go make a drink, sit down and read his last plans.....

Uber Plan#1
Uber Plan#2

- Melv.