On 18 November 2011 03:00, Serge Stinckwich <serge.stinckwich@gmail.com> wrote:
On Fri, Nov 18, 2011 at 9:54 AM, Igor Stasenko <siguctua@gmail.com> wrote:
2011/11/18 Levente Uzonyi <leves@elte.hu>:
On Thu, 17 Nov 2011, Javier Pimás wrote:
We are advancing on making OpenGL work with NativeBoost right now. If you have to write an app that uses OpenGL now, I would strongly recommend you to use NBOpenGL. It's
I see the hype about NBOpenGL, but I don't see how is it better than the FFI based OpenGL implementation. Can someone shed some light on it?
The marshalling code is faster. It also deals nice with per-context feature availability (depending on context you created, some functions may be availabale, some not). And it contains a lot of extensions (over 3000 OpenGL functions), up to version 3.1 , because all functions are automatically generated from specs taken from official source. A future versions of OpenGL is easy to use: you just regenerate sources from specs.
Looks great Igor !
I'm a bit curious, how this generation is automatically done ? Could you use the same technique for others C librairies ?
Well, it parsing the spec files , which having special format and of course has nothing to do with other C libraries. There is a project i seen on last ESUG conference, which using GCC compiler to automatically generate bindings to libraries. But still do not think that you can avoid manual work: if you care about quality and comprehensiveness of the code, you have to get your hands dirty, involving creating different classes to represent various abstractions provided by library, add a convenience layer etc etc.
Regards,
-- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Matsuno Laboratory, Kyoto University, Japan (until 12/2011) http://www.mechatronics.me.kyoto-u.ac.jp/ Every DSL ends up being Smalltalk http://doesnotunderstand.org/
-- Best regards, Igor Stasenko.