@carlw OK, here goes my changes. First, in

MainView.kt

I make the ListView utilize the `TodoItemFragment`:

lvItems.cellFragment(TodoItemFragment::class)

@User uploaded a file: Untitled

That's the whole thing. There is no code involved in unbinding or any kind of house keeping other than making sure the ViewModel is rebound when the itemProperty of the Fragment changes:

It's important to notice that all UI elements only bind to the model, not to the item itself. This is how we avoid doing any kind of binding or rebinding when the item changes.

ListView and friends will actually create two cells for the first element youadd. The first one is quickly discarded (put back in the pool) and replaced by the second cell. I think they did that to work around some issue, but it has no consequence to us. I just wanted to mention it in case you wonder why the first add results in two fragments, @carlw

Another interesting point here is the `ItemViewModel`:

@User uploaded a file: Untitled

When we create it, we don't have an item. For that reason, the bind function actually accepts that you return a null value. When an item is available, it will be rebound automatically. This makes it possible to express and execute bindings before you have the source object you want to proxy with the ViewModel. We also utilize the

autocommit

feature here. This is done so that when you click the completed check box, the item is written back into the source TodoItem so that the count label can be updated. The same goes for when you edit it in the text field.

You should be able to incorporate this into your app now @carlw. I will work on some other TornadoFX/FXLauncher issues that has surfaced, mostly support stuff it seems - no bugs as far as I can tell.

@Ruckus @thomasnield FYI: https://github.com/edvin/tornadofx/issues/191

@thomasnield We probably need more information about this in the Guide. What a killer thing @Ruckus made. All those sexy transitions. I'll try to create a screencast for it.

Now I think I'd like to create a Master Detail demo that includes the ViewModel and the ListItemFragment.

@edvin I have the cellfragment statement in the special branch I created already . Is there anything else I need to do to that code? Just the rebind on the model?

@carlw You must also update the ViewModel to use the new autocommit syntax, so just copy those lines. You might check if you bind against the

model.completed

property for the strikethrough css class, I think you bound against the UI element earlier. I guess both will work though.

@User uploaded a file: todomvcFX.zip

@edvin i'm testing the viewmodel changes. i have the new tornadofx bind() and autocommit code, but I'm still getting errors. see what happens at :10 when I start using the app for a while and adjusting the filters which manipulate the underlying model

@User uploaded a file: tornadofx_newviewmodel.mp4

@edvin i see this zip...i'll compare with that

I haven't look at how you calculate the item count, I'll have a look as soon as I can 🙂

I tried real quick to induce the error you're getting in my branch and I couldn't reproduce.

@edvin yours is working for me. i'll compare all the files

Sweet! Let me know what you find 🙂

my branch has the reworked property for the items left label that doesn't make a call on the view

do you listen to the ui element instead of the model property?

The discrepancy is from how I moved the view.update() call to a model property

can you modify line 56 of your TodoItemFragment.kt file and run the following test?

@User uploaded a file: Untitled and commented: modify for a test

1. Enter A and press return

2. Check item A. The console prints out a debugging line.