Now I run

Main

, which is an

App

, which creates a

MainView

And in

Main

I initialise

MemoryModel

, which is in Java and must not depend or be related to the kotlin code

The problem is I struggle to understand the way you intended the initialisation to be

MainView

creates UI on init, and it needs an initialised

MemoryModel

I can reach

Main

via

FX.application

, but it is not yet initialised at that point

the only way out I see is to create UI after init

this is unsatisfying

What do you mean by "and it needs an initialised `MemoryModel`"?

Sorry, bad question, let me rephrase..

Why don't you just put MemoryModel in a controller, initialize it and access it from there?

And I don't quite understand why

App

would need to know about

MemoryModel

. Isn't it

MainView

that needs it?

sorry, what do you call "controller"?

isn't it the thing with the

main

?

I may understand the role of

App

wrong

@User uploaded a file: Untitled

@User uploaded a file: Untitled

If app for some reason needs access to the memory model:

@User uploaded a file: Untitled

(Or just find to get to the StateController if you're using Java for the App class)

In general you shouldn't do much in

App

other than instruct the application to show the MainView.

A

Controller

is a singleton injectable just like

View

, so it is a good place for stuff like the MemoryModel

you might even do the

doSomethingIfYouNeedTo

in the init of the StateController

@ron Absolutely, good point.

So

App

is the starting point, but

Controller

is the controller, right?

so that the view or the app don't even have to know about the internal affairs of the controller

seperation of concerns

@voddan Yes, but remember

Controller

is not THE controller, it's just a controller 🙂 You can have multiple, and they don't have a hard connection to any specific View.

I thought

App

was the controller

No,

App

is just a way to bootstrap the application.

👀