-
Notifications
You must be signed in to change notification settings - Fork 8
TODO
The rest of the builder extensions as well as JavaFX binding extensions have to be written.
(This is currently being worked on)
See also https://github.com/eugenkiss/kotlinfx/issues/2
Like Kotlin's listOf etc. create functions for observable collections so as to not always have to FXCollections.observableList or observableList if statically imported FXCollections but rather package obs and then obs.listOf() etc.
Currently there are far too few examples in the kotlinfx-demos subproject.
KotlinFX Ensemble could use some help!
Creating more examples also helps in finding API issues. E.g. maybe a builder for a control should have an additional attribute as a named parameter to improve convenience of the API.
In ScalaFX it is sufficient to create an object that extends JFXApp and set its stage to create a launchable application. Presumably, JFXApp contains a main method that is implicitly executed when the object that extends JFXApp is run. So there is no need to define a main method for simple cases. KotlinFX should have this, too! See http://youtrack.jetbrains.com/issue/KT-5004
One eye-candy feature of JavaFX are animations. ScalaFX provides a tailored syntax for animations. KotlinFX should have this, too.
It would be cool if KotlinFX provided a type-assisted CSS DSL.
It'd be great if the JavaDoc from JavaFX could be injected into the builders and extension properties. But I don't know how feasible this is.
Research the distinctions of ReactFX and Kalium (Kalium focused on time-varying values, ReactFX focused on event-streams, observable collections and asynchronicity). Find out if and how ReactFX and Kalium can be combined.
There is this imperative reactive language in the Scala.React paper. Research if and how it can be integrated into KotlinFX or something similar and if it is even worthwhile to do so.
Create subprojects in this repository with bindings for popular external libraries like