interesting I also see components like tableview as completely self containing. If an event does something onthe tableview I would expect it on the tableview and not on the scene

Depends how you look at it. I put listeners on TableViews sometimes too. If there are multiple TableViews per Scene, then you'd need to make a distinction with my + shortcut. However, in this case, there were many screens for which the TableView was the main component. Putting the listener on the Scene allows the user to activate an AddRow operation when the window has the focus rather than the component.

...actually i should point out that the + operation in these cases adds a model object. The AddRow is just the presentation result.

New question, I already answered. Feel free to answer if you have more details. http://stackoverflow.com/questions/40551886/how-to-run-tornado-fx-hello-world-with-java-7/40553787#40553787

@thomasnield Dialogs.kt and ErrorHandler.kt use the Java 8 Alert class which is available only in 1.8.0_40 and up (not all Java 8’s will work with TornadoFX)

Okay you're welcome to add that if you want. I can do it too

is there a system requirements section of your documents?

There is not, but that probably would be a good addition.

That should be in the beginning. I'll add it later.

@edvin: @jakub.dyszkiewicz had some questions about FXML in TornadoFX (in the #general channel)

@Ruckus My current TODO example still features FXML. TornadoFX fully supports .fxml. I agree with Jakub’s comment in the general forum that Scene Builder is important and in line with other popular desktop toolkits like MS XAML, Apple Interface Builder, and Qt. https://github.com/bekwam/todomvcFX/tree/master/examples/tornadofx/src/main/kotlin/todomvcfx/tornadofx

I have nothing against FXML or Scene Builder. I prefer the UI DSL, but it's purely personal preference. My point was just that I'm not the one to ask :)

I’m also a bit confused about View vs Controller in TornadoFX. In JavaFX that was clear for me. FXML was the view, you bind components in controller pass flow to model where the business logic is stored. So when using TornadoFX with FXML, FXML is the view but you also have the class that subclass View and binds components.

so TornadoFX View = JavaFX Controller?

@jakub.dyszkiewicz That's correct, but think if View as a View Controller. A Controller should be used for non-ui stuff like business logic etc that you don't want to have in your view controller or other shared logic.

A View typically has even handler functions, but would call out to a Controller for the business logic or remoting/database calls

So I guess every MVC is different, I would be downvoted on gerrit for putting business logic in Controller in our Spring MVC project 🙂

@jakub.dyszkiewicz TornadoFX doesn't really force you to do this in a specific way, but I think it's a general consensus about not putting business logic in with your view handling logic. Every UI will have some code to deal with user interaction and that's strictly not business logic. I personally think this code belongs in a place quite close to where you build the UI.

@jakub.dyszkiewicz A typical example. Let's say you have a view with a save button and you want to save the current customer when the button is clicked.

So I would create Controller that handles click, maybe translate data structure and calls CustomerService.save(data)

@User uploaded a file: Untitled

Yes. As you can see, the button handler calls the controller (or service) function. Let me rename that

nothing wrong with the name controller 😉

Yeah, I get it 🙂

In the example above now, the

CustomerService

extends

Controller

.

OK, great 🙂

just one thing there.

by inject()

. Do I have to register CustomerService somewhere?

no

tornadoFX will find it for you

No, not necessary. By the way, if customerService does time consuming stuff like writing to a database or performing a rest call, it should be wrapped in a

runAsync

block. In that case, som people think it becomes too much code inside the button handler. I will update the example to show the best practic in that case.