I've moved Game Objects to Google Code. It's new home is http://code.google.com/p/gameobjects/. There are source and Win32 packages available.
Game Objects is intended to be a collection of classes to assist with the creation of games, or other realtime applications. Currently there is a 2D and 3D Vector class, and a well optimized 4x4 Matrix class, but eventually Game Objects will contain code for general route finding, entity management, AI and other cool stuff. I'm happy to take suggestions, and if you would like to submit code - even better! All classes should following these commandments.
- Easy to use. Thou shalt be no more complex than absolutely necessary, and thou shalt protect the user from doing stupid things.
- Fast. Thou shalt be fast, unless it comes in to conflict with 1.
- Pure Python. Thou shalt be in pure Python. Optimized C versions may exist as long as the interface is identical.
- Few dependencies. Thou shalt not require external modules, other than the standard library. External modules may be optional if they increase performance.
Current version is 0.0.1, but don't let the low version scare you, the current classes are quite stable. Most of my previous little PyGame experiments have used old versions of Game Objects, so I have ironed out most of the kinks. I plan on putting together a collection of samples, so there is something to play with. Any suggestions for interesting projects that make use of Game Objects will be gratefully received.
Update: I have created a Google Group for discussion of Game Objects (http://groups.google.com/group/gameobjects).
6 Responses to "Game Objects Commandments"
Great stuff!
Will,
Per my previous post (below) I now see that you *are* the author of these modules... great work! These should be in every developers toolbox (and not just gamers).
I haven't had time to look over every method, but if you need it I be glad to share some affine classes I've created.
Also, Is it ok to add a GLP license? As well as a credit? Not that I will be destributing your code... but I will be sharing it with my collaborators, and I like to see credit given where it's due. (and you deserve a lot of credit for this!)
And if you want I'll be glad to add some doc_strings
Feel free to email me.
rd
Hi Robb,
Glad you found Game Objects useful. I'll put copyright statement in the next release. As for license, I want to make it completely free for anyone to use, even commercially, with no draconian rules and regulations. Personally I'd like to use the term 'public domain', but everyone wants a 'license' these days. Let me think about it!
If you would like to submit something to the project, then you are more than welcome! Although, please work with the latest version from SVN, it's changing constantly.
Will
doesn't this have any documentation or something?
Hi Will!
I've been learning Python out of your book, and I have to say it's been a big help so far. I've just started getting into Chapter 5 and a lot of the material that wasn't clicking before is falling into place.
But I've just downloaded your game objects package, and I can't seem to install it onto my Mac OS X system. No worries though, I think I can just copy the files into the folder I'm using them in to use them, but it would be nice to have some documentation.
If I can help with it, please let me know.
Scratch that last post. I just misread the instructions.
Either way, great book and I'm learning a lot!