@User uploaded a file: Untitled

@edvin interesting one, do I really need to do

val currentItem = it

do access the selected item in the setOnAction

Let's see..

Nah, you should do

cellCache { currentItem ->

I rewrote the mainview with a builder and the listview in its seperate class and it is very very small

yup works like a charm

Sweet 🙂 It might make it clearer if you call a function inside

setOnAction

instead of putting the code there, then you can swap

this@listview.items

for

root.items

So

button { setOnAction { descriptiveFunctionName(currentItem)

I actually like the

this@listview.items

annotation

OK 🙂

I like it too, but to make it clearer for anyone not completely familiar with the Kotlin syntax it might be easier to read it if it's a separate function. The function name would also clarify the intent of the button press

Your call ofcourse, just my 2c 🙂

Why do you have a separate label for the checkbox instead of utilizing the label inside the checkbox?

@User uploaded a file: Untitled

the reference app switches to edit mode if you double click it

Nice, that's much more readable I think

you can then change the text inline

I am going to need your help I think creating the stylesheet class, I suck at CSS

No problem 🙂

But about the checkbox - I didn't get the reason for not using the label in the checkbox - what do you do in edit mode?

I don't think you need the type parameter for the listview by the way, you can just write

listview(controller.todoCursor)

I just pushed everything I have to https://github.com/ronsmits/todomvcFX

no idea yet

The type will be inferred from the todoCursor

I'll run out for a while, be back on an hour or so!

I am off for a few hours too, taking the dogs to the woods

see if I can lift my depressive mood a bit

Good plan 🙂

Do we need a checkbox builder that binds the label to a property as well perhaps? Will look into that later today.

By the way, I finally found a way to have inter module dependencies and being able to reload one of those dependencies in-flight in a JavaEE container. When a service is missing, it will retry while waiting for the service to come online until finally a timeout is reached or the service is available. I've been wanting something like that for a while and I thought OSGi was the only thing that could give me that, but I did not want to give up on the JavaEE programming model. Thinking about blogging about the approach. For me it means I can finally write highly modular JavaEE code without having to communicate with REST between modules living in the same JVM.