On Mar 26, 2:30 pm, Alex Holkner <[email protected]> wrote: > We used to have community pages for this sort of thing,
Do you mean these? http://groups.google.com/group/pyglet-users/web > but we were > forced to close them due to spam. We don't have anything comparable at > the moment. Don't the googlecode wiki, and the google groups Pages above, have effective CAPTCHA systems? If not, could you individually approve people (revocably) to let them add things to places like that? > Actually in these cases it would be much simpler to expose the > platform's dialogs as additional pyglet features. That would be great... but if you don't have time to do that yourself, will you consider patches which do it for individual platforms, though with an API intended to be implementable on all platforms? But for community development purposes, rather than patches, letting these grow up as example code in some sort of experimental area, before being proposed for pyglet proper, seems best... if there's no better idea, how about a new googlecode project "pyglet-examples" for which you'd approve any reasonable person as a developer? > > I made some headway into refactoring the context, window and a new > > canvas class in pyglet-1.2dev (SVN trunk), but this is not in a > > releasable state. > > > Is this what I see in the svn trunk right now? I assumed that was > > essentially identical to the 1.1.3 release. > > The 1.1.3 release is from the pyglet-1.1-maintenance branch. The trunk > contains an ambitious refactoring of pyglet that attempts to retain > backward compatibility while supporting some new features that weren't > possible in the old design. It's unlikely to be released, however. Several points about that: - it probably means that my recent mail about breakage in experimental and contrib should be disregarded, or at least understood to only apply to the trunk - you ought to update (IMHO) the following text on http://www.pyglet.org/contribute.html: The subversion repository houses the source trunk, documentation, examples and development tools. You can browse the repository or check out a working copy using an SVN client: svn checkout http://pyglet.googlecode.com/svn/trunk/ pyglet to warn potential contributors (of bug reports, tests, and patches) that the trunk is experimental, and give the command for checking out the 1.1 maintenance branch as a preferred alternative for most of us (if I understand you correctly) - it doesn't seem like a good situation to allow to last. Was the refactoring misguided in hindsight, or is it just taking too long to finish, relative to the time you have? If the latter, is it feasible for some of your many users to help out? If it will be abandoned (or even just take forever to finish), it seems better to put the refactoring in a branch and make sure the trunk represents the intended continuing line of development. - Bruce (These are all just suggestions, given humbly, to avoid potential confusion.) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
