On Mon, Apr 7, 2008 at 10:49 AM, Simon Wittber <[EMAIL PROTECTED]> wrote: > > I didn't finish anything for pyweek, though I think I produced some > code which other pyglet users may find useful. > > I've created C extension types for representing arrays of vectors, > with support for arithmetic operations on those arrays. This array > type does neat things like pre-allocation, dynamic resizing, memory > usage optimisizing, in-place math etc. > > I've also created a VertexArray type, which uses the above array type > to represent vertices, colors, texcoords and normals. This code is > fast enough to calculate the dynamics for rather massive particle > systems.
Why not just use Numpy? Or rather, what limitations did you find in such preexisting work that made you decide you had to write your own C-extension. > It can also do neat things like weld the vertices of an OBJ > vertex array, and produce an index into the array. > Welding? > There are some other goodies in there too, an OBJ loader with material > and texture support, a native Vector3 and a native OpenGL transform > class. Heh .. that makes 3 OBJ loaders for pyglet - the one in contrib is broken, though: http://hg.enterthefoo.com/Miru/file/d0c91d87c1ce/miru/tools/obj.py > These types are rather rigid and unflexible when compared to the > pyglet.graphics module, but when you have a need for speed, they will > prove useful. Really? Could you provide some numbers from performance tests you've done. -- \\\\\/\"/\\\\\\\\\\\ \\\\/ // //\/\\\\\\\ \\\/ \\// /\ \/\\\\ \\/ /\/ / /\/ /\ \\\ \/ / /\/ /\ /\\\ \\ / /\\\ /\\\ \\\\\/\ \/\\\\\/\\\\\/\\\\\\ d.p.s --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
