Re: replacing custom jni bindings for jogl
Posted by Sven Gothel on Jul 17, 2012; 6:17pm
URL: https://forum.jogamp.org/replacing-custom-jni-bindings-for-jogl-tp4025551p4025553.html
On 07/17/2012 06:20 PM, Sven Gothel wrote:
>
<snip/>
> You could do a [1] wrapper,
> [2] a custom binding requiring you to create your custom JOGL
> [3] or change your code .. which you don't like.
>
> Since we don't know how much your current binding looks like
> no statement can be given about the costs of [2].
>
<snip/>
>
> Even for [1] you could use GlueGen to create a wrapper,
> see how TraceGL* is created.
>
> Currently the naming solely depends on:
> - the header files
> - the build-in type explosion: arrays, NIO-buffer, ..
>
> However, I doubt it's more cost effective to do [1] or [2].
> Don't underestimate the costs of testing and fixing regressions.
> JOGL, as-is, is well tested on all supported platforms
> via our CI - have a look at our Jenkins build server.Further more, JOGL employs partial GL state tracking
allowing no-roundtrip queries, validation for correctness
and implementing certain features profile and platform agnostic.
The latter includes debug/trace, GLX/WGL/.. aliasing
and the currently in development API-transparent FBO offscreen rendering.
>
> [3] seems to be the most safe way, you can even try to use
> and automatic conversion w/ jackpotc, see 'jogl/tools/jackpotc'.
>
> (We haven't tested conversion using jackpotc for a long time though ..)
>
URL: https://forum.jogamp.org/replacing-custom-jni-bindings-for-jogl-tp4025551p4025553.html
On 07/17/2012 06:20 PM, Sven Gothel wrote:
>
<snip/>
> You could do a [1] wrapper,
> [2] a custom binding requiring you to create your custom JOGL
> [3] or change your code .. which you don't like.
>
> Since we don't know how much your current binding looks like
> no statement can be given about the costs of [2].
>
<snip/>
>
> Even for [1] you could use GlueGen to create a wrapper,
> see how TraceGL* is created.
>
> Currently the naming solely depends on:
> - the header files
> - the build-in type explosion: arrays, NIO-buffer, ..
>
> However, I doubt it's more cost effective to do [1] or [2].
> Don't underestimate the costs of testing and fixing regressions.
> JOGL, as-is, is well tested on all supported platforms
> via our CI - have a look at our Jenkins build server.
allowing no-roundtrip queries, validation for correctness
and implementing certain features profile and platform agnostic.
The latter includes debug/trace, GLX/WGL/.. aliasing
and the currently in development API-transparent FBO offscreen rendering.
>
> [3] seems to be the most safe way, you can even try to use
> and automatic conversion w/ jackpotc, see 'jogl/tools/jackpotc'.
>
> (We haven't tested conversion using jackpotc for a long time though ..)
>
signature.asc (910 bytes) | Free forum by Nabble | Edit this page |