@thomasnield Sounds good. I will let you guys know how this one goes. Our group is usually small and desktop programming is even smaller. But if it seems even remotely promising maybe we can do something in the future. Thanks.

@jchildress Sure, let us know. Try selling it as "building apps", even if it's for desktop.

Good idea.

apps work better with those young ones

@ron funny 🙂

"young ones"

its true

agree 100%

my eldest stepson studies informatics and only talks about apps and games

and when he shows me I go like thats not an app thats a desktop application and the "dazed and confused" look he gets.......

@dominik.petho @ron I'll look into touch support for datagrid tonight :)

@ron @jchildress I sometimes refer to the analyst desktop software I build as "business apps". Just a much more effective buzzword

@jchildress Exciting!! 👏

@jchildress Will it be filmed?

@edvin not sure about the filming. They don't as far as I know, but I will ask again.

@edvin You're doing this right? https://blog.jetbrains.com/kotlin/2017/03/announcing-kotlinconf/

@edvin thanks so much, appreciate it.

@thomasnield agree...

@thomasnield I want to 🙂

@dominik.petho What touch actions are you interested in?

@jchildress OK! So happy you're using TornadoFX for this :))

This some code for the coroutines proposal I was discussing earlier. The algorithm is simple 1. Do some initialization 2. Prompt the user to login 3. Login 4. Do some more initialization

The code needs to use JavaFX Tasks extensively otherwise the UI will become undesirable. On Windows, this is "Not Responding", on the Mac a spinning beach ball, and on Linux, a grayed-out window.

The code relies on several nested Tasks, each one spawning new activity in the FX thread safe succeeded() method (called "ui" in TorandoFX"). Additionally, I have to put handlers on all the failed() possibilities or the errors will be swallowed.

@User uploaded a file: Coroutine Candidate? and commented: Deeply nested Tasks to keep the UI responsive

@carlw I am not that experienced with TornadoFx yet but for the Login Fragment you could use the form-builder which takes care of the spacing it self, if am not mistaken.

@User uploaded a file:

Beware guys that @elizarov answered Carl in a thread 🙂 I know we've missed thread answers before so I just wanted to make it clear. This is very interesting stuff! I'm back at the office in 2 hours, will look more closely at it myself then.

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

@edvin I was testing the touch events on my Lenovo and think your Surface idea will help with Raspberry PI DataGrid testing. My Lenovo responded to the full complement of JavaFX events: touch, swipe, mouse.