Yeah, I think I super don't get this stuff heh

Every time I get something, then I try to do something more, and it doesn't seem to make intuitive sense.

So I should make a list of itemviewmodels that use a class containing my properties?

Hi, I'm a total noobie in JavaFX/TornadoFX, coming from server-side. I'd be greatful if someone explained. Why does tornadofx have two IoC mechanisms? Namely -

by di()

and

by inject()

. From samples I understand that

inject()

is for tornadofx `Component`s,

di()

for everything else, but why not keep one and inject everything with it? On an off note: I wish people used threads 🙂 On a note even more off: I wish Slack UX team made using threads easier and a more obvious choice.

I had some of my runAsync's in the controller, because that is where I know how to calculate progress for task.updateProgress(). But the view presumably is the thing that should be calling task.cancel() and task.updateMessage(). Right now I'm putting runAsync in the view and passing the FXTask to the controller so it can call updateProgress().

@sbyrne mmm, aren't the tasks off the background thread? As long as you have a reference to the thread, you can probably cancel/update from where ever right? My impression is that when you do something on the UI, you're just passing the result of the background thread to the front, but that doesn't necessarily end the background thread

@sbyrne I'm actually looking at that PDF - it has an example of what you might be talking about at page 54

@Czar oh wow I just found it here: https://edvin.gitbooks.io/tornadofx-guide/part2/Dependency%20Injection.html

This is REALLY cool, you can use

by di()

when you create dependency containers! This kind of reminds me of dagger or other third party injection frameworks

by inject( )

is more TornadoFX specific for the singleton instances

wow... the possibilities of being able to write larger applications and not having to couple so much. This is awesome! I normally write smaller applications so I don't have as much of a need for

di( )

containers, services etc. But I'd like to start getting there soon

I started working with Android the last half year, and I'm now working with Dagger in Android, and it's been a painful but necessary growing experience. I feel like a lot of concepts their have helped me better understand TornadoFX, for sure

Yeah, for me it's quite hard too, after 11 years of developing server-side almost exclusively 🙂 UI is confusing, UX even more so. So I try to reuse as much as I can from what I know, and I know Spring, so when I saw tornadofx can integrate with it, I jumped on the opportunity.

The specific problem it solved for me for now is my trouble with tornadofx

Rest

component it just isn't able to do some of the stuff I need and isn't flexible enough for my use case.

One thing I'm still trying to wrap my hand around are all the

runAsync{}

runLater

and friends. I'm using a reactive client and it's a bit painful 🙂

I'm not even sure if a proper way of integrating those exists or I'll have to write my own integration layers for Spring's reactive stuff, like `Mono`s and `Flux`s, to work seamlessly with tornadofx

what are you trying to do right now?

As usual I've picked quite ambitious pet project for learning desktop programming - I'm writing admin panel for our p2p lending system, the production uses a single-page web application for that, it's a bit dated and not easy to update, especially for people who doesn't like working with front-end web stack 🙂

So I've decided to write my own, new and shiny, and Kotliny 😄

Love it! I turned to TornadoFX because frontend burned me too many times. It's far more secure and stable as well.

So in your case, you have a rest client, and you're not able to do what? It sounds like it should have the ability to complete your requirement

@gtnarg I'm looking into

interact { }

now for testing. Giving it a shot. burned out a couple days ago. Does anyone know where I can look into documentation for that?

Now I'm able to do everything, initially problem was that tornadofx

Rest

component is not reactive and also its configuration approach isn't flexible enough for me. So I've switched to Spring's WebClient. This part already works in my application, I've even implemented log-in/log-out and can make authenticated requests. Now the real work begins - building all the screens and workflows, but the parts where reactive `Flux`s and `Mono`s touch with tornadofx stuff are a bit ugly.

So probably I'll try to get a grasp on this part before continuing with aforementioned screens and workflows 🙂

If I remember tomorrow when I'm at work, I'll post an example of what I'm talking about. I don't have access to that code at the moment.

Feel free to pop on here if you get stuck somewhere!

So far my question stands about

di()

inject()

I don't understand why the separation. Other frameworks I've seen which allow IoC container integration ususally just merge their own IoC with the one they're being integrated with.

If you're injecting a model/view/controller component, no work is needed to set up having to provide/inject the resource other than calling the inject. Otherwise, a little work might be required to set up that dicontainer

Ya'll I got the basics of TestFX application I'm actually crying I GOT it. I'll write a blurb on live testing your application and share it on here since you guys have been so AWESOME and helpful. Thank you all again for your help 😭

And, you can absolutely add ids dynamically to certainly elements in your test even if you don't have it in your project