@gtnarg I'm going to use the project to test some stuff while I write and review the guide. There are some functionalities @edvin made I haven't played with yet. This project will be a good opportunity to apply some of these recent developments. I'm also going to try and apply RxJava 2.0

My voice is a bit better now, so I'll try to create some screencasts soon as well 🙂

hey guys, im looking to use a binding expression with a kotlin property, does tornado FX supply something like that?

kotlin

class ThingyController { 
  val name by fxProperty()
}

fxml:

<Checkbox text="${controller.name}">

does tornado fx have an idiom around that?

@groostav No, we only go the other way around, but that's an interesting idea. Today you can do:

@User uploaded a file: Untitled

Most people use the type safe builders, so we haven't innovated a lot around FXML.

yeah i must confess the syntax is appealing but

the temptation to put conditional logic in view code

is too much of a turn off for me

and scenebuilder is pretty nifty

We'd like to support FXML/SceneBuilder as much as we can. I'd like to look into binding expressions 🙂

yeah I cant think of a reason that we couldnt do something like

var alphaValue by fxProperty()
fun alphaValueProperty() = existingProperty("alpha")

That would probably entail a custom FXMLLoader though.

yeah im not so sure

also i was looking into forking that thing myuself and i will say that i discovered

much to my surprise

it uses only public API's

so the

FXMLLoader

is forkable

well, aside from oracle licensing nonsense of course

Hm.. but the default loader already supports expression binding it seems? https://docs.oracle.com/javase/8/javafx/api/javafx/fxml/doc-files/introduction_to_fxml.html#expression_binding

Maybe we can hook into that somehow..

ah i see, yeah @edvin thats what I was doing

the FXML loader will automagically look for a getter and a

xProperty()

method by convention when it evalutes the little FXML snippit i gave you

what I want to leverage kotlin (and maybe tornadoFX) to do is use its property syntax to avoid the typical java boiler plate

consider something like the tornado-FX assisted kotlin:

var alphaValue by fxProperty()
fun alphaValueProperty() = existingProperty("alpha")

vs the typical java-based javafx boiler plate:

private final BooleanProperty editable = new EditableProperty<>(this);
    public final boolean isEditable() { return editable.get(); }
    public final void setEditable(boolean value) { editable.set(value); }
    public final BooleanProperty editableProperty() { return editable; }

the former is much more fun

and kotlins property semantics representa really good fit here

This we already have pretty good support for 🙂