@ron I added you as collaborator to the project, so now you can edit it directly :))

Thanks I wil add some wiki entries explaining some of the setup

I had to look at fxldemo a lot to make it work

Great, thanks a lot :)) Let me know if anything is unclear.

I will

in the weekend I will look at the gradle plugin

see if it needs anything changed

I want to write a Maven plugin as well, Maven pom's become ugly with all the manual stuff needed for FXLauncher right now. The gradle version is pretty simple.

Good! Important to keep the Gradle plugin up to date with new features. It's pretty easy to add features to it, almost no explanation needed.

yeah I found it a bit ugly with all the executions now

@User uploaded a file:

we found this in some old code

look at the warning: "dont be smarted then the jvm"

Hehe!

and look that while loop that code is sponsored by your electricity provider

I wonder why they thought they needed that thing.

the guy that wrote that is retired now (and thats a good thing ™️ )

guessing you guys already saw this... I haven't tried 1.1 at all... https://blog.jetbrains.com/kotlin/2017/02/kotlin-1-1-release-candidate-is-here/

yup seen it

and made me realize that keepassFX is still at 1.0.3 😉

Hm.. Release Candidate.. maybe time to start adapting! I hope the new release of the IDEA plugin is up to speed as well. I've run into so much trouble while testing it in the past.

is it possible to switch back from Kotlin EAP to stable? last time I checked some changes to the IntelliJ API were needed.

@User uploaded a file: and commented: can you not just change the update channel selection?

I haven't tried it...

I remember I had some issues when I wanted to go back.

Tried a few weeks ago and spent the next day trying to get my development environment so that it would work for 1.0 development again...it was frustrating

That sounds like my experience as well. It kind of put me off trying again until the final release..

Then there is no turning back 🙂

About Kotlin 1.1 - I guess we might as well upgrade TornadoFX to it at once when it's released? We could do one final release with any outstanding features, then a new release where the only difference is Kotlin 1.1. What do you guys think?

Sounds good to me