Nice! On Thursday, January 15, 2015 at 6:32:13 PM UTC+1, 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.
