I'm at a diner, can give a more complete answer soon, but the best way to deal with this would be to instantiate a ViewModel and stuff it in the DefaultScope. Actually, you even use find from ouside of TornadoFX to get it, and just set the values.

You can use scopes/find even if the app isn't started yet :)

@Ruckus It would be pretty cool if the backend for TornadoFX was pluggable, kind of like SWT :)

Just load core plus the toolkit module you want 😬

Would be a lot of work though.

@edvin would love to hear more about that suggestion when you get a chance . . . in the meantime, i'll do some googling

@edvin That it would, and native isn't where we need it yet, let alone the multiplatform project.

@danko9 Give me 30 minutes and I'll make you a demo app :)

excellent! @edvin

@Ruckus We need to play with this for sure, once things mature a little!

Definitely

@danko9 Here is the app:

@User uploaded a file: Untitled

@Ruckus do you run eclipse with SWT_GTK3=0 ?

I don't run eclipse...

I haven't used it in many years

i do from time to time. i wasn't sure where swt stood with regards to gtk2/3. probably soon will be better with unity dropping from ubuntu

ex, "libindicator"

thanks @edvin !

@danko9 Did it work like you intended?

@evin

@edvin yes, that is what i was looking for, thanks!

Hello, me again 🙂 I ran into another issue using FXProperties. I want to bind a TextField to a StringProperty which depends on another Property. This should be doable with the "select" method from TornadoFX's Binding.kt, but I can't get it right since the property I am depending on is nullable (rather, it's value is). I found some ways of doing it using standard JavaFX, but I hope there is a better way of doing it. Is there?

@doubleu You can use option 4, just do

it?.nameProperty ?: SimpleStringProperty()

, but this is the perfect use case for the ItemViewModel really.

I'd like to check if we do better for this null guard as well.

In any case, don't handle this kind of ugliness yourself, just use the ItemViewModel 🙂

I actually had it implemented the way you proposed - but I felt like the value wouldn't be updated properly. The empty StringProperty we create when the value is null doesn't get updates from my bean's name and the bean itself doesn't necessarily get updated so it may not be rebound ... if that makes sense. In any case; ItemViewModel seems like the way to go. I'll try it out!

@doubleu Absolutely, the ItemViewModel makes this a breeze. If you haven't read that chapter in the guide, you should browse through it. Let us know if you run into issues.

I had a really really bad day at work today so I will try to relax...will check in tomorrow again

@nimakro sorry to hear that... hang in there and try to enjoy the weekend....