yeah. you'll see the low impedance between the type safe builders and the scene graph right away

can you try setting that to JAVA_HOME?

Didn't work. I think it might have something to do with GTK or my linux config. I need to find sometime over a weekend to look into it.

ok. LMK if you want me to try something on one of my computers. I

ve been running scenic view for years

on ubuntu

Sure.

@carlw have you had any luck running ScenicView against OpenJDK on Linux/Ubuntu? Latest releases depend on some native WebKit symbols that only seem to be exported in the Oracle JDK.

@Gary Tierney OpenJDK version?

not yet. i'll be working with OpenJDK / OpenJFX soon with 11 so I'll give ScenicView 9 a try there

@abhinay 1.8.0_172

RHEL/Fedora builds

Since OpenJDK do not publish JavaFX modules, did you add one?

yes, Fedora ship OpenJFX builds for each of JDKs they ship

So when I instantiate circles as values in a Pane, I don't have to add them; they just show up. The thing is, I want to wait to add some of them, and I can't figure out how to do this. How can you keep them from showing up automatically?

builder functions that give you illusion of not having to add them actually work as

button { /*setup*/ }
// =>
val btn = Button()
btn./*setup*/
btn.attachTo(this)

Thanks

Could you elaborate some? I don't really understand what the pseudo-code means. You set the button up before instantiating it somehow?

short of it is: you can't use the builder syntax to create a UI component without attaching it

it'll always try to attach to the

EventTarget

that the lambda is in the scope of

it does however look like you can tune that behaviour: https://github.com/edvin/tornadofx/blob/3d72e79572d9ac77b1d45b89e62bbbece145688e/src/main/java/tornadofx/FX.kt#L464

but it looks like a bit of a hack

Thank you. Appreciate it.

@S you can also bind to a list that's a variable and add the items to the action handler

@ron I changed the what's new feature of FXLauncher so that it's meant to point to an absolute URL. It turned out to be unusable for subsequent updates since it was expected that the html content was located in the launcher itself (which is not updated on the clients).

Hmmz the idea was that the what's new as a resource available is. I am currently trying to convince my client to use it and they do not allow connections outside of the fab

@ron You can still use it, by giving it a file or classpath url 🙂 It just wouldn't work the way it was written, since existing clients don't get (or need) the new launcher.

@ron If the clients can update the app, that means they can access an url. On this url you could place the whats-new html file

yeah that is the discussion we are having at the moment 🙂

Aha 🙂