@nimakro How about put Event Bus in Utilities, leave OSGI off entirely

That would give you room on the right for another category, maybe

Application Framework

in which to put

Workspace

It just occurred to me, Dependency Injection might be worth putting somewhere

Yeah I think I will put

EventBus

into

Utils

and then make another box on the right for

Workspace

or workspace could be a layer above what you have now

Maybe I call it

RPC

and add DI as well

since it does rest on all the basic TFX capabilities

can I access UIComponents (defined in

View

) in

controller

?

or maybe I shouldn't ?

@kastork Yeah I could do

Workspace

on top and maybe OSGI beside it and then have DI underneath and then the rest ... let me see how I can rearrange things... thanks for the good input will check back later

@Sola Why would you want to access UIComponents in your controller?

@Sola You can inject a View into a Controller if that's what you're asking

@Sola and you can assign view nodes to `val`s

oh! I see, Thanks very much 🙂

Still curious what kind of manipulations you want to do the the view nodes in your controller

hmm.. is it not recommended?

@kastork @Sola I've used it several times. It depends on your workflow.

Well can you enplane what you are trying to achieve?

update status label ..

@Sola you should bind a property to your label for that

and update that property?

There are several ways to do such things in TornadoFX. Injecting views/controllers and calling functions, have a property you can bind to, use the Event Bus. I think the preferred way is which ever way works best for what you're doing.

oh.. sounds it's a better way to go

If you want to update the message from several different places, you could use the event bus and fire an event message.

Then you don't even have to worry about injections.

yeah, I didn't notice that

I'm new to fx world , surprised by your help 🙂

We were all new once 🙂