your visions are usually 🆗 by me

Sweet 🙂

AWS is partly back

"Update at 1:12 PM PST: S3 object retrieval, listing and deletion are fully recovered now. We are still working to recover normal operations for adding new objects to S3."

Looking better from here 🙂

@User uploaded a file: Possible dialog builder, without the optional buttonbar for now :)

This might not be general enough that the builder should be named

dialog

. It could be called

formDialog

perhaps.

@User uploaded a file:

@edvin do you have any builders involved in the JavaFX Alert class? I put custom content on that and it has a built in way of handling the buttons

@User uploaded a file:

@ron I guess we don't need the alignment parameter to the buttonbar builder anymore, right?

@carlw Yes, there is an

alert

builder 🙂

@carlw

alert(INFORMATION, "Heading here", "Content here")

It also has overloads for buttons etc.

i've added a content node for simple forms like logins using Alert

Maybe that's better than my current approach. Will investigate further tomorrow 🙂

It seems buttons inside a ButtonBar are added to the right by default on Windows.

I thought they would appear starting from the left.

Here is the dialog again with the shiny new buttonbar options specified. They aren't needed in most cases though.

@User uploaded a file: Untitled

@ron I committed this so we can discuss and explore more tomorrow 🙂

Haven't tested Forms thoroughly after the changes yet, will do that after we've examined this more closely.

@User uploaded a file: Dialog test

@edvin This piece of code gives an exception because of the requires

@User uploaded a file: Untitled

the exception is

java.lang.IllegalArgumentException: The addValidator extension on TextInputControl can only be used on inputs that are already bound bidirectionally to a property in a Viewmodel. Use validator.addValidator() instead or update the binding.

I would expect the

passwordEntered

to be bound correctly to use

required

The buttonbar works well, I do have to specify the ButtonData to make them show up in the correct places

@ron

required

only works when the bound properties come from a ViewModel. That's also where the validation rules are saved.I can look into supporting

required

without a ViewModel though, it's such a common requirement.

Actually in your case, you should use a viewmodel and validate against the current password. With your code right now you wouldn't get an error message if the password didn't match.