From 70185c3e58ff0c48d2bc21a88a25155cd3f18305 Mon Sep 17 00:00:00 2001
From: Hummer12007 <hilobakho@gmail.com>
Date: Thu, 13 Oct 2016 00:25:05 +0300
Subject: [PATCH] Created Running programs natively under Wayland (markdown)

---
 Running-programs-natively-under-Wayland.md | 33 ++++++++++++++++++++++
 1 file changed, 33 insertions(+)
 create mode 100644 Running-programs-natively-under-Wayland.md

diff --git a/Running-programs-natively-under-Wayland.md b/Running-programs-natively-under-Wayland.md
new file mode 100644
index 0000000..20ac570
--- /dev/null
+++ b/Running-programs-natively-under-Wayland.md
@@ -0,0 +1,33 @@
+If your toolkit/library supports this, you can have your apps run natively (without XWayland) by setting some environmental variables (you can add them to your launcher script or a session file (if you're using a dm)).
+
+Beware: clipboard synchronization between X and Wayland is not yet implemented.
+
+## GTK+ (3.0+)
+```
+GDK_BACKEND=wayland
+CLUTTER_BACKEND=wayland
+```
+
+## Qt5
+```
+QT_QPA_PLATFORM=wayland-egl
+```
+
+## Elementary/EFL
+```
+ECORE_EVAS_ENGINE=wayland_egl
+ELM_ENGINE=wayland_egl
+```
+
+You could set them to `wayland_shm` instead, if you want to use software rendering.
+
+## SDL
+```
+SDL_VIDEODRIVER=wayland
+```
+
+## Java
+Some Java awt applications would not display properly unless you set the following.
+```
+_JAVA_AWT_WM_NONREPARENTING=1`
+```