At one point there was one or one that had an API close to JOGL. It was
slower and bigger that what we have now. I would not be opposed to
someone in the community looking into this again, be we wouldn't revisit it.
Steve
On 2014-01-14 10:43 AM, Tom Schindl wrote:
Would it be better to work
I doubt it. We used to have a JOGL prism pipeline in FX 2, but retired
it, and got a significant footprint reduction and performance boost
(mainly due to how JOGL manages contexts and drawabled).
Btw, the ES2 code for windows is already in the repo, and is part of the
OpenJFX build. We just do
Would it be better to work on a jogl prism pipeline itself?
Tom
Von meinem iPhone gesendet
> Am 14.01.2014 um 16:15 schrieb Stephen F Northover
> :
>
> It should all just work. The first step is to go and build OpenJFX. If
> something doesn't work, we can help you through JIRA and this list
It should all just work. The first step is to go and build OpenJFX. If
something doesn't work, we can help you through JIRA and this list.
Steve
On 2014-01-14 6:57 AM, Felix Bembrick wrote:
Thanks Stephen.
If I were to build an OpenGL-based platform for Windows, would the
font rendering te
Thanks Stephen.
If I were to build an OpenGL-based platform for Windows, would the font
rendering technique need to change? That is, could DirectWrite still be
used to rasterise the glyphs (if that's what's currently happening) and
would there be any reason for the text rendering quality to degra
Essentially, OpenGL on Windows would be another platform to support. If
you build your own OpenJFX for Windows, it will work but it is
completely unsupported.
https://wiki.openjdk.java.net/display/OpenJFX/Building+OpenJFX
If you run into any problems after you have successfully built (ie. the
