Planning for JavaFX.next

[Johan Vos]

+1 on CSS and SG performance improvements. They are very tightly coupled
(e.g. lots of SG-related calls during CSS pass and lots of redundant CSS
processing during layout pass) so either they get decoupled, or they stay
like is, but then performance improvements require cross-team work.

- Johan

Op do 8 dec. 2016 om 00:46 schreef Jonathan Giles <jonathan.giles at oracle.com
>:

> 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
>