At the moment, there's zero core active contributors. Adam has taken the
initiative to move the code to bitbucket, and I'd like to hear his thoughts
on the future of the codebase, but frankly as far as I'm concerned (and I'm
sure Alex would agree with me on this) the pyglet code is everyone's now,
and whoever is actively working on it can pretty much dictate where it
goes, and how it goes.
Yes, I pay for and operate the website, but I'd love for someone to migrate
it to rtfd.org so I all I have to do is pay the annual domain fee :)
Richard
On Thu Jan 22 2015 at 2:22:44 PM Leif Theden <[email protected]> wrote:
> Thanks for the support! Take what you need, or I can do pull requests
> from this code in the future. Windows support is quiet stable in my
> testing.
>
>
> On Thursday, January 15, 2015 at 11:32:13 AM UTC-6, Leif Theden wrote:
>>
>> Hey pyglet users,
>>
>> I was working on a few in-house graphical utilities for the company that
>> I work for and I wanted to use pyglet for it. We use Windows and I was
>> required to have my apps run on it, and I found that pyglet was pretty
>> awkward to use on on Windows and python 3.4. So, I spent a couple weeks
>> developing my in-house apps and maintaining a fork of pyglet. I'd just
>> like to announce it here in case any one is interested. I'm not trying to
>> break up the community or pull developers away, just offering my own
>> changes in case any one is interested. I have changes in the CHANGELOG
>> file. I've tried to follow the issues on the google code project page, and
>> I have submitted a patch for some issues there,
>>
>> Overall, my goals were: a better clock, python 3.4 support, windows
>> support, PEP8 compliance, and to make it workable for me. I also refactored
>> many of the tests to operate like modern unit tests, and mocked out some
>> things to make it fast. That is considered a WIP and still needs a lot of
>> work. Anyone is welcome to pull changes from it. If anyone would like to
>> discuss change to the clock, event loop, windows, etc. Feel free to
>> discuss it here.
>>
>> Cheers!
>>
>> https://github.com/bitcraft/pyglet/
>>
> --
> 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/d/optout.
>
--
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/d/optout.
