Well after a day and all I have are some graphics in place. It's pretty safe to say I won't have everything ready by the end of the week at this pace. Tomorrow I'll have to decide what to cut.

The level editor has taken up most of the afternoon today because of a couple of hitches. Mostly, I was stuck for about an hour trying to figure out why my objects weren't being lit correctly in the glOrtho view. I ended up with a piece of test code that rendered a glutSolidSphere and then called a display list that also rendered a glutSolidSphere (same params, nothing else in the display list) and the second sphere was rendered unlit.

I still don't know why. My level editor now has the map portion drawn using a perspective view. It just means the picking is a little harder, but thanks to gluUnProject (and a little tweaking) I can get pretty accurate coords - enough to place map objects anyway.

Next up will be saving maps and enforcing a grid. Then I'll go back to working on more game code. Still plenty to do there...

I'm using Alex's text-rendering library PyGlyph to do the text in the buttons, if anyone's interested. It apparently has better layout than pygame.font.

The latest version of the game is bouncy-r3.

Had a busy weekend, and so only just got around to checking the winning theme.

It's not the one I'd have liked, but then that's hardly a problem as I'd given approximately zero time to thinking of ideas for any of the themes anyway.

My immediate thought is to make the "act" part of the theme an acronym. Don't know what yet, but I'll hopefully be able to come up with something that'll mean I don't have to do too much in the way of artwork. I can't draw for toffee, and with a theme like this, unless I'm very careful, I'll have to do something artistic.

Didn't get a whole lot done today. Lot's of Real Life stuff to keep me busy. This whole week might be like that. Tuesday especially looks to be a total loss. :(

I should have a playable game if I can get through my list tomorrow.

Cameron Blackwood requested a node class which rendered all its children using a display list, for performance reasons.

It was a good idea, so I implemented it for him. I modifed the QGL compiler to work with a new Static node.

The rest of you can get the updated modules from here:

http://qgl.googlecode.com/svn/trunk/qgl/scene.py
http://qgl.googlecode.com/svn/trunk/qgl/render.py

Use these modules instead of the QGL-7B versions. It provides a Static node, which works like a group node, but draws all its children using a display list. Any problems let me know, I'll do my best to fix em in a timely manner...

You can recompile the node at anytime to update it with a new display list.

I am yet to even decide on a game concept for my entry... :(

List of things we would like to see disappear:

• mother in law
• debts
• bikinis

Here's a screen shot of a simple game idea. It won't win me any prizes, though.

Still need an idea though...

Day one went pretty well. Settled on an idea without even really thinking about it. I started coding up quite a generic game architecture, events handling, graphics management code etc. Brain stopped working pretty early from lack of sleep from coding the night before, so I switched to art and got many of the game objects drawn. Today my cold/flu has returned somewhat, but I'll be trying to focus on getting the background scaling maths working correctly, and animating the player's avatar.

Ignoring a couple of collision-detection bugs (you can get through the fence in the right place, and the collision response "bounces") I went to work on some of the other game features. Notably the bunny now gets hungry when you make it do things. You can eat the yummy lettuce to satisfy your hunger.

I intend "easy" mode to be for people who just want to muck around, so the time limits will be much lower (or non-existant) and the farmer will move slower, etc. For example, on "hard" mode you'll also get hungry if you just sit around.