On Dec 11, 2007 12:14 AM, altern <[EMAIL PROTECTED]> wrote:
>
> Alex Holkner(e)k dio:
> > On Dec 10, 2007 10:51 PM, altern <[EMAIL PROTECTED]> wrote:
> >> hi
> >>
> >> I have some apps that I create using wxPython+PyOpenGL and some pygame
> >> sometimes. I am considering the possibility to switch to
> >> pyglet for several reasons (less dependencies, performance, simplicity).
> >
> > You're unlikely to get better performance with pyglet against PyOpenGL
> > 2 (as it's a C module, however pyglet is comparable in performance to
> > PyOpenGL 3, the last time I checked).
>
> So you mean it has ~ same performance as pyopengl3 ? I thought it was a
> bit faster because error checking or something like that.

The last time I checked (September last year) pyglet was around 3x
slower than PyOpenGL 2, and 2x faster than PyOpenGL-ctypes (now known
as PyOpenGL 3).  There's a good chance PyOpenGL has caught up since
then, but I haven't checked.

> > No support for using pyglet events/windows within a wxPython
> > application, however if you use wxPython to create the OpenGL context
> > you can trick pyglet into accepting that a context has been created,
> > and use pyglet as a replacement for PyOpenGL.
>
> so basically you access OpenGL calls via pyglet instead of PyOpenGL. Any
> advantages of using this method?

Not that I can think of, unless you're already using pyglet for
something else and want to avoid another dependency (assuming
PyOpenGL's bindings are up-to-date, again, I haven't checked
recently).

> > pyglet does not provide the overloaded function names; for example,
> > you must specify glVertex3f instead of just glVertex.  You must also
> > use ctypes arrays for all functions requiring arrays of data, whereas
> > PyOpenGL automatically handles conversions from strings and lists.
>
> how complex is dealing with this conversion? i dont never did anything
> similar.

It's just a recipe to follow, once you know the trick.  There have
been some recent threads on this mailing list with some complex
examples, or browse through any of the pyglet source code.

Alex.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pyglet-users" group.
To post to this group, send email to pyglet-users@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to