On 02/10/2007, Alex Holkner <[EMAIL PROTECTED]> wrote: > > Anthony Briggs wrote: > > 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.
Ok, I've added in my comments/input on issue 149. My bug isn't quite the same, but it seems to be very similar, so it may have to same root cause. I've also reverted all of my hacking on the code - probably not a good idea if I'm going to be submitting bug reports or documentation :) > > 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). I've managed to run gendoc.sh - there are a few errors, mainly to do with 'missing information': Warning: No information available for pyglet.com.COMInterface's base ctypes.Structure Warning: No information available for pyglet.com.GUID's base ctypes.Structure Warning: No information available for pyglet.media.drivers.directsound.lib_dsound.D3DVECTOR's base ctypes.Structure There were a lot of errors in pyglet.media.drivers.directsound.lib_dsound. I compared with the alsa library, but there doesn't seem to be much overlap in terms of how the two drivers(?) are implemented, so hard to work out what's causing it. There are also some errors related to a missing ctypes.HRESULT: | In /home/anthony/pyglet/pyglet/pyglet/com.py: | Import failed (but source code parsing was successful). | Error: AttributeError: 'module' object has no attribute 'HRESULT' (line 112) Perhaps my ctypes is out of date? > Generating PDF is a nightmare and requires all sorts of > extra programs, see tools/gendoc_pdf.py if you're interested. I had a look, but I'll get the html version down pat before I go down that route. > 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. Ok, will do. > > 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). So I've noticed. > If you can get some more info on any of them, > much kudos to you. I'll have a look through, but don't hold your breath just yet ;) > There are a couple of documentation or > packaging-related issues that should be tedious but straightforward to > address. I'll take care of those first then, get the documentation building properly, and then work through the docs and see what I can add/fix/expand on. Anthony -- ----------------------------------------------------- HyPEraCtiVE? HeY, WhO aRE YoU cALliNg HypERaCtIve?! [EMAIL PROTECTED] ----------------------------------------------------- --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
