just thought i should add a few comments.
i haven’t really used Magician that much, just downloaded it and wrote a few test applications. i didn’t like it, mostly because it’s not a direct wrapper around OGL.
i liked GL4Java better, it’s almost a direct wrapper (or interface, or whatever you want to call it) and is quite easy to get into.
after playing around for about two weeks in Java with OpenGL, i decided there HAD to be a memory leak SOMEWHERE, since after testrunning my apps about 50 times i had almost no free memory, and i never seemed to get that allocated memory back until i rebooted.
as we all know, Java has automatic GC (which is one of the reasons it might not yet be such a good idea to write an FPS engine in it, but also one of the reasons it’s so nice), so i knew my Java code wasn’t the problem.
GL4Java however, use native C code to call OpenGL etc. so i downloaded the source and took a look at it.
****. it’s fugly. it’s in dire need of some serious clean up. the best thing would probably be if it was rewritten. i would personally think twice before using it in a “serious” product.
still, Java is a damn fine language for testing new algorithms. it may not be a good idea to write your engine in it, but if you just want to try a new shadow algorithm, a new subdivision surface or whatever, Java is great.
just my two cents.