Dne 13. 12. 21 v 11:28 Neal Gompa napsal(a):
On Mon, Dec 13, 2021 at 4:56 AM Danilo Spinella firstname.lastname@example.org wrote:
On Mon, 2021-12-13 at 10:36 +0100, Michal Hlavac wrote:
There is an open issue about it which has been untouched for 1 year now. https://gitlab.freedesktop.org/wayland/wayland/-/issues/32 This is something the screencopy protocol supports. GNOME Shell has NACKed our protocols, so they won't implement it. Other compositors like KDE are potentially interested.
It seems to me like an issue with Gnome Devs not wanting to implement this protocol. Still an issue though. My guess is that for most use cases, pipewire should suffice for now.
I can't switch to wayland because java programs looks really bad in wayland on HiDPI display. https://wiki.openjdk.java.net/display/wakefield/Open+Unsolved+Problems
Yea, that's another good issue and reason to not use Wayland by default. openJDK is slowly adopting Wayland, but it will take time. Maybe we can create a wiki page to track the critical issues as this one?
No, it isn't. Project Wakefield is about making the applications run on Wayland natively. Today, those applications run fine on Wayland as Xwayland applications.
In fact, most application stacks that don't support Wayland directly work fine on Wayland through Xwayland. Unless you're crazy enough to turn off X11 compatibility in your Wayland session, switching to Wayland is transparent for all but a couple of cases (screen sharing being the main one).
Direct citation from https://wiki.openjdk.java.net/display/wakefield :
The Wakefield Project will pursue two goals: a short to medium term solution for JDK running on Wayland in X11 compatibility mode a medium to long term solution for JDK running as a native Wayland client.