I think that we'll be able to bump to Java 25 in JavaFX 25, like we did with 21. I suggested initially to bump to Java 22 exactly for FFM as it's very useful for JavaFX, but was told we shouldn't since it's not an LTS version.
I have no idea how long the work on Wayland will take including the code review (a rather long process), but you should be able to request code reviews with FFM and have it ready for integration by Java 25. On Mon, Apr 22, 2024 at 5:49 PM Thiago Milczarek Sayão < thiago.sa...@gmail.com> wrote: > I was just experimenting, but it seems to be less work than going with JNI. > If I am correct, the next Java LTS will be 25, which will be required on > JavaFX 29 to be released on September/29. > > It's 7 years - that's really too much. > > Maybe it's still worthwhile to prototype using FFM and then port > everything to JNI. > > -- Thiago. > > > Em seg., 22 de abr. de 2024 às 11:21, Kevin Rushforth < > kevin.rushfo...@oracle.com> escreveu: > >> Note also that we cannot use Panama in the JavaFX internals yet, since >> the minimum version of the JDK is 21. >> >> -- Kevin >> >> >> On 4/21/2024 10:51 AM, Thiago Milczarek Sayão wrote: >> > Hi, >> > >> > I did a small test app to explore Wayland client and portals (for >> > Robot and dialogs such as file open/save). >> > >> > https://github.com/tsayao/wayland-test/blob/main/wayland-test.c >> > >> > It seems it will work as a glass backend, but some walls will be hit >> > on the way :) >> > >> > I have tried to use jextract (from project Panama) to work directly >> > with java, but it seems it does not support wl_ types. >> > >> > -- Thiago. >> >>
