Hello, It's been long time since my last report!
I started working on pyglet about 5 months ago and although some progress has been made (we're below the 130 issues mark, wow!), there's a lot of work to do. I'm happy with the idea of more people using hg tip (the repo code) as it is where the fixes go and we're getting rid of the most frequent/annoying issues in 1.2 alpha1. Now that I've been working with the source code for some time I'm not as optimistic as I was 5 months ago regarding future releases :) but I'm still here with you! The main reasons for my despair are: - Documentation: the doc generation is kind of broken, docs re: migrating from pyglet 1.1.x are missing, the programming guide is not 100% in sync with 1.2 -- this is BAD - Missing code: there are some TODOs in the code, some of them are out of reach for me and my current skills (I can read and apply patches from contributors though) - Obscure bugs: there are some bugs related to platform code (ie. audio drivers problems in win, linux or mac) that I can't investigate or even reproduce We can improve the situation and, even pyglet 1.2 is not perfect (yet), I still think it's the way forward and eventually we will get there. I don't know when we will be ready for a new release, but I have to tackle the doc issues before we can think of getting anywhere close to a beta release. Any help will be appreciated! Regards, Juan -- jjm's home: http://www.usebox.net/jjm/ blackshell: http://blackshell.usebox.net/ -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pyglet-users. For more options, visit https://groups.google.com/groups/opt_out.
