by date
Plan for Bil Simser
Plan for Bil Simser
| Name: | Bil Simser | ![]() |
|---|---|---|
| Date Posted: | Jul 01, 2004 | |
| Rating: | Not Rated | |
| Public: | YES | |
| Comments: | YES | |
| RSS Feed: | or Subscribe with . | |
| Profile Page: | View profile page for Bil Simser |
Blog post
The Torque Cookbook. 'nuff said.
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!
Recent Blog Posts
| List: | 08/07/04 - Plan for Bil Simser 07/06/04 - Plan for Bil Simser 07/01/04 - Plan for Bil Simser 05/10/04 - Plan for Bil Simser 07/09/03 - Plan for Bil Simser 07/01/03 - Plan for Bil Simser 06/28/03 - Plan for Bil Simser 06/26/03 - Plan for Bil Simser |
|---|
Submit your own resources!| Jorgen Ewelonn (Jul 01, 2004 at 04:37 GMT) |
| Bil Simser (Jul 01, 2004 at 17:02 GMT) |
| Bryan Edds (Jul 01, 2004 at 19:57 GMT) |
My addy is bryanedds_yahoo.com (replace the underscore with the @ symbol)
You must be a member and be logged in to either append comments or rate this resource.



Not Rated


