Minor atomic jar issues

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Minor atomic jar issues

jouvieje
Here's some minor 'issues' I've found with the atomic jars:
 1) newt-core.jar contains all the classes of newt-event.jar. Is newt-event obsolete or newt-core contains events classes where it should not ?
 2) jogl-core contains the class com.jogamp.opengl.util.GLReadBufferUtil which depends on the texture classes of jogl-util.jar. It seems better to move GLReadBufferUtil to jogl-util jar.

I use one of the last build from here: gluegen_662-joal_425-jogl_957-jocl_776
Jérôme
Reply | Threaded
Open this post in threaded view
|

Re: Minor atomic jar issues

Sven Gothel
Administrator
On 04/13/2013 04:15 PM, jouvieje [via jogamp] wrote:
> Here's some minor 'issues' I've found with the atomic jars:
>  1) newt-core.jar contains all the classes of newt-event.jar. Is newt-event
> obsolete or newt-core contains events classes where it should not ?

newt-event.jar exist only is user like to deal w/ NEWT events w/o NEWT itself.
I don't really remember the use case right now, but it's there somehow :)

>  2) jogl-core contains the class com.jogamp.opengl.util.GLReadBufferUtil which
> depends on the texture classes of jogl-util.jar. It seems better to move
> GLReadBufferUtil to jogl-util jar.

Sounds reasonable, i.e. also for a package move of that util class
or it's cleanup. I will look at it. Thank you.

~Sven


signature.asc (911 bytes) Download Attachment