On May 3, 12:41 am, Jonathan Hartley <[email protected]> wrote: > On May 2, 3:35 am, Phillip Nguyen <[email protected]> wrote: > > > The other thing I can think of > > is that it needs a lot of documentation work. > > Is anyone in a good position to create a list of which areas need > documentation work? I could contribute to that, especially if there > was a more efficient way to get started than just searching through > the code for underdocumented bits. >
That would be great! >From going over the release schedule, the documentation areas seem to be pyglet.media, pyglet.input, the pyglet.media/gl/canvas refactor, and pyglet.app. Alex's mail suggests to me that a lot of this is may have been done since the release schedule was written. The mail says: "I don't believe the new public APIs have been documented in the Programming Guide, however the module and function-level documentation is fairly fleshed out.". And he mentions that there are some notes in the experimental directory that may help understand the design or limitations, though they're not to be considered documentation. > Also I can test on Windows, if that's useful. > It would be very useful! > Personally I'd like to support resolution switching, but I'm aware > it's a contraversial feature and I've contributed nada in the past, so > I shan't push it unless others think the feature needs a champion. I > didn't even know anyone had worked on this. > > Cheers, > > Jonathan If the 1.2 release is the way to go, looks like it's already in there :) -b -- 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.
