Rather than a "GLNode", I'm a strong advocate for a more API-agnostic "3D Canvas Node", given that JavaFX supports both OpenGL and Direct 3D currently (and one would expert Vulkan as well in the longer run).
But such a node type is IMHO absolutely critical for JavaFX and, for me, is the most obvious "missing feature" for a hardware-accelerated graphics toolkit. Felix > On 9 Dec. 2016, at 20:53, Nikos132 <nikos...@gmail.com> wrote: > > Hi again, > > I really miss a way to reuse all the OpenGL (jogamp) code developed for > many years. > > A kind of GLNode would be nice, and maybe the jogamp community could be > ready to contribute? > > > Erik De Rijcke's answer really speaks to me since I've experienced very > poor performances with the basic SwingNode solution and maintenance > problems with exotic tries to access GL context from Prism. > > Regards > > 2016-12-09 9:21 GMT+01:00 Matthieu BROUILLARD <matth...@brouillard.fr>: > >> Hi Folks, >> >> for us in my company I would said the most important topics are related to >> performances: >> >> * CSS performances >> * TableView performances >> * ensure correctness, including memory leaks, of software-rendering >> pipeline (lot of our customers use Citrix farms with no GPU acceleration) >> >> for everything related to webview (we embed lot of webapps in our client >> side java container) it is a bit late for us we are currently switching to >> JxBrowser. >> >> Matthieu Brouillard >> >> >> On Thu, Dec 8, 2016 at 12:45 AM, Jonathan Giles <jonathan.gi...@oracle.com >>> >> wrote: >> >>> Hi folks, >>> >>> Development on JDK 9 is slowly starting to ramp down, and we are starting >>> to turn our attention to the goals for JavaFX in JDK 10 and beyond. We >> are >>> starting to compile our list of what we think is important, but we really >>> want to hear from the community about what their highest priorities are >> to >>> them. As always, it's important to keep in mind what JavaFX is (e.g. it >>> isn't aiming to be a high-performance game engine), but even still there >>> are bound to be a number of places where people might want to weigh in, >> for >>> example: >>> >>> * New layout containers (e.g. Flexbox) >>> * Public APIs for UI control behaviors >>> * Marlin renderer enabled by default >>> * Support for CSS animations >>> * CSS performance improvements >>> * TableView improvements (cell spanning, row / column freezing, etc) >>> * TableView performance >>> * Focus traversal API >>> * WebGL support in WebView >>> * Improved image I/O support >>> * A JavaFX equivalent of the AWT Desktop APIs >>> * Multi-res image API >>> * NIO-backed writable images >>> >>> If there are other areas of interest that aren't listed here, please >> start >>> discussing them and we can work together to determine priorities. If all >>> you want to do is add a +1 for one of more of the items above, even that >>> will be very useful. >>> >>> Thanks, >>> -- Jonathan >>> >>
