-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Come up with a good design for Event handling #4
Comments
Eliminate interface ActionListener => Anything(ActionEvent);
closeButton.setOnAction(void (ActionEvent event) {
print("Bye!");
process.exit(0);
}); |
+1. |
Yes, I agree... creating event handlers inside node declarations should also be straight-forward... Button {
onAction = (ActionEvent event) => print(event);
} |
yes, that also looks very nice. what should be the default value in the constructor – |
I've been making this kind of thing null... it's not shared and the only time I need to check it for existence is when creating the component, simple enough. |
EvenHandling can probably benefit from Ceylon's syntax, similarly to Bindings as on #2.
The text was updated successfully, but these errors were encountered: