too funny...

i had a "9" in there @Ruckus ...I get the 2014 link too if I leave it out

It doesn't matter either way. The oracle link to the presentation is dead (https://oracleus.activeevents.com/2014/connect/sessionDetail.ww?SESSION_ID=3255)

@Ruckus you mean the jsessionid isn't set to 52,560 minutes?

I am pretty new to TornadoFx, I must say it's pretty awesome, kudos to @edvin and all the other contributors. Right now I am working on porting a java application to kotlin and the tornadofx project. That application is using a few dialogs build with the javafx dialog

Dialog.class

with a custom dialog content. While reading through the tornadofx documentation I came across

openInternalWindow

to use this I would have to implement the whole dialog by myself? I wanted to know how you guys are implementing dialogs? Are you using the dialog api from javafx, fragments or both? Which way should I prefer and why?

I haven't used a whole lot yet, but I have been using the "standard" dialog... not implementing my own.... I haven't needed anything to specialized yet....

@nimakro Hey 🙂 I use the default JavaFX dialogs for simple questions and the like, and quickly change to

openWindow

,

openModal

or

openInternalWindow

and create the content myself. It's not a lot of code, especially if you use the form builder. I find myself using the

builderWindow

more and more actually. You get the title and close-button "for free" but add your own buttons. However, we could even cut down even more of the boiler plate by creating a

dialog

builder based on a

form

builder. That's actually a good idea, I'll investigate a little 🙂

@edvin Yeah I think I will go with the builderWindow for now ... I think a

dialog

builder would be great... let me know if I can be any help ...

@nimakro here is an example of an internalWindow

gods that processing takes a long time

@nimakro Great! I think I'll add a

formWindow

first, and then a

dialog

based on that, with some default button actions etc 🙂

jup @ron I can't see your example

yeah its saying "processing uploaded file for a long time

😉

fun setupUpLockoutScreen() { val passwordEntered = SimpleStringProperty("") subscribe<lockScreen> { openInternalBuilderWindow("locked by idletime", escapeClosesWindow = false, closeButton = false, overlayPaint = Color.BLACK) { vbox { alignment = Pos.CENTER prefWidth = 400.0 form { fieldset { field("password") { passwordfield(passwordEntered) } buttonbar(Pos.BASELINE_RIGHT) { button("unlock") { setOnAction { if (controller.repository.isEqualToPassword(passwordEntered.value)) { close() controller.startIdleTimer() } } } } } } } } } }

@ron Insert code snippet instead 🙂

@ron File upload isn't working. Most likely it has something to do with AWS going down.

I did that is still processing

Ah 🙂

@ron Why do you have a

vbox

around the form?

You can probably get rid of the

vbox

, the

alignment

and the

prefWidth

and it will still look good.

I still need to add something like a status bar to it signalling that password was not correct

the prefWidth i need to force to make room for a large input field

@edvin Sounds good, we should also think about the button ordering, because I think the cancel button is ordering differently depending on linux/windows

most people I know have long pass phrases to unlock their keepass files

@nimakro That's right. For a typical dialog we should take that into consideration indeed.

mine is something like 40 characters

@ron thanks for the example

@ron Then it's probably better to set the preferred number of chars on the textfield, so it can scale correctly.