I don't see why not, a few things that could be done to make it better 
though:

   - Test the code against Pyglet 1.1 and not just 1.2.
   - Get a crucial bug fix 
   <https://code.google.com/p/pyeuclid/issues/detail?id=24> 
   of pyeuclid into the official repository.
   - Port the last 3 chapters of the Open.gl tutorial and not just the 
   first 5.

I can at least get on fixing that, but I don't know who's responsible for 
the docs.

On Saturday, January 10, 2015 at 9:48:05 AM UTC, Rob wrote:
>
> Nice. Maybe a good idea to add that to the Pyglet docs? 
>
> Rob
> On 9 Jan 2015 20:11, "01AutoMonkey" <[email protected] <javascript:>> 
> wrote:
>
>> I've ported the C++ and SFML http://open.gl/ tutorial sample code to 
>> Python and Pyglet, http://open.gl/ covers all the basics of modern 
>> OpenGL, you can find the translation/port at: 
>> https://github.com/01AutoMonkey/open.gl-tutorials-to-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] <javascript:>.
>> To post to this group, send email to [email protected] 
>> <javascript:>.
>> 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.

Reply via email to