there's a bunch of projects to work on here for pygame 1.9.
http://www.pygame.org/wiki/todo
Email back here if you feel like working on any of these things, or
something else for pygame 1.9 release.
cu,
- pygame.Camera - Video for windows version of
- Remove pyobjc dependency on macosx
- OSX Scrap clipboard
- pygame.Camera with quicktime on macosx
- fix up for py3k
- fastevent as default event module
- Keyword method signatures
- pygame.tests and pygame.examples
- Complete tests for all untested things.
- pygame.midi - include portmidi bindings
- Mark Numeric as depreciated, even more explicitly.
- New SDL 1.2.x release.
- pygame reloaded
On Sun, Jan 4, 2009 at 11:12 AM, Lenard Lindstrom <le...@telus.net> wrote:
> Hi,
>
> If the Pygame documents are to be included as part of the Pygame
> installation is there any reason to continue producing document bundles? And
> who is taking responsibility for modifying setup.py to add the documents and
> examples? If it is not on anyone's schedule the I will have a look at it.
>
> Lenard
>
> --
> Lenard Lindstrom
> <le...@telus.net>
>
>
Nirav
- Remove pyobjc dependency on macosx
cool :) I was hoping that you could get to it at some point. I also
have a long pygame todo list :)
However I did do a little more research... and found this link:
http://nehe.gamedev.net/data/lessons/lesson.asp?lesson=35
It uses video for windows to read from an avi, and write to a memory
buffer - and then send that to an opengl texture. So not exactly what
we need, but close I think.
If you want, we could meet on irc for a few hours one weekend to code
it together?
cheers,
Yeah, cherrypy is quite nice. I use it a lot myself... I think it
would be a good tool to use. Not so interested in using django.
I think the method would be to rewrite parts of the existing site,
trying to keep the existing functionality... writing tests for it as
we go.
Once the existing functionality has been implemented, then we can
start adding new stuff.
Alternatively, it might be possible to just replace parts of the php
based website to start with, as we change functionality. eg, we could
replace just the front page to start with, but leave the rest of the
pages php in the beginning.
cheers,
Indeed. It might be a good idea to try and remove as much of the
macosx.py that is there as possible... then try and add in what you
need until it is working.
cheers,
Indeed. It might be a good idea to try and remove as much of the
macosx.py that is there as possible... then try and add in what you
need until it is working.
--
Lenard Lindstrom
<le...@telus.net>
Yeah, I think it could go in as a branch. Or maybe in a separate svn
somewhere (like google code). Definitely a publically accessable
repository somewhere, so it's easy for people to contribute. Maybe
pygame.website ;)
It would be good to make use of pygame to make the pygame website too.
With the redesign of the site, maybe it's time to update the HTML in the
docs, make it strict XHTML. The style sheet would be compatible with
that of the new site.
--
Lenard Lindstrom
<le...@telus.net>