Posted by Sven Gothel on Jan 13, 2020; 8:56pm
URL: https://forum.jogamp.org/NEWTCanvasJFX-Resize-tp4040254p4040262.html

In 2015 I elaborated options
<https://jogamp.org/bugzilla//show_bug.cgi?id=607#c20>

Especially for a low memory footprint, high performance and
reducing library dependencies - I would recommend to drop
JavaFX's current GL binding w/ JOGL to be used by Prism
- and have NEWT replace Glass.

Embedded systems would benefit big time.

+++

WriteableImage is a poor design choice,
as it would have been easy to use something EGL based
for both, GL and Vulkan.

Exposing a factory interface implemented by the user,
who then would provide a matching framebuffer
within OpenJFX's requirements.

<https://jogamp.org/bugzilla//show_bug.cgi?id=607#c27>

That would have allowed a potential zero CPU copy
until the compositor does its thing - compositing ;-)

Exposed this comment here
<https://jogamp.org/wiki/index.php?title=SW_Tracking_Report_Feature_Objectives_Overview#OpenJFX>

I personally prefer a GraphUI/NEWT solution
<https://jogamp.org/wiki/index.php?title=SW_Tracking_Report_Feature_Objectives_Overview#Graph>

+++

It all depends on financing from commercial parties,
as we have surely many ideas to work on.

So again - if any companies are listening and can utilize JogAmp
more for their product, please see
<https://jogamp.org/wiki/index.php/Maintainer_and_Contacts#Commercial_Support>

As of today our project funding has reached ZERO.

;-)

Cheers, Sven

On 1/13/20 6:59 PM, MikeORC [via jogamp] wrote: health & wealth
mailto:[hidden email] ; http://jausoft.com
land : +49 (471) 4707742 ; fax : +49 (471) 4707741
Timezone CET: PST+9, EST+6, UTC+1