So we could bridge it to TornadoFX using that. I'll be upfront and say we will likely be biased to prototyping things in Kotlin because its tactical and easy to change. But I don't see many problems in migrating something over to ControlsFX/openjfx once it matures, except for one: we need to plan on deprecation cycles and phasing those functionalities out of TornadoFX in a controlled way.