Here is a tiny demo:
Hey great start! I especially like how you cannot directly escape the
planetoid’s gravity and must reach escape velocity gradually with a
suborbital trajectory! There must be a bug though because once I fell
through the planet.
Some observations about your gravity_linux.tar archive…
gzip your tar archives!
If you already have a tar file, just use “gzip archive.tar” and it
will become “archive.tar.gz”
You can automatically gzip your tars with "tar czf archive.tar.gz "
You can automatically ungzip your tars with “tar xzf archive.tar.gz”
You also have your entire Subversion repository in there! Yikes!
I also notice an extra file that doesn’t belong called ._gravity_linux in there.
Generating dependencies automatically is important to prevent from
making unneeded updates to a Makefile and creating a more error prone
development process. Learn how here:
On Mon, Aug 16, 2010 at 7:34 PM, Nikola Whallon <6.saturn.6 at gmail.com> wrote:
When loading images, I have a nice function in ImageObject that does that
for everything, but I call it all over the places (for example, in the
functions initShip, initPlanet, etc, each one loads its image). This makes
quitting after checking if the image loaded properly rather difficult. Is it
smarter to load all my textures at the beginning of execution?
Right now your game appears to have only one object per image, but if
that is not the case, it is important to abstract image loading away
from image referencing. So when an object asks the image API to use an
image, that image should only be loaded at that time if it is not