r had nothing to do with speed of data
structures in python, but the way data was being consumed by opengl (and
my absolute newbieness at opengl ;-)
i hope this helps anyone who is learning similar material
Dave
On Sat, 11 Mar 2006 16:54:06 +1100, Steven D'Aprano
<[EMAIL PROTECTED]>
On Fri, 10 Mar 2006 21:06:27 -0600, Terry Hancock wrote:
> On Sat, 11 Mar 2006 13:12:30 +1100
> "Steven D'Aprano" <[EMAIL PROTECTED]> wrote:
>> On Fri, 10 Mar 2006 23:24:46 +1100, Dave wrote:
>> > Hi. I am learning PyOpenGL and I am working with a
>> > largish fixed scene composed of several tho
On Sat, 11 Mar 2006 13:12:30 +1100
"Steven D'Aprano" <[EMAIL PROTECTED]> wrote:
> On Fri, 10 Mar 2006 23:24:46 +1100, Dave wrote:
> > Hi. I am learning PyOpenGL and I am working with a
> > largish fixed scene composed of several thousand
> > GLtriangles. I plan to store the coords and normals i
On Fri, 10 Mar 2006 23:24:46 +1100, Dave wrote:
>
> Hi. I am learning PyOpenGL and I am working with a largish fixed scene
> composed of several thousand GLtriangles. I plan to store the coords and
> normals in a NumPy array.
>
> Is this the fastest solution in python? would i be significant
Dave wrote:
> Hi. I am learning PyOpenGL and I am working with a largish fixed scene
> composed of several thousand GLtriangles. I plan to store the coords and
> normals in a NumPy array.
>
> Is this the fastest solution in python? would i be significantly better
> off (timewise or otherwise)
