🔒 Locked

java with OpenGl link

Started by prabu_sac Jan 30, 2004 at 2:10 AM 4 replies 400+ views

Original Post

Jan 30, 2004 at 2:10 AM

hi.. i want help in openGl...i don''t know how to link java with Open Gl. if anybody knows please reply... and i want to use satellite imagery(may be ortho image) so how to use java as GUI which module is best for this in java... i want to create component lirary in java then i have to use that one in open GL. please help me iam in urgent..

Aldacron

Jan 30, 2004 at 3:19 AM

Check out JOGL and the corresponding forum. Another option is LWJGL, but right now it does not support AWT/Swing.

xboxor

Jan 30, 2004 at 1:48 PM

Easy, just use C++ instead. Java sucks, and is slow, and completely defeats the purpose of using a hardware 3d API.

"Java is high performance. By high performance we mean adequate. By adequate we mean slow." - Mr. Bunny

teamonkey

Jan 30, 2004 at 4:48 PM

quote:
Original post by xboxor
Easy, just use C++ instead. Java sucks, and is slow, and completely defeats the purpose of using a hardware 3d API.

Actually, it''s pretty damn quick unless you use floating point stuff. And by really quick, I mean as fast as C++ with a good compiler. Floating-point does suck arse however, which does make it rather slow for OpenGL work. It doesn''t defeat the point of using hardware 3D though. It''s not going to be as fast as C++, but it''ll be fast enough.

Use LWJGL, as I said somewhere else.

justo

Jan 30, 2004 at 5:36 PM

quote:

Actually, it's pretty damn quick unless you use floating point stuff. And by really quick, I mean as fast as C++ with a good compiler. Floating-point does suck arse however, which does make it rather slow for OpenGL work. It doesn't defeat the point of using hardware 3D though. It's not going to be as fast as C++, but it'll be fast enough.

Use LWJGL, as I said somewhere else.

floating point slow in java? i see youve been working with j2me, but on a PC and with JIT compilation youre executing native code...just as fast as C++. there is still the VM overhead but with hotspot and JIT optimizations that a design-time compiler could never make get performed.

the only real drawback with java (**speed-wise**, mind you) right now is the trig problems made famous by that poorly done benchmark cited on slashdot...intel chips dont uphold ieee standards, so to keep standard across platforms the jvm is doing those in code right now...they need to get on that.

lwjgl and jogl are great (and fast), with great communities supporting them...check them out.

edit: fixed quote tags

[edited by - justo on January 30, 2004 6:36:43 PM]

teamonkey

Jan 31, 2004 at 8:19 AM

quote:
Original post by justo
the only real drawback with java (**speed-wise**, mind you) right now is the trig problems made famous by that poorly done benchmark cited on slashdot...intel chips dont uphold ieee standards, so to keep standard across platforms the jvm is doing those in code right now...they need to get on that.

Sorry, yeah. Trig is what I meant. Unfortunately trig''s really useful. Mind you, look-up tables and fixed point math aren''t hard to do. It doesn''t matter anyway. So what if Java''s maths is slower than C++? It''s more than fast enough for a decent game on today''s hardware.

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.