can someone tell me? do we have to use skellation? i want to handle all the stuff myself

Pyglibs 0.3 was released with 1.5 hours till the month-before deadline.

Check the pygame site to get it. :D

I will probably write a few more examples, clean up the docs, and maybe bug fix it a bit in the next few weeks - but no api changes till after pyweek, if that is ok, or would I need join the "you should dq me for using this lib" crowd if I do that?

http://www.eugmanhome.com/python/pyblib/pyblib1.py

It's basically a few functions that I don't want to have to recode for pyweek. I imagine after pyweek I could expand it into a block game library or a library with more general functions but I doubt there is much demand.

download .tgz

I'm not sure if this library is quite pyweek worthy yet (richard - can you comment on this), at the very least, I made a bit of progress and hope to release a better version in the future. Any feedback would be greatly appreciated!

------------------------------------------

Phil's mini-Utilities for pyGame
"pug" a 64k version of "pgu"
(c) 2007 Phil Hassey

"pug" is meant to be independant of pygame, but at present it only includes drivers for pygame.

cnst - contains all constants like K_q, MOUSEBUTTONDOWN, etc
driver - access to low-level drivers (pygame)
dialog - some handy States for Prompt, Choice, Pause
engine - the state Engine and a default State
gui - a re-written trimmed down version of the pgu.gui API
theme - the gui theme, meant to be customized on a per-game basis

The documentation is in-line in the code, and will be somewhat similar to www.imitationpickles.org/pgu/docs/. The documentation in here is not complete yet.

Feel free to run demo.py to see a sample gui screen.

In the same spirit as Hectigo and tsmaster, I have now with this post released a small library called pymunk just for pyweek! :)

Chipmunk is a 2d physics engine written in C, and can be found here: Chipmunk.

pymunk is a low level binding made with ctypes, so you can now use Chipmunk in your Python code!

The link: pymunk-0.1.zip

And a screenshot from the included demo:

And a cut-n-paste from the readme:

pymunk - pyweek5 edition
========================
2007, Victor Blomqvist - vb@viblo.se


ABOUT
pymunk is a wrapper around the 2d physics library Chipmunk
(http://wiki.slembcke.net/main/published/Chipmunk).

At the moment, its an autogenerated ctypes binding + a modified version
of the vector2d cookbook-snippet from pygame.org at
(http://www.pygame.org/wiki/2DVectorClass)


HOW TO USE
There is no specific pymunk documentation yet except for this readme.
However, The Chipmunk docs should be more or less enough together with ctypes,
as pymunk is just a very low level ctypes binding at the moment.
Chipmunk documentation can be found here:
http://files.slembcke.net/chipmunk/chipmunk-docs.html


EXAMPLE
See demo1.py for an example of how easy it is to use! :)


DEPENDENCIES/REQUIREMENTS
* A windows-dll of Chipmunk (or a *nix-library if you are on *nix). See COMPILE
for compile-instructions. The dll/lib should be placed somewhere where pymunk
can find it. A safe bet should be in the same folder, at least on Windows ;)
pymunk uses the source from Chipmunk SVN revision 125.
* ctypes (included in python 2.5)


COMPILE
If you are on a platform other than windows, you will have to build Chipmunk
on your own. It should be no problem, the source is included in the
Chipmunk_src folder.

> gcc -O3 -std=gnu99 -ffast-math -c *.c
> gcc -shared -o libChipmunkPyEd.so *.o
or run build.sh (untested!) to compile.
The output should be placed somewhere pymunk can find it.


THE FUTURE
I have plans to do a more high-level/pythonic wrapper in the future, and even
started a little. But the pyweek library release stop is today(! or tomorrow?),
so the low-level stuff had to do for now.

Do not confuse this with the official Skellington for PyWeek - the package is based on Skellington 1.10, but adds extra functionality some might find useful but others might not need. It's not a game engine, but rather a nice package of generic code I've found useful in game projects in the past. It's also very much in the beta stages, so bugs should be expected. I might be testing it more thoroughly during the PyWeek warmup, but since the rules state any code must be released one month before the competition, I won't be making any more updates even for my own use until after PyWeek.

I don't like repeating myself, so head for the Skellington Plus project's home page for more complete information.

I've got a bunch of code that I don't care to write again, so I've documented it and called it a library:
http://www.meatengine.com


In part to test out the library, in part because it's been an idea I've wanted to experiment with, I wrote a silly little flight sim today.


Collide with the boxes in the shortest amount of time. The flight dynamics are pretty cheesy, but they kind of feel like a glider - the higher you go, the slower you get. There's no collision with the ground or with the hilariously festive sombreros.


There's quite a lot that's not in here, like a graceful entrance/exit, and OpenGL display lists. By my reading of the PyWeek rules, this amounts to published code over a month ahead of the contest, so I think you're free to reuse (and improve on) anything you find interesting.

I just noticed today that Barbie SeaHorse Adventures made it on to the Linux Format cover disk, well done TOBA!

Hi Chaps.

If you can, please download this file: skellington-1.9-TEST.tar.gz

Then run python run_game.py, (using python2.5) and a small demo should appear. This test game should run on linux, mac, and windows _from_source_, as it includes platform specific eggs where needed. It doesn't package any required DLLS, such as the sdl libs, or zlib, which are assumed to be on the host system. If I can work out how to add these into the skellington, I will do so.

If anyone is able to test the skellington with py2app or py2exe, that would be helpful!

I knew I should have only taken on a 10 week placement this summer (rather than 11!). Looks like I'm not going to be able to spend as much time on this entry as I did on my last... but I do have the benifit of experience this time!

See you all in a few weeks!