Altough ScalaFX uses wrappers and implicits to deliver a transparent way to
code UIs, a ScalaFX control is not JavaFX control. It has enriched methods and
is a superclass of it.
I think ScalaFX should stand proud and make differences between a JavaFX
control and a ScalaFX one. Just like Scaloid [1] does.
Explicit is sometimes better than implicit in terms of readability.
Search for a component (JavaFX) that is a subset of another (ScalaFX) could be
a problem with the documentation.
What I propose is renaming the wrappers as S<Control Name>.
Button => SButton and so on.
This way, we explicitely know we are dealing with a ScalaFX control and showing
proudly the use of this library.
[1] https://github.com/pocorall/scaloid
Original issue reported on code.google.com by dae...@gmail.com on 9 Sep 2013 at 4:40
Original issue reported on code.google.com by
dae...@gmail.comon 9 Sep 2013 at 4:40