Experimental Applet without AWT (Applet3)

DISCLAIMER:
  - Only new Applet3 applets are supported under X11 for now

  - AWT Applet are disabled

  - Namespace com.jogamp.* and jogamp.* is only chosen
    to indicate new AWT-less code

  - Applet3 code path does not invoke any AWT function

  - JNLP code path still utilizes AWT/Swing (UIs, ..)

TODO:
  - Refactor AWT dependencies properly via UI interfaces ?

  - Decide whether we shall merge netx and plugin namespace ?
    IMHO the right thing to do, jumping hoops due to separation.

  - Add support for Windows, OSX, Wayland, ..

Applet3:

- New AWT-less Applet3 interfaces are:
  - com.jogamp.plugin.applet.Applet3
    - User implements

  - com.jogamp.plugin.applet.Applet3Context
    - Plugin implements

  - com.jogamp.plugin.ui.NativeWindowUpstream
    - Plugin window, aka browser parent of Applet3

  - com.jogamp.plugin.ui.NativeWindowDownstream
    - Applet3 user window

- User interfaces are exported as:
  - plugin3-public.jar
  - plugin3-public-src.zip

1 files changed, 21 insertions, 0 deletions

diff --git a/netx/sun/applet/Applet3MessageHandler.java b/netx/sun/applet/Applet3MessageHandler.java
new file mode 100644
index 0000000..140e5eb
--- /dev/null
+++ b/netx/sun/applet/Applet3MessageHandler.java
@@ -0,0 +1,21 @@
+package sun.applet;
+
+import sun.applet.AppletMessageHandler;
+
+public class Applet3MessageHandler extends AppletMessageHandler {
+
+    public Applet3MessageHandler(String baseKey) {
+        super(baseKey);
+    }
+    
+    public String getMessage(String key) {
+        return super.getMessage(key);
+    }
+    public String getMessage(String key, Object arg){
+        return super.getMessage(key, arg);
+    }
+    public String getMessage(String key, Object arg1, Object arg2){
+        return super.getMessage(key, arg1, arg2);
+    }
+    
+}