this almost feels like the problem Per had and what I blogged about?

are the fragments/components initialized

@carlw - they don't support passing parameters

@ron - this is a compile time issue (more of a Kotlin question than TornadoFx)...

@carlw - some of the code was copy/paste - so I could have used the builder syntax there...

@gtnarg are you binding to a viewmodel?

@carlw - just what you see

stepping out for a bit...

@gtnarg The function you're referring to (

EventTarget.add(type: KClass<T>, vararg params: Pair<String, Any>)

) is defined inside

UIComponent

. In your test, you're not inside a UIComponent, hence you cannot call that function, you can only call the one defined outside, which requires a

Node

as parameter.

The reason it's defined there, is so it can utilize the current scope to lookup the Fragment.

@edvin - thanks - makes perfect sense now 🙂

You could potentially do

component.add(find<Fragment1>().root)

, but that means

add an instance of Fragment1 to my adhoc Fragment

, but that fragment already has a root node 🙂

@edvin - would builder support for fragment and view make sense as a feature?

@User uploaded a file: Fragment Builder

and the third post in three days 🙂 https://ronsmits.org/2017/01/tornadofxandguice/

@gtnarg Hmm.. we might be able to add a parameter to the existing

add

actually.

Maybe not. I think the addition of vararg parameters made that impossible. Will try later. First, Jiu Jitsu! 🎆

Let me give it try 🙂

@gtnarg FWIW, I bind Fragments to ViewModels and have a refresh or load entry point in the View that initiates a ViewModel update. The ViewModel delegates an async call to a Model. When the Model returns, the ViewModel is updated. Binding updates the View and all the Fragments. In this respect, the View is just a container and isn't concerned with the details (parameters, initialization, etc) of its children.

Ok, I'm going nuts on this one: How do you get the scene coordinates of a

rectangle

that is placed in a GridPane?

fun getSceneRelativeCenter(): Point2D
    {
        val bounds = myConnectionPoint.boundsInLocal
        return myConnectionPoint.localToScene( bounds.minX, bounds.minY )
    }

In the above code minX and minY are aways 0, which is the same as 0,0 of the GridView itself.

@carlw - if you were going to add a fragment for a specific customer_id (for example) - how would the model know which customer to load?

call viewModel.loadCustomer(id)

viewModel gets an update and the binding updates the fragment

where does the id come from if not from a parameter (sorry if I'm not getting it)?

np. this is more of an FX suggestion to help build an app that doesn't get bottlenecked on initialization, loading, and parameterization 1. Build your View and Fragments as though they were data-less [edited] prototype 2. Add in a refresh method through the View to the ViewModel to the Model (passing the id along the way); this should also involve a Task 3. The ViewModel listens for the Model update event 4. When received, the ViewModel changes a bound property 5. The bound property, part of the Fragment, updates the UI

you can also just pass along an object through this and do away with the Task. Say you have the data already and just need to get it to the Fragment

vJUG is having an event next week covering JavaFX.... might be interesting https://www.meetup.com/virtualJUG/events/235903314

I take it that you manually call the refresh method after instantiating or retrieving the Fragment/View

yes, but not directly. i call it through an onShown, onDock or other event so that my progress bar and status message work while the data is being retrieved

@ron What do you think would be the best navigation construct for Boss? I'm thinking about how to present the menu for content, static files, config, themes, archetypes etc. I'm thinking possibly a vbox of titlepanes (or squeezebox) and inside most of them there will be a TreeView. What do you think? I'm not sure what's the best way to present it, this was just my initial thought.