Changes

doc/misc/robovm.txt: Writedown howto use JogAmp in combination with RoboVM AOT

doc/misc/robovm.txt: Mention -rvm: runtime flags

doc/misc/robovm.txt: Explore low footprint deployment 6.3Mb

doc/misc/robovm.txt: Update to JogAmp JOGL 2.3.2 and last libre RoboVM 1.6.1

Update CSS; Add responsive viewport design tag

Update CSS; Add responsive viewport design tag

Bug 1381: Keep host PixelFormat functional using requested immutable alphaRequested + add appropriate API doc

iOS: Initial working commit supporting iOS (ipad pro 11)

using our OpenJFK 9 x86_64 and arm64 build.

Test demo class is 'com.jogamp.opengl.demos.ios.Hello',
residing in the new demo folder 'src/demos/com/jogamp/opengl/demos/ios/Hello.java'.

This commit does not yet include a working NEWT
specialization for iOS, but it shall followup soon.

Instead this commit demonstrates JOGL operating on
native UIWindow, UIView and CAEAGLLayer as provided by
Nativewindow's IOSUtil.

Test Video https://www.youtube.com/watch?v=Z4lUQNFTGMI

+++

Notable bug: The FBO used and sharing the COLORBUFFER RENDERBUFFER
memory resources with CAEAGLLayer to be displayed in the UIView
seemingly cannot handle GL_DEPTH_COMPONENT16, GL_DEPTH_COMPONENT24
or GL_DEPTH_COMPONENT32 depth buffer - none at all (Device + Simulation).

Therefor the default demo GLEventListener chosen here
don't require a depth buffer ;-)

This issue can hopefully be mitigated with other means
than using a flat FBO sink similar to FBO multisampling.

iOS: Clean up promotion of EAGLLayer use down to FBObject

Initial commit bba73bc096250a3c7fc036d84b1ea054d1b70b06 hacked
its path using a context global EGLLayer instance attachement.
The hack was good for the first demo, however, it forbid using
other FBObjects etc on the way.

Properly specifying FBObject.Attachment.StorageDefinition,
allowing the user to inject code for selected FBO attachements
to define their storage. This might be useful for different
platforms as well - however, it is OS agnostic and instance specific now.

In this sense, GLFBODrawableImpl, hosting FBObject,
has a more specific instance of FBObject.Attachment.StorageDefinition
for color-renderbuffer. It is passed along newly created color renderbuffer.

GLDrawableFactoryImpl.createGLDrawable uses a derived interface,
OnscreenFBOColorbufferStorageDefinition which is defined in
IOSEAGLDrawableFactory and return by its getter.
GLDrawableFactoryImpl.createGLDrawable is therefor platform agnostic again.

Bottom line is, as more platforms will be added, these semi-public interfaces
have to adapt to suit them all ..

All this due to iOS architecture for 'onscreen rendering' using a FBO
which shares its color renderbuffer storage with the EAGLLayer,
associated with the UIView. A bit weird maybe in first sight,
but efficient for creating cheap hardware design ;-)
Only criticism here is that Apple didn't bother using EGL and an extension.

iOS: EAGLLayer FBO w/ DEPTH buffer workaround 1

Notable bug as mentioned before:
The FBO used and sharing the COLORBUFFER RENDERBUFFER
memory resources with CAEAGLLayer to be displayed in the UIView
seemingly cannot handle GL_DEPTH_COMPONENT16, GL_DEPTH_COMPONENT24
or GL_DEPTH_COMPONENT32 depth buffer - none at all (Device + Simulation).

This workaround re-binds the used color renderbuffer for EAGLLayer presentation
at the end of the FBO drawable instantiation.

FBO DEPTH buffer works now as demonstrated w/ GearsES2.

We have to issue one more test now, using a demo using an FBO itself.

NEWT: Align native MacOS / IOS file- and classnames

Fix build test jar regression (commit bba73bc096250a3c7fc036d84b1ea054d1b70b06)

java.part.test.all was erroneously removed, redefined.

NEWT WindowImpl.doPointerEvent: Use native short[] for pNames

and not int[], this avoid copying in case given pNames are normalized.

This is benecifical for X11, Windows and the upcoming iOS touch/pointer support.

Copyright: Add missing Copyright tag

Adding the missing JogAmp copyright tag on certain files.

Currently in debate whether 'JogAmp Community' is a legal Copyright tag in the first place,
we might need to add (or replace it with) my authorship.
However, as authorship is well documented via the git repository,
this should be no real world issue.

iOS / MacOS: PixelScale Update

- IOSUtil/OSXUtil: Return float value and refine name to GetScreenPixelScale*

- WindowDriver's updateMaxScreenPixelScaleByDisplayID(..) and updateMaxScreenPixelScaleByWindowHandle(..)
will only update the maxPixelScale, as actual user pixelSize change should not be triggered here.

A user pixelSize adaption to the changed underlying scale capabilities (e.g. switch monitor)
should be supported by the implemented WindowDriver's: updatePixelScale(..) called by native code.

NEWT iOS / MacOS: Simplify setJavaWindowObject

NEWT iOS: Support Multi-Touch Events, PixelScale, ..

Note: Two subsequent commit will add some required change in the
native UIWindow/UIView creation methods to actually make the NEWT view being displayed ;-)

The demo 'com.jogamp.opengl.demos.ios.Hello' demonstrated a standard NEWT application
running on iOS.
Previous NativeWindow wrap-around demo is preserved in 'com.jogamp.opengl.demos.ios.Hello1'.

Tested on ipad 11'inch arm64 and x86_64 simulation:
- Using GearsES2 demo
- PixelScale 1f, 2f and 0f - last two using max pixel scale
- Touch w/ GearsES2 works:
-- 1 finger rotate
-- 2 finger drag
-- 2 finger pinch-zoom gesture detection

NEWT iOS WindowDriver: native UIWindow/UIView creation change

Astonishingly, the original code path doesn't show up the CAEAGL View/Layer (only the red test background)
even though t is 1:1 equal to this alternative calls.
Keeping the original path intact for future validation, another round of hours of analysis.

The original code path will be removed in the next commit.

NEWT iOS WindowDriver: Remove unused orig UIWindow/UIView creation path

See commit 004c67c73a0309158c30929cd0d6513e23f34803

NEWT iOS: Support translucent windows

and remove the redColor default background (debug only).

IOSUtil.CreateUIWindow(..) also gets its 'visible' attribute,
to be true only for demo Hello1 code - false for intended Proxy Surface Hook.

iOS: IOSUtil_CreateGLViewDemoA0 tests native UIWindow parenting (works)

Fixed native header generation for native windowing code

Removed obsolete tools.jar

In Java 9+, the tools.jar file also no longer exists in Java
installations (it's now stored in a secret non-JAR format), so removed
it.

Removed references to non-existent method getPeer() in debug code

Removed import that caused GLUgl2/GLUgl2ProcAddressTable not to compile

Bug 1363: Java 11: javah replacement: Use conditional ant targets instead of branches, also re-add bootclasspath

Refines commit df7c0ad3b98d3520f023e026b6163bcba2c7ee7e

Bug 1363: Java 11: Adapt build scripts for java11

Removed remaining bootclasspath and javah; build now works on Windows 10

(sgothel: This cherry picked merge will be refined)

Also removed a couple of duplicate "source" tags in javac tasks.

Bug 1363: Java 11: bring back bootclasspath for java 8 target accuracy

Was removed mostly via commit 63e31d05ad9f1df99663997c2f04ad086f29c8fc

We have 2 choices building for java8 under java11:
1) use source, target and bootclasspath options
2) use release option

It is said that (2) is not yet accurate enough
and (1) shall be favored as it guarantees no java>8 class leak
from the build JDK.

This patch is isolated to allow removal of said bootclasspath
if desired by anybody

Bug 1363: Java 11: Complement javah replacement: Add new iOS

Complements patch 63e31d05ad9f1df99663997c2f04ad086f29c8fc

Bug 1363: Java 11: Aligned HowToBuild.html w/ GlueGen's updated version

Bug 1363: Java 11: Adapt scripts for java11 (cont)

Fixed clean target so it doesn't fail if GlueGenTask is not present

If gluegen was cleaned, the GlueGenTask would be absent, which would
cause a failure in jogl clean (even though GlueGenTask isn't needed in
the clean target). So, modified the jogl build so it doesn't load
GlueGenTask in the clean target.

Orig commit by Wade Walker.
This alternative patch uses the ant target common.gluegen.init
to define the 'gluegen' task post gluegen compile check and pre 'gluegen' call,
avoiding the if-then-else ant-task state query:
     <equals arg1="${ant.project.invoked-targets}" arg2="clean" />

Bug 1363: Java 11: (Hack) Inject OpenJFX [basic, graphics] into CLASSPATH

The OpenJDK JAR files within this folder
only conveniently serve to compile JOGL on all platforms.

They were extracted from Debian 10's 'libopenjfx-java' package version 11.0.2+1-1

See copyright (also extracted from package above) for (c) details.

Note: This is similar to our SWT injection etc.

Removed illegal reflective access to sun.java2d.opengl.OGLUtilities

We were reading a variety of surface type definitions from
sun.java2d.opengl.OGLUtilities using reflection, which has thrown
warnings since Java 9 and which soon will become illegal. For now, just
hard-coded these types to remove the warnings that happen during static
initialization. Eventually the entire Java2D class will have to be
revamped if we want to be able to actually use it.

Bug 1363: Java 11: Don't use sun.awt.SunToolkit.awtLock/Unlock on Java9+ [illegal reflective access]

Avoid illegal reflective access to sun.awt.SunToolkit.awtLock/Unlock on Java9+

Apparently these give a performance benefit on X11 by avoiding taking
the AWT global lock, and instead only taking a Java lock defined in
sun.awt.SunToolkit. But this has thrown a warning since Java 9, and will
soon be illegal. If a performance problem remains on X11, we'll need to
find another solution.

Orig patch by Wade Walker.
This patch only skips utilizing said API on Java9+
while maintaining orig code path for Java8.

Bug 1363: Java 11: Don't use GraphicsDevice.getScaleFactor() on Java9+ [illegal reflective access]

Use non-reflective method to get the pixel scale on Java9+

It's now possible to use GraphicsConfiguration.getDefaultTransform()
instead of using reflection to get the pixel scale, which eliminates an
illegal reflective access warning.

Orig patch by Wade Walker

Bug 1363: Java 11: Use getPixelScale standard method even on Mac under Java9+

Changed getPixelScale to use standard method, even on Mac

Previously it used a Mac-specific method, but the new standard method of
device.getDefaultConfiguration().getDefaultTransform() seems to work on
Mac, so use it instead to avoid illegal reflective access warnings.

Orig patch by Wade Walker.

Bug 1363: Java 11: Resolve unsupported JAWTUtil.getMonitorDisplayID(..)

Previous commits removed access to OSX's GraphicsDevice.getCGDisplayID()
on Java9+, avoiding illegal reflective access.

Here we JAWTUtil.getMonitorDisplayID(..) simply returns null
if Java9 or !OSX, so the sole NewtFactory caller falls back
to the alternative working solution.

Orig patch Wade Walker:
    This was used on Mac OS only to create a MonitorDevice in
    NewtFactoryAWT. But there was a fallback method for creating
    MonitorDevice, and testing with TestGearsES2GLJPanelAWT shows that the
    fallback method seems to give identical results on Mac, so changed to
    just use the fallback method (which is now the only method) everywhere.
    This gets rid of an illegal reflective access.

Reverting erroneous junit-test task condition (ant build)

as introduced while hacking on iOS.

- Builds on MacOS, Windows and GNU/Linux now.

- All but 2 tests passed on Windows

- GNU/Linux AMD GPU regression
-- 1) No compat profiles on X11 device
-- 2) Remaining core only profiles disclose buggy GLProfile selection
-- This needs to be fixed pre-release

Bug 1101: Add missing disposal of Pipelined_QuadRenderer's VBOs

Original author is 'Tof'

Bug 1384: Allow GLRendererQuirks to be overridden by user properties

Allow GLRendererQuirks to be overridden by user properties,
allowing to either force (inject) a quirk by a user property
or to ignore a quirk by a user property.

This helps:
- debugging certain quirk behavior (See Bug 1383)
- allowing a user to customize the quirk setting

+++

This patch also refines the quirk: GLNonCompliant -> GL3CompatNonCompliant,
i.e. constraints its semantics to GL3 compatible context.

+++

This patch also removed useless code of GLRendererQuirk,
i.e. the 'int[] quirk' array arguments which are nonsense
or wasteful, as we operate with bitmasks.

JoglVersion.getGLInfo: Increase robustness of debug output

GLRendererQuirks: Fix typo

Bug 1383: Cleanup GLContextImpl.setGLFunctionAvailability(..): Parameter, variables and clip at 180 line width

This cleanup became necessary to re-analyse the code after quite some time.

Using clear immutable input input parameters for the requested OpenGL version+profile
and mutable current state 'has'.

Bug 1383: GLContext.isValidGLVersion() ensure only one profile bit is set max; Add OpenGL version 4.6

Bug 1283: GLContextImpl.setGLFunctionAvailbility(..) calls: When leaving OpenGL version open, don't assume the profile

The profile should be queried at runtime like the version in these situations.

Bug 1383: GLContextImpl.setGLFunctionAvailbility(..): Ensure only one requested profile bit is set; Query GL_CONTEXT_PROFILE_MASK for hasCtxProfileBits

and finally guess the GL profile bit if none could be determined:
  'isESReq ? GLContext.CTX_PROFILE_ES : GLContext.CTX_PROFILE_COMPAT'

Bug 1383: Final fix: Always test GL3CompatNonCompliant and test on requested version/profile, also ..

also, if requested version is within GL3CompatNonCompliant valid range, i.e. < 3.1,
the detected actual version will be clipped for valid mapping to the requested data.

Here it might be essential to know, that all versions are being 'scanned'
via mapGLVersions from high to low.
Therefor Version 3.0 would be tried before 2.0
and both will be mapped to the clipped actual version 3.0.
The true actual version could be the maximum, however,
using the very same would lead to trying an invalid unavailable GLProfile.

Bug 1383: Tighten version/profile qualification: fail if: requested compat profile && has core profile

On Mesa, if requesting a 3.1 compat profile, we receive a 4.5 core profile.

This is natural due to constraints within glXCreateContextAttribsARB,
i.e. GLX_CONTEXT_PROFILE_MASK_ARB is only a available for versions >= 3.2
and these are not available on Mesa.

Tested with Mesa 18.3.6 of Debian 10 Buster,
which also confirms Bug 1385 fix of limitating GL3CompatNonCompliant
to Mesa < 18.2.0

Bug 1385: Limit Quirk GL3CompatNonCompliant to Mesa < 18.2.0

Bug 1384: Move remaining 'lose' property quirks into GLRendererQuirks.Override

Bug 1363: Java 11: Use new Android SDK 24 for Eclipse Android .classpath

check-junit: enhance output (make it a brief list of classes)

Bug 1363: Java 11: JAWTUtil: Use sun.awt.SunToolkit.awtLock/Unlock and disableBackgroundErase (impl. semantics)

Commit 13c6bbbde5ea476d60e0a2f04a5172d3302d0edd simply removed the
AWT commonly used SunToolkit lock/unlock methods, which was incorrect.
It lead to certain resources access collisions as access has to be synchronized
using the same reentry lock across AWT and NativeWindow/JOGL.

We utilize the new com.jogamp.common.util.UnsafeUtil of GlueGen commit 07c1885e9a3d1f3a3853414648c06fb3864bc69f
to disable the IllegalAccessLogger while fetching the methods/fields and making them accessible.

JAWUtil also hosts access to SunToolkit's disableBackgroundAccess(Component)
aligning the code for GLCanvas, NewtCanvasAWT and AWTCanvas.

Bug 1363: Java 11: Utilize UnsafeUtil.doWithoutIllegalAccessLogger(..) avoiding further unnecessary warnings

Access to said internal non-exported methods is essential.

See commit c5431f46b7bf64f109315ec78461859dd88f202a.

Further added verbose DEBUG output where applicable.

Bug 1390: Fix GLPixelBuffer.GLPixelAttributes::convert(GL, int, boolean) failure on unsupported GL data format/type

GLPixelBuffer.GLPixelAttributes::convert(GL, int, boolean) failed on unsupported GL data format/type

On Mesa/AMD for GLPBuffer chosen GLCaps used rgba 10/10/10/2
and the GLContext set default values:
GL_IMPLEMENTATION_COLOR_READ_FORMAT: 0x1908 GL_RGBA
GL_IMPLEMENTATION_COLOR_READ_TYPE: 0x8368 GL_UNSIGNED_INT_2_10_10_10_REV

GLPixelBuffer.GLPixelAttributes::getPixelFormat(int format, int type)
currently does not handle the type GL_UNSIGNED_INT_2_10_10_10_REV
and hence returned a null PixelFormat.

Therefor the ctor GLPixelAttributes failed and threw the exception:
"Caught GLException: Could not find PixelFormat for format and/or type:
 PixelAttributes[fmt 0x1908, type 0x8368, null]"

This fix has the GLContext default values pre-validated in the convert(..) method
and to use default GL_RGBA and GL_UNSIGNED_BYTE fallback values if not supported.
This is most important to be future proof.

Later we may shall add these 32bit coding 2+10+10+10 and its reverse.

Bug 1391: Cleanup to submit fix: Update known Quirk range; BuggyColorRenderbuffer enables NoFullFBOSupport

Bug 1392: Add CapabilitiesFilter and GLCapabilitiesFilter supporting diverse reusable [GL]CapabilitiesImmutable list filter

To implement fix for Bug 1392, we have to remove certain GLCapabilitiesImmutable from the availability list.

These filter provide a a clean reusable utility for the fix.

Bug 1391 Bug 1392: Implement GLRendererQuirks DontChooseFBConfigBestMatch and No10BitColorCompOffscreen

Further enhance unit tests TestGLProfile03NEWTOffscreen,
i.e. test all meta profile types on all offscreen drawable types (fbo, pbuffer and bitmap).

Align unit test name numbers of TestGLProfile01NEWT to TestGLProfile03NEWTOffscreen.

Bug 1392: X11PixmapGLXDrawable::createPixmap() requires X11GLXGraphicsConfiguration having a valid XVisualInfo

Therefor X11GLXGraphicsConfiguration::GLXFBConfig2GLCapabilities(..) also needs to clean the GLGraphicsConfigurationUtil.BITMAP_BIT
from drawableTypeBits and if all removed, drop the FBConfig.

Bug 1392: Simplify CapabilitiesFilter: Criteria -> Test, remove RemovalCriteria as all Test definitions may be used for anything.

Buig 1389: Fix SIGSEGV on OpenJDK11 on [NSApplicationAWT sendEvent:]

Culprit of the crash and the non propagated action on NSApp main-thread
was _simply_ our OSXUtil_KickNSApp() 'kick alive'
NSApplicationDefined NSEvent sent to the NSApp.

Java11's NSApp code overrides sendEvent and handles
  NSApplicationDefined + subtype=ExecuteBlockEvent
using the given data1 as a function pointer. 8-O

ExecuteBlockEvent defined as 0, which we have sent.

Simply passing subtype=8888 avoids this side-effect.
Whether it is still required to KickNSApp() is another question.

+++

Further, make code a bit more robuts regarding the offscreenSurfaceLayer
at JAWTWindow invalidate. I.e. if still not detached, do the late cleanup there.
This just in case the OSX Context callback to disassociate the drawable
has been missed.

OSXUtil::IsMainThread() Utilize ThreadLocal storage flag avoiding unnecessary JNI calls

Bug 1393: Run orderFront0(=setVisible) async off-thread on AppKit after sync AppKit NSWindow creation

MacOS 10.14.6 + OpenJDK11U produces occasional freezes on AppKit Main Thread

Latest manual tests after resolving Bug 1389
disclosed a few occasional freezes using NEWT + Java11.

These are related to probable AWT changes since Java8,
as these do not occur with Java8.

Fix: Spun off orderFront0(=setVisible) async off-thread on AppKit after sync AppKit NSWindow creation.

This fix also aligns the macos createWindow code with the new simplified ios implementation,
see commit 004c67c73a0309158c30929cd0d6513e23f34803

Bug 1393: MacOS/iOS: Issue updateSizePosInsets0 async to AppKit Main-Thread

Additionally, setPointerIcon0 must also be made async on AppKit (instead of wait),
we have to assume/hope the user won't pull the PointerIconImpl instance in-between ;-)
Hence removing the comment regarding the lifecycle.

Bug 1393: OSXUtil: Optionally inject Apple's 'Main Thread Checker'

To allow proper testing of whether all AppKit calls are performed on its Main-Thread where required,
we inject the libMainThreadChecker.dylib when property 'nativewindow.debug.OSXUtil.MainThreadChecker' is set.

See <https://developer.apple.com/documentation/code_diagnostics/main_thread_checker?language=objc>
Lib-Name: /Applications/Xcode.app/Contents/Developer/usr/lib/libMainThreadChecker.dylib

NEWT Cleanup: WindowImpl::visibleChanged(ZZ): Remove unused 'defer' argument. Method only changes state.

NEWT Cleanup: WindowImpl: Drop unused 'defer' argument (state change only): insetsChanged + insetsVisibleChanged

Bug 1393: Add window position validation in TestDisplayLifecycle*NEWT

The OSX fixes for bug 1393 spun off certain tasks like position/size gathering async to AppKit,
hence we should validate whether both are valid.

Further the TestDisplayLifecycle02NEWT had one bug,
it retrieved 'screen.getViewportInWindowUnits()' while it was not yet initialized.

Bug 1394 - NEWT X11Window didn't gather inset at window creation (properly)

X11Window.c's 'NewtWindows_getFrameExtends(..)'
retrieves the insets via XGetWindowProperty on _NET_FRAME_EXTENTS.

Right after window creation this method fails as the WM did not yet
provide the information as the window has not yet been mapped.

Implementation needs to retry for a certain amount of time (250ms)
and maximum number of attempts (96 XEvent).

This issue surfaced while validating fix for Bug 1393,
testing TestDisplayLifecycle02NEWT also on X11.

Bug 1393: Adding test cases setting visibility before enabling exclusive context thread animator

MacOS Java11 freezes occur on 3rd NEWT window creation (orderFront) after enabling exclusive context thread animator.
Here we add set visibility upfront which does not trigger the freeze on the AppKit main thread.
Note: OpenJDK8 works flawlessly.
For some reason, the exclusive context thread enabled animator interferes when 'orderFront' is issued.

Bug 1393: MacOS: Implement AppKit EDTUtil operating solely on main-thread

Introducing boolean property 'newt.macos.useAppKitEDTUtil', which defaults to 'false'.
If enabled, the new AppKitEDTUtil is being used, operating on the AppKit main thread.
This is used to ease debugging Bug 1393, minimizing thread context switches.

MacOS: Add more debug log details

IOS: CGL.updateContextRegister(..) call on main-thread using AppKit

Bug 1393: MacOS: Wait for window position setting on main-thread (blocking)

Also issue the orderFront0 call within createWindow1 (aligned with IOS code)

test scripts: add --illegal-access=warn

make void* an opaque long in EGL generated class

detect gbm platform on linux when no other display server is running

add gbm java & build modifications

add native gbm implementation for drm and gbm initialization.

Bug 1156: EGL-GBM: Cherry pick changes ..

gbm/WindowDriver: make it compile and link

Bug 1156: EGL-GBM: Cleanup Code & Replace Newt GBM implementation

GBM driver is now under egl/gbm subpackage and has been replaced by bcm_vc_iv boilerplate.
Native code is reentrant capable and cleaned up.
TODO: EGLDisplayUtil work with SharedResourceRunner

Bug 1156: EGL-GBM: Fix Cleanup (Newt package relocation / hack default GBM)

Now: TYPE_EGL_GBM == ".egl.gbm"

Bug 1156: GBM: FIXME: Hard link gbm and drm (temporary)

Bug 1156: Utilize internal glGetStringi (same as glGetString) - Robostness

Using EGL-GBM, using desktop GL we end up with an unsatisfied linkage error after the ProcAddressTable
has been reset using the 'hasMajor' and 'hasCtxOptions'.
However looking up using 'reqMajor' and 'reqCtxOptions' seems to work.
Needs more analysis.

This change also increases robustness for scanning through GL profiles at initialization.

Bug 1156: GBM: FIXME: Remove scanning for desktop-GL via EGL, see commit e674f4fa0e795bd67335025123f9af727d856f7d

Bug 1156: EGL-GBM: [Re]use EGL Platform type for eglCreatePlatformWindowSurface as well (like eglGetPlatformDisplay)

Bug 1156: EGL-GBM: Fix NativeWindowFactory native-window-type query according to Bug 1156

- Special files like '/dev/dri/card0' can't be tested via isFile(), use exists()

Order for GNU/Linux (and other unices) IMHO is

1) Display Server (Vendor neutral)
1.1) running X11 display server (DISPLAY check enough?)
1.2) running WAYLAND display server (WAYLAND_DISPLAY check enough?)

2) Console Mode Vendor Neutral
2.1) GBM (how to check?)

3) Console Mode Vendor Specific
3.1) VCIV (how to check)

Bug 1156: NEWT: NewtFactory.getCustomClass(..) Robustness

getCustomClass(..) shall throw all required exceptions upstream.
Previous essential NEWT driver exception information got suppressed if failing, only disclosed in debug mode.

Bug 1156: GBM: Fixing native GBM code, surviving initialization

Bug 1156: GBM: Bring up incl GL rendering (TODO: GBM working page flip / sync)

- EGLSurface: Factor out 'eglCreate[Platform]WindowSurface'

NEWT egl.gbm.WindowDriver
-- Properly use GBM fourcc format and use as visualID
   for GBM surface creation and EGL config selection
-- Create eglSurface within this class
-- Hook up GBM/DRM page flip (not working yet, no visible artifacts - no swap)

- ProxySurfaceImpl.surfaceSwap() call upstreamSurface's implementation if available

TODO: 'Permission denied' calling:
- drmSetMaster (optional)
- drmModeSetCrtc
- drmModePageFlip

Bug 1156 - Implement DRM/GBM Support for JOGL(EGL) and NEWT

Adding new classes DRMLib (gluegen of drm + gbm), DRMUtil and DRMMode GBMDummyUpstreamSurfaceHook
to new package jogamp.nativewindow.drm, allowing full awareness of DRM + GBM within NativeWindow for JOGL + NEWT.

DRMMode replaces the previous native code of collecting drmMode* attributes: active connector, used mode, encoder etc
and also supports multiple active connectors.

DRMUtil handles the global static drmFd (file descriptor), currently only the GNU/Linux DRM device is supported.

GBMDummyUpstreamSurfaceHook provides a simple dummy GBM surface.

NativeWindow provides the new nativewindow_drm.so and nativewindow-os-drm.jar,
which are included in most 'all' jar packages.

build property: setup.addNativeEGLGBM -> setup.addNativeDRMGBM

Changes NativeWindowFactory:
- TYPE_EGL_GBM -> TYPE_DRM_GBM while keeping the package ID of '.egl.gbm' for NEWT (using EGL)
- Initializing DRMUtil at initialization

Changes EGLDrawableFactory:
- Using native GBM device for the default EGL display creation instead of EGL_DEFAULT_DISPLAY.
  This resolves issues as seen in Bug 1402, as well in cases w/o surfaceless support.

- GL profile mapping uses surfaceless when available for GBM,
  otherwise uses createDummySurfaceImpl (dummy GBM surface via GBMDummyUpstreamSurfaceHook)

- createDummySurfaceImpl uses a dummy GBM surface via GBMDummyUpstreamSurfaceHook

- DesktopGL not available with GBM, see Bug 1401

NEWT's DRM + GBM + EGL Driver
- Using DRMLib, DRMUtil and DRMMode, removed most native code but WindowDriver swapBuffer
- ScreenDriver uses DRMMode, however currently only first connected CRT.
- WindowDriver aligns position and size to screen, positions other than 0/0 causes DRM failure
- WindowDriver reconfigure n/a

NEWT TODO:
- DRM Cursor support (mouse pointer)
- Pointer event handling

Bug 1402: Standalone native test attempting to reproduce issue

Mesa 18.3.6 issues mixing EGL_DEFAULT_DISPLAY and GBM device on EGL_PLATFORM_GBM_KHR

Interestingly, the issue is no more reproducible. Weird.

However, it is advised to use a real GBM device handle for EGL display creation
under EGL_PLATFORM_GBM_KHR.

Bug 1156: Using EGL.eglCreatePlatformWindowSurface(..) crashes on NVIDIA 430.40 on GNU/Linux X11

Avoiding this method for now.

Bug 1200: probeSurfacelessCtx works at least since NVIDIA 430.40.

Added this version as the safe version to limit GLRendererQuirks.NoSurfacelessCtx setting.

Bug 1200 - JOGL crashes on Debian8 GNU/Linux x86_64 'NVidia beta driver 355.06' @ probeSurfacelessCtx

Updating my eclipse jogl.build.launcher

Bug 1156: DRM/GBM Native test: Add Cursor

Bug 1156: LinuxKeyEventTracker: Fix 64bit InputEvent and attempt to only use keyboard event files

The time structure on 64bit machines uses two 8 byte long values instead of two 4 bytes int values on 32bit machines.
The insufficient read on 64bit machines caused an IllegalArgument exception.
This fix considers 32 or 64 bit operation.

Class renamed: LinuxEventDeviceTracker -> LinuxKeyEventTracker, as it tracks key events specifically.

Now the EventDeviceManager tries to only use /dev/input/by-id/*-event-kbd keyboard event files,
which reduces the handling on kbd event files only.

Bug 1156: DRM/GBM: Add full PointerIcon (Cursor) Support

DRM allows 64x64 pixel cursor images, using GBM_FORMAT_ARGB888 only.

Notable: GBM_FORMAT_ARGB888 == PixelFormat.BGRA8888

Having fixed mouse and keyboard input with previous commit,
the demo com.jogamp.opengl.test.junit.jogl.demos.es2.newt.TestGearsES2NEWT
shows via key press
- i -> pointer visible/invisible
- c -> pointer icon change

Bug 1156: LinuxKeyEventTracker: Add '/dev/input/by-path/*-event-kbd' and more documentation

Bug 1156: HowToBuild: Add GNU/Linux dependencies to libdrm and libgbm

Adding test invocation script for linux aarch64 / Refined HowToBuild.html

Bug 1156: LinuxKeyEventTracker, LinuxMouseTracker: Adding property to disable each

LinuxKeyEventTracker also disable the eventX reading by default, but can be enabled via new property.

The 'return bug' (crash due to underlying console) is indeed not occuring
when using a VT w/o running console application underneath.

As Xerxes showed, one may use chvt to a free known VT or openvt.

Bug 1156: LinuxKeyEventTracker, LinuxMouseTracker: Robostness (+NEWT fix)

commit 453f80e38bcb0945e7eac27a5917dce9bdc6446b added disabling the tracker,
however the NEWT usage didn't cover all mouse tracker null pointer.

Further, let's initialize and spawn off the threads only at first getSingleton() call
not at class initialization earlier.

Bug 1156: Remove verbose print in native CreatePointer..

Scripts: Macos /opt-share -> /usr/local (Catalina Read-Only)

Scripts: Tests No Verbose

VC4: Broadcom uses libbrcmEGL.so, libbrcmGLESv2.so, libbrcmOpenVG.so and libbrcmWFC.so since 7 Jul 2016

Raspbian integration (two libGLES side-by-side)
https://github.com/anholt/mesa/issues/24

VC4: Only load Broadcom EGL driver when guessVCIVUsed

Broadcom VC IV can be used from
both console and from inside X11

When used from inside X11
rendering is done on an DispmanX overlay surface
while keeping an X11 nativewindow under as input.

When Broadcom VC IV is guessed
only the Broadcom DispmanX EGL driver is loaded.
Therefore standard TYPE_X11 EGL can not be used.

Bug 1405: Provide stand alone demo launcher reducing complexity

The launcher script also allows inflating classes and native libs to test impact on Raspberry Pi 3 Model B+.

Bug 1406: DRMUtil: Probe DRM device whether it has resources attached (and is the desired one)

First issue was that the proper DRM file had to be queries,
as Raspberry 4 may have two of them:
<--
/dev/dri/dri0
/dev/dri/dri0
/dev/dri/by-path/platform-fec00000.v3d-card -> ../card0
/dev/dri/by-path/platform-soc:gpu-card -> ../card1
-->

This patch attempts to probe all /dev/dri/card[0..99]
using this arbitrary range.
The test loop ends if:
- drmOpenFile succeeds and drmModeGetResources delivers non-null value
- the iterated probed file doesn't even exist
- 100 files has been tested ;-)

build-test.xml: fix (unused) java.part.demo.mobile

Bug 1406: demos.Launcher0: More tests ..

Misc:
- Remove unused SysExit..
- showFPS=true default
- allow setting 'useDoubleBuffer' via '-single'
- demos.es2.GearsES2: Don't be verbose on display even w/o animator

IF '-noanim', issue glWindow.display() from main thread
instead of using the animator thread otherwise.
This shall test the swap buffering code in single threaded mode!

Bug 1406: demos.Launcher0: More code path reduction: useMultiplePointerIcon must be enabled via -pointerIcon

Bug 1156, Bug 1406: NEWT DRM/GBM WindowDriver.surfaceSwap(): Pass swapInterval to optionally skip VSYNC if 0

Bug 1406, Bug 1405: demos.Launcher0: No sleep w/o animator. VSYNC setting rules (launch script w/ key tracker)

NEWT: Align DisplayImpl.createPointerIcon(..) behavior; PointerIconImpl.validatedHandle() shall not create native resource.

Semantic cleanup for clarity and equal behavior

Align DisplayImpl.createPointerIcon(..) behavior
- return null handle of createPointerIconImplChecked(..) shall be accepted,
  no exception for neither of the two creation methods.

PointerIconImpl.validatedHandle() shall not create native resource.
- throws exception if handle is null (about to be used)
- no native creation shall happen here.

Display.PointerIcon.validate(): Removed, not used.

Bug 1408: NEWT DRM/GBM DisplayDriver: Add device locking/unlocking decoration for PointerIcon operations

Bug 1408: NEWT DisplayImpl PointerIcon: Property 'newt.disable.PointerIcon' disables PointerIcon usage in general.

Bug 1408: NEWT DRM/GBM WindowDriver: Adding glFinish() before eglSwapBuffers(..) just in case ..

This is the poor man's SYNC: glFenceSync () with glWaitSync().
However, this change did not resolve Bug 1408. Earmarked to be removed!

Bug 1156: NEWT DRM/GBM PointerIcon: Use hotX/hotY drmModeSetCursor2(..), hence pass PointerIconImpl through

Bug 1406, Bug 1405: demos.Launcher0: Allow passing GLEventListener via '-demo classname'