Anybody else has a Debian derivative and could run that code?

Works on Mac, even with 100% transparency...

So it's a Linux thing..

Looks like it, I'll work around that. Thanks for your help.

@Marcin Wisniowski JavaFX is lagging a little behind on Java8, but I think many of the issues have been resolved in Java9. After we port TornadoFX to Java 9 (shortly after JavaOne) you could give it another shot perhaps 🙂

No worries, I'm not doing anything important. I just wanted to learn Kotlin, so I decided to make a GUI application, which pointed me at JavaFX and that in turn pointed me at TornadoFX for Kotlin, so here I am. 🙂

Hello @edvin, I promised you that I will make a simple project concerning my dynamic lists. I post this here, so anyone else who has an idea or finds the code interesting can also have a look

This is the project…

I have two issues with this project. When I select a label from the combobox it is (rather than entering the text directly) not saved to the model and empty after I save it, go to another contact and come back.

The other problem is, that the dirty check does not seem to be correct. I will investigate this further. But when I select some other value in the combobox it cannot be saved. I am here not really sure if the line in the viewmodel where I set the dirty value is correct. I would really appreciate it if someone has some tips for me how to fix this problem. Thank you in advance

@dr.fornax Thanks, Stefan. I don't have time today, but hopefully I can take a look tomorrow 🙂

@edvin This is no problem, I am very happy that you will have a look at all 🙂

@dr.fornax I have a feeling this might reveal a bug , so I'm very eager to investigate.

I just started the last chapter in the first part of the Kotlin video course. Talking about extension functions. Guess what I'm extending? JavaFX classes, of course!

I'm implementing some of the principles of TornadoFX, in a simplistic way.

@edvin Thank you again, seems to me too that there might be something wrong. I hope the sample project is helpful. I tried to reduce everything as much as possible.

I look forward to your video

One other question by the way. What is the recommended way to close the TornadoFX application. When I close it by clicking the X in the windows, the app still runs and I have to close it in idea with the stop button. Do I have to implement some extra close function?

@dr.fornax Unless you have changed

implicitExit

, closing the last window or calling

Platform.exit()

would both close the app and stop the JVM, unless you have other threads or some other mechanism that keeps the app alive.

@dr.fornax You can verify this with a minimal sample app 🙂

@dr.fornax I'm testing this too. I'm able to replicate your bug. 1. Select the existing "edvin" contact 2. Add a phone number with the plus icon 3. Select the Business phone type 4. Navigate to the other combobox (tab, return, mouse) 5. Switch to the "stefan" contact 6. Navigate back to edvin and verify the type is cleared

(same with the TextField)

Hey guys, sorry for being quiet these past few weeks. I'm creating a new Kotlin for Data Science video for O'Reilly and going to San Francisco in two weeks to shoot. I do want to seek feedback from @edvin and all the other fellow DSL experts here. I have this example demonstrating how builder patterns can be beneficial in parameterizing and entering data into models quickly.

@User uploaded a file: hotel_builder

And here is the implementation:

@User uploaded a file: Untitled

Can any of you think of any ways to improve this? Or is this pretty straightforward and effective? I'm trying to keep it tight and simple so the value of the concept immediately pops out.

@thomasnield That looks pretty good to me. I'm actually working on builders for the Kotlin video course myself right now.. hehe 🙂 I only have one question: In the

range

function, do you need to repeat the word "Range" on the two parameters? Would removing range make it less clear?

An alternative approach would also be to skip the builders completely and use immutable objects instead. Those would copy the list when you call another function, so you'd get a new object back.

I must admit that I very seldom do that myself, it just feels wasteful to me.