class MyFragment : Fragment {

val profileVM : ProfileViewModel by inject()

@gtnarg That's what we're calling multi-tenant or MDI (multiple document interface from a 90's Microsoft term). The same View hierarchy is duplicated for a different set of instances. If you use IntelliJ IDEA, think of multiple Stages, one per Project.

@edvin How do you open a modeless secondary stage for a View? Do I create a Stage() and add the root to a Scene()?

this doesn't necessary have to be in a secondary stage - you could be opening a second document in a new tab in the same stage - correct?

I think so. I mostly deal with this scoping at the Stage level since that’s a strong application partition. There’s a case at the docked panel level if your application is architected like Eclipse

For me, the Stage will contain a whole complement of collaborating UI controls including menus

So eclipse and intellij are different in that respect?

IMO. intellij brings up multiple Stages for >1 project, eclipse has a workspace container that can host different projects (you don’t need extra windows)

a little bit of a gra(e)y area because intellij encourages modules in which case you’d use just one window

Okay - now I understand

I just created my second project with a wireframing tool called Balsamiq. That opens up a new window for a new project too

have to go do some yard work - we had 5 cm of snow night before last - today it's supposed to hit 20 C (about 70 F)!

O'Reilly just got its first Kotlin content https://player.oreilly.com/videos/9781491964118

@gtnarg me too…no snow but plenty of leaves

New SO question

Cool 🙂 I answered it, but when I posted it I saw that somebody actually beat me to it.

Finally back from the cabin, been working there the whole day, will try to catch up on everything later tonight.

@carlw About singleton, that's right. Now they become "singleton for current scope", so we need a better name for this if possible.

@gtnarg Correct, every object created or looked up within the context of a scope will belong to that scope only, unless you call

inject(someOtherScope)

or

find(viewtype, someOtherScope)

. There is a "global/default" scope available called

DefaultScope

you can use if you want to access "global singletons" from within another scope.

@carlw Multiple stages per View? I don't quite follow. Sorry for beeing dense, can you illustrate what you want to do in more detail? I've never had the need to touch Stage/Scene "manually" in a TornadoFX app.

@edvin one stage/one view…i was wondering if there was an openModeless()

@edvin - that was me 🙂

@edvin … I think scoped is fine. you see that in Seam, Weld, Guice, JavaEE, etc (RequestScoped,SessionScoped). Singleton should be reserved to single instances

@edvin - will scope ever get released (i.e. destroyed) so that it can be garbage collected if it's no longer needed?

@gtnarg scope should definitely be released. There should be a deregister() function for example. In the case I’m concerned with, the closing of a Stage closes the scope, releases scope-related resources and references

@gtnarg This ends up being a usage thing. For example, an HTTP request scoped object is released when the request is over. A HTTP session scoped object is released when the session is over (maybe a server reboot?). A Seam long running conversation scoped object is defined when a line of demarcation is crossed ending the converstation (say checking out of a shopping cart)

@carlw - I agree. Things like request scopes can be handled at the framework level. In this case, I believe we need to be able to "deregister" it as you mentioned. I'm just curious if it was built this way.

@gtnarg i’m mentioning the web stuff b/c it’s come up with the jpro stuff. if you use a Seam conversation scope or a JavaEE stateful bean, then it’s on the programmer to come up with when these things are closed out