Plan for Bil Simser
by Bil Simser · 06/30/2004 (9:33 pm) · 3 comments
Lately I've been turned onto the Cookbook type books out there (specificially the C# ones now). I spent sometime hunting down the various O'Reilly (and others) cookbook series and found them to be excellent on presentation.
If you haven't seen a cookbook, it offers a definitive collection of solutions and examples in a domain language (C++, Perl, C#, whatever). Recipes range from simple tasks to the more complex, and are organized with respect to the types of problems you'll need to solve as you progress in your experience as a programmer. Nearly every recipe contains a complete, documented code sample showing you how to solve the specific problem, as well as a discussion of how the underlying technology works and a discussion of alternatives, limitations, and other considerations where appropriate.
So I'm proposing the idea of constructing/collaborating/consolidating the snippets we all know and love into one place in the form of a Torque Cookbook. Simple, small, focused solutions to specific Torque problems. This is not "How do I make a game" but "How do I add random player start locations" or "How do I let the user take a screenshot". Stuff like that which is categorized and organized, all with sample code (I think the sample code is a must as more often than not, we have a post of "do this and this and magic will happen").
I've started a thread in the forums here if you're interested in continuing the idea. See you there!
If you haven't seen a cookbook, it offers a definitive collection of solutions and examples in a domain language (C++, Perl, C#, whatever). Recipes range from simple tasks to the more complex, and are organized with respect to the types of problems you'll need to solve as you progress in your experience as a programmer. Nearly every recipe contains a complete, documented code sample showing you how to solve the specific problem, as well as a discussion of how the underlying technology works and a discussion of alternatives, limitations, and other considerations where appropriate.
So I'm proposing the idea of constructing/collaborating/consolidating the snippets we all know and love into one place in the form of a Torque Cookbook. Simple, small, focused solutions to specific Torque problems. This is not "How do I make a game" but "How do I add random player start locations" or "How do I let the user take a screenshot". Stuff like that which is categorized and organized, all with sample code (I think the sample code is a must as more often than not, we have a post of "do this and this and magic will happen").
I've started a thread in the forums here if you're interested in continuing the idea. See you there!
About the author
#2
07/01/2004 (10:02 am)
I thought I would put it as a .plan as well since that's what it amounts to. The more exposure the better I guess.
#3
My addy is bryanedds_yahoo.com (replace the underscore with the @ symbol)
07/01/2004 (12:57 pm)
YES! Great idea! I totally encourage that! Hell, I might even help!My addy is bryanedds_yahoo.com (replace the underscore with the @ symbol)

Torque Owner Jorgen Ewelonn