@carlw How did you build yours without

mavenLocal()

in the build file? 🙂

you can't do a gradle build?

No, because gradle doesn't look in the local maven repo without

mavenLocal()

added to the repositories section. I added it, so it builds now, I just wondered how/why it is working for you?

my repository is in the standard .m2 folder

~/.m2/repository

global gradle setting?

Yeah, but Gradle won't look there with this build file

@ron That might be it 🙂

Anyways, not important. Moving on.. hehe

I never changed that and it works like a charm for me

@carlw I don't think you need a cache at all with your implementation. You can just get a fragment once for every cell, and just call your load function when the fragment for a cell changes, can't you?

If you use a ViewModel that would be much nicer though. No need to re-attach listeners or change bindings at all.

i think i went the cache route because it creates new list objects when you're operating on the listview

the cache is "business-y" in that it ties the generated identifier to a particular object

i think i traced this program and saw tons of updateItems() creating new object

What new objects do you mean?

Nodes

Nodes of what?

The ItemFragment hbox

b/c of prototype scope

But you wouldn't create a new Fragment in updateItem. You would do it in the constructor of the listcell, then you would just call fragment.load in updateItem (and remove all listeners from there to init)

aren't the ListCells recycled?

i think you'll get a bunch of phantom filled-in cells

You would basically have one ListCell per visible row, plus a couple. You would just remove the fragment.root from the graphic property when the list cell is not used.

If you can send me a little code, I can put it in my TodoItemListCell.kt class to test it

Sure. I think I would combine it with a viewmodel to make the rebinding a little nicer though. Let me have a look.

This seems to work with no other modifications, but it is not optimal as fragment.load does too much work:

@User uploaded a file: Untitled

I would probably rename fragment.load to fragment.updateItem or something like that for better symmetry.

seems like you might still want the cache. 1 million list objects are still going to hang around as ItemFragment members