Einar Forselv

I guess it should use `get_data` instead to support both 1.3 and 1.4. Pyglet 1.4 are just hiding some attributes. There is a lot of compatibility issues in 1.3.x that...

I might be looking into adding moderngl integration soon: https://github.com/moderngl/moderngl_window/issues/38 I don't think we should use the `opengl.ProgrammablePipelineRenderer`, but instead create a `ModernglRenderer` what would also contain its own programmable...

### Note about pyglet pyglet 2.x (under development) will move to 3.3 core contexts (might be 3.1 or 3.2, but 3.3 core is needed on OS X), so I'm guessing...

I just completed a working moderngl5 integration I will PR shortly. I can add a simple integration guide while I have all this info fresh in memory. Should not take...

The integration for moderngl 5.6 (moderngl-window 2.1): https://github.com/moderngl/moderngl-window/blob/2.1/moderngl_window/integrations/imgui.py I measured it's about twice as fast as the pyopengl one. Example: https://github.com/moderngl/moderngl-window/blob/2.1/examples/integration_imgui.py

You can easily hack it to work for moderngl 5.5.x if you remove/replace the scissoring. (`glScissor` support was added in 5.6). The `ProgrammablePipelineRenderer` is also more than reasonable for now...

I will PR it here very soon including a rough writeup on integrations. Just holding it back a bit because moderngl 5.6 is not out yet,

Colors should be in `object.vertices` and also interlaved in each material. You will have to look at the vertex format in the last case. See: https://github.com/pywavefront/PyWavefront/issues/87#issuecomment-464348971

Might be possible, but it's not something this library can support I think. Can you explain this more in detail?

Could be easier to use trimesh for this : https://github.com/mikedh/trimesh It does support inline visualization with tree.js. I have not used Google Colab much but I assume things working in...