I'm still coming up to speed, so I'll take general...
# tornadofx
r
I'm still coming up to speed, so I'll take general Kotlin and TornadoFX comments. There are a few ways to reorganize this -- like pushing the login code into an event hander -- but I think they'll all need a lot of nesting. What I hope to see with coroutines is a code organization closer to the 4-step pseudo code where what is asynchronous and what is on the FX thread isn't noticable. /end 6 replies if we make the coroutines a dependency on tornadoFX pom then it will have no impact on the user of tornadoFX