OK. Pulling it now.

there is a patch file in it called onrebind.patch it contains the changes I made to the ViewModel.kt

Should I apply it?

if you want to code to work 🙂

Hehe

I'll just look at the code instead, there was some issues applying it.

its probably not the best way of doing it, but it does show what I want to achieve

without this the only way I can do it is having the left know about the right so it can call an update function of the right

Nah.. but it makes it a bit harder because you don't have properties in your immutable domain objects. Need to think for a few minutes.

you dont like the onRebind?

Hang on, just need to understand it.

I have to start somewhere.. hm.. The items for the categoryListView is assigned via

items = controller.categories.observable()

so any changes to the items will not be reflected in the list view.. isn't that problematic?

nope it does not change. in the full program it will do a rest call to get the categories, those dont change

OK, I see. Moving on 🙂

in the example I use an

index

to select what I want to see in the right table

in the full program its an url that will be loaded in a

runAsync

(this is a poc for work, so I cannot share the real code)

OK

You have a

onUserSelect

thing that does the rebind. That works, but now it's possible to do it with a lot less work, but that would probably require your domain objects to use JavaFX properties, and you're not a fan, right?

@ron What you would need here, is a way to listen for rebinds on the data model, that would make this simpler for you, yes?

yes

I don't see any harm in adding it.

I dont mind javaFx properties, but I am bound here to already existing pojo’s

OK. Let me try to add a rebindListener to ViewModel.

the lot less work is the ItemViewModel?

Indeed. I could rewrite the app just to show you, but first let me add the listener, OK?

ok

and I would be quite interested in that

the

selectExample

I kept as small as possible

dont think I could make it smaller 😉