SB isn't that bad.

@mikehearn You're probably right. I'd like to play a little with the idea anyways. Many of the scene builder concepts are FXML specific and wouldn't be needed in a TornadoFX Builder, while the builders have other specific functionality not found in FXML, so there isn't a clear 1:1 between these things.

i suppose you could start in a simple way: make a tool that links an embedded intellij editor widget with a "live" view of what ui it builds.

@mikehearn @edvin i think FXMLLoader is fair game though

basically, slash the roundtrip time between editing the code and seeing what appears on-screen

I looked a the Scene Buildercode a while back and what should I say it's java and vanilla javaFx code so writing our own with TornadoFx and Kotlin would be also a very nice show case 😉

for instance, step 1 can be to add a new mode to the tfx plugin that uses hotswap very aggressively to refresh the live preview of the window. step 2 can be to extend the plugin to interpret the PSI in-process instead of doing a full compile to bytecode and hotswap. that should eliminate nearly all delay in constructing the ui from kotlin source.

once you have PSI->JFX Scene Graph, you can start going the other way, Scene Graph edit -> PSI

@mikehearn i use the Control+P feature in Scene Builder a lot to see how my screen resizes for example.

yes i like using SB too, but almost always i have to stop using it at some point because i end up needing custom widgets or something, and SB always sucked at handling that.

are your custom widgets packaged as custom controls?

no, normally by "custom widget" I mean "some class that builds some widgets and may inherit from a pane but which isn't a standard javafx thing"

you'll need to make sure you use fx:root, etc. but you can load your custom controls into scene builder http://docs.oracle.com/javafx/2/fxml_get_started/custom_control.htm

Same info, but less Windows XP 🙂 https://docs.oracle.com/javase/8/javafx/fxml-tutorial/custom_control.htm

@mikehearn I love that PSI approach!

@nimakro If the PSI approach works, that would be a fantastic base for a new builder tool as well.

After 1.7.5 and some more slide work, I will start experimenting with Mike's approach.

@edvin Hehe and tomorrow we will have TornadoSceneBuilder 0.1😀

Haha.. unfortunately I'm on my way to Oslo for a seminar tomorrow, so I won't have any play time in a couple of days.

@edvin What is the seminar about?

Oauth2 and payment APIs. It's for work. I don't have high hopes, but the best reason for going to Oslo is a Japanese restaurant I've found, so it won't be for nothing 😬

Just arrived. Ordered frog for the appetizer. Wish me luck!

Hey how do I change the background color of a button when it is clicked I tried this:

navButton {
   and(selected) { backgroundColor += c("#f3f3f1") }
   and(pressed) { backgroundColor += c("#f3f3f1") }
}

but non of them work what am I missing?

@nimakro

navButton and armed { backgroundColor += c("#f3f3f1") }

?

Mhm I guess both pseudoclasses are not what I want

Since I want the button to be a specific color when it is pressed and I just realized that I am stupid I should just use

toggle

buttons in a group 😉

But thanks anyways 🙈

@nimakro Ah, you wanted it to stay clicked. I didn't get that. If that's the case, toggle buttons are indeed the way to go.

@nimakro you might find this post interesting if the toggle group defines an enumerated value http://bekwam.blogspot.com/2017/04/kotlin-radiobuttons-and-enumerated.html

@carlw Thanks I was looking for that