The acceptance test will require some work. Everything needs id's, and some of the structure is set because of the tests, but that's no biggie.

its a gradle build so I will just make an fxlauncher for the origin app

Never mind Ron, I should be able to just fork it and run it 🙂

ok

rofl look at this: https://github.com/ronsmits/todomvcFX/blob/master/examples/mvvmfx/src/main/java/todomvcfx/mvvmfx/ui/item/ItemViewModel.java

That's boilerplate!! 🌪️ 🔫

just pointing it out

Hehe, I was trying to be funny 🙂

dont shoot the messenger 🛡️

Would it be nice to have builders for

visible

,

disabled

etc? So you can do:

visible { somethingThatReturnsABooleanBinding() }

etc?

that would be super handy

and it can be at Component or Node level 🙂

I'll try at node.

Should we require

ObservableBooleanValue

or just

ObservableValue<Boolean>

? Negating is smoother with

ObservableBooleanBinding

.

But it's less common.

ObservableBooleanValue so you can easily use the negate

Nah, I'll just create something that can turn an

ObservableValue<Boolean>

into a

BooleanBinding

.

Committed:

ObservableValue<Boolean>.toBinding()

converts observable boolean to

BooleanBinding

The

visible

builder is straight forward, but the

hidden

builder requires a little more effort:

@User uploaded a file: Hidden builder checks for BooleanBinding or converts

you expect obs to be at least an observable so the

toBinding().not

works

I'll do the same for

enable

, which negates the

disableProperty

of

Node

.

@edvin How about a visibleWhen instead?

I have that.

In total I've added:

disable, enable, visible, hidden

enable negates on the disableProperty and hidden negates on the visisbleProperty.

Are there more?

Nobody uses managed I guess.

I do in KPhoto