Great advice @nimakro regarding the Task . That's the #1 mistake even experienced developers coming to javafx make

if so, the

Controller

instance won't be created at startup because lazy constructed

@Sola The controller will be constructed as soon as the view is used since you are binding the list from the controller to the listview

emmmm.... any better way?

And you can call

SomeController

to

SomeModel

if you like that more, the

Controller

just allows you to inject the class in the

View

TornadoFx

also offers a

ViewModel

but I am not sure why you would need it for your use case, here are the docs to the `ViewModel`https://edvin.gitbooks.io/tornadofx-guide/content/11.%20Editing%20Models%20and%20Validation.html

ok I will take a look, thanks ^^

Here are also some more sample apps for you to get some inspiration: * https://github.com/bekwam/kcircuit * https://github.com/edvin/todomvc * https://github.com/edvin/tornadofx-samples * https://github.com/edvin/github-browser

wow, nice!

oky I hope that will get you started if not let us know....

I am off to bed guys ... talk to you later

@nimakro Thanks! good night ^^

So.. this is how it feels like to step away from the channel for a few hours? 😁 🎉

@edvin you can take over now and clean up my mess

@nimakro You guys did good :))

@edvin I didin't get around to write a few lines about the bindings stuff will do that tomorrow after work.. see you

I will stay home from work for a few hours tomorrow to do the screencast and get the 1.7.5 release out.

@nimakro Sweet!

@Sola you can use an object but a Controller is injectable and configurable.

@thomasnield Just trying to understand your suggestion -- The controller in this case would be where you are maintaining state?

@kastork yes, but please take my design pattern suggestions with a grain of salt. I tend to get critiqued by some more knowledgeable folks in this channel for being a bit improvisational with code separation.

@thomasnield well I've had this idea appear in my code as well. Then I see language in the guide that suggests controllers "are probably" stateless.

@kastork i may need to defer to @edvin on that since he probably established that. Ive used it for stateful contexts too though

I also use Rx so that affects my patterns too

@edvin may be a better authority on replicating those patterns. Id be curious to see what he says

Well, JavaFX is JavaFX, and that's the design

Well put

But TornadoFX has done a pretty good job of introducing pattern flavors

TFX takes a lot of the pain away

@thomasnield I guess fundamentally, the idea of state in the controller is just a way to make it injectable in the context of TFX. I've also done it with an

object

, so you access the singleton in a way similar to Java static method requesting the singleton.