TornadoFX snapshots are noe being published to oss.sonatype.org.

Did you see this one @ron ? https://github.com/edvin/fxlauncher/issues/65

I will check that one tonight on a win10 machine

Perfect!

Here is a two step wizard with shared view model which demonstrates how to do partial commits. I hate the code duplication here.

@User uploaded a file: Untitled

Back in a few hours!

About the way I handle completed state and partial commit above. It's OK, but it would be better if we found a way to tie only the validators created within the current view to the commit and valid calls, without having to mention all the fields explicitly.

I haven't found a good way to record this though.

Maybe it's good enough for now.

Well, I have one solution, and that is to add a list of validators to a View, and then overload

validate

and

required

with a parameter pointing to the view. The parameter would say that "this validator is only valid in the context of the given view" or something like that.

That's a solution that is technically easy to do, but it might be weird, I don't know.

textfield(customer.street).required(context = this)

for example.

Then we could also do

customer.commit(context = this)

to only commit those fields bound to the current view context. Does that make sense, or am I making too much fuzz about a corner case?

We also need a nice way to access the "result" of the Wizard from outside of it. Maybe a callback with the result for example.

Not all wizards would need that, because they might want to deal with the data only internally, but there should be an option I think.

I could try to create an optional typed interface that you can listen to for a result. Trying.

@edvin Is not JavaFx doing something like that with the Dialogs you might get some inspiration there 😉

@nimakro Indeed. I was looking at that as well.

They do it by calling showAndWait and returning an optional.

That's OK I guess. We could support this way of doing it as well. I will still need that interface I think.

Would it be OK if Wizard is always typed?

You would use that for the return type?

I would not like that

Yes, so if you want to get the result from a wizard from the outside you would do:

@User uploaded a file: Untitled

The wizard itself would simply need to set the result:

but what if you work with for example several objects?

which could easily happen with a wizard