@gtnarg OK, I'll see if I can support it in a meaningful way.

I agree that POKO would take priorty though...

It would require doing everything trough the TableColumn interface I believe.

allthough I completely understand the need to support javafx properties first, POJO's will always be a part of javafx I guess.

@ron I'm making this in a way so the interface can stay the same if we supporty POJO's later.

@thomasnield I've created some cool function to extract the underlying property and value from a TableColumn, given an item <T>. This is fun 🙂

Aahh.. it worked on the first try 🙂 Haven't started looking at the graphical representation, but I now track dirty items and a list of of dirty columns for each item, with rollback working.

@User uploaded a file: rollback.mp4

@edvin Dude nice, does it support rolling back specific records rather than all records too?

@thomasnield Yes, the rollback button here tells the model to call rollback on each item tracker.

Awesome. And BTW those functions, will they be publicly available? They sound very useful.

Absolutely 🙂

I'm currently trying to decide how much info should be available as observable properties. If you should be able to update individual column state and render it somehow, I think I need a map of properties corresponding to each item in the list, and keep them synced somehow.

I'll try the all out approach first.

That makes sense, and then we can see which stuff takes up memory and perhaps eliminate them or make them lazy.

Yes, I think actually I might be able to make them lazy by default.

That seems to be the easiest, and the most sensible.

I'm also making sure it handles the case where you change the itemsProperty of the tableview.

(Assign a new list)

I don't think I'll bother tracking removals, it might free up some memory, but I'll leave it as a TODO.

Yes, definitely new records need to be added, might be able to get away with not handling removals for awhile. It might become more significant if you frequently "rebuild" your

items

from scratch, as in a database query refresh.

Might be jumping ahead... how do we streamline conditional formatting? It may not be driven just by dirty state but also the value itself.

New webcast is now up!

@thomasnield When you change the itemsProperty I already clear the list, so the only case I'm not handling right now is if you edit an item and then remove it. It would still be in the underlying map. Actually, it's easy to fix, I'll make sure to handle removals at once.

@thomasnield Done 🙂

@thomasnield Will look at what we need to expose to do formatting easily later today. I'd like to write some more in the guide first 🙂

Okay awesome! Thanks @edvin, you are a wizard

@User uploaded a file: dirty column tracking.mp4

@thomasnield Observability is in place 🙂