Any help would be great :) As far as showstoppers, on my Windows 7 x64 Python 2.7.1 x32 system, I can't complete the trunk test suite, it crashes or hangs. We'll have to look into the frame rates as well. This of course is my starting point.
The rest of this a long rehash of http://code.google.com/p/pyglet/wiki/ReleaseSchedule with my opinions and comments. a lot of things seem to be functional improvements or fixes that may be small tasks. I apologize if there's committed code for some of these that just haven't been updated in the wiki. in the pyglet.media multithread changes section, I think most of those things should be done. * Pulse unknown timestamp -> None * Backward compat to dispatch_events * Backward compat source/player API * Discover cause of avbin segfaults on linux * Fix play/pause button in media_player example (not exactly a functional impairment, but sending out broken examples doesn't seem good) * Update docs s/ALSA/PulseAudio? * Document SourceGroup? and other new MT behaviour The following two from that section, maybe not. * Upgrade RIFF source. I don't know how important this is. * Example with many players. This would be a good thing to include but maybe we don't need to right away. Alex said this about the state of pyglet.media in his mail, http://groups.google.com/group/pyglet-users/msg/9733fab4436e635d : "In general, the media module needs far more testing and development for it to replace the existing 1.1 implementation; or reverted." I think we should evaluate the suitability of this module and see how much work it would be to finish versus reverting. Alex's statement implies to me that possibly the pyglet.media module is fairly independent of the other refactors, but I may be reading too much into it to come to that conclusion. Reverting would mean dropping PulseAudio for ALSA though, if I understand correctly. I'm afraid this is an area where I don't know a lot so I'll have to research and would appreciate advice. So on to pyglet.input * Document * Standard key and button names (not sure how much work this is yet) * Check multiple mouse/keyboard behaviour * DirectInput?: convert signed relative values (not sure how important this is) And maybe we don't need these for now; * Better joystick example * Better apple remote example next, pyglet.window/gl/canvas refactor * Fix documentation * Embedding example (Maybe Ben Powers sample would be appropriate and he would let us include it. http://groups.google.com/group/pyglet-users/browse_thread/thread/81c370dd78a1df13 ) pyglet.app, these all sound important to me. * Fix exit loop carnage * Fix clock/idle/sleep mess * Standardised wait/file objects * Some way to force another iteration (for Window.invalid) * Document MT features * Split user/system event loop for subclassing * Step method text/input: * Richard wants paragraph background colors / borders (This sounds like it would be nice to have, but I don't feel like it's a functional impairment) I also think it's very important to make sure we have rock solid timing across platforms that doesn't tax the CPU. If you made it this far, thanks heh -b On May 1, 10:35 pm, Phillip Nguyen <[email protected]> wrote: > On May 1, 8:03 pm, Ben Smith <[email protected]> wrote: > > > I think we need to agree to a plan for release that we can focus > > on.http://code.google.com/p/pyglet/wiki/ReleaseSchedulelookspretty good > > and maybe we should go with it, though I'm afraid I'm not an expert in > > some of the areas. We may want to add or remove some things from that > > list, as well, to open it more for discussion. I also haven't put as > > much time into pyglet as I intended after the 1.1.4 release, but I can > > spend a few hours a week working toward getting a release out. > > If you were able to coordinate the new release, I'd be willing to > provide help in any way that I can. I haven't dug into the 1.1.4 code > very much and don't fully understand all the differences between it > and 1.2. And I have very little experience working with any of the > platforms aside from OS X. It seems like the first big decision to > make is whether the next release will be 1.1.5 (based on the 1.1.4 > code) or 1.2 based on the trunk. > > The features that I think are important for the next release, whatever > it is called, are: > > 1. Addition of the input module for joystick support. > 2. Python 3 support. > 3. Integration of the cocoa code for continued OS X support in the > future. > 4. Bugfixes since 1.1.4 > > And not quite as important to me: > > 5. Screen resolution switching. > > It probably wouldn't be too hard to backport the joystick stuff and > the python 3 support, but trying backport everything else useful > that's in 1.2 seems like it would involve quite a lot of work. So I > think I am leaning towards just working on a 1.2 release. > > Are there are any showstopping problems in 1.2 currently? One thing > that I have noticed is that the reported frame rates do not appear to > be correct (or at any rate, they don't agree with 1.1.4) and I haven't > figured out what's going on there yet. The other thing I can think of > is that it needs a lot of documentation work. I agree that maybe we > should not worry too much at first about getting it working on every > possible combination of OS/graphics card/driver and just try to get > something out that people can use and report bugs on. If there's > anything in 1.2 that's too incomplete let's just strip it out for > now. > > The release schedule on the wiki looks like a good starting point, but > I think we should remove as much from that list as we can get away > with. So here are some questions for everyone else: > > 1. What are the features that we absolutely need in the next release? > 2. Are you having any major problems in using 1.2? -- 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.
