@edvin if you're looking for inspiration, take a look at WPF command binding. a different form factor than the data binding we're used to

@edvin https://msdn.microsoft.com/en-us/library/ms752308(v=vs.110).aspx

@carlw Thanks, checking!

I don't think we'll change it much though, just provide a leaner syntax.

That's my initial goal at least.

@edvin there is no maven information in the guide? or can I not find it?

@ron Hmm... maybe we need an initial chapter about setting up.

Already working on it in the Tools and utilities

@User uploaded a file: ViewModel binding improvements

We can always more it to its own chapter if needed

@ron Great! You've been pretty fantastic lately 🙂 Thank you for all the work you're putting into this.

only lately?!

😉

Especially lately!! Hehe

maven section is pushed, I will look later at the gradle part (need to get my gradle on again)

and added the toProperty to chapter 11

night guys

later @nimakro

@ron Great! I'm done implementing the new binding functions, testing now.

@borboss @ron This is probably the easiest way to support immutable objects now:

@User uploaded a file: Untitled

I haven't committed yet, still testing.

If you have normal JavaFX properties you can now write it like this:

@User uploaded a file: Untitled

For POJOs, you'd reference the getter:

val name = bind(Customer::getName)

Only the

xxxProperty

versions will actually write back to the item on commit, the others must be handled manually in

onCommit

like I showed above.

Passing in a customer as I did in the first example is of course totally optional.

The new binding functions also take the two optional parameters

autocommit

and

forceObjectProperty

, just like the normal bindings.

Commited!

I'll hold off on changing the syntax that the plugin generates until we're sure this works as advertised, but I think we just got a new/much cleaner way to create ItemViewModel bindings! 🎉