@abhinay @jschneider @edvin I'm not sure how general the function form of column is. the code from abhinay compiles and runs but doesn't display anything. it looks like a problem with the cellvaluefactory in that form of column{} we can't add a type safe builder initializer to set the cellvaluefactory like this val mc = column("Millis", Instant::toEpochMilli) mc.cellValueFactory = PropertyValueFactory<Person, Long>("Millis")

so i think for the reflection to work, you'll need a field

Of course because you do not suspend in rxjava

I expected that every column could be changed to readonlyColumn

I am not sure about

readonlyColumn

, but can't you just set editable property on the TableView to

false

?

The problem is, I can't get it to compile with plain java objects...

it is not about editing

If you only have pojos, i'm not sure how relevant these settings are anyway. You'll need properties to update from the textfields in the TableCells

With column, does it compile?

Yes. Of course. But how can I convert to a property?

besides, the function, are there other fields you're having trouble with

?

That is the question I am asking. I have a getter and nothing more (or maybe a val)

how to convert to an observable that is accepted by column/readonlyColumn

@jschneider does this code work for you?

Yes. It does 😉

I'd stay away from the functions. maybe there's an enhancement but there's a lot of meta reflection stuff that will match strings on just class.fields instead of class.field + class.methods

I've given up on "virtualized derived fields that ought to work" in my xml processing days

Yeah. The problem is the plain old java stuff....

which doesn't work as nicely

i think it will be ok if you come up with a strategy for the derived properties

And why doesn't readonlyColumn accept a function? Any reason therefore?

not sure if there's a rationale, but the reason is parameter type matching. column expects an ObservableValue <T, ObservableValue<S>> whereas it's open for readonlyColumn <T, S>

well, ok. I'll take this as: There are reasons for it. 😉 Thanks

everything in controls like this are property based in Javafx

in both cases, the TableView or ListView is filled with properties and it's somewhat hidden in TornadoFX

I am happy to provide a function/whatever that returns an observable.

readonlyColumn creates a property on-the-fly but there is no effect on the pojo member. the reference is never used

so, it's readonly

column links to the property you've passed in, so it will take updates. and because you have a reference to it (a non-POJO), it will update automatically