@edvin It's the current ListViewTest.kt file in the main fork

main project

Like it was before I merged your PR?

@edvin yes...it's an easy fix that i'm about to push up...use ListCellFragment in place of ItemFragment and add this... cellFormat { text = it.value }

That's correct, ItemFragment should not be possible to use anymore. I will change the signature of the

cellFragment

function.

Committed.

ok. look for my new PR...I added a SimpleListViewTest.kt which deconflicts all the class names, fixes the ClassCast and adds the line for cellFormat

Why do you need cellFormat if you have cellFragment?

if i leave it out, the items show up as blank. they're present (I can select them), but the value is not communicated

@User uploaded a file: Untitled and commented: New SimpleListViewTest

This is my version. Taking out the cellFormat makes the items blank

i was a little surprised not to see a toString() as I usually find in unformatted ListView entries ex, SimpleItem@ad9a8hg0a0d9hagh0

Of course that's blank, because you're just binding against the itemValue property which is not bound to anything 🙂

So the SimpleItem is not really there? Does cellFormat add it?

In the code above, MySimpleItemFragment's itemProperty will always reflect the currently active item for the cell, but there is nothing binding it to the label. The extra SimpleStringProperty() defined in there is never touched by anything. If you don't want bindings and just want to update the label you can do something like this:

@User uploaded a file: Untitled

Not very pretty, so using the ItemViewModel cleans that up.

@User uploaded a file: Untitled and commented: ListView w/o extra field

How about this? uses a declarative approach (cellFormat) instead of adding listeners

In this case, the MySimpleItemFragment does nothing, you simply don't need it since you assign to the text property of the listCell and you basically only have the label in the cell. For this use case you can simply skip the whole cellFragment and just use CellFormat and you're done.

great. i'll pull that out and repost

@User uploaded a file: Untitled and commented: Removes fragment

Grr... I forgot to include one small utility function in the release. The correct way to use fragments and binding is this is 1.5.7:

This is to supplement the more complex view model example /test BTW

@User uploaded a file: Untitled

But that stuff inside init is boiler plate and can be done automatically with a small change.

@User uploaded a file: Untitled

i'll add that change too

I don't see the bindTo() function. is that something you're working on?

I just committed it.