<@U78L28DMX> Scopes in TornadoFX grew out of an MD...
# tornadofxc
carlw
11/28/2017, 2:20 PM@amanda.hinchman-dominguez Scopes in TornadoFX grew out of an MDI requirement I had with a client. That's Multiple Document Interface termed from my work WAAAY back as a Microsoft Foundation Classes C++ developer. You can think of it as multiple instances of the same view (same screens / different data). A familiar example would be several IntelliJ windows each showing a different project.
Usually, you'll divide your app into Singletons and Prototype or Instance-scoped objects. There's only one Singleton object in an app like a model component that issues calls to a RESTful web service shared among many views. There can be many Prototype objects in an app, say a pair of details popups each one showing different data, but launched from a common table component.
Scopes were needed for what I was working on because there were many collaborating views and each view needed to be paired with the correct model components. In this case, there weren't Singleton model components since each distinct window was its own app. The scope provided a way for the code to treat the injections as Singleton from a programmers perspective, but the injection would be tuned to the specific window instance.