But I think instead we need to deprecate

cellCache

and introduce another function with a better name that does the above trick (

graphic = cache

).

Sorry for the basic question, I am new to both JavaFX and TornadoFX. I wonder why in the core framework FXProperties are always capsuled inside functions, like in the following example from FX.kt

private val _messages: SimpleObjectProperty<ResourceBundle> = SimpleObjectProperty()
var messages: ResourceBundle get() = _messages.get(); set(value) = _messages.set(value)
fun messagesProperty() = _messages

Why not write it like this and save a line?

val messagesProperty: SimpleObjectProperty<ResourceBundle> = SimpleObjectProperty()
var messages: ResourceBundle get() = messagesProperty.get(); set(value) = messagesProperty.set(value)

Isn't this effectively the same? Is this a mere convention or am I missing something?

It is a JavaFX properties convention to have a “xxxProperty” function. See here for details: http://docs.oracle.com/javafx/2/binding/jfxpub-binding.htm

However, it could be encoded in Kotlin just like you’ve suggested (with a single property), but one will need to use

@JvmName("xxxProperty")

annotation on the getter of the property.

.. which would require an additional line. Thanks for clarification, I'll stick to the fun convention 🙂

Personally I always liked that we did not have to use the @JvmName property for it

@doubleu This is not the idiomatic TornadoFX convention, and you really don't need to adhere to that JavaFX convention either. We support helpers for two different ways of defining properties and getters/setters. This code was written before any of them were created 🙂 These are the two ways you should create properties:

@User uploaded a file: Untitled

I always suggest using the latter unless you really need that JavaFX convention.

@elizarov I think one of the few places you need that convention is for defining table columns in vanilla JavaFX, and we have much smoother ways to do that in TornadoFX, which doesn't require exposing the property as a function.

column("Name", Customer::nameProperty)

The

column

builders in TornadoFX actually supports POJO (getter and/or setter reference), property field references, property function references and also a lambda to return the property.

Usage of the by-keyword indeed makes the code much smoother, especially in my use case. Thanks again, I'll refer to that

Yeah, I love that syntax myself.

I just added a

Tab.whenSelected

helper.

Got my System76 Galago Pro. Awesome machine. How they got the ports on a thin device is pretty clever, especially ethernet jack

@thomasnield That's refreshing to see, more and more vendors are removing the ethernet jack.

@thomasnield How is the track pad? Smooth?

@edvin Is there a way to pass (non-String) parameters via the constructor to a TornadoFx App and/or JavaFx application?

@thomasnield perhaps you might know also . . .

i am thinking I could constructo a tornadofx app and then launch it

but i can't figure out how to do that . . .

@danko9 Is your use-case command line arguments, or something else?

@kastork something else, yeah not just strings

i have seen the string passing

but from a command line

yea not command line

@elizarov @edvin The JavaFX convention is also needed for some magic binding from FXML if you use it, but it's a pretty rare use case. (Though admittedly I still prefer

@get:JvmName("xxxProperty")
val xxxProperty = SimpleStringProperty()
var xxx by xxxProperty

)

So you are trying to instantiate the application from some other java code?

When you have WiFi driver issues, having an ethernet is pretty critical.

@danko9 Why not convert the Strings to whatever primitive you need?