Hi.
Just a little note to say I've released cl-glfw-0.3 which now is able to work with cl-opengl (as well as with its own bindings, cl-glfw-opengl). So, maybe this option apart from SDL (with its custom application entry-point issues) and GLUT (for when you get stuck in a main loop) will be appealing to some.
The only caveat, at the moment, is that libglfw mostly only comes as statically linked libraries by default. We have been petitioning the glfw maintainers for dynamically loaded libraries by default to ease this problem somewhat.
Thanks for listening
</flamebait>
Ciao bill
Hello,
On 11/01/2008, William Robinson airbaggins@gmail.com wrote:
Just a little note to say I've released cl-glfw-0.3 which now is able to work with cl-opengl (as well as with its own bindings, cl-glfw-opengl).
In what ways does cl-glfw-opengl differ from cl-opengl?
So, maybe this option apart from SDL (with its custom application entry-point issues) and GLUT (for when you get stuck in a main loop) will be appealing to some.
This is very interesting. GLUT sucks a lot. Hopefully, GLFW's error handling is better and doesn't call exit() on errors like failing to open an X display, as GLUT does. It does seem very GLUT-like though.
cl-opengl-devel@common-lisp.net