Hi Chaps,

I've re-created the intro cutscene from Quido in the new SiGL cutscene format. The new format is specifically targeted at non programmer types (designers), so it uses some unusual python tricks to make things easier.

http://www.xerian.net/browser/sandbox/showcase

If anyone is going to use SiGL (probably nobody :) this is a good place to start if you want to build a nice intro sequence.

There are some bugfixes still to go in tonight, so you can work from SVN if you want (http://svn.xerian.net/svn) or use the official build from cheeseshop, which I will make later tonight. During the comp, I will copy SiGL to a new branch which will likely get a lot of modifications, so dont expect the trunk to change too much.

The few tests I have should also help anyone who wants to try out SiGL. http://www.xerian.net/browser/SiGL/trunk/tests

-Sw.

Palotai Robin has collated the results from the system survey run over the last month. Thanks!

This could be a useful guide for people looking to use uncommon technologies in their entry.

Hi all, I've collected some pre-made music which is licensed with the GNU General Public License which will be used in the pyweek entry. To comply with the rules, this music can be found on our website already, and is available to other entrants as well.

I am really excited about pyweek, can't wait. I decided to flex my game makin' muscles and whip up some stuff yesterday. In the end the basis for a lunar lander type game via steam. Fly it around until steam runs out! Thankfully I have a different idea should steam be the choice.. something a bit more creative and unique (but its good to have had the chance to play with rendering a barebones particle system type steam cloud :)

I finally managed to salvage my python work from my old hard drive, and these are the two modules I referred to in my previous post:

xmlValue

From that page:

This is a set of (two) modules which convert between a simple xml specification and nested Python dictionaries, making basic data easily writable and retrievable. The result is essentially very basic serialization that is language independent and human readable.

Again there are numerous serialization modules (Pickle, marshal, etc.), and I'm certain someone has made on that uses XML, however I was hoping to use these two that I've written (the data conversion is literally effortless). I know we're supposed to announce any personal libraries we plan to use far ahead of time, so if anyone has any qualms with these modules being used, I certainly won't complain. :)

Hi!
MaciekL speaking from UniLodians.
A statistical fraction of my mind cannot give up and shouts: Ask them what countries do they come from.
So I'm asking: Ppl, what countries do You come from? :D
We (UniLodians) are from ex-soviet-polluted Poland.

Today I tricked two more friends into joining us. This makes us a crew of six programmers!

http://gizmothunder.blogspot.com/2006/03/pyweek.html
I thought you guys might like it .. by the way its' my blog :D

Hi everyone!

I have a beginning idea for a game (theme vote permitting) but I want check if its 'legal'.

Im going to write my game logic in python (well, duh, obviously) but I want to write my user interface (graphics, input etc) in plib (http://plib.sourceforge.net/) which is a c++ graphics library.

Part 1 is that there _ISN'T_ a python interface for plib. Now from reading the rules, making one in the contest would be ok. (Under the bit that says: "doesn't preclude the use of supporting languages (eg. C or C++ libraries")

(Writing some C++... yes, I am insane, thanks for asking. :-)

My problem is that if Im going to write code to do some of the UI, Id much rather write:

• all the game stuff (mapping, unit control, game logic, what to display etc) in python 'game code'
• all graphics, key/mouse input, user interface and actual display (maybe even collision detection) in C++ plib 'client/UI code'

The idea is that the python engine could just do "begin burst_steam_pipe animation at x,y" and the C++ engine would draw and animate it and python could keep on with the game logic leaving C++ doing 'grunt' work.

The thing is that that would be more than just a 'simple' interface to the library, rather it would handle more complex stuff like animation and things like that which is why I'm posting here.

The key points seem to me to be:

• The source would have to be released with the game (duh).
• It wouldnt have any 'game logic' in it (plib is _just_ a graphics layer, UI, scene graphs and collision detection and other stuff)
• Does 'collision detection' count as game logic? It seems to me that game logic is what you do with the collision once you detect it (and that part has to be in python, naturally).
• Richard mentioned that using other languages for optimization (which this kind of fits) but its hardly mentioned in the rules.
• The rules say: "This is a Python programming challenge, but that doesn't preclude the use of supporting languages".. well ok...
• ... but the other hand, the line continues "eg. C or C++ libraries" which seems to point away from writing much non python code yourself.

It _feels_ ok to me (as the C++ code is for 'grunt' work only, graphics, collision crunching, all which seems to fall under 'optimization' and not game logic) but I thought Id ask....

Maybe we should insert into the rules (at point 2) something about languages and not roll it into "Entries are to be written 'from scratch'" section?

Opinions... ?

So I had fun opening the sealed themes package this morning...

• Someone else's trash
• A fraction too much friction
• Mind the gap
• Doorways
• It runs on steam!

I'm not sure I personally have a favourite yet. I like 'em all :)