On Tue, 15 Jul 2025 01:11:14 GMT, Kevin Rushforth <k...@openjdk.org> wrote:
> Even if this remains a testing feature, how should it eventually be > configured? Using system properties? Some sort of config file? Something else? This was discussed in a number of comments as well, and the suggested approach is to leave configuration for follow-up PR's. There are a number of options (e.g. system properties, but also an API), and some of them would require a CSR and/or more formal work. Getting more input from usecases would be helpful here. > How should this interact with the AWT headless toolkit? Or does it? There is no interaction yet. I believe there might be value in more direct interactions with AWT though, e.g. with the AWT Print API. > This requires the prism SW pipeline. How / where should be document this > restriction? Surprisingly (or not), most of the tests I've ran (e.g. the OpenJFX system tests) do not require the prism SW pipeline. But tests where one wants to check what pixels are rendered on screen require prism SW indeed. It's a good question where this needs to be documented. Since there is no new API, it can't be in the new API docs. One of the options is to add it in a property overview document, e.g. like the one from Abhinay at https://github.com/abhinayagarwal/abhinayagarwal.github.io/blob/master/_posts/2022-10-03-OpenJFX%20flags.markdown . Since the headless platform is enabled by setting a System Property, it could be useful to add the associated options along that system property. ------------- PR Comment: https://git.openjdk.org/jfx/pull/1836#issuecomment-3088443171
