if the format is known, yes JAXB. I did a lot with xstream

I prefer to stay away from SAX (I had some traumatic experiences 😢 )

Ahh.. Editable

SortedFilteredList

is beautiful 🙂

editable?

perks up

Yep.. you can add/remove/permuate objects of the SortedFilteredList. No need to access the underlying list. In fact, it could probably be made private now.

nooo dont

We probably wont. But I wonder if you have a need to access it?

I can't see any at the top of my head.

For all intents and purposes, the

SortedFilteredList

now is the underlying list.

I think (dont have the code in front of me) that I use to change the list

No, you don't. It has always been a

val

.

You may have called

setAll

on it, and you can still do that, but now you can do the same directly on the

SortedFilteredList

.

let me check in the repo

@carlw Thanks for pushing me to look at the TodoApp again. It is driving features and improvements just like last time.

Now I believe I can use a predicate to filter those different view states.

I can now also hook into change events for free, so no need to fire events or manually tell parts of the app to update itself.

I do a

setAll

indeed

right. there's a nice predicate property available for the filters

@edvin I might have some fresh ideas from the keyboard UI that I'm porting over

related to drag and drop

@carlw Great! I'll continue playing with the TODO app until it's perfect.

@carlw The

X items left

label always shows the total uncompleted tasks in your example. Is that how it should be, or was that one of the things you mentioned should be different, like we talked about earlier?

It's always present, showing the num active

Regardless of filtering mode, right?

yes. it's not tethered to the viewable itesm

(sorry for the typo, on a Vortex Core)

@edvin - if I want to filter multiple fields simultaneously, should I create a composite observable to aggregate them and set the predicate property of SortedFilteredList via a changelistener?

@grant that's the version i was shopping around. it's a little better because there's a predicate property you can bind toggles to

@gtnarg Either that, or make sure the predicate can check what it needs to filter at all times and just call

filteredList.refilter()

from the change listener.