Switching to ANGLE ?

[Kevin Rushforth]

We briefly considered this several years ago. We are unlikely to switch 
Prism rendering to Angle. Having a dependency on another large 
third-party library in our core renderer is not a direction we plan to 
go. As a note, WebGL wouldn't fall out for free from this anyway, since 
the way WebKit's WebGL integrates with Angle is different from what 
would happen if Prism used Angle internally, so there would still be 
effort needed to integrate them.

-- Kevin

On 11/4/2022 8:53 AM, Anirvan Sarkar wrote:
> There is an ANGLE RFE [1].
> It is closed as a duplicate of an older WebGL RFE [2].
>
> [1] :
> https://bugs.openjdk.org/browse/JDK-8134841
> [2] :
> https://bugs.openjdk.org/browse/JDK-8091035
>
>
>
> On Wed, 2 Nov 2022 at 7:56 PM, Mike Hearn <mike at hydraulic.software> wrote:
>
>     On a topic unrelated to Conveyor, I saw the JavaFX roadmap
>     document presented at JavaOne and the mention of a Metal pipeline.
>
>     It prompted a thought I've never got around to exploring - does it
>     make sense to switch JavaFX to using Google's ANGLE library i.e.
>     to decommission all but the GL backend and then use it on every
>     OS? This would have three big and obvious advantages:
>
>     1. A big reduction in the maintenance burden. A metal port is
>     maybe no longer required.
>
>     2. A component or canvas that exposes a GL context (implicitly, on
>     the current thread) could then be provided relatively easily,
>     allowing easier integration of arbitrary drawing with the scene
>     graph without compromising portability.
>
>     3. In turn that would unblock enabling WebGL in the WebView
>     control, fixing Google Maps.
>
>     It's mostly a question of curiosity but I'm wondering if that
>     approach has ever been prototyped or explored.
>
>     thanks,
>     -mike
>
> -- 
> Anirvan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/openjfx-dev/attachments/20221104/dee76768/attachment.htm>