On Wed, Jan 11, 2012 at 9:34 AM, Lawson English-2 [via Smalltalk] <[email protected]> wrote: > [cross-posting this reply because it certainly seems relevant to both > Pharo and Squeak] > > > This seems to me to be roundabout, and will make sure that any Mac > version of OpenGL will be far slower than any Windows version. > > What I'm not understanding is how the current OpenGL libs can render > directly on the screen on a Mac, while the Igor's can't. The Croquet > OpenGL package appears to be grabbing something from the Baloon3D > plugin, I think. Has anyone looked at how THAT tells OpenGL libs to > render to the appropriate area on the system window? > > primCreateRenderer: flags x: x y: y w: w h: h > <primitive: 'primitiveCreateRendererFlags' module:'B3DAcceleratorPlugin'> > ^nil
Sure. Baloon3D is tightly tied to the VM, and is creating the OpenGL rendering context (and attaching it the NSWindow, etc) directly on the C side. Igor's approach is to do this all from the image side, and he just ran into the reality that you need to know the whole render stack on Mac OS X to do this (NSWindow, NSView, and OpenGL context). (I don't mean to put words into Igor's mouth, but his approach is consistent across issues and he has been up front about wanting to move things to the image.) Nick -- View this message in context: http://forum.world.st/NativeBoost-and-NBOpenGL-on-Mac-tp4278813p4286296.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
