PeterHarding at 10:00, 19 December 2024

2024-12-19T10:00:43Z

← Older revision		Revision as of 10:00, 19 December 2024
Line 1:		Line 1:
	This is a starting point		This is a starting point...

			Apparently Java 3D is a wrapper over OpenGL primatives. Reimplementing Impact would best implement its own wrapper layer.

			= Notes =



	<pre>		<pre>

PeterHarding at 09:54, 19 December 2024

2024-12-19T09:54:27Z

← Older revision		Revision as of 09:54, 19 December 2024
Line 1:		Line 1:
			This is a starting point

			<pre>

	JOGL provides a direct access to OpenGL functions. These functions are mostly low level draw functions, and you have to deal with the 'state machine' nature of OpenGL while you are programming.		JOGL provides a direct access to OpenGL functions. These functions are mostly low level draw functions, and you have to deal with the 'state machine' nature of OpenGL while you are programming.
Line 27:		Line 29:

	I use JOGL 2.0 (which is a low level Java binding for the OpenGL (and OpenGL-ES) API. I have recently helped someone to revive Java3D. Now, it relies only on JOGL 2.0 and it works better, especially on Mac OS X. You can find the source code here: https://github.com/hharrison/java3d-core		I use JOGL 2.0 (which is a low level Java binding for the OpenGL (and OpenGL-ES) API. I have recently helped someone to revive Java3D. Now, it relies only on JOGL 2.0 and it works better, especially on Mac OS X. You can find the source code here: https://github.com/hharrison/java3d-core

			</pre>

			[[Category:Java 3D]]
			[[Category:OpenGL]]

PeterHarding: Created page with " JOGL provides a direct access to OpenGL functions. These functions are mostly low level draw functions, and you have to deal with the 'state machine' nature of OpenGL while you are programming. Java3D abstracts this state machine. It allows you to define a tree of graphic objects, placed in a virtual scene, and rendered by a camera. The manipulation of these graphic objects is easier with such a tree structure. Then, it's up to Java3D to walk through this tree and cal..."

2024-12-19T09:53:28Z

Created page with " JOGL provides a direct access to OpenGL functions. These functions are mostly low level draw functions, and you have to deal with the 'state machine' nature of OpenGL while you are programming. Java3D abstracts this state machine. It allows you to define a tree of graphic objects, placed in a virtual scene, and rendered by a camera. The manipulation of these graphic objects is easier with such a tree structure. Then, it's up to Java3D to walk through this tree and cal..."

New page

JOGL provides a direct access to OpenGL functions. These functions are mostly low level draw functions, and you have to deal with the 'state machine' nature of OpenGL while you are programming.

Java3D abstracts this state machine. It allows you to define a tree of graphic objects, placed in a virtual scene, and rendered by a camera. The manipulation of these graphic objects is easier with such a tree structure. Then, it's up to Java3D to walk through this tree and call the OpenGL drawing functions.

This kind of library is called a scenegraph. There are many scenegraph libraries in java, some are implemented on top of JOGL. I don't have a list, but this keyword will help you in your research.

In our project, we tried 3 or 4 different libraries, but no one filled all our requirements. We ended writing our own scenegraph library (on top of JOGL).

jMonkeyEngine, Ardor3D, jPCT or Xith3D are much better options these days.

JOGL is indeed a good option. However, it's simply a wrapper library for OpenGL. That means you'll still have to do a lot of the legwork yourself. If you're comfortable with that and it suits your needs, it's not actually all that difficult. But it might be a bit time consuming and not knowing your current code-base I don't know how easy the transfer is.

You could however go for an engine which might use JOGL. Something like JMonkey Engine to purely name an example. If you look, you'll surely find some others. Have a look at those, their ease of use and their functionality to see what best suits you. They probably won't take all the work away from you, but they might make it a bit easier.

See also this Java 3D forum thread : Java3D viability questions...

https://forums.oracle.com/forums/thread.jspa?threadID=2150209&tstart=15

The official Java3D forum moved to another location since its "resurrection": forum.jogamp.org/java3d-f3728156.html –

I use JOGL 2.0 (which is a low level Java binding for the OpenGL (and OpenGL-ES) API. I have recently helped someone to revive Java3D. Now, it relies only on JOGL 2.0 and it works better, especially on Mac OS X. You can find the source code here: https://github.com/hharrison/java3d-core

Java 3D Notes - Revision history

PeterHarding at 10:00, 19 December 2024

PeterHarding at 09:54, 19 December 2024