> in other words it is the browser engine's responsibility to thunk > down to opengl. it is *absolutely nothing* to do with pyopengl.
How does this work on pyjd then?
> in other words it is the browser engine's responsibility to thunk > down to opengl. it is *absolutely nothing* to do with pyopengl.
How does this work on pyjd then?