@carlw That error you got was actually also due to a change in IDEA metadata, specifying the wrong path for the build. I will commit a fix soon.

@thomasnield You could always use nv3d or something if you need more options. I've been wanting to add a TornadoFX frontend to it, typesafe creation of JavaScript charts, and rendering into a custom component which is basically a webview, as well as the option to render static images. That would be a fun project!

@napperley I'm pretty sure that would work 🙂 Let us know if you try!

I just got the email! Very excited! 🎉🎉

Javaone? That'd be something

@pim Hi 🙂 Can you post a complete sample with your 'MyObject' and sample data?

@Ruckus There is an animation question on SO - not my forte 🙂 Do you know? https://stackoverflow.com/questions/45233063/consecutive-animation-in-tornadofx

@napperley Yeah, you can only bootstrap a single JavaFX App in a single JVM. This is a JavaFX thing, but I did create a workaround for this in our OSGi support. It might be possible to use the same trick for the REPL.

Very nice @Ruckus - just want to stress that if you're doing a one off, you don't need to go all the way with the builder of course. If we created a "how to use GMap in TornadoFX" this could be an optional step 🙂

Does anybody have a working Gradle config for JitPack? Maybe we should add that to the README for the project.

found something...but ext.tornadofx_version = '1.5.9' 🙀

@nimakro Anything SortedFilteredList could help me? Or is there anything else we could do with the framework to help your use case?

@pim I still don't understand why you need the focusedProperty to fire for the datagrid?

@pike This is a good non-Kotlin summary of the technique https://fxdocs.github.io/docs/index.html#_tasks

hello did anyone implement WebScoket client on Java? What library can recommend

@eddy_wm There is also a library from jetbrains https://github.com/JetBrains/Exposed

I finally figured out why I've been having issues with SimpleListProperty mappings in ViewModel. It turns out that they return a hashCode value calculated from the contents of the list, so if anything was changed in the list, the correct facade couldn't be identified anymore.

I tried both

Run

, and

Debug

, with the default app generated by IDEA and it does not reflect changes like label text changed

Maybe

toProperty

is not the best word for it.. Any suggestions?

(

replace

is optional, but you should keep the

trim

so CSS doesn't panic about the placement of the final

;

)

@Ruckus I have another Css question, I see that you defined

baseColor

in

PropertyHolder

I would like to use some other properties defined in the default Stylesheet from JavaFx like

-fx-inner-border

but I can't use

cssprop

. So how would I define some properties in my own Type-Safe-Css class referencing the default stylesheet (Modena)? Or do we just have to add all of the root variables from the stylesheet in

PropertyHolder

if so I would be happy to sent a PR.

It has to be C++ as it runs on a machine

@Ruckus In

gradientsWithErrorColor

, there is a font definition:

font = Font.font(14.0)

. This renders like

-fx-font: normal 14.0px "System"

but the test wanted it to be

-fx-font: normal 14.0pt "System"

. The differens is px vs pt. Is it supposed to render as

pt

? I've changed it now to make the test pass in the meantime.

@pim The type information of an object is only visible in the local scope. From outside it can only be identified as its super type,

ViewModel

in this case

@voddan Did you have lots of Kotlin files in the project that was bogged down by the plugin?

@harshmaur That's easy, you just

add(SomeViewOrFragment::class)

to it at any time 🙂

and apart from that with all the boilerplate nicely abstracted away and tornadofx having full support for CSS, why bother at all with bringing in javascript?

@pim Awesome... I'll try it out real quick...

For anyone interested, the second prototype for the PCB seems to be flawless, I'm typing on the TornadoKeyboard now, and the instability issues I had in the first release (due to a faulty crystal footprint in my cad package) are now completely gone.