Page History

The Wakefield committers may hold off-line discussions from time-to-time. Since these meetings are just for the committers and invited wayland experts, summary minutes will be recorded here as time permits

Online Zoom Meeting 9am PST Apr 25  2024

Attendees: Niels de Graef, Kevin Rushforth, Victor D'yakov,  Alexey Ushakov, Olivier Fourdan, Phil Race, Maxim Kartashev, Alexander Zvegintsev

Phil:

We made changes in the specification of the Java 21 to accomodate Wayland.

At that time wasn't expected to be backported, but in order to be able to run 8,11,17 which are LTS and will be supported for a significant period of time,

that will overlaps with the lifetime of RedHat Linux 10 without the X11 session support.

Maintenance Releases of Java 8, 11 and 17 specifications, will have these specification changes to allow the implementation update on those.

Alexey:

Do you plan to port all the code that we are going to write to that releases? Pure Wayland Toolkit?

Phil:

Not a chance. This is purely by XWayland, this is a spec change, we not even backporting the Robot changes we did in 21.

At some point RedHat, Oracle, Azul or somebody else might decide to put the Robot changes into their versions of 8, 11 or 17 as well.

After the specification changes in MR, you don't have to backport Robot changes, you are compliant at this point, but it just doesn't work very well.

Alexander:

I've been busy with beforementioned spec backports for the MR, discovered and fixed missing doPriviliged calls on our TokenStorage implementation,

Fix tests that try to interact outside the XWayland server. I also tried to test the XTEST - libei support(should be available on Gnome 45) on beta of Ubuntu 24.04(Gnome 46), but it doesn't work, no confirmation dialog appeared.

I tried the xdotool and java.awt.Robot(XTEST internally). Is this supported only on Fedora?

Olivier:

just a couple of comments on xdotool, it heavily using XTEST for everything, I personally fixed upstream, it might now work.

I believe mutter had support of libei before XWayland, this is still optional, meaning that it depends whether XWayland itself have been build with libei support or not.

So it depends how XWayland was build on Ubuntu, but if they build the XWayland with libeie, than the XTEST would go through the libei as you expected.

Alexander:

Another question, what about the HiDPI support patch for the XWayland? It's probably good time to make it into JDK 23

Alexey:

We actually switched to the pure Wayland implementation now, but I ask Nikita to continue work on this.

I continue my work on Vulkan implementation, hopefully we will have something next week. It is similar to the Metal work, but this API is more complicated.

I have something working, but I need to put it together to at least have something interesting to show.

Niels:

Last meeting you mentioned that software rendering practically complete. It is interesting to know how people evaluate this.

Alexey:

Software rendering works quite good, but we got everighing possible from it. It is slower than hardware rendering. From our perspective is quite good for the preview.

In some cases we have low performance.

Maxim can provide more details.

Maxim:

We have received quite a few reports from users who tried this Wayland Toolkit and run our IDEs on that, discover some bugs.

Actually nobody complains about performance, I don't think that expectations are high, people know that it is not hardware accelerated.

Main complaint was from, I accidently discovered that window resizing was way slower on Wayland Toolkit comparing to XToolkit.

I made a few changes and now we got ~30 fps in 4k when it was ~10 fps before, it's quite smooth, even with software rendering.

We made a bunch of fixes here and ther since last meeting, e.g. one of the guys added support for more than 3 mouse buttons, which was not present before.

Olivier:

There is  a proposal for a new category of Wayland protocols at compatibility. That could be useful for Wakefield project as well. Right now it is more about creating the category.

The reason why I wanted to mention it, somebody mentioned Wakefield as part of the discussion, specifically about something Wakefield does, about a bug with the maximum size of a window.

Is that something that we know about?

Maxim:

If understand correctly, I did a small change relatively recently with regards to limiting the maximum window size, because one of the tests started crashing JVM. It creates a window of size MAX INT.

Now it limits the size twice the size of combined monitors.

Online Zoom Meeting 9am PST Feb 29  2024

Attendees: Jonas Adahl, Kevin Rushforth, Victor D'yakov,  Alexey Ushakov, Olivier Fourdan, Phil Race, Maxim Kartashev, Alexander Zvegintsev

...