[java] Official OpenGL bindings

Looks like this is mainly for J2ME. But I know it''s not JOGL. It''s a separate thing altogether.

How soon do you think soon is? I get the feeling that there won''t be an official release for a while.

FFS, we thrash away writing a J2ME compatible binding and they go and do this. Why are they repeatedly ignoring the community?

Cas

long term maintainability and reliability, i guess

Oh thank god sun realized that the spawn of evil they call Java3D was bad idea ever since the beginning. I find it kind of funny how most sworn supporters of Java3D switch to OpenGL when sun gives its blessing to it.

I liked java3d but I am not going to stick with a dead api.

"... we should have such an empire for liberty as she has never surveyed since the creation ..."
Thomas Jefferson

i stick with java3d, i love it!
...and what you call dead, i call mature

quote:

---

Original post by Anonymous Poster
Would it be better for me to stay with Java3D or start picking up OpenGL

---

Hard to say accurately, although I think in the long term you''re probably better off with OpenGL.

quote:

---

What''s JOGL, how do I get it and does it work with NetBeans

---

JOGL is a new set of OpenGL bindings for Java. With it in place you can write Java programs that use OpenGL. It''s just a native library and a jar, should work just fine in netbeans. It''s at jogl.dev.java.net

Speaking of JOGL, does anyone have any links to documentation about actually installing the thing? I''ve downloaded all sorts of stuff for it, but unless I''m completely blind, I''m not finding anything that actually tells you how to install it, thus I can''t use it.

The Artist Formerly Known as CmndrM

http://chaos.webhop.org

quote:

---

Original post by Anonymous Poster
Would it be better for me to stay with Java3D or start picking up OpenGL

---

It depends of what you wanna do...
Do you want a driving car? => java3d (high level api)
Or a powerfull motor? => JOGL (low level api)
Or a more powerfull and known but complex motor?
=> c++/ogl (more complex but fine)

The choice depends on your priorities... That's all i can say.

EDIT:
PS: strife: doesn't it work when you simply add the 2 jars to your classpath libs in your IDE?

[edited by - misterx on August 6, 2003 2:19:45 PM]

Just put your jars in the jre/lib/ext directory. I am still hoping they open up java3d and put it ontop of jogl.

"... we should have such an empire for liberty as she has never surveyed since the creation ..."
Thomas Jefferson

Tortise:

That''s what I''m thinking.


misterX:

How about SDL? Where would that fit?

GKW:

Could that be where we''re heading.

You''''ve never seen anyone like me, and you''''ll never see anyone like me again!

openGL == only 3d
SDL == openGL + input, sound, 2D...
SDL is a "complete" tool-set using openGL (which is itself only for displaying 3d stuff).

quote:

---

Original post by Strife
Speaking of JOGL, does anyone have any links to documentation about actually installing the thing? I''ve downloaded all sorts of stuff for it, but unless I''m completely blind, I''m not finding anything that actually tells you how to install it, thus I can''t use it.

---

The .jar needs to be somewhere in your classpath, and the .dll in your path. An easy option is to drop the jar into javaSDK/lib/ext and the dll into javaSDK/bin. You can use the -DJava.library.path="somepath" (i think, something similar, its in the javadocs for the SDK) to set the path to the dll as a command line to the VM on startup which is handy if you need to set it in an IDE.

quote:

---

Original post by misterX
openGL == only 3d
SDL == openGL + input, sound, 2D...
SDL is a "complete" tool-set using openGL (which is itself only for displaying 3d stuff).

---

OpenGL is great for 2D. My very 2D game has benefited wonderfully from it.

SDL is the Simple Direct Media Layer. It''s an open source, cross platform library for developing multimedia apps (primarily games). It''s relatively high level and straightforward, and uses different underlying technologies depending on what OS its ran on (it uses DirectX under Windows and Xlib and other things under Linux for example). It''s written in C.

SDL has been designed to work well with OpenGL, but otherwise has nothing to do with it. OpenGL is not required for SDL.

quote:

---

Original post by OrangyTang
The .jar needs to be somewhere in your classpath, and the .dll in your path. An easy option is to drop the jar into javaSDK/lib/ext and the dll into javaSDK/bin. You can use the -DJava.library.path="somepath" (i think, something similar, its in the javadocs for the SDK) to set the path to the dll as a command line to the VM on startup which is handy if you need to set it in an IDE.

---

See, this is what I''m talking about. Would it have really taken them all that much effort to have a 1-line text file saying that you must do this? I''ve noticed a certain lack of documentation in some Java projects, and this is a perfect example. In some ways, Java is not very friendly to people who haven''t been around it too long, such as myself.

But, thanks for clearing that up. I''ll be able to mess around with it now.



The Artist Formerly Known as CmndrM

http://chaos.webhop.org

quote:

---

Original post by Strife
See, this is what I''m talking about. Would it have really taken them all that much effort to have a 1-line text file saying that you must do this? I''ve noticed a certain lack of documentation in some Java projects, and this is a perfect example. In some ways, Java is not very friendly to people who haven''t been around it too long, such as myself.

---

That''s an unfair attack. JOGL is a Java library. Knowledge of Java is rightfully assumed. It''s not an end user application. I''m not sure how someone can get to the point of using a 3rd party Java library (especially one that enables somethign as complex as OpenGL) but hasn''t yet learned about the classpath.

JOGL is also open source and volunteer driven. Like many, many other open source, volunteer driven projects (Java or not), documentation is not (yet) a priority. This is often par for the course, hell there are entire operating systems out there with little to no documentation.

quote:

---

Original post by tortoise
That''s an unfair attack.

---

I don''t think so... Read on...

quote:

---

JOGL is a Java library. Knowledge of Java is rightfully assumed. It''s not an end user application.

---

Uh, correct me if I''m wrong, but most applications are developed for SOME end user to use. There isn''t anything on the site about even how to install just the libs for use.

quote:

---

I''m not sure how someone can get to the point of using a 3rd party Java library (especially one that enables somethign as complex as OpenGL) but hasn''t yet learned about the classpath.

---

I know about classpath, but like I said, I haven''t been around the Java community for all that long, so I don''t think it''s unfair for me to not automatically know how to install something.

quote:

---

JOGL is also open source and volunteer driven. Like many, many other open source, volunteer driven projects (Java or not), documentation is not (yet) a priority.

---

True, but that doesn''t mean that this is a good thing. I certainly understand there being limited documentation for a relatively new project, but I usually expect ever project to have at least a short thing about installation, if it''s not inherently obvious (such as an installer or something like that).

The Artist Formerly Known as CmndrM

http://chaos.webhop.org

quote:

---

Original post by Strife

quote:

---

JOGL is a Java library. Knowledge of Java is rightfully assumed. It''s not an end user application.

---

Uh, correct me if I''m wrong, but most applications are developed for SOME end user to use. There isn''t anything on the site about even how to install just the libs for use.

---

JOGL is neither an application nor intended for an end user. A developer is not an end user. They''re called developers for a reason after all.

It''s not the JOGL team''s responsibility to teach you how to use a jar. Jars are 100% standard Java, and are absolutely ubiquitist with the language. In short they definitely qualify as "common knowledge". If you don''t yet have that knowledge, then it''s your responsibility to attain it, not a library author''s. Car dealers don''t teach you how to drive, supermarkets don''t teach you how to cook, and lumber yards don''t teach you how to build. They all make assumptions about their customers/users that are valid and even necessary.