JogampWiki - User contributions [en]

SW Tracking Report Objectives for the release 2.6.0

2025-09-11T12:30:39Z

Sgothel:

List started on 2023-07-xx, concluding [[SW Tracking Report Objectives for the release 2.5.0|Release 2.5.0]] - '''Closed 2025-08-31''' - continuation @ [[SW Tracking Report Objectives for the release 2.7.0|Release 2.7.0]].

* [{{SERVER}}/gluegen/doc/JogAmpPlatforms-2.6.0.html Supported Platforms]
* [[Release 2.6.0|Release 2.6.0 Page]]
* [{{SERVER}}/bugzilla//show_bug.cgi?id=1512 Release 2.6.0 Bugzilla Entry]
* [{{SERVER}}/bugzilla/buglist.cgi?list_id=2822&query_format=advanced&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED&version=2.6.0 Complete Bugzilla List of Version 2.6.0]

= Features =

== Features to be classified for this release ==

<bugzilla>
{
"status":["UNCONFIRMED"],
"version":"2.6.0",
"cf_type":"FEATURE",
"include_fields":"id,product,component,priority,severity,status,summary"
}
</bugzilla>

== Features to implement for this release ==

<bugzilla>
{
"status":["IN_PROGRESS","CONFIRMED"],
"version":"2.6.0",
"cf_type":"FEATURE",
"include_fields":"id,product,component,priority,severity,status,summary"
}
</bugzilla>

== Features already implemented for this release ==

<bugzilla>
{
"status":["RESOLVED","VERIFIED"],
"version":"2.6.0",
"cf_type":"FEATURE",
"include_fields":"id,product,component,priority,severity,status,resolution,summary"
}
</bugzilla>

= Bugs =

== Bugs to be classified for this release ==

<bugzilla>
{
"status":["UNCONFIRMED"],
"version":"2.6.0",
"cf_type":["---", "DEFECT"],
"include_fields":"id,product,component,priority,severity,status,summary"
}
</bugzilla>

== Bugs to fix for this release ==

<bugzilla>
{
"status":["IN_PROGRESS","CONFIRMED"],
"version":"2.6.0",
"cf_type":["---", "DEFECT"],
"include_fields":"id,product,component,priority,severity,status,summary"
}
</bugzilla>

== Bugs already fixed for this release ==

<bugzilla>
{
"status":["RESOLVED","VERIFIED"],
"version":"2.6.0",
"cf_type":["---", "DEFECT"],
"include_fields":"id,product,component,priority,severity,status,resolution,summary"
}
</bugzilla>

Main Page

2025-09-11T08:40:40Z

Sgothel:

__NOTOC__
{| width="100%"
|-
|
<div>
Welcome to the [{{SERVER}}/ JogAmp] wiki. It documents JOGL, JOCL and JOAL, the cross-platform bindings to the OpenGL, OpenCL, and OpenAL APIs.

See [{{SERVER}}/cgit/jogl.git/about/#jogamp-history--milestones project history & milestones].
</div>
|-
|
{| style="width: 100%;"
|-
|style="vertical-align: top; padding: 5px; width: 50%"|<h3>Getting Started</h3>
*[[Downloading and installing JOGL|Downloading and installing]]
**[[Jogamp Versioning and Releases|Versioning and Releases]]
*[[Setting up a JogAmp project in your favorite IDE|Setting up a JogAmp project in your favorite IDE]]
*[[Jogamp SCM Repositories|Source Code Repositories]]
*[[SW Tracking|Tracking Reports]]
*[{{SERVER}}/chuck/ Build and Test Server]
|style="vertical-align: top; padding: 5px; width: 50%"|<h3>Community</h3>
*[[How to Contribute|Contribute to JogAmp]]
*[[How to Build|Build JogAmp]]
*[[Maintainer and Contacts]]
*[[Jogl FAQ#Bugreports & Testing|Report a bug]]
**[{{SERVER}}/bugzilla/ Bugzilla]
*[http://forum.jogamp.org/ Ask a question in the forum]
*[[chatroom|JogAmp IRC]]
|}
|-

{| style=" width: 100%;"
|-
|colspan="2"|<h1>JogAmp Modules</h1>
|-
|style="vertical-align: top; padding: 5px; width: 50%"|<h3>Roadmaps</h3>
* ''[[SW Tracking Report Feature Objectives Overview|Feature & Objectives]], [[SW Tracking Report Objectives undetermined release|tbd]], [[SW Tracking Report Objectives for the release 3.0.0|3.0.0]], [[SW Tracking Report Objectives for the release 2.7.0|2.7.0]]''
* '''[[SW Tracking Report Objectives for the release 2.6.0|2.6.0]] (last stable)''', [[SW Tracking Report Objectives for the release 2.5.0|2.5.0]], [[SW Tracking Report Objectives for the release 2.4.0|2.4.0]], [[SW Tracking Report Objectives for the release 2.3.2|2.3.2]], [[SW Tracking Report Objectives for the release 2.3.1|2.3.1]], [[SW Tracking Report Objectives for the release 2.3.0|2.3.0]]
* [[SW Tracking Report Objectives for the release 2.2.4|2.2.4]], [[SW Tracking Report Objectives for the release 2.2.3|2.2.3]], [[SW Tracking Report Objectives for the release 2.2.2|2.2.2]], [[SW Tracking Report Objectives for the release 2.2.1|2.2.1]], [[SW Tracking Report Objectives for the release 2.2.0|2.2.0]]
* [[SW Tracking Report Objectives for the release 2.1.5|2.1.5]], [[SW Tracking Report Objectives for the release 2.1.4|2.1.4]], [[SW Tracking Report Objectives for the release 2.1.3|2.1.3]], [[SW Tracking Report Objectives for the release 2.1.2|2.1.2]], [[SW Tracking Report Objectives for the release 2.1.1|2.1.1]], [[SW Tracking Report Objectives for the release 2.1.0|2.1.0]]
* [[SW Tracking Report Objectives for the release 2.0.2 of JOGL|2.0.2]]
|-

|style="vertical-align: top; padding: 5px; width: 50%"|<h3>JOGL</h3>
*[[Jogl Overview|Overview]] [ [{{SERVER}}/jogl/doc/Overview-OpenGL-Evolution-And-JOGL.html OpenGL Evolution & JOGL] ]
*[[Why Instance Design|Why Instance Design]]
*[[Jogl Tutorial|Tutorial]]
*[[Jogl FAQ|FAQ]]
*[{{SERVER}}/git/?p=jogl.git;a=blob;f=LICENSE.txt License]
*API Doc [ [{{SERVER}}/deployment/jogamp-next/javadoc/jogl/javadoc/ Public], Specs [ [{{SERVER}}/deployment/jogamp-next/javadoc/jogl/javadoc_nativewindow_spec/ Nativewindow], [{{SERVER}}/deployment/jogamp-next/javadoc/jogl/javadoc_jogl_spec/ JOGL] ] ]
*[[Jogl API Overview|API Overview]]
**[[GL Debug Output|GL Debug Output]]
*[{{SERVER}}/jogl/doc/HowToBuild.html How to Build JOGL]

|style="vertical-align: top; padding: 5px; width: 50%"|<h3>JOCL</h3>
*[[JOCL Overview|Overview]]
*[[JOCL Tutorial|Tutorial]]
*[[JOCL FAQ|FAQ]]
*[{{SERVER}}/git/?p=jocl.git;a=blob;f=LICENSE License]
*[{{SERVER}}/deployment/jogamp-next/javadoc/jocl/javadoc/ API Doc]
*[{{SERVER}}/jocl/doc/HowToBuild.html How to Build JOCL]
|-
|style="vertical-align: top; padding: 5px; width: 50%"|<h3>JOAL</h3>
*[[Joal Overview|Overview]]
*[[Joal Tutorial|Tutorial]]
*[[Joal FAQ|FAQ]]
*[{{SERVER}}/git/?p=joal.git;a=blob;f=LICENSE.txt License]
*API Doc [ [{{SERVER}}/deployment/jogamp-next/javadoc/joal/javadoc/ Public], [{{SERVER}}/deployment/jogamp-next/javadoc/joal/javadoc_dev/ Internal] ]

|style="vertical-align: top; padding: 5px; width: 50%"|<h3>GlueGen</h3>
* [[GlueGen_Wiki|Overview]]
* [{{SERVER}}/git/?p=gluegen.git;a=blob;f=LICENSE.txt License]
* [{{SERVER}}/deployment/jogamp-next/javadoc/gluegen/javadoc/ GlueGen Java™ API-Doc]
* [{{SERVER}}/gluegen/doc/GlueGen_Mapping.html GlueGen Native Data & Function Mapping]
* [{{SERVER}}/gluegen/doc/manual/ GlueGen Manual]
* [{{SERVER}}/gluegen/doc/HowToBuild.html How To Build]
|}

{| style=" width: 100%;"
|-
|colspan="2"|<h1>Related Projects</h1>
|-
|style="vertical-align: top; padding: 5px; width: 50%"|<h3>Java3D</h3>
*[[Java3D Overview|Overview]]
*[[Downloading and installing Java3D|Downloading and installing]]
*[[Java3D Tutorial|Tutorial]]
*[[Java3D API Documentation|API Documentation]]
*[[Java3D FAQ|FAQ]]
|style="vertical-align: top; padding: 5px; width: 50%"|<h3>Ji Gong</h3>
*[[Ji Gong Overview|Overview]]
*[[Ji Gong Motivation|Motivation]]
*[[Ji Gong FAQ|FAQ]]
|-
|style="vertical-align: top; padding: 5px; width: 50%"|<h3>Source Certification Contract (SCC)</h3>
*[[SCC Overview|Overview]]
*[{{SERVER}}/bugzilla/showdependencytree.cgi?id=1368&hide_resolved=0 Bugzilla Dependency Tree]
*[{{SERVER}}/bugzilla/show_bug.cgi?id=1368 Bugzilla Parent Entry]
*[[SCC FAQ|FAQ]]
|style="vertical-align: top; padding: 5px; width: 50%"|<h3>Ardor3D</h3>
*[[Ardor3D Overview|Overview]]
*[[Ardor3D Tutorial|Tutorial]]
*[http://jogamp.org/deployment/ardor3d/javadoc/ API Documentation]
*[[Ardor3D FAQ|FAQ]]
|}

Main Page

2025-09-11T08:29:13Z

Sgothel:

__NOTOC__
{| width="100%"
|-
|
<div>
Welcome to the [{{SERVER}}/ JogAmp] wiki. It documents JOGL, JOCL and JOAL, the cross-platform bindings to the OpenGL, OpenCL, and OpenAL APIs.
See [{{SERVER}}/cgit/jogl.git/about/#jogamp-history--milestones project history & milestones].
</div>
|-
|
{| style="width: 100%;"
|-
|style="vertical-align: top; padding: 5px; width: 50%"|<h3>Getting Started</h3>
*[[Downloading and installing JOGL|Downloading and installing]]
**[[Jogamp Versioning and Releases|Versioning and Releases]]
*[[Setting up a JogAmp project in your favorite IDE|Setting up a JogAmp project in your favorite IDE]]
*[[Jogamp SCM Repositories|Source Code Repositories]]
*[[SW Tracking|Tracking Reports]]
*[{{SERVER}}/chuck/ Build and Test Server]
|style="vertical-align: top; padding: 5px; width: 50%"|<h3>Community</h3>
*[[How to Contribute|Contribute to JogAmp]]
*[[How to Build|Build JogAmp]]
*[[Maintainer and Contacts]]
*[[Jogl FAQ#Bugreports & Testing|Report a bug]]
**[{{SERVER}}/bugzilla/ Bugzilla]
*[http://forum.jogamp.org/ Ask a question in the forum]
*[[chatroom|JogAmp IRC]]
|}
|-

{| style=" width: 100%;"
|-
|colspan="2"|<h1>JogAmp Modules</h1>
|-
|style="vertical-align: top; padding: 5px; width: 50%"|<h3>Roadmaps</h3>
* ''[[SW Tracking Report Feature Objectives Overview|Feature & Objectives]], [[SW Tracking Report Objectives undetermined release|tbd]], [[SW Tracking Report Objectives for the release 3.0.0|3.0.0]], [[SW Tracking Report Objectives for the release 2.7.0|2.7.0]]''
* '''[[SW Tracking Report Objectives for the release 2.6.0|2.6.0]] (last stable)''', [[SW Tracking Report Objectives for the release 2.5.0|2.5.0]], [[SW Tracking Report Objectives for the release 2.4.0|2.4.0]], [[SW Tracking Report Objectives for the release 2.3.2|2.3.2]], [[SW Tracking Report Objectives for the release 2.3.1|2.3.1]], [[SW Tracking Report Objectives for the release 2.3.0|2.3.0]]
* [[SW Tracking Report Objectives for the release 2.2.4|2.2.4]], [[SW Tracking Report Objectives for the release 2.2.3|2.2.3]], [[SW Tracking Report Objectives for the release 2.2.2|2.2.2]], [[SW Tracking Report Objectives for the release 2.2.1|2.2.1]], [[SW Tracking Report Objectives for the release 2.2.0|2.2.0]]
* [[SW Tracking Report Objectives for the release 2.1.5|2.1.5]], [[SW Tracking Report Objectives for the release 2.1.4|2.1.4]], [[SW Tracking Report Objectives for the release 2.1.3|2.1.3]], [[SW Tracking Report Objectives for the release 2.1.2|2.1.2]], [[SW Tracking Report Objectives for the release 2.1.1|2.1.1]], [[SW Tracking Report Objectives for the release 2.1.0|2.1.0]]
* [[SW Tracking Report Objectives for the release 2.0.2 of JOGL|2.0.2]]
|-

|style="vertical-align: top; padding: 5px; width: 50%"|<h3>JOGL</h3>
*[[Jogl Overview|Overview]] [ [{{SERVER}}/jogl/doc/Overview-OpenGL-Evolution-And-JOGL.html OpenGL Evolution & JOGL] ]
*[[Why Instance Design|Why Instance Design]]
*[[Jogl Tutorial|Tutorial]]
*[[Jogl FAQ|FAQ]]
*[{{SERVER}}/git/?p=jogl.git;a=blob;f=LICENSE.txt License]
*API Doc [ [{{SERVER}}/deployment/jogamp-next/javadoc/jogl/javadoc/ Public], Specs [ [{{SERVER}}/deployment/jogamp-next/javadoc/jogl/javadoc_nativewindow_spec/ Nativewindow], [{{SERVER}}/deployment/jogamp-next/javadoc/jogl/javadoc_jogl_spec/ JOGL] ] ]
*[[Jogl API Overview|API Overview]]
**[[GL Debug Output|GL Debug Output]]
*[{{SERVER}}/jogl/doc/HowToBuild.html How to Build JOGL]

|style="vertical-align: top; padding: 5px; width: 50%"|<h3>JOCL</h3>
*[[JOCL Overview|Overview]]
*[[JOCL Tutorial|Tutorial]]
*[[JOCL FAQ|FAQ]]
*[{{SERVER}}/git/?p=jocl.git;a=blob;f=LICENSE License]
*[{{SERVER}}/deployment/jogamp-next/javadoc/jocl/javadoc/ API Doc]
*[{{SERVER}}/jocl/doc/HowToBuild.html How to Build JOCL]
|-
|style="vertical-align: top; padding: 5px; width: 50%"|<h3>JOAL</h3>
*[[Joal Overview|Overview]]
*[[Joal Tutorial|Tutorial]]
*[[Joal FAQ|FAQ]]
*[{{SERVER}}/git/?p=joal.git;a=blob;f=LICENSE.txt License]
*API Doc [ [{{SERVER}}/deployment/jogamp-next/javadoc/joal/javadoc/ Public], [{{SERVER}}/deployment/jogamp-next/javadoc/joal/javadoc_dev/ Internal] ]

|style="vertical-align: top; padding: 5px; width: 50%"|<h3>GlueGen</h3>
* [[GlueGen_Wiki|Overview]]
* [{{SERVER}}/git/?p=gluegen.git;a=blob;f=LICENSE.txt License]
* [{{SERVER}}/deployment/jogamp-next/javadoc/gluegen/javadoc/ GlueGen Java™ API-Doc]
* [{{SERVER}}/gluegen/doc/GlueGen_Mapping.html GlueGen Native Data & Function Mapping]
* [{{SERVER}}/gluegen/doc/manual/ GlueGen Manual]
* [{{SERVER}}/gluegen/doc/HowToBuild.html How To Build]
|}

{| style=" width: 100%;"
|-
|colspan="2"|<h1>Related Projects</h1>
|-
|style="vertical-align: top; padding: 5px; width: 50%"|<h3>Java3D</h3>
*[[Java3D Overview|Overview]]
*[[Downloading and installing Java3D|Downloading and installing]]
*[[Java3D Tutorial|Tutorial]]
*[[Java3D API Documentation|API Documentation]]
*[[Java3D FAQ|FAQ]]
|style="vertical-align: top; padding: 5px; width: 50%"|<h3>Ji Gong</h3>
*[[Ji Gong Overview|Overview]]
*[[Ji Gong Motivation|Motivation]]
*[[Ji Gong FAQ|FAQ]]
|-
|style="vertical-align: top; padding: 5px; width: 50%"|<h3>Source Certification Contract (SCC)</h3>
*[[SCC Overview|Overview]]
*[{{SERVER}}/bugzilla/showdependencytree.cgi?id=1368&hide_resolved=0 Bugzilla Dependency Tree]
*[{{SERVER}}/bugzilla/show_bug.cgi?id=1368 Bugzilla Parent Entry]
*[[SCC FAQ|FAQ]]
|style="vertical-align: top; padding: 5px; width: 50%"|<h3>Ardor3D</h3>
*[[Ardor3D Overview|Overview]]
*[[Ardor3D Tutorial|Tutorial]]
*[http://jogamp.org/deployment/ardor3d/javadoc/ API Documentation]
*[[Ardor3D FAQ|FAQ]]
|}

WebAssembly (wasm) Target Platform

2025-09-11T06:17:45Z

Sgothel:

Extracted from [[SW Tracking Report Feature Objectives Overview|Feature & Objectives]].

= Overview =
See [https://jogamp.org/bugzilla//show_bug.cgi?id=1506 Bug 1506] describing this feature.

Since Java Applets are not more supported within browser or by OpenJDK for years,
it may seems feasible to evaluate the WebAssembly target running within e.g. web browser nowadays.

Since March '25 [https://2025.wasm.io/slides/the-future-of-write-once-run-anywhere-from-java-to-webassembly-wasmio25.pdf Recent GraalVM on JDK25 supports the wasm target].

An initial evaluation on small C++ projects using the emscripten front-end for LLVM's clang++ to wasm compiler, which supports many ported system libraries like SDL, OpenGL, .. has been undertaken successfully with variable results.
* [https://webassembly.org/ WebAssembly]
* [https://emscripten.org/ emscripten]
* [https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ gfxbox2 C++/wasm evaluation]
* Project [https://jausoft.com/cgit/gamp.git/about/ Gamp]

The wasm target is comparable to Java bytecode but the wasm virtual machine is not as performant, efficient or flexible as actual native code. The lack of hassle free native threads and native high-performance may remind one of the first JVM steps. The wasm code runs within a virtual machine like the JVM and additionally lacks of native binding capabilities.

Some limitations may be overcome, others are likely by design as it usually runs on the same browser virtual machine as the JavaScript companion. Compromises must be made on shared memory and native threads, cached non-local file I/O and socket communication - while other native features will simply never work, e.g. operating system ioctl-calls, etc.

Opening the door for any language to be compiled to a platform independent intermediate representation (IR) like Java’s bytecode suitable for a versatile runtime environment including its virtual machine is surely still desirable.

= Initial C++/wasm Evaluation =
[https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ Our little gfxbox2 games] compiled to [https://webassembly.org/ wasm] run about ~50% slower [https://jausoft.com/cgit/cs_class/gfxbox2.git/about/#online-webassembly-examples within a browser] than in native code, depending on coding strategy of our graphics (pixelmap vs SDL/OpenGL primitives).

The used [https://emscripten.org/ emscripten] frontend allowed us to use memory-growth, envelop files used in the wasm file, add cheap stack-overflow cockies and nullptr writes and so forth. Utilization of OpenGL ES via SDL2 was a breeze.

The underlying LLVM compiler did an excellent job and overall, the transition was easy and almost involved no code changes but dropping native thread (std::thread) usage.

The overall program structure had to be adapted to align to the single-thread main-loop workflow
and specific emscripten-javascript hooks added to allow seamless interaction.
All in all, nothing to be too afraid of and depending on the class of applications to be ported
to the browser these days, a feasible procedure.

= Project [https://jausoft.com/cgit/gamp.git/about/ Gamp] =
[https://jausoft.com/cgit/gamp.git/about/ Gamp] stands for Graphics, Audio, Multimedia and Processing, the same way as JogAmp, but natively plus using WebAssembly.

Gamp replicates JogAmp's experience natively via C++ in a condensed form, allowing a similar workflow on native targets and [https://jausoft.com/cgit/gamp.git/about/#online-webassembly-examples within the browser] via WebAssembly. Ironically this will bring back runs everywhere including the web.

Initial goal reimplementing [https://jausoft.com/blog/tag/graph_type_rendering/ Resolution independent NURBS curves rendering using programmable graphics pipeline (Graph)] has been completed.

Gamp uses [https://jausoft.com/cgit/jaulib.git/about/ jaulib] for general purpose functionality including linear algebra and geometry and builds upon initial wasm experience collected with [https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ gfxbox2].

= Java Support =
Java bytecode compiler to wasm including some ''runtime envelop''
* [https://github.com/google/j2cl/blob/master/docs/getting-started-j2wasm.md J2wasm] within [https://github.com/google/j2cl J2CL] emits naïve Wasm using the text format and it relies on Binaryen toolchain to assemble, link, and optimize
** [https://www.wingolog.org/pub/epfl-wasm-gc-feb-2024-slides.pdf 2024 Slides]
* [https://github.com/konsoletyper/teavm TeaVM] [https://teavm.org/docs/intro/overview.html overview]
* [https://github.com/i-net-software/JWebAssembly JWebAssembly] [https://github.com/i-net-software/JWebAssembly/wiki doc]
* [https://mirkosertic.github.io/Bytecoder/ Bytecoder]

Further interesting bits & pieces
* [https://openjdk.org/jeps/457 JEP 457: Class-File API ]
* [https://openjdk.org/projects/babylon/articles/linq Babylon]

== GraalVM ==
GraalVM on JDK 25 hosts wasm and supports ''wasm target'' for the wasm (browser) runtime.
* [https://2025.wasm.io/slides/the-future-of-write-once-run-anywhere-from-java-to-webassembly-wasmio25.pdf GraalVM Native Image supporting wasm as a target]
* [https://www.graalvm.org/latest/reference-manual/wasm/ GraalVM + wasm (WebAssembly runtime in Java)]
** with the help of emscripten
** [https://www.graalvm.org/22.0/reference-manual/native-image/JNI/ GraalVM + JNI]

[https://github.com/oracle/graal/issues/3391 Request for enhancement about wasm target in GraalVM].

= Java Browser Outlook =
So far the only question arises why reinventing the wheel once again? Dropping utilization of a well working JVM for the web had no technical reasoning.

However, in case no suitable wasm target for the Java bytecode and the Java Runtime pieces can be established, one might either want to also look into bringing back the JRE into the browser or painfully drop Java for C++, as the latter is already close to have acceptable (slower and limited) wasm target runtime properties.

WebAssembly (wasm) Target Platform

2025-09-11T06:12:41Z

Sgothel: /* GraalVM */

Extracted from [[SW Tracking Report Feature Objectives Overview|Feature & Objectives]].

= Overview =
See [https://jogamp.org/bugzilla//show_bug.cgi?id=1506 Bug 1506] describing this feature.

Since Java Applets are not more supported within browser or by OpenJDK for years,
it may seems feasible to evaluate the WebAssembly target running within e.g. web browser nowadays.

An initial evaluation on small C++ projects using the emscripten front-end for LLVM's clang++ to wasm compiler, which supports many ported system libraries like SDL, OpenGL, .. has been undertaken successfully with variable results.
* [https://webassembly.org/ WebAssembly]
* [https://emscripten.org/ emscripten]
* [https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ gfxbox2 C++/wasm evaluation]
* Project [https://jausoft.com/cgit/gamp.git/about/ Gamp]

The wasm target is comparable to Java bytecode but the wasm virtual machine is not as performant, efficient or flexible as actual native code. The lack of hassle free native threads and native high-performance may remind one of the first JVM steps. The wasm code runs within a virtual machine like the JVM and additionally lacks of native binding capabilities.

Some limitations may be overcome, others are likely by design as it usually runs on the same browser virtual machine as the JavaScript companion. Compromises must be made on shared memory and native threads, cached non-local file I/O and socket communication - while other native features will simply never work, e.g. operating system ioctl-calls, etc.

Opening the door for any language to be compiled to a platform independent intermediate representation (IR) like Java’s bytecode suitable for a versatile runtime environment including its virtual machine is surely still desirable.

= Initial C++/wasm Evaluation =
[https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ Our little gfxbox2 games] compiled to [https://webassembly.org/ wasm] run about ~50% slower [https://jausoft.com/cgit/cs_class/gfxbox2.git/about/#online-webassembly-examples within a browser] than in native code, depending on coding strategy of our graphics (pixelmap vs SDL/OpenGL primitives).

The used [https://emscripten.org/ emscripten] frontend allowed us to use memory-growth, envelop files used in the wasm file, add cheap stack-overflow cockies and nullptr writes and so forth. Utilization of OpenGL ES via SDL2 was a breeze.

The underlying LLVM compiler did an excellent job and overall, the transition was easy and almost involved no code changes but dropping native thread (std::thread) usage.

The overall program structure had to be adapted to align to the single-thread main-loop workflow
and specific emscripten-javascript hooks added to allow seamless interaction.
All in all, nothing to be too afraid of and depending on the class of applications to be ported
to the browser these days, a feasible procedure.

= Project [https://jausoft.com/cgit/gamp.git/about/ Gamp] =
[https://jausoft.com/cgit/gamp.git/about/ Gamp] stands for Graphics, Audio, Multimedia and Processing, the same way as JogAmp, but natively plus using WebAssembly.

Gamp replicates JogAmp's experience natively via C++ in a condensed form, allowing a similar workflow on native targets and [https://jausoft.com/cgit/gamp.git/about/#online-webassembly-examples within the browser] via WebAssembly. Ironically this will bring back runs everywhere including the web.

Initial goal reimplementing [https://jausoft.com/blog/tag/graph_type_rendering/ Resolution independent NURBS curves rendering using programmable graphics pipeline (Graph)] has been completed.

Gamp uses [https://jausoft.com/cgit/jaulib.git/about/ jaulib] for general purpose functionality including linear algebra and geometry and builds upon initial wasm experience collected with [https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ gfxbox2].

= Java Support =
Java bytecode compiler to wasm including some ''runtime envelop''
* [https://github.com/google/j2cl/blob/master/docs/getting-started-j2wasm.md J2wasm] within [https://github.com/google/j2cl J2CL] emits naïve Wasm using the text format and it relies on Binaryen toolchain to assemble, link, and optimize
** [https://www.wingolog.org/pub/epfl-wasm-gc-feb-2024-slides.pdf 2024 Slides]
* [https://github.com/konsoletyper/teavm TeaVM] [https://teavm.org/docs/intro/overview.html overview]
* [https://github.com/i-net-software/JWebAssembly JWebAssembly] [https://github.com/i-net-software/JWebAssembly/wiki doc]
* [https://mirkosertic.github.io/Bytecoder/ Bytecoder]

Further interesting bits & pieces
* [https://openjdk.org/jeps/457 JEP 457: Class-File API ]
* [https://openjdk.org/projects/babylon/articles/linq Babylon]

== GraalVM ==
GraalVM on JDK 25 hosts wasm and supports ''wasm target'' for the wasm (browser) runtime.
* [https://2025.wasm.io/slides/the-future-of-write-once-run-anywhere-from-java-to-webassembly-wasmio25.pdf GraalVM Native Image supporting wasm as a target]
* [https://www.graalvm.org/latest/reference-manual/wasm/ GraalVM + wasm (WebAssembly runtime in Java)]
** with the help of emscripten
** [https://www.graalvm.org/22.0/reference-manual/native-image/JNI/ GraalVM + JNI]

[https://github.com/oracle/graal/issues/3391 Request for enhancement about wasm target in GraalVM].

= Java Browser Outlook =
So far the only question arises why reinventing the wheel once again? Dropping utilization of a well working JVM for the web had no technical reasoning.

However, in case no suitable wasm target for the Java bytecode and the Java Runtime pieces can be established, one might either want to also look into bringing back the JRE into the browser or painfully drop Java for C++, as the latter is already close to have acceptable (slower and limited) wasm target runtime properties.

Setting up a JogAmp project in your favorite IDE

2025-09-08T18:18:02Z

Sgothel:

__TOC__

These instructions assume that you've created a project in your favorite IDE, and now you want your project to be able to use a JogAmp library like JOGL, JOCL, JOAL, or GlueGen. We use JOGL as an example below, but these instructions work equally well for any other JogAmp library.

= Download a JogAmp library =

If you haven't done so already, download and extract the JogAmp library you want to use. For example, to download and extract JOGL, see the instructions at [[Downloading and installing JOGL]].

To use a JogAmp library you'll do three things:

* Add its JAR files to the Java classpath
* Add its native libraries in one of two ways:
** Either place its native JAR files in the same directory as the library JAR files
** Or add its native library files(the <tt>.dll</tt>,<tt>.so</tt>, and <tt>.jnilib</tt> files) to the Java library path
* Optional: Associate the *-java-src.zip files with the corresponding JAR files.

Each IDE has a slightly different way to do these things, as we show below. Using the native JAR files is usually slightly easier than using the native library files directly, and native JARs make it possible for all platforms' libraries to coexist in one project, so this is the recommended method.

Please note that all JogAmp libraries depend on the GlueGen runtime libraries. These are included in every JogAmp library for convenience, but are only required once in the classpath and library path of your project.

See [[JogAmp JAR File Handling|JogAmp JAR File Handling]], for details on native JAR files and custom JAR bundling.

= Maven =

JogAmp supports Maven via its [https://jogamp.org/deployment/maven/ the Jogamp Mirror Repository].

From <tt>2.0-rc11</tt> to <tt>2.3.2</tt> and from <tt>2.6.0</tt>, packages are pushed to
[http://search.maven.org/#search|ga|1|jogamp Maven Central].

Please see the [[Maven]] page for details on how to use them in your projects.

= Gradle =

JogAmp supports Maven via its [https://jogamp.org/deployment/maven/ the Jogamp Mirror Repository].

From <tt>2.0-rc11</tt> to <tt>2.3.2</tt> and from <tt>2.6.0</tt>, packages are pushed to
[http://search.maven.org/#search|ga|1|jogamp Maven Central].

Please add the following code into build.gradle to use the version <tt>2.4.0</tt> from the Jogamp test repository:
<pre>
repositories {
maven { url "https://jogamp.org/deployment/maven" }
}

dependencies {
implementation 'org.jogamp.gluegen:gluegen-rt-main:2.6.0'
implementation 'org.jogamp.jogl:jogl-all-main:2.6.0'
}
</pre>

= Eclipse IDE project =

Probably the simplest way to use JOGL in an Eclipse project is to create another Eclipse project to contain the JOGL JARs, then make your project depend on this new JOGL project. In the example below, I include only the 64-bit Windows native JARs, but you can put native JARs for as many platforms as you wish together into the JOGL Eclipse project.

=== Create a JOGL project ===

* Put all the JOGL code JARs, native JARs for all platforms you wish to support, and source ZIP files in a directory called "JOGL" in your workspace directory.
* Click "File > New > Java Project". Type "JOGL" as the project name and click "Next".
[[File:Eclipse_project_setup_01_create_project.png|300px|thumb|none|Create JOGL project]]
* Remove the native JARs from the project, leaving only gluegen-rt.jar and jogl-all.jar.
[[File:Eclipse_project_setup_02_remove_native_JARs.png|300px|thumb|none|Remove native JARs]]
NOTE: The gluegen-rt-natives-*-*.jar and jogl-all-natives-*-*.jar are not
required in the classpath by JOGL, but are required by Eclipse to export
your project as a runnable JAR file.
* Expand the jogl-all and gluegen-rt JARs. For each of them, double-click "Source attachment", click "Workspace...", navigate to the corresponding <tt>*-java-src.zip</tt> file in the project, select it, click "OK", and click "OK" again to dismiss the "Source Attachment Configuration" dialog. The JARs should look like this when you're done:
[[File:Eclipse_project_setup_03_JARs_with_source_attached.png|300px|thumb|none|Attach source to JARs]]
* Click the "Order and Export" tab. Check both JOGL JARs, then click "Finish".
[[File:Eclipse_project_setup_04_order_and_export.png|300px|thumb|none|Exporting JOGL JARs]]

=== Add dependency on the JOGL project ===

* Right-click your project and click "Properties".
* Select the "Java Build Path" on the left, then click the "Projects" tab on the right.
* Click the "Add..." button, check "JOGL", and click "OK".
* Your dependent project should look like this. Click "OK" to dismiss the "Properties" dialog.
[[File:Eclipse_project_setup_05_project_dependency.png|300px|thumb|none|JOGL project dependency]]

That's it! Your project can now use the library.

= Eclipse IDE user library =

If you don't want to put JOGL in a separate Eclipse project, you can put it in a user library instead. The drawback to this is that the user library is defined in your .metadata directory and contains absolute paths, so it's hard to share with others. But for a non-shared project this works fine.

=== Create a user library ===

* Click "Window > Preferences", then select "Java > Build Path > User Libraries" on the left.
* Click the "New..." button, type "JOGL" for the library name, and click "OK".
[[File:Eclipse_setup_01_create_user_library.png|300px|thumb|none|Create user library]]
* Click the "Add JARs..." button, navigate to the directory where you've stored the JARs, select all the non-native JARs, then click "Open".
* If you're using native JAR files:
** Make sure the <tt>gluegen-rt-natives-*-*.jar</tt> and <tt>jogl-all-natives-*-*.jar</tt> files for each platform you want to run on are in the same directory as the other JAR files. The native JAR files don't need to be added to the classpath.
* Expand each non-native JAR in the list
** Double-click "Source attachment", type the module's source zip name, (e.g. <tt>jogl-java-src.zip</tt> for the JAR file <tt>jogl-all.jar</tt>), and click "OK".
** If you're using native library files:
*** Double-click "Native library location", type the directory where native library files are stored, and click "OK".
[[File:Eclipse_setup_02_set_native_library_locations.png|300px|thumb|none|Set native library locations]]
* Click "OK" to exit Preferences dialog.

=== Add the user library to your project's dependencies ===

* Right-click your project in the Package Explorer and click "Properties".
* Select "Java Build Path" and click the "Libraries" tab.
[[File:Eclipse_setup_03_add_library_to_project.png|300px|thumb|none|Add library to project]]
* Click "Add Library...", select "User Library", click "Next", check "JOGL", and click "Finish".
[[File:Eclipse_setup_04_add_JOGL_library_to_project.png|300px|thumb|none|Add JOGL library to project]]
* Click "OK" to dismiss the Properties dialog.

That's it! You can now use the library in your project.

= IntelliJ IDEA =
=== Add a library dependency to your project ===

* Click "File > Project Structure".
* Select "Modules" on the left, then click the "Dependencies" tab on the right.
* Click the "+" button on the right, then select "Library... > Java".
[[File:IntelliJ_setup_01_add_library.png|300px|thumb|none|Add library]]
* Navigate to the directory where you extracted the JARs, select it, and click "OK".
[[File:IntelliJ_setup_02_find_library.png|300px|thumb|none|Find library]]
* Click "OK" to dismiss the Configure Library dialog.
[[File:IntelliJ_setup_03_configure_library.png|300px|thumb|none|Configure library]]
* Click "OK" to dismiss the Project Structure dialog. The external libraries in your project should now look like this if you're using native JAR files:
[[File:IntelliJ_setup_04_external_library_native_JARs.png|300px|thumb|none|Native JARs]]
or like this if you're using native library files:
[[File:IntelliJ_setup_04_external_library.png|300px|thumb|none|Native library files]]

* If you're using native JAR files:
** Make sure the <tt>gluegen-rt-natives-*-*.jar</tt> and <tt>jogl-all-natives-*-*.jar</tt> files for each platform you want to run on are in the same directory as the other JAR files.
* Otherwise, if you're using native library files:
** Click "Run > Edit Configurations".
** Type <tt>-Djava.library.path=your/path/to/native/library/files</tt> in the "VM Parameters" box. Note that paths with spaces must be double-quoted on Windows.
[[File:IntelliJ_setup_05_run_configuration.png|300px|thumb|none|Edit run configuration]]
** Click "OK" to dismiss the Run/Debug Configurations dialog.

That's it! You can now use the library in your project.

= NetBeans IDE =
=== Create a library and add it to your project ===

* Right-click your project and click "Properties".
* Select "Libraries" on the left and click "Add Library...".
* Click the "Create" button, then type "JOGL" for the library name and click "OK".[[File:NetBeans_setup_01_create_library.png|300px|thumb|none|Create library]]
* Click "Add JAR/Folder...", then navigate to the directory you extracted the JAR files, select them and click "Add JAR/Folder".
* Click "OK" to dismiss the Customize Library dialog.
* Click "Add Library" to dismiss the Add Library dialog.[[File:NetBeans_setup_02_add_library.png|300px|thumb|none|Add library]]
* Click "OK" to dismiss the Project Properties dialog. The libraries in your project should look like this.[[File:NetBeans_setup_03_libraries_in_project.png|300px|thumb|none|Libraries in project]]

* If you're using native JAR files:
** Make sure the <tt>gluegen-rt-natives-*-*.jar</tt> and <tt>jogl-all-natives-*-*.jar</tt> files for each platform you want to run on are in the same directory as the other JAR files. The native JAR files don't need to be added to the classpath.
* Otherwise, if you're using native library files:
** Click "Run > Set Project Configuration > Customize...". Select "Run" on the left if it isn't selected already.
** Type <tt>-Djava.library.path=your/path/to/native/library/files</tt> in the "VM Options" box.
** NOTE: If the library path has spaces in it, you must put quotes around it (at least on Windows) or you may get an odd NoClassDefFoundError when you try to run.[[File:NetBeans_setup_04_native_library_path.png|300px|thumb|none|Native library path]]
** Click "OK" to dismiss the Project Properties dialog.

That's it! You can now use the library in your project.

= vi and other text editors =
=== Create your project with the editor of your choice ===
* For example, to open vi, simply type <tt>vi</tt> and press <return>.
* Type all your code, then save it.

=== Compile and run your project from the command line ===
* We assume your JOGL JAR files are in a directory called <tt>jar</tt>. If you're using native JARs, we assume they're also in the <tt>jar</tt> directory. If you're using native library files, we assume they're in a directory called <tt>lib</tt>.

* First compile your program. We assume all your code is in a single file called <tt>name/someone/MyProject.java</tt>.
** Windows: Type <tt>javac -classpath "jar\gluegen-rt.jar;jar\jogl-all.jar" name\someone\MyProject.java</tt>
** Linux/MacOS X: Type <tt>javac -classpath "jar/gluegen-rt.jar:jar/jogl-all.jar" name/someone/MyProject.java</tt>

* Then run your project. We assume your main class is <tt>name.someone.MyProject</tt>. If you're using native JARs:
** Windows: Type <tt>java -classpath "jar\gluegen-rt.jar;jar\jogl-all.jar;." name.someone.MyProject</tt>
** Linux/MacOS X: Type <tt>java -classpath "jar/gluegen-rt.jar:jar/jogl-all.jar:." name.someone.MyProject</tt>
* If you're using native library files:
** Windows: Type <tt>java -classpath "jar\gluegen-rt.jar;jar\jogl-all.jar;." -Djava.library.path=lib -Djogamp.gluegen.UseTempJarCache=false name.someone.MyProject</tt>
** Linux/MacOS X: Type <tt>java -classpath "jar/gluegen-rt.jar:jar/jogl-all.jar:." -Djava.library.path=lib -Djogamp.gluegen.UseTempJarCache=false name.someone.MyProject</tt>

That's it! You can now use the library in your project.

Maven

2025-09-08T18:17:35Z

Sgothel:

__TOC__

JogAmp supports Maven via its [https://jogamp.org/deployment/maven/ the Jogamp Mirror Repository].

From <tt>2.0-rc11</tt> to <tt>2.3.2</tt> and from <tt>2.6.0</tt>, packages are pushed to
[http://search.maven.org/#search|ga|1|jogamp Maven Central].

= Add dependencies on the correct packages =

If you don't know which packages you want, you almost certainly want to use the
<tt>jogl-all-main</tt> and <tt>gluegen-rt-main</tt> packages, as these automatically
set up the correct dependencies on the native jar files for all platforms.

As an example, if your project uses JOGL <tt>2.6.0</tt>:

<pre>
<dependencies>
<dependency>
<groupId>org.jogamp.gluegen</groupId>
<artifactId>gluegen-rt-main</artifactId>
<version>2.6.0</version>
</dependency>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>jogl-all-main</artifactId>
<version>2.6.0</version>
</dependency>
</dependencies>
</pre>

Maven will pull all of the dependencies the next time you attempt to build the project.

Additionally, for <tt>joal</tt> and <tt>jocl</tt> support:

<pre>
<dependencies>
<dependency>
<groupId>org.jogamp.jocl</groupId>
<artifactId>jocl-main</artifactId>
<version>2.6.0</version>
</dependency>
<dependency>
<groupId>org.jogamp.joal</groupId>
<artifactId>joal-main</artifactId>
<version>2.6.0</version>
</dependency>
</dependencies>
</pre>

An example project is available in the <tt>maven</tt> subdirectory of the <tt>jogl-demos</tt> project
[https://jogamp.org/git/?p=jogl-demos.git;a=tree;f=maven].

= Package details =

For each JogAmp project, there are essentially two packages published: One contains the main compiled
jar files and any associated native library jar files, and the other simply contains <i>dependencies</i>
on those files. Using <tt>jogl-all</tt> and <tt>jogl-all-main</tt> as the example, the <tt>jogl-all</tt>
package in the jogamp.org mirror repository:

https://jogamp.org/deployment/maven/org/jogamp/jogl/jogl-all/2.6.0/

Note that there are many native jar files attached to the main package. However, if you were to use
the following dependency in your own project:

<pre>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>jogl-all</artifactId>
<version>2.6.0</version>
</dependency>
</pre>

Maven would download <tt>jogl-all-2.6.0.jar</tt> but would completely ignore all of the other
native jar files. Why? The reason for this is that the native jar files are uploaded as extra artifacts
to the <tt>jogl-all</tt> package and are, in a manner of speaking, not really considered to be part of
the package where dependencies are concerned. The POM for the <tt>jogl-all-main</tt> package adds
explicit dependencies on all of the extra artifacts in the <tt>jogl-all</tt> package:

https://jogamp.org/deployment/maven/org/jogamp/jogl/jogl-all-main/2.6.0/jogl-all-main-2.6.0.pom

So, when you add a dependency on <tt>jogl-all-main</tt> in your own project, the native jar files of
<tt>jogl-all</tt> are brought in as transitive dependencies and everything works as expected.

= Available packages =

{|
|Group ID
|Artifact ID
|Since
|Description
|-
|org.jogamp.gluegen
|gluegen-rt-android
|2.0.2-rc12
|GlueGen runtime code and native libraries (Android)
|-
|org.jogamp.gluegen
|gluegen-rt-main
|2.0-rc11
|Meta-package for automatic dependency resolution for the GlueGen runtime
|-
|org.jogamp.gluegen
|gluegen-rt
|2.0-rc11
|GlueGen runtime code and native libraries
|-
|org.jogamp.gluegen
|gluegen
|2.0-rc11
|GlueGen non-runtime code and native libraries (and atomic jars)
|-
|org.jogamp.joal
|joal-main
|2.0-rc11
|Meta-package for automatic dependency resolution for JOAL
|-
|org.jogamp.joal
|joal
|2.0-rc11
|JOAL code and native libraries
|-
|org.jogamp.joal
|joal-android
|2.2.0
|JOAL Android runtime
|-
|org.jogamp.jocl
|jocl-main
|2.0-rc11
|Meta-package for automatic dependency resolution for JOCL
|-
|org.jogamp.jocl
|jocl-android
|2.2.0
|JOCL Android runtime
|-
|org.jogamp.jocl
|jocl
|2.0-rc11
|JOCL code and native libraries
|-
|org.jogamp.jogl
|jogl-all-main
|2.0-rc11
|Meta-package for automatic dependency resolution for JOGL
|-
|org.jogamp.jogl
|jogl-all
|2.0-rc11
|JOGL code and native libraries
|-
|org.jogamp.jogl
|jogl-android
|2.0.2-rc12
|JOGL code and native libraries (Android)
|-
|org.jogamp.jogl
|jogl-android-main
|2.2.0
|Meta-package for automatic dependency resolution for JOGL (Android)
|-
|org.jogamp.jogl
|jogl-mobile-main
|2.0-rc11
|Meta-package for automatic dependency resolution for JOGL (mobile)
|-
|org.jogamp.jogl
|jogl-mobile
|2.0-rc11
|JOGL mobile code and native libraries (without AWT)
|-
|org.jogamp.jogl
|jogl-noawt-main
|2.0-rc11
|Meta-package for automatic dependency resolution for JOGL (without AWT)
|-
|org.jogamp.jogl
|jogl-noawt
|2.0-rc11
|JOGL code and native libraries (without AWT)
|-
|org.jogamp.jogl
|jogl
|2.0.2
|JOGL atomic jar files
|-
|org.jogamp.jogl
|nativewindow
|2.0.2
|Native window drivers for NEWT (atomic jars)
|-
|org.jogamp.jogl
|nativewindow-main
|2.2.0
|Native window drivers for NEWT (atomic frontend)
|-
|org.jogamp.jogl
|newt
|2.0.2
|NEWT code and native libraries (atomic jars)
|-
|org.jogamp.jogl
|newt-main
|2.2.0
|NEWT code and native libraries (atomic frontend)
|-
|org.jogamp.jogl
|occulusvr
|2.2.0
|JOGL code and native libraries (Oculus VR atomic jar files)
|-
|}

= Atomic jar files (optional) =

The so-called <i>atomic</i> jar files are provided as attachments to the <tt>jogl</tt>, <tt>newt</tt>,
<tt>nativewindow</tt> and <tt>gluegen</tt> packages. As an example, to depend only on the Linux AMD64
native jar files, on X11, using only the core of <tt>jogl</tt> and the native window toolkit in your
own projects, use the following dependencies:

<pre>
<dependency>
<groupId>org.jogamp.gluegen-rt</groupId>
<artifactId>jogl</artifactId>
<version>2.6.0</version>
</dependency>
<dependency>
<groupId>org.jogamp.gluegen-rt</groupId>
<artifactId>jogl</artifactId>
<version>2.6.0</version>
<classifier>natives-linux-amd64</classifier>
</dependency>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>jogl</artifactId>
<version>2.6.0</version>
<classifier>core</classifier>
</dependency>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>jogl</artifactId>
<version>2.6.0</version>
<classifier>natives-linux-amd64</classifier>
</dependency>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>jogl</artifactId>
<version>2.6.0</version>
<classifier>os-x11</classifier>
</dependency>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>jogl</artifactId>
<version>2.6.0</version>
<classifier>os-x11</classifier>
</dependency>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>newt</artifactId>
<version>2.6.0</version>
<classifier>driver-x11</classifier>
</dependency>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>newt</artifactId>
<version>2.6.0</version>
<classifier>core</classifier>
</dependency>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>newt</artifactId>
<version>2.6.0</version>
<classifier>natives-linux-amd64</classifier>
</dependency>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>nativewindow</artifactId>
<version>2.6.0</version>
<classifier>core</classifier>
</dependency>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>nativewindow</artifactId>
<version>2.6.0</version>
<classifier>natives-linux-amd64</classifier>
</dependency>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>nativewindow</artifactId>
<version>2.6.0</version>
<classifier>driver-x11</classifier>
</dependency>
</pre>

Note that the choice of which atomic jars are required is really outside of the scope of this
documentation. It's recommended that you browse the packages in question to see which jar
files are available. It's <i>not</i> recommended to depend on platform-specific jar files
in the manner shown above unless there's an extremely good reason to do so; to do otherwise
harms portability for no good reason!

= The jogamp.org Mirror Repository =

Bleeding edge, experimental packages will continue to be made available from the
[https://jogamp.org/deployment/maven Jogamp Mirror Repository] and can be used
by adding a new profile in your <tt>~/.m2/settings.xml</tt> file that specifies this repository:

<pre>
<?xml version="1.0" encoding="UTF-8"?>
<settings
xmlns="http://maven.apache.org/SETTINGS/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
<profiles>
<profile>
<id>jogamp</id>
<repositories>
<repository>
<id>jogamp-remote</id>
<name>jogamp mirror</name>
<url>https://www.jogamp.org/deployment/maven/</url>
<layout>default</layout>
</repository>
</repositories>
</profile>
</profiles>
<activeProfiles>
<activeProfile>jogamp</activeProfile>
</activeProfiles>
</settings>
</pre>

This repository can be added into the POM file like in this [https://jogamp.org/cgit/jogl-demos.git/tree/maven/trivial-test/pom.xml very simple example].

Maven will then check this repository for packages in addition to Maven Central when resolving dependencies.

= Android =

There is a [[Maven_And_Android|separate page]] documenting one method of producing packages that work on both Android and ordinary
desktop Java.

= Producing a fat jar =

See [[JogAmp_JAR_File_Handling#Maven_Assembly_Plugin|JAR File Handling]].

Downloading and installing JOGL

2025-09-08T18:17:10Z

Sgothel:

Before you can build a project that uses JOGL [https://jogamp.org/wiki/index.php/Setting_up_a_JogAmp_project_in_your_favorite_IDE in your IDE or on the command line], you'll need to download and install the JOGL JAR files and native JARs or native library files (<tt>.dll</tt>/<tt>.so</tt>/<tt>.jnilib</tt> files).

You have a choice of JOGL versions to download. The [{{SERVER}}/deployment/jogamp-current/archive/ latest stable version] is the safest, but lags behind in features. The [{{SERVER}}/deployment/autobuilds/master/ latest automatic build] contains all checked-in code, but may be failing some tests.

See also [[Jogamp Versioning and Releases]] for versioning details.

= Downloading the latest stable version =

== Fat Jar for all platforms ==
(excluding Android)

* [{{SERVER}}/deployment/jogamp-current/fat/jogamp-fat.jar jogamp-fat.jar]
* Demo files
** [{{SERVER}}/deployment/jogamp-current/fat/jogl-demos.jar jogl-demos.jar]
** [{{SERVER}}/deployment/jogamp-current/fat/jogl-fonts-p0.jar jogl-fonts-p0.jar]

=== Using the fat jar ===
Download all three jar files into a folder as described above and launch e.g.
''java -cp jogamp-fat.jar:jogl-demos.jar com.jogamp.opengl.demos.graph.ui.UISceneDemo03''

== APK for Android ==
* See [[Android Packages]]
* [{{SERVER}}/deployment/jogamp-current/apk/ Latest APK files location]

User are encouraged to merge the ''<module>-all-android-<arch>.apk'' or jar files with their own application.

=== Testing a single fat APK ===
A fat demo APK ''jogl-demos-fat-android-${arch}.apk'' resides inside the [{{SERVER}}/deployment/jogamp-current/apk/ APK release folder] and can be directly installed and tested on your device w/ developer mode enabled.

== 7z all-in-one archive ==
Go to [{{SERVER}}/deployment/jogamp-current/archive/ this page] and download the all-in-one 7z archive file:

: [{{SERVER}}/deployment/jogamp-current/archive/jogamp-all-platforms.7z jogamp-all-platforms.7z]

=== Using the jogamp-all-platforms ===

After inflating the file with [http://www.7-zip.org/ 7zip], you will have the general directory structure:

<pre>
<jogamp-all-platforms>/
<jogamp-all-platforms>/etc/test.sh
<jogamp-all-platforms>/etc/test.bat
<jogamp-all-platforms>/etc/test_dbg.sh
<jogamp-all-platforms>/etc/test_dbg.bat
<jogamp-all-platforms>/jar/<module>.jar
<jogamp-all-platforms>/jar/<module>-natives-<os.and.arch>.jar
<jogamp-all-platforms>/lib/
<jogamp-all-platforms>/<module>-java-src.zip*
</pre>
Legend:
* [{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html#NativeJARFileNameConvention os.and.arch]
* module: gluegen, joal, jogl or jocl

Now you can '''test''' the ''archive'' as described
in [[Jogamp Versioning and Releases#Runtime Version Check|runtime version check]]
and [[Jogamp Versioning and Releases#Runtime Debug Logs|runtime debug test]].

If anything doesn't work as predicted, please follow our [[Jogl FAQ#Bugreports & Testing|bugreport guide]].

While keeping the above directory structure as-is, you can go ahead and
* add the non-native JAR files to your CLASSPATH (IDE, manual, ..)
* attach the java-source files to the non-native JAR files (IDE)

.. now you are set to start using JogAmp module in your project.

The above is detailed in [[Setting_up_a_JogAmp_project_in_your_favorite_IDE#Eclipse_IDE_project|Eclipse Project]]
and [[Setting_up_a_JogAmp_project_in_your_favorite_IDE#Eclipse_IDE_user_library|Eclipse User Library]].

== Maven ==

JogAmp supports Maven via its [https://jogamp.org/deployment/maven/ the Jogamp Mirror Repository].

From <tt>2.0-rc11</tt> to <tt>2.3.2</tt> and from <tt>2.6.0</tt>, packages are pushed to
[http://search.maven.org/#search|ga|1|jogamp Maven Central].

Please see the [[Maven]] page for details on how to use them in your projects.

== Gradle ==

JogAmp supports Maven via its [https://jogamp.org/deployment/maven/ the Jogamp Mirror Repository].

From <tt>2.0-rc11</tt> to <tt>2.3.2</tt> and from <tt>2.6.0</tt>, packages are pushed to
[http://search.maven.org/#search|ga|1|jogamp Maven Central].

Please add the following code into build.gradle to use the version <tt>2.4.0</tt> from the Jogamp test repository:
<pre>
repositories {
maven { url "https://jogamp.org/deployment/maven" }
}

dependencies {
implementation 'org.jogamp.gluegen:gluegen-rt-main:2.6.0'
implementation 'org.jogamp.jogl:jogl-all-main:2.6.0'
}
</pre>

= Downloading the latest aggregated autobuild =

Got to [{{SERVER}}/deployment/archive/master/?C=M;O=D this page] and navigate into the first folder,
which shall be the latest ''aggregated autobuild''.

Then navigate further down to '''archive''' and download the file '''jogamp-all-platforms.7z'''.

For example, on '''13-Mar-2013 20:19 CET''', the latest ''aggregated autobuild'' was:

[{{SERVER}}/deployment/archive/master/gluegen_646-joal_408-jogl_930-jocl_756/archive/jogamp-all-platforms.7z {{SERVER}}/deployment/archive/master/gluegen_646-joal_408-jogl_930-jocl_756/archive/jogamp-all-platforms.7z]

Now you can continue [[#Using the 7z jogamp-all-platforms archive|here]].

= Downloading the latest automatic build =

For the latest automatic build, we have to download gluegen and jogl separately.

First, go to [{{SERVER}}/deployment/autobuilds/master/?C=M;O=D this page] and click on the most recent <tt>gluegen-b*</tt> directory. Then download one of these files for each platform you're developing on:

: 32-bit Windows: <tt>gluegen-2.0-bvvv-20yymmdd-windows-i586.7z</tt>
: 64-bit Windows: <tt>gluegen-2.0-bvvv-20yymmdd-windows-amd64.7z</tt>
: 32/64-bit Mac OS X: <tt>gluegen-2.0-bvvv-20yymmdd-macosx-universal.7z</tt>
: 32-bit Linux: <tt>gluegen-2.0-bvvv-20yymmdd-linux-i586.7z</tt>
: 64-bit Linux: <tt>gluegen-2.0-bvvv-20yymmdd-linux-amd64.7z</tt>
: 32-bit Solaris: <tt>gluegen-2.0-bvvv-20yymmdd-solaris-i586.7z</tt>
: 64-bit Solaris: <tt>gluegen-2.0-bvvv-20yymmdd-solaris-amd64.7z</tt>

Then, go back to [{{SERVER}}/deployment/autobuilds/master/?C=M;O=D this page] and click on the most recent <tt>jogl-b*</tt> directory. Then download one of these files for each platform you're developing on:

: 32-bit Windows: <tt>jogl-2.0-bvvv-20yymmdd-windows-i586.7z</tt>
: 64-bit Windows: <tt>jogl-2.0-bvvv-20yymmdd-windows-amd64.7z</tt>
: 32/64-bit Mac OS X: <tt>jogl-2.0-bvvv-20yymmdd-macosx-universal.7z</tt>
: 32-bit Linux: <tt>jogl-2.0-bvvv-20yymmdd-linux-i586.7z</tt>
: 64-bit Linux: <tt>jogl-2.0-bvvv-20yymmdd-linux-amd64.7z</tt>
: 32-bit Solaris: <tt>jogl-2.0-bvvv-20yymmdd-solaris-i586.7z</tt>
: 64-bit Solaris: <tt>jogl-2.0-bvvv-20yymmdd-solaris-amd64.7z</tt>

Note that these automatic builds may not have passed all the regression tests. You can check the test results on the [https://jogamp.org/chuck/ build server] to make sure you're not downloading a broken build.

== Native JARs vs. native library files ==

JOGL uses native libraries to interface with each platform's OpenGL library. You can either download these native libraries wrapped up in JAR files (the "native JARs" option), or you can download them as separate <tt>.dll</tt>/<tt>.so</tt>/<tt>.jnilib</tt> files (the "native library files" option).

When using native JARs, JOGL automatically unzips the native JARs at startup into a temporary directory, then loads the resulting <tt>.dll</tt>/<tt>.so</tt>/<tt>.jnilib</tt> files from there. When using native library files, JOGL just loads them directly from where they sit, with no unzipping.

Using native JARs is usually easiest, since there are fewer files to manage and it allows different platforms' native library files to coexist in the same directory. Only use the native library files directly if you need fine control over native library file placement or if your app doesn't have permissions to create temporary directories.

See [[JogAmp JAR File Handling|JogAmp JAR File Handling]], for details on native JAR files and custom JAR bundling.

== Unzipping the files ==

Unzip all the downloaded files with [http://www.7-zip.org/ 7zip]. An unzipped file has this general directory structure:

<pre>
<archive>/
<archive>/jar/
<archive>/lib/
<archive>/<module>-java-src.zip*
</pre>

Now you may copy the required JARs out of each <tt>jar</tt> folder and the native library files (if you're using them) out of each <tt>lib</tt> folder. For a full desktop installation using native JARs, here are the files you need. Note that the native JAR names are different for each platform, so you can use some or all of the native JARs together to create a multi-platform installation.

{|cellpadding="4" cellspacing="0"
!align="left"|64-bit Windows
!align="left"|64-bit Linux
!align="left"|32/64-bit Mac
|-
|<tt>gluegen-rt.jar</tt>||<tt>gluegen-rt.jar</tt>||<tt>gluegen-rt.jar</tt>
|-
|<tt>jogl-all.jar</tt>||<tt>jogl-all.jar</tt>||<tt>jogl-all.jar</tt>
|-
|<tt>gluegen-java-src.zip</tt>||<tt>gluegen-java-src.zip</tt>||<tt>gluegen-java-src.zip</tt>
|-
|<tt>jogl-java-src.zip</tt>||<tt>jogl-java-src.zip</tt>||<tt>jogl-java-src.zip</tt>
|-
|<tt>gluegen-rt-natives-windows-amd64.jar</tt>||<tt>gluegen-rt-natives-linux-amd64.jar</tt>||<tt>gluegen-rt-natives-macosx-universal.jar</tt>
|-
|<tt>jogl-all-natives-windows-amd64.jar</tt>||<tt>jogl-all-natives-linux-amd64.jar</tt>||<tt>jogl-all-natives-macosx-universal.jar</tt>
|}
<br/>
{|cellpadding="4" cellspacing="0"
!align="left"|32-bit Windows
!align="left"|32-bit Linux
|-
|<tt>gluegen-rt.jar</tt>||<tt>gluegen-rt.jar</tt>
|-
|<tt>jogl-all.jar</tt>||<tt>jogl-all.jar</tt>||
|-
|<tt>gluegen-java-src.zip</tt>||<tt>gluegen-java-src.zip</tt>||
|-
|<tt>jogl-java-src.zip</tt>||<tt>jogl-java-src.zip</tt>||
|-
|<tt>gluegen-rt-natives-windows-i586.jar</tt>||<tt>gluegen-rt-natives-linux-i586.jar</tt>
|-
|<tt>jogl-all-natives-windows-i586.jar</tt>||<tt>jogl-all-natives-linux-i586.jar</tt>
|}

<br/>
For a full desktop installation using native library files, here are the files you need. Note that the native library files have the same names for 32-bit and 64-bit platforms, so 32-bit and 64-bit platforms can't coexist in one installation.
<br/>

{|cellpadding="4" cellspacing="0"
!align="left"|Windows
!align="left"|Linux
!align="left"|Mac
|-
|<tt>gluegen-rt.jar</tt>||<tt>gluegen-rt.jar</tt>||<tt>gluegen-rt.jar</tt>
|-
|<tt>jogl-all.jar</tt>||<tt>jogl-all.jar</tt>||<tt>jogl-all.jar</tt>
|-
|<tt>gluegen-java-src.zip</tt>||<tt>gluegen-java-src.zip</tt>||<tt>gluegen-java-src.zip</tt>
|-
|<tt>jogl-java-src.zip</tt>||<tt>jogl-java-src.zip</tt>||<tt>jogl-java-src.zip</tt>
|-
|<tt>gluegen-rt.dll</tt>||<tt>libgluegen-rt.so</tt>||<tt>libgluegen-rt.jnilib</tt>
|-
|<tt>jogl_desktop.dll</tt>||<tt>libjogl_desktop.so</tt>||<tt>libjogl_desktop.jnilib</tt>
|-
|<tt>nativewindow_awt.dll</tt>||<tt>libnativewindow_awt.so</tt>||<tt>libnativewindow_awt.jnilib</tt>
|-
|<tt>nativewindow_win32.dll</tt>||<tt>libnativewindow_x11.so</tt>||<tt>libnativewindow_macosx.jnilib</tt>
|-
|<tt>newt.dll</tt>||<tt>libnewt.so</tt>||<tt>libnewt.jnilib</tt>
|}

= Maven =
Alternatively, the Jogamp packages are available through Maven.

See the [[Setting_up_a_JogAmp_project_in_your_favorite_IDE#Maven|maven instructions]] for a guide to using Jogamp in
Maven projects.

= More information =

JogAmp follows a [[Jogamp_Versioning_and_Releases#Release_Classification|release scheme]],
which describes the following locations to download the 7z archives from:

* [{{SERVER}}/deployment/ Deployment Home]
** [{{SERVER}}/deployment/jogamp-current/archive/ Signed Release]
** [{{SERVER}}/deployment/jogamp-next/archive/ Signed Candidate]
** [{{SERVER}}/deployment/jogamp-next/v2.0-rc3archive/ Specific Version]

[{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html JOGL Deployment] describes the content of the 7z archive files.

These installations contain all of JOGL. If you want to remove parts you don't use, see [{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html JOGL Deployment] for more information.

Downloading and installing JOGL

2025-09-08T18:15:33Z

Sgothel:

Before you can build a project that uses JOGL [https://jogamp.org/wiki/index.php/Setting_up_a_JogAmp_project_in_your_favorite_IDE in your IDE or on the command line], you'll need to download and install the JOGL JAR files and native JARs or native library files (<tt>.dll</tt>/<tt>.so</tt>/<tt>.jnilib</tt> files).

You have a choice of JOGL versions to download. The [{{SERVER}}/deployment/jogamp-current/archive/ latest stable version] is the safest, but lags behind in features. The [{{SERVER}}/deployment/autobuilds/master/ latest automatic build] contains all checked-in code, but may be failing some tests.

See also [[Jogamp Versioning and Releases]] for versioning details.

= Downloading the latest stable version =

== Fat Jar for all platforms ==
(excluding Android)

* [{{SERVER}}/deployment/jogamp-current/fat/jogamp-fat.jar jogamp-fat.jar]
* Demo files
** [{{SERVER}}/deployment/jogamp-current/fat/jogl-demos.jar jogl-demos.jar]
** [{{SERVER}}/deployment/jogamp-current/fat/jogl-fonts-p0.jar jogl-fonts-p0.jar]

=== Using the fat jar ===
Download all three jar files into a folder as described above and launch e.g.
''java -cp jogamp-fat.jar:jogl-demos.jar com.jogamp.opengl.demos.graph.ui.UISceneDemo03''

== APK for Android ==
* See [[Android Packages]]
* [{{SERVER}}/deployment/jogamp-current/apk/ Latest APK files location]

User are encouraged to merge the ''<module>-all-android-<arch>.apk'' or jar files with their own application.

=== Testing a single fat APK ===
A fat demo APK ''jogl-demos-fat-android-${arch}.apk'' resides inside the [{{SERVER}}/deployment/jogamp-current/apk/ APK release folder] and can be directly installed and tested on your device w/ developer mode enabled.

== 7z all-in-one archive ==
Go to [{{SERVER}}/deployment/jogamp-current/archive/ this page] and download the all-in-one 7z archive file:

: [{{SERVER}}/deployment/jogamp-current/archive/jogamp-all-platforms.7z jogamp-all-platforms.7z]

=== Using the jogamp-all-platforms ===

After inflating the file with [http://www.7-zip.org/ 7zip], you will have the general directory structure:

<pre>
<jogamp-all-platforms>/
<jogamp-all-platforms>/etc/test.sh
<jogamp-all-platforms>/etc/test.bat
<jogamp-all-platforms>/etc/test_dbg.sh
<jogamp-all-platforms>/etc/test_dbg.bat
<jogamp-all-platforms>/jar/<module>.jar
<jogamp-all-platforms>/jar/<module>-natives-<os.and.arch>.jar
<jogamp-all-platforms>/lib/
<jogamp-all-platforms>/<module>-java-src.zip*
</pre>
Legend:
* [{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html#NativeJARFileNameConvention os.and.arch]
* module: gluegen, joal, jogl or jocl

Now you can '''test''' the ''archive'' as described
in [[Jogamp Versioning and Releases#Runtime Version Check|runtime version check]]
and [[Jogamp Versioning and Releases#Runtime Debug Logs|runtime debug test]].

If anything doesn't work as predicted, please follow our [[Jogl FAQ#Bugreports & Testing|bugreport guide]].

While keeping the above directory structure as-is, you can go ahead and
* add the non-native JAR files to your CLASSPATH (IDE, manual, ..)
* attach the java-source files to the non-native JAR files (IDE)

.. now you are set to start using JogAmp module in your project.

The above is detailed in [[Setting_up_a_JogAmp_project_in_your_favorite_IDE#Eclipse_IDE_project|Eclipse Project]]
and [[Setting_up_a_JogAmp_project_in_your_favorite_IDE#Eclipse_IDE_user_library|Eclipse User Library]].

== Maven ==

JogAmp supports for Maven via its [https://jogamp.org/deployment/maven/ the Jogamp Mirror Repository].

From <tt>2.0-rc11</tt> to <tt>2.3.2</tt> and from <tt>2.6.0</tt>, packages are pushed to
[http://search.maven.org/#search|ga|1|jogamp Maven Central].

Please see the [[Maven]] page for details on how to use them in your projects.

== Gradle ==

JogAmp supports for Maven via its [https://jogamp.org/deployment/maven/ the Jogamp Mirror Repository].

From <tt>2.0-rc11</tt> to <tt>2.3.2</tt> and from <tt>2.6.0</tt>, packages are pushed to
[http://search.maven.org/#search|ga|1|jogamp Maven Central].

Please add the following code into build.gradle to use the version <tt>2.4.0</tt> from the Jogamp test repository:
<pre>
repositories {
maven { url "https://jogamp.org/deployment/maven" }
}

dependencies {
implementation 'org.jogamp.gluegen:gluegen-rt-main:2.6.0'
implementation 'org.jogamp.jogl:jogl-all-main:2.6.0'
}
</pre>

= Downloading the latest aggregated autobuild =

Got to [{{SERVER}}/deployment/archive/master/?C=M;O=D this page] and navigate into the first folder,
which shall be the latest ''aggregated autobuild''.

Then navigate further down to '''archive''' and download the file '''jogamp-all-platforms.7z'''.

For example, on '''13-Mar-2013 20:19 CET''', the latest ''aggregated autobuild'' was:

[{{SERVER}}/deployment/archive/master/gluegen_646-joal_408-jogl_930-jocl_756/archive/jogamp-all-platforms.7z {{SERVER}}/deployment/archive/master/gluegen_646-joal_408-jogl_930-jocl_756/archive/jogamp-all-platforms.7z]

Now you can continue [[#Using the 7z jogamp-all-platforms archive|here]].

= Downloading the latest automatic build =

For the latest automatic build, we have to download gluegen and jogl separately.

First, go to [{{SERVER}}/deployment/autobuilds/master/?C=M;O=D this page] and click on the most recent <tt>gluegen-b*</tt> directory. Then download one of these files for each platform you're developing on:

: 32-bit Windows: <tt>gluegen-2.0-bvvv-20yymmdd-windows-i586.7z</tt>
: 64-bit Windows: <tt>gluegen-2.0-bvvv-20yymmdd-windows-amd64.7z</tt>
: 32/64-bit Mac OS X: <tt>gluegen-2.0-bvvv-20yymmdd-macosx-universal.7z</tt>
: 32-bit Linux: <tt>gluegen-2.0-bvvv-20yymmdd-linux-i586.7z</tt>
: 64-bit Linux: <tt>gluegen-2.0-bvvv-20yymmdd-linux-amd64.7z</tt>
: 32-bit Solaris: <tt>gluegen-2.0-bvvv-20yymmdd-solaris-i586.7z</tt>
: 64-bit Solaris: <tt>gluegen-2.0-bvvv-20yymmdd-solaris-amd64.7z</tt>

Then, go back to [{{SERVER}}/deployment/autobuilds/master/?C=M;O=D this page] and click on the most recent <tt>jogl-b*</tt> directory. Then download one of these files for each platform you're developing on:

: 32-bit Windows: <tt>jogl-2.0-bvvv-20yymmdd-windows-i586.7z</tt>
: 64-bit Windows: <tt>jogl-2.0-bvvv-20yymmdd-windows-amd64.7z</tt>
: 32/64-bit Mac OS X: <tt>jogl-2.0-bvvv-20yymmdd-macosx-universal.7z</tt>
: 32-bit Linux: <tt>jogl-2.0-bvvv-20yymmdd-linux-i586.7z</tt>
: 64-bit Linux: <tt>jogl-2.0-bvvv-20yymmdd-linux-amd64.7z</tt>
: 32-bit Solaris: <tt>jogl-2.0-bvvv-20yymmdd-solaris-i586.7z</tt>
: 64-bit Solaris: <tt>jogl-2.0-bvvv-20yymmdd-solaris-amd64.7z</tt>

Note that these automatic builds may not have passed all the regression tests. You can check the test results on the [https://jogamp.org/chuck/ build server] to make sure you're not downloading a broken build.

== Native JARs vs. native library files ==

JOGL uses native libraries to interface with each platform's OpenGL library. You can either download these native libraries wrapped up in JAR files (the "native JARs" option), or you can download them as separate <tt>.dll</tt>/<tt>.so</tt>/<tt>.jnilib</tt> files (the "native library files" option).

When using native JARs, JOGL automatically unzips the native JARs at startup into a temporary directory, then loads the resulting <tt>.dll</tt>/<tt>.so</tt>/<tt>.jnilib</tt> files from there. When using native library files, JOGL just loads them directly from where they sit, with no unzipping.

Using native JARs is usually easiest, since there are fewer files to manage and it allows different platforms' native library files to coexist in the same directory. Only use the native library files directly if you need fine control over native library file placement or if your app doesn't have permissions to create temporary directories.

See [[JogAmp JAR File Handling|JogAmp JAR File Handling]], for details on native JAR files and custom JAR bundling.

== Unzipping the files ==

Unzip all the downloaded files with [http://www.7-zip.org/ 7zip]. An unzipped file has this general directory structure:

<pre>
<archive>/
<archive>/jar/
<archive>/lib/
<archive>/<module>-java-src.zip*
</pre>

Now you may copy the required JARs out of each <tt>jar</tt> folder and the native library files (if you're using them) out of each <tt>lib</tt> folder. For a full desktop installation using native JARs, here are the files you need. Note that the native JAR names are different for each platform, so you can use some or all of the native JARs together to create a multi-platform installation.

{|cellpadding="4" cellspacing="0"
!align="left"|64-bit Windows
!align="left"|64-bit Linux
!align="left"|32/64-bit Mac
|-
|<tt>gluegen-rt.jar</tt>||<tt>gluegen-rt.jar</tt>||<tt>gluegen-rt.jar</tt>
|-
|<tt>jogl-all.jar</tt>||<tt>jogl-all.jar</tt>||<tt>jogl-all.jar</tt>
|-
|<tt>gluegen-java-src.zip</tt>||<tt>gluegen-java-src.zip</tt>||<tt>gluegen-java-src.zip</tt>
|-
|<tt>jogl-java-src.zip</tt>||<tt>jogl-java-src.zip</tt>||<tt>jogl-java-src.zip</tt>
|-
|<tt>gluegen-rt-natives-windows-amd64.jar</tt>||<tt>gluegen-rt-natives-linux-amd64.jar</tt>||<tt>gluegen-rt-natives-macosx-universal.jar</tt>
|-
|<tt>jogl-all-natives-windows-amd64.jar</tt>||<tt>jogl-all-natives-linux-amd64.jar</tt>||<tt>jogl-all-natives-macosx-universal.jar</tt>
|}
<br/>
{|cellpadding="4" cellspacing="0"
!align="left"|32-bit Windows
!align="left"|32-bit Linux
|-
|<tt>gluegen-rt.jar</tt>||<tt>gluegen-rt.jar</tt>
|-
|<tt>jogl-all.jar</tt>||<tt>jogl-all.jar</tt>||
|-
|<tt>gluegen-java-src.zip</tt>||<tt>gluegen-java-src.zip</tt>||
|-
|<tt>jogl-java-src.zip</tt>||<tt>jogl-java-src.zip</tt>||
|-
|<tt>gluegen-rt-natives-windows-i586.jar</tt>||<tt>gluegen-rt-natives-linux-i586.jar</tt>
|-
|<tt>jogl-all-natives-windows-i586.jar</tt>||<tt>jogl-all-natives-linux-i586.jar</tt>
|}

<br/>
For a full desktop installation using native library files, here are the files you need. Note that the native library files have the same names for 32-bit and 64-bit platforms, so 32-bit and 64-bit platforms can't coexist in one installation.
<br/>

{|cellpadding="4" cellspacing="0"
!align="left"|Windows
!align="left"|Linux
!align="left"|Mac
|-
|<tt>gluegen-rt.jar</tt>||<tt>gluegen-rt.jar</tt>||<tt>gluegen-rt.jar</tt>
|-
|<tt>jogl-all.jar</tt>||<tt>jogl-all.jar</tt>||<tt>jogl-all.jar</tt>
|-
|<tt>gluegen-java-src.zip</tt>||<tt>gluegen-java-src.zip</tt>||<tt>gluegen-java-src.zip</tt>
|-
|<tt>jogl-java-src.zip</tt>||<tt>jogl-java-src.zip</tt>||<tt>jogl-java-src.zip</tt>
|-
|<tt>gluegen-rt.dll</tt>||<tt>libgluegen-rt.so</tt>||<tt>libgluegen-rt.jnilib</tt>
|-
|<tt>jogl_desktop.dll</tt>||<tt>libjogl_desktop.so</tt>||<tt>libjogl_desktop.jnilib</tt>
|-
|<tt>nativewindow_awt.dll</tt>||<tt>libnativewindow_awt.so</tt>||<tt>libnativewindow_awt.jnilib</tt>
|-
|<tt>nativewindow_win32.dll</tt>||<tt>libnativewindow_x11.so</tt>||<tt>libnativewindow_macosx.jnilib</tt>
|-
|<tt>newt.dll</tt>||<tt>libnewt.so</tt>||<tt>libnewt.jnilib</tt>
|}

= Maven =
Alternatively, the Jogamp packages are available through Maven.

See the [[Setting_up_a_JogAmp_project_in_your_favorite_IDE#Maven|maven instructions]] for a guide to using Jogamp in
Maven projects.

= More information =

JogAmp follows a [[Jogamp_Versioning_and_Releases#Release_Classification|release scheme]],
which describes the following locations to download the 7z archives from:

* [{{SERVER}}/deployment/ Deployment Home]
** [{{SERVER}}/deployment/jogamp-current/archive/ Signed Release]
** [{{SERVER}}/deployment/jogamp-next/archive/ Signed Candidate]
** [{{SERVER}}/deployment/jogamp-next/v2.0-rc3archive/ Specific Version]

[{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html JOGL Deployment] describes the content of the 7z archive files.

These installations contain all of JOGL. If you want to remove parts you don't use, see [{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html JOGL Deployment] for more information.

Setting up a JogAmp project in your favorite IDE

2025-09-08T18:11:07Z

Sgothel:

__TOC__

These instructions assume that you've created a project in your favorite IDE, and now you want your project to be able to use a JogAmp library like JOGL, JOCL, JOAL, or GlueGen. We use JOGL as an example below, but these instructions work equally well for any other JogAmp library.

= Download a JogAmp library =

If you haven't done so already, download and extract the JogAmp library you want to use. For example, to download and extract JOGL, see the instructions at [[Downloading and installing JOGL]].

To use a JogAmp library you'll do three things:

* Add its JAR files to the Java classpath
* Add its native libraries in one of two ways:
** Either place its native JAR files in the same directory as the library JAR files
** Or add its native library files(the <tt>.dll</tt>,<tt>.so</tt>, and <tt>.jnilib</tt> files) to the Java library path
* Optional: Associate the *-java-src.zip files with the corresponding JAR files.

Each IDE has a slightly different way to do these things, as we show below. Using the native JAR files is usually slightly easier than using the native library files directly, and native JARs make it possible for all platforms' libraries to coexist in one project, so this is the recommended method.

Please note that all JogAmp libraries depend on the GlueGen runtime libraries. These are included in every JogAmp library for convenience, but are only required once in the classpath and library path of your project.

See [[JogAmp JAR File Handling|JogAmp JAR File Handling]], for details on native JAR files and custom JAR bundling.

= Maven =

JogAmp supports for Maven via its [https://jogamp.org/deployment/maven/ the Jogamp Mirror Repository].

From <tt>2.0-rc11</tt> to <tt>2.3.2</tt> and from <tt>2.6.0</tt>, packages are pushed to
[http://search.maven.org/#search|ga|1|jogamp Maven Central].

Please see the [[Maven]] page for details on how to use them in your projects.

= Gradle =

JogAmp supports for Maven via its [https://jogamp.org/deployment/maven/ the Jogamp Mirror Repository].

From <tt>2.0-rc11</tt> to <tt>2.3.2</tt> and from <tt>2.6.0</tt>, packages are pushed to
[http://search.maven.org/#search|ga|1|jogamp Maven Central].

Please add the following code into build.gradle to use the version <tt>2.4.0</tt> from the Jogamp test repository:
<pre>
repositories {
maven { url "https://jogamp.org/deployment/maven" }
}

dependencies {
implementation 'org.jogamp.gluegen:gluegen-rt-main:2.6.0'
implementation 'org.jogamp.jogl:jogl-all-main:2.6.0'
}
</pre>

= Eclipse IDE project =

Probably the simplest way to use JOGL in an Eclipse project is to create another Eclipse project to contain the JOGL JARs, then make your project depend on this new JOGL project. In the example below, I include only the 64-bit Windows native JARs, but you can put native JARs for as many platforms as you wish together into the JOGL Eclipse project.

=== Create a JOGL project ===

* Put all the JOGL code JARs, native JARs for all platforms you wish to support, and source ZIP files in a directory called "JOGL" in your workspace directory.
* Click "File > New > Java Project". Type "JOGL" as the project name and click "Next".
[[File:Eclipse_project_setup_01_create_project.png|300px|thumb|none|Create JOGL project]]
* Remove the native JARs from the project, leaving only gluegen-rt.jar and jogl-all.jar.
[[File:Eclipse_project_setup_02_remove_native_JARs.png|300px|thumb|none|Remove native JARs]]
NOTE: The gluegen-rt-natives-*-*.jar and jogl-all-natives-*-*.jar are not
required in the classpath by JOGL, but are required by Eclipse to export
your project as a runnable JAR file.
* Expand the jogl-all and gluegen-rt JARs. For each of them, double-click "Source attachment", click "Workspace...", navigate to the corresponding <tt>*-java-src.zip</tt> file in the project, select it, click "OK", and click "OK" again to dismiss the "Source Attachment Configuration" dialog. The JARs should look like this when you're done:
[[File:Eclipse_project_setup_03_JARs_with_source_attached.png|300px|thumb|none|Attach source to JARs]]
* Click the "Order and Export" tab. Check both JOGL JARs, then click "Finish".
[[File:Eclipse_project_setup_04_order_and_export.png|300px|thumb|none|Exporting JOGL JARs]]

=== Add dependency on the JOGL project ===

* Right-click your project and click "Properties".
* Select the "Java Build Path" on the left, then click the "Projects" tab on the right.
* Click the "Add..." button, check "JOGL", and click "OK".
* Your dependent project should look like this. Click "OK" to dismiss the "Properties" dialog.
[[File:Eclipse_project_setup_05_project_dependency.png|300px|thumb|none|JOGL project dependency]]

That's it! Your project can now use the library.

= Eclipse IDE user library =

If you don't want to put JOGL in a separate Eclipse project, you can put it in a user library instead. The drawback to this is that the user library is defined in your .metadata directory and contains absolute paths, so it's hard to share with others. But for a non-shared project this works fine.

=== Create a user library ===

* Click "Window > Preferences", then select "Java > Build Path > User Libraries" on the left.
* Click the "New..." button, type "JOGL" for the library name, and click "OK".
[[File:Eclipse_setup_01_create_user_library.png|300px|thumb|none|Create user library]]
* Click the "Add JARs..." button, navigate to the directory where you've stored the JARs, select all the non-native JARs, then click "Open".
* If you're using native JAR files:
** Make sure the <tt>gluegen-rt-natives-*-*.jar</tt> and <tt>jogl-all-natives-*-*.jar</tt> files for each platform you want to run on are in the same directory as the other JAR files. The native JAR files don't need to be added to the classpath.
* Expand each non-native JAR in the list
** Double-click "Source attachment", type the module's source zip name, (e.g. <tt>jogl-java-src.zip</tt> for the JAR file <tt>jogl-all.jar</tt>), and click "OK".
** If you're using native library files:
*** Double-click "Native library location", type the directory where native library files are stored, and click "OK".
[[File:Eclipse_setup_02_set_native_library_locations.png|300px|thumb|none|Set native library locations]]
* Click "OK" to exit Preferences dialog.

=== Add the user library to your project's dependencies ===

* Right-click your project in the Package Explorer and click "Properties".
* Select "Java Build Path" and click the "Libraries" tab.
[[File:Eclipse_setup_03_add_library_to_project.png|300px|thumb|none|Add library to project]]
* Click "Add Library...", select "User Library", click "Next", check "JOGL", and click "Finish".
[[File:Eclipse_setup_04_add_JOGL_library_to_project.png|300px|thumb|none|Add JOGL library to project]]
* Click "OK" to dismiss the Properties dialog.

That's it! You can now use the library in your project.

= IntelliJ IDEA =
=== Add a library dependency to your project ===

* Click "File > Project Structure".
* Select "Modules" on the left, then click the "Dependencies" tab on the right.
* Click the "+" button on the right, then select "Library... > Java".
[[File:IntelliJ_setup_01_add_library.png|300px|thumb|none|Add library]]
* Navigate to the directory where you extracted the JARs, select it, and click "OK".
[[File:IntelliJ_setup_02_find_library.png|300px|thumb|none|Find library]]
* Click "OK" to dismiss the Configure Library dialog.
[[File:IntelliJ_setup_03_configure_library.png|300px|thumb|none|Configure library]]
* Click "OK" to dismiss the Project Structure dialog. The external libraries in your project should now look like this if you're using native JAR files:
[[File:IntelliJ_setup_04_external_library_native_JARs.png|300px|thumb|none|Native JARs]]
or like this if you're using native library files:
[[File:IntelliJ_setup_04_external_library.png|300px|thumb|none|Native library files]]

* If you're using native JAR files:
** Make sure the <tt>gluegen-rt-natives-*-*.jar</tt> and <tt>jogl-all-natives-*-*.jar</tt> files for each platform you want to run on are in the same directory as the other JAR files.
* Otherwise, if you're using native library files:
** Click "Run > Edit Configurations".
** Type <tt>-Djava.library.path=your/path/to/native/library/files</tt> in the "VM Parameters" box. Note that paths with spaces must be double-quoted on Windows.
[[File:IntelliJ_setup_05_run_configuration.png|300px|thumb|none|Edit run configuration]]
** Click "OK" to dismiss the Run/Debug Configurations dialog.

That's it! You can now use the library in your project.

= NetBeans IDE =
=== Create a library and add it to your project ===

* Right-click your project and click "Properties".
* Select "Libraries" on the left and click "Add Library...".
* Click the "Create" button, then type "JOGL" for the library name and click "OK".[[File:NetBeans_setup_01_create_library.png|300px|thumb|none|Create library]]
* Click "Add JAR/Folder...", then navigate to the directory you extracted the JAR files, select them and click "Add JAR/Folder".
* Click "OK" to dismiss the Customize Library dialog.
* Click "Add Library" to dismiss the Add Library dialog.[[File:NetBeans_setup_02_add_library.png|300px|thumb|none|Add library]]
* Click "OK" to dismiss the Project Properties dialog. The libraries in your project should look like this.[[File:NetBeans_setup_03_libraries_in_project.png|300px|thumb|none|Libraries in project]]

* If you're using native JAR files:
** Make sure the <tt>gluegen-rt-natives-*-*.jar</tt> and <tt>jogl-all-natives-*-*.jar</tt> files for each platform you want to run on are in the same directory as the other JAR files. The native JAR files don't need to be added to the classpath.
* Otherwise, if you're using native library files:
** Click "Run > Set Project Configuration > Customize...". Select "Run" on the left if it isn't selected already.
** Type <tt>-Djava.library.path=your/path/to/native/library/files</tt> in the "VM Options" box.
** NOTE: If the library path has spaces in it, you must put quotes around it (at least on Windows) or you may get an odd NoClassDefFoundError when you try to run.[[File:NetBeans_setup_04_native_library_path.png|300px|thumb|none|Native library path]]
** Click "OK" to dismiss the Project Properties dialog.

That's it! You can now use the library in your project.

= vi and other text editors =
=== Create your project with the editor of your choice ===
* For example, to open vi, simply type <tt>vi</tt> and press <return>.
* Type all your code, then save it.

=== Compile and run your project from the command line ===
* We assume your JOGL JAR files are in a directory called <tt>jar</tt>. If you're using native JARs, we assume they're also in the <tt>jar</tt> directory. If you're using native library files, we assume they're in a directory called <tt>lib</tt>.

* First compile your program. We assume all your code is in a single file called <tt>name/someone/MyProject.java</tt>.
** Windows: Type <tt>javac -classpath "jar\gluegen-rt.jar;jar\jogl-all.jar" name\someone\MyProject.java</tt>
** Linux/MacOS X: Type <tt>javac -classpath "jar/gluegen-rt.jar:jar/jogl-all.jar" name/someone/MyProject.java</tt>

* Then run your project. We assume your main class is <tt>name.someone.MyProject</tt>. If you're using native JARs:
** Windows: Type <tt>java -classpath "jar\gluegen-rt.jar;jar\jogl-all.jar;." name.someone.MyProject</tt>
** Linux/MacOS X: Type <tt>java -classpath "jar/gluegen-rt.jar:jar/jogl-all.jar:." name.someone.MyProject</tt>
* If you're using native library files:
** Windows: Type <tt>java -classpath "jar\gluegen-rt.jar;jar\jogl-all.jar;." -Djava.library.path=lib -Djogamp.gluegen.UseTempJarCache=false name.someone.MyProject</tt>
** Linux/MacOS X: Type <tt>java -classpath "jar/gluegen-rt.jar:jar/jogl-all.jar:." -Djava.library.path=lib -Djogamp.gluegen.UseTempJarCache=false name.someone.MyProject</tt>

That's it! You can now use the library in your project.

Setting up a JogAmp project in your favorite IDE

2025-09-08T18:09:08Z

Sgothel: /* Maven */

__TOC__

These instructions assume that you've created a project in your favorite IDE, and now you want your project to be able to use a JogAmp library like JOGL, JOCL, JOAL, or GlueGen. We use JOGL as an example below, but these instructions work equally well for any other JogAmp library.

= Download a JogAmp library =

If you haven't done so already, download and extract the JogAmp library you want to use. For example, to download and extract JOGL, see the instructions at [[Downloading and installing JOGL]].

To use a JogAmp library you'll do three things:

* Add its JAR files to the Java classpath
* Add its native libraries in one of two ways:
** Either place its native JAR files in the same directory as the library JAR files
** Or add its native library files(the <tt>.dll</tt>,<tt>.so</tt>, and <tt>.jnilib</tt> files) to the Java library path
* Optional: Associate the *-java-src.zip files with the corresponding JAR files.

Each IDE has a slightly different way to do these things, as we show below. Using the native JAR files is usually slightly easier than using the native library files directly, and native JARs make it possible for all platforms' libraries to coexist in one project, so this is the recommended method.

Please note that all JogAmp libraries depend on the GlueGen runtime libraries. These are included in every JogAmp library for convenience, but are only required once in the classpath and library path of your project.

See [[JogAmp JAR File Handling|JogAmp JAR File Handling]], for details on native JAR files and custom JAR bundling.

= Eclipse IDE project =

Probably the simplest way to use JOGL in an Eclipse project is to create another Eclipse project to contain the JOGL JARs, then make your project depend on this new JOGL project. In the example below, I include only the 64-bit Windows native JARs, but you can put native JARs for as many platforms as you wish together into the JOGL Eclipse project.

=== Create a JOGL project ===

* Put all the JOGL code JARs, native JARs for all platforms you wish to support, and source ZIP files in a directory called "JOGL" in your workspace directory.
* Click "File > New > Java Project". Type "JOGL" as the project name and click "Next".
[[File:Eclipse_project_setup_01_create_project.png|300px|thumb|none|Create JOGL project]]
* Remove the native JARs from the project, leaving only gluegen-rt.jar and jogl-all.jar.
[[File:Eclipse_project_setup_02_remove_native_JARs.png|300px|thumb|none|Remove native JARs]]
NOTE: The gluegen-rt-natives-*-*.jar and jogl-all-natives-*-*.jar are not
required in the classpath by JOGL, but are required by Eclipse to export
your project as a runnable JAR file.
* Expand the jogl-all and gluegen-rt JARs. For each of them, double-click "Source attachment", click "Workspace...", navigate to the corresponding <tt>*-java-src.zip</tt> file in the project, select it, click "OK", and click "OK" again to dismiss the "Source Attachment Configuration" dialog. The JARs should look like this when you're done:
[[File:Eclipse_project_setup_03_JARs_with_source_attached.png|300px|thumb|none|Attach source to JARs]]
* Click the "Order and Export" tab. Check both JOGL JARs, then click "Finish".
[[File:Eclipse_project_setup_04_order_and_export.png|300px|thumb|none|Exporting JOGL JARs]]

=== Add dependency on the JOGL project ===

* Right-click your project and click "Properties".
* Select the "Java Build Path" on the left, then click the "Projects" tab on the right.
* Click the "Add..." button, check "JOGL", and click "OK".
* Your dependent project should look like this. Click "OK" to dismiss the "Properties" dialog.
[[File:Eclipse_project_setup_05_project_dependency.png|300px|thumb|none|JOGL project dependency]]

That's it! Your project can now use the library.

= Eclipse IDE user library =

If you don't want to put JOGL in a separate Eclipse project, you can put it in a user library instead. The drawback to this is that the user library is defined in your .metadata directory and contains absolute paths, so it's hard to share with others. But for a non-shared project this works fine.

=== Create a user library ===

* Click "Window > Preferences", then select "Java > Build Path > User Libraries" on the left.
* Click the "New..." button, type "JOGL" for the library name, and click "OK".
[[File:Eclipse_setup_01_create_user_library.png|300px|thumb|none|Create user library]]
* Click the "Add JARs..." button, navigate to the directory where you've stored the JARs, select all the non-native JARs, then click "Open".
* If you're using native JAR files:
** Make sure the <tt>gluegen-rt-natives-*-*.jar</tt> and <tt>jogl-all-natives-*-*.jar</tt> files for each platform you want to run on are in the same directory as the other JAR files. The native JAR files don't need to be added to the classpath.
* Expand each non-native JAR in the list
** Double-click "Source attachment", type the module's source zip name, (e.g. <tt>jogl-java-src.zip</tt> for the JAR file <tt>jogl-all.jar</tt>), and click "OK".
** If you're using native library files:
*** Double-click "Native library location", type the directory where native library files are stored, and click "OK".
[[File:Eclipse_setup_02_set_native_library_locations.png|300px|thumb|none|Set native library locations]]
* Click "OK" to exit Preferences dialog.

=== Add the user library to your project's dependencies ===

* Right-click your project in the Package Explorer and click "Properties".
* Select "Java Build Path" and click the "Libraries" tab.
[[File:Eclipse_setup_03_add_library_to_project.png|300px|thumb|none|Add library to project]]
* Click "Add Library...", select "User Library", click "Next", check "JOGL", and click "Finish".
[[File:Eclipse_setup_04_add_JOGL_library_to_project.png|300px|thumb|none|Add JOGL library to project]]
* Click "OK" to dismiss the Properties dialog.

That's it! You can now use the library in your project.

= IntelliJ IDEA =
=== Add a library dependency to your project ===

* Click "File > Project Structure".
* Select "Modules" on the left, then click the "Dependencies" tab on the right.
* Click the "+" button on the right, then select "Library... > Java".
[[File:IntelliJ_setup_01_add_library.png|300px|thumb|none|Add library]]
* Navigate to the directory where you extracted the JARs, select it, and click "OK".
[[File:IntelliJ_setup_02_find_library.png|300px|thumb|none|Find library]]
* Click "OK" to dismiss the Configure Library dialog.
[[File:IntelliJ_setup_03_configure_library.png|300px|thumb|none|Configure library]]
* Click "OK" to dismiss the Project Structure dialog. The external libraries in your project should now look like this if you're using native JAR files:
[[File:IntelliJ_setup_04_external_library_native_JARs.png|300px|thumb|none|Native JARs]]
or like this if you're using native library files:
[[File:IntelliJ_setup_04_external_library.png|300px|thumb|none|Native library files]]

* If you're using native JAR files:
** Make sure the <tt>gluegen-rt-natives-*-*.jar</tt> and <tt>jogl-all-natives-*-*.jar</tt> files for each platform you want to run on are in the same directory as the other JAR files.
* Otherwise, if you're using native library files:
** Click "Run > Edit Configurations".
** Type <tt>-Djava.library.path=your/path/to/native/library/files</tt> in the "VM Parameters" box. Note that paths with spaces must be double-quoted on Windows.
[[File:IntelliJ_setup_05_run_configuration.png|300px|thumb|none|Edit run configuration]]
** Click "OK" to dismiss the Run/Debug Configurations dialog.

That's it! You can now use the library in your project.

= NetBeans IDE =
=== Create a library and add it to your project ===

* Right-click your project and click "Properties".
* Select "Libraries" on the left and click "Add Library...".
* Click the "Create" button, then type "JOGL" for the library name and click "OK".[[File:NetBeans_setup_01_create_library.png|300px|thumb|none|Create library]]
* Click "Add JAR/Folder...", then navigate to the directory you extracted the JAR files, select them and click "Add JAR/Folder".
* Click "OK" to dismiss the Customize Library dialog.
* Click "Add Library" to dismiss the Add Library dialog.[[File:NetBeans_setup_02_add_library.png|300px|thumb|none|Add library]]
* Click "OK" to dismiss the Project Properties dialog. The libraries in your project should look like this.[[File:NetBeans_setup_03_libraries_in_project.png|300px|thumb|none|Libraries in project]]

* If you're using native JAR files:
** Make sure the <tt>gluegen-rt-natives-*-*.jar</tt> and <tt>jogl-all-natives-*-*.jar</tt> files for each platform you want to run on are in the same directory as the other JAR files. The native JAR files don't need to be added to the classpath.
* Otherwise, if you're using native library files:
** Click "Run > Set Project Configuration > Customize...". Select "Run" on the left if it isn't selected already.
** Type <tt>-Djava.library.path=your/path/to/native/library/files</tt> in the "VM Options" box.
** NOTE: If the library path has spaces in it, you must put quotes around it (at least on Windows) or you may get an odd NoClassDefFoundError when you try to run.[[File:NetBeans_setup_04_native_library_path.png|300px|thumb|none|Native library path]]
** Click "OK" to dismiss the Project Properties dialog.

That's it! You can now use the library in your project.

= Maven =

JogAmp supports for Maven via its [https://jogamp.org/deployment/maven/ the Jogamp Mirror Repository].

From <tt>2.0-rc11</tt> to <tt>2.3.2</tt> and from <tt>2.6.0</tt>, packages are pushed to
[http://search.maven.org/#search|ga|1|jogamp Maven Central].

Please see the [[Maven]] page for details on how to use them in your projects.

= Gradle =

From <tt>2.0-rc11</tt> to <tt>2.3.2</tt>, packages for all the JogAmp projects have been pushed to
[http://search.maven.org/#search|ga|1|jogamp Maven Central]. Since <tt>2.4.0</tt>, they have been pushed only to [https://jogamp.org/deployment/maven/ the JogAmp test repository]. Please add the following code into build.gradle to use the version <tt>2.4.0</tt> from the Jogamp test repository:
<pre>
repositories {
maven { url "https://jogamp.org/deployment/maven" }
}

dependencies {
implementation 'org.jogamp.gluegen:gluegen-rt-main:2.4.0'
implementation 'org.jogamp.jogl:jogl-all-main:2.4.0'
}
</pre>

= vi and other text editors =
=== Create your project with the editor of your choice ===
* For example, to open vi, simply type <tt>vi</tt> and press <return>.
* Type all your code, then save it.

=== Compile and run your project from the command line ===
* We assume your JOGL JAR files are in a directory called <tt>jar</tt>. If you're using native JARs, we assume they're also in the <tt>jar</tt> directory. If you're using native library files, we assume they're in a directory called <tt>lib</tt>.

* First compile your program. We assume all your code is in a single file called <tt>name/someone/MyProject.java</tt>.
** Windows: Type <tt>javac -classpath "jar\gluegen-rt.jar;jar\jogl-all.jar" name\someone\MyProject.java</tt>
** Linux/MacOS X: Type <tt>javac -classpath "jar/gluegen-rt.jar:jar/jogl-all.jar" name/someone/MyProject.java</tt>

* Then run your project. We assume your main class is <tt>name.someone.MyProject</tt>. If you're using native JARs:
** Windows: Type <tt>java -classpath "jar\gluegen-rt.jar;jar\jogl-all.jar;." name.someone.MyProject</tt>
** Linux/MacOS X: Type <tt>java -classpath "jar/gluegen-rt.jar:jar/jogl-all.jar:." name.someone.MyProject</tt>
* If you're using native library files:
** Windows: Type <tt>java -classpath "jar\gluegen-rt.jar;jar\jogl-all.jar;." -Djava.library.path=lib -Djogamp.gluegen.UseTempJarCache=false name.someone.MyProject</tt>
** Linux/MacOS X: Type <tt>java -classpath "jar/gluegen-rt.jar:jar/jogl-all.jar:." -Djava.library.path=lib -Djogamp.gluegen.UseTempJarCache=false name.someone.MyProject</tt>

That's it! You can now use the library in your project.

Maven

2025-09-08T18:08:27Z

Sgothel:

__TOC__

JogAmp supports for Maven via its [https://jogamp.org/deployment/maven/ the Jogamp Mirror Repository].

From <tt>2.0-rc11</tt> to <tt>2.3.2</tt> and from <tt>2.6.0</tt>, packages are pushed to
[http://search.maven.org/#search|ga|1|jogamp Maven Central].

= Add dependencies on the correct packages =

If you don't know which packages you want, you almost certainly want to use the
<tt>jogl-all-main</tt> and <tt>gluegen-rt-main</tt> packages, as these automatically
set up the correct dependencies on the native jar files for all platforms.

As an example, if your project uses JOGL <tt>2.6.0</tt>:

<pre>
<dependencies>
<dependency>
<groupId>org.jogamp.gluegen</groupId>
<artifactId>gluegen-rt-main</artifactId>
<version>2.6.0</version>
</dependency>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>jogl-all-main</artifactId>
<version>2.6.0</version>
</dependency>
</dependencies>
</pre>

Maven will pull all of the dependencies the next time you attempt to build the project.

Additionally, for <tt>joal</tt> and <tt>jocl</tt> support:

<pre>
<dependencies>
<dependency>
<groupId>org.jogamp.jocl</groupId>
<artifactId>jocl-main</artifactId>
<version>2.6.0</version>
</dependency>
<dependency>
<groupId>org.jogamp.joal</groupId>
<artifactId>joal-main</artifactId>
<version>2.6.0</version>
</dependency>
</dependencies>
</pre>

An example project is available in the <tt>maven</tt> subdirectory of the <tt>jogl-demos</tt> project
[https://jogamp.org/git/?p=jogl-demos.git;a=tree;f=maven].

= Package details =

For each JogAmp project, there are essentially two packages published: One contains the main compiled
jar files and any associated native library jar files, and the other simply contains <i>dependencies</i>
on those files. Using <tt>jogl-all</tt> and <tt>jogl-all-main</tt> as the example, the <tt>jogl-all</tt>
package in the jogamp.org mirror repository:

https://jogamp.org/deployment/maven/org/jogamp/jogl/jogl-all/2.6.0/

Note that there are many native jar files attached to the main package. However, if you were to use
the following dependency in your own project:

<pre>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>jogl-all</artifactId>
<version>2.6.0</version>
</dependency>
</pre>

Maven would download <tt>jogl-all-2.6.0.jar</tt> but would completely ignore all of the other
native jar files. Why? The reason for this is that the native jar files are uploaded as extra artifacts
to the <tt>jogl-all</tt> package and are, in a manner of speaking, not really considered to be part of
the package where dependencies are concerned. The POM for the <tt>jogl-all-main</tt> package adds
explicit dependencies on all of the extra artifacts in the <tt>jogl-all</tt> package:

https://jogamp.org/deployment/maven/org/jogamp/jogl/jogl-all-main/2.6.0/jogl-all-main-2.6.0.pom

So, when you add a dependency on <tt>jogl-all-main</tt> in your own project, the native jar files of
<tt>jogl-all</tt> are brought in as transitive dependencies and everything works as expected.

= Available packages =

{|
|Group ID
|Artifact ID
|Since
|Description
|-
|org.jogamp.gluegen
|gluegen-rt-android
|2.0.2-rc12
|GlueGen runtime code and native libraries (Android)
|-
|org.jogamp.gluegen
|gluegen-rt-main
|2.0-rc11
|Meta-package for automatic dependency resolution for the GlueGen runtime
|-
|org.jogamp.gluegen
|gluegen-rt
|2.0-rc11
|GlueGen runtime code and native libraries
|-
|org.jogamp.gluegen
|gluegen
|2.0-rc11
|GlueGen non-runtime code and native libraries (and atomic jars)
|-
|org.jogamp.joal
|joal-main
|2.0-rc11
|Meta-package for automatic dependency resolution for JOAL
|-
|org.jogamp.joal
|joal
|2.0-rc11
|JOAL code and native libraries
|-
|org.jogamp.joal
|joal-android
|2.2.0
|JOAL Android runtime
|-
|org.jogamp.jocl
|jocl-main
|2.0-rc11
|Meta-package for automatic dependency resolution for JOCL
|-
|org.jogamp.jocl
|jocl-android
|2.2.0
|JOCL Android runtime
|-
|org.jogamp.jocl
|jocl
|2.0-rc11
|JOCL code and native libraries
|-
|org.jogamp.jogl
|jogl-all-main
|2.0-rc11
|Meta-package for automatic dependency resolution for JOGL
|-
|org.jogamp.jogl
|jogl-all
|2.0-rc11
|JOGL code and native libraries
|-
|org.jogamp.jogl
|jogl-android
|2.0.2-rc12
|JOGL code and native libraries (Android)
|-
|org.jogamp.jogl
|jogl-android-main
|2.2.0
|Meta-package for automatic dependency resolution for JOGL (Android)
|-
|org.jogamp.jogl
|jogl-mobile-main
|2.0-rc11
|Meta-package for automatic dependency resolution for JOGL (mobile)
|-
|org.jogamp.jogl
|jogl-mobile
|2.0-rc11
|JOGL mobile code and native libraries (without AWT)
|-
|org.jogamp.jogl
|jogl-noawt-main
|2.0-rc11
|Meta-package for automatic dependency resolution for JOGL (without AWT)
|-
|org.jogamp.jogl
|jogl-noawt
|2.0-rc11
|JOGL code and native libraries (without AWT)
|-
|org.jogamp.jogl
|jogl
|2.0.2
|JOGL atomic jar files
|-
|org.jogamp.jogl
|nativewindow
|2.0.2
|Native window drivers for NEWT (atomic jars)
|-
|org.jogamp.jogl
|nativewindow-main
|2.2.0
|Native window drivers for NEWT (atomic frontend)
|-
|org.jogamp.jogl
|newt
|2.0.2
|NEWT code and native libraries (atomic jars)
|-
|org.jogamp.jogl
|newt-main
|2.2.0
|NEWT code and native libraries (atomic frontend)
|-
|org.jogamp.jogl
|occulusvr
|2.2.0
|JOGL code and native libraries (Oculus VR atomic jar files)
|-
|}

= Atomic jar files (optional) =

The so-called <i>atomic</i> jar files are provided as attachments to the <tt>jogl</tt>, <tt>newt</tt>,
<tt>nativewindow</tt> and <tt>gluegen</tt> packages. As an example, to depend only on the Linux AMD64
native jar files, on X11, using only the core of <tt>jogl</tt> and the native window toolkit in your
own projects, use the following dependencies:

<pre>
<dependency>
<groupId>org.jogamp.gluegen-rt</groupId>
<artifactId>jogl</artifactId>
<version>2.6.0</version>
</dependency>
<dependency>
<groupId>org.jogamp.gluegen-rt</groupId>
<artifactId>jogl</artifactId>
<version>2.6.0</version>
<classifier>natives-linux-amd64</classifier>
</dependency>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>jogl</artifactId>
<version>2.6.0</version>
<classifier>core</classifier>
</dependency>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>jogl</artifactId>
<version>2.6.0</version>
<classifier>natives-linux-amd64</classifier>
</dependency>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>jogl</artifactId>
<version>2.6.0</version>
<classifier>os-x11</classifier>
</dependency>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>jogl</artifactId>
<version>2.6.0</version>
<classifier>os-x11</classifier>
</dependency>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>newt</artifactId>
<version>2.6.0</version>
<classifier>driver-x11</classifier>
</dependency>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>newt</artifactId>
<version>2.6.0</version>
<classifier>core</classifier>
</dependency>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>newt</artifactId>
<version>2.6.0</version>
<classifier>natives-linux-amd64</classifier>
</dependency>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>nativewindow</artifactId>
<version>2.6.0</version>
<classifier>core</classifier>
</dependency>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>nativewindow</artifactId>
<version>2.6.0</version>
<classifier>natives-linux-amd64</classifier>
</dependency>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>nativewindow</artifactId>
<version>2.6.0</version>
<classifier>driver-x11</classifier>
</dependency>
</pre>

Note that the choice of which atomic jars are required is really outside of the scope of this
documentation. It's recommended that you browse the packages in question to see which jar
files are available. It's <i>not</i> recommended to depend on platform-specific jar files
in the manner shown above unless there's an extremely good reason to do so; to do otherwise
harms portability for no good reason!

= The jogamp.org Mirror Repository =

Bleeding edge, experimental packages will continue to be made available from the
[https://jogamp.org/deployment/maven Jogamp Mirror Repository] and can be used
by adding a new profile in your <tt>~/.m2/settings.xml</tt> file that specifies this repository:

<pre>
<?xml version="1.0" encoding="UTF-8"?>
<settings
xmlns="http://maven.apache.org/SETTINGS/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
<profiles>
<profile>
<id>jogamp</id>
<repositories>
<repository>
<id>jogamp-remote</id>
<name>jogamp mirror</name>
<url>https://www.jogamp.org/deployment/maven/</url>
<layout>default</layout>
</repository>
</repositories>
</profile>
</profiles>
<activeProfiles>
<activeProfile>jogamp</activeProfile>
</activeProfiles>
</settings>
</pre>

This repository can be added into the POM file like in this [https://jogamp.org/cgit/jogl-demos.git/tree/maven/trivial-test/pom.xml very simple example].

Maven will then check this repository for packages in addition to Maven Central when resolving dependencies.

= Android =

There is a [[Maven_And_Android|separate page]] documenting one method of producing packages that work on both Android and ordinary
desktop Java.

= Producing a fat jar =

See [[JogAmp_JAR_File_Handling#Maven_Assembly_Plugin|JAR File Handling]].

Maven

2025-09-07T21:54:07Z

Sgothel:

__TOC__

JogAmp now contains support for Maven via its [https://jogamp.org/deployment/maven/ the Jogamp Mirror Repository].

From <tt>2.0-rc11</tt> to <tt>2.3.2</tt> and from <tt>2.6.0</tt>, packages are pushed to
[http://search.maven.org/#search|ga|1|jogamp Maven Central].

= Add dependencies on the correct packages =

If you don't know which packages you want, you almost certainly want to use the
<tt>jogl-all-main</tt> and <tt>gluegen-rt-main</tt> packages, as these automatically
set up the correct dependencies on the native jar files for all platforms.

As an example, if your project uses JOGL <tt>2.6.0</tt>:

<pre>
<dependencies>
<dependency>
<groupId>org.jogamp.gluegen</groupId>
<artifactId>gluegen-rt-main</artifactId>
<version>2.6.0</version>
</dependency>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>jogl-all-main</artifactId>
<version>2.6.0</version>
</dependency>
</dependencies>
</pre>

Maven will pull all of the dependencies the next time you attempt to build the project.

Additionally, for <tt>joal</tt> and <tt>jocl</tt> support:

<pre>
<dependencies>
<dependency>
<groupId>org.jogamp.jocl</groupId>
<artifactId>jocl-main</artifactId>
<version>2.6.0</version>
</dependency>
<dependency>
<groupId>org.jogamp.joal</groupId>
<artifactId>joal-main</artifactId>
<version>2.6.0</version>
</dependency>
</dependencies>
</pre>

An example project is available in the <tt>maven</tt> subdirectory of the <tt>jogl-demos</tt> project
[https://jogamp.org/git/?p=jogl-demos.git;a=tree;f=maven].

= Package details =

For each JogAmp project, there are essentially two packages published: One contains the main compiled
jar files and any associated native library jar files, and the other simply contains <i>dependencies</i>
on those files. Using <tt>jogl-all</tt> and <tt>jogl-all-main</tt> as the example, the <tt>jogl-all</tt>
package in the jogamp.org mirror repository:

https://jogamp.org/deployment/maven/org/jogamp/jogl/jogl-all/2.6.0/

Note that there are many native jar files attached to the main package. However, if you were to use
the following dependency in your own project:

<pre>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>jogl-all</artifactId>
<version>2.6.0</version>
</dependency>
</pre>

Maven would download <tt>jogl-all-2.6.0.jar</tt> but would completely ignore all of the other
native jar files. Why? The reason for this is that the native jar files are uploaded as extra artifacts
to the <tt>jogl-all</tt> package and are, in a manner of speaking, not really considered to be part of
the package where dependencies are concerned. The POM for the <tt>jogl-all-main</tt> package adds
explicit dependencies on all of the extra artifacts in the <tt>jogl-all</tt> package:

https://jogamp.org/deployment/maven/org/jogamp/jogl/jogl-all-main/2.6.0/jogl-all-main-2.6.0.pom

So, when you add a dependency on <tt>jogl-all-main</tt> in your own project, the native jar files of
<tt>jogl-all</tt> are brought in as transitive dependencies and everything works as expected.

= Available packages =

{|
|Group ID
|Artifact ID
|Since
|Description
|-
|org.jogamp.gluegen
|gluegen-rt-android
|2.0.2-rc12
|GlueGen runtime code and native libraries (Android)
|-
|org.jogamp.gluegen
|gluegen-rt-main
|2.0-rc11
|Meta-package for automatic dependency resolution for the GlueGen runtime
|-
|org.jogamp.gluegen
|gluegen-rt
|2.0-rc11
|GlueGen runtime code and native libraries
|-
|org.jogamp.gluegen
|gluegen
|2.0-rc11
|GlueGen non-runtime code and native libraries (and atomic jars)
|-
|org.jogamp.joal
|joal-main
|2.0-rc11
|Meta-package for automatic dependency resolution for JOAL
|-
|org.jogamp.joal
|joal
|2.0-rc11
|JOAL code and native libraries
|-
|org.jogamp.joal
|joal-android
|2.2.0
|JOAL Android runtime
|-
|org.jogamp.jocl
|jocl-main
|2.0-rc11
|Meta-package for automatic dependency resolution for JOCL
|-
|org.jogamp.jocl
|jocl-android
|2.2.0
|JOCL Android runtime
|-
|org.jogamp.jocl
|jocl
|2.0-rc11
|JOCL code and native libraries
|-
|org.jogamp.jogl
|jogl-all-main
|2.0-rc11
|Meta-package for automatic dependency resolution for JOGL
|-
|org.jogamp.jogl
|jogl-all
|2.0-rc11
|JOGL code and native libraries
|-
|org.jogamp.jogl
|jogl-android
|2.0.2-rc12
|JOGL code and native libraries (Android)
|-
|org.jogamp.jogl
|jogl-android-main
|2.2.0
|Meta-package for automatic dependency resolution for JOGL (Android)
|-
|org.jogamp.jogl
|jogl-mobile-main
|2.0-rc11
|Meta-package for automatic dependency resolution for JOGL (mobile)
|-
|org.jogamp.jogl
|jogl-mobile
|2.0-rc11
|JOGL mobile code and native libraries (without AWT)
|-
|org.jogamp.jogl
|jogl-noawt-main
|2.0-rc11
|Meta-package for automatic dependency resolution for JOGL (without AWT)
|-
|org.jogamp.jogl
|jogl-noawt
|2.0-rc11
|JOGL code and native libraries (without AWT)
|-
|org.jogamp.jogl
|jogl
|2.0.2
|JOGL atomic jar files
|-
|org.jogamp.jogl
|nativewindow
|2.0.2
|Native window drivers for NEWT (atomic jars)
|-
|org.jogamp.jogl
|nativewindow-main
|2.2.0
|Native window drivers for NEWT (atomic frontend)
|-
|org.jogamp.jogl
|newt
|2.0.2
|NEWT code and native libraries (atomic jars)
|-
|org.jogamp.jogl
|newt-main
|2.2.0
|NEWT code and native libraries (atomic frontend)
|-
|org.jogamp.jogl
|occulusvr
|2.2.0
|JOGL code and native libraries (Oculus VR atomic jar files)
|-
|}

= Atomic jar files (optional) =

The so-called <i>atomic</i> jar files are provided as attachments to the <tt>jogl</tt>, <tt>newt</tt>,
<tt>nativewindow</tt> and <tt>gluegen</tt> packages. As an example, to depend only on the Linux AMD64
native jar files, on X11, using only the core of <tt>jogl</tt> and the native window toolkit in your
own projects, use the following dependencies:

<pre>
<dependency>
<groupId>org.jogamp.gluegen-rt</groupId>
<artifactId>jogl</artifactId>
<version>2.6.0</version>
</dependency>
<dependency>
<groupId>org.jogamp.gluegen-rt</groupId>
<artifactId>jogl</artifactId>
<version>2.6.0</version>
<classifier>natives-linux-amd64</classifier>
</dependency>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>jogl</artifactId>
<version>2.6.0</version>
<classifier>core</classifier>
</dependency>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>jogl</artifactId>
<version>2.6.0</version>
<classifier>natives-linux-amd64</classifier>
</dependency>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>jogl</artifactId>
<version>2.6.0</version>
<classifier>os-x11</classifier>
</dependency>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>jogl</artifactId>
<version>2.6.0</version>
<classifier>os-x11</classifier>
</dependency>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>newt</artifactId>
<version>2.6.0</version>
<classifier>driver-x11</classifier>
</dependency>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>newt</artifactId>
<version>2.6.0</version>
<classifier>core</classifier>
</dependency>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>newt</artifactId>
<version>2.6.0</version>
<classifier>natives-linux-amd64</classifier>
</dependency>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>nativewindow</artifactId>
<version>2.6.0</version>
<classifier>core</classifier>
</dependency>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>nativewindow</artifactId>
<version>2.6.0</version>
<classifier>natives-linux-amd64</classifier>
</dependency>
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>nativewindow</artifactId>
<version>2.6.0</version>
<classifier>driver-x11</classifier>
</dependency>
</pre>

Note that the choice of which atomic jars are required is really outside of the scope of this
documentation. It's recommended that you browse the packages in question to see which jar
files are available. It's <i>not</i> recommended to depend on platform-specific jar files
in the manner shown above unless there's an extremely good reason to do so; to do otherwise
harms portability for no good reason!

= The jogamp.org Mirror Repository =

Bleeding edge, experimental packages will continue to be made available from the
[https://jogamp.org/deployment/maven Jogamp Mirror Repository] and can be used
by adding a new profile in your <tt>~/.m2/settings.xml</tt> file that specifies this repository:

<pre>
<?xml version="1.0" encoding="UTF-8"?>
<settings
xmlns="http://maven.apache.org/SETTINGS/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
<profiles>
<profile>
<id>jogamp</id>
<repositories>
<repository>
<id>jogamp-remote</id>
<name>jogamp mirror</name>
<url>https://www.jogamp.org/deployment/maven/</url>
<layout>default</layout>
</repository>
</repositories>
</profile>
</profiles>
<activeProfiles>
<activeProfile>jogamp</activeProfile>
</activeProfiles>
</settings>
</pre>

This repository can be added into the POM file like in this [https://jogamp.org/cgit/jogl-demos.git/tree/maven/trivial-test/pom.xml very simple example].

Maven will then check this repository for packages in addition to Maven Central when resolving dependencies.

= Android =

There is a [[Maven_And_Android|separate page]] documenting one method of producing packages that work on both Android and ordinary
desktop Java.

= Producing a fat jar =

See [[JogAmp_JAR_File_Handling#Maven_Assembly_Plugin|JAR File Handling]].

Downloading and installing JOGL

2025-09-01T02:12:25Z

Sgothel:

Before you can build a project that uses JOGL [https://jogamp.org/wiki/index.php/Setting_up_a_JogAmp_project_in_your_favorite_IDE in your IDE or on the command line], you'll need to download and install the JOGL JAR files and native JARs or native library files (<tt>.dll</tt>/<tt>.so</tt>/<tt>.jnilib</tt> files).

You have a choice of JOGL versions to download. The [{{SERVER}}/deployment/jogamp-current/archive/ latest stable version] is the safest, but lags behind in features. The [{{SERVER}}/deployment/autobuilds/master/ latest automatic build] contains all checked-in code, but may be failing some tests.

See also [[Jogamp Versioning and Releases]] for versioning details.

= Downloading the latest stable version =

== Fat Jar for all platforms ==
(excluding Android)

* [{{SERVER}}/deployment/jogamp-current/fat/jogamp-fat.jar jogamp-fat.jar]
* Demo files
** [{{SERVER}}/deployment/jogamp-current/fat/jogl-demos.jar jogl-demos.jar]
** [{{SERVER}}/deployment/jogamp-current/fat/jogl-fonts-p0.jar jogl-fonts-p0.jar]

=== Using the fat jar ===
Download all three jar files into a folder as described above and launch e.g.
''java -cp jogamp-fat.jar:jogl-demos.jar com.jogamp.opengl.demos.graph.ui.UISceneDemo03''

== APK for Android ==
* See [[Android Packages]]
* [{{SERVER}}/deployment/jogamp-current/apk/ Latest APK files location]

User are encouraged to merge the ''<module>-all-android-<arch>.apk'' or jar files with their own application.

=== Testing a single fat APK ===
A fat demo APK ''jogl-demos-fat-android-${arch}.apk'' resides inside the [{{SERVER}}/deployment/jogamp-current/apk/ APK release folder] and can be directly installed and tested on your device w/ developer mode enabled.

== 7z all-in-one archive ==
Go to [{{SERVER}}/deployment/jogamp-current/archive/ this page] and download the all-in-one 7z archive file:

: [{{SERVER}}/deployment/jogamp-current/archive/jogamp-all-platforms.7z jogamp-all-platforms.7z]

=== Using the jogamp-all-platforms ===

After inflating the file with [http://www.7-zip.org/ 7zip], you will have the general directory structure:

<pre>
<jogamp-all-platforms>/
<jogamp-all-platforms>/etc/test.sh
<jogamp-all-platforms>/etc/test.bat
<jogamp-all-platforms>/etc/test_dbg.sh
<jogamp-all-platforms>/etc/test_dbg.bat
<jogamp-all-platforms>/jar/<module>.jar
<jogamp-all-platforms>/jar/<module>-natives-<os.and.arch>.jar
<jogamp-all-platforms>/lib/
<jogamp-all-platforms>/<module>-java-src.zip*
</pre>
Legend:
* [{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html#NativeJARFileNameConvention os.and.arch]
* module: gluegen, joal, jogl or jocl

Now you can '''test''' the ''archive'' as described
in [[Jogamp Versioning and Releases#Runtime Version Check|runtime version check]]
and [[Jogamp Versioning and Releases#Runtime Debug Logs|runtime debug test]].

If anything doesn't work as predicted, please follow our [[Jogl FAQ#Bugreports & Testing|bugreport guide]].

While keeping the above directory structure as-is, you can go ahead and
* add the non-native JAR files to your CLASSPATH (IDE, manual, ..)
* attach the java-source files to the non-native JAR files (IDE)

.. now you are set to start using JogAmp module in your project.

The above is detailed in [[Setting_up_a_JogAmp_project_in_your_favorite_IDE#Eclipse_IDE_project|Eclipse Project]]
and [[Setting_up_a_JogAmp_project_in_your_favorite_IDE#Eclipse_IDE_user_library|Eclipse User Library]].

= Downloading the latest aggregated autobuild =

Got to [{{SERVER}}/deployment/archive/master/?C=M;O=D this page] and navigate into the first folder,
which shall be the latest ''aggregated autobuild''.

Then navigate further down to '''archive''' and download the file '''jogamp-all-platforms.7z'''.

For example, on '''13-Mar-2013 20:19 CET''', the latest ''aggregated autobuild'' was:

[{{SERVER}}/deployment/archive/master/gluegen_646-joal_408-jogl_930-jocl_756/archive/jogamp-all-platforms.7z {{SERVER}}/deployment/archive/master/gluegen_646-joal_408-jogl_930-jocl_756/archive/jogamp-all-platforms.7z]

Now you can continue [[#Using the 7z jogamp-all-platforms archive|here]].

= Downloading the latest automatic build =

For the latest automatic build, we have to download gluegen and jogl separately.

First, go to [{{SERVER}}/deployment/autobuilds/master/?C=M;O=D this page] and click on the most recent <tt>gluegen-b*</tt> directory. Then download one of these files for each platform you're developing on:

: 32-bit Windows: <tt>gluegen-2.0-bvvv-20yymmdd-windows-i586.7z</tt>
: 64-bit Windows: <tt>gluegen-2.0-bvvv-20yymmdd-windows-amd64.7z</tt>
: 32/64-bit Mac OS X: <tt>gluegen-2.0-bvvv-20yymmdd-macosx-universal.7z</tt>
: 32-bit Linux: <tt>gluegen-2.0-bvvv-20yymmdd-linux-i586.7z</tt>
: 64-bit Linux: <tt>gluegen-2.0-bvvv-20yymmdd-linux-amd64.7z</tt>
: 32-bit Solaris: <tt>gluegen-2.0-bvvv-20yymmdd-solaris-i586.7z</tt>
: 64-bit Solaris: <tt>gluegen-2.0-bvvv-20yymmdd-solaris-amd64.7z</tt>

Then, go back to [{{SERVER}}/deployment/autobuilds/master/?C=M;O=D this page] and click on the most recent <tt>jogl-b*</tt> directory. Then download one of these files for each platform you're developing on:

: 32-bit Windows: <tt>jogl-2.0-bvvv-20yymmdd-windows-i586.7z</tt>
: 64-bit Windows: <tt>jogl-2.0-bvvv-20yymmdd-windows-amd64.7z</tt>
: 32/64-bit Mac OS X: <tt>jogl-2.0-bvvv-20yymmdd-macosx-universal.7z</tt>
: 32-bit Linux: <tt>jogl-2.0-bvvv-20yymmdd-linux-i586.7z</tt>
: 64-bit Linux: <tt>jogl-2.0-bvvv-20yymmdd-linux-amd64.7z</tt>
: 32-bit Solaris: <tt>jogl-2.0-bvvv-20yymmdd-solaris-i586.7z</tt>
: 64-bit Solaris: <tt>jogl-2.0-bvvv-20yymmdd-solaris-amd64.7z</tt>

Note that these automatic builds may not have passed all the regression tests. You can check the test results on the [https://jogamp.org/chuck/ build server] to make sure you're not downloading a broken build.

== Native JARs vs. native library files ==

JOGL uses native libraries to interface with each platform's OpenGL library. You can either download these native libraries wrapped up in JAR files (the "native JARs" option), or you can download them as separate <tt>.dll</tt>/<tt>.so</tt>/<tt>.jnilib</tt> files (the "native library files" option).

When using native JARs, JOGL automatically unzips the native JARs at startup into a temporary directory, then loads the resulting <tt>.dll</tt>/<tt>.so</tt>/<tt>.jnilib</tt> files from there. When using native library files, JOGL just loads them directly from where they sit, with no unzipping.

Using native JARs is usually easiest, since there are fewer files to manage and it allows different platforms' native library files to coexist in the same directory. Only use the native library files directly if you need fine control over native library file placement or if your app doesn't have permissions to create temporary directories.

See [[JogAmp JAR File Handling|JogAmp JAR File Handling]], for details on native JAR files and custom JAR bundling.

== Unzipping the files ==

Unzip all the downloaded files with [http://www.7-zip.org/ 7zip]. An unzipped file has this general directory structure:

<pre>
<archive>/
<archive>/jar/
<archive>/lib/
<archive>/<module>-java-src.zip*
</pre>

Now you may copy the required JARs out of each <tt>jar</tt> folder and the native library files (if you're using them) out of each <tt>lib</tt> folder. For a full desktop installation using native JARs, here are the files you need. Note that the native JAR names are different for each platform, so you can use some or all of the native JARs together to create a multi-platform installation.

{|cellpadding="4" cellspacing="0"
!align="left"|64-bit Windows
!align="left"|64-bit Linux
!align="left"|32/64-bit Mac
|-
|<tt>gluegen-rt.jar</tt>||<tt>gluegen-rt.jar</tt>||<tt>gluegen-rt.jar</tt>
|-
|<tt>jogl-all.jar</tt>||<tt>jogl-all.jar</tt>||<tt>jogl-all.jar</tt>
|-
|<tt>gluegen-java-src.zip</tt>||<tt>gluegen-java-src.zip</tt>||<tt>gluegen-java-src.zip</tt>
|-
|<tt>jogl-java-src.zip</tt>||<tt>jogl-java-src.zip</tt>||<tt>jogl-java-src.zip</tt>
|-
|<tt>gluegen-rt-natives-windows-amd64.jar</tt>||<tt>gluegen-rt-natives-linux-amd64.jar</tt>||<tt>gluegen-rt-natives-macosx-universal.jar</tt>
|-
|<tt>jogl-all-natives-windows-amd64.jar</tt>||<tt>jogl-all-natives-linux-amd64.jar</tt>||<tt>jogl-all-natives-macosx-universal.jar</tt>
|}
<br/>
{|cellpadding="4" cellspacing="0"
!align="left"|32-bit Windows
!align="left"|32-bit Linux
|-
|<tt>gluegen-rt.jar</tt>||<tt>gluegen-rt.jar</tt>
|-
|<tt>jogl-all.jar</tt>||<tt>jogl-all.jar</tt>||
|-
|<tt>gluegen-java-src.zip</tt>||<tt>gluegen-java-src.zip</tt>||
|-
|<tt>jogl-java-src.zip</tt>||<tt>jogl-java-src.zip</tt>||
|-
|<tt>gluegen-rt-natives-windows-i586.jar</tt>||<tt>gluegen-rt-natives-linux-i586.jar</tt>
|-
|<tt>jogl-all-natives-windows-i586.jar</tt>||<tt>jogl-all-natives-linux-i586.jar</tt>
|}

<br/>
For a full desktop installation using native library files, here are the files you need. Note that the native library files have the same names for 32-bit and 64-bit platforms, so 32-bit and 64-bit platforms can't coexist in one installation.
<br/>

{|cellpadding="4" cellspacing="0"
!align="left"|Windows
!align="left"|Linux
!align="left"|Mac
|-
|<tt>gluegen-rt.jar</tt>||<tt>gluegen-rt.jar</tt>||<tt>gluegen-rt.jar</tt>
|-
|<tt>jogl-all.jar</tt>||<tt>jogl-all.jar</tt>||<tt>jogl-all.jar</tt>
|-
|<tt>gluegen-java-src.zip</tt>||<tt>gluegen-java-src.zip</tt>||<tt>gluegen-java-src.zip</tt>
|-
|<tt>jogl-java-src.zip</tt>||<tt>jogl-java-src.zip</tt>||<tt>jogl-java-src.zip</tt>
|-
|<tt>gluegen-rt.dll</tt>||<tt>libgluegen-rt.so</tt>||<tt>libgluegen-rt.jnilib</tt>
|-
|<tt>jogl_desktop.dll</tt>||<tt>libjogl_desktop.so</tt>||<tt>libjogl_desktop.jnilib</tt>
|-
|<tt>nativewindow_awt.dll</tt>||<tt>libnativewindow_awt.so</tt>||<tt>libnativewindow_awt.jnilib</tt>
|-
|<tt>nativewindow_win32.dll</tt>||<tt>libnativewindow_x11.so</tt>||<tt>libnativewindow_macosx.jnilib</tt>
|-
|<tt>newt.dll</tt>||<tt>libnewt.so</tt>||<tt>libnewt.jnilib</tt>
|}

= Maven =
Alternatively, the Jogamp packages are available through Maven.

See the [[Setting_up_a_JogAmp_project_in_your_favorite_IDE#Maven|maven instructions]] for a guide to using Jogamp in
Maven projects.

= More information =

JogAmp follows a [[Jogamp_Versioning_and_Releases#Release_Classification|release scheme]],
which describes the following locations to download the 7z archives from:

* [{{SERVER}}/deployment/ Deployment Home]
** [{{SERVER}}/deployment/jogamp-current/archive/ Signed Release]
** [{{SERVER}}/deployment/jogamp-next/archive/ Signed Candidate]
** [{{SERVER}}/deployment/jogamp-next/v2.0-rc3archive/ Specific Version]

[{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html JOGL Deployment] describes the content of the 7z archive files.

These installations contain all of JOGL. If you want to remove parts you don't use, see [{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html JOGL Deployment] for more information.

Downloading and installing JOGL

2025-08-31T18:59:29Z

Sgothel:

Before you can build a project that uses JOGL [https://jogamp.org/wiki/index.php/Setting_up_a_JogAmp_project_in_your_favorite_IDE in your IDE or on the command line], you'll need to download and install the JOGL JAR files and native JARs or native library files (<tt>.dll</tt>/<tt>.so</tt>/<tt>.jnilib</tt> files).

You have a choice of JOGL versions to download. The [{{SERVER}}/deployment/jogamp-current/archive/ latest stable version] is the safest, but lags behind in features. The [{{SERVER}}/deployment/autobuilds/master/ latest automatic build] contains all checked-in code, but may be failing some tests.

= Downloading the latest stable version =

== Fat Jar for all platforms ==
(excluding Android)

* [{{SERVER}}/deployment/jogamp-current/fat/jogamp-fat.jar jogamp-fat.jar]
* Demo files
** [{{SERVER}}/deployment/jogamp-current/fat/jogl-demos.jar jogl-demos.jar]
** [{{SERVER}}/deployment/jogamp-current/fat/jogl-fonts-p0.jar jogl-fonts-p0.jar]

=== Using the fat jar ===
Download all three jar files into a folder as described above and launch e.g.
''java -cp jogamp-fat.jar:jogl-demos.jar com.jogamp.opengl.demos.graph.ui.UISceneDemo03''

== APK for Android ==
* See [[Android Packages]]
* [{{SERVER}}/deployment/jogamp-current/apk/ Latest APK files location]

User are encouraged to merge the ''<module>-all-android-<arch>.apk'' or jar files with their own application.

=== Testing a single fat APK ===
A fat demo APK ''jogl-demos-fat-android-${arch}.apk'' resides inside the [{{SERVER}}/deployment/jogamp-current/apk/ APK release folder] and can be directly installed and tested on your device w/ developer mode enabled.

== 7z all-in-one archive ==
Go to [{{SERVER}}/deployment/jogamp-current/archive/ this page] and download the all-in-one 7z archive file:

: [{{SERVER}}/deployment/jogamp-current/archive/jogamp-all-platforms.7z jogamp-all-platforms.7z]

=== Using the jogamp-all-platforms ===

After inflating the file with [http://www.7-zip.org/ 7zip], you will have the general directory structure:

<pre>
<jogamp-all-platforms>/
<jogamp-all-platforms>/etc/test.sh
<jogamp-all-platforms>/etc/test.bat
<jogamp-all-platforms>/etc/test_dbg.sh
<jogamp-all-platforms>/etc/test_dbg.bat
<jogamp-all-platforms>/jar/<module>.jar
<jogamp-all-platforms>/jar/<module>-natives-<os.and.arch>.jar
<jogamp-all-platforms>/lib/
<jogamp-all-platforms>/<module>-java-src.zip*
</pre>
Legend:
* [{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html#NativeJARFileNameConvention os.and.arch]
* module: gluegen, joal, jogl or jocl

Now you can '''test''' the ''archive'' as described
in [[Jogamp Versioning and Releases#Runtime Version Check|runtime version check]]
and [[Jogamp Versioning and Releases#Runtime Debug Logs|runtime debug test]].

If anything doesn't work as predicted, please follow our [[Jogl FAQ#Bugreports & Testing|bugreport guide]].

While keeping the above directory structure as-is, you can go ahead and
* add the non-native JAR files to your CLASSPATH (IDE, manual, ..)
* attach the java-source files to the non-native JAR files (IDE)

.. now you are set to start using JogAmp module in your project.

The above is detailed in [[Setting_up_a_JogAmp_project_in_your_favorite_IDE#Eclipse_IDE_project|Eclipse Project]]
and [[Setting_up_a_JogAmp_project_in_your_favorite_IDE#Eclipse_IDE_user_library|Eclipse User Library]].

= Downloading the latest aggregated autobuild =

Got to [{{SERVER}}/deployment/archive/master/?C=M;O=D this page] and navigate into the first folder,
which shall be the latest ''aggregated autobuild''.

Then navigate further down to '''archive''' and download the file '''jogamp-all-platforms.7z'''.

For example, on '''13-Mar-2013 20:19 CET''', the latest ''aggregated autobuild'' was:

[{{SERVER}}/deployment/archive/master/gluegen_646-joal_408-jogl_930-jocl_756/archive/jogamp-all-platforms.7z {{SERVER}}/deployment/archive/master/gluegen_646-joal_408-jogl_930-jocl_756/archive/jogamp-all-platforms.7z]

Now you can continue [[#Using the 7z jogamp-all-platforms archive|here]].

= Downloading the latest automatic build =

For the latest automatic build, we have to download gluegen and jogl separately.

First, go to [{{SERVER}}/deployment/autobuilds/master/?C=M;O=D this page] and click on the most recent <tt>gluegen-b*</tt> directory. Then download one of these files for each platform you're developing on:

: 32-bit Windows: <tt>gluegen-2.0-bvvv-20yymmdd-windows-i586.7z</tt>
: 64-bit Windows: <tt>gluegen-2.0-bvvv-20yymmdd-windows-amd64.7z</tt>
: 32/64-bit Mac OS X: <tt>gluegen-2.0-bvvv-20yymmdd-macosx-universal.7z</tt>
: 32-bit Linux: <tt>gluegen-2.0-bvvv-20yymmdd-linux-i586.7z</tt>
: 64-bit Linux: <tt>gluegen-2.0-bvvv-20yymmdd-linux-amd64.7z</tt>
: 32-bit Solaris: <tt>gluegen-2.0-bvvv-20yymmdd-solaris-i586.7z</tt>
: 64-bit Solaris: <tt>gluegen-2.0-bvvv-20yymmdd-solaris-amd64.7z</tt>

Then, go back to [{{SERVER}}/deployment/autobuilds/master/?C=M;O=D this page] and click on the most recent <tt>jogl-b*</tt> directory. Then download one of these files for each platform you're developing on:

: 32-bit Windows: <tt>jogl-2.0-bvvv-20yymmdd-windows-i586.7z</tt>
: 64-bit Windows: <tt>jogl-2.0-bvvv-20yymmdd-windows-amd64.7z</tt>
: 32/64-bit Mac OS X: <tt>jogl-2.0-bvvv-20yymmdd-macosx-universal.7z</tt>
: 32-bit Linux: <tt>jogl-2.0-bvvv-20yymmdd-linux-i586.7z</tt>
: 64-bit Linux: <tt>jogl-2.0-bvvv-20yymmdd-linux-amd64.7z</tt>
: 32-bit Solaris: <tt>jogl-2.0-bvvv-20yymmdd-solaris-i586.7z</tt>
: 64-bit Solaris: <tt>jogl-2.0-bvvv-20yymmdd-solaris-amd64.7z</tt>

Note that these automatic builds may not have passed all the regression tests. You can check the test results on the [https://jogamp.org/chuck/ build server] to make sure you're not downloading a broken build.

== Native JARs vs. native library files ==

JOGL uses native libraries to interface with each platform's OpenGL library. You can either download these native libraries wrapped up in JAR files (the "native JARs" option), or you can download them as separate <tt>.dll</tt>/<tt>.so</tt>/<tt>.jnilib</tt> files (the "native library files" option).

When using native JARs, JOGL automatically unzips the native JARs at startup into a temporary directory, then loads the resulting <tt>.dll</tt>/<tt>.so</tt>/<tt>.jnilib</tt> files from there. When using native library files, JOGL just loads them directly from where they sit, with no unzipping.

Using native JARs is usually easiest, since there are fewer files to manage and it allows different platforms' native library files to coexist in the same directory. Only use the native library files directly if you need fine control over native library file placement or if your app doesn't have permissions to create temporary directories.

See [[JogAmp JAR File Handling|JogAmp JAR File Handling]], for details on native JAR files and custom JAR bundling.

== Unzipping the files ==

Unzip all the downloaded files with [http://www.7-zip.org/ 7zip]. An unzipped file has this general directory structure:

<pre>
<archive>/
<archive>/jar/
<archive>/lib/
<archive>/<module>-java-src.zip*
</pre>

Now you may copy the required JARs out of each <tt>jar</tt> folder and the native library files (if you're using them) out of each <tt>lib</tt> folder. For a full desktop installation using native JARs, here are the files you need. Note that the native JAR names are different for each platform, so you can use some or all of the native JARs together to create a multi-platform installation.

{|cellpadding="4" cellspacing="0"
!align="left"|64-bit Windows
!align="left"|64-bit Linux
!align="left"|32/64-bit Mac
|-
|<tt>gluegen-rt.jar</tt>||<tt>gluegen-rt.jar</tt>||<tt>gluegen-rt.jar</tt>
|-
|<tt>jogl-all.jar</tt>||<tt>jogl-all.jar</tt>||<tt>jogl-all.jar</tt>
|-
|<tt>gluegen-java-src.zip</tt>||<tt>gluegen-java-src.zip</tt>||<tt>gluegen-java-src.zip</tt>
|-
|<tt>jogl-java-src.zip</tt>||<tt>jogl-java-src.zip</tt>||<tt>jogl-java-src.zip</tt>
|-
|<tt>gluegen-rt-natives-windows-amd64.jar</tt>||<tt>gluegen-rt-natives-linux-amd64.jar</tt>||<tt>gluegen-rt-natives-macosx-universal.jar</tt>
|-
|<tt>jogl-all-natives-windows-amd64.jar</tt>||<tt>jogl-all-natives-linux-amd64.jar</tt>||<tt>jogl-all-natives-macosx-universal.jar</tt>
|}
<br/>
{|cellpadding="4" cellspacing="0"
!align="left"|32-bit Windows
!align="left"|32-bit Linux
|-
|<tt>gluegen-rt.jar</tt>||<tt>gluegen-rt.jar</tt>
|-
|<tt>jogl-all.jar</tt>||<tt>jogl-all.jar</tt>||
|-
|<tt>gluegen-java-src.zip</tt>||<tt>gluegen-java-src.zip</tt>||
|-
|<tt>jogl-java-src.zip</tt>||<tt>jogl-java-src.zip</tt>||
|-
|<tt>gluegen-rt-natives-windows-i586.jar</tt>||<tt>gluegen-rt-natives-linux-i586.jar</tt>
|-
|<tt>jogl-all-natives-windows-i586.jar</tt>||<tt>jogl-all-natives-linux-i586.jar</tt>
|}

<br/>
For a full desktop installation using native library files, here are the files you need. Note that the native library files have the same names for 32-bit and 64-bit platforms, so 32-bit and 64-bit platforms can't coexist in one installation.
<br/>

{|cellpadding="4" cellspacing="0"
!align="left"|Windows
!align="left"|Linux
!align="left"|Mac
|-
|<tt>gluegen-rt.jar</tt>||<tt>gluegen-rt.jar</tt>||<tt>gluegen-rt.jar</tt>
|-
|<tt>jogl-all.jar</tt>||<tt>jogl-all.jar</tt>||<tt>jogl-all.jar</tt>
|-
|<tt>gluegen-java-src.zip</tt>||<tt>gluegen-java-src.zip</tt>||<tt>gluegen-java-src.zip</tt>
|-
|<tt>jogl-java-src.zip</tt>||<tt>jogl-java-src.zip</tt>||<tt>jogl-java-src.zip</tt>
|-
|<tt>gluegen-rt.dll</tt>||<tt>libgluegen-rt.so</tt>||<tt>libgluegen-rt.jnilib</tt>
|-
|<tt>jogl_desktop.dll</tt>||<tt>libjogl_desktop.so</tt>||<tt>libjogl_desktop.jnilib</tt>
|-
|<tt>nativewindow_awt.dll</tt>||<tt>libnativewindow_awt.so</tt>||<tt>libnativewindow_awt.jnilib</tt>
|-
|<tt>nativewindow_win32.dll</tt>||<tt>libnativewindow_x11.so</tt>||<tt>libnativewindow_macosx.jnilib</tt>
|-
|<tt>newt.dll</tt>||<tt>libnewt.so</tt>||<tt>libnewt.jnilib</tt>
|}

= Maven =
Alternatively, the Jogamp packages are available through Maven.

See the [[Setting_up_a_JogAmp_project_in_your_favorite_IDE#Maven|maven instructions]] for a guide to using Jogamp in
Maven projects.

= More information =

JogAmp follows a [[Jogamp_Versioning_and_Releases#Release_Classification|release scheme]],
which describes the following locations to download the 7z archives from:

* [{{SERVER}}/deployment/ Deployment Home]
** [{{SERVER}}/deployment/jogamp-current/archive/ Signed Release]
** [{{SERVER}}/deployment/jogamp-next/archive/ Signed Candidate]
** [{{SERVER}}/deployment/jogamp-next/v2.0-rc3archive/ Specific Version]

[{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html JOGL Deployment] describes the content of the 7z archive files.

These installations contain all of JOGL. If you want to remove parts you don't use, see [{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html JOGL Deployment] for more information.

Android Packages

2025-08-31T18:56:21Z

Sgothel: /* Direct download and installation of our Android Packages */

= Direct download and installation of our Android Packages =

[{{SERVER}}/deployment/jogamp-current/apk Latest APK files location]

You may need to uninstall previous installed versions first!

== Single Fat Application Method ==
A fat demo APK ''jogl-demos-fat-android-${arch}.apk'' resides inside the [{{SERVER}}/deployment/jogamp-current/apk APK release folder] and can be directly installed and tested on your device w/ developer mode enabled.

User are encouraged to merge the ''<module>-all-android-<arch>.apk'' or jar files with their own application.

== Launcher Method ==
The following APKs must be installed to complete a JogAmp installation:
* [{{Server}}/deployment/jogamp-current/apk/jogamp-android-launcher.apk Launcher]
* ARM 32-bit >= armv6
** [{{Server}}/deployment/jogamp-current/apk/gluegen-rt-android-armv6.apk GlueGen]
** [{{Server}}/deployment/jogamp-current/apk/joal-android-armv6.apk JOAL]
** [{{Server}}/deployment/jogamp-current/apk/jogl-all-android-armv6.apk JOGL]
* ARM 64-bit >= aarch64
** [{{Server}}/deployment/jogamp-current/apk/gluegen-rt-android-aarch64.apk GlueGen]
** [{{Server}}/deployment/jogamp-current/apk/joal-android-aarch64.apk JOAL]
** [{{Server}}/deployment/jogamp-current/apk/jogl-all-android-aarch64.apk JOGL]

The following demo APK should be installed:
* [{{Server}}/deployment/jogamp-current/apk/joal-test-android.apk JOAL Tests]
* [{{Server}}/deployment/jogamp-current/apk/jogl-test-android.apk JOGL Tests]

= Download and installation via ''Google Play'' =

''' These versions are currently not maintained and are older versions! '''

The following APKs must be installed to complete a JogAmp installation:
* [https://play.google.com/store/apps/details?id=jogamp.android.launcher Launcher]
* [https://play.google.com/store/apps/details?id=com.jogamp.common GlueGen]
* [https://play.google.com/store/apps/details?id=com.jogamp.openal JOAL]
* [https://play.google.com/store/apps/details?id=javax.media.opengl JOGL]

The following demo APK should be installed:
* [https://play.google.com/store/apps/details?id=com.jogamp.opengl.test JOAL Tests]
* [https://play.google.com/store/apps/details?id=com.jogamp.opengl.test JOGL Tests]

Downloading and installing JOGL

2025-08-31T18:55:28Z

Sgothel:

Before you can build a project that uses JOGL [https://jogamp.org/wiki/index.php/Setting_up_a_JogAmp_project_in_your_favorite_IDE in your IDE or on the command line], you'll need to download and install the JOGL JAR files and native JARs or native library files (<tt>.dll</tt>/<tt>.so</tt>/<tt>.jnilib</tt> files).

You have a choice of JOGL versions to download. The [{{SERVER}}/deployment/jogamp-current/archive/ latest stable version] is the safest, but lags behind in features. The [{{SERVER}}/deployment/autobuilds/master/ latest automatic build] contains all checked-in code, but may be failing some tests.

= Downloading the latest stable version =

== Fat Jar for all platforms ==
(excluding Android)

* [{{SERVER}}/deployment/jogamp-current/fat/jogamp-fat.jar jogamp-fat.jar]
* Demo files
** [{{SERVER}}/deployment/jogamp-current/fat/jogl-demos.jar jogl-demos.jar]
** [{{SERVER}}/deployment/jogamp-current/fat/jogl-fonts-p0.jar jogl-fonts-p0.jar]

=== Using the fat jar ===
Download all three jar files into a folder as described above and launch e.g.
''java -cp jogamp-fat.jar:jogl-demos.jar com.jogamp.opengl.demos.graph.ui.UISceneDemo03''

== Fat APK for Android ==
* See [[Android Packages]]
* [{{SERVER}}/deployment/jogamp-current/apk/ Latest APK files location]

=== Testing a single fat APK ===
A fat demo APK ''jogl-demos-fat-android-${arch}.apk'' resides inside the [{{SERVER}}/deployment/jogamp-current/apk/ APK release folder] and can be directly installed and tested on your device w/ developer mode enabled.

User are encouraged to merge the ''<module>-all-android-<arch>.apk'' or jar files with their own application.

== 7z all-in-one archive ==
Go to [{{SERVER}}/deployment/jogamp-current/archive/ this page] and download the all-in-one 7z archive file:

: [{{SERVER}}/deployment/jogamp-current/archive/jogamp-all-platforms.7z jogamp-all-platforms.7z]

=== Using the jogamp-all-platforms ===

After inflating the file with [http://www.7-zip.org/ 7zip], you will have the general directory structure:

<pre>
<jogamp-all-platforms>/
<jogamp-all-platforms>/etc/test.sh
<jogamp-all-platforms>/etc/test.bat
<jogamp-all-platforms>/etc/test_dbg.sh
<jogamp-all-platforms>/etc/test_dbg.bat
<jogamp-all-platforms>/jar/<module>.jar
<jogamp-all-platforms>/jar/<module>-natives-<os.and.arch>.jar
<jogamp-all-platforms>/lib/
<jogamp-all-platforms>/<module>-java-src.zip*
</pre>
Legend:
* [{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html#NativeJARFileNameConvention os.and.arch]
* module: gluegen, joal, jogl or jocl

Now you can '''test''' the ''archive'' as described
in [[Jogamp Versioning and Releases#Runtime Version Check|runtime version check]]
and [[Jogamp Versioning and Releases#Runtime Debug Logs|runtime debug test]].

If anything doesn't work as predicted, please follow our [[Jogl FAQ#Bugreports & Testing|bugreport guide]].

While keeping the above directory structure as-is, you can go ahead and
* add the non-native JAR files to your CLASSPATH (IDE, manual, ..)
* attach the java-source files to the non-native JAR files (IDE)

.. now you are set to start using JogAmp module in your project.

The above is detailed in [[Setting_up_a_JogAmp_project_in_your_favorite_IDE#Eclipse_IDE_project|Eclipse Project]]
and [[Setting_up_a_JogAmp_project_in_your_favorite_IDE#Eclipse_IDE_user_library|Eclipse User Library]].

= Downloading the latest aggregated autobuild =

Got to [{{SERVER}}/deployment/archive/master/?C=M;O=D this page] and navigate into the first folder,
which shall be the latest ''aggregated autobuild''.

Then navigate further down to '''archive''' and download the file '''jogamp-all-platforms.7z'''.

For example, on '''13-Mar-2013 20:19 CET''', the latest ''aggregated autobuild'' was:

[{{SERVER}}/deployment/archive/master/gluegen_646-joal_408-jogl_930-jocl_756/archive/jogamp-all-platforms.7z {{SERVER}}/deployment/archive/master/gluegen_646-joal_408-jogl_930-jocl_756/archive/jogamp-all-platforms.7z]

Now you can continue [[#Using the 7z jogamp-all-platforms archive|here]].

= Downloading the latest automatic build =

For the latest automatic build, we have to download gluegen and jogl separately.

First, go to [{{SERVER}}/deployment/autobuilds/master/?C=M;O=D this page] and click on the most recent <tt>gluegen-b*</tt> directory. Then download one of these files for each platform you're developing on:

: 32-bit Windows: <tt>gluegen-2.0-bvvv-20yymmdd-windows-i586.7z</tt>
: 64-bit Windows: <tt>gluegen-2.0-bvvv-20yymmdd-windows-amd64.7z</tt>
: 32/64-bit Mac OS X: <tt>gluegen-2.0-bvvv-20yymmdd-macosx-universal.7z</tt>
: 32-bit Linux: <tt>gluegen-2.0-bvvv-20yymmdd-linux-i586.7z</tt>
: 64-bit Linux: <tt>gluegen-2.0-bvvv-20yymmdd-linux-amd64.7z</tt>
: 32-bit Solaris: <tt>gluegen-2.0-bvvv-20yymmdd-solaris-i586.7z</tt>
: 64-bit Solaris: <tt>gluegen-2.0-bvvv-20yymmdd-solaris-amd64.7z</tt>

Then, go back to [{{SERVER}}/deployment/autobuilds/master/?C=M;O=D this page] and click on the most recent <tt>jogl-b*</tt> directory. Then download one of these files for each platform you're developing on:

: 32-bit Windows: <tt>jogl-2.0-bvvv-20yymmdd-windows-i586.7z</tt>
: 64-bit Windows: <tt>jogl-2.0-bvvv-20yymmdd-windows-amd64.7z</tt>
: 32/64-bit Mac OS X: <tt>jogl-2.0-bvvv-20yymmdd-macosx-universal.7z</tt>
: 32-bit Linux: <tt>jogl-2.0-bvvv-20yymmdd-linux-i586.7z</tt>
: 64-bit Linux: <tt>jogl-2.0-bvvv-20yymmdd-linux-amd64.7z</tt>
: 32-bit Solaris: <tt>jogl-2.0-bvvv-20yymmdd-solaris-i586.7z</tt>
: 64-bit Solaris: <tt>jogl-2.0-bvvv-20yymmdd-solaris-amd64.7z</tt>

Note that these automatic builds may not have passed all the regression tests. You can check the test results on the [https://jogamp.org/chuck/ build server] to make sure you're not downloading a broken build.

== Native JARs vs. native library files ==

JOGL uses native libraries to interface with each platform's OpenGL library. You can either download these native libraries wrapped up in JAR files (the "native JARs" option), or you can download them as separate <tt>.dll</tt>/<tt>.so</tt>/<tt>.jnilib</tt> files (the "native library files" option).

When using native JARs, JOGL automatically unzips the native JARs at startup into a temporary directory, then loads the resulting <tt>.dll</tt>/<tt>.so</tt>/<tt>.jnilib</tt> files from there. When using native library files, JOGL just loads them directly from where they sit, with no unzipping.

Using native JARs is usually easiest, since there are fewer files to manage and it allows different platforms' native library files to coexist in the same directory. Only use the native library files directly if you need fine control over native library file placement or if your app doesn't have permissions to create temporary directories.

See [[JogAmp JAR File Handling|JogAmp JAR File Handling]], for details on native JAR files and custom JAR bundling.

== Unzipping the files ==

Unzip all the downloaded files with [http://www.7-zip.org/ 7zip]. An unzipped file has this general directory structure:

<pre>
<archive>/
<archive>/jar/
<archive>/lib/
<archive>/<module>-java-src.zip*
</pre>

Now you may copy the required JARs out of each <tt>jar</tt> folder and the native library files (if you're using them) out of each <tt>lib</tt> folder. For a full desktop installation using native JARs, here are the files you need. Note that the native JAR names are different for each platform, so you can use some or all of the native JARs together to create a multi-platform installation.

{|cellpadding="4" cellspacing="0"
!align="left"|64-bit Windows
!align="left"|64-bit Linux
!align="left"|32/64-bit Mac
|-
|<tt>gluegen-rt.jar</tt>||<tt>gluegen-rt.jar</tt>||<tt>gluegen-rt.jar</tt>
|-
|<tt>jogl-all.jar</tt>||<tt>jogl-all.jar</tt>||<tt>jogl-all.jar</tt>
|-
|<tt>gluegen-java-src.zip</tt>||<tt>gluegen-java-src.zip</tt>||<tt>gluegen-java-src.zip</tt>
|-
|<tt>jogl-java-src.zip</tt>||<tt>jogl-java-src.zip</tt>||<tt>jogl-java-src.zip</tt>
|-
|<tt>gluegen-rt-natives-windows-amd64.jar</tt>||<tt>gluegen-rt-natives-linux-amd64.jar</tt>||<tt>gluegen-rt-natives-macosx-universal.jar</tt>
|-
|<tt>jogl-all-natives-windows-amd64.jar</tt>||<tt>jogl-all-natives-linux-amd64.jar</tt>||<tt>jogl-all-natives-macosx-universal.jar</tt>
|}
<br/>
{|cellpadding="4" cellspacing="0"
!align="left"|32-bit Windows
!align="left"|32-bit Linux
|-
|<tt>gluegen-rt.jar</tt>||<tt>gluegen-rt.jar</tt>
|-
|<tt>jogl-all.jar</tt>||<tt>jogl-all.jar</tt>||
|-
|<tt>gluegen-java-src.zip</tt>||<tt>gluegen-java-src.zip</tt>||
|-
|<tt>jogl-java-src.zip</tt>||<tt>jogl-java-src.zip</tt>||
|-
|<tt>gluegen-rt-natives-windows-i586.jar</tt>||<tt>gluegen-rt-natives-linux-i586.jar</tt>
|-
|<tt>jogl-all-natives-windows-i586.jar</tt>||<tt>jogl-all-natives-linux-i586.jar</tt>
|}

<br/>
For a full desktop installation using native library files, here are the files you need. Note that the native library files have the same names for 32-bit and 64-bit platforms, so 32-bit and 64-bit platforms can't coexist in one installation.
<br/>

{|cellpadding="4" cellspacing="0"
!align="left"|Windows
!align="left"|Linux
!align="left"|Mac
|-
|<tt>gluegen-rt.jar</tt>||<tt>gluegen-rt.jar</tt>||<tt>gluegen-rt.jar</tt>
|-
|<tt>jogl-all.jar</tt>||<tt>jogl-all.jar</tt>||<tt>jogl-all.jar</tt>
|-
|<tt>gluegen-java-src.zip</tt>||<tt>gluegen-java-src.zip</tt>||<tt>gluegen-java-src.zip</tt>
|-
|<tt>jogl-java-src.zip</tt>||<tt>jogl-java-src.zip</tt>||<tt>jogl-java-src.zip</tt>
|-
|<tt>gluegen-rt.dll</tt>||<tt>libgluegen-rt.so</tt>||<tt>libgluegen-rt.jnilib</tt>
|-
|<tt>jogl_desktop.dll</tt>||<tt>libjogl_desktop.so</tt>||<tt>libjogl_desktop.jnilib</tt>
|-
|<tt>nativewindow_awt.dll</tt>||<tt>libnativewindow_awt.so</tt>||<tt>libnativewindow_awt.jnilib</tt>
|-
|<tt>nativewindow_win32.dll</tt>||<tt>libnativewindow_x11.so</tt>||<tt>libnativewindow_macosx.jnilib</tt>
|-
|<tt>newt.dll</tt>||<tt>libnewt.so</tt>||<tt>libnewt.jnilib</tt>
|}

= Maven =
Alternatively, the Jogamp packages are available through Maven.

See the [[Setting_up_a_JogAmp_project_in_your_favorite_IDE#Maven|maven instructions]] for a guide to using Jogamp in
Maven projects.

= More information =

JogAmp follows a [[Jogamp_Versioning_and_Releases#Release_Classification|release scheme]],
which describes the following locations to download the 7z archives from:

* [{{SERVER}}/deployment/ Deployment Home]
** [{{SERVER}}/deployment/jogamp-current/archive/ Signed Release]
** [{{SERVER}}/deployment/jogamp-next/archive/ Signed Candidate]
** [{{SERVER}}/deployment/jogamp-next/v2.0-rc3archive/ Specific Version]

[{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html JOGL Deployment] describes the content of the 7z archive files.

These installations contain all of JOGL. If you want to remove parts you don't use, see [{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html JOGL Deployment] for more information.

Main Page

2025-08-31T18:48:35Z

Sgothel:

__NOTOC__
{| width="100%"
|-
|
<div>
Welcome to the [{{SERVER}}/ JogAmp] wiki. It documents JOGL, JOCL and JOAL, the cross-platform bindings to the OpenGL, OpenCL, and OpenAL APIs.
</div>
|-
|
{| style="width: 100%;"
|-
|style="vertical-align: top; padding: 5px; width: 50%"|<h3>Getting Started</h3>
*[[Downloading and installing JOGL|Downloading and installing]]
**[[Jogamp Versioning and Releases|Versioning and Releases]]
*[[Setting up a JogAmp project in your favorite IDE|Setting up a JogAmp project in your favorite IDE]]
*[[Jogamp SCM Repositories|Source Code Repositories]]
*[[SW Tracking|Tracking Reports]]
*[{{SERVER}}/chuck/ Build and Test Server]
|style="vertical-align: top; padding: 5px; width: 50%"|<h3>Community</h3>
*[[How to Contribute|Contribute to JogAmp]]
*[[How to Build|Build JogAmp]]
*[[Maintainer and Contacts]]
*[[Jogl FAQ#Bugreports & Testing|Report a bug]]
**[{{SERVER}}/bugzilla/ Bugzilla]
*[http://forum.jogamp.org/ Ask a question in the forum]
*[[chatroom|JogAmp IRC]]
|}
|-

{| style=" width: 100%;"
|-
|colspan="2"|<h1>JogAmp Modules</h1>
|-
|style="vertical-align: top; padding: 5px; width: 50%"|<h3>Roadmaps</h3>
* ''[[SW Tracking Report Feature Objectives Overview|Feature & Objectives]], [[SW Tracking Report Objectives undetermined release|tbd]], [[SW Tracking Report Objectives for the release 3.0.0|3.0.0]], [[SW Tracking Report Objectives for the release 2.7.0|2.7.0]]''
* '''[[SW Tracking Report Objectives for the release 2.6.0|2.6.0]] (last stable)''', [[SW Tracking Report Objectives for the release 2.5.0|2.5.0]], [[SW Tracking Report Objectives for the release 2.4.0|2.4.0]], [[SW Tracking Report Objectives for the release 2.3.2|2.3.2]], [[SW Tracking Report Objectives for the release 2.3.1|2.3.1]], [[SW Tracking Report Objectives for the release 2.3.0|2.3.0]]
* [[SW Tracking Report Objectives for the release 2.2.4|2.2.4]], [[SW Tracking Report Objectives for the release 2.2.3|2.2.3]], [[SW Tracking Report Objectives for the release 2.2.2|2.2.2]], [[SW Tracking Report Objectives for the release 2.2.1|2.2.1]], [[SW Tracking Report Objectives for the release 2.2.0|2.2.0]]
* [[SW Tracking Report Objectives for the release 2.1.5|2.1.5]], [[SW Tracking Report Objectives for the release 2.1.4|2.1.4]], [[SW Tracking Report Objectives for the release 2.1.3|2.1.3]], [[SW Tracking Report Objectives for the release 2.1.2|2.1.2]], [[SW Tracking Report Objectives for the release 2.1.1|2.1.1]], [[SW Tracking Report Objectives for the release 2.1.0|2.1.0]]
* [[SW Tracking Report Objectives for the release 2.0.2 of JOGL|2.0.2]]
|-

|style="vertical-align: top; padding: 5px; width: 50%"|<h3>JOGL</h3>
*[[Jogl Overview|Overview]] [ [{{SERVER}}/jogl/doc/Overview-OpenGL-Evolution-And-JOGL.html OpenGL Evolution & JOGL] ]
*[[Why Instance Design|Why Instance Design]]
*[[Jogl Tutorial|Tutorial]]
*[[Jogl FAQ|FAQ]]
*[{{SERVER}}/git/?p=jogl.git;a=blob;f=LICENSE.txt License]
*API Doc [ [{{SERVER}}/deployment/jogamp-next/javadoc/jogl/javadoc/ Public], Specs [ [{{SERVER}}/deployment/jogamp-next/javadoc/jogl/javadoc_nativewindow_spec/ Nativewindow], [{{SERVER}}/deployment/jogamp-next/javadoc/jogl/javadoc_jogl_spec/ JOGL] ] ]
*[[Jogl API Overview|API Overview]]
**[[GL Debug Output|GL Debug Output]]
*[{{SERVER}}/jogl/doc/HowToBuild.html How to Build JOGL]

|style="vertical-align: top; padding: 5px; width: 50%"|<h3>JOCL</h3>
*[[JOCL Overview|Overview]]
*[[JOCL Tutorial|Tutorial]]
*[[JOCL FAQ|FAQ]]
*[{{SERVER}}/git/?p=jocl.git;a=blob;f=LICENSE License]
*[{{SERVER}}/deployment/jogamp-next/javadoc/jocl/javadoc/ API Doc]
*[{{SERVER}}/jocl/doc/HowToBuild.html How to Build JOCL]
|-
|style="vertical-align: top; padding: 5px; width: 50%"|<h3>JOAL</h3>
*[[Joal Overview|Overview]]
*[[Joal Tutorial|Tutorial]]
*[[Joal FAQ|FAQ]]
*[{{SERVER}}/git/?p=joal.git;a=blob;f=LICENSE.txt License]
*API Doc [ [{{SERVER}}/deployment/jogamp-next/javadoc/joal/javadoc/ Public], [{{SERVER}}/deployment/jogamp-next/javadoc/joal/javadoc_dev/ Internal] ]

|style="vertical-align: top; padding: 5px; width: 50%"|<h3>GlueGen</h3>
* [[GlueGen_Wiki|Overview]]
* [{{SERVER}}/git/?p=gluegen.git;a=blob;f=LICENSE.txt License]
* [{{SERVER}}/deployment/jogamp-next/javadoc/gluegen/javadoc/ GlueGen Java™ API-Doc]
* [{{SERVER}}/gluegen/doc/GlueGen_Mapping.html GlueGen Native Data & Function Mapping]
* [{{SERVER}}/gluegen/doc/manual/ GlueGen Manual]
* [{{SERVER}}/gluegen/doc/HowToBuild.html How To Build]
|}

{| style=" width: 100%;"
|-
|colspan="2"|<h1>Related Projects</h1>
|-
|style="vertical-align: top; padding: 5px; width: 50%"|<h3>Java3D</h3>
*[[Java3D Overview|Overview]]
*[[Downloading and installing Java3D|Downloading and installing]]
*[[Java3D Tutorial|Tutorial]]
*[[Java3D API Documentation|API Documentation]]
*[[Java3D FAQ|FAQ]]
|style="vertical-align: top; padding: 5px; width: 50%"|<h3>Ji Gong</h3>
*[[Ji Gong Overview|Overview]]
*[[Ji Gong Motivation|Motivation]]
*[[Ji Gong FAQ|FAQ]]
|-
|style="vertical-align: top; padding: 5px; width: 50%"|<h3>Source Certification Contract (SCC)</h3>
*[[SCC Overview|Overview]]
*[{{SERVER}}/bugzilla/showdependencytree.cgi?id=1368&hide_resolved=0 Bugzilla Dependency Tree]
*[{{SERVER}}/bugzilla/show_bug.cgi?id=1368 Bugzilla Parent Entry]
*[[SCC FAQ|FAQ]]
|style="vertical-align: top; padding: 5px; width: 50%"|<h3>Ardor3D</h3>
*[[Ardor3D Overview|Overview]]
*[[Ardor3D Tutorial|Tutorial]]
*[http://jogamp.org/deployment/ardor3d/javadoc/ API Documentation]
*[[Ardor3D FAQ|FAQ]]
|}

Jogamp Versioning and Releases

2025-08-31T18:41:06Z

Sgothel: /* Releases */

__TOC__

== Semantic Version Numbers ==

Given a version number MAJOR.MINOR.PATCH, increment the:

* MAJOR version indicates major incompatible API changes,
* MINOR version indicates minor incompatible API changes, and
* PATCH version indicates backwards-compatible bug fixes or added backwards-compatible functionality, i.e. these versions are binary compatible and a drop-in replacement.

Above semantics describe binary compatibility,
i.e. whether a new version can be used without recompilation (PATCH increment only).

Above semantics differ from [http://semver.org/ Semantic Versioning] since our MINOR
change allows minor incompatible API changes.

An example of a MAJOR incompatible API increment is JOGL 1.y.z -> 2.y.z,
where we thoroughly change the OO model, packaging, implementation or overall semantics.

Upgrading to a MINOR incompatible API increment of JogAmp
shall assure users that the model has not changed and the differences are indeed minor.

Hence a PATCH increment not only allows bugfixes but also
additional functionality, both backwards-compatible.

Note that manual test results showed that <i>none</i> of our 2.1 PATCH incrementing releases
were satisfying above semantics and hence incompatibilities could appear.
While this might be unlikely, the tests exposed at least removed protected fields or methods
at some uncommon places and hence compatibility was broken.

From version 2.2.0 on, we incorporate [https://github.com/jeluard/semantic-versioning semver]
in our JogAmp junit tests to guarantee automated validation and proper version increments.

See [{{SERVER}}/bugzilla/show_bug.cgi?id=1008 Bug 1008].

== Releases ==

* [[Release 2.6.0|2.6.0]], [[Release 2.5.0|2.5.0]], [[Release 2.4.0|2.4.0]]
* [[Release 2.3.2|2.3.2]], [[Release 2.3.1|2.3.1]], [[Release 2.3.0|2.3.0]]
* [[Release 2.2.4|2.2.4]], [[Release 2.2.3|2.2.3]], [[Release 2.2.2|2.2.2]], [[Release 2.2.1|2.2.1]], [[Release 2.2.0|2.2.0]]
* [[Release 2.1.5|2.1.5]], [[Release 2.1.4|2.1.4]], [[Release 2.1.3|2.1.3]], [[Release 2.1.2|2.1.2]], [[Release 2.1.1|2.1.1]], [[Release 2.1.0|2.1.0]]
* [[Release 2.0.2|2.0.2]]
** [[Release 2.0.2-rc12|2.0.2-rc12]],[[Release 2.0-rc11|2.0-rc11]],[[Release 2.0-rc10|2.0-rc10]], [[Release 2.0-rc9|2.0-rc9]], [[Release 2.0-rc8|2.0-rc8]], [[Release 2.0-rc7|2.0-rc7]], [[Release 2.0-rc6|2.0-rc6]], [[Release 2.0-rc5|2.0-rc5]], [[Release 2.0-rc4|2.0-rc4]], [[Release 2.0-rc3|2.0-rc3]], [[Release 2.0-rc2|2.0-rc2]], [[Release 2.0-rc1|2.0-rc1]]

[[Android Packages]]

=== Current Aliases ===

* [http://jogamp.org/deployment/jogamp-current/ jogamp-current] -> [http://jogamp.org/deployment/v2.5.0/ v2.5.0]
* [http://jogamp.org/deployment/jogamp-next/ jogamp-next] -> [http://jogamp.org/deployment/v2.5.0/ v2.5.0]
* [http://jogamp.org/deployment/webstart/ webstart] -> [http://jogamp.org/deployment/v2.5.0/ v2.5.0]
* [http://jogamp.org/deployment/webstart-next/ webstart-next] -> [http://jogamp.org/deployment/v2.5.0/ v2.5.0]

== Release Classification ==

Releases follow the above mentioned [[#Version_Classification|versioning]] scheme.

The following list is ordered from <i>stable and oldest</i> to <i>experimental and newest</i>.

=== [{{SERVER}}/deployment/jogamp-current/ Signed Release] ===
* This is our current signed release, IE a manual promoted and signed autobuild.
* It is suitable for JNLP and Applets (with or without JNLP).
* This is the <b>most stable and recommended</b> version.
* [{{SERVER}}/deployment/jogamp-current/archive/ Archive folder] containing [[#Release_and_Archived_Files|platform ZIP files]] for manual installation.
* [[Downloading and installing JOGL#Downloading the latest aggregated autobuild|this section]]
* See instructions for [[Downloading and installing JOGL#Downloading the latest stable version|downloading and installing]].

=== [{{SERVER}}/deployment/jogamp-next/ Signed Release Candidate] ===
* This is our signed release candidate, IE a manual promoted and signed autobuild.
* It is suitable for JNLP and Applets (with or without JNLP).
* [{{SERVER}}/deployment/jogamp-next/archive/ Platform ZIP archive's URL] for manual installation.
* [{{SERVER}}/deployment/jogamp-next/archive/ Archive folder] containing [[#Release_and_Archived_Files|platform ZIP files]] for manual installation.
* See instructions for [[Downloading and installing JOGL#Downloading the latest stable version|downloading and installing]].

=== [{{SERVER}}/deployment/v2.0-rc3/ Signed Release Specific Version] ===
* This is a specific signed release, IE a manual promoted autobuild.
* It is suitable for JNLP and Applets (with or without JNLP).
* [{{SERVER}}/deployment/v2.0-rc3/archive/ Archive folder] containing [[#Release_and_Archived_Files|platform ZIP files]] for manual installation.
* See instructions for [[Downloading and installing JOGL#Downloading the latest stable version|downloading and installing]].

=== [{{SERVER}}/deployment/archive/master/?C=M;O=D Latest Aggregated Autobuild] ===
* This is our latest aggregated autobuild, which we seem fit for broad testing and submitting a [[Jogl FAQ#Bugreports & Testing|bugreport]].
* It is not signed and hence not suitable for JNLP and Applets.
* See instructions for [[Downloading and installing JOGL#Downloading the latest aggregated autobuild|downloading and installing]].

=== [{{SERVER}}/deployment/autobuilds/ Autobuilds] ===
What others call <i>nightlies</i>, we call it autobuild.
Autobuilds are provided by our [{{SERVER}}/chuck/job/jogl/ Jenkins build server]:
* For [{{SERVER}}/chuck/job/jogl/ each project build reports] are available:
** [{{SERVER}}/chuck/job/jogl/lastSuccessfulBuild/ Last Successful JOGL Build]
** [{{SERVER}}/chuck/job/jogl/476/ JOGL Build 476]
* They are [{{SERVER}}/chuck/job/jogl/476/changes#detail0 triggered by git commits]
* Here is a [{{SERVER}}/chuck/job/jogl/changes list of all JOGL changes].
* These builds are also tested on all supported platforms automatically with junit, see a [{{SERVER}}/chuck/job/jogl/label=win7-x86_64-nvida/lastCompletedBuild/testReport/ complete test report from one platform].
* [{{SERVER}}/deployment/autobuilds/master/jogl-b485-2011-09-20_08-30-36/ Autobuild URL] containing [[#Autobuild_Files|platform ZIP files]] for manual installation.

=== [{{SERVER}}/deployment/archive/ Archived builds] ===
* Contains archived builds and releases.
* May be signed.
* [{{SERVER}}/deployment/archive/rc/gluegen_28-joal_17-jogl_41-jocl_25/archive/ archive URL] containing [[#Release_and_Archived_Files|platform ZIP files]] for manual installation.

== Version Classification ==

=== Version Fingerprint ===

You can get the [[Jogl FAQ#Get the Source Code|get the source code]] via git,
hence all references of a JogAmp module version boils down to:

* module base version
* git commit sha1 hash
* build number
* module OS and ARCH

We construct a full version string as follows:
<pre>
<module>-<base_version>-b<build_number>-<yyyymmdd>
</pre>

=== artifact.properties ===

The version fingerprint is available in the
[{{SERVER}}/deployment/autobuilds/master/jogl-b485-2011-09-20_08-30-36/artifact.properties artifact.properties] file:
<pre>
gluegen.build.branch=origin/master
gluegen.build.commit=3fec08a69de571cf2939e6028487faea8a23ccaa
gluegen.build.id=2013-11-01_05-57-23
gluegen.build.number=741
gluegen.build.version=2.1.2
jogl.build.branch=origin/master
jogl.build.commit=3ed74abaddb90cb537897b9928e923be50f7f99f
jogl.build.id=2013-11-01_19-08-47
jogl.build.number=1135
jogl.build.version=2.1.2
</pre>

We deploy artifacts.properties in the online [{{SERVER}}/deployment/autobuilds/master/jogl-b485-2011-09-20_08-30-36/ build folder]
and within the platform ZIP archives.

=== JAR Manifest ===

The version fingerprint is also included within each JAR Manifest file,
where the Specification-Version equals the module base version
and the Implementation-Version equals the above mentioned full version string
<pre>
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.8.2
Created-By: 1.7.0_45-b18 (Oracle Corporation)
Application-Name: Java Bindings for OpenGL
Specification-Title: Java Bindings for OpenGL API Specification
Specification-Version: 2.1
Specification-Vendor: JogAmp Community
Implementation-Title: Java Bindings for OpenGL Runtime Environment
Implementation-Version: 2.1.2
Implementation-Build: 2.1-b1135-20131101
Implementation-Branch: origin/master
Implementation-Commit: 3ed74abaddb90cb537897b9928e923be50f7f99f
Implementation-Vendor: JogAmp Community
Implementation-URL: http://jogamp.org/
Extension-Name: javax.media.opengl
Implementation-Vendor-Id: com.jogamp
Trusted-Library: true
Permissions: all-permissions
Codebase: *.jogamp.org
</pre>

Each module has also a base version, like major and minor, ie 2.0,
which we may change to emphasize major feature and API changes.

==== Runtime Version Check ====

Each module has a build in [http://jogamp.org/deployment/jogamp-next/javadoc/gluegen/javadoc/com/jogamp/common/util/JogampVersion.html JogampVersion] specialization with a static <code>getInstance()</code> method to access the singleton instance,
eg. for the [http://jogamp.org/deployment/jogamp-next/javadoc/gluegen/javadoc/com/jogamp/common/GlueGenVersion.html#getInstance%28%29 GlueGenVersion] or [http://jogamp.org/deployment/jogamp-next/javadoc/jogl/javadoc/com/jogamp/opengl/JoglVersion.html#getInstance%28%29 JoglVersion]. You may utilize the version information from within your application in a programmatic manner. For the latter you may find the [http://jogamp.org/deployment/jogamp-next/javadoc/gluegen/javadoc/com/jogamp/common/os/Platform.html Platform] information useful as well.

Each module's [http://jogamp.org/deployment/jogamp-next/javadoc/gluegen/javadoc/com/jogamp/common/util/JogampVersion.html JogampVersion] specialization also contain a static main entry allowing you to retrieve the version information at runtime as described below.

When invoked, ie via JOGL's platform ZIP file:
* sh etc/test.sh (Unixoid), or
* etc\test.bat (Windows)
you will see the full dump of the runtime platform and the above mentioned version footprint.

<pre>
-----------------------------------------------------------------------------------------------------
Platform: LINUX / Linux 3.11.6-x64-k10-nlb-jau01 (3.11.6), amd64 (arch), GENERIC_ABI, 8 cores
MachineDescription: runtimeValidated true, littleEndian true, 32Bit false, primitive size / alignment:
int8 1 / 1, int16 2 / 2
int 4 / 4, long 8 / 8
int32 4 / 4, int64 8 / 8
float 4 / 4, double 8 / 8, ldouble 16 / 16
pointer 8 / 8, page 4096
Platform: Java Version: 1.7.0_45 (1.7.0u45), VM: Java HotSpot(TM) 64-Bit Server VM, Runtime: Java(TM) SE Runtime Environment
Platform: Java Vendor: Oracle Corporation, http://java.oracle.com/, JavaSE: true, Java6: true, AWT enabled: true
-----------------------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------------------
Package: com.jogamp.common
Extension Name: com.jogamp.common
Specification Title: GlueGen Java Bindings Generator
Specification Vendor: JogAmp Community
Specification Version: 2.1
Implementation Title: GlueGen Run-Time
Implementation Vendor: JogAmp Community
Implementation Vendor ID: com.jogamp
Implementation URL: http://jogamp.org/
Implementation Version: 2.1.2
Implementation Build: 2.1-b741-20131101
Implementation Branch: origin/master
Implementation Commit: 3fec08a69de571cf2939e6028487faea8a23ccaa
-----------------------------------------------------------------------------------------------------
Package: javax.media.opengl
Extension Name: javax.media.opengl
Specification Title: Java Bindings for OpenGL API Specification
Specification Vendor: JogAmp Community
Specification Version: 2.1
Implementation Title: Java Bindings for OpenGL Runtime Environment
Implementation Vendor: JogAmp Community
Implementation Vendor ID: com.jogamp
Implementation URL: http://jogamp.org/
Implementation Version: 2.1.2
Implementation Build: 2.1-b1135-20131101
Implementation Branch: origin/master
Implementation Commit: 3ed74abaddb90cb537897b9928e923be50f7f99f
-----------------------------------------------------------------------------------------------------

GLProfiles on device X11GraphicsDevice[type .x11, connection :0, unitID 0, handle 0x0, owner false, ResourceToolkitLock[obj 0x207fd4ec, isOwner false, <2873e29f, 50234978>[count 0, qsz 0, owner <NULL>]]]
Natives
GL4bc true [4.4 (Compat profile, arb, ES2 compat, ES3 compat, FBO, hardware)]
GL4 true [4.4 (Core profile, arb, ES2 compat, ES3 compat, FBO, hardware)]
GLES3 false
GL3bc true [4.4 (Compat profile, arb, ES2 compat, ES3 compat, FBO, hardware)]
GL3 true [4.4 (Core profile, arb, ES2 compat, ES3 compat, FBO, hardware)]
GL2 true [4.4 (Compat profile, arb, ES2 compat, ES3 compat, FBO, hardware)]
GLES2 true [2.0 (ES profile, ES2 compat, FBO, software)]
GLES1 true [1.0 (ES profile, FP32 compat, software)]
Count 7 / 8
Common
GL4ES3 true
GL2GL3 true
GL2ES2 true
GL2ES1 true
Mappings
GL2ES2 GLProfile[GL2ES2/GL4.hw]
GL2ES1 GLProfile[GL2ES1/GL4bc.hw]
GL2 GLProfile[GL2/GL4bc.hw]
GL4 GLProfile[GL4/GL4.hw]
GL3 GLProfile[GL3/GL4.hw]
GL4bc GLProfile[GL4bc/GL4bc.hw]
GLES2 GLProfile[GLES2/GLES2.sw]
GLES1 GLProfile[GLES1/GLES1.sw]
GL4ES3 GLProfile[GL4ES3/GL4.hw]
GL2GL3 GLProfile[GL2GL3/GL4bc.hw]
GL3bc GLProfile[GL3bc/GL4bc.hw]
default GLProfile[GL4bc/GL4bc.hw]
Count 11 / 12

Desktop Capabilities:
GLCaps[glx vid 0x21, fbc 0x105: rgba 8/8/8/0, opaque, accum-rgba 16/16/16/16, dp/st/ms 24/8/0, dbl, mono , hw, GLProfile[GL4bc/GL4bc.hw], on-scr[fbo, pbuffer, bitmap]]
.....

Requesting: GLCaps[rgba 8/8/8/0, opaque, accum-rgba 0/0/0/0, dp/st/ms 16/0/0, dbl, mono , hw, GLProfile[GL4bc/GL4bc.hw], on-scr[.]]
-----------------------------------------------------------------------------------------------------
X11GraphicsDevice[type .x11, connection :0]:
Natives
GL4bc true [4.4 (Compat profile, arb, ES2 compat, ES3 compat, FBO, hardware)]
GL4 true [4.4 (Core profile, arb, ES2 compat, ES3 compat, FBO, hardware)]
GLES3 false
GL3bc true [4.4 (Compat profile, arb, ES2 compat, ES3 compat, FBO, hardware)]
GL3 true [4.4 (Core profile, arb, ES2 compat, ES3 compat, FBO, hardware)]
GL2 true [4.4 (Compat profile, arb, ES2 compat, ES3 compat, FBO, hardware)]
GLES2 true [2.0 (ES profile, ES2 compat, FBO, software)]
GLES1 true [1.0 (ES profile, FP32 compat, software)]
Count 7 / 8
Common
GL4ES3 true
GL2GL3 true
GL2ES2 true
GL2ES1 true
Mappings
GL2ES2 GLProfile[GL2ES2/GL4.hw]
GL2ES1 GLProfile[GL2ES1/GL4bc.hw]
GL2 GLProfile[GL2/GL4bc.hw]
GL4 GLProfile[GL4/GL4.hw]
GL3 GLProfile[GL3/GL4.hw]
GL4bc GLProfile[GL4bc/GL4bc.hw]
GLES2 GLProfile[GLES2/GLES2.sw]
GLES1 GLProfile[GLES1/GLES1.sw]
GL4ES3 GLProfile[GL4ES3/GL4.hw]
GL2GL3 GLProfile[GL2GL3/GL4bc.hw]
GL3bc GLProfile[GL3bc/GL4bc.hw]
default GLProfile[GL4bc/GL4bc.hw]
Count 11 / 12

GL Profile GLProfile[GL4bc/GL4bc.hw]
GL Version 4.4 (Compat profile, arb, ES2 compat, ES3 compat, FBO, hardware) - 4.4.0 NVIDIA 331.13 [GL 4.4.0, vendor 331.13.0 (NVIDIA 331.13)]
Quirks []
Impl. class jogamp.opengl.gl4.GL4bcImpl
GL_VENDOR NVIDIA Corporation
GL_RENDERER GeForce GTX 660/PCIe/SSE2
GL_VERSION 4.4.0 NVIDIA 331.13
GLSL true, has-compiler-func: true, version: 4.40 NVIDIA via Cg compiler / 4.40.0
GL FBO: basic true, full true
GL_EXTENSIONS 292
GLX_EXTENSIONS 28
-----------------------------------------------------------------------------------------------------
Requested: GLCaps[rgba 8/8/8/0, opaque, accum-rgba 0/0/0/0, dp/st/ms 16/0/0, dbl, mono , hw, GLProfile[GL4bc/GL4bc.hw], on-scr[.]]
Chosen : GLCaps[glx vid 0x27, fbc 0x10d: rgba 8/8/8/0, opaque, accum-rgba 16/16/16/16, dp/st/ms 24/0/0, dbl, mono , hw, GLProfile[GL4bc/GL4bc.hw], on-scr[.]]
GL impl. class jogamp.opengl.gl4.GL4bcImpl
GL4ES3 retrieved, impl. class jogamp.opengl.gl4.GL4bcImpl
GL3 retrieved, impl. class jogamp.opengl.gl4.GL4bcImpl

</pre>
The dump is hold in the file <pre>test.log</pre> which you should send to us in case of a bugreport.

===== Runtime Debug Logs =====

You may also like to send us the debug version:
* sh etc/test_dbg.sh (Unixoid), or
* etc\test_dbg.bat (Windows)
which produces the file <pre>test_dbg.log</pre> and should be send to us to complete the bugreport as well.

==== Retrieve Release Version Tag from GIT Hash ====

git-show-tags-of-commit.sh
<pre>
#! /bin/sh

sha1=$1
shift

git show-ref --tags -d | grep ^$sha1 | sed -e 's,.* refs/tags/,,' -e 's/\^{}//'
</pre>

JOGL example:
<pre>
> git-show-tags-of-commit.sh 9ff0b0dafea2a03a915c97eb1513c39c27b6a7ae
v2.0-rc8
</pre>

GlueGen example:
<pre>
> git-show-tags-of-commit.sh 4ce601b38ca8418eddbe8cca4d531e6161fae26b
v2.0-rc7
v2.0-rc8
</pre>

== Maven ==
See the [[Setting_up_a_JogAmp_project_in_your_favorite_IDE#Maven|maven instructions]] for a guide to using Jogamp in
Maven projects.

== Autobuild Files ==
[{{SERVER}}/deployment/autobuilds/master/jogl-b485-2011-09-20_08-30-36/ Autobuild Platform ZIP files] for each module
follow the [[#Version_Classification|versioning]] scheme plus contain the platform identifier [{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html#NativeJARFileNameConvention OS and ARCH]:
<pre>
jogl-2.0-b210-20101110-linux-amd64.zip
</pre>

== Release and Archived Files ==
The [{{SERVER}}/deployment/jogamp-current/archive/ release archive folder]
contains 7z archive files for each platform containing all modules, ie. ''jogamp-linux-'''os.and.arch'''.7z''.
The '''os.and.arch''' refers to the
[{{SERVER}}/jogl/doc/deployment/JOGL-DEPLOYMENT.html#NativeJARFileNameConvention native file naming convention].

For example:
* <tt>jogamp-linux-amd64.7z</tt>
* <tt>jogamp-linux-i586.7z</tt>
* <tt>jogamp-windows-amd64.7z</tt>
* <tt>jogamp-windows-i586.7z</tt>

The folder also contains the Java API document ZIP files:
* <tt>gluegen-javadoc.zip</tt>
* <tt>jogl-javadoc.zip</tt>
* <tt>jocl-javadoc.zip</tt>
* <tt>joal-javadoc.zip</tt>

Release 2.6.0

2025-08-31T18:34:16Z

Sgothel:

Git Tag v2.6.0
* [{{Server}}/git/?p=gluegen.git;a=tag;h=refs/tags/v2.6.0 gluegen]
* [{{Server}}/git/?p=joal.git;a=tag;h=refs/tags/v2.6.0 joal]
* [{{Server}}/git/?p=jogl.git;a=tag;h=refs/tags/v2.6.0 jogl]
* [{{Server}}/git/?p=jocl.git;a=tag;h=refs/tags/v2.6.0 jocl]

Information
* [{{SERVER}}/gluegen/doc/JogAmpPlatforms-2.6.0.html Supported Platforms]
* [[SW Tracking Report Objectives for the release 2.6.0|Roadmap Release 2.6.0]]
* [{{SERVER}}/bugzilla//show_bug.cgi?id=1512 Release 2.6.0 Bugzilla Entry]
* [{{SERVER}}/bugzilla/buglist.cgi?list_id=2822&query_format=advanced&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED&version=2.6.0 Complete Bugzilla List of Version 2.6.0]
* [https://jausoft.com/blog/2025/08/27/jogamp-2-6-0-release-coming-up Blog entry w/ video]

General Artifacts
* [{{Server}}/deployment/v2.6.0/ Main entry, signed release]
* [{{Server}}/deployment/v2.6.0/fat/ Fat jar files including sources]
* [{{Server}}/deployment/v2.6.0/apk/ Android APK files including jogl-demos-fat-android-<arch>.apk to test]
* [{{Server}}/deployment/v2.6.0/archive/ Sources, ChangeLogs, Platform 7z Files, test results, ..]

Maven Artifacts
* version 2.6.0
* repo-url https://jogamp.org/deployment/maven/

CI Build Information:
* [{{Server}}/chuck/view/fwd/job/gluegen/987/ gluegen]
* [{{Server}}/chuck/view/fwd/job/joal/698/ joal]
* [{{Server}}/chuck/view/fwd/job/jogl/1548/ jogl]
* [{{Server}}/chuck/view/fwd/job/jocl/1191/ jocl]

[{{Server}}/deployment/v2.6.0/log/all.artifact.properties.sorted Detailed Version Information]

<pre>
gluegen.build.branch=origin/master
gluegen.build.commit=c06493e448332ace78721f5dfc3718c863783a12
gluegen.build.id=987
gluegen.build.number=987
gluegen.build.version=2.6.0
joal.build.branch=origin/master
joal.build.commit=a16d1e631091a3eb27f6f10b7e7d279df6b3e8e2
joal.build.id=698
joal.build.number=698
joal.build.version=2.6.0
joal-demos.build.branch=origin/master
joal-demos.build.commit=62cbae51663091db2984229abfc7d78b32cb99b5
joal-demos.build.id=554
joal-demos.build.number=554
jocl.build.branch=origin/master
jocl.build.commit=6d9649249b40e1ac880288bbad144649170092df
jocl.build.id=1191
jocl.build.number=1191
jocl.build.version=2.6.0
jocl-demos.build.branch=origin/master
jocl-demos.build.commit=03bc23b87d44b779b30022c19ee6cdfd16a5fd11
jocl-demos.build.id=1064
jocl-demos.build.number=1064
jogl.build.branch=origin/master
jogl.build.commit=f5964604d3e940c07c3e6af884f06b4eceb08dd4
jogl.build.id=1548
jogl.build.number=1548
jogl.build.version=2.6.0
jogl-demos.build.branch=origin/master
jogl-demos.build.commit=a2d87f82a81ff87555d09131fae638a9b8dc6dd7
jogl-demos.build.id=527
jogl-demos.build.number=527
</pre>

Release 2.6.0

2025-08-31T18:33:11Z

Sgothel:

Git Tag v2.6.0
* [{{Server}}/git/?p=gluegen.git;a=tag;h=refs/tags/v2.6.0 gluegen]
* [{{Server}}/git/?p=joal.git;a=tag;h=refs/tags/v2.6.0 joal]
* [{{Server}}/git/?p=jogl.git;a=tag;h=refs/tags/v2.6.0 jogl]
* [{{Server}}/git/?p=jocl.git;a=tag;h=refs/tags/v2.6.0 jocl]

Information
* [{{SERVER}}/gluegen/doc/JogAmpPlatforms-2.6.0.html Supported Platforms]
* [[SW Tracking Report Objectives for the release 2.6.0|Roadmap Release 2.6.0]]
* [{{SERVER}}/bugzilla//show_bug.cgi?id=1512 Release 2.6.0 Bugzilla Entry]
* [{{SERVER}}/bugzilla/buglist.cgi?list_id=2822&query_format=advanced&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED&version=2.6.0 Complete Bugzilla List of Version 2.6.0]
* [https://jausoft.com/blog/2025/08/27/jogamp-2-6-0-release-coming-up Blog entry w/ video]

General Artifacts
* [{{Server}}/deployment/v2.6.0/ Main entry, signed release]
* [{{Server}}/deployment/v2.6.0/fat/ Fat jar files including sources]
* [{{Server}}/deployment/v2.6.0/apk/ Android APK files including jogl-demos-fat-android-<arch>.apk to test]
* [{{Server}}/deployment/v2.6.0/archive/ Sources, ChangeLogs, Platform 7z Files, test results, ..]

Maven Artifacts
* version 2.6.0
* repo-url https://www.jogamp.org/deployment/maven/

CI Build Information:
* [{{Server}}/chuck/view/fwd/job/gluegen/987/ gluegen]
* [{{Server}}/chuck/view/fwd/job/joal/698/ joal]
* [{{Server}}/chuck/view/fwd/job/jogl/1548/ jogl]
* [{{Server}}/chuck/view/fwd/job/jocl/1191/ jocl]

[{{Server}}/deployment/v2.6.0/log/all.artifact.properties.sorted Detailed Version Information]

<pre>
gluegen.build.branch=origin/master
gluegen.build.commit=c06493e448332ace78721f5dfc3718c863783a12
gluegen.build.id=987
gluegen.build.number=987
gluegen.build.version=2.6.0
joal.build.branch=origin/master
joal.build.commit=a16d1e631091a3eb27f6f10b7e7d279df6b3e8e2
joal.build.id=698
joal.build.number=698
joal.build.version=2.6.0
joal-demos.build.branch=origin/master
joal-demos.build.commit=62cbae51663091db2984229abfc7d78b32cb99b5
joal-demos.build.id=554
joal-demos.build.number=554
jocl.build.branch=origin/master
jocl.build.commit=6d9649249b40e1ac880288bbad144649170092df
jocl.build.id=1191
jocl.build.number=1191
jocl.build.version=2.6.0
jocl-demos.build.branch=origin/master
jocl-demos.build.commit=03bc23b87d44b779b30022c19ee6cdfd16a5fd11
jocl-demos.build.id=1064
jocl-demos.build.number=1064
jogl.build.branch=origin/master
jogl.build.commit=f5964604d3e940c07c3e6af884f06b4eceb08dd4
jogl.build.id=1548
jogl.build.number=1548
jogl.build.version=2.6.0
jogl-demos.build.branch=origin/master
jogl-demos.build.commit=a2d87f82a81ff87555d09131fae638a9b8dc6dd7
jogl-demos.build.id=527
jogl-demos.build.number=527
</pre>

Release 2.6.0

2025-08-31T15:43:05Z

Sgothel:

Git Tag v2.6.0
* [{{Server}}/git/?p=gluegen.git;a=tag;h=refs/tags/v2.6.0 gluegen]
* [{{Server}}/git/?p=joal.git;a=tag;h=refs/tags/v2.6.0 joal]
* [{{Server}}/git/?p=jogl.git;a=tag;h=refs/tags/v2.6.0 jogl]
* [{{Server}}/git/?p=jocl.git;a=tag;h=refs/tags/v2.6.0 jocl]

Information
* [{{SERVER}}/gluegen/doc/JogAmpPlatforms-2.6.0.html Supported Platforms]
* [[SW Tracking Report Objectives for the release 2.6.0|Roadmap Release 2.6.0]]
* [{{SERVER}}/bugzilla//show_bug.cgi?id=1512 Release 2.6.0 Bugzilla Entry]
* [{{SERVER}}/bugzilla/buglist.cgi?list_id=2822&query_format=advanced&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED&version=2.6.0 Complete Bugzilla List of Version 2.6.0]
* [https://jausoft.com/blog/2025/08/27/jogamp-2-6-0-release-coming-up Blog entry w/ video]

General Artifacts
* [{{Server}}/deployment/v2.6.0/ Main entry, signed release]
* [{{Server}}/deployment/v2.6.0/fat/ Fat jar files including sources]
* [{{Server}}/deployment/v2.6.0/apk/ Android APK files including jogl-demos-fat-android-<arch>.apk to test]
* [{{Server}}/deployment/v2.6.0/archive/ Sources, ChangeLogs, Platform 7z Files, test results, ..]

Maven Artifacts
* version 2.6.0
* repo-url http://www.jogamp.org/deployment/maven/

CI Build Information:
* [{{Server}}/chuck/view/fwd/job/gluegen/987/ gluegen]
* [{{Server}}/chuck/view/fwd/job/joal/698/ joal]
* [{{Server}}/chuck/view/fwd/job/jogl/1548/ jogl]
* [{{Server}}/chuck/view/fwd/job/jocl/1191/ jocl]

[{{Server}}/deployment/v2.6.0/log/all.artifact.properties.sorted Detailed Version Information]

<pre>
gluegen.build.branch=origin/master
gluegen.build.commit=c06493e448332ace78721f5dfc3718c863783a12
gluegen.build.id=987
gluegen.build.number=987
gluegen.build.version=2.6.0
joal.build.branch=origin/master
joal.build.commit=a16d1e631091a3eb27f6f10b7e7d279df6b3e8e2
joal.build.id=698
joal.build.number=698
joal.build.version=2.6.0
joal-demos.build.branch=origin/master
joal-demos.build.commit=62cbae51663091db2984229abfc7d78b32cb99b5
joal-demos.build.id=554
joal-demos.build.number=554
jocl.build.branch=origin/master
jocl.build.commit=6d9649249b40e1ac880288bbad144649170092df
jocl.build.id=1191
jocl.build.number=1191
jocl.build.version=2.6.0
jocl-demos.build.branch=origin/master
jocl-demos.build.commit=03bc23b87d44b779b30022c19ee6cdfd16a5fd11
jocl-demos.build.id=1064
jocl-demos.build.number=1064
jogl.build.branch=origin/master
jogl.build.commit=f5964604d3e940c07c3e6af884f06b4eceb08dd4
jogl.build.id=1548
jogl.build.number=1548
jogl.build.version=2.6.0
jogl-demos.build.branch=origin/master
jogl-demos.build.commit=a2d87f82a81ff87555d09131fae638a9b8dc6dd7
jogl-demos.build.id=527
jogl-demos.build.number=527
</pre>

Release 2.6.0

2025-08-31T02:39:35Z

Sgothel:

Git Tag v2.6.0
* [{{Server}}/git/?p=gluegen.git;a=tag;h=refs/tags/v2.6.0 gluegen]
* [{{Server}}/git/?p=joal.git;a=tag;h=refs/tags/v2.6.0 joal]
* [{{Server}}/git/?p=jogl.git;a=tag;h=refs/tags/v2.6.0 jogl]
* [{{Server}}/git/?p=jocl.git;a=tag;h=refs/tags/v2.6.0 jocl]

Information
* [{{SERVER}}/gluegen/doc/JogAmpPlatforms-2.6.0.html Supported Platforms]
* [[SW Tracking Report Objectives for the release 2.6.0|Roadmap Release 2.6.0]]
* [{{SERVER}}/bugzilla//show_bug.cgi?id=1512 Release 2.6.0 Bugzilla Entry]
* [{{SERVER}}/bugzilla/buglist.cgi?list_id=2822&query_format=advanced&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED&version=2.6.0 Complete Bugzilla List of Version 2.6.0]
* [https://jausoft.com/blog/2025/08/27/jogamp-2-6-0-release-coming-up Blog entry w/ video]

General Artifacts
* [{{Server}}/deployment/v2.6.0/ Main entry, signed release]
* [{{Server}}/deployment/v2.6.0/fat/ Fat jar files including sources]
* [{{Server}}/deployment/v2.6.0/apk/ Android APK files including jogl-demos-fat-android-<arch>.apk to test]
* [{{Server}}/deployment/v2.6.0/archive/ Sources, ChangeLogs, Platform 7z Files, test results, ..]

Maven Artifacts
* version 2.6.0
* repo-url http://www.jogamp.org/deployment/maven/

CI Build Information:
* [{{Server}}/chuck/view/fwd/job/gluegen/987/ gluegen]
* [{{Server}}/chuck/view/fwd/job/joal/698/ joal]
* [{{Server}}/chuck/view/fwd/job/jogl/1548/ jogl]
* [{{Server}}/chuck/view/fwd/job/jocl/1191/ jocl]

[{{Server}}/deployment/v2.6.0/log/all.artifact.properties.sorted Detailed Version Information]

<pre>
gluegen.build.branch=origin/master
gluegen.build.commit=c06493e448332ace78721f5dfc3718c863783a12
gluegen.build.id=987
gluegen.build.number=987
gluegen.build.sha.classes=5201b95b2924bbac09519a922e7e7a26930f928ebc7ee0666c442d4a127ddbb5
gluegen.build.sha.natives=28de07778748b1c36e45b596563830181a3032ae507e09b8a68a68fbb0b7eef8
gluegen.build.sha.natives=44aaf0af1599ea491b947dd445fb9749b1c7a921daffbb529688836d8b8efd08
gluegen.build.sha.natives=8255743fd43ce87d89470d6a81176cf1188fe889a053427eaaaa9b4d889baa9d
gluegen.build.sha.natives=8f26171638c833b314f23c94c5880d5e86489e42d6534e1277c8d6d1fb8f1a90
gluegen.build.sha.natives=c1296426ba7cfb0d9dc7080878b74ece275ccf54e6091a117e639f88e2dc1926
gluegen.build.sha.natives=f46936374e6016170ae1400fb081a5609c38c997fb6dd619c1eea29c371be64c
gluegen.build.sha.sources=d7d4d9b4ac2337edb70516467403b2f7931567a436932f29399d72e65a91802a
gluegen.build.sha.sources=dd837463de04c023b9ca611f42095276b47f1e5cbd0d0ce97f5f91a427f07fb6
gluegen.build.version=2.6.0
joal.build.branch=origin/master
joal.build.commit=a16d1e631091a3eb27f6f10b7e7d279df6b3e8e2
joal.build.id=698
joal.build.number=698
joal.build.version=2.6.0
joal-demos.build.branch=origin/master
joal-demos.build.commit=62cbae51663091db2984229abfc7d78b32cb99b5
joal-demos.build.id=554
joal-demos.build.number=554
jocl.build.branch=origin/master
jocl.build.commit=6d9649249b40e1ac880288bbad144649170092df
jocl.build.id=1191
jocl.build.number=1191
jocl.build.version=2.6.0
jocl-demos.build.branch=origin/master
jocl-demos.build.commit=03bc23b87d44b779b30022c19ee6cdfd16a5fd11
jocl-demos.build.id=1064
jocl-demos.build.number=1064
jogl.build.branch=origin/master
jogl.build.commit=f5964604d3e940c07c3e6af884f06b4eceb08dd4
jogl.build.id=1548
jogl.build.number=1548
jogl.build.version=2.6.0
jogl-demos.build.branch=origin/master
jogl-demos.build.commit=a2d87f82a81ff87555d09131fae638a9b8dc6dd7
jogl-demos.build.id=527
jogl-demos.build.number=527
</pre>

Android Packages

2025-08-31T02:22:25Z

Sgothel:

= Direct download and installation of our Android Packages =

[http://jogamp.org/deployment/jogamp-current/apk Latest APK files location]

You may need to uninstall previous installed versions first!

== Single Fat Application Method ==
A fat demo APK ''jogl-demos-fat-android-${arch}.apk'' resides inside the [http://jogamp.org/deployment/jogamp-current/apk APK release folder] and can be directly installed and tested on your device w/ developer mode enabled.

User are encouraged to merge the ''<module>-all-android-<arch>.apk'' or jar files with their own application.

== Launcher Method ==
The following APKs must be installed to complete a JogAmp installation:
* [{{Server}}/deployment/jogamp-current/apk/jogamp-android-launcher.apk Launcher]
* ARM 32-bit >= armv6
** [{{Server}}/deployment/jogamp-current/apk/gluegen-rt-android-armv6.apk GlueGen]
** [{{Server}}/deployment/jogamp-current/apk/joal-android-armv6.apk JOAL]
** [{{Server}}/deployment/jogamp-current/apk/jogl-all-android-armv6.apk JOGL]
* ARM 64-bit >= aarch64
** [{{Server}}/deployment/jogamp-current/apk/gluegen-rt-android-aarch64.apk GlueGen]
** [{{Server}}/deployment/jogamp-current/apk/joal-android-aarch64.apk JOAL]
** [{{Server}}/deployment/jogamp-current/apk/jogl-all-android-aarch64.apk JOGL]

The following demo APK should be installed:
* [{{Server}}/deployment/jogamp-current/apk/joal-test-android.apk JOAL Tests]
* [{{Server}}/deployment/jogamp-current/apk/jogl-test-android.apk JOGL Tests]

= Download and installation via ''Google Play'' =

''' These versions are currently not maintained and are older versions! '''

The following APKs must be installed to complete a JogAmp installation:
* [https://play.google.com/store/apps/details?id=jogamp.android.launcher Launcher]
* [https://play.google.com/store/apps/details?id=com.jogamp.common GlueGen]
* [https://play.google.com/store/apps/details?id=com.jogamp.openal JOAL]
* [https://play.google.com/store/apps/details?id=javax.media.opengl JOGL]

The following demo APK should be installed:
* [https://play.google.com/store/apps/details?id=com.jogamp.opengl.test JOAL Tests]
* [https://play.google.com/store/apps/details?id=com.jogamp.opengl.test JOGL Tests]

Release 2.6.0

2025-08-31T02:07:22Z

Sgothel:

Git Tag v2.6.0
* [{{Server}}/git/?p=gluegen.git;a=tag;h=refs/tags/v2.6.0 gluegen]
* [{{Server}}/git/?p=joal.git;a=tag;h=refs/tags/v2.6.0 joal]
* [{{Server}}/git/?p=jogl.git;a=tag;h=refs/tags/v2.6.0 jogl]
* [{{Server}}/git/?p=jocl.git;a=tag;h=refs/tags/v2.6.0 jocl]

Information
* [{{SERVER}}/gluegen/doc/JogAmpPlatforms-2.6.0.html Supported Platforms]
* [[SW Tracking Report Objectives for the release 2.6.0|Roadmap Release 2.6.0]]
* [{{SERVER}}/bugzilla//show_bug.cgi?id=1512 Release 2.6.0 Bugzilla Entry]
* [{{SERVER}}/bugzilla/buglist.cgi?list_id=2822&query_format=advanced&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED&version=2.6.0 Complete Bugzilla List of Version 2.6.0]

General Artifacts
* [{{Server}}/deployment/v2.6.0/ Main entry, signed release]
* [{{Server}}/deployment/v2.6.0/fat/ Fat jar files including sources]
* [{{Server}}/deployment/v2.6.0/apk/ Android APK files including jogl-demos-fat-android-<arch>.apk to test]
* [{{Server}}/deployment/v2.6.0/archive/ Sources, ChangeLogs, Platform 7z Files, test results, ..]

Maven Artifacts
* version 2.6.0
* repo-url http://www.jogamp.org/deployment/maven/

CI Build Information:
* [{{Server}}/chuck/view/fwd/job/gluegen/987/ gluegen]
* [{{Server}}/chuck/view/fwd/job/joal/698/ joal]
* [{{Server}}/chuck/view/fwd/job/jogl/1548/ jogl]
* [{{Server}}/chuck/view/fwd/job/jocl/1191/ jocl]

[{{Server}}/deployment/v2.6.0/log/all.artifact.properties.sorted Detailed Version Information]

<pre>
gluegen.build.branch=origin/master
gluegen.build.commit=c06493e448332ace78721f5dfc3718c863783a12
gluegen.build.id=987
gluegen.build.number=987
gluegen.build.sha.classes=5201b95b2924bbac09519a922e7e7a26930f928ebc7ee0666c442d4a127ddbb5
gluegen.build.sha.natives=28de07778748b1c36e45b596563830181a3032ae507e09b8a68a68fbb0b7eef8
gluegen.build.sha.natives=44aaf0af1599ea491b947dd445fb9749b1c7a921daffbb529688836d8b8efd08
gluegen.build.sha.natives=8255743fd43ce87d89470d6a81176cf1188fe889a053427eaaaa9b4d889baa9d
gluegen.build.sha.natives=8f26171638c833b314f23c94c5880d5e86489e42d6534e1277c8d6d1fb8f1a90
gluegen.build.sha.natives=c1296426ba7cfb0d9dc7080878b74ece275ccf54e6091a117e639f88e2dc1926
gluegen.build.sha.natives=f46936374e6016170ae1400fb081a5609c38c997fb6dd619c1eea29c371be64c
gluegen.build.sha.sources=d7d4d9b4ac2337edb70516467403b2f7931567a436932f29399d72e65a91802a
gluegen.build.sha.sources=dd837463de04c023b9ca611f42095276b47f1e5cbd0d0ce97f5f91a427f07fb6
gluegen.build.version=2.6.0
joal.build.branch=origin/master
joal.build.commit=a16d1e631091a3eb27f6f10b7e7d279df6b3e8e2
joal.build.id=698
joal.build.number=698
joal.build.version=2.6.0
joal-demos.build.branch=origin/master
joal-demos.build.commit=62cbae51663091db2984229abfc7d78b32cb99b5
joal-demos.build.id=554
joal-demos.build.number=554
jocl.build.branch=origin/master
jocl.build.commit=6d9649249b40e1ac880288bbad144649170092df
jocl.build.id=1191
jocl.build.number=1191
jocl.build.version=2.6.0
jocl-demos.build.branch=origin/master
jocl-demos.build.commit=03bc23b87d44b779b30022c19ee6cdfd16a5fd11
jocl-demos.build.id=1064
jocl-demos.build.number=1064
jogl.build.branch=origin/master
jogl.build.commit=f5964604d3e940c07c3e6af884f06b4eceb08dd4
jogl.build.id=1548
jogl.build.number=1548
jogl.build.version=2.6.0
jogl-demos.build.branch=origin/master
jogl-demos.build.commit=a2d87f82a81ff87555d09131fae638a9b8dc6dd7
jogl-demos.build.id=527
jogl-demos.build.number=527
</pre>

SW Tracking Report Objectives for the release 2.6.0

2025-08-31T01:58:00Z

Sgothel:

List started on 2023-07-xx, concluding [[SW Tracking Report Objectives for the release 2.5.0|Release 2.5.0]] - '''Closed 2025-08-21''' - continuation @ [[SW Tracking Report Objectives for the release 2.7.0|Release 2.7.0]].

* [{{SERVER}}/gluegen/doc/JogAmpPlatforms-2.6.0.html Supported Platforms]
* [[Release 2.6.0|Release 2.6.0 Page]]
* [{{SERVER}}/bugzilla//show_bug.cgi?id=1512 Release 2.6.0 Bugzilla Entry]
* [{{SERVER}}/bugzilla/buglist.cgi?list_id=2822&query_format=advanced&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED&version=2.6.0 Complete Bugzilla List of Version 2.6.0]

= Features =

== Features to be classified for this release ==

<bugzilla>
{
"status":["UNCONFIRMED"],
"version":"2.6.0",
"cf_type":"FEATURE",
"include_fields":"id,product,component,priority,severity,status,summary"
}
</bugzilla>

== Features to implement for this release ==

<bugzilla>
{
"status":["IN_PROGRESS","CONFIRMED"],
"version":"2.6.0",
"cf_type":"FEATURE",
"include_fields":"id,product,component,priority,severity,status,summary"
}
</bugzilla>

== Features already implemented for this release ==

<bugzilla>
{
"status":["RESOLVED","VERIFIED"],
"version":"2.6.0",
"cf_type":"FEATURE",
"include_fields":"id,product,component,priority,severity,status,resolution,summary"
}
</bugzilla>

= Bugs =

== Bugs to be classified for this release ==

<bugzilla>
{
"status":["UNCONFIRMED"],
"version":"2.6.0",
"cf_type":["---", "DEFECT"],
"include_fields":"id,product,component,priority,severity,status,summary"
}
</bugzilla>

== Bugs to fix for this release ==

<bugzilla>
{
"status":["IN_PROGRESS","CONFIRMED"],
"version":"2.6.0",
"cf_type":["---", "DEFECT"],
"include_fields":"id,product,component,priority,severity,status,summary"
}
</bugzilla>

== Bugs already fixed for this release ==

<bugzilla>
{
"status":["RESOLVED","VERIFIED"],
"version":"2.6.0",
"cf_type":["---", "DEFECT"],
"include_fields":"id,product,component,priority,severity,status,resolution,summary"
}
</bugzilla>

Release 2.6.0

2025-08-31T01:54:46Z

Sgothel: Created page with "Git Tag v2.6.0 * [{{Server}}/git/?p=gluegen.git;a=tag;h=refs/tags/v2.6.0 gluegen] * [{{Server}}/git/?p=joal.git;a=tag;h=refs/tags/v2.6.0 joal] * [{{Server}}/git/?p=jogl.git;a=tag;h=refs/tags/v2.6.0 jogl] * [{{Server}}/git/?p=jocl.git;a=tag;h=refs/tags/v2.6.0 jocl] Information * [{{SERVER}}/gluegen/doc/JogAmpPlatforms-2.6.0.html Supported Platforms] * Roadmap Release 2.6.0 * [{{SERVER}}/bugzilla//show_bug.cgi?id=151..."

Git Tag v2.6.0
* [{{Server}}/git/?p=gluegen.git;a=tag;h=refs/tags/v2.6.0 gluegen]
* [{{Server}}/git/?p=joal.git;a=tag;h=refs/tags/v2.6.0 joal]
* [{{Server}}/git/?p=jogl.git;a=tag;h=refs/tags/v2.6.0 jogl]
* [{{Server}}/git/?p=jocl.git;a=tag;h=refs/tags/v2.6.0 jocl]

Information
* [{{SERVER}}/gluegen/doc/JogAmpPlatforms-2.6.0.html Supported Platforms]
* [[SW Tracking Report Objectives for the release 2.6.0|Roadmap Release 2.6.0]]
* [{{SERVER}}/bugzilla//show_bug.cgi?id=1512 Release 2.6.0 Bugzilla Entry]
* [{{SERVER}}/bugzilla/buglist.cgi?list_id=2822&query_format=advanced&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED&version=2.6.0 Complete Bugzilla List of Version 2.6.0]

General Artifacts
* [{{Server}}/deployment/v2.6.0/ Main entry, signed release]
* [{{Server}}/deployment/v2.6.0/fat/ Fat jar files including sources]
* [{{Server}}/deployment/v2.6.0/archive/ Sources, ChangeLogs, Platform 7z Files, test results, ..]

Maven Artifacts
* version 2.6.0
* repo-url http://www.jogamp.org/deployment/maven/

CI Build Information:
* [{{Server}}/chuck/view/fwd/job/gluegen/987/ gluegen]
* [{{Server}}/chuck/view/fwd/job/joal/698/ joal]
* [{{Server}}/chuck/view/fwd/job/jogl/1548/ jogl]
* [{{Server}}/chuck/view/fwd/job/jocl/1191/ jocl]

[{{Server}}/deployment/v2.6.0/log/all.artifact.properties.sorted Detailed Version Information]

<pre>
gluegen.build.branch=origin/master
gluegen.build.commit=c06493e448332ace78721f5dfc3718c863783a12
gluegen.build.id=987
gluegen.build.number=987
gluegen.build.sha.classes=5201b95b2924bbac09519a922e7e7a26930f928ebc7ee0666c442d4a127ddbb5
gluegen.build.sha.natives=28de07778748b1c36e45b596563830181a3032ae507e09b8a68a68fbb0b7eef8
gluegen.build.sha.natives=44aaf0af1599ea491b947dd445fb9749b1c7a921daffbb529688836d8b8efd08
gluegen.build.sha.natives=8255743fd43ce87d89470d6a81176cf1188fe889a053427eaaaa9b4d889baa9d
gluegen.build.sha.natives=8f26171638c833b314f23c94c5880d5e86489e42d6534e1277c8d6d1fb8f1a90
gluegen.build.sha.natives=c1296426ba7cfb0d9dc7080878b74ece275ccf54e6091a117e639f88e2dc1926
gluegen.build.sha.natives=f46936374e6016170ae1400fb081a5609c38c997fb6dd619c1eea29c371be64c
gluegen.build.sha.sources=d7d4d9b4ac2337edb70516467403b2f7931567a436932f29399d72e65a91802a
gluegen.build.sha.sources=dd837463de04c023b9ca611f42095276b47f1e5cbd0d0ce97f5f91a427f07fb6
gluegen.build.version=2.6.0
joal.build.branch=origin/master
joal.build.commit=a16d1e631091a3eb27f6f10b7e7d279df6b3e8e2
joal.build.id=698
joal.build.number=698
joal.build.version=2.6.0
joal-demos.build.branch=origin/master
joal-demos.build.commit=62cbae51663091db2984229abfc7d78b32cb99b5
joal-demos.build.id=554
joal-demos.build.number=554
jocl.build.branch=origin/master
jocl.build.commit=6d9649249b40e1ac880288bbad144649170092df
jocl.build.id=1191
jocl.build.number=1191
jocl.build.version=2.6.0
jocl-demos.build.branch=origin/master
jocl-demos.build.commit=03bc23b87d44b779b30022c19ee6cdfd16a5fd11
jocl-demos.build.id=1064
jocl-demos.build.number=1064
jogl.build.branch=origin/master
jogl.build.commit=f5964604d3e940c07c3e6af884f06b4eceb08dd4
jogl.build.id=1548
jogl.build.number=1548
jogl.build.version=2.6.0
jogl-demos.build.branch=origin/master
jogl-demos.build.commit=a2d87f82a81ff87555d09131fae638a9b8dc6dd7
jogl-demos.build.id=527
jogl-demos.build.number=527
</pre>

SW Tracking Report Objectives for the release 2.6.0

2025-08-27T14:51:20Z

Sgothel:

List started on 2023-07-xx, concluding [[SW Tracking Report Objectives for the release 2.5.0|Release 2.5.0]] - '''In Progress''' - continuation @ [[SW Tracking Report Objectives for the release 2.7.0|Release 2.7.0]].

* [{{SERVER}}/gluegen/doc/JogAmpPlatforms-2.6.0.html Supported Platforms]
* [{{SERVER}}/bugzilla//show_bug.cgi?id=1512 Release 2.6.0 Entry]
* [{{SERVER}}/bugzilla/buglist.cgi?list_id=2822&query_format=advanced&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED&version=2.6.0 Complete Bugzilla List of Version 2.6.0]

Warning: WIP

= Features =

== Features to be classified for this release ==

<bugzilla>
{
"status":["UNCONFIRMED"],
"version":"2.6.0",
"cf_type":"FEATURE",
"include_fields":"id,product,component,priority,severity,status,summary"
}
</bugzilla>

== Features to implement for this release ==

<bugzilla>
{
"status":["IN_PROGRESS","CONFIRMED"],
"version":"2.6.0",
"cf_type":"FEATURE",
"include_fields":"id,product,component,priority,severity,status,summary"
}
</bugzilla>

== Features already implemented for this release ==

<bugzilla>
{
"status":["RESOLVED","VERIFIED"],
"version":"2.6.0",
"cf_type":"FEATURE",
"include_fields":"id,product,component,priority,severity,status,resolution,summary"
}
</bugzilla>

= Bugs =

== Bugs to be classified for this release ==

<bugzilla>
{
"status":["UNCONFIRMED"],
"version":"2.6.0",
"cf_type":["---", "DEFECT"],
"include_fields":"id,product,component,priority,severity,status,summary"
}
</bugzilla>

== Bugs to fix for this release ==

<bugzilla>
{
"status":["IN_PROGRESS","CONFIRMED"],
"version":"2.6.0",
"cf_type":["---", "DEFECT"],
"include_fields":"id,product,component,priority,severity,status,summary"
}
</bugzilla>

== Bugs already fixed for this release ==

<bugzilla>
{
"status":["RESOLVED","VERIFIED"],
"version":"2.6.0",
"cf_type":["---", "DEFECT"],
"include_fields":"id,product,component,priority,severity,status,resolution,summary"
}
</bugzilla>

SW Tracking Report Objectives for the release 2.6.0

2025-08-23T19:06:52Z

Sgothel:

List started on 2023-07-xx, concluding [[SW Tracking Report Objectives for the release 2.5.0|Release 2.5.0]] - '''In Progress''' - continuation @ [[SW Tracking Report Objectives for the release 2.7.0|Release 2.7.0]].

* [{{SERVER}}/bugzilla//show_bug.cgi?id=1512 Release 2.6.0 Entry]
* [{{SERVER}}/bugzilla/buglist.cgi?list_id=2822&query_format=advanced&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED&version=2.6.0 Complete Bugzilla List of Version 2.6.0]

Warning: WIP

= Features =

== Features to be classified for this release ==

<bugzilla>
{
"status":["UNCONFIRMED"],
"version":"2.6.0",
"cf_type":"FEATURE",
"include_fields":"id,product,component,priority,severity,status,summary"
}
</bugzilla>

== Features to implement for this release ==

<bugzilla>
{
"status":["IN_PROGRESS","CONFIRMED"],
"version":"2.6.0",
"cf_type":"FEATURE",
"include_fields":"id,product,component,priority,severity,status,summary"
}
</bugzilla>

== Features already implemented for this release ==

<bugzilla>
{
"status":["RESOLVED","VERIFIED"],
"version":"2.6.0",
"cf_type":"FEATURE",
"include_fields":"id,product,component,priority,severity,status,resolution,summary"
}
</bugzilla>

= Bugs =

== Bugs to be classified for this release ==

<bugzilla>
{
"status":["UNCONFIRMED"],
"version":"2.6.0",
"cf_type":["---", "DEFECT"],
"include_fields":"id,product,component,priority,severity,status,summary"
}
</bugzilla>

== Bugs to fix for this release ==

<bugzilla>
{
"status":["IN_PROGRESS","CONFIRMED"],
"version":"2.6.0",
"cf_type":["---", "DEFECT"],
"include_fields":"id,product,component,priority,severity,status,summary"
}
</bugzilla>

== Bugs already fixed for this release ==

<bugzilla>
{
"status":["RESOLVED","VERIFIED"],
"version":"2.6.0",
"cf_type":["---", "DEFECT"],
"include_fields":"id,product,component,priority,severity,status,resolution,summary"
}
</bugzilla>

SW Tracking Report Objectives for the release 2.7.0

2025-06-21T10:01:33Z

Sgothel: Created page with "List started on 2025-06-21, concluding Release 2.6.0 - '''TBD''' - continuation @ Release 3.0.0. [{{SERVER}}/bugzilla/buglist.cgi?list_id=2822&query_format=advanced&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED&version=2.7.0 Complete Bugzilla List of Version 2.7.0] Warning: W..."

List started on 2025-06-21, concluding [[SW Tracking Report Objectives for the release 2.6.0|Release 2.6.0]] - '''TBD''' - continuation @ [[SW Tracking Report Objectives for the release 3.0.0|Release 3.0.0]].

[{{SERVER}}/bugzilla/buglist.cgi?list_id=2822&query_format=advanced&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED&version=2.7.0 Complete Bugzilla List of Version 2.7.0]

Warning: WIP

= Features =

== Features to be classified for this release ==

<bugzilla>
{
"status":["UNCONFIRMED"],
"version":"2.7.0",
"cf_type":"FEATURE",
"include_fields":"id,product,component,priority,severity,status,summary"
}
</bugzilla>

== Features to implement for this release ==

<bugzilla>
{
"status":["IN_PROGRESS","CONFIRMED"],
"version":"2.7.0",
"cf_type":"FEATURE",
"include_fields":"id,product,component,priority,severity,status,summary"
}
</bugzilla>

== Features already implemented for this release ==

<bugzilla>
{
"status":["RESOLVED","VERIFIED"],
"version":"2.7.0",
"cf_type":"FEATURE",
"include_fields":"id,product,component,priority,severity,status,resolution,summary"
}
</bugzilla>

= Bugs =

== Bugs to be classified for this release ==

<bugzilla>
{
"status":["UNCONFIRMED"],
"version":"2.7.0",
"cf_type":["---", "DEFECT"],
"include_fields":"id,product,component,priority,severity,status,summary"
}
</bugzilla>

== Bugs to fix for this release ==

<bugzilla>
{
"status":["IN_PROGRESS","CONFIRMED"],
"version":"2.7.0",
"cf_type":["---", "DEFECT"],
"include_fields":"id,product,component,priority,severity,status,summary"
}
</bugzilla>

== Bugs already fixed for this release ==

<bugzilla>
{
"status":["RESOLVED","VERIFIED"],
"version":"2.7.0",
"cf_type":["---", "DEFECT"],
"include_fields":"id,product,component,priority,severity,status,resolution,summary"
}
</bugzilla>

SW Tracking Report Objectives for the release 2.6.0

2025-06-21T09:59:51Z

Sgothel:

List started on 2023-07-xx, concluding [[SW Tracking Report Objectives for the release 2.5.0|Release 2.5.0]] - '''In Progress''' - continuation @ [[SW Tracking Report Objectives for the release 2.7.0|Release 2.7.0]].

[{{SERVER}}/bugzilla/buglist.cgi?list_id=2822&query_format=advanced&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED&version=2.6.0 Complete Bugzilla List of Version 2.6.0]

Warning: WIP

= Features =

== Features to be classified for this release ==

<bugzilla>
{
"status":["UNCONFIRMED"],
"version":"2.6.0",
"cf_type":"FEATURE",
"include_fields":"id,product,component,priority,severity,status,summary"
}
</bugzilla>

== Features to implement for this release ==

<bugzilla>
{
"status":["IN_PROGRESS","CONFIRMED"],
"version":"2.6.0",
"cf_type":"FEATURE",
"include_fields":"id,product,component,priority,severity,status,summary"
}
</bugzilla>

== Features already implemented for this release ==

<bugzilla>
{
"status":["RESOLVED","VERIFIED"],
"version":"2.6.0",
"cf_type":"FEATURE",
"include_fields":"id,product,component,priority,severity,status,resolution,summary"
}
</bugzilla>

= Bugs =

== Bugs to be classified for this release ==

<bugzilla>
{
"status":["UNCONFIRMED"],
"version":"2.6.0",
"cf_type":["---", "DEFECT"],
"include_fields":"id,product,component,priority,severity,status,summary"
}
</bugzilla>

== Bugs to fix for this release ==

<bugzilla>
{
"status":["IN_PROGRESS","CONFIRMED"],
"version":"2.6.0",
"cf_type":["---", "DEFECT"],
"include_fields":"id,product,component,priority,severity,status,summary"
}
</bugzilla>

== Bugs already fixed for this release ==

<bugzilla>
{
"status":["RESOLVED","VERIFIED"],
"version":"2.6.0",
"cf_type":["---", "DEFECT"],
"include_fields":"id,product,component,priority,severity,status,resolution,summary"
}
</bugzilla>

Main Page

2025-06-21T09:59:13Z

Sgothel:

__NOTOC__
{| width="100%"
|-
|
<div>
Welcome to the [{{SERVER}}/ JogAmp] wiki. It documents JOGL, JOCL and JOAL, the cross-platform bindings to the OpenGL, OpenCL, and OpenAL APIs.
</div>
|-
|
{| style="width: 100%;"
|-
|style="vertical-align: top; padding: 5px; width: 50%"|<h3>Getting Started</h3>
*[[Downloading and installing JOGL|Downloading and installing]]
**[[Jogamp Versioning and Releases|Versioning and Releases]]
*[[Setting up a JogAmp project in your favorite IDE|Setting up a JogAmp project in your favorite IDE]]
*[[Jogamp SCM Repositories|Source Code Repositories]]
*[[SW Tracking|Tracking Reports]]
*[{{SERVER}}/chuck/ Build and Test Server]
|style="vertical-align: top; padding: 5px; width: 50%"|<h3>Community</h3>
*[[How to Contribute|Contribute to JogAmp]]
*[[How to Build|Build JogAmp]]
*[[Maintainer and Contacts]]
*[[Jogl FAQ#Bugreports & Testing|Report a bug]]
**[{{SERVER}}/bugzilla/ Bugzilla]
*[http://forum.jogamp.org/ Ask a question in the forum]
*[[chatroom|JogAmp IRC]]
|}
|-

{| style=" width: 100%;"
|-
|colspan="2"|<h1>JogAmp Modules</h1>
|-
|style="vertical-align: top; padding: 5px; width: 50%"|<h3>Roadmaps</h3>
* ''[[SW Tracking Report Feature Objectives Overview|Feature & Objectives]], [[SW Tracking Report Objectives undetermined release|tbd]], [[SW Tracking Report Objectives for the release 3.0.0|3.0.0]], [[SW Tracking Report Objectives for the release 2.7.0|2.7.0]], [[SW Tracking Report Objectives for the release 2.6.0|2.6.0]]''
* '''[[SW Tracking Report Objectives for the release 2.5.0|2.5.0]] (last stable)''', [[SW Tracking Report Objectives for the release 2.4.0|2.4.0]], [[SW Tracking Report Objectives for the release 2.3.2|2.3.2]], [[SW Tracking Report Objectives for the release 2.3.1|2.3.1]], [[SW Tracking Report Objectives for the release 2.3.0|2.3.0]]
* [[SW Tracking Report Objectives for the release 2.2.4|2.2.4]], [[SW Tracking Report Objectives for the release 2.2.3|2.2.3]], [[SW Tracking Report Objectives for the release 2.2.2|2.2.2]], [[SW Tracking Report Objectives for the release 2.2.1|2.2.1]], [[SW Tracking Report Objectives for the release 2.2.0|2.2.0]]
* [[SW Tracking Report Objectives for the release 2.1.5|2.1.5]], [[SW Tracking Report Objectives for the release 2.1.4|2.1.4]], [[SW Tracking Report Objectives for the release 2.1.3|2.1.3]], [[SW Tracking Report Objectives for the release 2.1.2|2.1.2]], [[SW Tracking Report Objectives for the release 2.1.1|2.1.1]], [[SW Tracking Report Objectives for the release 2.1.0|2.1.0]]
* [[SW Tracking Report Objectives for the release 2.0.2 of JOGL|2.0.2]]
|-

|style="vertical-align: top; padding: 5px; width: 50%"|<h3>JOGL</h3>
*[[Jogl Overview|Overview]] [ [{{SERVER}}/jogl/doc/Overview-OpenGL-Evolution-And-JOGL.html OpenGL Evolution & JOGL] ]
*[[Why Instance Design|Why Instance Design]]
*[[Jogl Tutorial|Tutorial]]
*[[Jogl FAQ|FAQ]]
*[{{SERVER}}/git/?p=jogl.git;a=blob;f=LICENSE.txt License]
*API Doc [ [{{SERVER}}/deployment/jogamp-next/javadoc/jogl/javadoc/ Public], Specs [ [{{SERVER}}/deployment/jogamp-next/javadoc/jogl/javadoc_nativewindow_spec/ Nativewindow], [{{SERVER}}/deployment/jogamp-next/javadoc/jogl/javadoc_jogl_spec/ JOGL] ] ]
*[[Jogl API Overview|API Overview]]
**[[GL Debug Output|GL Debug Output]]
*[{{SERVER}}/jogl/doc/HowToBuild.html How to Build JOGL]

|style="vertical-align: top; padding: 5px; width: 50%"|<h3>JOCL</h3>
*[[JOCL Overview|Overview]]
*[[JOCL Tutorial|Tutorial]]
*[[JOCL FAQ|FAQ]]
*[{{SERVER}}/git/?p=jocl.git;a=blob;f=LICENSE License]
*[{{SERVER}}/deployment/jogamp-next/javadoc/jocl/javadoc/ API Doc]
*[{{SERVER}}/jocl/doc/HowToBuild.html How to Build JOCL]
|-
|style="vertical-align: top; padding: 5px; width: 50%"|<h3>JOAL</h3>
*[[Joal Overview|Overview]]
*[[Joal Tutorial|Tutorial]]
*[[Joal FAQ|FAQ]]
*[{{SERVER}}/git/?p=joal.git;a=blob;f=LICENSE.txt License]
*API Doc [ [{{SERVER}}/deployment/jogamp-next/javadoc/joal/javadoc/ Public], [{{SERVER}}/deployment/jogamp-next/javadoc/joal/javadoc_dev/ Internal] ]

|style="vertical-align: top; padding: 5px; width: 50%"|<h3>GlueGen</h3>
* [[GlueGen_Wiki|Overview]]
* [{{SERVER}}/git/?p=gluegen.git;a=blob;f=LICENSE.txt License]
* [{{SERVER}}/deployment/jogamp-next/javadoc/gluegen/javadoc/ GlueGen Java™ API-Doc]
* [{{SERVER}}/gluegen/doc/GlueGen_Mapping.html GlueGen Native Data & Function Mapping]
* [{{SERVER}}/gluegen/doc/manual/ GlueGen Manual]
* [{{SERVER}}/gluegen/doc/HowToBuild.html How To Build]
|}

{| style=" width: 100%;"
|-
|colspan="2"|<h1>Related Projects</h1>
|-
|style="vertical-align: top; padding: 5px; width: 50%"|<h3>Java3D</h3>
*[[Java3D Overview|Overview]]
*[[Downloading and installing Java3D|Downloading and installing]]
*[[Java3D Tutorial|Tutorial]]
*[[Java3D API Documentation|API Documentation]]
*[[Java3D FAQ|FAQ]]
|style="vertical-align: top; padding: 5px; width: 50%"|<h3>Ji Gong</h3>
*[[Ji Gong Overview|Overview]]
*[[Ji Gong Motivation|Motivation]]
*[[Ji Gong FAQ|FAQ]]
|-
|style="vertical-align: top; padding: 5px; width: 50%"|<h3>Source Certification Contract (SCC)</h3>
*[[SCC Overview|Overview]]
*[{{SERVER}}/bugzilla/showdependencytree.cgi?id=1368&hide_resolved=0 Bugzilla Dependency Tree]
*[{{SERVER}}/bugzilla/show_bug.cgi?id=1368 Bugzilla Parent Entry]
*[[SCC FAQ|FAQ]]
|style="vertical-align: top; padding: 5px; width: 50%"|<h3>Ardor3D</h3>
*[[Ardor3D Overview|Overview]]
*[[Ardor3D Tutorial|Tutorial]]
*[http://jogamp.org/deployment/ardor3d/javadoc/ API Documentation]
*[[Ardor3D FAQ|FAQ]]
|}

WebAssembly (wasm) Target Platform

2025-05-27T20:50:54Z

Sgothel:

Extracted from [[SW Tracking Report Feature Objectives Overview|Feature & Objectives]].

= Overview =
See [https://jogamp.org/bugzilla//show_bug.cgi?id=1506 Bug 1506] describing this feature.

Since Java Applets are not more supported within browser or by OpenJDK for years,
it may seems feasible to evaluate the WebAssembly target running within e.g. web browser nowadays.

An initial evaluation on small C++ projects using the emscripten front-end for LLVM's clang++ to wasm compiler, which supports many ported system libraries like SDL, OpenGL, .. has been undertaken successfully with variable results.
* [https://webassembly.org/ WebAssembly]
* [https://emscripten.org/ emscripten]
* [https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ gfxbox2 C++/wasm evaluation]
* Project [https://jausoft.com/cgit/gamp.git/about/ Gamp]

The wasm target is comparable to Java bytecode but the wasm virtual machine is not as performant, efficient or flexible as actual native code. The lack of hassle free native threads and native high-performance may remind one of the first JVM steps. The wasm code runs within a virtual machine like the JVM and additionally lacks of native binding capabilities.

Some limitations may be overcome, others are likely by design as it usually runs on the same browser virtual machine as the JavaScript companion. Compromises must be made on shared memory and native threads, cached non-local file I/O and socket communication - while other native features will simply never work, e.g. operating system ioctl-calls, etc.

Opening the door for any language to be compiled to a platform independent intermediate representation (IR) like Java’s bytecode suitable for a versatile runtime environment including its virtual machine is surely still desirable.

= Initial C++/wasm Evaluation =
[https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ Our little gfxbox2 games] compiled to [https://webassembly.org/ wasm] run about ~50% slower [https://jausoft.com/cgit/cs_class/gfxbox2.git/about/#online-webassembly-examples within a browser] than in native code, depending on coding strategy of our graphics (pixelmap vs SDL/OpenGL primitives).

The used [https://emscripten.org/ emscripten] frontend allowed us to use memory-growth, envelop files used in the wasm file, add cheap stack-overflow cockies and nullptr writes and so forth. Utilization of OpenGL ES via SDL2 was a breeze.

The underlying LLVM compiler did an excellent job and overall, the transition was easy and almost involved no code changes but dropping native thread (std::thread) usage.

The overall program structure had to be adapted to align to the single-thread main-loop workflow
and specific emscripten-javascript hooks added to allow seamless interaction.
All in all, nothing to be too afraid of and depending on the class of applications to be ported
to the browser these days, a feasible procedure.

= Project [https://jausoft.com/cgit/gamp.git/about/ Gamp] =
[https://jausoft.com/cgit/gamp.git/about/ Gamp] stands for Graphics, Audio, Multimedia and Processing, the same way as JogAmp, but natively plus using WebAssembly.

Gamp replicates JogAmp's experience natively via C++ in a condensed form, allowing a similar workflow on native targets and [https://jausoft.com/cgit/gamp.git/about/#online-webassembly-examples within the browser] via WebAssembly. Ironically this will bring back runs everywhere including the web.

Initial goal reimplementing [https://jausoft.com/blog/tag/graph_type_rendering/ Resolution independent NURBS curves rendering using programmable graphics pipeline (Graph)] has been completed.

Gamp uses [https://jausoft.com/cgit/jaulib.git/about/ jaulib] for general purpose functionality including linear algebra and geometry and builds upon initial wasm experience collected with [https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ gfxbox2].

= Java Support =
Java bytecode compiler to wasm including some ''runtime envelop''
* [https://github.com/google/j2cl/blob/master/docs/getting-started-j2wasm.md J2wasm] within [https://github.com/google/j2cl J2CL] emits naïve Wasm using the text format and it relies on Binaryen toolchain to assemble, link, and optimize
** [https://www.wingolog.org/pub/epfl-wasm-gc-feb-2024-slides.pdf 2024 Slides]
* [https://github.com/konsoletyper/teavm TeaVM] [https://teavm.org/docs/intro/overview.html overview]
* [https://github.com/i-net-software/JWebAssembly JWebAssembly] [https://github.com/i-net-software/JWebAssembly/wiki doc]
* [https://mirkosertic.github.io/Bytecoder/ Bytecoder]

Further interesting bits & pieces
* [https://openjdk.org/jeps/457 JEP 457: Class-File API ]
* [https://openjdk.org/projects/babylon/articles/linq Babylon]

== GraalVM ==
GraalVM experimentally hosts wasm only,
but is not producing a wasm target for the wasm (browser) runtime.
* [https://www.graalvm.org/latest/reference-manual/wasm/ GraalVM + wasm]
** with the help of emscripten
** [https://www.graalvm.org/22.0/reference-manual/native-image/JNI/ GraalVM + JNI]

[https://github.com/oracle/graal/issues/3391 Request for enhancement about wasm target in GraalVM].

= Java Browser Outlook =
So far the only question arises why reinventing the wheel once again? Dropping utilization of a well working JVM for the web had no technical reasoning.

However, in case no suitable wasm target for the Java bytecode and the Java Runtime pieces can be established, one might either want to also look into bringing back the JRE into the browser or painfully drop Java for C++, as the latter is already close to have acceptable (slower and limited) wasm target runtime properties.

WebAssembly (wasm) Target Platform

2025-05-27T18:11:37Z

Sgothel: /* Initial C++/wasm Evaluation */

Extracted from [[SW Tracking Report Feature Objectives Overview|Feature & Objectives]].

= Overview =
See [https://jogamp.org/bugzilla//show_bug.cgi?id=1506 Bug 1506] describing this feature.

Since Java Applets are not more supported within browser or by OpenJDK for years,
it may seems feasible to evaluate the WebAssembly target running within e.g. web browser nowadays.

An initial evaluation on small C++ projects using the emscripten front-end for LLVM's clang++ to wasm compiler, which supports many ported system libraries like SDL, OpenGL, .. has been undertaken successfully with variable results.
* [https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ gfxbox2 C++/wasm evaluation]
* [https://emscripten.org/ emscripten]
* [https://webassembly.org/ WebAssembly]

The wasm target is comparable to Java bytecode but the wasm virtual machine is not as performant, efficient or flexible as actual native code. The lack of hassle free native threads and native high-performance may remind one of the first JVM steps. The wasm code runs within a virtual machine like the JVM and additionally lacks of native binding capabilities.

Some limitations may be overcome, others are likely by design as it usually runs on the same browser virtual machine as the JavaScript companion. Compromises must be made on shared memory and native threads, cached non-local file I/O and socket communication - while other native features will simply never work, e.g. operating system ioctl-calls, etc.

Opening the door for any language to be compiled to a platform independent intermediate representation (IR) like Java’s bytecode suitable for a versatile runtime environment including its virtual machine is surely still desirable.

= Initial C++/wasm Evaluation =
[https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ Our little gfxbox2 games] compiled to [https://webassembly.org/ wasm] run about ~50% slower [https://jausoft.com/cgit/cs_class/gfxbox2.git/about/#online-webassembly-examples within a browser] than in native code, depending on coding strategy of our graphics (pixelmap vs SDL/OpenGL primitives).

The used [https://emscripten.org/ emscripten] frontend allowed us to use memory-growth, envelop files used in the wasm file, add cheap stack-overflow cockies and nullptr writes and so forth. Utilization of OpenGL ES via SDL2 was a breeze.

The underlying LLVM compiler did an excellent job and overall, the transition was easy and almost involved no code changes but dropping native thread (std::thread) usage.

'''Project [https://jausoft.com/cgit/gamp.git/about/ Gamp]''' has been created to address Graph and GraphUI, implemented in C++ to be utilized natively and [https://jausoft.com/cgit/gamp.git/about/#online-webassembly-examples within a browser] via WebAssembly.

The overall program structure had to be adapted to align to the single-thread main-loop workflow
and specific emscripten-javascript hooks added to allow seamless interaction.
All in all, nothing to be too afraid of and depending on the class of applications to be ported
to the browser these days, a feasible procedure.

= Java Support =
Java bytecode compiler to wasm including some ''runtime envelop''
* [https://github.com/google/j2cl/blob/master/docs/getting-started-j2wasm.md J2wasm] within [https://github.com/google/j2cl J2CL] emits naïve Wasm using the text format and it relies on Binaryen toolchain to assemble, link, and optimize
** [https://www.wingolog.org/pub/epfl-wasm-gc-feb-2024-slides.pdf 2024 Slides]
* [https://github.com/konsoletyper/teavm TeaVM] [https://teavm.org/docs/intro/overview.html overview]
* [https://github.com/i-net-software/JWebAssembly JWebAssembly] [https://github.com/i-net-software/JWebAssembly/wiki doc]
* [https://mirkosertic.github.io/Bytecoder/ Bytecoder]

Further interesting bits & pieces
* [https://openjdk.org/jeps/457 JEP 457: Class-File API ]
* [https://openjdk.org/projects/babylon/articles/linq Babylon]

== GraalVM ==
GraalVM experimentally hosts wasm only,
but is not producing a wasm target for the wasm (browser) runtime.
* [https://www.graalvm.org/latest/reference-manual/wasm/ GraalVM + wasm]
** with the help of emscripten
** [https://www.graalvm.org/22.0/reference-manual/native-image/JNI/ GraalVM + JNI]

[https://github.com/oracle/graal/issues/3391 Request for enhancement about wasm target in GraalVM].

= Java Browser Outlook =
So far the only question arises why reinventing the wheel once again? Dropping utilization of a well working JVM for the web had no technical reasoning.

However, in case no suitable wasm target for the Java bytecode and the Java Runtime pieces can be established, one might either want to also look into bringing back the JRE into the browser or painfully drop Java for C++, as the latter is already close to have acceptable (slower and limited) wasm target runtime properties.

WebAssembly (wasm) Target Platform

2024-04-04T06:35:12Z

Sgothel: /* Java Support */

Extracted from [[SW Tracking Report Feature Objectives Overview|Feature & Objectives]].

= Overview =
See [https://jogamp.org/bugzilla//show_bug.cgi?id=1506 Bug 1506] describing this feature.

Since Java Applets are not more supported within browser or by OpenJDK for years,
it may seems feasible to evaluate the WebAssembly target running within e.g. web browser nowadays.

An initial evaluation on small C++ projects using the emscripten front-end for LLVM's clang++ to wasm compiler, which supports many ported system libraries like SDL, OpenGL, .. has been undertaken successfully with variable results.
* [https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ gfxbox2 C++/wasm evaluation]
* [https://emscripten.org/ emscripten]
* [https://webassembly.org/ WebAssembly]

The wasm target is comparable to Java bytecode but the wasm virtual machine is not as performant, efficient or flexible as actual native code. The lack of hassle free native threads and native high-performance may remind one of the first JVM steps. The wasm code runs within a virtual machine like the JVM and additionally lacks of native binding capabilities.

Some limitations may be overcome, others are likely by design as it usually runs on the same browser virtual machine as the JavaScript companion. Compromises must be made on shared memory and native threads, cached non-local file I/O and socket communication - while other native features will simply never work, e.g. operating system ioctl-calls, etc.

Opening the door for any language to be compiled to a platform independent intermediate representation (IR) like Java’s bytecode suitable for a versatile runtime environment including its virtual machine is surely still desirable.

= Initial C++/wasm Evaluation =
[https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ Our little gfxbox2 games] compiled to [https://webassembly.org/ wasm] run about 40-60% slower within a browser than in native code, depending on coding strategy of our graphics (pixelmap vs SDL/OpenGL primitives).

The used [https://emscripten.org/ emscripten] frontend allowed us to use memory-growth, envelop files used in the wasm file, add cheap stack-overflow cockies and nullptr writes and so forth. Utilization of OpenGL ES via SDL2 was a breeze.

The underlying LLVM compiler did an excellent job and overall, the transition was easy and almost involved no code changes but dropping native thread (std::thread) usage.

The overall program structure had to be adapted to align to the single-thread main-loop workflow
and specific emscripten-javascript hooks added to allow seamless interaction.
All in all, nothing to be too afraid of and depending on the class of applications to be ported
to the browser these days, a feasible procedure.

= Java Support =
Java bytecode compiler to wasm including some ''runtime envelop''
* [https://github.com/google/j2cl/blob/master/docs/getting-started-j2wasm.md J2wasm] within [https://github.com/google/j2cl J2CL] emits naïve Wasm using the text format and it relies on Binaryen toolchain to assemble, link, and optimize
** [https://www.wingolog.org/pub/epfl-wasm-gc-feb-2024-slides.pdf 2024 Slides]
* [https://github.com/konsoletyper/teavm TeaVM] [https://teavm.org/docs/intro/overview.html overview]
* [https://github.com/i-net-software/JWebAssembly JWebAssembly] [https://github.com/i-net-software/JWebAssembly/wiki doc]
* [https://mirkosertic.github.io/Bytecoder/ Bytecoder]

Further interesting bits & pieces
* [https://openjdk.org/jeps/457 JEP 457: Class-File API ]
* [https://openjdk.org/projects/babylon/articles/linq Babylon]

== GraalVM ==
GraalVM experimentally hosts wasm only,
but is not producing a wasm target for the wasm (browser) runtime.
* [https://www.graalvm.org/latest/reference-manual/wasm/ GraalVM + wasm]
** with the help of emscripten
** [https://www.graalvm.org/22.0/reference-manual/native-image/JNI/ GraalVM + JNI]

[https://github.com/oracle/graal/issues/3391 Request for enhancement about wasm target in GraalVM].

= Java Browser Outlook =
So far the only question arises why reinventing the wheel once again? Dropping utilization of a well working JVM for the web had no technical reasoning.

However, in case no suitable wasm target for the Java bytecode and the Java Runtime pieces can be established, one might either want to also look into bringing back the JRE into the browser or painfully drop Java for C++, as the latter is already close to have acceptable (slower and limited) wasm target runtime properties.

WebAssembly (wasm) Target Platform

2024-04-04T06:29:52Z

Sgothel: /* Java Support */

Extracted from [[SW Tracking Report Feature Objectives Overview|Feature & Objectives]].

= Overview =
See [https://jogamp.org/bugzilla//show_bug.cgi?id=1506 Bug 1506] describing this feature.

Since Java Applets are not more supported within browser or by OpenJDK for years,
it may seems feasible to evaluate the WebAssembly target running within e.g. web browser nowadays.

An initial evaluation on small C++ projects using the emscripten front-end for LLVM's clang++ to wasm compiler, which supports many ported system libraries like SDL, OpenGL, .. has been undertaken successfully with variable results.
* [https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ gfxbox2 C++/wasm evaluation]
* [https://emscripten.org/ emscripten]
* [https://webassembly.org/ WebAssembly]

The wasm target is comparable to Java bytecode but the wasm virtual machine is not as performant, efficient or flexible as actual native code. The lack of hassle free native threads and native high-performance may remind one of the first JVM steps. The wasm code runs within a virtual machine like the JVM and additionally lacks of native binding capabilities.

Some limitations may be overcome, others are likely by design as it usually runs on the same browser virtual machine as the JavaScript companion. Compromises must be made on shared memory and native threads, cached non-local file I/O and socket communication - while other native features will simply never work, e.g. operating system ioctl-calls, etc.

Opening the door for any language to be compiled to a platform independent intermediate representation (IR) like Java’s bytecode suitable for a versatile runtime environment including its virtual machine is surely still desirable.

= Initial C++/wasm Evaluation =
[https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ Our little gfxbox2 games] compiled to [https://webassembly.org/ wasm] run about 40-60% slower within a browser than in native code, depending on coding strategy of our graphics (pixelmap vs SDL/OpenGL primitives).

The used [https://emscripten.org/ emscripten] frontend allowed us to use memory-growth, envelop files used in the wasm file, add cheap stack-overflow cockies and nullptr writes and so forth. Utilization of OpenGL ES via SDL2 was a breeze.

The underlying LLVM compiler did an excellent job and overall, the transition was easy and almost involved no code changes but dropping native thread (std::thread) usage.

The overall program structure had to be adapted to align to the single-thread main-loop workflow
and specific emscripten-javascript hooks added to allow seamless interaction.
All in all, nothing to be too afraid of and depending on the class of applications to be ported
to the browser these days, a feasible procedure.

= Java Support =
Java bytecode compiler to wasm including some ''runtime envelop''
* [https://github.com/google/j2cl/blob/master/docs/getting-started-j2wasm.md J2wasm] within [https://github.com/google/j2cl J2CL] emits very naïve Wasm using the text format and it relies on Binaryen toolchain to assemble, link, and optimize
** [https://www.wingolog.org/pub/epfl-wasm-gc-feb-2024-slides.pdf 2024 Slides]
* [https://github.com/konsoletyper/teavm TeaVM] [https://teavm.org/docs/intro/overview.html overview]
* [https://github.com/i-net-software/JWebAssembly JWebAssembly] [https://github.com/i-net-software/JWebAssembly/wiki doc]
* [https://mirkosertic.github.io/Bytecoder/ Bytecoder]

Further interesting bits & pieces
* [https://openjdk.org/jeps/457 JEP 457: Class-File API ]
* [https://openjdk.org/projects/babylon/articles/linq Babylon]

== GraalVM ==
GraalVM experimentally hosts wasm only,
but is not producing a wasm target for the wasm (browser) runtime.
* [https://www.graalvm.org/latest/reference-manual/wasm/ GraalVM + wasm]
** with the help of emscripten
** [https://www.graalvm.org/22.0/reference-manual/native-image/JNI/ GraalVM + JNI]

[https://github.com/oracle/graal/issues/3391 Request for enhancement about wasm target in GraalVM].

= Java Browser Outlook =
So far the only question arises why reinventing the wheel once again? Dropping utilization of a well working JVM for the web had no technical reasoning.

However, in case no suitable wasm target for the Java bytecode and the Java Runtime pieces can be established, one might either want to also look into bringing back the JRE into the browser or painfully drop Java for C++, as the latter is already close to have acceptable (slower and limited) wasm target runtime properties.

WebAssembly (wasm) Target Platform

2024-04-04T06:24:28Z

Sgothel: /* Java Support */

Extracted from [[SW Tracking Report Feature Objectives Overview|Feature & Objectives]].

= Overview =
See [https://jogamp.org/bugzilla//show_bug.cgi?id=1506 Bug 1506] describing this feature.

Since Java Applets are not more supported within browser or by OpenJDK for years,
it may seems feasible to evaluate the WebAssembly target running within e.g. web browser nowadays.

An initial evaluation on small C++ projects using the emscripten front-end for LLVM's clang++ to wasm compiler, which supports many ported system libraries like SDL, OpenGL, .. has been undertaken successfully with variable results.
* [https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ gfxbox2 C++/wasm evaluation]
* [https://emscripten.org/ emscripten]
* [https://webassembly.org/ WebAssembly]

The wasm target is comparable to Java bytecode but the wasm virtual machine is not as performant, efficient or flexible as actual native code. The lack of hassle free native threads and native high-performance may remind one of the first JVM steps. The wasm code runs within a virtual machine like the JVM and additionally lacks of native binding capabilities.

Some limitations may be overcome, others are likely by design as it usually runs on the same browser virtual machine as the JavaScript companion. Compromises must be made on shared memory and native threads, cached non-local file I/O and socket communication - while other native features will simply never work, e.g. operating system ioctl-calls, etc.

Opening the door for any language to be compiled to a platform independent intermediate representation (IR) like Java’s bytecode suitable for a versatile runtime environment including its virtual machine is surely still desirable.

= Initial C++/wasm Evaluation =
[https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ Our little gfxbox2 games] compiled to [https://webassembly.org/ wasm] run about 40-60% slower within a browser than in native code, depending on coding strategy of our graphics (pixelmap vs SDL/OpenGL primitives).

The used [https://emscripten.org/ emscripten] frontend allowed us to use memory-growth, envelop files used in the wasm file, add cheap stack-overflow cockies and nullptr writes and so forth. Utilization of OpenGL ES via SDL2 was a breeze.

The underlying LLVM compiler did an excellent job and overall, the transition was easy and almost involved no code changes but dropping native thread (std::thread) usage.

The overall program structure had to be adapted to align to the single-thread main-loop workflow
and specific emscripten-javascript hooks added to allow seamless interaction.
All in all, nothing to be too afraid of and depending on the class of applications to be ported
to the browser these days, a feasible procedure.

= Java Support =
Java bytecode compiler to wasm including some ''runtime envelop''
* [https://github.com/konsoletyper/teavm TeaVM] [https://teavm.org/docs/intro/overview.html overview]
* [https://github.com/i-net-software/JWebAssembly JWebAssembly] [https://github.com/i-net-software/JWebAssembly/wiki doc]
* [https://mirkosertic.github.io/Bytecoder/ Bytecoder]

Further interesting bits & pieces
* [https://openjdk.org/jeps/457 JEP 457: Class-File API ]
* [https://openjdk.org/projects/babylon/articles/linq Babylon]
* [https://github.com/google/j2cl/blob/master/docs/getting-started-j2wasm.md J2wasm] within [https://github.com/google/j2cl J2CL] emits very naïve Wasm using the text format and it relies on Binaryen toolchain to assemble, link, and optimize
** [https://www.wingolog.org/pub/epfl-wasm-gc-feb-2024-slides.pdf 2024 Slides]

== GraalVM ==
GraalVM experimentally hosts wasm only,
but is not producing a wasm target for the wasm (browser) runtime.
* [https://www.graalvm.org/latest/reference-manual/wasm/ GraalVM + wasm]
** with the help of emscripten
** [https://www.graalvm.org/22.0/reference-manual/native-image/JNI/ GraalVM + JNI]

[https://github.com/oracle/graal/issues/3391 Request for enhancement about wasm target in GraalVM].

= Java Browser Outlook =
So far the only question arises why reinventing the wheel once again? Dropping utilization of a well working JVM for the web had no technical reasoning.

However, in case no suitable wasm target for the Java bytecode and the Java Runtime pieces can be established, one might either want to also look into bringing back the JRE into the browser or painfully drop Java for C++, as the latter is already close to have acceptable (slower and limited) wasm target runtime properties.

WebAssembly (wasm) Target Platform

2024-04-04T06:20:40Z

Sgothel:

Extracted from [[SW Tracking Report Feature Objectives Overview|Feature & Objectives]].

= Overview =
See [https://jogamp.org/bugzilla//show_bug.cgi?id=1506 Bug 1506] describing this feature.

Since Java Applets are not more supported within browser or by OpenJDK for years,
it may seems feasible to evaluate the WebAssembly target running within e.g. web browser nowadays.

An initial evaluation on small C++ projects using the emscripten front-end for LLVM's clang++ to wasm compiler, which supports many ported system libraries like SDL, OpenGL, .. has been undertaken successfully with variable results.
* [https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ gfxbox2 C++/wasm evaluation]
* [https://emscripten.org/ emscripten]
* [https://webassembly.org/ WebAssembly]

The wasm target is comparable to Java bytecode but the wasm virtual machine is not as performant, efficient or flexible as actual native code. The lack of hassle free native threads and native high-performance may remind one of the first JVM steps. The wasm code runs within a virtual machine like the JVM and additionally lacks of native binding capabilities.

Some limitations may be overcome, others are likely by design as it usually runs on the same browser virtual machine as the JavaScript companion. Compromises must be made on shared memory and native threads, cached non-local file I/O and socket communication - while other native features will simply never work, e.g. operating system ioctl-calls, etc.

Opening the door for any language to be compiled to a platform independent intermediate representation (IR) like Java’s bytecode suitable for a versatile runtime environment including its virtual machine is surely still desirable.

= Initial C++/wasm Evaluation =
[https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ Our little gfxbox2 games] compiled to [https://webassembly.org/ wasm] run about 40-60% slower within a browser than in native code, depending on coding strategy of our graphics (pixelmap vs SDL/OpenGL primitives).

The used [https://emscripten.org/ emscripten] frontend allowed us to use memory-growth, envelop files used in the wasm file, add cheap stack-overflow cockies and nullptr writes and so forth. Utilization of OpenGL ES via SDL2 was a breeze.

The underlying LLVM compiler did an excellent job and overall, the transition was easy and almost involved no code changes but dropping native thread (std::thread) usage.

The overall program structure had to be adapted to align to the single-thread main-loop workflow
and specific emscripten-javascript hooks added to allow seamless interaction.
All in all, nothing to be too afraid of and depending on the class of applications to be ported
to the browser these days, a feasible procedure.

= Java Support =
Java bytecode compiler to wasm including some ''runtime envelop''
* [https://github.com/konsoletyper/teavm TeaVM] [https://teavm.org/docs/intro/overview.html overview]
* [https://github.com/i-net-software/JWebAssembly JWebAssembly] [https://github.com/i-net-software/JWebAssembly/wiki doc]
* [https://mirkosertic.github.io/Bytecoder/ Bytecoder]

Further interesting bits & pieces
* [https://openjdk.org/jeps/457 JEP 457: Class-File API ]
* [https://openjdk.org/projects/babylon/articles/linq Babylon]
* [https://github.com/google/j2cl/blob/master/docs/getting-started-j2wasm.md J2wasm] within [[https://github.com/google/j2cl J2CL] emits very naïve Wasm using the text format and it relies on Binaryen toolchain to assemble, link, and optimize
** [https://www.wingolog.org/pub/epfl-wasm-gc-feb-2024-slides.pdf 2024 Slides]

== GraalVM ==
GraalVM experimentally hosts wasm only,
but is not producing a wasm target for the wasm (browser) runtime.
* [https://www.graalvm.org/latest/reference-manual/wasm/ GraalVM + wasm]
** with the help of emscripten
** [https://www.graalvm.org/22.0/reference-manual/native-image/JNI/ GraalVM + JNI]

[https://github.com/oracle/graal/issues/3391 Request for enhancement about wasm target in GraalVM].

= Java Browser Outlook =
So far the only question arises why reinventing the wheel once again? Dropping utilization of a well working JVM for the web had no technical reasoning.

However, in case no suitable wasm target for the Java bytecode and the Java Runtime pieces can be established, one might either want to also look into bringing back the JRE into the browser or painfully drop Java for C++, as the latter is already close to have acceptable (slower and limited) wasm target runtime properties.

SW Tracking Report Feature Objectives Overview

2024-04-04T06:11:59Z

Sgothel:

This list exposes building blocks
for potential use and business case scenarios
using Java & JogAmp on Desktop and Embedded Devices.

Notably [[#Graph|Graph & Graph UI]] as well as [[#NEWT_+_Wayland|Wayland]] & [[#Vulkan|Vulkan]] support could be of interest here?

Also see [[Completed Features Objectives]] ...

= Graph =
[https://jausoft.com/blog/tag/graph_type_rendering/ Graph/GraphUI Progress Blog Entries]

== Desired Work Items ==

This is an ad-hoc list of desired features and fixes,
which shall result in proper bug-reports soon.

After having reached [https://jausoft.com/blog/2024/01/21/graphui-frustum-culling-clipping-modelview-space/ UI usability with widgets and clipping],
the following items are becoming more interesting

* Fix general issues with current implementation and API, if any
* Fix Graph rendering bugs (Tessellation)
** [https://jausoft.com/blog/2024/02/13/fixing-jogamps-graph-delaunay-tessellation-of-complex-non-convex-shapes/ First round done]
* Use of super-sized triangles to render Graph lines & curves to allow
** Using a one-pass smooth AA Graph renderer to save resources otherwise used in our pass-2 FBO supersampling renderer
** Generate outlines, i.e. outlined fonts
** Generate special effects like glowing/pumping outlines indicating selection etc
* Allow passing or better attaching per-vertex color to Graph Outline (API)
* <s>Add subtitles in MediaPlayer GraphUI widget</s> ''([https://jausoft.com/blog/2024/02/07/graphui-mediaplayer-feature-complete/ done])''
* Add video encoding in our FFmpeg binding, i.e. an FFMPEGMediaRecorder (Encoding + Multiplexing)

Further more, if so desired, a C++ implementation of our Graph + GraphUI framework
may also be of interest.

In case any company or organization is interested and likes to support
this work and may also like to receive support in adopting this framework,
please contact [[Maintainer_and_Contacts#Commercial_Support|Göthel Software e.K.]]

== OpenJDK Compatibility / Integration ==

Objectives should be to allow seamless integration into
OpenJDK's deployment and JVM launch methods.

A dual JAR file to be used with and without modules is desired,
however it seems that certain JAR options are not available with this
configuration if our classes are not build as modules itself.

An optional [https://jogamp.org/bugzilla/show_bug.cgi?id=1505#c0 JVM Launch Pad (JLP)] might be helpful,
even though it instructs further complexity and is not helping
with a vanilla OpenJDK deployment.

=== OpenJDK >= 11 ===

See [https://jogamp.org/bugzilla/show_bug.cgi?id=1404 Bug 1404]

'''JVM Commandline Parameter'''

Current used 'add-opens' in my JogAmp test scripts for Java >= 11,
covering all AWT utilization including background erase is:

<pre>
--add-opens java.desktop/sun.awt=ALL-UNNAMED
--add-opens java.desktop/sun.awt.windows=ALL-UNNAMED
--add-opens java.desktop/sun.java2d=ALL-UNNAMED
</pre>

=== OpenJDK >= 2x ===

See [https://jogamp.org/bugzilla/show_bug.cgi?id=1505 Bug 1505]

'''JVM Commandline Parameter'''

Current used 'add-opens' in my JogAmp test scripts for Java >= 23,
covering all AWT utilization including background erase is:

<pre>
--add-opens java.desktop/sun.awt=ALL-UNNAMED
--add-opens java.desktop/sun.awt.windows=ALL-UNNAMED
--add-opens java.desktop/sun.java2d=ALL-UNNAMED
--TO_BE_DETERMINED
</pre>

== Graph UI ==

[https://jausoft.com/blog/2023/02/22/reimagine-java-on-desktop-bare-metal-devices/ ''Graph UI'' will enable an immersive UI within the 3D scene] on the desktop, mobile and on bare-metal embedded systems without a windowing system.

Graph UI utilizes [https://jausoft.com/blog/2011/10/05/jogljogamp-red-square-moscow-nurbs-graphicon2011/ Resolution Independent NURBS Curves Rendering using Programmable Graphics Pipeline], i.e. rendering curves directly on the GPU, resolution independent [ [https://jogamp.org/doc/gpunurbs2011/p70-santina.pdf paper], [https://jogamp.org/doc/gpunurbs2011/graphicon2011-slides.pdf slides] ].

This method allows us to have an ultimate fast font and UI rendering engine, suitable for all devices and applications. No CPU based curve nor font pre-rendering (matching a target resolution) is required.

Think of an integrated QT or OpenJFX in your 2D/3D application
working on desktop and embedded devices even w/o any windowing system on top
of a plain console [{{SERVER}}/bugzilla/show_bug.cgi?id=1156 DRM/GBM as support by JOGL(EGL) and NEWT]
as demonstrated [https://ict.zafena.se/improved-graphical-information-technology/ by Xerxes on a Raspberry Pi4].

[https://jausoft.com/blog/2023/02/22/reimagine-java-on-desktop-bare-metal-devices/ Reimagine Java on Desktop & Bare-Metal Devices]
demonstrates the updated Graph Curve Rendering and UI, while [https://jausoft.com/blog/2024/01/21/graphui-frustum-culling-clipping-modelview-space/ this update shows clipping and widgets]. [https://jausoft.com/blog/tag/graph_type_rendering/ Further updates will be posted here...].

Notably the ''Graph Curve Rendering'' is almost feature complete, as well as our own user input including gesture detection within NEWT.

;Parent Main Node
: [{{SERVER}}/bugzilla/showdependencytree.cgi?id=803&hide_resolved=0 Dependency Tree]
: [{{SERVER}}/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=IN_PROGRESS&bug_status=RESOLVED&bug_status=VERIFIED&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cversion%2Cshort_desc%2Cchangeddate&component=core&component=Plugin&list_id=2265&product=GraphUI&query_format=advanced&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED All GraphUI]

;Open Items ''graphui''
<bugzilla>
{
"status":["IN_PROGRESS","CONFIRMED", "UNCONFIRMED"],
"product":"graphui",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

;Completed Items ''graphui''
<bugzilla>
{
"status":["RESOLVED","VERIFIED"],
"product":"graphui",
"include_fields":"id,version,product,component,status,resolution,summary"
}
</bugzilla>

== Jogl / Graph ==

[{{SERVER}}/bugzilla/showdependencytree.cgi?id=1064&hide_resolved=0 Dependency Tree Graph Font Issues]

[{{SERVER}}/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=IN_PROGRESS&bug_status=RESOLVED&bug_status=VERIFIED&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cversion%2Cshort_desc%2Cchangeddate&component=graph&list_id=2264&product=Jogl&query_format=advanced&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED All Jogl Graph]

;Open Items ''Jogl / graph''
<bugzilla>
{
"status":["IN_PROGRESS","CONFIRMED", "UNCONFIRMED"],
"product":"jogl",
"component":"graph",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

;Completed Items ''Jogl / graph''
<bugzilla>
{
"status":["RESOLVED","VERIFIED"],
"product":"jogl",
"component":"graph",
"include_fields":"id,version,product,component,status,resolution,summary"
}
</bugzilla>

= WebAssembly (wasm) Target Platform =
See [[WebAssembly (wasm) Target Platform]]

= NEWT =

* [{{SERVER}}/bugzilla/showdependencytree.cgi?id=807&hide_resolved=0 Dependency Tree NEWT Input Devices]
* [{{SERVER}}/bugzilla/showdependencytree.cgi?id=814&hide_resolved=0 Dependency Tree NEWT Pointer Event]

<bugzilla>
{
"product":["newt","jinput"],
"version":["2.5.0","3.0.0","tbd"],
"cf_type":"FEATURE",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

= NEWT + Wayland =
Currently NEWT supports the X11/Xorg windowing server on Unix alike platforms.

It might be desired to add direct support to Wayland, as we already added support for
[https://jogamp.org/bugzilla/show_bug.cgi?id=1156 bare metal devices w/o a windowing system via the Linux DRM/GBM console mode]
throughout JOGL + NEWT.

= Vulkan =

<bugzilla>
{
"component":"vulkan",
"cf_type":"FEATURE",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

= Video Encoding/Decoding & Player =

Across our releases, we supported video encoding and decoding (with a player)
based on either FFmpeg or Android's library as [https://youtu.be/4gWStKCioi8?t=132 shown in this clip at 2:12 min mark].

Goal would be to
* Update general ffmpeg video decoding support
* Enhance ffmpeg video encoding support
* Potentially add better control about video-frame to framebuffer control for editing software

See [https://jogamp.org/bugzilla//buglist.cgi?bug_status=__open__&component=video&list_id=3053&product=Jogl related buglist]

<bugzilla>
{
"component":"video",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

= iOS Enhancements =

Early iOS support has been demonstrated in 2019
* [https://jausoft.com/blog/2019/06/17/jogamp-ios-arm64-bring-up/ iOS Arm64 bring-up]
* [https://jausoft.com/blog/2019/06/23/jogamp-ios-arm64-port-first-visuals/ iOS Arm64 Port: First Visuals]
* [https://jausoft.com/blog/2019/07/08/jogamp-ios-arm64-port-newt/ iOS Arm64 Port: NEWT]

Enhancing this port would allow to use JogAmp in a similar fashion as on Android,
but using an OpenJDK iOS build.

= [[SCC Overview|Source Certification Contract (SCC)]] =

[{{SERVER}}/bugzilla/showdependencytree.cgi?id=1368&hide_resolved=0 Dependency Tree]

[{{SERVER}}/bugzilla/show_bug.cgi?id=1368 Root Parent Entry]

<bugzilla>
{
"id":["1368", "1369"],
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

= OpenJFX =

[https://jogamp.org/bugzilla//show_bug.cgi?id=607#c20 Bug report 607] describes different ways to either
* enhance external rendering via JOGL into an OpenJFX UI elements, or
* to replace OpenJFX's Glass w/ NEWT and Prism's OpenGL coding with JOGL

= Misc =



<bugzilla>
{
"version":["2.5.0","3.0.0","tbd"],
"cf_type":"FEATURE",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

WebAssembly (wasm) Target Platform

2024-04-04T06:10:11Z

Sgothel:

WebAssembly (wasm) Target Platform

2024-04-04T06:09:34Z

Sgothel:

= WebAssembly (wasm) Target Platform =

Extracted from [[SW Tracking Report Feature Objectives Overview|Feature & Objectives]].

= Overview =
See [https://jogamp.org/bugzilla//show_bug.cgi?id=1506 Bug 1506] describing this feature.

Since Java Applets are not more supported within browser or by OpenJDK for years,
it may seems feasible to evaluate the WebAssembly target running within e.g. web browser nowadays.

An initial evaluation on small C++ projects using the emscripten front-end for LLVM's clang++ to wasm compiler, which supports many ported system libraries like SDL, OpenGL, .. has been undertaken successfully with variable results.
* [https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ gfxbox2 C++/wasm evaluation]
* [https://emscripten.org/ emscripten]
* [https://webassembly.org/ WebAssembly]

The wasm target is comparable to Java bytecode but the wasm virtual machine is not as performant, efficient or flexible as actual native code. The lack of hassle free native threads and native high-performance may remind one of the first JVM steps. The wasm code runs within a virtual machine like the JVM and additionally lacks of native binding capabilities.

Some limitations may be overcome, others are likely by design as it usually runs on the same browser virtual machine as the JavaScript companion. Compromises must be made on shared memory and native threads, cached non-local file I/O and socket communication - while other native features will simply never work, e.g. operating system ioctl-calls, etc.

Opening the door for any language to be compiled to a platform independent intermediate representation (IR) like Java’s bytecode suitable for a versatile runtime environment including its virtual machine is surely still desirable.

= Initial C++/wasm Evaluation =
[https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ Our little gfxbox2 games] compiled to [https://webassembly.org/ wasm] run about 40-60% slower within a browser than in native code, depending on coding strategy of our graphics (pixelmap vs SDL/OpenGL primitives).

The used [https://emscripten.org/ emscripten] frontend allowed us to use memory-growth, envelop files used in the wasm file, add cheap stack-overflow cockies and nullptr writes and so forth. Utilization of OpenGL ES via SDL2 was a breeze.

The underlying LLVM compiler did an excellent job and overall, the transition was easy and almost involved no code changes but dropping native thread (std::thread) usage.

The overall program structure had to be adapted to align to the single-thread main-loop workflow
and specific emscripten-javascript hooks added to allow seamless interaction.
All in all, nothing to be too afraid of and depending on the class of applications to be ported
to the browser these days, a feasible procedure.

= Java Support =
Java bytecode compiler to wasm including some ''runtime envelop''
* [https://github.com/konsoletyper/teavm TeaVM] [https://teavm.org/docs/intro/overview.html overview]
* [https://github.com/i-net-software/JWebAssembly JWebAssembly] [https://github.com/i-net-software/JWebAssembly/wiki doc]
* [https://mirkosertic.github.io/Bytecoder/ Bytecoder]

Further interesting bits & pieces
** [https://openjdk.org/jeps/457 JEP 457: Class-File API ]
** [https://openjdk.org/projects/babylon/articles/linq Babylon]

GraalVM experimentally hosts wasm only,
but is not producing a wasm target for the wasm (browser) runtime.

* [https://www.graalvm.org/latest/reference-manual/wasm/ GraalVM + wasm]
** with the help of emscripten
** [https://www.graalvm.org/22.0/reference-manual/native-image/JNI/ GraalVM + JNI]

= Java Browser Outlook =
So far the only question arises why reinventing the wheel once again? Dropping utilization of a well working JVM for the web had no technical reasoning.

However, in case no suitable wasm target for the Java bytecode and the Java Runtime pieces can be established, one might either want to also look into bringing back the JRE into the browser or painfully drop Java for C++, as the latter is already close to have acceptable (slower and limited) wasm target runtime properties.

WebAssembly (wasm) Target Platform

2024-04-04T06:08:47Z

Sgothel: Created page with "= WebAssembly (wasm) Target Platform = Extracted from Feature & Objectives. == Overview == See [https://jogamp.org/bugzilla//show_bug.cgi?id=1506 Bug 1506] describing this feature. Since Java Applets are not more supported within browser or by OpenJDK for years, it may seems feasible to evaluate the WebAssembly target running within e.g. web browser nowadays. An initial evaluation on small C++ projects using the emsc..."

= WebAssembly (wasm) Target Platform =

Extracted from [[SW Tracking Report Feature Objectives Overview|Feature & Objectives]].

== Overview ==
See [https://jogamp.org/bugzilla//show_bug.cgi?id=1506 Bug 1506] describing this feature.

Since Java Applets are not more supported within browser or by OpenJDK for years,
it may seems feasible to evaluate the WebAssembly target running within e.g. web browser nowadays.

An initial evaluation on small C++ projects using the emscripten front-end for LLVM's clang++ to wasm compiler, which supports many ported system libraries like SDL, OpenGL, .. has been undertaken successfully with variable results.
* [https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ gfxbox2 C++/wasm evaluation]
* [https://emscripten.org/ emscripten]
* [https://webassembly.org/ WebAssembly]

The wasm target is comparable to Java bytecode but the wasm virtual machine is not as performant, efficient or flexible as actual native code. The lack of hassle free native threads and native high-performance may remind one of the first JVM steps. The wasm code runs within a virtual machine like the JVM and additionally lacks of native binding capabilities.

Some limitations may be overcome, others are likely by design as it usually runs on the same browser virtual machine as the JavaScript companion. Compromises must be made on shared memory and native threads, cached non-local file I/O and socket communication - while other native features will simply never work, e.g. operating system ioctl-calls, etc.

Opening the door for any language to be compiled to a platform independent intermediate representation (IR) like Java’s bytecode suitable for a versatile runtime environment including its virtual machine is surely still desirable.

== Initial C++/wasm Evaluation ==
[https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ Our little gfxbox2 games] compiled to [https://webassembly.org/ wasm] run about 40-60% slower within a browser than in native code, depending on coding strategy of our graphics (pixelmap vs SDL/OpenGL primitives).

The used [https://emscripten.org/ emscripten] frontend allowed us to use memory-growth, envelop files used in the wasm file, add cheap stack-overflow cockies and nullptr writes and so forth. Utilization of OpenGL ES via SDL2 was a breeze.

The underlying LLVM compiler did an excellent job and overall, the transition was easy and almost involved no code changes but dropping native thread (std::thread) usage.

The overall program structure had to be adapted to align to the single-thread main-loop workflow
and specific emscripten-javascript hooks added to allow seamless interaction.
All in all, nothing to be too afraid of and depending on the class of applications to be ported
to the browser these days, a feasible procedure.

== Java Support ==
Java bytecode compiler to wasm including some ''runtime envelop''
* [https://github.com/konsoletyper/teavm TeaVM] [https://teavm.org/docs/intro/overview.html overview]
* [https://github.com/i-net-software/JWebAssembly JWebAssembly] [https://github.com/i-net-software/JWebAssembly/wiki doc]
* [https://mirkosertic.github.io/Bytecoder/ Bytecoder]

Further interesting bits & pieces
** [https://openjdk.org/jeps/457 JEP 457: Class-File API ]
** [https://openjdk.org/projects/babylon/articles/linq Babylon]

GraalVM experimentally hosts wasm only,
but is not producing a wasm target for the wasm (browser) runtime.

* [https://www.graalvm.org/latest/reference-manual/wasm/ GraalVM + wasm]
** with the help of emscripten
** [https://www.graalvm.org/22.0/reference-manual/native-image/JNI/ GraalVM + JNI]

== Java Browser Outlook ==
So far the only question arises why reinventing the wheel once again? Dropping utilization of a well working JVM for the web had no technical reasoning.

However, in case no suitable wasm target for the Java bytecode and the Java Runtime pieces can be established, one might either want to also look into bringing back the JRE into the browser or painfully drop Java for C++, as the latter is already close to have acceptable (slower and limited) wasm target runtime properties.

SW Tracking Report Feature Objectives Overview

2024-04-03T04:34:13Z

Sgothel: /* Java Support */

This list exposes building blocks
for potential use and business case scenarios
using Java & JogAmp on Desktop and Embedded Devices.

Notably [[#Graph|Graph & Graph UI]] as well as [[#NEWT_+_Wayland|Wayland]] & [[#Vulkan|Vulkan]] support could be of interest here?

Also see [[Completed Features Objectives]] ...

= Graph =
[https://jausoft.com/blog/tag/graph_type_rendering/ Graph/GraphUI Progress Blog Entries]

== Desired Work Items ==

This is an ad-hoc list of desired features and fixes,
which shall result in proper bug-reports soon.

After having reached [https://jausoft.com/blog/2024/01/21/graphui-frustum-culling-clipping-modelview-space/ UI usability with widgets and clipping],
the following items are becoming more interesting

* Fix general issues with current implementation and API, if any
* Fix Graph rendering bugs (Tessellation)
** [https://jausoft.com/blog/2024/02/13/fixing-jogamps-graph-delaunay-tessellation-of-complex-non-convex-shapes/ First round done]
* Use of super-sized triangles to render Graph lines & curves to allow
** Using a one-pass smooth AA Graph renderer to save resources otherwise used in our pass-2 FBO supersampling renderer
** Generate outlines, i.e. outlined fonts
** Generate special effects like glowing/pumping outlines indicating selection etc
* Allow passing or better attaching per-vertex color to Graph Outline (API)
* <s>Add subtitles in MediaPlayer GraphUI widget</s> ''([https://jausoft.com/blog/2024/02/07/graphui-mediaplayer-feature-complete/ done])''
* Add video encoding in our FFmpeg binding, i.e. an FFMPEGMediaRecorder (Encoding + Multiplexing)

Further more, if so desired, a C++ implementation of our Graph + GraphUI framework
may also be of interest.

In case any company or organization is interested and likes to support
this work and may also like to receive support in adopting this framework,
please contact [[Maintainer_and_Contacts#Commercial_Support|Göthel Software e.K.]]

== OpenJDK Compatibility / Integration ==

Objectives should be to allow seamless integration into
OpenJDK's deployment and JVM launch methods.

A dual JAR file to be used with and without modules is desired,
however it seems that certain JAR options are not available with this
configuration if our classes are not build as modules itself.

An optional [https://jogamp.org/bugzilla/show_bug.cgi?id=1505#c0 JVM Launch Pad (JLP)] might be helpful,
even though it instructs further complexity and is not helping
with a vanilla OpenJDK deployment.

=== OpenJDK >= 11 ===

See [https://jogamp.org/bugzilla/show_bug.cgi?id=1404 Bug 1404]

'''JVM Commandline Parameter'''

Current used 'add-opens' in my JogAmp test scripts for Java >= 11,
covering all AWT utilization including background erase is:

<pre>
--add-opens java.desktop/sun.awt=ALL-UNNAMED
--add-opens java.desktop/sun.awt.windows=ALL-UNNAMED
--add-opens java.desktop/sun.java2d=ALL-UNNAMED
</pre>

=== OpenJDK >= 2x ===

See [https://jogamp.org/bugzilla/show_bug.cgi?id=1505 Bug 1505]

'''JVM Commandline Parameter'''

Current used 'add-opens' in my JogAmp test scripts for Java >= 23,
covering all AWT utilization including background erase is:

<pre>
--add-opens java.desktop/sun.awt=ALL-UNNAMED
--add-opens java.desktop/sun.awt.windows=ALL-UNNAMED
--add-opens java.desktop/sun.java2d=ALL-UNNAMED
--TO_BE_DETERMINED
</pre>

== Graph UI ==

[https://jausoft.com/blog/2023/02/22/reimagine-java-on-desktop-bare-metal-devices/ ''Graph UI'' will enable an immersive UI within the 3D scene] on the desktop, mobile and on bare-metal embedded systems without a windowing system.

Graph UI utilizes [https://jausoft.com/blog/2011/10/05/jogljogamp-red-square-moscow-nurbs-graphicon2011/ Resolution Independent NURBS Curves Rendering using Programmable Graphics Pipeline], i.e. rendering curves directly on the GPU, resolution independent [ [https://jogamp.org/doc/gpunurbs2011/p70-santina.pdf paper], [https://jogamp.org/doc/gpunurbs2011/graphicon2011-slides.pdf slides] ].

This method allows us to have an ultimate fast font and UI rendering engine, suitable for all devices and applications. No CPU based curve nor font pre-rendering (matching a target resolution) is required.

Think of an integrated QT or OpenJFX in your 2D/3D application
working on desktop and embedded devices even w/o any windowing system on top
of a plain console [{{SERVER}}/bugzilla/show_bug.cgi?id=1156 DRM/GBM as support by JOGL(EGL) and NEWT]
as demonstrated [https://ict.zafena.se/improved-graphical-information-technology/ by Xerxes on a Raspberry Pi4].

[https://jausoft.com/blog/2023/02/22/reimagine-java-on-desktop-bare-metal-devices/ Reimagine Java on Desktop & Bare-Metal Devices]
demonstrates the updated Graph Curve Rendering and UI, while [https://jausoft.com/blog/2024/01/21/graphui-frustum-culling-clipping-modelview-space/ this update shows clipping and widgets]. [https://jausoft.com/blog/tag/graph_type_rendering/ Further updates will be posted here...].

Notably the ''Graph Curve Rendering'' is almost feature complete, as well as our own user input including gesture detection within NEWT.

;Parent Main Node
: [{{SERVER}}/bugzilla/showdependencytree.cgi?id=803&hide_resolved=0 Dependency Tree]
: [{{SERVER}}/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=IN_PROGRESS&bug_status=RESOLVED&bug_status=VERIFIED&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cversion%2Cshort_desc%2Cchangeddate&component=core&component=Plugin&list_id=2265&product=GraphUI&query_format=advanced&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED All GraphUI]

;Open Items ''graphui''
<bugzilla>
{
"status":["IN_PROGRESS","CONFIRMED", "UNCONFIRMED"],
"product":"graphui",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

;Completed Items ''graphui''
<bugzilla>
{
"status":["RESOLVED","VERIFIED"],
"product":"graphui",
"include_fields":"id,version,product,component,status,resolution,summary"
}
</bugzilla>

== Jogl / Graph ==

[{{SERVER}}/bugzilla/showdependencytree.cgi?id=1064&hide_resolved=0 Dependency Tree Graph Font Issues]

[{{SERVER}}/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=IN_PROGRESS&bug_status=RESOLVED&bug_status=VERIFIED&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cversion%2Cshort_desc%2Cchangeddate&component=graph&list_id=2264&product=Jogl&query_format=advanced&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED All Jogl Graph]

;Open Items ''Jogl / graph''
<bugzilla>
{
"status":["IN_PROGRESS","CONFIRMED", "UNCONFIRMED"],
"product":"jogl",
"component":"graph",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

;Completed Items ''Jogl / graph''
<bugzilla>
{
"status":["RESOLVED","VERIFIED"],
"product":"jogl",
"component":"graph",
"include_fields":"id,version,product,component,status,resolution,summary"
}
</bugzilla>

= WebAssembly (wasm) Target Platform =

== Overview ==
See [https://jogamp.org/bugzilla//show_bug.cgi?id=1506 Bug 1506] describing this feature.

Since Java Applets are not more supported within browser or by OpenJDK for years,
it may seems feasible to evaluate the WebAssembly target running within e.g. web browser nowadays.

An initial evaluation on small C++ projects using the emscripten front-end for LLVM's clang++ to wasm compiler, which supports many ported system libraries like SDL, OpenGL, .. has been undertaken successfully with variable results.
* [https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ gfxbox2 C++/wasm evaluation]
* [https://emscripten.org/ emscripten]
* [https://webassembly.org/ WebAssembly]

The wasm target is comparable to Java bytecode but the wasm virtual machine is not as performant, efficient or flexible as actual native code. The lack of hassle free native threads and native high-performance may remind one of the first JVM steps. The wasm code runs within a virtual machine like the JVM and additionally lacks of native binding capabilities.

Some limitations may be overcome, others are likely by design as it usually runs on the same browser virtual machine as the JavaScript companion. Compromises must be made on shared memory and native threads, cached non-local file I/O and socket communication - while other native features will simply never work, e.g. operating system ioctl-calls, etc.

Opening the door for any language to be compiled to a platform independent intermediate representation (IR) like Java’s bytecode suitable for a versatile runtime environment including its virtual machine is surely still desirable.

== Initial C++/wasm Evaluation ==
[https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ Our little gfxbox2 games] compiled to [https://webassembly.org/ wasm] run about 40-60% slower within a browser than in native code, depending on coding strategy of our graphics (pixelmap vs SDL/OpenGL primitives).

The used [https://emscripten.org/ emscripten] frontend allowed us to use memory-growth, envelop files used in the wasm file, add cheap stack-overflow cockies and nullptr writes and so forth. Utilization of OpenGL ES via SDL2 was a breeze.

The underlying LLVM compiler did an excellent job and overall, the transition was easy and almost involved no code changes but dropping native thread (std::thread) usage.

The overall program structure had to be adapted to align to the single-thread main-loop workflow
and specific emscripten-javascript hooks added to allow seamless interaction.
All in all, nothing to be too afraid of and depending on the class of applications to be ported
to the browser these days, a feasible procedure.

== Java Support ==
Java bytecode compiler to wasm including some ''runtime envelop''
* [https://github.com/konsoletyper/teavm TeaVM] [https://teavm.org/docs/intro/overview.html overview]
* [https://github.com/i-net-software/JWebAssembly JWebAssembly] [https://github.com/i-net-software/JWebAssembly/wiki doc]
* [https://mirkosertic.github.io/Bytecoder/ Bytecoder]

Further interesting bits & pieces
** [https://openjdk.org/jeps/457 JEP 457: Class-File API ]
** [https://openjdk.org/projects/babylon/articles/linq Babylon]

GraalVM experimentally hosts wasm only,
but is not producing a wasm target for the wasm (browser) runtime.

* [https://www.graalvm.org/latest/reference-manual/wasm/ GraalVM + wasm]
** with the help of emscripten
** [https://www.graalvm.org/22.0/reference-manual/native-image/JNI/ GraalVM + JNI]

== Java Browser Outlook ==
So far the only question arises why reinventing the wheel once again? Dropping utilization of a well working JVM for the web had no technical reasoning.

However, in case no suitable wasm target for the Java bytecode and the Java Runtime pieces can be established, one might either want to also look into bringing back the JRE into the browser or painfully drop Java for C++, as the latter is already close to have acceptable (slower and limited) wasm target runtime properties.

= NEWT =

* [{{SERVER}}/bugzilla/showdependencytree.cgi?id=807&hide_resolved=0 Dependency Tree NEWT Input Devices]
* [{{SERVER}}/bugzilla/showdependencytree.cgi?id=814&hide_resolved=0 Dependency Tree NEWT Pointer Event]

<bugzilla>
{
"product":["newt","jinput"],
"version":["2.5.0","3.0.0","tbd"],
"cf_type":"FEATURE",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

= NEWT + Wayland =
Currently NEWT supports the X11/Xorg windowing server on Unix alike platforms.

It might be desired to add direct support to Wayland, as we already added support for
[https://jogamp.org/bugzilla/show_bug.cgi?id=1156 bare metal devices w/o a windowing system via the Linux DRM/GBM console mode]
throughout JOGL + NEWT.

= Vulkan =

<bugzilla>
{
"component":"vulkan",
"cf_type":"FEATURE",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

= Video Encoding/Decoding & Player =

Across our releases, we supported video encoding and decoding (with a player)
based on either FFmpeg or Android's library as [https://youtu.be/4gWStKCioi8?t=132 shown in this clip at 2:12 min mark].

Goal would be to
* Update general ffmpeg video decoding support
* Enhance ffmpeg video encoding support
* Potentially add better control about video-frame to framebuffer control for editing software

See [https://jogamp.org/bugzilla//buglist.cgi?bug_status=__open__&component=video&list_id=3053&product=Jogl related buglist]

<bugzilla>
{
"component":"video",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

= iOS Enhancements =

Early iOS support has been demonstrated in 2019
* [https://jausoft.com/blog/2019/06/17/jogamp-ios-arm64-bring-up/ iOS Arm64 bring-up]
* [https://jausoft.com/blog/2019/06/23/jogamp-ios-arm64-port-first-visuals/ iOS Arm64 Port: First Visuals]
* [https://jausoft.com/blog/2019/07/08/jogamp-ios-arm64-port-newt/ iOS Arm64 Port: NEWT]

Enhancing this port would allow to use JogAmp in a similar fashion as on Android,
but using an OpenJDK iOS build.

= [[SCC Overview|Source Certification Contract (SCC)]] =

[{{SERVER}}/bugzilla/showdependencytree.cgi?id=1368&hide_resolved=0 Dependency Tree]

[{{SERVER}}/bugzilla/show_bug.cgi?id=1368 Root Parent Entry]

<bugzilla>
{
"id":["1368", "1369"],
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

= OpenJFX =

[https://jogamp.org/bugzilla//show_bug.cgi?id=607#c20 Bug report 607] describes different ways to either
* enhance external rendering via JOGL into an OpenJFX UI elements, or
* to replace OpenJFX's Glass w/ NEWT and Prism's OpenGL coding with JOGL

= Misc =



<bugzilla>
{
"version":["2.5.0","3.0.0","tbd"],
"cf_type":"FEATURE",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

SW Tracking Report Feature Objectives Overview

2024-04-03T04:34:01Z

Sgothel: /* Java Support */

This list exposes building blocks
for potential use and business case scenarios
using Java & JogAmp on Desktop and Embedded Devices.

Notably [[#Graph|Graph & Graph UI]] as well as [[#NEWT_+_Wayland|Wayland]] & [[#Vulkan|Vulkan]] support could be of interest here?

Also see [[Completed Features Objectives]] ...

= Graph =
[https://jausoft.com/blog/tag/graph_type_rendering/ Graph/GraphUI Progress Blog Entries]

== Desired Work Items ==

This is an ad-hoc list of desired features and fixes,
which shall result in proper bug-reports soon.

After having reached [https://jausoft.com/blog/2024/01/21/graphui-frustum-culling-clipping-modelview-space/ UI usability with widgets and clipping],
the following items are becoming more interesting

* Fix general issues with current implementation and API, if any
* Fix Graph rendering bugs (Tessellation)
** [https://jausoft.com/blog/2024/02/13/fixing-jogamps-graph-delaunay-tessellation-of-complex-non-convex-shapes/ First round done]
* Use of super-sized triangles to render Graph lines & curves to allow
** Using a one-pass smooth AA Graph renderer to save resources otherwise used in our pass-2 FBO supersampling renderer
** Generate outlines, i.e. outlined fonts
** Generate special effects like glowing/pumping outlines indicating selection etc
* Allow passing or better attaching per-vertex color to Graph Outline (API)
* <s>Add subtitles in MediaPlayer GraphUI widget</s> ''([https://jausoft.com/blog/2024/02/07/graphui-mediaplayer-feature-complete/ done])''
* Add video encoding in our FFmpeg binding, i.e. an FFMPEGMediaRecorder (Encoding + Multiplexing)

Further more, if so desired, a C++ implementation of our Graph + GraphUI framework
may also be of interest.

In case any company or organization is interested and likes to support
this work and may also like to receive support in adopting this framework,
please contact [[Maintainer_and_Contacts#Commercial_Support|Göthel Software e.K.]]

== OpenJDK Compatibility / Integration ==

Objectives should be to allow seamless integration into
OpenJDK's deployment and JVM launch methods.

A dual JAR file to be used with and without modules is desired,
however it seems that certain JAR options are not available with this
configuration if our classes are not build as modules itself.

An optional [https://jogamp.org/bugzilla/show_bug.cgi?id=1505#c0 JVM Launch Pad (JLP)] might be helpful,
even though it instructs further complexity and is not helping
with a vanilla OpenJDK deployment.

=== OpenJDK >= 11 ===

See [https://jogamp.org/bugzilla/show_bug.cgi?id=1404 Bug 1404]

'''JVM Commandline Parameter'''

Current used 'add-opens' in my JogAmp test scripts for Java >= 11,
covering all AWT utilization including background erase is:

<pre>
--add-opens java.desktop/sun.awt=ALL-UNNAMED
--add-opens java.desktop/sun.awt.windows=ALL-UNNAMED
--add-opens java.desktop/sun.java2d=ALL-UNNAMED
</pre>

=== OpenJDK >= 2x ===

See [https://jogamp.org/bugzilla/show_bug.cgi?id=1505 Bug 1505]

'''JVM Commandline Parameter'''

Current used 'add-opens' in my JogAmp test scripts for Java >= 23,
covering all AWT utilization including background erase is:

<pre>
--add-opens java.desktop/sun.awt=ALL-UNNAMED
--add-opens java.desktop/sun.awt.windows=ALL-UNNAMED
--add-opens java.desktop/sun.java2d=ALL-UNNAMED
--TO_BE_DETERMINED
</pre>

== Graph UI ==

[https://jausoft.com/blog/2023/02/22/reimagine-java-on-desktop-bare-metal-devices/ ''Graph UI'' will enable an immersive UI within the 3D scene] on the desktop, mobile and on bare-metal embedded systems without a windowing system.

Graph UI utilizes [https://jausoft.com/blog/2011/10/05/jogljogamp-red-square-moscow-nurbs-graphicon2011/ Resolution Independent NURBS Curves Rendering using Programmable Graphics Pipeline], i.e. rendering curves directly on the GPU, resolution independent [ [https://jogamp.org/doc/gpunurbs2011/p70-santina.pdf paper], [https://jogamp.org/doc/gpunurbs2011/graphicon2011-slides.pdf slides] ].

This method allows us to have an ultimate fast font and UI rendering engine, suitable for all devices and applications. No CPU based curve nor font pre-rendering (matching a target resolution) is required.

Think of an integrated QT or OpenJFX in your 2D/3D application
working on desktop and embedded devices even w/o any windowing system on top
of a plain console [{{SERVER}}/bugzilla/show_bug.cgi?id=1156 DRM/GBM as support by JOGL(EGL) and NEWT]
as demonstrated [https://ict.zafena.se/improved-graphical-information-technology/ by Xerxes on a Raspberry Pi4].

[https://jausoft.com/blog/2023/02/22/reimagine-java-on-desktop-bare-metal-devices/ Reimagine Java on Desktop & Bare-Metal Devices]
demonstrates the updated Graph Curve Rendering and UI, while [https://jausoft.com/blog/2024/01/21/graphui-frustum-culling-clipping-modelview-space/ this update shows clipping and widgets]. [https://jausoft.com/blog/tag/graph_type_rendering/ Further updates will be posted here...].

Notably the ''Graph Curve Rendering'' is almost feature complete, as well as our own user input including gesture detection within NEWT.

;Parent Main Node
: [{{SERVER}}/bugzilla/showdependencytree.cgi?id=803&hide_resolved=0 Dependency Tree]
: [{{SERVER}}/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=IN_PROGRESS&bug_status=RESOLVED&bug_status=VERIFIED&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cversion%2Cshort_desc%2Cchangeddate&component=core&component=Plugin&list_id=2265&product=GraphUI&query_format=advanced&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED All GraphUI]

;Open Items ''graphui''
<bugzilla>
{
"status":["IN_PROGRESS","CONFIRMED", "UNCONFIRMED"],
"product":"graphui",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

;Completed Items ''graphui''
<bugzilla>
{
"status":["RESOLVED","VERIFIED"],
"product":"graphui",
"include_fields":"id,version,product,component,status,resolution,summary"
}
</bugzilla>

== Jogl / Graph ==

[{{SERVER}}/bugzilla/showdependencytree.cgi?id=1064&hide_resolved=0 Dependency Tree Graph Font Issues]

[{{SERVER}}/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=IN_PROGRESS&bug_status=RESOLVED&bug_status=VERIFIED&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cversion%2Cshort_desc%2Cchangeddate&component=graph&list_id=2264&product=Jogl&query_format=advanced&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED All Jogl Graph]

;Open Items ''Jogl / graph''
<bugzilla>
{
"status":["IN_PROGRESS","CONFIRMED", "UNCONFIRMED"],
"product":"jogl",
"component":"graph",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

;Completed Items ''Jogl / graph''
<bugzilla>
{
"status":["RESOLVED","VERIFIED"],
"product":"jogl",
"component":"graph",
"include_fields":"id,version,product,component,status,resolution,summary"
}
</bugzilla>

= WebAssembly (wasm) Target Platform =

== Overview ==
See [https://jogamp.org/bugzilla//show_bug.cgi?id=1506 Bug 1506] describing this feature.

Since Java Applets are not more supported within browser or by OpenJDK for years,
it may seems feasible to evaluate the WebAssembly target running within e.g. web browser nowadays.

An initial evaluation on small C++ projects using the emscripten front-end for LLVM's clang++ to wasm compiler, which supports many ported system libraries like SDL, OpenGL, .. has been undertaken successfully with variable results.
* [https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ gfxbox2 C++/wasm evaluation]
* [https://emscripten.org/ emscripten]
* [https://webassembly.org/ WebAssembly]

The wasm target is comparable to Java bytecode but the wasm virtual machine is not as performant, efficient or flexible as actual native code. The lack of hassle free native threads and native high-performance may remind one of the first JVM steps. The wasm code runs within a virtual machine like the JVM and additionally lacks of native binding capabilities.

Some limitations may be overcome, others are likely by design as it usually runs on the same browser virtual machine as the JavaScript companion. Compromises must be made on shared memory and native threads, cached non-local file I/O and socket communication - while other native features will simply never work, e.g. operating system ioctl-calls, etc.

Opening the door for any language to be compiled to a platform independent intermediate representation (IR) like Java’s bytecode suitable for a versatile runtime environment including its virtual machine is surely still desirable.

== Initial C++/wasm Evaluation ==
[https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ Our little gfxbox2 games] compiled to [https://webassembly.org/ wasm] run about 40-60% slower within a browser than in native code, depending on coding strategy of our graphics (pixelmap vs SDL/OpenGL primitives).

The used [https://emscripten.org/ emscripten] frontend allowed us to use memory-growth, envelop files used in the wasm file, add cheap stack-overflow cockies and nullptr writes and so forth. Utilization of OpenGL ES via SDL2 was a breeze.

The underlying LLVM compiler did an excellent job and overall, the transition was easy and almost involved no code changes but dropping native thread (std::thread) usage.

The overall program structure had to be adapted to align to the single-thread main-loop workflow
and specific emscripten-javascript hooks added to allow seamless interaction.
All in all, nothing to be too afraid of and depending on the class of applications to be ported
to the browser these days, a feasible procedure.

== Java Support ==
Java bytecode compiler to wasm including some ''runtime envelop''
* [https://github.com/konsoletyper/teavm TeaVM] [https://teavm.org/docs/intro/overview.html overview)
* [https://github.com/i-net-software/JWebAssembly JWebAssembly] [https://github.com/i-net-software/JWebAssembly/wiki doc]
* [https://mirkosertic.github.io/Bytecoder/ Bytecoder]

Further interesting bits & pieces
** [https://openjdk.org/jeps/457 JEP 457: Class-File API ]
** [https://openjdk.org/projects/babylon/articles/linq Babylon]

GraalVM experimentally hosts wasm only,
but is not producing a wasm target for the wasm (browser) runtime.

* [https://www.graalvm.org/latest/reference-manual/wasm/ GraalVM + wasm]
** with the help of emscripten
** [https://www.graalvm.org/22.0/reference-manual/native-image/JNI/ GraalVM + JNI]

== Java Browser Outlook ==
So far the only question arises why reinventing the wheel once again? Dropping utilization of a well working JVM for the web had no technical reasoning.

However, in case no suitable wasm target for the Java bytecode and the Java Runtime pieces can be established, one might either want to also look into bringing back the JRE into the browser or painfully drop Java for C++, as the latter is already close to have acceptable (slower and limited) wasm target runtime properties.

= NEWT =

* [{{SERVER}}/bugzilla/showdependencytree.cgi?id=807&hide_resolved=0 Dependency Tree NEWT Input Devices]
* [{{SERVER}}/bugzilla/showdependencytree.cgi?id=814&hide_resolved=0 Dependency Tree NEWT Pointer Event]

<bugzilla>
{
"product":["newt","jinput"],
"version":["2.5.0","3.0.0","tbd"],
"cf_type":"FEATURE",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

= NEWT + Wayland =
Currently NEWT supports the X11/Xorg windowing server on Unix alike platforms.

It might be desired to add direct support to Wayland, as we already added support for
[https://jogamp.org/bugzilla/show_bug.cgi?id=1156 bare metal devices w/o a windowing system via the Linux DRM/GBM console mode]
throughout JOGL + NEWT.

= Vulkan =

<bugzilla>
{
"component":"vulkan",
"cf_type":"FEATURE",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

= Video Encoding/Decoding & Player =

Across our releases, we supported video encoding and decoding (with a player)
based on either FFmpeg or Android's library as [https://youtu.be/4gWStKCioi8?t=132 shown in this clip at 2:12 min mark].

Goal would be to
* Update general ffmpeg video decoding support
* Enhance ffmpeg video encoding support
* Potentially add better control about video-frame to framebuffer control for editing software

See [https://jogamp.org/bugzilla//buglist.cgi?bug_status=__open__&component=video&list_id=3053&product=Jogl related buglist]

<bugzilla>
{
"component":"video",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

= iOS Enhancements =

Early iOS support has been demonstrated in 2019
* [https://jausoft.com/blog/2019/06/17/jogamp-ios-arm64-bring-up/ iOS Arm64 bring-up]
* [https://jausoft.com/blog/2019/06/23/jogamp-ios-arm64-port-first-visuals/ iOS Arm64 Port: First Visuals]
* [https://jausoft.com/blog/2019/07/08/jogamp-ios-arm64-port-newt/ iOS Arm64 Port: NEWT]

Enhancing this port would allow to use JogAmp in a similar fashion as on Android,
but using an OpenJDK iOS build.

= [[SCC Overview|Source Certification Contract (SCC)]] =

[{{SERVER}}/bugzilla/showdependencytree.cgi?id=1368&hide_resolved=0 Dependency Tree]

[{{SERVER}}/bugzilla/show_bug.cgi?id=1368 Root Parent Entry]

<bugzilla>
{
"id":["1368", "1369"],
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

= OpenJFX =

[https://jogamp.org/bugzilla//show_bug.cgi?id=607#c20 Bug report 607] describes different ways to either
* enhance external rendering via JOGL into an OpenJFX UI elements, or
* to replace OpenJFX's Glass w/ NEWT and Prism's OpenGL coding with JOGL

= Misc =



<bugzilla>
{
"version":["2.5.0","3.0.0","tbd"],
"cf_type":"FEATURE",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

SW Tracking Report Feature Objectives Overview

2024-04-03T04:32:05Z

Sgothel: /* Java Support */

This list exposes building blocks
for potential use and business case scenarios
using Java & JogAmp on Desktop and Embedded Devices.

Notably [[#Graph|Graph & Graph UI]] as well as [[#NEWT_+_Wayland|Wayland]] & [[#Vulkan|Vulkan]] support could be of interest here?

Also see [[Completed Features Objectives]] ...

= Graph =
[https://jausoft.com/blog/tag/graph_type_rendering/ Graph/GraphUI Progress Blog Entries]

== Desired Work Items ==

This is an ad-hoc list of desired features and fixes,
which shall result in proper bug-reports soon.

After having reached [https://jausoft.com/blog/2024/01/21/graphui-frustum-culling-clipping-modelview-space/ UI usability with widgets and clipping],
the following items are becoming more interesting

* Fix general issues with current implementation and API, if any
* Fix Graph rendering bugs (Tessellation)
** [https://jausoft.com/blog/2024/02/13/fixing-jogamps-graph-delaunay-tessellation-of-complex-non-convex-shapes/ First round done]
* Use of super-sized triangles to render Graph lines & curves to allow
** Using a one-pass smooth AA Graph renderer to save resources otherwise used in our pass-2 FBO supersampling renderer
** Generate outlines, i.e. outlined fonts
** Generate special effects like glowing/pumping outlines indicating selection etc
* Allow passing or better attaching per-vertex color to Graph Outline (API)
* <s>Add subtitles in MediaPlayer GraphUI widget</s> ''([https://jausoft.com/blog/2024/02/07/graphui-mediaplayer-feature-complete/ done])''
* Add video encoding in our FFmpeg binding, i.e. an FFMPEGMediaRecorder (Encoding + Multiplexing)

Further more, if so desired, a C++ implementation of our Graph + GraphUI framework
may also be of interest.

In case any company or organization is interested and likes to support
this work and may also like to receive support in adopting this framework,
please contact [[Maintainer_and_Contacts#Commercial_Support|Göthel Software e.K.]]

== OpenJDK Compatibility / Integration ==

Objectives should be to allow seamless integration into
OpenJDK's deployment and JVM launch methods.

A dual JAR file to be used with and without modules is desired,
however it seems that certain JAR options are not available with this
configuration if our classes are not build as modules itself.

An optional [https://jogamp.org/bugzilla/show_bug.cgi?id=1505#c0 JVM Launch Pad (JLP)] might be helpful,
even though it instructs further complexity and is not helping
with a vanilla OpenJDK deployment.

=== OpenJDK >= 11 ===

See [https://jogamp.org/bugzilla/show_bug.cgi?id=1404 Bug 1404]

'''JVM Commandline Parameter'''

Current used 'add-opens' in my JogAmp test scripts for Java >= 11,
covering all AWT utilization including background erase is:

<pre>
--add-opens java.desktop/sun.awt=ALL-UNNAMED
--add-opens java.desktop/sun.awt.windows=ALL-UNNAMED
--add-opens java.desktop/sun.java2d=ALL-UNNAMED
</pre>

=== OpenJDK >= 2x ===

See [https://jogamp.org/bugzilla/show_bug.cgi?id=1505 Bug 1505]

'''JVM Commandline Parameter'''

Current used 'add-opens' in my JogAmp test scripts for Java >= 23,
covering all AWT utilization including background erase is:

<pre>
--add-opens java.desktop/sun.awt=ALL-UNNAMED
--add-opens java.desktop/sun.awt.windows=ALL-UNNAMED
--add-opens java.desktop/sun.java2d=ALL-UNNAMED
--TO_BE_DETERMINED
</pre>

== Graph UI ==

[https://jausoft.com/blog/2023/02/22/reimagine-java-on-desktop-bare-metal-devices/ ''Graph UI'' will enable an immersive UI within the 3D scene] on the desktop, mobile and on bare-metal embedded systems without a windowing system.

Graph UI utilizes [https://jausoft.com/blog/2011/10/05/jogljogamp-red-square-moscow-nurbs-graphicon2011/ Resolution Independent NURBS Curves Rendering using Programmable Graphics Pipeline], i.e. rendering curves directly on the GPU, resolution independent [ [https://jogamp.org/doc/gpunurbs2011/p70-santina.pdf paper], [https://jogamp.org/doc/gpunurbs2011/graphicon2011-slides.pdf slides] ].

This method allows us to have an ultimate fast font and UI rendering engine, suitable for all devices and applications. No CPU based curve nor font pre-rendering (matching a target resolution) is required.

Think of an integrated QT or OpenJFX in your 2D/3D application
working on desktop and embedded devices even w/o any windowing system on top
of a plain console [{{SERVER}}/bugzilla/show_bug.cgi?id=1156 DRM/GBM as support by JOGL(EGL) and NEWT]
as demonstrated [https://ict.zafena.se/improved-graphical-information-technology/ by Xerxes on a Raspberry Pi4].

[https://jausoft.com/blog/2023/02/22/reimagine-java-on-desktop-bare-metal-devices/ Reimagine Java on Desktop & Bare-Metal Devices]
demonstrates the updated Graph Curve Rendering and UI, while [https://jausoft.com/blog/2024/01/21/graphui-frustum-culling-clipping-modelview-space/ this update shows clipping and widgets]. [https://jausoft.com/blog/tag/graph_type_rendering/ Further updates will be posted here...].

Notably the ''Graph Curve Rendering'' is almost feature complete, as well as our own user input including gesture detection within NEWT.

;Parent Main Node
: [{{SERVER}}/bugzilla/showdependencytree.cgi?id=803&hide_resolved=0 Dependency Tree]
: [{{SERVER}}/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=IN_PROGRESS&bug_status=RESOLVED&bug_status=VERIFIED&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cversion%2Cshort_desc%2Cchangeddate&component=core&component=Plugin&list_id=2265&product=GraphUI&query_format=advanced&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED All GraphUI]

;Open Items ''graphui''
<bugzilla>
{
"status":["IN_PROGRESS","CONFIRMED", "UNCONFIRMED"],
"product":"graphui",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

;Completed Items ''graphui''
<bugzilla>
{
"status":["RESOLVED","VERIFIED"],
"product":"graphui",
"include_fields":"id,version,product,component,status,resolution,summary"
}
</bugzilla>

== Jogl / Graph ==

[{{SERVER}}/bugzilla/showdependencytree.cgi?id=1064&hide_resolved=0 Dependency Tree Graph Font Issues]

[{{SERVER}}/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=IN_PROGRESS&bug_status=RESOLVED&bug_status=VERIFIED&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cversion%2Cshort_desc%2Cchangeddate&component=graph&list_id=2264&product=Jogl&query_format=advanced&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED All Jogl Graph]

;Open Items ''Jogl / graph''
<bugzilla>
{
"status":["IN_PROGRESS","CONFIRMED", "UNCONFIRMED"],
"product":"jogl",
"component":"graph",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

;Completed Items ''Jogl / graph''
<bugzilla>
{
"status":["RESOLVED","VERIFIED"],
"product":"jogl",
"component":"graph",
"include_fields":"id,version,product,component,status,resolution,summary"
}
</bugzilla>

= WebAssembly (wasm) Target Platform =

== Overview ==
See [https://jogamp.org/bugzilla//show_bug.cgi?id=1506 Bug 1506] describing this feature.

Since Java Applets are not more supported within browser or by OpenJDK for years,
it may seems feasible to evaluate the WebAssembly target running within e.g. web browser nowadays.

An initial evaluation on small C++ projects using the emscripten front-end for LLVM's clang++ to wasm compiler, which supports many ported system libraries like SDL, OpenGL, .. has been undertaken successfully with variable results.
* [https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ gfxbox2 C++/wasm evaluation]
* [https://emscripten.org/ emscripten]
* [https://webassembly.org/ WebAssembly]

The wasm target is comparable to Java bytecode but the wasm virtual machine is not as performant, efficient or flexible as actual native code. The lack of hassle free native threads and native high-performance may remind one of the first JVM steps. The wasm code runs within a virtual machine like the JVM and additionally lacks of native binding capabilities.

Some limitations may be overcome, others are likely by design as it usually runs on the same browser virtual machine as the JavaScript companion. Compromises must be made on shared memory and native threads, cached non-local file I/O and socket communication - while other native features will simply never work, e.g. operating system ioctl-calls, etc.

Opening the door for any language to be compiled to a platform independent intermediate representation (IR) like Java’s bytecode suitable for a versatile runtime environment including its virtual machine is surely still desirable.

== Initial C++/wasm Evaluation ==
[https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ Our little gfxbox2 games] compiled to [https://webassembly.org/ wasm] run about 40-60% slower within a browser than in native code, depending on coding strategy of our graphics (pixelmap vs SDL/OpenGL primitives).

The used [https://emscripten.org/ emscripten] frontend allowed us to use memory-growth, envelop files used in the wasm file, add cheap stack-overflow cockies and nullptr writes and so forth. Utilization of OpenGL ES via SDL2 was a breeze.

The underlying LLVM compiler did an excellent job and overall, the transition was easy and almost involved no code changes but dropping native thread (std::thread) usage.

The overall program structure had to be adapted to align to the single-thread main-loop workflow
and specific emscripten-javascript hooks added to allow seamless interaction.
All in all, nothing to be too afraid of and depending on the class of applications to be ported
to the browser these days, a feasible procedure.

== Java Support ==
Java bytecode compiler to wasm including some ''runtime envelop''
* [https://github.com/konsoletyper/teavm TeaVM]
* [https://github.com/i-net-software/JWebAssembly JWebAssembly]
* [https://mirkosertic.github.io/Bytecoder/ Bytecoder]

Further interesting bits & pieces
** [https://openjdk.org/jeps/457 JEP 457: Class-File API ]
** [https://openjdk.org/projects/babylon/articles/linq Babylon]

GraalVM experimentally hosts wasm only,
but is not producing a wasm target for the wasm (browser) runtime.

* [https://www.graalvm.org/latest/reference-manual/wasm/ GraalVM + wasm]
** with the help of emscripten
** [https://www.graalvm.org/22.0/reference-manual/native-image/JNI/ GraalVM + JNI]

== Java Browser Outlook ==
So far the only question arises why reinventing the wheel once again? Dropping utilization of a well working JVM for the web had no technical reasoning.

However, in case no suitable wasm target for the Java bytecode and the Java Runtime pieces can be established, one might either want to also look into bringing back the JRE into the browser or painfully drop Java for C++, as the latter is already close to have acceptable (slower and limited) wasm target runtime properties.

= NEWT =

* [{{SERVER}}/bugzilla/showdependencytree.cgi?id=807&hide_resolved=0 Dependency Tree NEWT Input Devices]
* [{{SERVER}}/bugzilla/showdependencytree.cgi?id=814&hide_resolved=0 Dependency Tree NEWT Pointer Event]

<bugzilla>
{
"product":["newt","jinput"],
"version":["2.5.0","3.0.0","tbd"],
"cf_type":"FEATURE",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

= NEWT + Wayland =
Currently NEWT supports the X11/Xorg windowing server on Unix alike platforms.

It might be desired to add direct support to Wayland, as we already added support for
[https://jogamp.org/bugzilla/show_bug.cgi?id=1156 bare metal devices w/o a windowing system via the Linux DRM/GBM console mode]
throughout JOGL + NEWT.

= Vulkan =

<bugzilla>
{
"component":"vulkan",
"cf_type":"FEATURE",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

= Video Encoding/Decoding & Player =

Across our releases, we supported video encoding and decoding (with a player)
based on either FFmpeg or Android's library as [https://youtu.be/4gWStKCioi8?t=132 shown in this clip at 2:12 min mark].

Goal would be to
* Update general ffmpeg video decoding support
* Enhance ffmpeg video encoding support
* Potentially add better control about video-frame to framebuffer control for editing software

See [https://jogamp.org/bugzilla//buglist.cgi?bug_status=__open__&component=video&list_id=3053&product=Jogl related buglist]

<bugzilla>
{
"component":"video",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

= iOS Enhancements =

Early iOS support has been demonstrated in 2019
* [https://jausoft.com/blog/2019/06/17/jogamp-ios-arm64-bring-up/ iOS Arm64 bring-up]
* [https://jausoft.com/blog/2019/06/23/jogamp-ios-arm64-port-first-visuals/ iOS Arm64 Port: First Visuals]
* [https://jausoft.com/blog/2019/07/08/jogamp-ios-arm64-port-newt/ iOS Arm64 Port: NEWT]

Enhancing this port would allow to use JogAmp in a similar fashion as on Android,
but using an OpenJDK iOS build.

= [[SCC Overview|Source Certification Contract (SCC)]] =

[{{SERVER}}/bugzilla/showdependencytree.cgi?id=1368&hide_resolved=0 Dependency Tree]

[{{SERVER}}/bugzilla/show_bug.cgi?id=1368 Root Parent Entry]

<bugzilla>
{
"id":["1368", "1369"],
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

= OpenJFX =

[https://jogamp.org/bugzilla//show_bug.cgi?id=607#c20 Bug report 607] describes different ways to either
* enhance external rendering via JOGL into an OpenJFX UI elements, or
* to replace OpenJFX's Glass w/ NEWT and Prism's OpenGL coding with JOGL

= Misc =



<bugzilla>
{
"version":["2.5.0","3.0.0","tbd"],
"cf_type":"FEATURE",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

SW Tracking Report Feature Objectives Overview

2024-04-03T04:17:36Z

Sgothel: /* Java Support */

This list exposes building blocks
for potential use and business case scenarios
using Java & JogAmp on Desktop and Embedded Devices.

Notably [[#Graph|Graph & Graph UI]] as well as [[#NEWT_+_Wayland|Wayland]] & [[#Vulkan|Vulkan]] support could be of interest here?

Also see [[Completed Features Objectives]] ...

= Graph =
[https://jausoft.com/blog/tag/graph_type_rendering/ Graph/GraphUI Progress Blog Entries]

== Desired Work Items ==

This is an ad-hoc list of desired features and fixes,
which shall result in proper bug-reports soon.

After having reached [https://jausoft.com/blog/2024/01/21/graphui-frustum-culling-clipping-modelview-space/ UI usability with widgets and clipping],
the following items are becoming more interesting

* Fix general issues with current implementation and API, if any
* Fix Graph rendering bugs (Tessellation)
** [https://jausoft.com/blog/2024/02/13/fixing-jogamps-graph-delaunay-tessellation-of-complex-non-convex-shapes/ First round done]
* Use of super-sized triangles to render Graph lines & curves to allow
** Using a one-pass smooth AA Graph renderer to save resources otherwise used in our pass-2 FBO supersampling renderer
** Generate outlines, i.e. outlined fonts
** Generate special effects like glowing/pumping outlines indicating selection etc
* Allow passing or better attaching per-vertex color to Graph Outline (API)
* <s>Add subtitles in MediaPlayer GraphUI widget</s> ''([https://jausoft.com/blog/2024/02/07/graphui-mediaplayer-feature-complete/ done])''
* Add video encoding in our FFmpeg binding, i.e. an FFMPEGMediaRecorder (Encoding + Multiplexing)

Further more, if so desired, a C++ implementation of our Graph + GraphUI framework
may also be of interest.

In case any company or organization is interested and likes to support
this work and may also like to receive support in adopting this framework,
please contact [[Maintainer_and_Contacts#Commercial_Support|Göthel Software e.K.]]

== OpenJDK Compatibility / Integration ==

Objectives should be to allow seamless integration into
OpenJDK's deployment and JVM launch methods.

A dual JAR file to be used with and without modules is desired,
however it seems that certain JAR options are not available with this
configuration if our classes are not build as modules itself.

An optional [https://jogamp.org/bugzilla/show_bug.cgi?id=1505#c0 JVM Launch Pad (JLP)] might be helpful,
even though it instructs further complexity and is not helping
with a vanilla OpenJDK deployment.

=== OpenJDK >= 11 ===

See [https://jogamp.org/bugzilla/show_bug.cgi?id=1404 Bug 1404]

'''JVM Commandline Parameter'''

Current used 'add-opens' in my JogAmp test scripts for Java >= 11,
covering all AWT utilization including background erase is:

<pre>
--add-opens java.desktop/sun.awt=ALL-UNNAMED
--add-opens java.desktop/sun.awt.windows=ALL-UNNAMED
--add-opens java.desktop/sun.java2d=ALL-UNNAMED
</pre>

=== OpenJDK >= 2x ===

See [https://jogamp.org/bugzilla/show_bug.cgi?id=1505 Bug 1505]

'''JVM Commandline Parameter'''

Current used 'add-opens' in my JogAmp test scripts for Java >= 23,
covering all AWT utilization including background erase is:

<pre>
--add-opens java.desktop/sun.awt=ALL-UNNAMED
--add-opens java.desktop/sun.awt.windows=ALL-UNNAMED
--add-opens java.desktop/sun.java2d=ALL-UNNAMED
--TO_BE_DETERMINED
</pre>

== Graph UI ==

[https://jausoft.com/blog/2023/02/22/reimagine-java-on-desktop-bare-metal-devices/ ''Graph UI'' will enable an immersive UI within the 3D scene] on the desktop, mobile and on bare-metal embedded systems without a windowing system.

Graph UI utilizes [https://jausoft.com/blog/2011/10/05/jogljogamp-red-square-moscow-nurbs-graphicon2011/ Resolution Independent NURBS Curves Rendering using Programmable Graphics Pipeline], i.e. rendering curves directly on the GPU, resolution independent [ [https://jogamp.org/doc/gpunurbs2011/p70-santina.pdf paper], [https://jogamp.org/doc/gpunurbs2011/graphicon2011-slides.pdf slides] ].

This method allows us to have an ultimate fast font and UI rendering engine, suitable for all devices and applications. No CPU based curve nor font pre-rendering (matching a target resolution) is required.

Think of an integrated QT or OpenJFX in your 2D/3D application
working on desktop and embedded devices even w/o any windowing system on top
of a plain console [{{SERVER}}/bugzilla/show_bug.cgi?id=1156 DRM/GBM as support by JOGL(EGL) and NEWT]
as demonstrated [https://ict.zafena.se/improved-graphical-information-technology/ by Xerxes on a Raspberry Pi4].

[https://jausoft.com/blog/2023/02/22/reimagine-java-on-desktop-bare-metal-devices/ Reimagine Java on Desktop & Bare-Metal Devices]
demonstrates the updated Graph Curve Rendering and UI, while [https://jausoft.com/blog/2024/01/21/graphui-frustum-culling-clipping-modelview-space/ this update shows clipping and widgets]. [https://jausoft.com/blog/tag/graph_type_rendering/ Further updates will be posted here...].

Notably the ''Graph Curve Rendering'' is almost feature complete, as well as our own user input including gesture detection within NEWT.

;Parent Main Node
: [{{SERVER}}/bugzilla/showdependencytree.cgi?id=803&hide_resolved=0 Dependency Tree]
: [{{SERVER}}/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=IN_PROGRESS&bug_status=RESOLVED&bug_status=VERIFIED&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cversion%2Cshort_desc%2Cchangeddate&component=core&component=Plugin&list_id=2265&product=GraphUI&query_format=advanced&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED All GraphUI]

;Open Items ''graphui''
<bugzilla>
{
"status":["IN_PROGRESS","CONFIRMED", "UNCONFIRMED"],
"product":"graphui",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

;Completed Items ''graphui''
<bugzilla>
{
"status":["RESOLVED","VERIFIED"],
"product":"graphui",
"include_fields":"id,version,product,component,status,resolution,summary"
}
</bugzilla>

== Jogl / Graph ==

[{{SERVER}}/bugzilla/showdependencytree.cgi?id=1064&hide_resolved=0 Dependency Tree Graph Font Issues]

[{{SERVER}}/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=IN_PROGRESS&bug_status=RESOLVED&bug_status=VERIFIED&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cversion%2Cshort_desc%2Cchangeddate&component=graph&list_id=2264&product=Jogl&query_format=advanced&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED All Jogl Graph]

;Open Items ''Jogl / graph''
<bugzilla>
{
"status":["IN_PROGRESS","CONFIRMED", "UNCONFIRMED"],
"product":"jogl",
"component":"graph",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

;Completed Items ''Jogl / graph''
<bugzilla>
{
"status":["RESOLVED","VERIFIED"],
"product":"jogl",
"component":"graph",
"include_fields":"id,version,product,component,status,resolution,summary"
}
</bugzilla>

= WebAssembly (wasm) Target Platform =

== Overview ==
See [https://jogamp.org/bugzilla//show_bug.cgi?id=1506 Bug 1506] describing this feature.

Since Java Applets are not more supported within browser or by OpenJDK for years,
it may seems feasible to evaluate the WebAssembly target running within e.g. web browser nowadays.

An initial evaluation on small C++ projects using the emscripten front-end for LLVM's clang++ to wasm compiler, which supports many ported system libraries like SDL, OpenGL, .. has been undertaken successfully with variable results.
* [https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ gfxbox2 C++/wasm evaluation]
* [https://emscripten.org/ emscripten]
* [https://webassembly.org/ WebAssembly]

The wasm target is comparable to Java bytecode but the wasm virtual machine is not as performant, efficient or flexible as actual native code. The lack of hassle free native threads and native high-performance may remind one of the first JVM steps. The wasm code runs within a virtual machine like the JVM and additionally lacks of native binding capabilities.

Some limitations may be overcome, others are likely by design as it usually runs on the same browser virtual machine as the JavaScript companion. Compromises must be made on shared memory and native threads, cached non-local file I/O and socket communication - while other native features will simply never work, e.g. operating system ioctl-calls, etc.

Opening the door for any language to be compiled to a platform independent intermediate representation (IR) like Java’s bytecode suitable for a versatile runtime environment including its virtual machine is surely still desirable.

== Initial C++/wasm Evaluation ==
[https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ Our little gfxbox2 games] compiled to [https://webassembly.org/ wasm] run about 40-60% slower within a browser than in native code, depending on coding strategy of our graphics (pixelmap vs SDL/OpenGL primitives).

The used [https://emscripten.org/ emscripten] frontend allowed us to use memory-growth, envelop files used in the wasm file, add cheap stack-overflow cockies and nullptr writes and so forth. Utilization of OpenGL ES via SDL2 was a breeze.

The underlying LLVM compiler did an excellent job and overall, the transition was easy and almost involved no code changes but dropping native thread (std::thread) usage.

The overall program structure had to be adapted to align to the single-thread main-loop workflow
and specific emscripten-javascript hooks added to allow seamless interaction.
All in all, nothing to be too afraid of and depending on the class of applications to be ported
to the browser these days, a feasible procedure.

== Java Support ==
Java support for the WebAssembly target are claimed by
* [https://github.com/i-net-software/JWebAssembly JWebAssembly]
* [https://github.com/konsoletyper/teavm TeaVM]
* [https://mirkosertic.github.io/Bytecoder/ Bytecoder]

Further interesting bits & pieces
** [https://openjdk.org/jeps/457 JEP 457: Class-File API ]
** [https://openjdk.org/projects/babylon/articles/linq Babylon]

GraalVM experimentally hosts wasm only,
but is not producing a wasm target for the wasm (browser) runtime.

* [https://www.graalvm.org/latest/reference-manual/wasm/ GraalVM + wasm]
** with the help of emscripten
** [https://www.graalvm.org/22.0/reference-manual/native-image/JNI/ GraalVM + JNI]

== Java Browser Outlook ==
So far the only question arises why reinventing the wheel once again? Dropping utilization of a well working JVM for the web had no technical reasoning.

However, in case no suitable wasm target for the Java bytecode and the Java Runtime pieces can be established, one might either want to also look into bringing back the JRE into the browser or painfully drop Java for C++, as the latter is already close to have acceptable (slower and limited) wasm target runtime properties.

= NEWT =

* [{{SERVER}}/bugzilla/showdependencytree.cgi?id=807&hide_resolved=0 Dependency Tree NEWT Input Devices]
* [{{SERVER}}/bugzilla/showdependencytree.cgi?id=814&hide_resolved=0 Dependency Tree NEWT Pointer Event]

<bugzilla>
{
"product":["newt","jinput"],
"version":["2.5.0","3.0.0","tbd"],
"cf_type":"FEATURE",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

= NEWT + Wayland =
Currently NEWT supports the X11/Xorg windowing server on Unix alike platforms.

It might be desired to add direct support to Wayland, as we already added support for
[https://jogamp.org/bugzilla/show_bug.cgi?id=1156 bare metal devices w/o a windowing system via the Linux DRM/GBM console mode]
throughout JOGL + NEWT.

= Vulkan =

<bugzilla>
{
"component":"vulkan",
"cf_type":"FEATURE",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

= Video Encoding/Decoding & Player =

Across our releases, we supported video encoding and decoding (with a player)
based on either FFmpeg or Android's library as [https://youtu.be/4gWStKCioi8?t=132 shown in this clip at 2:12 min mark].

Goal would be to
* Update general ffmpeg video decoding support
* Enhance ffmpeg video encoding support
* Potentially add better control about video-frame to framebuffer control for editing software

See [https://jogamp.org/bugzilla//buglist.cgi?bug_status=__open__&component=video&list_id=3053&product=Jogl related buglist]

<bugzilla>
{
"component":"video",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

= iOS Enhancements =

Early iOS support has been demonstrated in 2019
* [https://jausoft.com/blog/2019/06/17/jogamp-ios-arm64-bring-up/ iOS Arm64 bring-up]
* [https://jausoft.com/blog/2019/06/23/jogamp-ios-arm64-port-first-visuals/ iOS Arm64 Port: First Visuals]
* [https://jausoft.com/blog/2019/07/08/jogamp-ios-arm64-port-newt/ iOS Arm64 Port: NEWT]

Enhancing this port would allow to use JogAmp in a similar fashion as on Android,
but using an OpenJDK iOS build.

= [[SCC Overview|Source Certification Contract (SCC)]] =

[{{SERVER}}/bugzilla/showdependencytree.cgi?id=1368&hide_resolved=0 Dependency Tree]

[{{SERVER}}/bugzilla/show_bug.cgi?id=1368 Root Parent Entry]

<bugzilla>
{
"id":["1368", "1369"],
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

= OpenJFX =

[https://jogamp.org/bugzilla//show_bug.cgi?id=607#c20 Bug report 607] describes different ways to either
* enhance external rendering via JOGL into an OpenJFX UI elements, or
* to replace OpenJFX's Glass w/ NEWT and Prism's OpenGL coding with JOGL

= Misc =



<bugzilla>
{
"version":["2.5.0","3.0.0","tbd"],
"cf_type":"FEATURE",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

SW Tracking Report Feature Objectives Overview

2024-04-03T04:11:19Z

Sgothel: /* Java Support */

This list exposes building blocks
for potential use and business case scenarios
using Java & JogAmp on Desktop and Embedded Devices.

Notably [[#Graph|Graph & Graph UI]] as well as [[#NEWT_+_Wayland|Wayland]] & [[#Vulkan|Vulkan]] support could be of interest here?

Also see [[Completed Features Objectives]] ...

= Graph =
[https://jausoft.com/blog/tag/graph_type_rendering/ Graph/GraphUI Progress Blog Entries]

== Desired Work Items ==

This is an ad-hoc list of desired features and fixes,
which shall result in proper bug-reports soon.

After having reached [https://jausoft.com/blog/2024/01/21/graphui-frustum-culling-clipping-modelview-space/ UI usability with widgets and clipping],
the following items are becoming more interesting

* Fix general issues with current implementation and API, if any
* Fix Graph rendering bugs (Tessellation)
** [https://jausoft.com/blog/2024/02/13/fixing-jogamps-graph-delaunay-tessellation-of-complex-non-convex-shapes/ First round done]
* Use of super-sized triangles to render Graph lines & curves to allow
** Using a one-pass smooth AA Graph renderer to save resources otherwise used in our pass-2 FBO supersampling renderer
** Generate outlines, i.e. outlined fonts
** Generate special effects like glowing/pumping outlines indicating selection etc
* Allow passing or better attaching per-vertex color to Graph Outline (API)
* <s>Add subtitles in MediaPlayer GraphUI widget</s> ''([https://jausoft.com/blog/2024/02/07/graphui-mediaplayer-feature-complete/ done])''
* Add video encoding in our FFmpeg binding, i.e. an FFMPEGMediaRecorder (Encoding + Multiplexing)

Further more, if so desired, a C++ implementation of our Graph + GraphUI framework
may also be of interest.

In case any company or organization is interested and likes to support
this work and may also like to receive support in adopting this framework,
please contact [[Maintainer_and_Contacts#Commercial_Support|Göthel Software e.K.]]

== OpenJDK Compatibility / Integration ==

Objectives should be to allow seamless integration into
OpenJDK's deployment and JVM launch methods.

A dual JAR file to be used with and without modules is desired,
however it seems that certain JAR options are not available with this
configuration if our classes are not build as modules itself.

An optional [https://jogamp.org/bugzilla/show_bug.cgi?id=1505#c0 JVM Launch Pad (JLP)] might be helpful,
even though it instructs further complexity and is not helping
with a vanilla OpenJDK deployment.

=== OpenJDK >= 11 ===

See [https://jogamp.org/bugzilla/show_bug.cgi?id=1404 Bug 1404]

'''JVM Commandline Parameter'''

Current used 'add-opens' in my JogAmp test scripts for Java >= 11,
covering all AWT utilization including background erase is:

<pre>
--add-opens java.desktop/sun.awt=ALL-UNNAMED
--add-opens java.desktop/sun.awt.windows=ALL-UNNAMED
--add-opens java.desktop/sun.java2d=ALL-UNNAMED
</pre>

=== OpenJDK >= 2x ===

See [https://jogamp.org/bugzilla/show_bug.cgi?id=1505 Bug 1505]

'''JVM Commandline Parameter'''

Current used 'add-opens' in my JogAmp test scripts for Java >= 23,
covering all AWT utilization including background erase is:

<pre>
--add-opens java.desktop/sun.awt=ALL-UNNAMED
--add-opens java.desktop/sun.awt.windows=ALL-UNNAMED
--add-opens java.desktop/sun.java2d=ALL-UNNAMED
--TO_BE_DETERMINED
</pre>

== Graph UI ==

[https://jausoft.com/blog/2023/02/22/reimagine-java-on-desktop-bare-metal-devices/ ''Graph UI'' will enable an immersive UI within the 3D scene] on the desktop, mobile and on bare-metal embedded systems without a windowing system.

Graph UI utilizes [https://jausoft.com/blog/2011/10/05/jogljogamp-red-square-moscow-nurbs-graphicon2011/ Resolution Independent NURBS Curves Rendering using Programmable Graphics Pipeline], i.e. rendering curves directly on the GPU, resolution independent [ [https://jogamp.org/doc/gpunurbs2011/p70-santina.pdf paper], [https://jogamp.org/doc/gpunurbs2011/graphicon2011-slides.pdf slides] ].

This method allows us to have an ultimate fast font and UI rendering engine, suitable for all devices and applications. No CPU based curve nor font pre-rendering (matching a target resolution) is required.

Think of an integrated QT or OpenJFX in your 2D/3D application
working on desktop and embedded devices even w/o any windowing system on top
of a plain console [{{SERVER}}/bugzilla/show_bug.cgi?id=1156 DRM/GBM as support by JOGL(EGL) and NEWT]
as demonstrated [https://ict.zafena.se/improved-graphical-information-technology/ by Xerxes on a Raspberry Pi4].

[https://jausoft.com/blog/2023/02/22/reimagine-java-on-desktop-bare-metal-devices/ Reimagine Java on Desktop & Bare-Metal Devices]
demonstrates the updated Graph Curve Rendering and UI, while [https://jausoft.com/blog/2024/01/21/graphui-frustum-culling-clipping-modelview-space/ this update shows clipping and widgets]. [https://jausoft.com/blog/tag/graph_type_rendering/ Further updates will be posted here...].

Notably the ''Graph Curve Rendering'' is almost feature complete, as well as our own user input including gesture detection within NEWT.

;Parent Main Node
: [{{SERVER}}/bugzilla/showdependencytree.cgi?id=803&hide_resolved=0 Dependency Tree]
: [{{SERVER}}/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=IN_PROGRESS&bug_status=RESOLVED&bug_status=VERIFIED&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cversion%2Cshort_desc%2Cchangeddate&component=core&component=Plugin&list_id=2265&product=GraphUI&query_format=advanced&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED All GraphUI]

;Open Items ''graphui''
<bugzilla>
{
"status":["IN_PROGRESS","CONFIRMED", "UNCONFIRMED"],
"product":"graphui",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

;Completed Items ''graphui''
<bugzilla>
{
"status":["RESOLVED","VERIFIED"],
"product":"graphui",
"include_fields":"id,version,product,component,status,resolution,summary"
}
</bugzilla>

== Jogl / Graph ==

[{{SERVER}}/bugzilla/showdependencytree.cgi?id=1064&hide_resolved=0 Dependency Tree Graph Font Issues]

[{{SERVER}}/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=IN_PROGRESS&bug_status=RESOLVED&bug_status=VERIFIED&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cversion%2Cshort_desc%2Cchangeddate&component=graph&list_id=2264&product=Jogl&query_format=advanced&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED All Jogl Graph]

;Open Items ''Jogl / graph''
<bugzilla>
{
"status":["IN_PROGRESS","CONFIRMED", "UNCONFIRMED"],
"product":"jogl",
"component":"graph",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

;Completed Items ''Jogl / graph''
<bugzilla>
{
"status":["RESOLVED","VERIFIED"],
"product":"jogl",
"component":"graph",
"include_fields":"id,version,product,component,status,resolution,summary"
}
</bugzilla>

= WebAssembly (wasm) Target Platform =

== Overview ==
See [https://jogamp.org/bugzilla//show_bug.cgi?id=1506 Bug 1506] describing this feature.

Since Java Applets are not more supported within browser or by OpenJDK for years,
it may seems feasible to evaluate the WebAssembly target running within e.g. web browser nowadays.

An initial evaluation on small C++ projects using the emscripten front-end for LLVM's clang++ to wasm compiler, which supports many ported system libraries like SDL, OpenGL, .. has been undertaken successfully with variable results.
* [https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ gfxbox2 C++/wasm evaluation]
* [https://emscripten.org/ emscripten]
* [https://webassembly.org/ WebAssembly]

The wasm target is comparable to Java bytecode but the wasm virtual machine is not as performant, efficient or flexible as actual native code. The lack of hassle free native threads and native high-performance may remind one of the first JVM steps. The wasm code runs within a virtual machine like the JVM and additionally lacks of native binding capabilities.

Some limitations may be overcome, others are likely by design as it usually runs on the same browser virtual machine as the JavaScript companion. Compromises must be made on shared memory and native threads, cached non-local file I/O and socket communication - while other native features will simply never work, e.g. operating system ioctl-calls, etc.

Opening the door for any language to be compiled to a platform independent intermediate representation (IR) like Java’s bytecode suitable for a versatile runtime environment including its virtual machine is surely still desirable.

== Initial C++/wasm Evaluation ==
[https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ Our little gfxbox2 games] compiled to [https://webassembly.org/ wasm] run about 40-60% slower within a browser than in native code, depending on coding strategy of our graphics (pixelmap vs SDL/OpenGL primitives).

The used [https://emscripten.org/ emscripten] frontend allowed us to use memory-growth, envelop files used in the wasm file, add cheap stack-overflow cockies and nullptr writes and so forth. Utilization of OpenGL ES via SDL2 was a breeze.

The underlying LLVM compiler did an excellent job and overall, the transition was easy and almost involved no code changes but dropping native thread (std::thread) usage.

The overall program structure had to be adapted to align to the single-thread main-loop workflow
and specific emscripten-javascript hooks added to allow seamless interaction.
All in all, nothing to be too afraid of and depending on the class of applications to be ported
to the browser these days, a feasible procedure.

== Java Support ==
Java support for the WebAssembly target are claimed to be supported by
* [https://github.com/i-net-software/JWebAssembly JWebAssembly]
* [https://github.com/konsoletyper/teavm TeaVM]
* [https://mirkosertic.github.io/Bytecoder/ Bytecoder]

Further interesting bits & pieces
** [https://openjdk.org/jeps/457 JEP 457: Class-File API ]
** [https://openjdk.org/projects/babylon/articles/linq Babylon]

GraalVM experimentally hosts wasm only,
but is not producing a wasm target for the wasm (browser) runtime.

* [https://www.graalvm.org/latest/reference-manual/wasm/ GraalVM + wasm]
** with the help of emscripten
** [https://www.graalvm.org/22.0/reference-manual/native-image/JNI/ GraalVM + JNI]

== Java Browser Outlook ==
So far the only question arises why reinventing the wheel once again? Dropping utilization of a well working JVM for the web had no technical reasoning.

However, in case no suitable wasm target for the Java bytecode and the Java Runtime pieces can be established, one might either want to also look into bringing back the JRE into the browser or painfully drop Java for C++, as the latter is already close to have acceptable (slower and limited) wasm target runtime properties.

= NEWT =

* [{{SERVER}}/bugzilla/showdependencytree.cgi?id=807&hide_resolved=0 Dependency Tree NEWT Input Devices]
* [{{SERVER}}/bugzilla/showdependencytree.cgi?id=814&hide_resolved=0 Dependency Tree NEWT Pointer Event]

<bugzilla>
{
"product":["newt","jinput"],
"version":["2.5.0","3.0.0","tbd"],
"cf_type":"FEATURE",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

= NEWT + Wayland =
Currently NEWT supports the X11/Xorg windowing server on Unix alike platforms.

It might be desired to add direct support to Wayland, as we already added support for
[https://jogamp.org/bugzilla/show_bug.cgi?id=1156 bare metal devices w/o a windowing system via the Linux DRM/GBM console mode]
throughout JOGL + NEWT.

= Vulkan =

<bugzilla>
{
"component":"vulkan",
"cf_type":"FEATURE",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

= Video Encoding/Decoding & Player =

Across our releases, we supported video encoding and decoding (with a player)
based on either FFmpeg or Android's library as [https://youtu.be/4gWStKCioi8?t=132 shown in this clip at 2:12 min mark].

Goal would be to
* Update general ffmpeg video decoding support
* Enhance ffmpeg video encoding support
* Potentially add better control about video-frame to framebuffer control for editing software

See [https://jogamp.org/bugzilla//buglist.cgi?bug_status=__open__&component=video&list_id=3053&product=Jogl related buglist]

<bugzilla>
{
"component":"video",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

= iOS Enhancements =

Early iOS support has been demonstrated in 2019
* [https://jausoft.com/blog/2019/06/17/jogamp-ios-arm64-bring-up/ iOS Arm64 bring-up]
* [https://jausoft.com/blog/2019/06/23/jogamp-ios-arm64-port-first-visuals/ iOS Arm64 Port: First Visuals]
* [https://jausoft.com/blog/2019/07/08/jogamp-ios-arm64-port-newt/ iOS Arm64 Port: NEWT]

Enhancing this port would allow to use JogAmp in a similar fashion as on Android,
but using an OpenJDK iOS build.

= [[SCC Overview|Source Certification Contract (SCC)]] =

[{{SERVER}}/bugzilla/showdependencytree.cgi?id=1368&hide_resolved=0 Dependency Tree]

[{{SERVER}}/bugzilla/show_bug.cgi?id=1368 Root Parent Entry]

<bugzilla>
{
"id":["1368", "1369"],
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

= OpenJFX =

[https://jogamp.org/bugzilla//show_bug.cgi?id=607#c20 Bug report 607] describes different ways to either
* enhance external rendering via JOGL into an OpenJFX UI elements, or
* to replace OpenJFX's Glass w/ NEWT and Prism's OpenGL coding with JOGL

= Misc =



<bugzilla>
{
"version":["2.5.0","3.0.0","tbd"],
"cf_type":"FEATURE",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

SW Tracking Report Feature Objectives Overview

2024-04-03T04:06:57Z

Sgothel: /* WebAssembly (wasm) Target Platform */

This list exposes building blocks
for potential use and business case scenarios
using Java & JogAmp on Desktop and Embedded Devices.

Notably [[#Graph|Graph & Graph UI]] as well as [[#NEWT_+_Wayland|Wayland]] & [[#Vulkan|Vulkan]] support could be of interest here?

Also see [[Completed Features Objectives]] ...

= Graph =
[https://jausoft.com/blog/tag/graph_type_rendering/ Graph/GraphUI Progress Blog Entries]

== Desired Work Items ==

This is an ad-hoc list of desired features and fixes,
which shall result in proper bug-reports soon.

After having reached [https://jausoft.com/blog/2024/01/21/graphui-frustum-culling-clipping-modelview-space/ UI usability with widgets and clipping],
the following items are becoming more interesting

* Fix general issues with current implementation and API, if any
* Fix Graph rendering bugs (Tessellation)
** [https://jausoft.com/blog/2024/02/13/fixing-jogamps-graph-delaunay-tessellation-of-complex-non-convex-shapes/ First round done]
* Use of super-sized triangles to render Graph lines & curves to allow
** Using a one-pass smooth AA Graph renderer to save resources otherwise used in our pass-2 FBO supersampling renderer
** Generate outlines, i.e. outlined fonts
** Generate special effects like glowing/pumping outlines indicating selection etc
* Allow passing or better attaching per-vertex color to Graph Outline (API)
* <s>Add subtitles in MediaPlayer GraphUI widget</s> ''([https://jausoft.com/blog/2024/02/07/graphui-mediaplayer-feature-complete/ done])''
* Add video encoding in our FFmpeg binding, i.e. an FFMPEGMediaRecorder (Encoding + Multiplexing)

Further more, if so desired, a C++ implementation of our Graph + GraphUI framework
may also be of interest.

In case any company or organization is interested and likes to support
this work and may also like to receive support in adopting this framework,
please contact [[Maintainer_and_Contacts#Commercial_Support|Göthel Software e.K.]]

== OpenJDK Compatibility / Integration ==

Objectives should be to allow seamless integration into
OpenJDK's deployment and JVM launch methods.

A dual JAR file to be used with and without modules is desired,
however it seems that certain JAR options are not available with this
configuration if our classes are not build as modules itself.

An optional [https://jogamp.org/bugzilla/show_bug.cgi?id=1505#c0 JVM Launch Pad (JLP)] might be helpful,
even though it instructs further complexity and is not helping
with a vanilla OpenJDK deployment.

=== OpenJDK >= 11 ===

See [https://jogamp.org/bugzilla/show_bug.cgi?id=1404 Bug 1404]

'''JVM Commandline Parameter'''

Current used 'add-opens' in my JogAmp test scripts for Java >= 11,
covering all AWT utilization including background erase is:

<pre>
--add-opens java.desktop/sun.awt=ALL-UNNAMED
--add-opens java.desktop/sun.awt.windows=ALL-UNNAMED
--add-opens java.desktop/sun.java2d=ALL-UNNAMED
</pre>

=== OpenJDK >= 2x ===

See [https://jogamp.org/bugzilla/show_bug.cgi?id=1505 Bug 1505]

'''JVM Commandline Parameter'''

Current used 'add-opens' in my JogAmp test scripts for Java >= 23,
covering all AWT utilization including background erase is:

<pre>
--add-opens java.desktop/sun.awt=ALL-UNNAMED
--add-opens java.desktop/sun.awt.windows=ALL-UNNAMED
--add-opens java.desktop/sun.java2d=ALL-UNNAMED
--TO_BE_DETERMINED
</pre>

== Graph UI ==

[https://jausoft.com/blog/2023/02/22/reimagine-java-on-desktop-bare-metal-devices/ ''Graph UI'' will enable an immersive UI within the 3D scene] on the desktop, mobile and on bare-metal embedded systems without a windowing system.

Graph UI utilizes [https://jausoft.com/blog/2011/10/05/jogljogamp-red-square-moscow-nurbs-graphicon2011/ Resolution Independent NURBS Curves Rendering using Programmable Graphics Pipeline], i.e. rendering curves directly on the GPU, resolution independent [ [https://jogamp.org/doc/gpunurbs2011/p70-santina.pdf paper], [https://jogamp.org/doc/gpunurbs2011/graphicon2011-slides.pdf slides] ].

This method allows us to have an ultimate fast font and UI rendering engine, suitable for all devices and applications. No CPU based curve nor font pre-rendering (matching a target resolution) is required.

Think of an integrated QT or OpenJFX in your 2D/3D application
working on desktop and embedded devices even w/o any windowing system on top
of a plain console [{{SERVER}}/bugzilla/show_bug.cgi?id=1156 DRM/GBM as support by JOGL(EGL) and NEWT]
as demonstrated [https://ict.zafena.se/improved-graphical-information-technology/ by Xerxes on a Raspberry Pi4].

[https://jausoft.com/blog/2023/02/22/reimagine-java-on-desktop-bare-metal-devices/ Reimagine Java on Desktop & Bare-Metal Devices]
demonstrates the updated Graph Curve Rendering and UI, while [https://jausoft.com/blog/2024/01/21/graphui-frustum-culling-clipping-modelview-space/ this update shows clipping and widgets]. [https://jausoft.com/blog/tag/graph_type_rendering/ Further updates will be posted here...].

Notably the ''Graph Curve Rendering'' is almost feature complete, as well as our own user input including gesture detection within NEWT.

;Parent Main Node
: [{{SERVER}}/bugzilla/showdependencytree.cgi?id=803&hide_resolved=0 Dependency Tree]
: [{{SERVER}}/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=IN_PROGRESS&bug_status=RESOLVED&bug_status=VERIFIED&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cversion%2Cshort_desc%2Cchangeddate&component=core&component=Plugin&list_id=2265&product=GraphUI&query_format=advanced&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED All GraphUI]

;Open Items ''graphui''
<bugzilla>
{
"status":["IN_PROGRESS","CONFIRMED", "UNCONFIRMED"],
"product":"graphui",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

;Completed Items ''graphui''
<bugzilla>
{
"status":["RESOLVED","VERIFIED"],
"product":"graphui",
"include_fields":"id,version,product,component,status,resolution,summary"
}
</bugzilla>

== Jogl / Graph ==

[{{SERVER}}/bugzilla/showdependencytree.cgi?id=1064&hide_resolved=0 Dependency Tree Graph Font Issues]

[{{SERVER}}/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=IN_PROGRESS&bug_status=RESOLVED&bug_status=VERIFIED&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cversion%2Cshort_desc%2Cchangeddate&component=graph&list_id=2264&product=Jogl&query_format=advanced&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED All Jogl Graph]

;Open Items ''Jogl / graph''
<bugzilla>
{
"status":["IN_PROGRESS","CONFIRMED", "UNCONFIRMED"],
"product":"jogl",
"component":"graph",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

;Completed Items ''Jogl / graph''
<bugzilla>
{
"status":["RESOLVED","VERIFIED"],
"product":"jogl",
"component":"graph",
"include_fields":"id,version,product,component,status,resolution,summary"
}
</bugzilla>

= WebAssembly (wasm) Target Platform =

== Overview ==
See [https://jogamp.org/bugzilla//show_bug.cgi?id=1506 Bug 1506] describing this feature.

Since Java Applets are not more supported within browser or by OpenJDK for years,
it may seems feasible to evaluate the WebAssembly target running within e.g. web browser nowadays.

An initial evaluation on small C++ projects using the emscripten front-end for LLVM's clang++ to wasm compiler, which supports many ported system libraries like SDL, OpenGL, .. has been undertaken successfully with variable results.
* [https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ gfxbox2 C++/wasm evaluation]
* [https://emscripten.org/ emscripten]
* [https://webassembly.org/ WebAssembly]

The wasm target is comparable to Java bytecode but the wasm virtual machine is not as performant, efficient or flexible as actual native code. The lack of hassle free native threads and native high-performance may remind one of the first JVM steps. The wasm code runs within a virtual machine like the JVM and additionally lacks of native binding capabilities.

Some limitations may be overcome, others are likely by design as it usually runs on the same browser virtual machine as the JavaScript companion. Compromises must be made on shared memory and native threads, cached non-local file I/O and socket communication - while other native features will simply never work, e.g. operating system ioctl-calls, etc.

Opening the door for any language to be compiled to a platform independent intermediate representation (IR) like Java’s bytecode suitable for a versatile runtime environment including its virtual machine is surely still desirable.

== Initial C++/wasm Evaluation ==
[https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ Our little gfxbox2 games] compiled to [https://webassembly.org/ wasm] run about 40-60% slower within a browser than in native code, depending on coding strategy of our graphics (pixelmap vs SDL/OpenGL primitives).

The used [https://emscripten.org/ emscripten] frontend allowed us to use memory-growth, envelop files used in the wasm file, add cheap stack-overflow cockies and nullptr writes and so forth. Utilization of OpenGL ES via SDL2 was a breeze.

The underlying LLVM compiler did an excellent job and overall, the transition was easy and almost involved no code changes but dropping native thread (std::thread) usage.

The overall program structure had to be adapted to align to the single-thread main-loop workflow
and specific emscripten-javascript hooks added to allow seamless interaction.
All in all, nothing to be too afraid of and depending on the class of applications to be ported
to the browser these days, a feasible procedure.

== Java Support ==
Java support for the WebAssembly target are claimed to be supported by
* [https://github.com/i-net-software/JWebAssembly JWebAssembly]
* [https://github.com/konsoletyper/teavm TeaVM]
* [https://mirkosertic.github.io/Bytecoder/ Bytecoder]

Further interesting bits & pieces
** [https://openjdk.org/jeps/457 JEP 457: Class-File API ]
** [https://openjdk.org/projects/babylon/articles/linq Babylon]

GraalVM is (only) hosting wasm
GraalVM experimentally hosts wasm only,
but is not producing a wasm target for the wasm (browser) runtime.

* [https://www.graalvm.org/latest/reference-manual/wasm/ GraalVM + wasm]
** with the help of emscripten
** [https://www.graalvm.org/22.0/reference-manual/native-image/JNI/ GraalVM + JNI]

== Java Browser Outlook ==
So far the only question arises why reinventing the wheel once again? Dropping utilization of a well working JVM for the web had no technical reasoning.

However, in case no suitable wasm target for the Java bytecode and the Java Runtime pieces can be established, one might either want to also look into bringing back the JRE into the browser or painfully drop Java for C++, as the latter is already close to have acceptable (slower and limited) wasm target runtime properties.

= NEWT =

* [{{SERVER}}/bugzilla/showdependencytree.cgi?id=807&hide_resolved=0 Dependency Tree NEWT Input Devices]
* [{{SERVER}}/bugzilla/showdependencytree.cgi?id=814&hide_resolved=0 Dependency Tree NEWT Pointer Event]

<bugzilla>
{
"product":["newt","jinput"],
"version":["2.5.0","3.0.0","tbd"],
"cf_type":"FEATURE",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

= NEWT + Wayland =
Currently NEWT supports the X11/Xorg windowing server on Unix alike platforms.

It might be desired to add direct support to Wayland, as we already added support for
[https://jogamp.org/bugzilla/show_bug.cgi?id=1156 bare metal devices w/o a windowing system via the Linux DRM/GBM console mode]
throughout JOGL + NEWT.

= Vulkan =

<bugzilla>
{
"component":"vulkan",
"cf_type":"FEATURE",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

= Video Encoding/Decoding & Player =

Across our releases, we supported video encoding and decoding (with a player)
based on either FFmpeg or Android's library as [https://youtu.be/4gWStKCioi8?t=132 shown in this clip at 2:12 min mark].

Goal would be to
* Update general ffmpeg video decoding support
* Enhance ffmpeg video encoding support
* Potentially add better control about video-frame to framebuffer control for editing software

See [https://jogamp.org/bugzilla//buglist.cgi?bug_status=__open__&component=video&list_id=3053&product=Jogl related buglist]

<bugzilla>
{
"component":"video",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

= iOS Enhancements =

Early iOS support has been demonstrated in 2019
* [https://jausoft.com/blog/2019/06/17/jogamp-ios-arm64-bring-up/ iOS Arm64 bring-up]
* [https://jausoft.com/blog/2019/06/23/jogamp-ios-arm64-port-first-visuals/ iOS Arm64 Port: First Visuals]
* [https://jausoft.com/blog/2019/07/08/jogamp-ios-arm64-port-newt/ iOS Arm64 Port: NEWT]

Enhancing this port would allow to use JogAmp in a similar fashion as on Android,
but using an OpenJDK iOS build.

= [[SCC Overview|Source Certification Contract (SCC)]] =

[{{SERVER}}/bugzilla/showdependencytree.cgi?id=1368&hide_resolved=0 Dependency Tree]

[{{SERVER}}/bugzilla/show_bug.cgi?id=1368 Root Parent Entry]

<bugzilla>
{
"id":["1368", "1369"],
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

= OpenJFX =

[https://jogamp.org/bugzilla//show_bug.cgi?id=607#c20 Bug report 607] describes different ways to either
* enhance external rendering via JOGL into an OpenJFX UI elements, or
* to replace OpenJFX's Glass w/ NEWT and Prism's OpenGL coding with JOGL

= Misc =



<bugzilla>
{
"version":["2.5.0","3.0.0","tbd"],
"cf_type":"FEATURE",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

SW Tracking Report Feature Objectives Overview

2024-04-03T03:49:34Z

Sgothel: /* Initial C++/wasm Evaluation */

This list exposes building blocks
for potential use and business case scenarios
using Java & JogAmp on Desktop and Embedded Devices.

Notably [[#Graph|Graph & Graph UI]] as well as [[#NEWT_+_Wayland|Wayland]] & [[#Vulkan|Vulkan]] support could be of interest here?

Also see [[Completed Features Objectives]] ...

= Graph =
[https://jausoft.com/blog/tag/graph_type_rendering/ Graph/GraphUI Progress Blog Entries]

== Desired Work Items ==

This is an ad-hoc list of desired features and fixes,
which shall result in proper bug-reports soon.

After having reached [https://jausoft.com/blog/2024/01/21/graphui-frustum-culling-clipping-modelview-space/ UI usability with widgets and clipping],
the following items are becoming more interesting

* Fix general issues with current implementation and API, if any
* Fix Graph rendering bugs (Tessellation)
** [https://jausoft.com/blog/2024/02/13/fixing-jogamps-graph-delaunay-tessellation-of-complex-non-convex-shapes/ First round done]
* Use of super-sized triangles to render Graph lines & curves to allow
** Using a one-pass smooth AA Graph renderer to save resources otherwise used in our pass-2 FBO supersampling renderer
** Generate outlines, i.e. outlined fonts
** Generate special effects like glowing/pumping outlines indicating selection etc
* Allow passing or better attaching per-vertex color to Graph Outline (API)
* <s>Add subtitles in MediaPlayer GraphUI widget</s> ''([https://jausoft.com/blog/2024/02/07/graphui-mediaplayer-feature-complete/ done])''
* Add video encoding in our FFmpeg binding, i.e. an FFMPEGMediaRecorder (Encoding + Multiplexing)

Further more, if so desired, a C++ implementation of our Graph + GraphUI framework
may also be of interest.

In case any company or organization is interested and likes to support
this work and may also like to receive support in adopting this framework,
please contact [[Maintainer_and_Contacts#Commercial_Support|Göthel Software e.K.]]

== OpenJDK Compatibility / Integration ==

Objectives should be to allow seamless integration into
OpenJDK's deployment and JVM launch methods.

A dual JAR file to be used with and without modules is desired,
however it seems that certain JAR options are not available with this
configuration if our classes are not build as modules itself.

An optional [https://jogamp.org/bugzilla/show_bug.cgi?id=1505#c0 JVM Launch Pad (JLP)] might be helpful,
even though it instructs further complexity and is not helping
with a vanilla OpenJDK deployment.

=== OpenJDK >= 11 ===

See [https://jogamp.org/bugzilla/show_bug.cgi?id=1404 Bug 1404]

'''JVM Commandline Parameter'''

Current used 'add-opens' in my JogAmp test scripts for Java >= 11,
covering all AWT utilization including background erase is:

<pre>
--add-opens java.desktop/sun.awt=ALL-UNNAMED
--add-opens java.desktop/sun.awt.windows=ALL-UNNAMED
--add-opens java.desktop/sun.java2d=ALL-UNNAMED
</pre>

=== OpenJDK >= 2x ===

See [https://jogamp.org/bugzilla/show_bug.cgi?id=1505 Bug 1505]

'''JVM Commandline Parameter'''

Current used 'add-opens' in my JogAmp test scripts for Java >= 23,
covering all AWT utilization including background erase is:

<pre>
--add-opens java.desktop/sun.awt=ALL-UNNAMED
--add-opens java.desktop/sun.awt.windows=ALL-UNNAMED
--add-opens java.desktop/sun.java2d=ALL-UNNAMED
--TO_BE_DETERMINED
</pre>

== Graph UI ==

[https://jausoft.com/blog/2023/02/22/reimagine-java-on-desktop-bare-metal-devices/ ''Graph UI'' will enable an immersive UI within the 3D scene] on the desktop, mobile and on bare-metal embedded systems without a windowing system.

Graph UI utilizes [https://jausoft.com/blog/2011/10/05/jogljogamp-red-square-moscow-nurbs-graphicon2011/ Resolution Independent NURBS Curves Rendering using Programmable Graphics Pipeline], i.e. rendering curves directly on the GPU, resolution independent [ [https://jogamp.org/doc/gpunurbs2011/p70-santina.pdf paper], [https://jogamp.org/doc/gpunurbs2011/graphicon2011-slides.pdf slides] ].

This method allows us to have an ultimate fast font and UI rendering engine, suitable for all devices and applications. No CPU based curve nor font pre-rendering (matching a target resolution) is required.

Think of an integrated QT or OpenJFX in your 2D/3D application
working on desktop and embedded devices even w/o any windowing system on top
of a plain console [{{SERVER}}/bugzilla/show_bug.cgi?id=1156 DRM/GBM as support by JOGL(EGL) and NEWT]
as demonstrated [https://ict.zafena.se/improved-graphical-information-technology/ by Xerxes on a Raspberry Pi4].

[https://jausoft.com/blog/2023/02/22/reimagine-java-on-desktop-bare-metal-devices/ Reimagine Java on Desktop & Bare-Metal Devices]
demonstrates the updated Graph Curve Rendering and UI, while [https://jausoft.com/blog/2024/01/21/graphui-frustum-culling-clipping-modelview-space/ this update shows clipping and widgets]. [https://jausoft.com/blog/tag/graph_type_rendering/ Further updates will be posted here...].

Notably the ''Graph Curve Rendering'' is almost feature complete, as well as our own user input including gesture detection within NEWT.

;Parent Main Node
: [{{SERVER}}/bugzilla/showdependencytree.cgi?id=803&hide_resolved=0 Dependency Tree]
: [{{SERVER}}/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=IN_PROGRESS&bug_status=RESOLVED&bug_status=VERIFIED&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cversion%2Cshort_desc%2Cchangeddate&component=core&component=Plugin&list_id=2265&product=GraphUI&query_format=advanced&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED All GraphUI]

;Open Items ''graphui''
<bugzilla>
{
"status":["IN_PROGRESS","CONFIRMED", "UNCONFIRMED"],
"product":"graphui",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

;Completed Items ''graphui''
<bugzilla>
{
"status":["RESOLVED","VERIFIED"],
"product":"graphui",
"include_fields":"id,version,product,component,status,resolution,summary"
}
</bugzilla>

== Jogl / Graph ==

[{{SERVER}}/bugzilla/showdependencytree.cgi?id=1064&hide_resolved=0 Dependency Tree Graph Font Issues]

[{{SERVER}}/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=IN_PROGRESS&bug_status=RESOLVED&bug_status=VERIFIED&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cversion%2Cshort_desc%2Cchangeddate&component=graph&list_id=2264&product=Jogl&query_format=advanced&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED All Jogl Graph]

;Open Items ''Jogl / graph''
<bugzilla>
{
"status":["IN_PROGRESS","CONFIRMED", "UNCONFIRMED"],
"product":"jogl",
"component":"graph",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

;Completed Items ''Jogl / graph''
<bugzilla>
{
"status":["RESOLVED","VERIFIED"],
"product":"jogl",
"component":"graph",
"include_fields":"id,version,product,component,status,resolution,summary"
}
</bugzilla>

= WebAssembly (wasm) Target Platform =

== Overview ==
See [https://jogamp.org/bugzilla//show_bug.cgi?id=1506 Bug 1506] describing this feature.

Since Java Applets are not more supported within browser or by OpenJDK for years,
it may seems feasible to evaluate the WebAssembly target running within e.g. web browser nowadays.

An initial evaluation on small C++ projects using the emscripten front-end for LLVM's clang++ to wasm compiler, which supports many ported system libraries like SDL, OpenGL, .. has been undertaken successfully with variable results.
* [https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ gfxbox2 C++/wasm evaluation]
* [https://emscripten.org/ emscripten]
* [https://webassembly.org/ WebAssembly]

== Java Support ==
Java support for the WebAssembly target are claimed to be supported by
* [https://github.com/i-net-software/JWebAssembly JWebAssembly]
* [https://github.com/konsoletyper/teavm TeaVM]
* [https://mirkosertic.github.io/Bytecoder/ Bytecoder]

Further interesting bits & pieces
** [https://openjdk.org/jeps/457 JEP 457: Class-File API ]
** [https://openjdk.org/projects/babylon/articles/linq Babylon]

GraalVM is (only) hosting wasm
GraalVM experimentally hosts wasm only,
but is not producing a wasm target for the wasm (browser) runtime.

* [https://www.graalvm.org/latest/reference-manual/wasm/ GraalVM + wasm]
** with the help of emscripten
** [https://www.graalvm.org/22.0/reference-manual/native-image/JNI/ GraalVM + JNI]

== Initial C++/wasm Evaluation ==
For once, the wasm target is comparable to Java bytecode but the wasm virtual machine is not as performant, efficient or flexible as actual native code. The lack of hassle free native threads and performance may remind one of the first JVM steps. The wasm code runs within a virtual machine like the JVM and additionally lacks of native binding capabilities, besides aforementioned limitations.

Some limitations may be overcome, others are likely by design as it usually runs on the same browser virtual machine as the JavaScript companion. Compromises must be made on shared memory and native threads, cached non-local file I/O and socket communication - while other native features will simply never work, e.g. operating system ioctl-calls, etc.

So far the only question arises why reinventing the wheel once again? Dropping utilization of a well working JVM for the web had no technical reasoning.

One might want to evaluate this Java target platform as well before recoding the whole application.

Opening the door for any language to be compiled to a platform independent intermediate representation (IR) like Java’s bytecode suitable for a versatile runtime environment including its virtual machine is surely still desirable.

However, in case no suitable wasm target for the Java bytecode and the Java Runtime pieces can be established, one might either want to also look into bringing back the JRE into the browser or painfully drop Java for C++, as the latter is already close to have acceptable (slower and limited) wasm target runtime properties.

= NEWT =

* [{{SERVER}}/bugzilla/showdependencytree.cgi?id=807&hide_resolved=0 Dependency Tree NEWT Input Devices]
* [{{SERVER}}/bugzilla/showdependencytree.cgi?id=814&hide_resolved=0 Dependency Tree NEWT Pointer Event]

<bugzilla>
{
"product":["newt","jinput"],
"version":["2.5.0","3.0.0","tbd"],
"cf_type":"FEATURE",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

= NEWT + Wayland =
Currently NEWT supports the X11/Xorg windowing server on Unix alike platforms.

It might be desired to add direct support to Wayland, as we already added support for
[https://jogamp.org/bugzilla/show_bug.cgi?id=1156 bare metal devices w/o a windowing system via the Linux DRM/GBM console mode]
throughout JOGL + NEWT.

= Vulkan =

<bugzilla>
{
"component":"vulkan",
"cf_type":"FEATURE",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

= Video Encoding/Decoding & Player =

Across our releases, we supported video encoding and decoding (with a player)
based on either FFmpeg or Android's library as [https://youtu.be/4gWStKCioi8?t=132 shown in this clip at 2:12 min mark].

Goal would be to
* Update general ffmpeg video decoding support
* Enhance ffmpeg video encoding support
* Potentially add better control about video-frame to framebuffer control for editing software

See [https://jogamp.org/bugzilla//buglist.cgi?bug_status=__open__&component=video&list_id=3053&product=Jogl related buglist]

<bugzilla>
{
"component":"video",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

= iOS Enhancements =

Early iOS support has been demonstrated in 2019
* [https://jausoft.com/blog/2019/06/17/jogamp-ios-arm64-bring-up/ iOS Arm64 bring-up]
* [https://jausoft.com/blog/2019/06/23/jogamp-ios-arm64-port-first-visuals/ iOS Arm64 Port: First Visuals]
* [https://jausoft.com/blog/2019/07/08/jogamp-ios-arm64-port-newt/ iOS Arm64 Port: NEWT]

Enhancing this port would allow to use JogAmp in a similar fashion as on Android,
but using an OpenJDK iOS build.

= [[SCC Overview|Source Certification Contract (SCC)]] =

[{{SERVER}}/bugzilla/showdependencytree.cgi?id=1368&hide_resolved=0 Dependency Tree]

[{{SERVER}}/bugzilla/show_bug.cgi?id=1368 Root Parent Entry]

<bugzilla>
{
"id":["1368", "1369"],
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

= OpenJFX =

[https://jogamp.org/bugzilla//show_bug.cgi?id=607#c20 Bug report 607] describes different ways to either
* enhance external rendering via JOGL into an OpenJFX UI elements, or
* to replace OpenJFX's Glass w/ NEWT and Prism's OpenGL coding with JOGL

= Misc =



<bugzilla>
{
"version":["2.5.0","3.0.0","tbd"],
"cf_type":"FEATURE",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

SW Tracking Report Feature Objectives Overview

2024-04-03T03:38:21Z

Sgothel: /* Java Support */

This list exposes building blocks
for potential use and business case scenarios
using Java & JogAmp on Desktop and Embedded Devices.

Notably [[#Graph|Graph & Graph UI]] as well as [[#NEWT_+_Wayland|Wayland]] & [[#Vulkan|Vulkan]] support could be of interest here?

Also see [[Completed Features Objectives]] ...

= Graph =
[https://jausoft.com/blog/tag/graph_type_rendering/ Graph/GraphUI Progress Blog Entries]

== Desired Work Items ==

This is an ad-hoc list of desired features and fixes,
which shall result in proper bug-reports soon.

After having reached [https://jausoft.com/blog/2024/01/21/graphui-frustum-culling-clipping-modelview-space/ UI usability with widgets and clipping],
the following items are becoming more interesting

* Fix general issues with current implementation and API, if any
* Fix Graph rendering bugs (Tessellation)
** [https://jausoft.com/blog/2024/02/13/fixing-jogamps-graph-delaunay-tessellation-of-complex-non-convex-shapes/ First round done]
* Use of super-sized triangles to render Graph lines & curves to allow
** Using a one-pass smooth AA Graph renderer to save resources otherwise used in our pass-2 FBO supersampling renderer
** Generate outlines, i.e. outlined fonts
** Generate special effects like glowing/pumping outlines indicating selection etc
* Allow passing or better attaching per-vertex color to Graph Outline (API)
* <s>Add subtitles in MediaPlayer GraphUI widget</s> ''([https://jausoft.com/blog/2024/02/07/graphui-mediaplayer-feature-complete/ done])''
* Add video encoding in our FFmpeg binding, i.e. an FFMPEGMediaRecorder (Encoding + Multiplexing)

Further more, if so desired, a C++ implementation of our Graph + GraphUI framework
may also be of interest.

In case any company or organization is interested and likes to support
this work and may also like to receive support in adopting this framework,
please contact [[Maintainer_and_Contacts#Commercial_Support|Göthel Software e.K.]]

== OpenJDK Compatibility / Integration ==

Objectives should be to allow seamless integration into
OpenJDK's deployment and JVM launch methods.

A dual JAR file to be used with and without modules is desired,
however it seems that certain JAR options are not available with this
configuration if our classes are not build as modules itself.

An optional [https://jogamp.org/bugzilla/show_bug.cgi?id=1505#c0 JVM Launch Pad (JLP)] might be helpful,
even though it instructs further complexity and is not helping
with a vanilla OpenJDK deployment.

=== OpenJDK >= 11 ===

See [https://jogamp.org/bugzilla/show_bug.cgi?id=1404 Bug 1404]

'''JVM Commandline Parameter'''

Current used 'add-opens' in my JogAmp test scripts for Java >= 11,
covering all AWT utilization including background erase is:

<pre>
--add-opens java.desktop/sun.awt=ALL-UNNAMED
--add-opens java.desktop/sun.awt.windows=ALL-UNNAMED
--add-opens java.desktop/sun.java2d=ALL-UNNAMED
</pre>

=== OpenJDK >= 2x ===

See [https://jogamp.org/bugzilla/show_bug.cgi?id=1505 Bug 1505]

'''JVM Commandline Parameter'''

Current used 'add-opens' in my JogAmp test scripts for Java >= 23,
covering all AWT utilization including background erase is:

<pre>
--add-opens java.desktop/sun.awt=ALL-UNNAMED
--add-opens java.desktop/sun.awt.windows=ALL-UNNAMED
--add-opens java.desktop/sun.java2d=ALL-UNNAMED
--TO_BE_DETERMINED
</pre>

== Graph UI ==

[https://jausoft.com/blog/2023/02/22/reimagine-java-on-desktop-bare-metal-devices/ ''Graph UI'' will enable an immersive UI within the 3D scene] on the desktop, mobile and on bare-metal embedded systems without a windowing system.

Graph UI utilizes [https://jausoft.com/blog/2011/10/05/jogljogamp-red-square-moscow-nurbs-graphicon2011/ Resolution Independent NURBS Curves Rendering using Programmable Graphics Pipeline], i.e. rendering curves directly on the GPU, resolution independent [ [https://jogamp.org/doc/gpunurbs2011/p70-santina.pdf paper], [https://jogamp.org/doc/gpunurbs2011/graphicon2011-slides.pdf slides] ].

This method allows us to have an ultimate fast font and UI rendering engine, suitable for all devices and applications. No CPU based curve nor font pre-rendering (matching a target resolution) is required.

Think of an integrated QT or OpenJFX in your 2D/3D application
working on desktop and embedded devices even w/o any windowing system on top
of a plain console [{{SERVER}}/bugzilla/show_bug.cgi?id=1156 DRM/GBM as support by JOGL(EGL) and NEWT]
as demonstrated [https://ict.zafena.se/improved-graphical-information-technology/ by Xerxes on a Raspberry Pi4].

[https://jausoft.com/blog/2023/02/22/reimagine-java-on-desktop-bare-metal-devices/ Reimagine Java on Desktop & Bare-Metal Devices]
demonstrates the updated Graph Curve Rendering and UI, while [https://jausoft.com/blog/2024/01/21/graphui-frustum-culling-clipping-modelview-space/ this update shows clipping and widgets]. [https://jausoft.com/blog/tag/graph_type_rendering/ Further updates will be posted here...].

Notably the ''Graph Curve Rendering'' is almost feature complete, as well as our own user input including gesture detection within NEWT.

;Parent Main Node
: [{{SERVER}}/bugzilla/showdependencytree.cgi?id=803&hide_resolved=0 Dependency Tree]
: [{{SERVER}}/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=IN_PROGRESS&bug_status=RESOLVED&bug_status=VERIFIED&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cversion%2Cshort_desc%2Cchangeddate&component=core&component=Plugin&list_id=2265&product=GraphUI&query_format=advanced&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED All GraphUI]

;Open Items ''graphui''
<bugzilla>
{
"status":["IN_PROGRESS","CONFIRMED", "UNCONFIRMED"],
"product":"graphui",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

;Completed Items ''graphui''
<bugzilla>
{
"status":["RESOLVED","VERIFIED"],
"product":"graphui",
"include_fields":"id,version,product,component,status,resolution,summary"
}
</bugzilla>

== Jogl / Graph ==

[{{SERVER}}/bugzilla/showdependencytree.cgi?id=1064&hide_resolved=0 Dependency Tree Graph Font Issues]

[{{SERVER}}/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=IN_PROGRESS&bug_status=RESOLVED&bug_status=VERIFIED&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cversion%2Cshort_desc%2Cchangeddate&component=graph&list_id=2264&product=Jogl&query_format=advanced&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED All Jogl Graph]

;Open Items ''Jogl / graph''
<bugzilla>
{
"status":["IN_PROGRESS","CONFIRMED", "UNCONFIRMED"],
"product":"jogl",
"component":"graph",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

;Completed Items ''Jogl / graph''
<bugzilla>
{
"status":["RESOLVED","VERIFIED"],
"product":"jogl",
"component":"graph",
"include_fields":"id,version,product,component,status,resolution,summary"
}
</bugzilla>

= WebAssembly (wasm) Target Platform =

== Overview ==
See [https://jogamp.org/bugzilla//show_bug.cgi?id=1506 Bug 1506] describing this feature.

Since Java Applets are not more supported within browser or by OpenJDK for years,
it may seems feasible to evaluate the WebAssembly target running within e.g. web browser nowadays.

An initial evaluation on small C++ projects using the emscripten front-end for LLVM's clang++ to wasm compiler, which supports many ported system libraries like SDL, OpenGL, .. has been undertaken successfully with variable results.
* [https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ gfxbox2 C++/wasm evaluation]
* [https://emscripten.org/ emscripten]
* [https://webassembly.org/ WebAssembly]

== Java Support ==
Java support for the WebAssembly target are claimed to be supported by
* [https://github.com/i-net-software/JWebAssembly JWebAssembly]
* [https://github.com/konsoletyper/teavm TeaVM]
* [https://mirkosertic.github.io/Bytecoder/ Bytecoder]

Further interesting bits & pieces
** [https://openjdk.org/jeps/457 JEP 457: Class-File API ]
** [https://openjdk.org/projects/babylon/articles/linq Babylon]

GraalVM is (only) hosting wasm
GraalVM experimentally hosts wasm only,
but is not producing a wasm target for the wasm (browser) runtime.

* [https://www.graalvm.org/latest/reference-manual/wasm/ GraalVM + wasm]
** with the help of emscripten
** [https://www.graalvm.org/22.0/reference-manual/native-image/JNI/ GraalVM + JNI]

== Initial C++/wasm Evaluation ==
For once, the wasm target is comparable to Java bytecode but the virtual machine might not be as performant, efficient or flexible. The lack of hassle free native threads and performance may remind one of the first JVM steps. The wasm code runs within a virtual machine like the JVM and additionally lacks of native binding capabilities, besides aforementioned limitations.

Some limitations may be overcome, others are likely by design as it usually runs on the same browser virtual machine as the JavaScript companion.

So far the only question arises why reinventing the wheel once again? Dropping utilization of a well working JVM for the web had not technical reasoning.

GraalVM seems to support the wasm target, hence one might want to evaluate this Java target platform as well before recoding the whole application.
Opening the door for any language to be compiled to a platform independent intermediate representation (IR) like Java’s bytecode suitable for a versatile runtime environment including its virtual machine is surely still desirable.
Hopefully this technology will mature and be maintained for the years to come.

= NEWT =

* [{{SERVER}}/bugzilla/showdependencytree.cgi?id=807&hide_resolved=0 Dependency Tree NEWT Input Devices]
* [{{SERVER}}/bugzilla/showdependencytree.cgi?id=814&hide_resolved=0 Dependency Tree NEWT Pointer Event]

<bugzilla>
{
"product":["newt","jinput"],
"version":["2.5.0","3.0.0","tbd"],
"cf_type":"FEATURE",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

= NEWT + Wayland =
Currently NEWT supports the X11/Xorg windowing server on Unix alike platforms.

It might be desired to add direct support to Wayland, as we already added support for
[https://jogamp.org/bugzilla/show_bug.cgi?id=1156 bare metal devices w/o a windowing system via the Linux DRM/GBM console mode]
throughout JOGL + NEWT.

= Vulkan =

<bugzilla>
{
"component":"vulkan",
"cf_type":"FEATURE",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

= Video Encoding/Decoding & Player =

Across our releases, we supported video encoding and decoding (with a player)
based on either FFmpeg or Android's library as [https://youtu.be/4gWStKCioi8?t=132 shown in this clip at 2:12 min mark].

Goal would be to
* Update general ffmpeg video decoding support
* Enhance ffmpeg video encoding support
* Potentially add better control about video-frame to framebuffer control for editing software

See [https://jogamp.org/bugzilla//buglist.cgi?bug_status=__open__&component=video&list_id=3053&product=Jogl related buglist]

<bugzilla>
{
"component":"video",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

= iOS Enhancements =

Early iOS support has been demonstrated in 2019
* [https://jausoft.com/blog/2019/06/17/jogamp-ios-arm64-bring-up/ iOS Arm64 bring-up]
* [https://jausoft.com/blog/2019/06/23/jogamp-ios-arm64-port-first-visuals/ iOS Arm64 Port: First Visuals]
* [https://jausoft.com/blog/2019/07/08/jogamp-ios-arm64-port-newt/ iOS Arm64 Port: NEWT]

Enhancing this port would allow to use JogAmp in a similar fashion as on Android,
but using an OpenJDK iOS build.

= [[SCC Overview|Source Certification Contract (SCC)]] =

[{{SERVER}}/bugzilla/showdependencytree.cgi?id=1368&hide_resolved=0 Dependency Tree]

[{{SERVER}}/bugzilla/show_bug.cgi?id=1368 Root Parent Entry]

<bugzilla>
{
"id":["1368", "1369"],
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>

= OpenJFX =

[https://jogamp.org/bugzilla//show_bug.cgi?id=607#c20 Bug report 607] describes different ways to either
* enhance external rendering via JOGL into an OpenJFX UI elements, or
* to replace OpenJFX's Glass w/ NEWT and Prism's OpenGL coding with JOGL

= Misc =



<bugzilla>
{
"version":["2.5.0","3.0.0","tbd"],
"cf_type":"FEATURE",
"include_fields":"id,version,product,component,priority,severity,status,summary"
}
</bugzilla>