I guess I should qualify my statement (a bit more). Everything is relative... Implementing OpnGL 'within' the app should be relatively trivial (ie. it's much easier than writing your own 3d pipeline down to the point where you are rasterizing polygons - so, much easier than the code that's already there/written for example). But I don't know enough about Python (or the given interface/implementation) to know if that would be trivial (or even practical). My guess is that due to the amount of interface you need with the rest of the existing application (dials, mouse and such), it would be much better implemented within the app and not as a plugin/add-on.

Cinema4D Plugins (Home of Riptide, Riptide Pro, Undertow, Morph Mill, KyamaSlide and I/Ogre plugins) Poser products Freelance Modelling, Poser Rigging, UV-mapping work for hire.