Bug 27 - convenient usage of jogl from a jdk perspective
Summary: convenient usage of jogl from a jdk perspective
Alias: None
Product: Jogl
Classification: JogAmp
Component: core (show other bugs)
Version: 1
Hardware: All all
: P3 normal
Assignee: Sven Gothel
URL: http://www.javagaming.org/cgi-bin/JGN...
Depends on:
Reported: 2003-07-20 05:27 CEST by Sven Gothel
Modified: 2015-09-27 03:15 CEST (History)
0 users

See Also:
SCM Refs:
Workaround: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Sven Gothel 2010-03-24 07:45:39 CET

---- Reported by thebohemian 2003-07-20 17:27:35 ----

On Java.net forums I once saw a post about adding methods like glColor
(java.awt.Color) to jogl. At the given thread I wanted to know about the latest 
opinion regarding this feature is and had given the following example of why such a 
feature should be usefull:

The current implementation needs the following code to get an AWT-Color-object 
to OpenGL:

float[] rgb = color.getRGBComponents(null); 
gl.glClearColor3f(rgb[0], rgb[1], rgb[2]); 

It would be possible to write a wrapper for such but it would speedup development 
with jogl in conjunction with the JDK to have convenient methods ready. There 
may be more situations like this.

I know that including such methods to the GL class might be a design break so one 
could implement as a helper class/package similar to the SwingUtilities.

---- Additional Comments From kbr 2005-01-28 18:11:20 ----

This won't be fixed in the core JOGL package. JOGL exposes pure OpenGL; wrapper
classes could be created to make it more convenient to use. The community would
have to contribute these utility classes.

--- Bug imported by sgothel@jausoft.com 2010-03-24 07:45 EDT  ---

This bug was previously known as _bug_ 27 at https://jogl.dev.java.net/bugs/show_bug.cgi?id=27