@edvin that's my hope, although I'm ready for a break at the moment!

@thomasnield Soon :))

@edvin I do have some ideas for some future endeavors I may bounce off you later.

and thank you : )

@thomasnield Great! Let's talk about it this weekend if you have the time

Yes, I'll gather my thoughts and present a few ideas. But first, I'm going to wrap up the TornadoFX Guide before I start anything else...

dont claim him 😆

he promised the review of the todo app and my kphoto app 😉

Haha 🙂

@ron Looking at editing still 🙂

that is actually quite a good usecase tornadofx can support

@thomasnield Great, Thomas. I will do the same, it would be nice to finish the guide!

the stuff I have learned from kotlin and javafx in this channel is awesome

Same here 🙂

So, I have editing support up and running, but I'm not in love with the interface, so the current implementation is committed only so you can play with it. Pretty sure we'll want to change this when everybody has had a chance to review it.

@User uploaded a file: Untitled

There is no need to commit the edit here, since we operate directly on the bound value.

@User uploaded a file: bandicam 2016-10-02 19-40-33-533.mp4

the onEdit is available on the label?

and a double click enters it?

I like the

graphic.lookup

no the onEdit is on the cellFormat

onEdit

is available on the ListView, but it operates on the ListCell, and it's passed two arguments: The kind of edit operation and the value if the edit operation was a commit (not used here)

I mean listView

What we need to figure out is if this is a good call interface, and if it covers most use cases this way.

For advanced use cases creating a ListCell the old way is probably best.

but but but 😄 that is so much boilerplate and for me feels going against the tornadofx way of thinking

That's why I want this to work for as many use cases as possible. The result right here is that I need to use lookup to get to the label and textfield, but if the cache operated on a Fragment instead, this would look a lot cleaner. I will try to rewrite your example and show you Ron.

I want to create a Node.hiddenProperty which is a boolean property that modifies visible and managed, so that you can achieve the same effect as

display: none

in HTML. That would be very neat for this use case, and lots of others, I'm sure.

did you fork my repo?