I'm a fan of using JavaFX properties to implement MVVM patterns.

IMHO, it might be worth exploring native debounce/throttle support in JavaFX's event model.

This could potentially improve performance while also enhancing developer convenience.
(Just sharing a thought, not a feature request.)

I'm a fan of using JavaFX properties to implement MVVM patterns.

IMHO, it might be worth exploring native debounce/throttle support in JavaFX's event model.

This could potentially improve performance while also enhancing developer convenience.
(Just sharing a thought, not a feature request.)

That doesn't apply to JavaFX. There are many devs, it's used in major corporate projects. But it's not a strategic component for any of the big companies working on openjfx/openjdk, so no devrel, no techvideos, no T&M sales/support... just tons of incoming mail for me.

This adds flavors that fluent API enthusiasts will appreciate on top of the original JavaFX API.

Currently, it is a SNAPSHOT version that can be tested by adding it as a Maven dependency.

I plan to release an early access version next, but before that, I would like feedback from JavaFX developers.