: maven:3-jdk-8 before_script: - apt-get update - apt-get install -y openjfx build: script: mvn install -B artifacts: paths: - target/KeepassFX-1.0-SNAPSHOT.jar

looks good. i ran into a similar problem with travis ci in bitbucket

@edvin K 1.1.1 was just released and contains the fix for your default param issue.

@thomasnield You ready to give a TornadoFX presentation? 😉

@Ruckus Sweet jambalaya! I'll update to 1.1.1 tonight and test compilation against jvmtarget 1.8 🙂

🙂

It worked! We're now on Kotlin 1.1.1 and JvmTarget 1.8

Sweetness!

So nice. I think we should do a release soon, so everybody can enjoy it easily. Would like to close a few issues together with the release, and we need to test 1.1.1 for a little while before we go, but it could happen pretty soon.

Indeed. Also, coroutines 0.13 was released today with the UI coroutines update.

Quick question: Do we want to try integrating coroutines for our async code 1️⃣ Now 2️⃣ When out of experimental 3️⃣ Never

@Ruckus Are you thinking about hooking in an API that would suspend a process if say a window were closed minimized?

I was thinking about converting our

asyncItems()

calls for data driven controls, but I haven't actually looked into them at all to know if they were a good fit, let alone if it's something we want to do.

But that's not a bad idea

Thetime is now. I talked to Roman Elizarov and they haven't done anything specific to

Task

. They might down the line, or they might not. I think the coroutine support in TornadoFX should leverage Task if possible.

@Ruckus I like that. It could be a nice place to start.

@edvin I think I sent you a link before to some Phaser code I wrote. Do you think this would be a good use case? This kicks a thread off and then blocks until the user interacts, then continues

@carlw That could be a good fit indeed.

@edvin the use case I see is when you have an interactive Task. That's a task where you want user interaction in the middle. The value of the Task is to not lock up the UI

Absolutely 🙂

This is a link to the Phaser video I just referenced. A Phaser is a more general CountdownLatch

My understanding of coroutines aren't good enough yet, I need to get my hands on some use cases.

The use case of "process -> get user input -> continue" is easy without Tasks, but it locks the UI. With Tasks, it's awkward because you're actually working with two Tasks or a wait / notify/ phaser scheme. Maybe a process / suspend / get user input and resume is doable with coroutines?

the value would be to automatically know where you are instead of relying on flags

You can already do that pretty easy with

openModal(block = true)

though.

i'll look at that

oh...the problem is doing that within a Task body...you get the freed-up UI from the Task but a Platform.runLater() causes me problems which is required for the openModal()

Maybe a concrete example would be easier here.

or we can start with @Ruckus 's use case and get some coroutines under our belts

That's probably smart.