Posted by Sven Gothel on Feb 10, 2014; 3:30pm
URL: https://forum.jogamp.org/Improvements-API-Support-tp4031509p4031532.html

On 02/10/2014 03:23 PM, gouessej [via jogamp] wrote:
> AWTTextureIO is quite convenient to use whereas AWTGLPixelBuffer requires tons
> of parameters. AWTTextureIO doesn't provide BufferedImage instances but there
> is already a RFE about that.

AWTGLPixelBuffer is most versatile, requiring only necessary params
as tested in the GLJPanel use-case.

AWTTextureIO: I would like to either keep-it or remove it.
.. no 'enhancing', since it is windowing toolkit depending,
where TextureIO is not.

IMHO we could add a TextureData ctor to AWTGLPixelBuffer
to allow convenient access.

Something like this ..

~Sven