Anthony Briggs wrote: > Hi All, > > I've just started playing around with pyglet, trying to get it > working. See > http://groups.google.com/group/pyglet-users/web/sound-under-ubuntu-feisty > for the gory details - I almost made a fool of myself by submitting a > bug for it ;) > Looks like a bug to me! ALSA works in the current trunk (r1307) (there are some issues with attenuation, panning and synchronisation, but it should definitely make noise). pyglet no longer uses Gstreamer at all.
The current trunk also looks at the PYGLET_AUDIO environment variable which you can override to 'openal' as a friendlier alternative to hacking the source. > I've only just joined, so I'm still looking through the docs, etc. but > I'd like to put my hand up to do some of the documentation. I'm a > Python programmer, but no OpenGL/gaming guru, so I can probably help > out by going through the docs with a sort-of-newbie hat on, blundering > into things, if someone can point me in the right direction as far as > the right way to submit patches. > Cool! The docs online and in the distribution are not up-to-date. If you grab the SVN trunk you'll see: doc/programming_guide/*.txt The source files for the programming guide tools/gendoc.sh The top-level script for generating HTML and PDF documentation. Generating HTML documentation from the sources is easy, and only requires docutils (this is a good thing to do, as many doc bugs will be markup errors). Generating PDF is a nightmare and requires all sorts of extra programs, see tools/gendoc_pdf.py if you're interested. The API docs are docstrings within the pyglet source code. Note that pyglet has its own patched copy of epydoc which adds some extra markup syntax (but is mostly just restructured text). Patches against the documentation source (either a .txt or .py file) are best. Submit them via the tracker. > Failing that, I can take on any relatively obvious and/or small python > jobs, or have a look in the issue tracker and see if there's anything > I can fix. > I tend to fix the obvious and small jobs quickly; most of the issues on the tracker are Hard(TM). If you can get some more info on any of them, much kudos to you. There are a couple of documentation or packaging-related issues that should be tedious but straightforward to address. > Basically, what would be most useful for me to do? > Any of the above! Thanks in advance for your help :-) Alex. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en -~----------~----~----~----~------~----~------~--~---
