hmmz I never saw javafx as having an event bus. It has events, but I would not call it an eventbus 😉

are there any examples about the itemFactory?

@ron Any Node can be used as an event bus, it has everything you need: A way to register and deregister listeners and a way to fire events.

@ron You can add the

itemFactory

like this:

populate(itemFactory = { TreeItem(it).apply { isExpanded = true } }) { .. normal stuff here }

hmmz this

`
with(root) {
            root = TreeItem<OrderPart>(part)
            populate { parent -> parent.value.orders }
            openallChildren(root)
        }
    }

`

is the current part

@User uploaded a file: Untitled

I didn't try this so there might be some syntax errors, and it's kind of ugly calling a function with multiple lambdas. Sorry about that.

(Remember to remove the openallChildren call)

I will try it out tonight, I also have to check what changed between 1.5.2 and 1.5.7 to mess up my already messed up layout 😉

Haha 🙂

on another note, I am doing a miniconf on november 27th about tornadofx (pure for the company I work for) I will show this channel too 😉

Cool @ron 🙂

@edvin for the javafx event bus, do you mean sending a custom event around?

@carlw Yes

@edvin that might be a little too restrictive. i think you would need specific nodes that are participating to be in the even fire method. delivery in a scene graph is going to be limited to one pathway

@carlw Basically, you can create a node (any node) in a scope, and use that. That node doesn't need to be part of a scene graph. The creation of this node can also be hidden. No need to even give access to the node, we would simply add some functions to

Scope

.

i'm going to be looking at this later today (unrelated to tornadofx). i've done something similar to what you're describing. IMHO i'd like to see something off the FX Thread so that I can pub things in the middle of a Task

plus there may be some additional services that a general pub/sub capability brings in like filtering or a more sophisticated delivery system

@carlw Great! I was just thinking that there might be little to no value in reusing the existing event bus. Implementing the Event class from JavaFX is a bit cumbersome as well. Let me know what you find. Maybe you could write an event bus for TornadoFX? I think Scope is a good place to put it.

I'd base one on a library like RxJava (notifications.subscribe(), etc). I'm thinking singleton since it's app-wide

I see. OK, I might add one in TornadoFX as well though, not based on a library.

I'd be interested to see your implementation in any case 🙂

@User uploaded a file: and commented: For the mvvm, this notification mechanism would be the "PropertyChanged events" in this diagram

a specific use case that comes in mind is a non-JavaFX View element like SwingNode

this will avoid ViewModel needing a reference to the View

the diagram is from Microsoft's docs here https://msdn.microsoft.com/en-us/library/ff798384.aspx

@edvin i think you're right about not adding a library to keep that dependency away

Model change events is already pretty well covered in JavaFX though.

Off topic... I might be getting lazy or spoiled with Kotlin, but is there a more concise way to do the following: