In fact, there should almost never be a need for doing

javaClass.getResource

in a TornadoFX component 🙂

If you're struggling with understanding builders, this SO question and answer might provide some insight:

Builders can have unwanted side effects if you don't understand their context.

Has anyone done anything significant with SVG and TornadoFX or JavaFX?

What do you mean by “with SVG and TornadoFx or JavaFX”? There is no SVG in JavaFX but the concepts are so close that it is not a big problem to do the same.

@carlw ^^

This and how well it covers different SVG strings

Ok. I understand what you mean. SVGPath is only one component of SVG. It appeared during our development that SVGPath in JavaFX was not very good. We used https://docs.oracle.com/javase/8/javafx/api/javafx/scene/shape/Path.html which gives exactly the same results than a “real” SVG path.

@gaetan uploaded a file:

It’s now almost pixel perfect. Kotlin/JS on the left inside chrome. Kotlin/JVM on the right with JavaFX.

thanks gaetan. do you work with SVG at all in your data viz application as an external interface? something you translate to Path?

We use a common multiplateform API and then translate it in “what we find” on each plateform. 😅

We are currently working on the Android version of it and it may impact the global API.

This the JavaFx version of our path: https://github.com/data2viz/data2viz/blob/master/path/d2v-path-jvm/src/main/kotlin/io/data2viz/path/PathJfx.kt

You may also have a look to https://github.com/hudsonb/kubed/ which is focused on JavaFX viz.

I specifically mention kubed because on this problem with SVGPath we used kubed’s solution.

thanks. those links are helpful

@gaetan that's beautiful! And it's multiplatform

hi, i guess this is the best place to ask questions about how to tornadofx ? i am trying to use a treeview (or treetableview) to update its contents when the model in the controller changes, so far rebindOnChange seems to not do what i want at all

so far i have this

kotlin
treetableview<EntryWrapper> {
    root = TreeItem(controller.selectedModel.rootEntry.value)
    ....
}

and tried

kotlin
 controller.selectedModel.rebindOnChange(this) {
    root = TreeItem(rootEntry.value)
    populate { it.value.entries }
}

inside the treetableview

@Nikky This example might give you some ideas. I don't think manipulating the UI control like I'm doing is the best way to go, but it works. If you have a directory selected, the Add button will put a new entry under it. If a file is selected, the Add button will put a new entry as a sibling of the selected item.

For working with the model, you can post a model update even back to the view layer using the EventBus. The view code will capture the event and reconcile the change with the data.

@edvin looks like there's an open issue on this #51. i think the inline editing of a treeview is handled by properties, but it seems like adding and removing items needs to work directly with TreeItems that aren't bound to anything

so will this work to change the root item and then repopulate the children given the lambda from populate ?

i have a list of packs, selectiong one should change the secpcond column to display the nested entries, selecting one will change the third colum to the editor

I was keeping the root item and adding in the items. Are you swapping out a whole new root item? that can work with binding which makes the code look better. however, i think it will collapse the tree which might cause the viewer to lose their place post-update

yes well its a whole different set of data so its fine if it collapses