3D & Multimedia Across Platforms and Devices Using JOGL

Tuesday, 27 July | 4:00 PM – 6:00 PM | Los Angeles Convention Center Room 507

This session discusses the features, contributions, and future of
OpenGL, OpenCL, and OpenMax across devices and OS
exposed on top of Java using the JogAmp open-source libraries.

Sven Gothel
sgothel (at) jausoft.com

JogAmp

Until then, we work hard to have at least the following platforms working stable:

• linux-x86_64
• linux-x86
• window-x86_64
• window-x86
• macosx-x86_64
• macosx-x86

utilizing deployment methods

• Applet: applet-loader (fallback)
• Applet: JNLP (where available)
• Webstart: JNLP (where available)
• Pre-Installed JARs (static last-resort (mobile))

where Applet shall work with

• Firefox 3.x
• IE x.y
• Safari z.y

Further more a mobile device running JOGL on top of it shall be done, if time allows
and the ordered beagleboard, an OMAP 3530 device arrives.

Hope to see you there, if you are there

However, all our results will be visible as usual via jogamp.org.

However, with the great help of Michael Bien, we are close to something here:

• Main http://jogamp.org
• Wiki http://jogamp.org/wiki/
• SCM http://jogamp.org/git/
• Bugzilla http://jogamp.org/bugzilla/
• Our Forum/Mailinglist http://jogamp.762907.n3.nabble.com/
• Gathered News and Blogs http://jogamp.org/blog/
• Gathered Video Streams http://jogamp.org/stream/
• Automated build and test http://jogamp.org/chuck/
• The next JNLP base http://jogamp.org/deployment/webstart-next/

So again .. we are not dead yet

Our first intermediate-term goals are

• reproduce automated builds
• recreated all web resources on free server space
• receive a signature for the JAR files

Then we wish to continue with the actual development and deployment

Contributions are very welcome, and a new sponsor might be needed.

Further details about the project changes will be posted soon.

Thank you very much .. stay tuned.

Fixes: Swing/Java2D OpenGL usage, PBuffer usage

Adds: OpenGL 3.2 instantiation with WGL/GLX and incl. their extensions in GL3

Changes: Proper extension promotion/aliasing for OpenGL 3.0,3.1 and 3.2

The new repository homepages are:

http://kenai.com/projects/gluegen/
http://kenai.com/projects/jogl/

Create a local copy/branch of the git repository,
either anonymous:

git clone git://kenai.com/gluegen~gluegen-git gluegen
git clone git://kenai.com/jogl~jogl-git jogl
git clone git://kenai.com/jogl~jogl-demos-git jogl-demos

or via SSH and your user credential, so you can easily push back your
changes to the kenai server:

git clone ssh://username@git.kenai.com/gluegen~gluegen-git gluegen
git clone ssh://username@git.kenai.com/jogl~jogl-git jogl
git clone ssh://username@git.kenai.com/jogl~jogl-demos-git jogl-demos

TODO:

• autobuild git repository checkout (WIP)
• webpages / manual automatically checked-out by autobuild and hosted on download.java.net
• …

The general nightly download sites are

• http://download.java.net/media/jogl/builds/nightly/

Let’s assume we are in the test directory ‘test’, from which we operate from this point.

• Get http://download.java.net/media/jogl/builds/nightly/jogl-demos.zip
  Extract the archive, i.e. unzip jogl-demos.zip
• Get http://download.java.net/media/jogl/builds/nightly/jogl-2.0-pre-20090702-linux-amd64.zip
  In case we have build a reference implementation (RI) the substring ‘pre-yyyymmdd-’ will be dropped.
  Replace the version 2.0 with the latest available and the OS/arch linux-amd64 with your test platform.
  Extract the archive, ie unzip jogl-2.0-pre-20090702-linux-amd64.zip
  Create a symbolic link or rename the archive directory from jogl-2.0-pre-20090702-linux-amd64 to jogl.
• If you like to test the binding to NV’s Cg, download and install http://developer.nvidia.com/object/cg_download.html

We assume java is in your binary search path.

On X11/Unix and MaxOSX you can test the build as follows:

sh java-run-newt.sh demos.es2.RedSquare -GL2 -GL2 -GL2
sh java-run.sh demos.gears.Gears

and with debug output

sh java-dbg-newt.sh demos.es2.RedSquare -GL2 -GL2 -GL2
sh java-dbg.sh demos.gears.Gears


On Windows you shall be able to run:

java-win32.bat demos.es2.RedSquare -GL2 -GL2 -GL2
java-win32.bat demos.gears.Gears

and with debug output

java-win32-dbg.bat demos.es2.RedSquare -GL2 -GL2 -GL2
java-win32-dbg.bat demos.gears.Gears

The windows scripts are pretty simple and flat.

The magic unix scripts offer more features and can be used either in the autobuild environment or in your development one.

• setenv-jogl.sh <JOGL-PROFILE> [<jogl-build-dir>]
  Looks up and invokes profile.jogl, finds gluegen, sets the environment variables (CLASSPATH, LD_LIBRARY_PATH & PATH).
• jogl/etc/profile.jogl <JOGL-PROFILE> [<jogl-build-dir>]
  JOGL profiles are one of JOGL_ALL, JOGL_ES1_MIN, JOGL_ES1_MAX, JOGL_ES2_MIN, JOGL_ES2_MAX, JOGL_GL2ES12_MIN, JOGL_GL2ES12_MAX, JOGL_GL2_MIN, JOGL_GL2_MAX.
  Looks up the set of JAR files necessary to satisfy the chosen JOGL-PROFILE.

This allows you to test a specific environment, ie ES2 without GL2 and AWT, using JOGL_ES2_MIN.
For this case I would recommend the native ES2 implementation from imageon SDK_OGLES2_LINUX_PCEMULATION_2.02.22.0756.

• Test case
  • Source code, or reference to it
  • Invocation command-line
• Platform
  • OS & version
  • Architecture
  • Java version (java -version)
• JOGL Source/build versions
  • SVN revision and/or
  • Autobuild version (date/filename)
• Exceptions, stdout/stderr log file

If possible, please add the following system properties to enable DEBUG logging:
-Dnewt.debug=all -Dnativewindow.debug=all -Djogl.debug=all

For example:

java -Djava.awt.headless=true -Dnewt.debug=all -Dnativewindow.debug=all \
-Djogl.debug=all demos.es2.RedSquare 2>&1 | tee RedSquare.report.log

To test applets use the jcontrol panel or edit ~/.java/deployment.properties directly and

• Add JRE Arguments: -Djava.awt.headless=true -Dnewt.debug=all -Dnativewindow.debug=all -Djogl.debug=all
• Enable logging/trace
• Show the console window, or just use th latest log-file in ~/.java/deployment/log/

Newt is capable of handling multiple threads and windows.

For best compliance with the underlying OS, one shall create a window,

and handle it’s events within the same thread.

Below you see the invocation of the ES2 RedSquare jogl-demos utilizing multiple threads.

• Single thread (Unix, Win32)
  java -Djava.awt.headless=true demos.es2.RedSquare -GL2

• Single thread (MacOSX)
  java -XstartOnFirstThread -Djava.awt.headless=true demos.es2.RedSquare -GL2

• Multiple threads & windows (Unix, Win32)
  java -Djava.awt.headless=true demos.es2.RedSquare -GL2 -GL2 -GL2 -GL2

• Multiple threads & windows (Unix, Win32)
  java -XstartOnFirstThread -Djava.awt.headless=true com.sun.javafx.newt.util.MainThread demos.es2.RedSquare -GL2 -GL2 -GL2 -GL2

The serialization of the main Java class through com.sun.javafx.newt.util.MainThread

may be used for all platforms, since it only takes effect on MacOSX.

This allows you an almost platform independent invocation of your multithreaded Java applications.

On MacOSX, com.sun.javafx.newt.util.MainThread will occupy the main thread and
serializes all native window related tasks through it.
This mechanism is thread safe utilizes reentrant locking.

We will maintain the old JOGL variant under the version tag 1.x and the new one under 2.x, which development is in the SVN trunk.

OpenGL 1.5 – 3.0, OpenGL 3.1, OpenGL ES1.x and OpenGL 2.x profiles are supported.

The new API specification is available online.

Besides the traditional AWT Java Abstract Windowing Toolkit binding, the new JOGL architecture uses an abstract windowing toolkit binding specified with the new NativeWindow interface package. This allows users to bind any windowing interface to JOGL.

NEWT serves not only as an example of the abstraction, but also as a very simple, highly-available & high performance  implementation of the  new NativeWindow interface. It supports X11, OpenKode/EGL, MacOSX, Windows & AWT and features multithreading, fullscreen, multi-monitor and basic keyboard & mouse input.